Update proper destroy status when SSVM is destroyed.#5908
Conversation
|
@blueorangutan package |
|
@sureshanaparti a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
DaanHoogland
left a comment
There was a problem hiding this comment.
clgtm. So we basically failed to delete what was no longer there in the first place? strange.
that is addressed as the fix there, but it should also return true when host entry doesn't exists. |
yes, of course. fix is good afaics |
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 2366 |
|
@blueorangutan test |
|
@sureshanaparti a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-3106)
|

Description
This PR fixes reporting of the destroy status when SSVM is destroyed.
Issue due to changes here:
1aef5cb#diff-d8fdd320d08cc4eff5dfe391d01c910c660e08ced5afcb2915c78da35f23c453R988-R996
Fixes #5895
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?