Closed PashaPash closed 8 years ago
@PashaPash, thanks for reporting, we'll check this case.
@dtretyakov I also noticed that cloud instance is now marked with exclamation mark / "No agents connected after instance start" and it remains in that state even if agent is manually started/connected/authorized.
It seems that TeamCity just cannot match the cloud instance with the connected agent. Please let me know if you will need any additional info to reproduce the issue.
@dtretyakov it seems that I found a workaround - server-side plugin expects the azure.instance.name
parameter set on agent side.
For image-based instances that parameter is passed as a part of a CloudData and mixed in to the agent properties by AgentConfigReader
.
For pre-configured VMs that parameter remains blank (because of no provisioning/no CloudData availble), and server-side plugin fails to match the agent with could instance.
Workaround is to manually specify that parameter in buildAgent.properties
:
azure.instance.name=azbuild-d2-1
@PashaPash, you can try to download latest azure classic plugin version, where automatic authorization was fixed: https://github.com/JetBrains/teamcity-azure-plugin#classic
@dtretyakov installed a new version, agent authorization works correctly now. Thanks for a quick fix!
Cloud agent connects as "Unauthorized" if started by azure service.
Teamcity successfully started the VM, Agent went to "upgrading" state, then to "unauthorized".
Agent is displayed as "Launched" on Cloud tab:
but it not available on new build dialog, so it seems to stuck in some "starting" state:
teamcity-clouds.log:
then just a number of repeated
getDetailedAsync
calls.Agent-side log:
Could be related to #25, but I'm using pre-configured VM and it just starts and fails to authorize.
Please advise.