Bug 1827603 - vSphere - Unit tests for zone and regions
Summary: vSphere - Unit tests for zone and regions
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.5
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: 4.5.0
Assignee: Alexander Demicev
QA Contact: Milind Yadav
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-24 10:06 UTC by Alexander Demicev
Modified: 2020-07-13 17:31 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:31:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-api-operator pull 569 0 None closed Bug 1827603: vSphere - Unit tests for zone and regions 2020-11-16 14:07:45 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:31:28 UTC

Description Alexander Demicev 2020-04-24 10:06:19 UTC
Description of problem:

We need to add unit tests for zone and regions in vSphere. Regions and zones are not always present on the machine, this depends on vSphere configuration but we can lower risks of an error on our site and make sure we set them properly.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Milind Yadav 2020-05-12 11:12:49 UTC
Dont think QE will need to test , please share your thoughts..

Comment 4 Milind Yadav 2020-05-12 11:53:17 UTC
Thanks Alexander for info on slack . Will move it to VERIFIED

Comment 5 errata-xmlrpc 2020-07-13 17:31:14 UTC
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/RHBA-2020:2409


Note You need to log in before you can comment on or make changes to this bug.