strange behaviour when factorizing (new '0' issue with nodeset) #293
Description
Hi,
Recently I had some issue with factorization (#288 which was a duplicated of #286) which I fixed by installing the last version (from master branch). It fixed my issue.
I have now a new one (after eating my '0', it's adding an extra '0'):
$ cat liste_failed_for_clush firstgroupa001 firstgroupa002 secondgroup001 secondgroup002 secondgroup003 secondgroup005 secondgroup006 secondgroup008 namewithissue007 namewithissue008 namewithissue009 namewithissue01 namewithissue02 namewithissue03 namewithissue04 namewithissue10 $ paste -sd, liste_failed_for_clush | nodeset -f firstgroupa[001-002],namewithissue[001-004,007-010],secondgroup[001-003,005-006,008] It is adding a 0 to the last five servers!
namewithissue[001-004,007-010] should be namewithissue[01-04,10],namewithissue[007-009]
If the servers are not in the same order (starting with 2 digits server's name instead of the 3 digits one):
$ cat liste_failed_for_clush2 namewithissue01 namewithissue02 namewithissue03 namewithissue04 namewithissue10 firstgroupa001 firstgroupa002 secondgroup001 secondgroup002 secondgroup003 secondgroup005 secondgroup006 secondgroup008 namewithissue007 namewithissue008 namewithissue009 $ paste -sd, liste_failed_for_clush2 | nodeset -f firstgroupa[001-002],namewithissue[01-04,07-10],secondgroup[001-003,005-006,008] This time, it's eating a '0'.
As I saw the last version was released (which should be the same I installed 10 days before), I installed it instead, and it is the same behaviour
$ rpm -qa | grep clustershell clustershell-1.7.1-1.el6.noarch $ /usr/bin/nodeset --version nodeset 1.7.1 I even try to rollback to my initial version (1.7-1, and it is the same).
Is it a new bug?
Thanks