Created attachment 1432995 [details] rolling update log_vv Description of problem: nfs-ganesha packages are not getting upgraded through rolling update from 3.0Z2 to Z3 Version-Release number of selected component (if applicable): rpm -qa | grep ansible ansible-2.4.2.0-2.el7.noarch ceph-ansible-3.0.32-1.el7cp.noarch How reproducible: always Steps to Reproduce: 1. Configure Z2 cluster with NFS. 2. Upgrade to Z3 by running rolling update. Actual results: NFS packages are not upgraded. TASK [ceph-nfs : install redhat nfs-ganesha-rgw and ceph-radosgw packages] ********** task path: /usr/share/ceph-ansible/roles/ceph-nfs/tasks/pre_requisite_non_container.yml:82 ok: [magna023] => (item=nfs-ganesha-rgw) => {"changed": false, "item": "nfs-ganesha-rgw", "msg": "", "rc": 0, "results": ["nfs-ganesha-rgw-2.5.5-3.el7cp.x86_64 providing nfs-ganesha-rgw is already installed"]} ok: [magna023] => (item=ceph-radosgw) => {"changed": false, "item": "ceph-radosgw", "msg": "", "rc": 0, "results": ["2:ceph-radosgw-12.2.4-10.el7cp.x86_64 providing ceph-radosgw is already installed"]} NFS Packages in Z2: ------------------- nfs-ganesha-2.5.5-3.el7cp.x86_64 nfs-ganesha-debuginfo-2.5.5-3.el7cp.x86_64 nfs-ganesha-rgw-2.5.5-3.el7cp.x86_64 NFS packages in Z3 repo( that is to be upgraded to): --------------------------------------------------- nfs-ganesha-2.5.5-5.el7cp.x86_64.rpm nfs-ganesha-rgw-2.5.5-5.el7cp.x86_64.rpm Expected results: NFS packages should be upgraded Additional info: I can manually upgrade on nfs node: sudo yum update nfs-ganesha Loaded plugins: fastestmirror, langpacks, priorities, product-id, search-disabled-repos, subscription-manager Loading mirror speeds from cached hostfile Resolving Dependencies --> Running transaction check ---> Package nfs-ganesha.x86_64 0:2.5.5-3.el7cp will be updated --> Processing Dependency: nfs-ganesha = 2.5.5-3.el7cp for package: nfs-ganesha-rgw-2.5.5-3.el7cp.x86_64 ---> Package nfs-ganesha.x86_64 0:2.5.5-5.el7cp will be an update --> Running transaction check ---> Package nfs-ganesha-rgw.x86_64 0:2.5.5-3.el7cp will be updated ---> Package nfs-ganesha-rgw.x86_64 0:2.5.5-5.el7cp will be an update --> Finished Dependency Resolution Dependencies Resolved =================================================================================================================================================================================================================== Package Arch Version Repository Size =================================================================================================================================================================================================================== Updating: nfs-ganesha x86_64 2.5.5-5.el7cp download-node-02.eng.bos.redhat.com_composes_auto_ceph-3.0-rhel-7_latest-RHCEPH-3-RHEL-7_compose_Tools_x86_64_os_ 649 k Updating for dependencies: nfs-ganesha-rgw x86_64 2.5.5-5.el7cp download-node-02.eng.bos.redhat.com_composes_auto_ceph-3.0-rhel-7_latest-RHCEPH-3-RHEL-7_compose_Tools_x86_64_os_ 34 k Transaction Summary =================================================================================================================================================================================================================== Upgrade 1 Package (+1 Dependent package) Workaround: NFS node can be upgraded manually. 1. Stop nfs-ganesha service 2. yum update nfs-ganesh 3. Start the nfs-ganesha service I have attached the rolling update log.
v3.0.33 upstream has the fix.
nfs-ganesha packages are now getting upgraded through rolling update from 3.0Z2 to Z3 ,moving to verified state. Version-Release number of selected component (if applicable): rpm -qa | grep ansible ansible-2.4.2.0-2.el7.noarch ceph-ansible-3.0.33-1.el7cp NFS Packages in Z2: ------------------- nfs-ganesha-2.5.5-3.el7cp.x86_64 nfs-ganesha-rgw-2.5.5-3.el7cp.x86_64 NFS packages in Z3 repo( after upgrade): --------------------------------------------------- nfs-ganesha-2.5.5-5.el7cp.x86_64.rpm nfs-ganesha-rgw-2.5.5-5.el7cp.x86_64.rpm
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. https://access.redhat.com/errata/RHBA-2018:1563