Description of problem: ===================== In a effort to make the cli more organised, we had some fixes, where all tiering commands will come under "gluster v tier" But with this all the expected o/p errors/messages have not be updated accordinly wrt to the older cli. There is a disparity on the older cli o/p and new cli o/p We need to have this fixed, as it will lead to unncessary regressions both from feature perspective and for automation cases. Following are the examples(there are more): ========================== 1)detach tier status on non tier volume old: [root@zod distrep]# gluster v detach-tier clitest status volume detach-tier status: failed: volume clitest is not a tier volume. Tier command failed New: [root@zod distrep]# gluster v tier clitest detach status Node Rebalanced-files size scanned failures skipped status run time in secs --------- ----------- ----------- ----------- ----------- ----------- ------------ -------------- 2)detach tier stop on non tier volume: old: [root@zod distrep]# gluster v detach-tier clitest stop volume detach-tier stop: failed: volume clitest is not a tier volume. Tier command failed new: [root@zod distrep]# gluster v tier clitest detach stop Node Rebalanced-files size scanned failures skipped status run time in secs --------- ----------- ----------- ----------- ----------- ----------- ------------ -------------- 'detach-tier' process may be in the middle of a file migration. The process will be fully stopped once the migration of the file is complete. Version-Release number of selected component (if applicable): ============================== [root@zod distrep]# rpm -qa|grep gluster glusterfs-libs-3.7.5-6.el7rhgs.x86_64 glusterfs-fuse-3.7.5-6.el7rhgs.x86_64 glusterfs-3.7.5-6.el7rhgs.x86_64 glusterfs-server-3.7.5-6.el7rhgs.x86_64 glusterfs-client-xlators-3.7.5-6.el7rhgs.x86_64 glusterfs-cli-3.7.5-6.el7rhgs.x86_64 glusterfs-api-3.7.5-6.el7rhgs.x86_64 glusterfs-debuginfo-3.7.5-6.el7rhgs.x86_64 NOTE:Kindly analyze all the possible options in new cli and change them accordingly
we need to take care of the parity like bug#1279350, which was fixed, but cannot be said that it is validated against new cli as the o/p is different
https://code.engineering.redhat.com/gerrit/63889
Tested and verified this on the build glusterfs-3.7.5-12.el7rhgs.x86_64 Mapped the commands and the corresponding outputs of: 'gluster v tier attach/detach' alongside 'gluster v tier-attach' and 'gluster v tier-detach' at various stages of tier lifecycles and found them to be similar. Moving the present bug to verified in 3.1.2. Detailed logs are attached.
Created attachment 1107976 [details] server logs
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://rhn.redhat.com/errata/RHBA-2016-0193.html