Bug 1836368 - [ovirt] validating instanceTypeID panics
Summary: [ovirt] validating instanceTypeID panics
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.5.0
Assignee: Roy Golan
QA Contact: Jan Zmeskal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-15 17:36 UTC by Roy Golan
Modified: 2020-07-13 17:39 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:39:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 3609 0 None closed Bug 1836368: ovirt: return slice and not nil in instanceTypeID validation 2020-06-24 03:01:07 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:39:42 UTC

Description Roy Golan 2020-05-15 17:36:46 UTC
Description of problem:

using this valid machine pool panics the installation:

compute:
- architecture: amd64
  name: worker
  platform:
    ovirt: {}

openshift-install create install-config --dir /test
FATAL %!v(PANIC=Format method: runtime error: invalid memory address or nil pointer dereference)

The reason is an nil value inside an error list.

Comment 3 Jan Zmeskal 2020-05-18 08:17:54 UTC
Verified with: 
openshift-install-linux-4.5.0-0.nightly-2020-05-18-043243
rhvm-4.3.10.3-0.1.master.el7.noarch

Verification steps:
1. Put this into install-config.yaml:

controlPlane:
  architecture: amd64
  hyperthreading: Enabled
  name: master
  platform:
    ovirt:
      osDisk:
        sizeGB: 18
  replicas: 3

2. Run the installation
3. Make sure it successfully creates master nodes

Comment 4 errata-xmlrpc 2020-07-13 17:39:24 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.