Skip to content
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

Add a section in the README.md about requiring and auto-attach activation key. #131

Open
bschonec opened this issue Oct 31, 2022 · 2 comments

Comments

@bschonec
Copy link

In order for this module to work properly, an auto-activate activation key needs to be created and used.

I spent an hour or so using an activation key that didn't have the auto-attach flag set until I realized that the auto-attach needs to be enabled.

I suggest putting in some verbiage in the README.md reminding the users of this fact.

@kallies
Copy link
Contributor

kallies commented Oct 31, 2022

If the module does not work without auto-attach, changes to the module are needed (to be confirmed). Background is the way Red Hat handles (newly) created manifests. Simple Content Access does not require auto-attach and this feature is therefore disabled.

@bschonec
Copy link
Author

Please be aware that subscription-manager does not support auto-attach feature when using an activation key.

[root@example.com security]# subscription-manager register --activationkey=my_activation_key --org=my_org--auto-attach
Error: Activation keys cannot be used with --auto-attach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants