I am having the same (or at least very similar) issue as well. After
upgrading to 1.13.0 I can't create an interface that is seen as bonded to
my snippets. 1.13.1 didn't fix it either.
When adding a bonded interface to a host in foreman, the only way I see the
options to enter attached interfaces or bonding options is to select "Bond"
and add the interface (without being able to specify attached interfaces or
bonding options because those are missing), then when I edit the bonded
interface again, those options are available to me. The interface saves
after I make my edits, but the attached interfaces information does not
persist.
Also, @host.bond_interfaces remains empty because the Bond interface
apparently isn't seen as a bond?
On the host I am working with, I have the provisioning interface, eth0 with
an IP address and MAC assigned to it and marked managed and provisioning.
I have a bonded interface, bond0, which uses eth4/eth7. The bond0 interface
is marked primary and given an IP, but not marked as managed.
eth4 and eth7 are not marked managed, primary or provisioning.
Here's the @host.interfaces array:
@host.interfaces.to_a = [#<Nic::Managed id: 12226, mac: "1c:1c:1c:1c:1c:1c",
ip: "1.2.3.31", type: "Nic::Managed", name: "testbox.admin.domain.com",
host_id: 18415, subnet_id: 533, domain_id: 10, attrs: {}, created_at:
"2016-10-31 19:22:44", updated_at: "2016-10-31 19:22:44", provider: nil,
username: nil, password: nil, virtual: false, link: true, identifier: "", tag:
"", attached_to: "", managed: true, mode: "balance-rr", attached_devices: "",
bond_options: "", primary: false, provision: true, compute_attributes: {}, ip6:
"", subnet6_id: nil>, #<Nic::Bond id: 12229, mac: nil, ip: "1.2.4.31", type:
"Nic::Bond", name: "testbox.domain.com", host_id: 18415, subnet_id: 534,
domain_id: 1, attrs: {}, created_at: "2016-10-31 19:22:44", updated_at:
"2016-10-31 19:36:40", provider: nil, username: nil, password: nil, virtual:
true, link: true, identifier: "bond0", tag: "", attached_to: "", managed:
false, mode: "balance-rr", attached_devices: "", bond_options: "mode=1
miimon=100 downdelay=200 updelay=200 use_ca...", primary: true, provision:
false, compute_attributes: {}, ip6: "", subnet6_id: nil>, #<Nic::Managed id:
12227, mac: nil, ip: "", type: "Nic::Managed", name: "", host_id: 18415,
subnet_id: nil, domain_id: nil, attrs: {}, created_at: "2016-10-31 19:22:44",
updated_at: "2016-10-31 19:22:44", provider: nil, username: nil, password: nil,
virtual: false, link: true, identifier: "eth4", tag: "", attached_to: "",
managed: false, mode: "balance-rr", attached_devices: "", bond_options: "",
primary: false, provision: false, compute_attributes: {}, ip6: "", subnet6_id:
nil>, #<Nic::Managed id: 12228, mac: nil, ip: "", type: "Nic::Managed", name:
"", host_id: 18415, subnet_id: nil, domain_id: nil, attrs: {}, created_at:
"2016-10-31 19:22:44", updated_at: "2016-10-31 19:22:44", provider: nil,
username: nil, password: nil, virtual: false, link: true, identifier: "eth7",
tag: "", attached_to: "", managed: false, mode: "balance-rr", attached_devices:
"", bond_options: "", primary: false, provision: false, compute_attributes: {},
ip6: "", subnet6_id: nil>]
Is there at least a workaround here?
Bill
Later,
> Lukas #lzap Zapletal
>
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
