-
Notifications
You must be signed in to change notification settings - Fork 897
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
Disconnect inventory on targeted refresh #16718
Conversation
while not directly fixing it, this is required to fix: https://bugzilla.redhat.com/show_bug.cgi?id=1511445 |
07459d0
to
7f66cf9
Compare
When doing a targeted refresh the condition to disconnect the target from the ems was not granular enough. For example in some cases when refreshing a template the 'folder' hashes were not not empty while the 'template' hashes were, still the template was not disconnected from the ems in that case. The new condition is more accurate and should mitigate this kind of scenarios. This is part of prs that fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1511445
7f66cf9
to
5eb95a4
Compare
Checked commit borod108@5eb95a4 with ruby 2.3.3, rubocop 0.47.1, haml-lint 0.20.0, and yamllint 1.10.0 |
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.
👍 LGTM
Fixes an issue found by ManageIQ#16718 where relationships are deleted even though disconnect is false.
Fixes an issue found by ManageIQ#16718 where relationships are deleted even though disconnect is false.
Fixes an issue found by ManageIQ#16718 where relationships are deleted even though disconnect is false.
Fixes an issue found by ManageIQ#16718 where relationships are deleted even though disconnect is false.
Disconnect inventory on targeted refresh (cherry picked from commit 14d1aa3)
Gaprindashvili backport details:
|
Fixes an issue found by ManageIQ#16718 where relationships are deleted even though disconnect is false.
When doing a targeted refresh the condition to disconnect the target
from the ems was not granular enough.
For example in some cases when refreshing a template the 'folder' hashes
were not not empty while the 'template' hashes were, still the template
was not disconnected from the ems in that case.
The new condition is more accurate and should mitigate this kind of
scenarios.
The specs for this PR are here: ManageIQ/manageiq-providers-ovirt#184