-
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 always return changed status #226
Comments
Files identified in the description: If these files are inaccurate, please update the |
Hi @tinsjourney , Thank you for your contribution in making this colleciton even better! Please notice that this collection is supported for Ansible 2.9.10 onwards, and even so, only critical security fixes will be applied on the Ansible 2.9 branch. Thus, this issue should be checked against ansible-base 2.10.x or, preferably, against ansible-core 2.11.x to ensure the problem has not been fixed yet. Thanks in advance! Cheers! |
needs_info |
Hi @russoz, I tried with ansible-core 2.11.3, and I have the same behavior, always return changed.
|
Files identified in the description: If these files are incorrect, please update the |
It looks to me that this issue is an "older copy" of #5313, which was fixed few months ago, and backported to some older branches:
@tinsjourney can you please check again with any of the fixed versions mentioned above? |
Also, another thing to check is whether the account uses SCA (Simple Content Access) or not -- you can easily do that by checking the output of
for an SCA account. In case of SCA, individual subscriptions and pools don't apply, so specified |
!component redhat_subscription |
!component redhat_subscription |
@ptoscano the component has already been set correctly, there's no need to try it again. (That's also why the bot doesn't seem to react.) |
SUMMARY
Since ansible Version 2.9.5 and PR #66478, redhat_subscription status is always changed even is host is already registered with RHN
ISSUE TYPE
COMPONENT NAME
redhat_subscription
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
Red Hat 8.1
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: