Bug 1832832

Summary:	Disk extension fails due to misuse of oVirt api
Product:	OpenShift Container Platform	Reporter:	Roy Golan <rgolan>
Component:	Cloud Compute	Assignee:	Roy Golan <rgolan>
Cloud Compute sub component:	oVirt Provider	QA Contact:	Jan Zmeskal <jzmeskal>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	urgent	CC:	jzmeskal, stbenjam
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:35:55 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 Roy Golan 2020-05-07 10:58:08 UTC

Description of problem:

Disk extension fails due to misuse of the API. 

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

How reproducible:
100%

Steps to Reproduce:
1.edit the machineset like so (stripping unrelated parts)

spec:
  template:
    spec:
      providerSpec:
        value:
          os_disk:
            size_gb: 18

Note that the value 18 must be greater than the current disk size, which is 16 (at the moment, will change in the future)


2. delete a machine, let the controller recreate it. It will not boot
and the disk size will remain 16

Expected results:
VM boots and the disk extends to 18GB

Comment 4 Jan Zmeskal 2020-05-19 09:11:14 UTC

Verified on cluster version: 4.5.0-0.nightly-2020-05-18-043243
RHV: rhvm-4.3.10.3-0.1.master.el7.noarch

Verification steps:
1. Have a deployed OCP4.5 cluster
2. Edit worker MachineSet and increase disk size from my original value (32 GB) to a new value (36 GB)
3. Scale the MachineSet down
4. Scela the MachineSet up
5. Make sure that the newly created VM has a disk of 36 GB

Comment 5 errata-xmlrpc 2020-07-13 17:35:55 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