spinnaker: Failed to trigger the bake and deploy pipeline
Issue Summary:
It failed to trigger the bake and deploy pipeline (createServerGroup) and it failed to trigger the disable and destroy pipeline. After investigated, it seems that the failure is caused by the commit https://github.com/spinnaker/clouddriver/pull/5791. If reverted this commit, it works fine. @ovidiupopa07, so could you take a look this issue and fix it asap since we’re blocked now? Thanks.
Error Message while triggering the bake and deploy pipeline:
{
"phase": "ORCHESTRATION",
"status": "Orchestration failed: CreateAzureServerGroupWithAzureLoadBalancerAtomicOperation | ManagementException: [Status code 400, "{ "error": { "code": "LoadBalancingRuleBackendAdressPoolAndBackendAddressPoolsCannotBeSetAtTheSameTimeWithDifferentValue", "message": "BackendAddressPool and BackendAddressPools[] in LoadBalancingRule xxxx-st-frontend-rule0 cannot be set at the same time with different value.", "details": [] }}"]"
}
Error Message while triggering the disable and destroy pipeline:
"type": "determineTargetServerGroup",
"name": "determineTargetServerGroup",
"status": "TERMINAL",
"context": {
"exception": {
"exceptionType": "NotFoundException",
"shouldRetry": false,
"details": {
"stackTrace": "com.netflix.spinnaker.orca.clouddriver.pipeline.servergroup.support.TargetServerGroup$NotFoundException: Unable to locate current_asg_dynamic in my-azure-account/westus2/xxxx-st-frontend\n\tat java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)\n\tat java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)\n\tat java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)\n\tat,
"error": "Unexpected Task Failure",
"errors": [
"Unable to locate current_asg_dynamic in my-azure-account/westus2/xxxx-st-frontend"
]
},
"operation": "determineTargetServerGroup"
},
Cloud Provider(s):
Azure
Environment:
ubuntu 18.04
Feature Area:
Clouddriver
Steps to Reproduce:
- hal config version edit --version branch:upstream/master
- hal deploy apply
- Create a new Spinnaker Application
- Create a new load balancer
- Create the bake and deploy pipeline
- Create the disable and destroy pipeline
- Trigger the bake and deploy pipeline. This creates a new server group below the given load balancer but it failed
- Trigger the disable and destroy pipeline but it failed
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 17
Commits related to this issue
- fix(provider/azure): Fix CreateAzureServerGroupWithAzureLoadBalancerAtomicOperation and DestroyAzureServerGroupAtomicOperation after migrating to latest Azure SDK After the migration of the SDK to co... — committed to armory-io/clouddriver by ovidiupopa07 2 years ago
- fix(provider/azure): Fix CreateAzureServerGroupWithAzureLoadBalancerAtomicOperation and DestroyAzureServerGroupAtomicOperation after migrating to latest Azure SDK After the migration of the SDK to co... — committed to armory-io/clouddriver by ovidiupopa07 2 years ago
- fix(provider/azure): Fix CreateAzureServerGroupWithAzureLoadBalancerAtomicOperation and DestroyAzureServerGroupAtomicOperation after migrating to latest Azure SDK (#5803) After the migration of the S... — committed to spinnaker/clouddriver by ovidiupopa07 2 years ago
Hi @neil-yechenwei. I fixed the issue:
The disable and destroy pipeline works too

I will open a PR later today. Thanks for pointing this out 👍
Actually, I just saw something. In the old SDK, there is only one property
backendAddressPooldefined inLoadBalancingRuleInner.In the latest SDK there are 2 properties
Anyway, I will check how can we fix this.
Hi @neil-yechenwei. Unfortunately, I was out last week and had to take care of some personal matters. I started to work on this issue yesterday. Currently, I am trying to setup everything on Azure -> to reproduce the problem. I will let you know when I have something to share.
Yes, I agree, I will fix it for sure. I was mentioning this as a workaround until I fix the issue in the master branch, just to unblock you. I will let you know when I push the fix.
@ovidiupopa07 , Sure. Hopes it would be helpful.
The json content for Bake and Deploy pipeline:
The json content for Disable and Destroy pipeline: