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.
Version-Release number of selected component (if applicable): 6.3.2
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.
verified:
@satellite 6.5.0 snap 1
steps:
1. hammer defaults add --param-name organization_id --param-value <org_id>
2. hammer subnet create --name test --network 192.168.22.0 --mask 255.255.255.0
3. hammer subnet info --name test
observation:
Default organization is set automatically to the subnet when the subnet is created.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2019:1222
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. Version-Release number of selected component (if applicable): 6.3.2 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.