Bug 1776936 - Non-unique Machine names in cluster-api-actuator-pkg E2E tests
Summary: Non-unique Machine names in cluster-api-actuator-pkg E2E tests
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.2.z
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.2.z
Assignee: Brad Ison
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On: 1776879
Blocks: 1776885
TreeView+ depends on / blocked
 
Reported: 2019-11-26 15:37 UTC by Brad Ison
Modified: 2020-01-07 17:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1776879
Environment:
Last Closed: 2020-01-07 17:55:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-api-actuator-pkg pull 126 0 None None None 2019-12-13 15:16:44 UTC
Red Hat Product Errata RHBA-2020:0014 0 None None None 2020-01-07 17:55:25 UTC

Description Brad Ison 2019-11-26 15:37:14 UTC 
+++ This bug was initially created as a clone of Bug #1776879 +++

The E2E test suite shared by OpenShift machine-api components in the cluster-api-actuator-pkg repo do not use unique names for some Machine resources. This leads to collisions when running tests in parallel.

--- Additional comment from Brad Ison on 2019-11-26 15:22:50 UTC ---

I'm not really sure what status to put this in. The PR is merged, and I've verified it's working. This repo is only an E2E suite. It's not in OpenShift directly. There's not really anything further to QA.
Comment 3 errata-xmlrpc 2020-01-07 17:55:11 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:0014
Note You need to log in before you can comment on or make changes to this bug.