Bug 1791437

Summary: Unable to specify OPENSHIFT_INSTALL_INVOKER when doing a UPI installation
Product: OpenShift Container Platform Reporter: Alex Crawford <crawford>
Component: InstallerAssignee: Alex Crawford <crawford>
Installer sub component: openshift-installer QA Contact: Yang Yang <yanyang>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: jialiu, sdodson
Version: 4.2.zKeywords: NeedsTestCase
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1791440 (view as bug list) Environment:
Last Closed: 2020-05-04 11:24:44 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:
Bug Depends On:    
Bug Blocks: 1791440    

Description Alex Crawford 2020-01-15 20:19:00 UTC
The OPENSHIFT_INSTALL_INVOKER only takes effect when doing an IPI installation. CI (and maybe others) need to use that override, even when doing a UPI installation.

Comment 1 Scott Dodson 2020-01-24 14:25:02 UTC
*** Bug 1794602 has been marked as a duplicate of this bug. ***

Comment 3 Yang Yang 2020-02-04 10:42:31 UTC
Verified with 4.4.0-0.nightly-2020-02-03-163409

Steps of verification are as below:
1. Set environment variable
export OPENSHIFT_INSTALL_INVOKER=yanyang

2. Install a UPI cluster on GCP

3. Check configmap
# oc get configmap -n openshift-config openshift-install -o yaml
apiVersion: v1
data:
  invoker: yanyang
  version: v4.4.0
kind: ConfigMap
metadata:
  creationTimestamp: "2020-02-04T09:52:19Z"
  name: openshift-install
  namespace: openshift-config
  resourceVersion: "926"
  selfLink: /api/v1/namespaces/openshift-config/configmaps/openshift-install
  uid: a6254f26-9ffa-4af8-8526-7c95b7d2d9dc

The test results are as expected hence moving it to verified state.

Comment 5 errata-xmlrpc 2020-05-04 11:24:44 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:0581