Hide Forgot
Description of problem: subscription manager register activationkey with special character failed Version-Release number of selected component (if applicable): subscription-manager-1.23.8-4.el8.x86_64 subscription-manager-rhsm-certificates-1.23.8-4.el8.x86_64 python3-subscription-manager-rhsm-1.23.8-4.el8.x86_64 subscription-manager-cockpit-1.23.8-4.el8.noarch dnf-plugin-subscription-manager-1.23.8-4.el8.x86_64 satellite6.4 katello-server-ca-1.0-1.noarch katello-3.7.0-8.el7sat.noarch candlepin-2.4.8-1.el7.noarch How reproducible: always Steps to Reproduce: 1.Create a activationkey named ",.;?" on satellite6.4 Please reference picture activationkey.png 2.Register satellite server with this activationkey # subscription-manager register --org=Default_Organization --activationkey=',.;?' HTTP error (404 - Not Found): Couldn't find activation key '' 3. Register satellite server with cockpit Error: HTTP error (404 - Not Found): Couldn't find activation key '' Please reference picture cockpit_activationkey.png 4. Used other special characters, it work well. # subscription-manager register --org=Default_Organization --activationkey='!@#$%^&*()_+-={}{}[<.>' The system has been registered with ID: 5978380b-9ba8-40aa-9d66-4f2641cfa403 The registered system name is: dell-r730-001-guest14.dsal.lab.eng.rdu2.redhat.com Installed Product Current Status: Product Name: Red Hat Enterprise Linux for x86_64 High Touch Beta Status: Subscribed Actual results: As step 3 Expected results: As satellite server support special character creation, register to satellite server also should support, even though we do not use this characters usually. If we think these characters are not useful, maybe satellite server need to add validation for creating activate key using these special characters. Additional info:
Created attachment 1512349 [details] activationkey.png
Created attachment 1512350 [details] cockpit_activationkey.png
Hello Jenny, I have tried in Stage and Satellite 6.5. Stage: Stage can not support creating activate key using special characters. It would display warning message "Name may only contain letters, numbers, underscore, or hyphen ". Satellite6.5: Satellite6.5 has the same issue with satellite6.4. So I think it maybe a Satellite candlepin issue.
Can you provide candlepin logs?
Hello Kevin, Which candlepin log do you need? rhel register stage candlepin log or rhel regiter satellite candlepin log? And how to catch these logs? Thanks.
> Which candlepin log do you need? rhel register stage candlepin log or rhel regiter satellite candlepin log? We would want to see the satellite candlepin log. > And how to catch these logs? On a Satellite server, you can grab the log from /var/log/candlepin/candlepin.log.
Attached logs: 1.Create activation key using ",.;?" on satellite6.4 log: Create_activationkey_using_specail_characters.log 2.Register satellite server with this activationkey by subscription manager # subscription-manager register --org=Default_Organization --activationkey=',.;?' register_satellite_server_with_specailcharacters_by_subscriptionmanager.log 3. Register satellite server with cockpit using activationkey=',.;?' register_satelliteserver_using_specailcharacters_by_cockpit.log 5.Create activation key using "!@#$%^&*()_+-={}{}[<.>" on satellite6.4 log: create_activationkey_by!@#$%^&*()_+-={}{}[<.>.log 6. Register satellite server with activationkey='!@#$%^&*()_+-={}{}[<.>' by subscription manager # subscription-manager register --org=Default_Organization --activationkey='!@#$%^&*()_+-={}{}[<.>' register_satelliteserver_!@#$%^&*()_+-={}{}[<.>_by_subscriptionmanager.log
Created attachment 1519621 [details] Create_activationkey_using_specail_characters.log
Created attachment 1519622 [details] register_satellite_server_with_specailcharacters_by_subscriptionmanager.log
Created attachment 1519623 [details] register_satelliteserver_using_specailcharacters_by_cockpit.log
Created attachment 1519624 [details] create_activationkey_by!@#$%^&*()_+-={}{}[<.>.log
Created attachment 1519625 [details] register_satelliteserver_!@#$%^&*()_+-={}{}[<.>_by_subscriptionmanager.log
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.