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.
DescriptionDimitar Yordanov
2011-03-28 08:26:45 UTC
Description of problem:
Firstboot - "Set up software updates" could get confused.
Version-Release number of selected component (if applicable):
RHEL 6.1
firstboot-1.110.10-1.el6.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. Install RHEL 6.1 + Desktop + VNC + firstboot
2. Connect to the system via VNC and SSH (two connections)
3. Register the system to errata.stage using the SSH connection.
4. In your VNC connection, open terminal and execute "firstboot --debug".
5. VNC: As your system is registered already you will not be asked to register again to RHN.
6. VNC: Get to the Create User Screen.
7. SSH: rm -f /etc/sysconfig/rhn/systemid
8. VNC: Press "BACK" button untill get to the first screen of Firstboot.
9. VNC: Press Forward Button.
10.VNC: You are offered to register your system to RHN
11.VNC: Press Forward button.
Actual results:
You get to Created User Screen
Expected results:
Continue with the registration to RHN
Additional info:
The work flow described in the initial comment is very unorthodox and in
no way resembles a typical use of firstboot and RHN registration.
I'm closing this with wontfix.
Description of problem: Firstboot - "Set up software updates" could get confused. Version-Release number of selected component (if applicable): RHEL 6.1 firstboot-1.110.10-1.el6.x86_64 How reproducible: Always. Steps to Reproduce: 1. Install RHEL 6.1 + Desktop + VNC + firstboot 2. Connect to the system via VNC and SSH (two connections) 3. Register the system to errata.stage using the SSH connection. 4. In your VNC connection, open terminal and execute "firstboot --debug". 5. VNC: As your system is registered already you will not be asked to register again to RHN. 6. VNC: Get to the Create User Screen. 7. SSH: rm -f /etc/sysconfig/rhn/systemid 8. VNC: Press "BACK" button untill get to the first screen of Firstboot. 9. VNC: Press Forward Button. 10.VNC: You are offered to register your system to RHN 11.VNC: Press Forward button. Actual results: You get to Created User Screen Expected results: Continue with the registration to RHN Additional info: