Bug 1749367

Summary:	OCP on OSP 13 IPI install fails when Ceph RGW used for object store
Product:	OpenShift Container Platform	Reporter:	jliberma <jliberma>
Component:	Installer	Assignee:	Mike Fedosin <mfedosin>
Installer sub component:	OpenShift on OpenStack	QA Contact:	David Sanz <dsanzmor>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	asadawar, asimonel, dsanzmor, dsundqvi, eduen, elavarde, gkadam, moddi, xtian
Version:	4.2.0	Flags:	dsanzmor: needinfo-
Target Milestone:	---
Target Release:	4.3.z
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-02-12 09:42:20 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 jliberma@redhat.com 2019-09-05 13:20:38 UTC

Description of problem:

OCP on OSP 13 IPI install fails when Ceph RGW for object store. Rgw does not use tempURLs by default. tempURLs are used by installer to generate the temporary bucket . The bootstrap ignition config is not available.


Errors are here:
http://pastebin.test.redhat.com/778570
http://pastebin.test.redhat.com/778544


How reproducible:
Every time.


Steps to Reproduce:
1. Deploy OSP 13 with Ceph RGW object store
2. Attempt OCP 4.2 IPI installation

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

Expected results:

openshift-install can fetch bootstrap ignition file from RGW object store.

Additional info:

Here are Red Hat internal notes on steps to reproduce the issue: https://docs.google.com/document/d/14cfKC1mTGqZFeqUC7YLNMkLVv1FFQsB92hSBibrk0SY/edit

Comment 1 Eric Duen 2019-09-05 15:31:34 UTC

Assigned to Mike.

Comment 13 David Sanz 2020-01-17 11:31:20 UTC

Verified on 4.3.0-0.nightly-2020-01-16-123848

Comment 19 errata-xmlrpc 2020-02-12 09:42:20 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:0391