community.general
community.general copied to clipboard
Update zypper.py
add more checks for t-u
SUMMARY
Adds a few more files to check for to see if the target is using transactional updates. This is especially relevant for newly provisioned hosts that lack the file in /var/lib/misc.
ISSUE TYPE
- Bugfix Pull Request
COMPONENT NAME
zypper.py
ADDITIONAL INFORMATION
Provision a new MicroOS machine. Try to use the zypper module before any updates. It will fail. Add these checkes, and it will know to use t-u.
cc @AnderEnder @alxgu @andytom @commel @dcermak @evrardjp @lrupp @sealor @toabctl click here for bot help
The test ansible-test sanity --test pep8
[explain] failed with 1 error:
plugins/modules/packaging/os/zypper.py:515:12: E126: continuation line over-indented for hanging indent
The test ansible-test sanity --test pep8
[explain] failed with 1 error:
plugins/modules/packaging/os/zypper.py:515:12: E126: continuation line over-indented for hanging indent
The test ansible-test sanity --test pep8
[explain] failed with 1 error:
plugins/modules/packaging/os/zypper.py:515:12: E126: continuation line over-indented for hanging indent
The test ansible-test sanity --test pep8
[explain] failed with 1 error:
plugins/modules/packaging/os/zypper.py:515:12: E126: continuation line over-indented for hanging indent
Thanks for your contribution! Could you please add a changelog fragment? Thanks.
I'll get to this shortly. :)
Docs Build 📝
This PR is closed and any previously published docsite has been unpublished.
Hi @spacemule just a friendly reminder: don't forget to add the changelog fragment!
@spacemule ping
needs_info
@spacemule This pullrequest is waiting for your response. Please respond or the pullrequest will be closed.
Please note that in #5461 the collection repository was restructured to remove the directory tree in plugins/modules/, and the corresponding tree in tests/unit/plugins/modules/. Your PR modifies files in this directory structure, and unfortunately now has some conflicts, potentially because of this. Please rebase with the current main
branch to remove the conflicts.
@spacemule You have not responded to information requests in this pullrequest so we will assume it no longer affects you. If you are still interested in this, please create a new pullrequest with the requested information.