Bug 1829409

Summary:	Update vsphere machine api from alpha to beta
Product:	OpenShift Container Platform	Reporter:	Alexander Demicev <ademicev>
Component:	Installer	Assignee:	Alexander Demicev <ademicev>
Installer sub component:	openshift-installer	QA Contact:	jima
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	esimard, jima
Version:	4.5
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:32:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alexander Demicev 2020-04-29 14:07:57 UTC

Description of problem:

Update vsphere machine api from alpha to beta

Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
ansible --version

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated

Expected results:

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 4 jima 2020-05-19 08:15:51 UTC

@Alexander, 

I checked that apiVersion of machine and machineset on IPI cluster with 4.5.0-0.nightly-2020-05-17-220731 on vsphere.
$ oc get machineset wzheng-45-q4cj5-worker -n openshift-machine-api -o json | jq -r .apiVersion
machine.openshift.io/v1beta1
$ oc get machine wzheng-45-q4cj5-master-0 -n openshift-machine-api -o json | jq -r .apiVersion
machine.openshift.io/v1beta1

Both apiVersion are v1beta1, is it enough to verify this issue?

Comment 5 Alexander Demicev 2020-05-19 11:58:26 UTC

Hi, yes this is enough

Comment 6 errata-xmlrpc 2020-07-13 17:32:51 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