Description of problem: It appears that some white space was recently removed from the interoperability message. I suspect the white space was crushed without realizing the effect in subscription-manager-gui. The extra white space was used to separate the paragraphs making it more pleasant to read. See the attached screenshots. I suggest reverting back the prior version used in subscription-manager-0.96.17-1 Version-Release number of selected component (if applicable): offending version: subscription-manager-0.98.3-1.el5 How reproducible: Steps to Reproduce: 1.subscription-manager unregister 2.touch /etc/sysconfig/rhn/systemid 3.subscription-manager-gui Actual results: WARNING This system has already been registered with RHN using RHN Classic technology. The tool you are using is attempting to re-register using RHN Certificate-Based technology. Red Hat recommends (except in a few cases) that customers only register with RHN once. To learn more about RHN registration and technologies please consult this Knowledge Base Article: https://access.redhat.com/kb/docs/DOC-45563 Expected results: WARNING This system has already been registered with RHN using RHN Classic technology. The tool you are using is attempting to re-register using RHN Certificate-Based technology. Red Hat recommends (except in a few cases) that customers only register with RHN once. To learn more about RHN registration and technologies please consult this Knowledge Base Article: https://access.redhat.com/kb/docs/DOC-45563 Additional info:
Created attachment 534516 [details] Interoperability message in subscription-manager-0.98.3-1.el5
Created attachment 534517 [details] Interoperability message in subscription-manager-0.96.17-1.el6.x86_64
I think you'll agree the old text with extra white space in attachment 534517 [details] is more pleasant than attachment 534516 [details] . Yes I know this affects the CLI too. And yes I think the extra white space in the cli is more pleasant too... ------------------------------------------------------ [root@jsefler-onprem-5server ~]# rpm -q subscription-manager subscription-manager-0.98.3-1.el5 [root@jsefler-onprem-5server ~]# subscription-manager register WARNING This system has already been registered with RHN using RHN Classic technology. The tool you are using is attempting to re-register using RHN Certificate-Based technology. Red Hat recommends (except in a few cases) that customers only register with RHN once. To learn more about RHN registration and technologies please consult this Knowledge Base Article: https://access.redhat.com/kb/docs/DOC-45563 This system is already registered. Use --force to override [root@jsefler-onprem-5server ~]# ------------------------------------------------------ [root@jsefler-onprem-62server ~]# rpm -q subscription-manager subscription-manager-0.96.17-1.git.0.a4f61be.el6.x86_64 [root@jsefler-onprem-62server ~]# subscription-manager register WARNING This system has already been registered with RHN using RHN Classic technology. The tool you are using is attempting to re-register using RHN Certificate-Based technology. Red Hat recommends (except in a few cases) that customers only register with RHN once. To learn more about RHN registration and technologies please consult this Knowledge Base Article: https://access.redhat.com/kb/docs/DOC-45563 This system is already registered. Use --force to override [root@jsefler-onprem-62server ~]# ------------------------------------------------------
e0cb3d9 master 0.98.4+
Created attachment 541480 [details] Interoperability message in subscription-manager-0.98.5-1.el5 (with missing html link) Verifying Version... [root@jsefler-onprem-5server ~]# rpm -q subscription-manager subscription-manager-0.98.5-1.el5 [root@jsefler-onprem-5server ~]# subscription-manager register --username testuser1 --password password --org admin WARNING This system has already been registered with RHN using RHN Classic technology. The tool you are using is attempting to re-register using RHN Certificate-Based technology. Red Hat recommends (except in a few cases) that customers only register with RHN once. To learn more about RHN registration and technologies please consult this Knowledge Base Article: https://access.redhat.com/kb/docs/DOC-45563 The system has been registered with id: 5a13362b-2e2d-48b0-81e5-49955ed9082c [root@jsefler-onprem-5server ~]# ^^^ THE CARRIAGE RETURNS HAVE BEEN RESTORED INTO THE INTEROPERABILITY WARNING Looking at the attached screenshot of the GUI, the carriage returns have returned, but the integrated html linkification to the knowledge base article has not been restored. Is this expected? Will the link return after translation? Moving back to NEW/FailedQA for more info needed.
John, This issue doesn't appear to be a regression. It looks like the linkification only worked in RHEL 6 and not in 5. I'm making this determination based on the git history which indicates that the link never had any mark-up associated with it. Can you confirm the linkification did not work in earlier versions?
Alex, You are correct. This is not a regression from rhel57. I started up a rhel57 box and there is no linkification in the warning message: [root@dell-pe840-01 ~]# rpm -q subscription-manager-gnome subscription-manager-gnome-0.95.5.21-1.el5 In Summary: On rhel57 and rhel58, there is NO linkification of the Knowledgce Base Article url in the warning message. On rhel62, there *is* linkification of the Knowledgce Base Article url in the warning message. Maybe GTK in rhel6 automatically linkifys substrings that appear to be a url and rhel5 does not.
Attempting to undo comment 8 and move to VERIFIED since the original point of this bug was fixed in comment 4 against rhel58.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No description necessary
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. http://rhn.redhat.com/errata/RHBA-2012-0154.html