This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 1302787 - Node web proxy configuration file is overwritten upon update
Node web proxy configuration file is overwritten upon update
Product: OpenShift Container Platform
Classification: Red Hat
Component: Upgrade (Show other bugs)
x86_64 Linux
unspecified Severity low
: ---
: ---
Assigned To: Timothy Williams
Anping Li
Depends On:
  Show dependency treegraph
Reported: 2016-01-28 10:56 EST by Timothy Williams
Modified: 2016-03-22 12:54 EDT (History)
4 users (show)

See Also:
Fixed In Version: openshift-origin-node-proxy-
Doc Type: Bug Fix
Doc Text:
Cause: The /etc/openshift/web-proxy-config.json configuration file for the node web proxy was not marked as a configuration file upon install. Consequence: New versions of the openshift-origin-node-proxy package would overwrite any changes to the /etc/openshift/web-proxy-config.json file with the original version of the file. Fix: The /etc/openshift/web-proxy-config.json file is now marked as a configuration file in the rpm spec. Result: The /etc/openshift/web-proxy-config.json file will no longer be overwritten when openshift-origin-node-proxy is updated.
Story Points: ---
Clone Of:
Last Closed: 2016-03-22 12:54:09 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Timothy Williams 2016-01-28 10:56:20 EST
Description of problem:
The node web proxy's configuration file, /etc/openshift/web-proxy-config.json, is overwritten upon updating the rpm. 

The configuration file is not marked as a configuration file in the openshift-origin-node-proxy rpm spec file.
Comment 1 Timothy Williams 2016-01-28 10:57:26 EST
This bug was resolved upstream in the following PR:
Comment 5 Anping Li 2016-02-24 00:37:09 EST
The web-proxy-config.json was still overwritten. the web-proxy-config.json was pull in by openshift-origin-node-proxy. while this bug fixed in openshift-origin-node-util-
Comment 8 Anping Li 2016-02-29 00:30:06 EST
There isn't web-proxy-config.json.rpmnew file after upgrade.
Comment 9 Timothy Williams 2016-02-29 11:23:01 EST
This is working for me. You can see in the yum output that upgrading after modifying the web-proxy-config.json file results in an rpmnew file being created:

# yum localinstall /tmp/openshift-origin-node-proxy- 
Loaded plugins: priorities, security
Setting up Local Package Process
Examining /tmp/openshift-origin-node-proxy- openshift-origin-node-proxy-
Marking /tmp/openshift-origin-node-proxy- as an update to openshift-origin-node-proxy-1.26.1-1.git.1103.c6cf7cf.el6.noarch
--> Running transaction check
---> Package openshift-origin-node-proxy.noarch 0:1.26.1-1.git.1103.c6cf7cf.el6 will be updated
---> Package openshift-origin-node-proxy.noarch 0: will be an update
--> Finished Dependency Resolution

Dependencies Resolved

 Package                      Arch    Version              Repository                                             Size
 openshift-origin-node-proxy  noarch     /openshift-origin-node-proxy-  100 k

Transaction Summary
Upgrade       1 Package(s)

Total size: 100 k
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Warning: RPMDB altered outside of yum.
  Updating   : openshift-origin-node-proxy-                                                 1/2 
warning: /etc/openshift/web-proxy-config.json created as /etc/openshift/web-proxy-config.json.rpmnew
[  OK  ] node-web-proxy: [  OK  ]
Starting node-web-proxy: [  OK  ]
  Cleanup    : openshift-origin-node-proxy-1.26.1-1.git.1103.c6cf7cf.el6.noarch                                    2/2 
  Verifying  : openshift-origin-node-proxy-                                                 1/2 
  Verifying  : openshift-origin-node-proxy-1.26.1-1.git.1103.c6cf7cf.el6.noarch                                    2/2 

  openshift-origin-node-proxy.noarch 0:                                                                

# ls /etc/openshift | grep web-proxy

Could you re-test please? If this fails again, please provide the old version, the new version, and the modification you made to the web-proxy-config.json so we can investigate.
Comment 12 Anping Li 2016-03-07 02:43:41 EST
It work well now.

---> Package openshift-origin-node-proxy.noarch 0: will be updated
---> Package openshift-origin-node-proxy.noarch 0: will be an update
ls -1 /etc/openshift/web-proxy-config.json*
Comment 14 errata-xmlrpc 2016-03-22 12:54:09 EDT
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.