Actions
Bug #8779
closedVLAN_ID - Subnet Foreman 1.7.1
Difficulty:
trivial
Triaged:
Pull request:
Description
Hello everyone,
I found an issue in Foreman 1.7.1 with the Subnet-Section. After defining a Subnet as following:
Name: test Network address: 192.168.178.0 Network mask: 255.255.255.0 Gateway address: 192.168.178.1 Primary DNS server: 192.168.178.2 Secondary DNS server: 192.168.178.3 IPAM: None VLAN ID: 101 Boot mode: Static
and assign it to a hostgroup the following happens when I add a node to this hostgroup (yaml ouput of the node):
foreman_subnets: - network: 192.168.178.0 mask: 255.255.255.0 name: test gateway: 192.168.178.1 dns_primary: 192.168.178.2 dns_secondary: 192.168.178.3 boot_mode: Static ipam: None
So every value I defined will assigned to the node but at least not the VLAN_ID. Why is this happening? Because this value is optional?
Greetings
Marcel
Updated by Dominic Cleal about 10 years ago
- Related to Feature #2089: Expose network configuration via ENC added
Updated by Dominic Cleal about 10 years ago
- Category set to Network
- Difficulty set to trivial
Needs adding to enc_attributes in app/models/subnet.rb.
Updated by Marek Hulán almost 10 years ago
- Status changed from New to Assigned
- Assignee set to Marek Hulán
Note that as a "workaround" you can read vlanid from interfaces assigned to this subnet if they don't override the value (vlanid is inherited from subnet).
Updated by The Foreman Bot almost 10 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2199 added
- Pull request deleted (
)
Updated by Marek Hulán almost 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset a899d97175c683bb648e3cbd34d0aebcae1252cf.
Updated by Dominic Cleal almost 10 years ago
- Translation missing: en.field_release set to 36
Actions