Bug 1465643
| Summary: | foreman-discovery-image fails to setup static networking when cpu count is greater than 1 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Reartes Guillermo <greartes> | ||||||||
| Component: | Discovery Image | Assignee: | Lukas Zapletal <lzap> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | |||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 6.2.10 | CC: | akarimi, asamad, bbuckingham, ehelms, hmore, jcallaha, lzap, nshaik | ||||||||
| Target Milestone: | Unspecified | Keywords: | Triaged | ||||||||
| Target Release: | Unused | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| URL: | http://projects.theforeman.org/issues/20128 | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | foreman-discovery-image-3.4.2-1 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2018-02-21 16:54:17 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: | |||||||||||
| Bug Depends On: | 1426067 | ||||||||||
| Bug Blocks: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 1292452 [details]
1 cpu, it works
Created attachment 1292453 [details]
2 cpus. failure to setup networking
Additional Info: On another different kvm/libvirt enviorment, i found an older fdi iso. So i re tested on that new environment: * foreman-discovery-image-3.1.1-16 1 cpu ... OK 2 cpu ... OK * foreman-discovery-image-3.1.1-22 1 cpu ... OK 2 cpu ... FAILURE It looks like foreman-discovery-image-3.1.1-22 has the issue. So, as a workaround use an older fdi iso. Hello, upstream version FDI 3.4 should not have this problem: http://downloads.theforeman.org/discovery/releases/3.4/ You can use it with Satellite 6.2+ until we backport the fix or rebase the FDI there. More info about this issue in: http://projects.theforeman.org/issues/20128 For the record, CPU count is causing NetworkManager setup script to start quicker than normal. TRIAGE NOTES: We need to either backport a fix or schedule FDI rebase for the next z-stream which I'd prefer. It is important bug to backport, let's keep this one for 6.3 and I am requesting FDI rebase in z-stream in a separate bug: https://bugzilla.redhat.com/show_bug.cgi?id=1426067 This missed the 3.4.1 release by git tagging error and we need to rebase to 3.4.2 to have that fix. GA only, not blocker. The missing commit is: commit 78fb1ab72643e95ee39806635a227d5d51a6d3d7 I messed up downstream tagging, so bumped to minor version which includes it. Before building FDI make sure this dependency is included in build roots: https://bugzilla.redhat.com/show_bug.cgi?id=1508455 Googlers or Satellite 6.2.x customers: Please use this build to workaround the issue: http://people.redhat.com/~lzapleta/scratch/fdi/foreman-discovery-image-3.4.4-1.el7sat.noarch.rpm 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
|
Created attachment 1292451 [details] failure, with 2 or more cpus Description of problem: It is not possible to configure static network when the guest has more than 1 cpu. Noticed on vmware (vcenter55) and later i reproduced it with kvm/libvirt. I don't have an older fdi to test at this time. Version-Release number of selected component (if applicable): * foreman-discovery-image-3.1.1-22 * Sat 6.2.9 (and other 6.2.10 in the vcenter case) How reproducible: always Steps to Reproduce: 1. create a guest with 2 or more cpus 2. boot the foreman-discovery-image 3. select the nic 4. choose manual 5. set network parameters (for example 192.168.205.99/24, 192.168.205.1, 192.168.205.15) 6. the foreman-discovery-image gets broken, since it was unable to bringup the network. (one can switch to vt3 and issue an nmcli con mod and nmcli con up and it will work). Actual results: * unable to provision via PXE-Less foreman-discovery-image with Sat6.2 Expected results: * PXE-Less foreman-discovery-image should work with any valid cpu count. Thanks in advance.