gluster volume start --xml outputs <cliOutput> <volStart> <flags>0</flags> <volname>test1</volname> </volStart> </cliOutput> expected output is <cliOutput> <opRet>0</opRet> <opErrno>0</opErrno> <opErrstr/> <volStart> <volume> <name>music</name> <id>b3114c71-741b-4c6f-a39e-80384c4ea3cf</id> <status>1</status> </volume> </volStart> </cliOutput>
Patch under review at http://review.gluster.org/3869
Fixed by commit f1f3d1c (cli: Changes and enhancements to XML output) for bug https://bugzilla.redhat.com/show_bug.cgi?id=828131 . Reviewed at http://review.gluster.org/3869 .
Not fixed in upstream [root@localhost x86_64]# gluster volume start music --xml [root@localhost x86_64]# If a volume is in started state, it returns error xml correctly [root@localhost x86_64]# gluster volume start music --xml <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <cliOutput><opRet>-1</opRet><opErrno>0</opErrno><opErrstr>Volume music already started</opErrstr></cliOutput>