Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Can not register through firstboot in s390x
Version-Release number of selected component (if applicable):
subscription-manager-firstboot-1.16.8-3.el6.s390x
firstboot-1.110.15-4.el6.s390x
subscription-manager: 1.16.8-3.el6
python-rhsm: 1.16.6-1.el6
How reproducible:
1/1
Steps to Reproduce:
1. Install RHEL-6.8-server-s390x-20160225.0
2. Open firstboot, and register to Satellite-6.1.0-RHEL-7-20160209.1
Actual results:
An Exception window prompts, and there is nothing after clicking the 'debug' button on this window. The registering process bar is rolling all the time. Please see attachment 'stuck_registration_in_firstboot.png'
Expected results:
The registration should succeed in firstboot.
Additional info:
Could you attach the system log (IIRC it should be in /var/log/messages on RHEL 6) from the system ? There could be some more information about the exception.
(In reply to Martin Kolman from comment #3)
> Could you attach the system log (IIRC it should be in /var/log/messages on
> RHEL 6) from the system ? There could be some more information about the
> exception.
I still can not provision a s390x machine all day, so I will update this info immediately.
I tried again, and exception still prompted when registering to satellite via firstboot. Please see attachments 'exception_when_registering_s390_to_satellite.png' and 'messages'.
Verifying version:
subscription-manager: 1.16.8-5.el6
python-rhsm: 1.16.6-1.el6
Verification:
1. Install RHEL-6.8-server-s390x-20160315.0
2. Open firstboot, and register to Satellite-6.1.0-RHEL-7-20160209.1 successfully. Please see attachment 'successfully_register_through_firstboot_in_s390x.png'
Close the bug as WORKSFORME