Bug 1515457 - [3.7] fact gathering fails during upgrade from 3.4 to 3.5 on delete_empty_keys(facts['master']['admission_plugin_config']['BuildDefaults']['configuration']['env'])\r\nKeyError: 'env'\r\n"
Summary: [3.7] fact gathering fails during upgrade from 3.4 to 3.5 on delete_empty_key...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 3.7.z
Assignee: Scott Dodson
QA Contact: Gan Huang
Depends On: 1469387 1515458 1515459
Blocks: 1491718
TreeView+ depends on / blocked
Reported: 2017-11-20 20:04 UTC by Scott Dodson
Modified: 2021-03-11 16:20 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The configuration management for builddefaults attempts to remove environment variables that were previously defined but have since been removed from the configuration. In situations where no environment variables have been configured this was failing because the 'env' key did not exist. The process has now been updated to skip the cleanup when the env key does not exist.
Clone Of: 1469387
Last Closed: 2017-12-18 13:23:56 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:3464 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.7 bug fix and enhancement update 2017-12-18 18:22:05 UTC

Comment 3 Gan Huang 2017-12-08 02:20:31 UTC
Verified in openshift-ansible-3.7.13-1.git.0.a8e2fcb.el7.noarch.rpm

Installation succeed with the parameter set:

openshift_builddefaults_json={"BuildDefaults": {"configuration": {"apiVersion": "v1","kind": "BuildDefaultsConfig"}}}

Comment 6 errata-xmlrpc 2017-12-18 13:23:56 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.


Note You need to log in before you can comment on or make changes to this bug.