Description of problem: After updating the "rubygem-openshift-origin-node" package, resource_limits.conf.rpmnew file is not generated. Version-Release number of selected component (if applicable): puddle[2.0/2013-10-14.3] rubygem-openshift-origin-node-1.17.4-1.git.0.5f8f113.el6op.noarch.rpm How reproducible: always Steps to Reproduce: 1. Launch old_instance 2. modify the resource configuration file, e.g: change node_profile # vim resource_limits.conf <--snip--> node_profile=xxxx <--snip--> quota_files=80000 # 1GB. 1 block = 1024byte quota_blocks=2048576 <--snip--> 3. Update packages to latest Actual results: resource_limits.conf is not updated, but .rpmnew file is not generated. User can not notice some change if new new config file has some change. Expected results: old conf file is still used, new conf file is saved to .rpmnew Additional info:
I'm a little confused. Was the a change in the resource_limits.conf between the previous package and the new package? It's labeled as a configuration file in the spec so RPM should do the right thing. If there was no change then an .rpnnew won't be created.
(In reply to Brenton Leanhardt from comment #2) > I'm a little confused. Was the a change in the resource_limits.conf between > the previous package and the new package? It's labeled as a configuration > file in the spec so RPM should do the right thing. If there was no change > then an .rpnnew won't be created. Yes, user did a change in the resource_limits.conf installed by previous package, then yum update the package to the latest version. The new package does not create .rpmnew file.