-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
redhat_subscription module broken with RHEL 9 #4741
Comments
This comment was marked as outdated.
This comment was marked as outdated.
Files identified in the description: If these files are incorrect, please update the |
subscription-manager remove --all
subscription-manager unregister |
subscription-manager developer here o/ Thanks for the ticket, I just opened #4809 for fixing this. |
Will this change to the module also cover unregistering the host altogether? I see that unsubscribe is replaced with remove according to the linked PR The description of the state field for the module says:
As you can see state:absent should also unregister the system altogether, not just remove a subscription or set of subscriptions. From the subscription-manager docs:
Remove:
|
The
I'm not sure why you are looking at the documentation of
Is this the case? If so, that would be a new issue to file, and something already broken before this issue (with my PR). |
Summary
When I try to ensure that a system does not have a subscription active, I get a failed task for a RHEL 9 system.
Example:
fails for a RHEL9 host.
Issue Type
Bug Report
Component Name
redhat_subscription
Ansible Version
$ ansible --version
Community.general Version
Configuration
$ ansible-config dump --only-changed
OS / Environment
RHEL 9
Steps to Reproduce
for a RHEL9 host, the task fails:
Expected Results
I expected this to unsubscribe the host.
Actual Results
This appears to happen because in RHEL 9,
subscription-manager unsubscribe
is not a valid command sequence. There is notunsubscribe
sub-command (but there is, in RHEL 8).Code of Conduct
The text was updated successfully, but these errors were encountered: