You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 18, 2021. It is now read-only.
Performing an 'airship install --all' only tries to install the specified software on one server, not all available servers. Doing some packet sniffing it does seem like the Coordinator returns all of the existing servers, but the airship cli must not be handling them correctly.
I have tested this with 3 existing airship agents.
Steps that work for me to reproduce:
Build new environment
Make 3 agent servers
Try to do install --all
My airship cli server is a RHEL 6.x Linux box with the latest JDK from Oracle and I'm running as the root user.
The text was updated successfully, but these errors were encountered:
Thanks for the bug report. The --all argument is actually an agent filter, just like --uuid or --host. It is used the same way that the --all slot filter is used for commands like airship start or airship stop. Those commands require a slot filter, so --all is necessary to select everything.
The install command (and the show command) selects all agents by default, so --all is not necessary. We will remove it from all commands that do not need it to avoid confusion.
You can install on multiple agents by specifying a count like --count 50 and it will install on up to that many agents. If the count is lower than the number of matching agents, then it will arbitrarily pick which ones to install onto.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Performing an 'airship install --all' only tries to install the specified software on one server, not all available servers. Doing some packet sniffing it does seem like the Coordinator returns all of the existing servers, but the airship cli must not be handling them correctly.
I have tested this with 3 existing airship agents.
Steps that work for me to reproduce:
My airship cli server is a RHEL 6.x Linux box with the latest JDK from Oracle and I'm running as the root user.
The text was updated successfully, but these errors were encountered: