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
ovirt_vm: Check next_run configuration update if exist #47282
Conversation
Hi @machacekondra, thank you for submitting this pull-request! |
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.
shipit
Ryan, could you please merge? This is a customer related bug, so we would really need to get this into Ansible 2.7.1. Thanks! |
Could you add a changelog entry for this? It will be ready to merge once that is added. |
@mwperina @machacekondra Also... today is the last day for merging for the 2.7.1 release. So if you can get it in ASAP, that would be extremely helpful for getting it into 2.7.1 as opposed to 2.7.2. |
020cec6
to
1f65665
Compare
@abadger Thanks for review. I've added the changelog. |
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.
shipit
@@ -0,0 +1,2 @@ | |||
bugfixes: | |||
- ovirt_vm: Check next_run configuration update if exist (https://github.com/ansible/ansible/pull/47282/). |
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.
The problem in the changelog is the ": ". In yaml, that has a special meaning, the separator between a dictionary's key and value elements.
The easiest fix is to change the ": " into a " - ".
The test
|
1f65665
to
c6fae57
Compare
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.
shipit
There are now conflicts in this PR (after merging other ovirt PRs) If you have a chance to resolve those that would be great. I'll take a look after I run through the backport queue at whether you've had a chance and whether it would be straightforward for me to resolve the conflict myself. |
Okay, I'm looking at whether I can resolve the conflicts now. |
@abadger conflicts resolved |
This PR fixes the update check method so it now check also the next_run configuration of the virtual machine if it exists. So if previously the VM was updated with new parameters, and then reset back, the module didn't set the parameters to be set back in next_run. This PR fixes it so the next run configuration is set back with proper parameters. Signed-off-by: Ondra Machacek <omachace@redhat.com> Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1639894 Signed-off-by: Ondra Machacek <omachace@redhat.com>
ef9f7c1
to
9442889
Compare
@machacekondra Thanks. github was still telling me there's conflicts, likely because of the merge (as opposed to rebase). But I can see how to fix that thanks to your work. I've pushed up a resolution to that. Please review to be sure I haven't done anything wrong. |
@abadger Change looks OK, thanks you! |
Merged for the 2.7.1 release. |
Backport of #47280
This PR fixes the update check method so it now check also the next_run
configuration of the virtual machine if it exists.
So if previously the VM was updated with new parameters, and then reset
back, the module didn't set the parameters to be set back in next_run.
This PR fixes it so the next run configuration is set back with proper
parameters.
Signed-off-by: Ondra Machacek omachace@redhat.com
Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1639894
Signed-off-by: Ondra Machacek omachace@redhat.com
SUMMARY
ISSUE TYPE
COMPONENT NAME
ANSIBLE VERSION
ADDITIONAL INFORMATION