Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to determine PowerState of virtual machine rhel93-boys-01"} #1371

Closed
tux1980 opened this issue Dec 12, 2023 · 6 comments
Labels
duplicate This issue or pull request already exists has_pr PR fixes have been made medium_priority Medium priority question Further information is requested

Comments

@tux1980
Copy link

tux1980 commented Dec 12, 2023

I cannot start install any Red HAt Linux System (Marketplace Instance) since I always get the messsage: Failed to determine PowerState of virtual machine rhel93-01"}.

Even the setting is apprantly okay with "started: "true" - that is the only Power Setting I know.
image:
started: "{{ started_the_vm }}"
offer: "{{ offer_rhel }}"
publisher: "{{ publisher_redhat }}"
sku: "{{ linux_vm_sku }}"
version: "{{ version_rhel }}"

SUMMARY

I'm using the newest Ansible collections and executing the playbook via a RED Hat ansible Controller (Version 4.4.8).

ISSUE TYPE
  • Bug Report
COMPONENT NAME

fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to determine PowerState of virtual machine rhel93-boys-01"})-->

ANSIBLE VERSION

COLLECTION VERSION

azure.azcollection 2.0.0

CONFIGURATION

OS / ENVIRONMENT
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS

@Fred-sun
Copy link
Collaborator

@tux1980 Thanks for reporting the problem, could you share your test case? This is a better way to solve your problems, thank you!

@Fred-sun Fred-sun added question Further information is requested medium_priority Medium priority work in In trying to solve, or in working with contributors labels Dec 13, 2023
@Fred-sun
Copy link
Collaborator

Fred-sun commented Jan 5, 2024

@tux1980 I am very sorry for replying to your question so late. I did not encounter the problem you submitted after repeated local tests, and this error is caused by VM status. Previously, there was a PR #1354 dedicated to detecting VM status after VM creation, can you update to the latest branch to check if your problem still exists? Thank you!

@Fred-sun
Copy link
Collaborator

Fred-sun commented Jan 9, 2024

Any feedback?

@Fred-sun Fred-sun added the duplicate This issue or pull request already exists label Jan 16, 2024
@Fred-sun
Copy link
Collaborator

Duplicate of #1365

@Fred-sun Fred-sun marked this as a duplicate of #1365 Jan 16, 2024
@Fred-sun
Copy link
Collaborator

@tux1980 This problem is very beggar, and I cannot copy it for the time being, so I have tested 'powerstate' in PR#1412. You can update to the branch of 1412, will you still encounter this problem? Thank you!

@Fred-sun
Copy link
Collaborator

kindly ping!

@Fred-sun Fred-sun added has_pr PR fixes have been made and removed work in In trying to solve, or in working with contributors labels Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists has_pr PR fixes have been made medium_priority Medium priority question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants