Bug #24642
closedhammer subnet create do not honor the default organization and location
Description
Description of problem: hammer subnet create doesn't set the default organization/location. If this is expected behavior this should be documented in a hammer.
How reproducible: Always
- hammer organization list
---|--------|--------|-------------|--------|------------
ID | TITLE | NAME | DESCRIPTION | LABEL | DESCRIPTION
---|--------|--------|-------------|--------|------------
1 | Redhat | Redhat | | Redhat |
---|--------|--------|-------------|--------|------------
Steps to Reproduce:
1. Create Default for an organization
# hammer defaults add --param-name organization_id --param-value 1
# hammer defaults list
----------------|------
PARAMETER | VALUE
----------------|------
organization_id | 1
----------------|------
2. Create Subnet
# hammer subnet create --name test --network 192.168.22.0 --mask 255.255.255.0
Subnet created
3. Get Subnet Info, here we can see that organization is not set for the subnet
# hammer subnet info --name test
Id: 20
Name: test
Network: 192.168.22.0
Mask: 255.255.255.0
VLAN ID:
Priority:
DNS:
Primary DNS:
Secondary DNS:
TFTP:
DHCP:
IPAM: None
Gateway:
From:
To:
Domains:
Actual results: Default organization is not assigned to subnet
Expected results: Default organization should be set automatically to the subnet when the subnet is created.
Note** If the current behavior is expected then it should be added into the hammer documentation.
Updated by Ondřej Pražák almost 7 years ago
- Project changed from Foreman to Hammer CLI
- Subject changed from hammer subnet create do not honor the default organization and location to hammer subnet create do not honor the default organization and location
- Category deleted (
Network)
Updated by Aditi Puntambekar over 6 years ago
- Status changed from New to Closed
- Fixed in Releases hammer-cli-foreman-0.14.1 added
The issue seems to be fixed. Hence, marking it closed.