Bug 1827593 - [vSphere] Check if tag is already attached to vm
Summary: [vSphere] Check if tag is already attached to vm
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
low
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 09:44 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 563 0 None closed Bug 1827593: Check if tag is already attached to vm 2020-06-23 10:22:36 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 09:44:03 UTC
Description of problem:

Attaching a tag to VM takes about 20-30 seconds and waiting for it becomes a bit annoying. We should check if the tag was already attached to VM and skip attaching it for multiple times.

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-04 02:44:39 UTC
Please provide info on steps to reproduce

Comment 4 Milind Yadav 2020-05-05 10:30:01 UTC
looks like reducing time taken to reconcile machine , more of a non-functional change , which we cannot validate .

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.