Jesus Sanchez wrote: > Hello. > > I am running systemimager 4.0.2-1 on the server side and 4.1.4-1 on the > client side. > > I have one golden node and 11 replicated nodes with an operating image of > openSUSE 10.3. I installed some new software on the golden node and tried to > push the updates to the rest of the nodes using the following command: > > si_pushupdate --ssh-user root --client "pac-node" --range 2-12 --server > pac-master --image "suse-10.3" --updateclient-options "--no-bootloader" > > but I get the following error: > > "Option image requires an argument" > > I have also trid without the quotes but the error message is exactly the same. > > Finally I decided to do it without the range option using the following > command: > > si_pushupdate --ssh-user root --client "pac-node2" --server pac-master > --image > "suse-10.3" --updateclient-options "--no-bootloader" > > When I launched it I did not have any output so I decided to click 'Enter' > and that's what I got: > > pac-master:~ # si_pushupdate --ssh-user root --client "pac-node2" --server > pac-master --image "suse-10.3" --updateclient-options "--no-bootloader" > > ======================= WARNING ================================= > This command will update this host with the image: suse-10.3 > and overrides (in order of importance): > > > > Some files could be deleted or overwritten, so probably it is a > good idea to run this command with --dry-run before and stop the > production on this host. > ======================= WARNING ================================= > > Are you sure to continue? (y / N)? Noting has not been modified... > > pac-master:~ # > > Finally I launched it the same way but clicking 'y' instead of 'Enter' and > then I managed to update the nodes. > > I wonder whether it is the expected way to work for si_pushupdate or if it > is > a bug. Or probably I am not using it properly, which obviously I would like > to > know because now that we have the cluster running again with the same image > running on nodes from two different generations this is the most common > operation that we perform. > > Many thanks. > > jesus sanchez.- >
Jesus, si_pushupdate has been completely rewritten in 4.1.x branch and it'll be backported in the stable 4.0.x branch ASAP. For now, if you don't want to move to 4.1.6 on the server side, I would suggest to just use si_psh and si_updateclient. The following command should work: si_psh -n "pac\-node2-pac\-node12" "si_updateclient --server pac-master --yes" -Andrea ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
