-
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
Consumed subscriptions, still listed as available are consumed again #1228
Comments
Files identified in the description: If these files are inaccurate, please update the |
Could you provide one or two SKUs which appears like that? I am a bit curious about this. |
Files identified in the description: If these files are incorrect, please update the |
It looks to me that this issue may be an "older copy" of #5313, which was fixed few months ago, and backported to some older branches:
@tomaciazek can you please check again with any of the fixed versions mentioned above? |
Sorry, I no longer have access to that environment where RHEL subscriptions were used, or any other environment that could allow me to test that. |
Ouch, that's unfortunate... thanks anyway :) @felixfontein: what should we do in this case? |
@ptoscano I guess we can close it then. If nobody complains, I'll do that later today. |
SUMMARY
For some subscriptions (instance-based, I believe)
subscription-manager
will still report them as available forsubscription-manager list --available
, but with 'suggested' entitlements to consume equal to 0. This breaks the behavior of this module when either thepool
option is provided or thepool_ids
option but without the quantities specified.NB: To make the module work correctly with the
pool_ids
option, the quantity must be a text value, otherwise module will re-subscribe (fortunately not consuming more entitlements) and reportchanged: true
. That, I believe, is another bug.ISSUE TYPE
COMPONENT NAME
redhat_subscription
ANSIBLE VERSION
CONFIGURATION
ansible-config dump --only-changed
returns no outputOS / ENVIRONMENT
Tested on RHEL 8.2 and RHEL 7.9
STEPS TO REPRODUCE
AND
EXPECTED RESULTS
Invoking twice, should show change only the first time. The second time, no changes should be reported and
no new entitlements consumed
ACTUAL RESULTS
Invoking the module the second time shows changes and consumes additional entitlements.
The text was updated successfully, but these errors were encountered: