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.
Bug 1259801 - Network spoke should always show up in Initial Setup GUI
Summary: Network spoke should always show up in Initial Setup GUI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.2
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Martin Kolman
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-03 14:32 UTC by Martin Kolman
Modified: 2015-11-19 10:04 UTC (History)
3 users (show)

Fixed In Version: anaconda-21.48.22.43-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 10:04:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1265593 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Product Errata RHBA-2015:2284 0 normal SHIPPED_LIVE anaconda bug fix and enhancement update 2015-11-19 09:44:49 UTC

Internal Links: 1265593

Description Martin Kolman 2015-09-03 14:32:52 UTC 
Description of problem:
Now that the Subscription Manager addon is always present in Initial Setup GUI the Network spoke should be be also always present as the Subscription Manager addon needs network connectivity to function.

Without the network spoke the users might not be able to register due to no connectivity any by not having any way to enable it.

Possible scenarios where this might happen:
* DVD installations don't need network connectivity so network is not enabled by default
* network environment changes after the installation has been finished but before Initial Setup has been run
- this also applies to stuff like "OEM installs" where one party installs the system in their environment but another party is expected to finish the configuration via Initial Setup in their own environment

How reproducible:
always

Steps to Reproduce:
1. install RHEL 7.2 from DVD
2. do not enable networking during the installation
3. reboot

Actual results:
Initial Setup shows up, including the Subscription Manager addon, but without the Network Spoke. As networking is not enabled and Network spoke is not present it is not possible to successfully register.

Expected results:
Network spoke is present in Initial setup and can be used to enable networking.
Comment 4 errata-xmlrpc 2015-11-19 10:04:34 UTC 
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://rhn.redhat.com/errata/RHBA-2015-2284.html
Note You need to log in before you can comment on or make changes to this bug.