Description of problem: ======================= In latest 3.2.0 RHGS ISO, the gluster-deploy script provided at /usr/lib/glusterfs/.unsupported is not appropriate with the current release version. The current gdeploy version running with the iso is gdeploy-2.0.1-8.el6rhs.noarch but the gdeploy script provided at /usr/lib/glusterfs/.unsupported is having a very older version i.e gluster-deploy-0.8. drwxr-xr-x. 7 root root 4096 Feb 2 01:42 gluster-deploy-0.8 Seems like this gluster-deploy directory is not being used for any purpose as the directory was not updated since a long time. In that case the directory "gluster-deploy-0.8" can be removed from the iso to reduce the size of iso. If purposefully the gdeploy script is placed then it has to be updated with the latest version. Version-Release number of selected component (if applicable): 3.8.4-13.el6rhs.x86_64 RHGS ISO location: ================== RHGS-3.2-RHEL-6.8-z : http://download-node-02.eng.bos.redhat.com/nightly/RHGS/3.2/RHGSS-3.2-RHEL-6-20170130.n.1/compose/RHGSS/x86_64/iso/RHGSS-3.2-RHEL-6-20170130.n.1-RHGSS-x86_64-dvd1.iso RHGS-3.2-RHEL-7.3-z : http://download-node-02.eng.bos.redhat.com/nightly/RHGS/3.2/RHGSS-3.2-RHEL-7-20170131.n.0/compose/RHGSS/x86_64/iso/RHGSS-3.2-RHEL-7-20170131.n.0-RHGSS-x86_64-dvd1.iso
Hi Milind, I see you moving the assignee to rhs-bugs, but without telling what is required to be done to resolve this bug. Can you update what we have to do to resolve the bug? If there is nothing from Engineering, then it would be good to CLOSE the bug (with relevant reason, can even be WONTFIX).
I'm not sure if gluster-deploy is the same as gdeploy. If they are the same, then we need to remove gluster-deploy from redhat-storage-server RPM. @Sac: are they the same ?
(In reply to Milind Changire from comment #6) > I'm not sure if gluster-deploy is the same as gdeploy. > If they are the same, then we need to remove gluster-deploy from > redhat-storage-server RPM. > > @Sac: are they the same ? They are not same, this was a script shipped a long time back. I'm not sure if anyone used it at all. We can remove it and take the bug to closure.