-
Notifications
You must be signed in to change notification settings - Fork 93
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
roles: hosted_engine_setup: restore - remove host also based on name #567
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
OK for me, but perhaps better warn the user if there are any inconsistencies - at least if we removed more than one host (e.g. one matching uuid and one matching name). |
Where do you think we need to warn the user?
|
That's a good question. I wrote a bit about it in the bug. Ideally IMO we should prompt and ask the user what to do, e.g. similarly to what we do when 'Add host' fails. I realize this is a large change, so not requiring it right now. I also see it's not easy to emit warnings, ansible/ansible#67260, but perhaps we can still do something, not sure. |
In restore, remove the host from DB based on the name in addition to the UUID. Using multiple hosts with the same name is not allowed anyway. Bug-Url: https://bugzilla.redhat.com/2003515 Signed-off-by: Asaf Rachmani <arachman@redhat.com>
Signed-off-by: Asaf Rachmani <arachman@redhat.com>
Signed-off-by: Asaf Rachmani <arachman@redhat.com>
Verified locally:
|
In restore, remove the host from DB based on the name
in addition to the UUID.
Using multiple hosts with the same name is not allowed anyway.
Bug-Url: https://bugzilla.redhat.com/2003515
Signed-off-by: Asaf Rachmani arachman@redhat.com