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

Metal Power Exits on VM Not Existing #353

Open
ColonelPanics opened this issue Mar 27, 2018 · 2 comments
Open

Metal Power Exits on VM Not Existing #353

ColonelPanics opened this issue Mar 27, 2018 · 2 comments
Labels

Comments

@ColonelPanics
Copy link
Contributor

I believe that the fix in #337 should also have addressed VM nodes that don't exist.

A VM that doesn't exist should be treated like an IPMI interface that is not responding.

Example command before renaming a node VM:

[root@controller [adminware] ~]# metal power -g nodes status
node001: Power state: off
node002: Power state: off
node003: Power state: off
node004: Power state: off
node005: Power state: off

Example after renaming node002:

[root@controller [adminware] ~]# metal power -g nodes status
node001: Power state: off
error: Call to virDomainLookupByName failed: Domain not found: no domain with matching name 'node002'. Use --trace to view backtrace
@bobwhitelock
Copy link
Contributor

How much of a priority do you think fixing this soon is? Do you run into this much in practice or only when testing things?

@ColonelPanics
Copy link
Contributor Author

Only running into it with testing, isn't a huge issue. Don't feel a fix is needed for this release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants