Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1837794

Summary: OCP 4.4 cannot be installed on RHV
Product: OpenShift Container Platform Reporter: Chen <cchen>
Component: InstallerAssignee: Roy Golan <rgolan>
Installer sub component: OpenShift on RHV QA Contact: Lucie Leistnerova <lleistne>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: unspecified CC: dougsland
Version: 4.4   
Target Milestone: ---   
Target Release: ---   
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-05-28 10:57:28 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 Chen 2020-05-20 02:08:17 UTC
Description of problem:

OCP4.4 on RHV INI can not install master successfully.

Version-Release number of the following components:

OCP 4.4

How reproducible:

100%

Steps to Reproduce:
1. Create template and upload to RHV
2. Export environment variables
3. openshift-install create cluster --dir=<path>

Actual results:

Several operators can not start properly on master

Expected results:

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

Comment 3 Roy Golan 2020-05-20 12:45:08 UTC
The panic was handled in Bug 1830486.

Regarding networking, you'd have to make the rhv address resolvable to that network. That is a basic demand.

Comment 4 Douglas Schilling Landgraf 2020-05-28 10:57:28 UTC
Hi Chen,

(In reply to Roy Golan from comment #3)
> The panic was handled in Bug 1830486.
> 
> Regarding networking, you'd have to make the rhv address resolvable to that
> network. That is a basic demand.

Based on Roy's comment I am closing this bug as dup of 1830486. Fell free to re-open in case you need more assistance.

*** This bug has been marked as a duplicate of bug 1830486 ***