Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1529769 - Discovery image unable to configure network via DHCP on the first attempt
Summary: Discovery image unable to configure network via DHCP on the first attempt
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Discovery Image
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Perry Gagne
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-29 21:12 UTC by Radovan Drazny
Modified: 2019-09-26 16:10 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 22112 0 None None None 2018-01-02 11:01:53 UTC

Description Radovan Drazny 2017-12-29 21:12:44 UTC 
Description of problem:
Booting a system using the foreman-discovery-image and selecting the "Discover with DHCP" option always leads to a "Unable to bring network via DHCP". Cancelling the following static networking config dialog and again selecting the "Discover with DHCP" works, and IP config is correctly acquired from the DHCP server.

Version-Release number of selected component (if applicable):
foreman-discovery-image-3.4.1-3

How reproducible:
always

Steps to Reproduce:
1. Boot a system with the foreman-discovery-image-3.4.1-3.iso
2. Press the "Discover with DHCP" button
3. The "Unable to bring network via DHCP" dialog is displayed instantly
4. Confirm the error message, and cancel the following dialog requesting a static IP config.The intro dialog for static or DHCP config will be displayed again.
5. Press the "Discover with DHCP" button again. Network device will be successfully configured this time.

Actual results:
DHCP config is not successful on the first time.

Expected results:
DHCP config should work first time.

Additional info:
Following message in the journalctl regarding the DHCP failure:

Dec 29 20:53:01 fdi /usr/bin/discovery-menu[766]: Building net interfaces TUI (bootif=)
Dec 29 20:53:01 fdi /usr/bin/discovery-menu[766]: Device ens3 52:54:00:2f:25:59 link=true booted=false
Dec 29 20:53:03 fdi /usr/bin/discovery-menu[766]: Entering screen_info
Dec 29 20:53:03 fdi /usr/bin/discovery-menu[766]: TUI executing: systemctl stop foreman-proxy
Dec 29 20:53:03 fdi polkitd[817]: Registered Authentication Agent for unix-process:957:6326 (system bus name :1.9 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.
Dec 29 20:53:03 fdi polkitd[817]: Unregistered Authentication Agent for unix-process:957:6326 (system bus name :1.9, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Dec 29 20:53:03 fdi /usr/bin/discovery-menu[766]: TUI executing: nm-configure primary '52:54:00:2f:25:59' ''
Dec 29 20:53:03 fdi NetworkManager[750]: <warn>  [1514580783.1280] keyfile: error loading connection from file /etc/NetworkManager/system-connections/primary: File permissions (100644) were insecure
Dec 29 20:53:03 fdi NetworkManager[750]: <warn>  [1514580783.1287] keyfile: error loading connection from file /etc/NetworkManager/system-connections/primary: File permissions (100644) were insecure
Dec 29 20:53:03 fdi /usr/bin/discovery-menu[766]: TUI executing: nmcli connection up primary
Dec 29 20:53:03 fdi /usr/bin/discovery-menu[766]: TUI executing: nm-online -s -q --timeout=45
Dec 29 21:07:30 fdi /usr/bin/discovery-menu[766]: Entering screen_network
Comment 1 Lukas Zapletal 2018-01-01 10:51:10 UTC 
Thanks, this is known bug in 3.4 series, BLOCKER.
Comment 3 Lukas Zapletal 2018-01-01 11:09:05 UTC 
In this patch, I will fix the root cause of this bug plus:

A) Timeout is maxed at 90s (https://bugzilla.redhat.com/show_bug.cgi?id=1426068)
B) Insecure permissions warning

keyfile: error loading connection from file /etc/NetworkManager/system-connections/primary: File permissions (100644) were insecure
Comment 5 Satellite Program 2018-01-11 15:29:44 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22112 has been resolved.
Comment 8 Satellite Program 2018-02-21 16:54:37 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://access.redhat.com/errata/RHSA-2018:0336
Note You need to log in before you can comment on or make changes to this bug.