Using sdcadm 1.12.0 (release-20161027-20161027T013125Z-gb4c58fe), running the following command
sdcadm experimental update dockerlogger --servers=44454c4c-4400-1033-8052-c6c04f323253,44454c4c-4800-1036-8054-b1c04f423253,44454c4c-5800-1057-8039-b6c04f433253
errors because one server in the Triton deployment (that is not listed on the --servers argument) is down. It appears that the argument is not being honoured because I see the following in the output:
This update will make the following changes:
update "dockerlogger" service to image cbd0dae6-80cb-45a0-a6cf-30f2135358dd
dockerlogger@1.0.0-release-20161110-20161110T014419Z-g3abcf86
in all the setup servers
i.e. the " in all the setup servers" on the last line
A full gist output is available here
Using sdcadm 1.12.0 (release-20161027-20161027T013125Z-gb4c58fe), running the following command
errors because one server in the Triton deployment (that is not listed on the --servers argument) is down. It appears that the argument is not being honoured because I see the following in the output:
This update will make the following changes: update "dockerlogger" service to image cbd0dae6-80cb-45a0-a6cf-30f2135358dd dockerlogger@1.0.0-release-20161110-20161110T014419Z-g3abcf86 in all the setup serversi.e. the " in all the setup servers" on the last line
A full gist output is available here