Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.