Hide Forgot
Description of problem: whiel upgrading from 3.1.3 to 3.8.4.5 warning messages are thrown Version-Release number of selected component (if applicable): [root@dhcp47-114 /]# gluster --version glusterfs 3.8.4 built on Nov 11 2016 06:45:09 Repository revision: git://git.gluster.com/glusterfs.git Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com> GlusterFS comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of GlusterFS under the terms of the GNU General Public License. How reproducible: Steps to Reproduce: 1. Upgrade from RHGS 3.1.3 RHEL 6.8 server packages to RHGS 3.8.4.5 server packages 2. Warning messages like below are shown during the upgrade process. <Cut> Updating : glusterfs-server-3.8.4-5.el6rhs.x86_64 7/26 warning: %post(glusterfs-server-3.8.4-5.el6rhs.x86_64) scriptlet failed, exit status 1 Non-fatal POSTIN scriptlet failure in rpm package glusterfs-server-3.8.4-5.el6rhs.x86_64 </cut> Actual results: [root@dhcp47-131 3.2]# [root@dhcp47-131 3.2]# ls gdeploy-2.0.1-3.el6rhs.noarch.rpm glusterfs-ganesha-3.8.4-5.el6rhs.x86_64.rpm glusterfs-3.8.4-5.el6rhs.x86_64.rpm glusterfs-geo-replication-3.8.4-5.el6rhs.x86_64.rpm glusterfs-api-3.8.4-5.el6rhs.x86_64.rpm glusterfs-libs-3.8.4-5.el6rhs.x86_64.rpm glusterfs-api-devel-3.8.4-5.el6rhs.x86_64.rpm glusterfs-rdma-3.8.4-5.el6rhs.x86_64.rpm glusterfs-cli-3.8.4-5.el6rhs.x86_64.rpm glusterfs-server-3.8.4-5.el6rhs.x86_64.rpm glusterfs-client-xlators-3.8.4-5.el6rhs.x86_64.rpm gluster-nagios-addons-0.2.8-1.el6rhs.x86_64.rpm glusterfs-devel-3.8.4-5.el6rhs.x86_64.rpm python-gluster-3.8.4-5.el6rhs.noarch.rpm glusterfs-events-3.8.4-5.el6rhs.x86_64.rpm redhat-storage-server-3.2.0.1-1.el6rhs.noarch.rpm glusterfs-fuse-3.8.4-5.el6rhs.x86_64.rpm swiftonfile-1.13.1-9.el6rhs.noarch.rpm [root@dhcp47-131 3.2]# [root@dhcp47-131 3.2]# [root@dhcp47-131 3.2]# [root@dhcp47-131 3.2]# yum localupdate *.rpm Loaded plugins: product-id, rhnplugin, search-disabled-repos, security, subscription-manager This system is receiving updates from RHN Classic or RHN Satellite. Setting up Local Package Process Examining gdeploy-2.0.1-3.el6rhs.noarch.rpm: gdeploy-2.0.1-3.el6rhs.noarch Package gdeploy not installed, cannot update it. Run yum install to install it instead. Examining glusterfs-3.8.4-5.el6rhs.x86_64.rpm: glusterfs-3.8.4-5.el6rhs.x86_64 Marking glusterfs-3.8.4-5.el6rhs.x86_64.rpm as an update to glusterfs-3.7.9-12.el6rhs.x86_64 Examining glusterfs-api-3.8.4-5.el6rhs.x86_64.rpm: glusterfs-api-3.8.4-5.el6rhs.x86_64 Marking glusterfs-api-3.8.4-5.el6rhs.x86_64.rpm as an update to glusterfs-api-3.7.9-12.el6rhs.x86_64 Examining glusterfs-api-devel-3.8.4-5.el6rhs.x86_64.rpm: glusterfs-api-devel-3.8.4-5.el6rhs.x86_64 Package glusterfs-api-devel not installed, cannot update it. Run yum install to install it instead. Examining glusterfs-cli-3.8.4-5.el6rhs.x86_64.rpm: glusterfs-cli-3.8.4-5.el6rhs.x86_64 Marking glusterfs-cli-3.8.4-5.el6rhs.x86_64.rpm as an update to glusterfs-cli-3.7.9-12.el6rhs.x86_64 Examining glusterfs-client-xlators-3.8.4-5.el6rhs.x86_64.rpm: glusterfs-client-xlators-3.8.4-5.el6rhs.x86_64 Marking glusterfs-client-xlators-3.8.4-5.el6rhs.x86_64.rpm as an update to glusterfs-client-xlators-3.7.9-12.el6rhs.x86_64 Examining glusterfs-devel-3.8.4-5.el6rhs.x86_64.rpm: glusterfs-devel-3.8.4-5.el6rhs.x86_64 Package glusterfs-devel not installed, cannot update it. Run yum install to install it instead. Examining glusterfs-events-3.8.4-5.el6rhs.x86_64.rpm: glusterfs-events-3.8.4-5.el6rhs.x86_64 Package glusterfs-events not installed, cannot update it. Run yum install to install it instead. Examining glusterfs-fuse-3.8.4-5.el6rhs.x86_64.rpm: glusterfs-fuse-3.8.4-5.el6rhs.x86_64 Marking glusterfs-fuse-3.8.4-5.el6rhs.x86_64.rpm as an update to glusterfs-fuse-3.7.9-12.el6rhs.x86_64 Examining glusterfs-ganesha-3.8.4-5.el6rhs.x86_64.rpm: glusterfs-ganesha-3.8.4-5.el6rhs.x86_64 Package glusterfs-ganesha not installed, cannot update it. Run yum install to install it instead. Examining glusterfs-geo-replication-3.8.4-5.el6rhs.x86_64.rpm: glusterfs-geo-replication-3.8.4-5.el6rhs.x86_64 Marking glusterfs-geo-replication-3.8.4-5.el6rhs.x86_64.rpm as an update to glusterfs-geo-replication-3.7.9-12.el6rhs.x86_64 Examining glusterfs-libs-3.8.4-5.el6rhs.x86_64.rpm: glusterfs-libs-3.8.4-5.el6rhs.x86_64 Marking glusterfs-libs-3.8.4-5.el6rhs.x86_64.rpm as an update to glusterfs-libs-3.7.9-12.el6rhs.x86_64 Examining glusterfs-rdma-3.8.4-5.el6rhs.x86_64.rpm: glusterfs-rdma-3.8.4-5.el6rhs.x86_64 Marking glusterfs-rdma-3.8.4-5.el6rhs.x86_64.rpm as an update to glusterfs-rdma-3.7.9-12.el6rhs.x86_64 Examining glusterfs-server-3.8.4-5.el6rhs.x86_64.rpm: glusterfs-server-3.8.4-5.el6rhs.x86_64 Marking glusterfs-server-3.8.4-5.el6rhs.x86_64.rpm as an update to glusterfs-server-3.7.9-12.el6rhs.x86_64 Examining gluster-nagios-addons-0.2.8-1.el6rhs.x86_64.rpm: gluster-nagios-addons-0.2.8-1.el6rhs.x86_64 Marking gluster-nagios-addons-0.2.8-1.el6rhs.x86_64.rpm as an update to gluster-nagios-addons-0.2.7-1.el6rhs.x86_64 Examining python-gluster-3.8.4-5.el6rhs.noarch.rpm: python-gluster-3.8.4-5.el6rhs.noarch Marking python-gluster-3.8.4-5.el6rhs.noarch.rpm as an update to python-gluster-3.7.9-12.el6rhs.noarch Examining redhat-storage-server-3.2.0.1-1.el6rhs.noarch.rpm: redhat-storage-server-3.2.0.1-1.el6rhs.noarch Marking redhat-storage-server-3.2.0.1-1.el6rhs.noarch.rpm as an update to redhat-storage-server-3.1.3.0-3.el6rhs.noarch Examining swiftonfile-1.13.1-9.el6rhs.noarch.rpm: swiftonfile-1.13.1-9.el6rhs.noarch Marking swiftonfile-1.13.1-9.el6rhs.noarch.rpm as an update to swiftonfile-1.13.1-8.el6rhs.noarch Resolving Dependencies --> Running transaction check ---> Package gluster-nagios-addons.x86_64 0:0.2.7-1.el6rhs will be updated ---> Package gluster-nagios-addons.x86_64 0:0.2.8-1.el6rhs will be an update ---> Package glusterfs.x86_64 0:3.7.9-12.el6rhs will be updated ---> Package glusterfs.x86_64 0:3.8.4-5.el6rhs will be an update ---> Package glusterfs-api.x86_64 0:3.7.9-12.el6rhs will be updated ---> Package glusterfs-api.x86_64 0:3.8.4-5.el6rhs will be an update ---> Package glusterfs-cli.x86_64 0:3.7.9-12.el6rhs will be updated ---> Package glusterfs-cli.x86_64 0:3.8.4-5.el6rhs will be an update ---> Package glusterfs-client-xlators.x86_64 0:3.7.9-12.el6rhs will be updated ---> Package glusterfs-client-xlators.x86_64 0:3.8.4-5.el6rhs will be an update ---> Package glusterfs-fuse.x86_64 0:3.7.9-12.el6rhs will be updated ---> Package glusterfs-fuse.x86_64 0:3.8.4-5.el6rhs will be an update ---> Package glusterfs-geo-replication.x86_64 0:3.7.9-12.el6rhs will be updated ---> Package glusterfs-geo-replication.x86_64 0:3.8.4-5.el6rhs will be an update ---> Package glusterfs-libs.x86_64 0:3.7.9-12.el6rhs will be updated ---> Package glusterfs-libs.x86_64 0:3.8.4-5.el6rhs will be an update ---> Package glusterfs-rdma.x86_64 0:3.7.9-12.el6rhs will be updated ---> Package glusterfs-rdma.x86_64 0:3.8.4-5.el6rhs will be an update ---> Package glusterfs-server.x86_64 0:3.7.9-12.el6rhs will be updated ---> Package glusterfs-server.x86_64 0:3.8.4-5.el6rhs will be an update ---> Package python-gluster.noarch 0:3.7.9-12.el6rhs will be updated ---> Package python-gluster.noarch 0:3.8.4-5.el6rhs will be an update ---> Package redhat-storage-server.noarch 0:3.1.3.0-3.el6rhs will be updated ---> Package redhat-storage-server.noarch 0:3.2.0.1-1.el6rhs will be an update ---> Package swiftonfile.noarch 0:1.13.1-8.el6rhs will be updated ---> Package swiftonfile.noarch 0:1.13.1-9.el6rhs will be an update --> Finished Dependency Resolution Dependencies Resolved ===================================================================================================================== Package Arch Version Repository Size ===================================================================================================================== Updating: gluster-nagios-addons x86_64 0.2.8-1.el6rhs /gluster-nagios-addons-0.2.8-1.el6rhs.x86_64 160 k glusterfs x86_64 3.8.4-5.el6rhs /glusterfs-3.8.4-5.el6rhs.x86_64 1.8 M glusterfs-api x86_64 3.8.4-5.el6rhs /glusterfs-api-3.8.4-5.el6rhs.x86_64 153 k glusterfs-cli x86_64 3.8.4-5.el6rhs /glusterfs-cli-3.8.4-5.el6rhs.x86_64 465 k glusterfs-client-xlators x86_64 3.8.4-5.el6rhs /glusterfs-client-xlators-3.8.4-5.el6rhs.x86_64 3.6 M glusterfs-fuse x86_64 3.8.4-5.el6rhs /glusterfs-fuse-3.8.4-5.el6rhs.x86_64 320 k glusterfs-geo-replication x86_64 3.8.4-5.el6rhs /glusterfs-geo-replication-3.8.4-5.el6rhs.x86_64 818 k glusterfs-libs x86_64 3.8.4-5.el6rhs /glusterfs-libs-3.8.4-5.el6rhs.x86_64 1.2 M glusterfs-rdma x86_64 3.8.4-5.el6rhs /glusterfs-rdma-3.8.4-5.el6rhs.x86_64 87 k glusterfs-server x86_64 3.8.4-5.el6rhs /glusterfs-server-3.8.4-5.el6rhs.x86_64 4.6 M python-gluster noarch 3.8.4-5.el6rhs /python-gluster-3.8.4-5.el6rhs.noarch 15 k redhat-storage-server noarch 3.2.0.1-1.el6rhs /redhat-storage-server-3.2.0.1-1.el6rhs.noarch 2.3 M swiftonfile noarch 1.13.1-9.el6rhs /swiftonfile-1.13.1-9.el6rhs.noarch 561 k Transaction Summary ===================================================================================================================== Upgrade 13 Package(s) Total size: 16 M Is this ok [y/N]: y Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Updating : glusterfs-libs-3.8.4-5.el6rhs.x86_64 1/26 Updating : glusterfs-3.8.4-5.el6rhs.x86_64 2/26 Updating : glusterfs-client-xlators-3.8.4-5.el6rhs.x86_64 3/26 Updating : glusterfs-fuse-3.8.4-5.el6rhs.x86_64 4/26 Updating : glusterfs-api-3.8.4-5.el6rhs.x86_64 5/26 Updating : glusterfs-cli-3.8.4-5.el6rhs.x86_64 6/26 Updating : glusterfs-server-3.8.4-5.el6rhs.x86_64 7/26 warning: %post(glusterfs-server-3.8.4-5.el6rhs.x86_64) scriptlet failed, exit status 1 Non-fatal POSTIN scriptlet failure in rpm package glusterfs-server-3.8.4-5.el6rhs.x86_64 Updating : glusterfs-geo-replication-3.8.4-5.el6rhs.x86_64 8/26 Updating : python-gluster-3.8.4-5.el6rhs.noarch 9/26 Updating : swiftonfile-1.13.1-9.el6rhs.noarch 10/26 Updating : gluster-nagios-addons-0.2.8-1.el6rhs.x86_64 11/26 Updating : redhat-storage-server-3.2.0.1-1.el6rhs.noarch 12/26 Updating : glusterfs-rdma-3.8.4-5.el6rhs.x86_64 13/26 Cleanup : redhat-storage-server-3.1.3.0-3.el6rhs.noarch 14/26 Cleanup : glusterfs-geo-replication-3.7.9-12.el6rhs.x86_64 15/26 Cleanup : glusterfs-server-3.7.9-12.el6rhs.x86_64 16/26 Cleanup : glusterfs-fuse-3.7.9-12.el6rhs.x86_64 17/26 Cleanup : glusterfs-api-3.7.9-12.el6rhs.x86_64 18/26 Cleanup : glusterfs-rdma-3.7.9-12.el6rhs.x86_64 19/26 Cleanup : glusterfs-3.7.9-12.el6rhs.x86_64 20/26 Cleanup : glusterfs-client-xlators-3.7.9-12.el6rhs.x86_64 21/26 Cleanup : glusterfs-cli-3.7.9-12.el6rhs.x86_64 22/26 Cleanup : swiftonfile-1.13.1-8.el6rhs.noarch 23/26 Cleanup : python-gluster-3.7.9-12.el6rhs.noarch 24/26 Cleanup : glusterfs-libs-3.7.9-12.el6rhs.x86_64 25/26 Cleanup : gluster-nagios-addons-0.2.7-1.el6rhs.x86_64 26/26 Verifying : glusterfs-client-xlators-3.8.4-5.el6rhs.x86_64 1/26 Verifying : gluster-nagios-addons-0.2.8-1.el6rhs.x86_64 2/26 Verifying : glusterfs-geo-replication-3.8.4-5.el6rhs.x86_64 3/26 Verifying : glusterfs-api-3.8.4-5.el6rhs.x86_64 4/26 Verifying : glusterfs-libs-3.8.4-5.el6rhs.x86_64 5/26 Verifying : python-gluster-3.8.4-5.el6rhs.noarch 6/26 Verifying : glusterfs-fuse-3.8.4-5.el6rhs.x86_64 7/26 Verifying : glusterfs-rdma-3.8.4-5.el6rhs.x86_64 8/26 Verifying : redhat-storage-server-3.2.0.1-1.el6rhs.noarch 9/26 Verifying : glusterfs-server-3.8.4-5.el6rhs.x86_64 10/26 Verifying : swiftonfile-1.13.1-9.el6rhs.noarch 11/26 Verifying : glusterfs-3.8.4-5.el6rhs.x86_64 12/26 Verifying : glusterfs-cli-3.8.4-5.el6rhs.x86_64 13/26 Verifying : glusterfs-server-3.7.9-12.el6rhs.x86_64 14/26 Verifying : gluster-nagios-addons-0.2.7-1.el6rhs.x86_64 15/26 Verifying : swiftonfile-1.13.1-8.el6rhs.noarch 16/26 Verifying : redhat-storage-server-3.1.3.0-3.el6rhs.noarch 17/26 Verifying : glusterfs-3.7.9-12.el6rhs.x86_64 18/26 Verifying : glusterfs-api-3.7.9-12.el6rhs.x86_64 19/26 Verifying : glusterfs-geo-replication-3.7.9-12.el6rhs.x86_64 20/26 Verifying : glusterfs-libs-3.7.9-12.el6rhs.x86_64 21/26 Verifying : glusterfs-rdma-3.7.9-12.el6rhs.x86_64 22/26 Verifying : glusterfs-fuse-3.7.9-12.el6rhs.x86_64 23/26 Verifying : glusterfs-cli-3.7.9-12.el6rhs.x86_64 24/26 Verifying : glusterfs-client-xlators-3.7.9-12.el6rhs.x86_64 25/26 Verifying : python-gluster-3.7.9-12.el6rhs.noarch 26/26 Updated: gluster-nagios-addons.x86_64 0:0.2.8-1.el6rhs glusterfs.x86_64 0:3.8.4-5.el6rhs glusterfs-api.x86_64 0:3.8.4-5.el6rhs glusterfs-cli.x86_64 0:3.8.4-5.el6rhs glusterfs-client-xlators.x86_64 0:3.8.4-5.el6rhs glusterfs-fuse.x86_64 0:3.8.4-5.el6rhs glusterfs-geo-replication.x86_64 0:3.8.4-5.el6rhs glusterfs-libs.x86_64 0:3.8.4-5.el6rhs glusterfs-rdma.x86_64 0:3.8.4-5.el6rhs glusterfs-server.x86_64 0:3.8.4-5.el6rhs python-gluster.noarch 0:3.8.4-5.el6rhs redhat-storage-server.noarch 0:3.2.0.1-1.el6rhs swiftonfile.noarch 0:1.13.1-9.el6rhs Complete! [root@dhcp47-131 3.2]# [root@dhcp47-131 3.2]# Expected results: No warnignmessage should appear while updating rpms. Additional info: [root@dhcp47-131 3.2]# ls gdeploy-2.0.1-3.el6rhs.noarch.rpm glusterfs-ganesha-3.8.4-5.el6rhs.x86_64.rpm glusterfs-3.8.4-5.el6rhs.x86_64.rpm glusterfs-geo-replication-3.8.4-5.el6rhs.x86_64.rpm glusterfs-api-3.8.4-5.el6rhs.x86_64.rpm glusterfs-libs-3.8.4-5.el6rhs.x86_64.rpm glusterfs-api-devel-3.8.4-5.el6rhs.x86_64.rpm glusterfs-rdma-3.8.4-5.el6rhs.x86_64.rpm glusterfs-cli-3.8.4-5.el6rhs.x86_64.rpm glusterfs-server-3.8.4-5.el6rhs.x86_64.rpm glusterfs-client-xlators-3.8.4-5.el6rhs.x86_64.rpm gluster-nagios-addons-0.2.8-1.el6rhs.x86_64.rpm glusterfs-devel-3.8.4-5.el6rhs.x86_64.rpm python-gluster-3.8.4-5.el6rhs.noarch.rpm glusterfs-events-3.8.4-5.el6rhs.x86_64.rpm redhat-storage-server-3.2.0.1-1.el6rhs.noarch.rpm glusterfs-fuse-3.8.4-5.el6rhs.x86_64.rpm swiftonfile-1.13.1-9.el6rhs.noarch.rpm [root@dhcp47-131 3.2]#
Please retry upgrade with the following command: # yum --verbose --rpmverbosity=debug *.rpm Since the default debug level is 'info', it doesn't help to identify what part of the scriptlet exactly failed.
Some info about this issue: This warning message will come when we try to update packages without stopping glusterd, as per the installation guide we ask CUS to stop all gluster processes before starting update. More details are can be found in the BZ-https://bugzilla.redhat.com/show_bug.cgi?id=1378316
Byreddy, I haven't started the glusterd services. its a fresh setup with no volumes. i just installed 3.1.3 and upgraded to 3.8.4.5 without starting any services. Millind, I'll do with the same steps mentioned in the comment 2 and update the bug. Thanks & regards Karan Sandha
Created attachment 1222300 [details] as per comment 2
Karan, Looks like the post-install scriptlet for glusterfs-server returned a 0 this time as per attachment 1222300 [details]. If the issue was as described by Byreddy in comment #2, then there's not much to be looked into. Else, you need to reproduce the issue while running "yum upgrade" in debug mode.
Milind, I'll check again and report you back. Thanks & regards Karan Sandha
As per comment 8 Closing this bug, feel free to reopen if the issue reappears.
Reopening this BZ. I was able to reproduce this issue with debug flag as per Comment 2. I hit this while updating from RHEL 6.8+ 3.1.3 --> RHEL 6.9+ 3.2.0. D: +++ h# 929 Header SHA1 digest: OK (2ff7e0bcfe854bea7372064bdafba9c45f1bdf8e) D: adding "glusterfs-server" to Name index. D: adding 137 entries to Basenames index. D: adding "System Environment/Daemons" to Group index. D: adding 83 entries to Requirename index. D: adding 3 entries to Providename index. D: adding 45 entries to Dirnames index. D: adding 83 entries to Requireversion index. D: adding 3 entries to Provideversion index. D: adding 1 entries to Installtid index. D: adding 1 entries to Sigmd5 index. D: adding "2ff7e0bcfe854bea7372064bdafba9c45f1bdf8e" to Sha1header index. D: adding 137 entries to Filedigests index. D: install: %post(glusterfs-server-3.8.4-15.el6rhs.x86_64) scriptlet start D: install: %post(glusterfs-server-3.8.4-15.el6rhs.x86_64) execv(/bin/sh) pid 8565 + /sbin/chkconfig --add glusterd + '[' -f /var/log/glusterfs/.cmd_log_history ']' + '[' -d /etc/glusterd -a '!' -h /var/lib/glusterd ']' + '[' -d /var/lib/glusterd/vols ']' ++ find /var/lib/glusterd/vols -name '*.vol' + '[' -e /etc/ld.so.conf.d/glusterfs.conf ']' + pidof -c -o %PPID -x glusterd + '[' 0 -eq 0 ']' ++ pgrep -f gsyncd.py + kill -9 + killall --wait glusterd + glusterd --xlator-option '*.upgrade=on' -N + rm -rf /var/run/glusterd.socket + /sbin/service glusterd start D: install: waitpid(8565) rc 8565 status 100 secs 3.219 warning: %post(glusterfs-server-3.8.4-15.el6rhs.x86_64) scriptlet failed, exit status 1 Non-fatal POSTIN scriptlet failure in rpm package glusterfs-server-3.8.4-15.el6rhs.x86_64 Updating : mdadm-3.3.4-8.el6.x86_64 [########################################## ] 143/418XZDIO: 101 reads, 826836 total bytes in 0.079985 secs Updating : mdadm-3.3.4-8.el6.x86_64 143/418 D: ========== +++ mdadm-3.3.4-8.el6 x86_64-linux 0x2 D: Expected size: 356660 = lead(96)+sigs(1284)+pad(4)+data(355276) D: Actual size: 356660 D: mdadm-3.3.4-8.el6.x86_64: Header V3 RSA/SHA256 Signature, key ID fd431d51: OK D: install: mdadm-3.3.4-8.el6 has 19 files, test = 0 D: ========== Directories not explicitly included in package: D: 0 /etc/cron.d/ D: 1 /etc/rc.d/init.d/ D: 2 /etc/sysconfig/ D: 3 /lib/udev/rules.d/ D: 4 /sbin/ D: 5 /usr/sbin/ D: 6 /usr/share/doc/ D: 8 /usr/share/man/man4/ D: 9 /usr/share/man/man5/ D: 10 /usr/share/man/man8/ D: 11 /var/run/ D: ========== D: fini 100600 1 ( 0, 0) 108 /etc/cron.d/raid-check;58b974be D: fini 100755 1 ( 0, 0) 2571 /etc/rc.d/init.d/mdmonitor;58b974be D: fini 100644 1 ( 0, 0) 2585 /etc/sysconfig/raid-check;58b974be D: fini 100644 1 ( 0, 0) 2751 /lib/udev/rules.d/65-md-incremental.rules;58b974be D: fini 100755 1 ( 0, 0) 479920 /sbin/mdadm;58b974be D: fini 100755 1 ( 0, 0) 230992 /sbin/mdmon;58b974be D: fini 100755 1 ( 0, 0) 3793 /usr/sbin/raid-check;58b974be D: fini 040755 2 ( 0, 0) 0 /usr/share/doc/mdadm-3.3.4 D: fini 100644 1 ( 0, 0) 18092 /usr/share/doc/mdadm-3.3.4/COPYING;58b974be D: fini 100644 1 ( 0, 0) 14814 /usr/share/doc/mdadm-3.3.4/ChangeLog;58b974be D: fini 100644 1 ( 0, 0) 7191 /usr/share/doc/mdadm-3.3.4/TODO;58b974be D: fini 100644 1 ( 0, 0) 2687 /usr/share/doc/mdadm-3.3.4/mdadm.conf-example;58b974be D: fini 100644 1 ( 0, 0) 3565 /usr/share/doc/mdadm-3.3.4/mdcheck;58b974be D: fini 100644 1 ( 0, 0) 550 /usr/share/doc/mdadm-3.3.4/syslog-events;58b974be D: fini 100644 1 ( 0, 0) 13591 /usr/share/man/man4/md.4.gz;58b974be D: fini 100644 1 ( 0, 0) 6539 /usr/share/man/man5/mdadm.conf.5.gz;58b974be D: fini 100644 1 ( 0, 0) 31064 /usr/share/man/man8/mdadm.8.gz;58b974be D: fini 100644 1 ( 0, 0) 3183 /usr/share/man/man8/mdmon.8.gz;58b974be D: fini 040700 2 ( 0, 0) 0 /var/run/mdadm D: +++ h# 930 Header V3 RSA/SHA256 Signature, key ID fd431d51: OK
Created attachment 1259572 [details] Yum update with debug flag complete output
In this run, the PID of gsyncd.py wasn't found. So the argument to the kill -9 command was empty. + kill -9 ----- Looks like there wasn't any geo-replication active on the system since gsyncd.py is a geo-replication artifact. Could you confirm if geo-replication for any volume was running at the time the "yum update" was attempted ?
(In reply to Milind Changire from comment #12) > In this run, the PID of gsyncd.py wasn't found. So the argument to the kill > -9 command was empty. > > + kill -9 > > ----- > > Looks like there wasn't any geo-replication active on the system since > gsyncd.py is a geo-replication artifact. Could you confirm if > geo-replication for any volume was running at the time the "yum update" was > attempted No volumes were present at the time of upgrade. I have just created a 3.1.3 setup and without creating any volume or running any services performed upgrade to 3.2.0.
Not much demand to have it in release since last 2 years, not in in upgrades in recent 3 releases. Closing as WORKSFORME.