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
syspatch: Check for apply=no condition #65350
Conversation
The test
|
Thank you @Akasurde , this does resolve the issue in #65216 A different issue is apparent now, though. On the remote host I reverted one patch:
Then when I ran
I reverted the patch on the remote host again. Then when I ran
I'll suggest a way to resolve this, tho I'm unfamiliar with how @precurse intends it to work. |
410b980
to
22045c3
Compare
Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
22045c3
to
796619c
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.
Thank you for taking care of this @Akasurde
These each succeeded as expected with OpenBSD 6.6 and Python 3.7 at this PR's HEAD commit:
- apply=no
- apply=yes
- revert=one
- revert=all
Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
SUMMARY
Signed-off-by: Abhijeet Kasurde akasurde@redhat.com
ISSUE TYPE
COMPONENT NAME
lib/ansible/modules/system/syspatch.py