Bug 1455455
| Summary: | [RFE] PXE less provisioning - Add delay to discovery image boot for slow DHCP networks | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Roman Bobek <rbobek> |
| Component: | Discovery Image | Assignee: | Lukas Zapletal <lzap> |
| Status: | CLOSED ERRATA | QA Contact: | Lukáš Hellebrandt <lhellebr> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | Unspecified | CC: | bbuckingham, inecas, lhellebr, lzap, rbobek, sthirugn |
| Target Milestone: | Unspecified | Keywords: | FutureFeature, Reopened, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://projects.theforeman.org/issues/19984 | ||
| Whiteboard: | |||
| Fixed In Version: | foreman-discovery-image-3.4.1-1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-02-21 12:39:11 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Roman Bobek
2017-05-25 08:57:04 UTC
Lukas, thoughts on this one? Roman I can indeed implement the fix but I cannot reproduce, can you send me full logs from the discovered node when you encounter this kind of error? The script is called discovery-debug, send me output of this to the BZ. I am asking because I don't understand, in PXE-less mode there is plenty of time if you go screen by screen. Do you mean semi-automatic or full-automatic (unattended) mode when you enter all the details on the kernel command line? What was your setting then? I need to know before I can put the delay. (In reply to Lukas Zapletal from comment #3) > I am asking because I don't understand, in PXE-less mode there is plenty of > time if you go screen by screen. Do you mean semi-automatic or > full-automatic (unattended) mode when you enter all the details on the > kernel command line? What was your setting then? I need to know before I can > put the delay. I have asked for the logs, but the customer unfortunately does not have the HW to reproduce this issue. Have asked him for more details about booting mode and settings. Waiting for the reply. The error message from the attached image is triggered by this statement:
nmcli connection down primary
this happens when the primary connection is brought down and it was not yet brought up. So the error is expected in this case. It's just a cosmetic issue and it has no effect.
I filed this upstream: http://projects.theforeman.org/issues/19950
We will eventually fix this, no backport or QA needed for this one, closing.
Sorry, this was a different issue. Re-opening: http://projects.theforeman.org/issues/19984 Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19984 has been resolved. Verified with foreman-discovery-image-3.4.1-3.iso. There is no clear reproducer for the issue so I did the following: 1) Used FDI to discover a host which worked correctly 2) Verified the change was actually present on the ISO in /usr/lib64/ruby/vendor_ruby/discovery/menu.rb 3) The error "nmcli connection down" is not present in journalctl Note: waiting for a magic constant "10 seconds" is fishy, it would be better to wait in a loop 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 |