Unable to join machine with bonded primary interface


#1

Problem:
I am unable to join a machine with bonded primary interface. I get this error when using subscription-manager. HTTP error (422 - Unknown): Validation failed: Attached to can’t be blank
I traced through the logs - I think it is an issue that it can’t tell what the slave ethernet devices are. However I’m unsure if there is a way that I can specify that. Can anyone help me with this?

Expected outcome:
Join successfully using subscription-manager register to Katello

Foreman and Proxy versions:
foreman 1.22

Foreman and Proxy plugin versions:

Other relevant data:
this is from the /var/log/foreman/production.log

2019-07-10T10:29:32 [I|app|a25781d5] Import facts for '<redacted system name>' completed. Added: 220, Updated: 0, Deleted 0 facts
2019-07-10T10:29:32 [I|aud|a25781d5] Nic::Managed (834) update event on mac , <redacted>
2019-07-10T10:29:32 [I|aud|a25781d5] Nic::Managed (834) update event on virtual false, true
2019-07-10T10:29:32 [I|aud|a25781d5] Nic::Managed (834) update event on identifier , bond0
2019-07-10T10:29:32 [W|app|a25781d5] Not queueing Nic::Managed: ["Attached to can't be blank"]
2019-07-10T10:29:32 [W|app|a25781d5] Not queueing Nic::Managed: ["Attached to can't be blank"]
2019-07-10T10:29:32 [W|app|a25781d5] Not queueing Nic::Managed: ["Attached to can't be blank"]


#2

what I am kinda hoping is that there is way to specify the attached-to nics in an /etc/rhsm/facts


#3

Hi, i have the same issue too. At first i thought it is bare metal hosts related, but You comment pointed to bond interface and i can relate.

Do we need to upload some logs for debugging?

Clean install RH7 1.22.0, 3.12.0