Actions
Bug #24753
closed
Deploying bonds and vlans does not work correctly
Difficulty:
Triaged:
No
Bugzilla link:
Description
When deploying a vlan, the interface name in Foreman gets incorrectly updated - the physical interface gets the same name as a vlan and tag gets attached to vlan identifier. When deploying vlans over bonds, the interfaces do not come up.
Files
Updated by Ondřej Pražák over 5 years ago
- Related to Bug #13092: 802.3ad bonding setup doesn't work correctly added
Updated by Ondřej Pražák over 5 years ago
- Related to Bug #20229: Virtual interface detection from facts not working unless there is an underscore in interface name added
Updated by The Foreman Bot over 5 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/community-templates/pull/505 added
Updated by The Foreman Bot over 5 years ago
- Pull request https://github.com/theforeman/foreman/pull/6033 added
Updated by The Foreman Bot over 5 years ago
- Pull request https://github.com/theforeman/community-templates/pull/515 added
Updated by Marek Hulán over 5 years ago
- Pull request deleted (
https://github.com/theforeman/foreman/pull/6033, https://github.com/theforeman/community-templates/pull/505)
I think this in fact combined two things. The linked BZ talks about bond deployments (also mentioned here), so I'll keep this ticket for tracking the bond deployment only. The other part - detecting vlans and aliases correctly will be addressed by #20229.
Updated by Anonymous over 5 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset community-templates|cf47f839f6bd8e4d1445ef2dd75b47a1d6f9ab39.
Updated by
Actions