Bug 1497599 - BuildDefaults are not automatically inherited in master-config.yaml after upgrade
Summary: BuildDefaults are not automatically inherited in master-config.yaml after upg...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.6.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.9.z
Assignee: Scott Dodson
QA Contact: liujia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-02 06:51 UTC by Jaspreet Kaur
Modified: 2021-09-09 12:39 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-29 21:12:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1486054 0 high CLOSED Installer removes custom configuration from master-config.yaml during upgrade 2021-02-22 00:41:40 UTC

Internal Links: 1486054

Description Jaspreet Kaur 2017-10-02 06:51:01 UTC 
Description of problem: It is observed that the master config parameters having build defaults are not preserved after upgrade. These build defaults are there to provide proxies to the builds

Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
ansible --version

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results: Builddefaults are wiped off from master config after upgrade to 3.5

Expected results: These parameters should be preserved.

Additional info:
Please attach logs from ansible-playbook with the -vvv flag
Comment 4 Michael Gugino 2018-11-29 21:12:26 UTC 
I believe this is corrected in 3.9 and newer.  If you still face this problem after upgrading to the latest versions, please file a new BZ against the newer version.
Note You need to log in before you can comment on or make changes to this bug.