Description of problem: Run "atomic-openshift-excluder exclude" and "atomic-openshift-docker-excluder exclude" to exclude expected packages updated after rpm install excluder successfully, the expected packages in /usr/sbin/*excluder* are not added into /etc/yum.conf to prevent ocp and docker not updated. # cat /etc/yum.conf [main] cachedir=/var/cache/yum/$basearch/$releasever keepcache=0 debuglevel=2 logfile=/var/log/yum.log exactarch=1 obsoletes=1 excludes= excludes= excludes= excludes= gpgcheck=1 plugins=1 installonly_limit=3 Version-Release number of selected component (if applicable): atomic-openshift-docker-excluder-3.4.0.33-1.git.0.71c05b2.el7.noarch atomic-openshift-excluder-3.4.0.33-1.git.0.71c05b2.el7.noarch How reproducible: always Steps to Reproduce: 1. rpm install ose/ocp on rhel hosts. 2. rpm install atomic-openshift-excluder and atomic-openshift-docker-excluder 3. run "atomic-openshift-excluder exclude" and "atomic-openshift-docker-excluder exclude" Actual results: the expected packages in /usr/sbin/*excluder* are not added into /etc/yum.conf to prevent ocp and docker not updated. Expected results: It should add expected packages into yum.conf to prevent ocp and docker updated when run "*excluder* exclude" command as a postinstall after install excluder or run "*excluder* exclude" command manually.
Found the problem and fixed it. Upstream pull request: https://github.com/openshift/origin/pull/12191 OSE 3.4 pull request: https://github.com/openshift/ose/pull/499
Version: atomic-openshift-excluder-3.4.0.34-1.git.0.87d9d8d.el7.noarch atomic-openshift-docker-excluder-3.4.0.34-1.git.0.87d9d8d.el7.noarch Steps: 1. rpm install ocp on rhel hosts. 2. install atomic-openshift-excluder 3. run "atomic-openshift-excluder exclude" 4. run "atomic-openshift-excluder unexclude" as a workaround of bug1403655 5. install atomic-openshift-docker-excluder 6. run "atomic-openshift-docker-excluder exclude" Result: For step3 and step6,all packages need to be excluded have been added into yum config file rightly as an exclude line. I think the problem has been fixed.
Since this has not been released yet, and no customers were affected, I am marking this Closed.