This message was deleted.
# azures
sparse-intern-71089
02/23/2022, 6:14 PMThis message was deleted.
c
clever-byte-21551
02/23/2022, 9:52 PMFurther investigating this -
After upgrading we are forced to recreate the cluster like a said.
Subsequent stack updates won’t trigger recreation however - let’s say I just modified node count for the system agent pool -> it forces an entire cluster recreation while it never should!
Something is obviously broken and we’re unable to upgrade to newer versions because of this.
I thought about trying various versions but these tests take forever as recreation takes ~15-20 minutes each time..
clever-byte-21551
02/23/2022, 10:28 PMUsing our existing stack definition, running update stack from scratch in version 1.59.0 works, cluster is created successfully
However subsequent call to stack update triggers an entire cluster recreation..!
There’s definitely some regression, how can I check which field triggered the recreation?
I’m only seeing this:
Copy code
aks updated [diff: ~agentPoolProfiles]clever-byte-21551
02/23/2022, 10:35 PMAnother issue that happens occacionally during these cluster recreations
Copy code
azure-native:containerservice/v20210501:ManagedCluster (aks):
error: 1 error occurred:
* Code="ReconcileMSICredentialError" Message="Reconcile MSI credential failed. Details: autorest/azure: Service returned an error. Status=404 Code=\"NotFound\" Message=\"Resource '/subscriptions/XXXX/resourcegroups/dev-eu1-eastus2-xxx-orchestrator-rg-kMr7/providers/Microsoft.ContainerService/managedClusters/xxx-orchestrator-aks-v2p-eastus2-kmr7' was not found.\"."clever-byte-21551
02/23/2022, 10:46 PMhttps://github.com/pulumi/pulumi-azure-native/issues/1532
Created a ticket with all the information
clever-byte-21551
02/23/2022, 10:47 PM@happy-parrot-60128
13 Views