Bug 1862146 - [UPI][BAREMETAL] RHCOS 4.5 Deployment failed due to bond not configured
Summary: [UPI][BAREMETAL] RHCOS 4.5 Deployment failed due to bond not configured
Keywords:
Status: CLOSED DUPLICATE of bug 1857532
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RHCOS
Version: 4.5
Hardware: x86_64
OS: Other
high
high
Target Milestone: ---
: 4.6.0
Assignee: Dusty Mabe
QA Contact: Michael Nguyen
URL:
Whiteboard:
Depends On:
Blocks: 1186913
TreeView+ depends on / blocked
 
Reported: 2020-07-30 14:40 UTC by Gianluca Villani
Modified: 2024-03-25 16:14 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-19 20:40:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 1 Micah Abbott 2020-07-30 19:05:50 UTC
This may be a limitation of passing the `vlan=` parameter from dracut into the real root during install in RHCOS.  We have seen similar reports in BZ#1857532, BZ#1859897, and BZ#1860060

RHCOS 4.6 will be better support for complex network configurations, but we will investigate this as is.

Setting as high priority and targeting 4.6

Comment 2 Dusty Mabe 2020-07-30 19:37:37 UTC
This bug has not been selected for work in the current sprint.

Comment 3 Dusty Mabe 2020-08-12 20:36:10 UTC
Hey gvillani,

There are several bugs related to VLANs and I think I'm going to try to get them all moved into the same bug (assuming they are the same root cause). Do you mind looking at https://bugzilla.redhat.com/show_bug.cgi?id=1857532#c4 and help give us more information if you can (i.e. test against 4.6 if you have access to latest builds).

Dusty

Comment 4 Gianluca Villani 2020-08-13 08:09:49 UTC
Hi Dusty

I am not sure if the customer wants to test it against 4.6 at the moment, because this environment is a PoC for upgrading from 3.x ---> 4.x.
I will ask to our consultants if it is possible do it afterwards.

Many thanks

Gianluca

Comment 5 Dusty Mabe 2020-08-19 20:40:40 UTC
I'm going to close this and a few other bugs as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1857532. Unless more information comes to light, I think that is the case.

*** This bug has been marked as a duplicate of bug 1857532 ***


Note You need to log in before you can comment on or make changes to this bug.