MicrosoftHi, posting here out of desperation. I am consistently seeing the issue mentioned in this article where the local administrator group is not populated with the correct accounts and NT service accounts. The first failure this causes is at the "Install the update orchestrator" stage where we get this error
WatsonBuckets": null }, "Message": "AzureStack File Copy Agent is not running.", "Type": "HealthCheckException", "CallStack": "HealthCheckException: AzureStack File Copy Agent is not running.\r\n" } }, { "ErrorType": "ResourceFailureLocalGroupMembership", "ErrorInfo": { "Exception": { "ClassName": "Microsoft.AzureStack.Infrastructure.Orchestration.AgentLifecycleAgent.ResourceManagement.Exceptions.LocalGroupMembershipException", "Message": "Failed to set up membership for NT SERVICE\\AzureStack File Copy Agent", "Data": null, "InnerException": { "ClassName":
You can watch the event logs whilst the deployment running for it constantly trying to create this service, which I assume is failing due to it not being able to add the service account to the local admin group.
Permissions have been verified for the deployment user (its in the administrators group on both nodes). I have a long running case open with MS but we are going around in circles at the moment.
I notice this exact issue is mentioned here and thought i'd reach out to see if anyone else is having / has had this and knows of a cause of fix. I am nearly in double digits for the times i've flattened and rebuilt / re-deployed this cluster!
All help greatly appreciated whilst I still have some hair
