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.
DescriptionJitendra Yejare
2019-12-19 15:22:32 UTC
Description:
-------------------
Compute Resource create does not validate the zone name for GCE CR and creates the Compute Resource. If I provide any non-existence zone name while creating the CR, it doesn't validate if the zone is present or not and creates the CR.
How Reproducible:
-------------------
Always
Steps:
-------------------
1. Create a Compute Resource from a hammer with the zone(that doesn't exist in GCE).
Actual Behavior:
-------------------
1. The Compute Resource is created
2. No sign of error or warning for non-existence of zone.
Expected Behavior:
--------------------
1. Either the Compute Resource should not be created or should show a warning and create CR with zone.
Verified!
@ Satellite 6.7 snap 8
Steps:
---------------------
1. Create a Compute Resource from a hammer with the zone(that doesn't exist in GCE).
2. Also for regression if any, check with valid GCE zone.
Observation:
---------------------
1. The Zone field is now being verified before the CR is created.
2. No regression caused by fix, with valid Zone the GCE CR is being 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-2020:1454