ESX Agent Manager - AgentVMs not powered on
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 763
- PR merge metrics
- No merged PRs in 30d
Description
After deploying Agent VMs through ESX Agent Manager, AddHost to the cluster deploys an AgentVM on the new host, but the AgentVM is not started/poweredon.
Similarly, Exit Maintenance mode of the ESXi host does not start/poweron the AgentVM.
Is it something that needs to be a property of my AgentVM ovf that is missing?
Any inputs will be of help.
Thanks,
Amudha
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing AgentVM deployment through ESX Agent Manager, then check the AddHost and Exit Maintenance flows described in the report. Determine whether the missing power-on behavior belongs to the AgentVM OVF or to lifecycle handling; done means identifying the cause and documenting or implementing the expected start behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100