Hide Forgot
Created attachment 1150398 [details] Registration with subscription manager is done message Description of problem: Initial-setup : A message "Error during registration" when system is registered successfully but auto-attach failed due to installed products not being covered by a single service-level Version-Release number of selected component (if applicable): [root@dhcp35-180 ~]# subscription-manager version server type: Red Hat Subscription Management subscription management server: 2.0.10-1 subscription management rules: 5.20 subscription-manager: 1.17.5-1.git.0.9f499d8.el7 python-rhsm: 1.17.1-1.git.1.323232f.el7 How reproducible: Steps to Reproduce: Have multiple installed product certs that are not covered by a single service-level 1.[root@dhcp35-180 ~]# systemctl enable initial-setup-graphical.service Created symlink from /etc/systemd/system/graphical.target.wants/initial-setup-graphical.service to /usr/lib/systemd/system/initial-setup-graphical.service. 2.[root@dhcp35-180 ~]# reboot 3.Click on "register to rhsm" on inital-setup panel 4. Enter the server details --> next ---> enter the credentials ---> do not select "manually attach subscriptions after registering" checkbox---> Click on register --->A message saying "No service level will cover all the installed products should be displayed", now click on done button Actual results: message under RHSM spoke says "Error during registration" , though system was registered successfully Expected results: Message should be something similar to "System is registered successfully but none of the installed products are covered" Additional info:
Created attachment 1150399 [details] Error on RHSM spoke
Created attachment 1350354 [details] See the message "System is successfully registered" Verified! [root@dhcp35-121 ~]# subscription-manager version server type: Red Hat Subscription Management subscription management server: 2.2.0-1 subscription management rules: 5.26 subscription-manager: 1.20.5-1.el7
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0681