Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: =================== on live RHEL 7.5 +RHGS 3.4, I installed colonizer after subscribing to ansible channel However when running colonizer deployment, it is failing with pexpect unavailability as below [root@rhs-client28 oemid]# gluster-colonizer.py -f g1-oemid-kvm-nas.yml Traceback (most recent call last): File "/usr/bin/gluster-colonizer.py", line 50, in <module> import pexpect ImportError: No module named pexpect Previously, when checked about 10 days back(as part of 3.4.0 live testing), I never hit this issue, however hitting it now Version-Release number of selected component (if applicable): rhel 7.5 rhgs 3.4 colonizer-1.2.2 ansible 2.6.4-1 How reproducible: =========== always Steps to Reproduce: 1.install colonizer 2.run a deployment script 3.it fails with pexpect module unavailable Expected results: ----------- pexpect should be installed as part of initial installation as dependency if need be, and deployment should not fail due to this Additional info: ################ [root@rhs-client28 gluster-colonizer]# cd oemid/ [root@rhs-client28 oemid]# gluster-colonizer.py -f g1-oemid-kvm-nas.yml Traceback (most recent call last): File "/usr/bin/gluster-colonizer.py", line 50, in <module> import pexpect ImportError: No module named pexpect [root@rhs-client28 oemid]# yum install pexpect [root@rhs-client28 oemid]# yum install pexpect Loaded plugins: product-id, search-disabled-repos, subscription-manager rh-gluster-3-for-rhel-7-server-rpms | 4.0 kB 00:00:00 rhel-7-server-ansible-2-rpms | 4.0 kB 00:00:00 rhel-7-server-rpms | 3.5 kB 00:00:00 Resolving Dependencies --> Running transaction check ---> Package pexpect.noarch 0:2.3-11.el7 will be installed --> Finished Dependency Resolution Dependencies Resolved ===================================================================================================================== Package Arch Version Repository Size ===================================================================================================================== Installing: pexpect noarch 2.3-11.el7 rhel-7-server-rpms 142 k Transaction Summary ===================================================================================================================== Install 1 Package Total download size: 142 k Installed size: 784 k Is this ok [y/d/N]: y Downloading packages: pexpect-2.3-11.el7.noarch.rpm | 142 kB 00:00:02 Running transaction check Running transaction test Transaction test succeeded Running transaction Installing : pexpect-2.3-11.el7.noarch 1/1 Verifying : pexpect-2.3-11.el7.noarch 1/1 Installed: pexpect.noarch 0:2.3-11.el7 Complete! [root@rhs-client28 oemid]# gluster-colonizer.py -f g1-oemid-kvm-nas.yml ____ __ _______ ____ / __ \/ / / / ___/ / __ \____ ___ / /_/ / /_/ /\__ \ / / / / __ \/ _ \ / _, _/ __ /___/ / / /_/ / / / / __/ /_/ |_/_/ /_//____/ \____/_/ /_/\___/ Welcome to the Red Hat Storage One Gluster deployment tool! This node will be configured as the deployment master for your Gluster storage pool. Before proceeding, please ensure that all RHS One Gluster nodes are connected to the management network infrastructure and are booted. Do you wish to continue? [Y/n] y Begin RHS One Gluster inventory phase Your deployment node type is KVM-node Your deployment flavor is NAS How many RHS One Gluster nodes are you deploying? Number of nodes (valid range is 4-24): Something went wrong and the deployment is being aborted.
Created attachment 1484240 [details] attaching the RPM SPEC file for reference.
I would need the QA and PM_ACK for this.
Created attachment 1486248 [details] gluster-colonizer-1.2-3 spec file
have check this and is working fine on latest 3.4.1 and with subscribing to live ansible. Moving it to verified , but may have to recheck on ISO, if it gets build
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:3465