-
Notifications
You must be signed in to change notification settings - Fork 541
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sos collect in Juju environment #3399
Labels
Good First Issue
This is a good issue for a first time contributor
Comments
I've also tried:
but I get
|
arif-ali
added
the
Good First Issue
This is a good issue for a first time contributor
label
Oct 30, 2023
This has been confirmed as an issue with sos collect for juju, when we use newer juju releases. Thanks for reporting this. Will debug on what is going on, when will look towards a fix |
arif-ali
added a commit
to arif-ali/sos
that referenced
this issue
Oct 30, 2023
New version of juju uses colorisation, and therefore juju status and json.loads doesn't load the juju status correctly. By using --no-color based on the version of juju this should this particular use-case Resolves: sosreport#3399 Resolves: SET-339 Signed-off-by: Arif Ali <arif.ali@canonical.com>
5 tasks
arif-ali
added a commit
to arif-ali/sos
that referenced
this issue
Oct 30, 2023
New version of juju uses colorisation, and therefore juju status and json.loads doesn't load the juju status correctly. By using --no-color based on the version of juju this should this particular use-case Resolves: sosreport#3399 Resolves: SET-339 Signed-off-by: Arif Ali <arif.ali@canonical.com>
arif-ali
added a commit
to arif-ali/sos
that referenced
this issue
Oct 31, 2023
New version of juju uses colorisation, and therefore juju status and json.loads doesn't load the juju status correctly. By using --no-color based on the version of juju this should this particular use-case Resolves: sosreport#3399 Resolves: SET-339 Signed-off-by: Arif Ali <arif.ali@canonical.com>
TurboTurtle
added a commit
to TurboTurtle/sos
that referenced
this issue
Nov 3, 2023
The `get_pty` parameter for remote executed commands was both a bit of a misnomer and applied too broadly. Refactor this to `use_shell` to be more obvious about what the intent behind the option is, and default all transports to `False`, so that by default we do not wrap any commands in a bash shell. This may be overriden on a per-transport basis via the ned `_need_shell` property within transport subclasses. Further, this facility has been expanded to be allowed on a per-command basis from `SoSNode.run_command()` and wherever that is linked. Related: sosreport#3399 Related: sosreport#3400 Signed-off-by: Jake Hunsaker <jacob.r.hunsaker@gmail.com>
5 tasks
TurboTurtle
added a commit
that referenced
this issue
Nov 7, 2023
The `get_pty` parameter for remote executed commands was both a bit of a misnomer and applied too broadly. Refactor this to `use_shell` to be more obvious about what the intent behind the option is, and default all transports to `False`, so that by default we do not wrap any commands in a bash shell. This may be overriden on a per-transport basis via the ned `_need_shell` property within transport subclasses. Further, this facility has been expanded to be allowed on a per-command basis from `SoSNode.run_command()` and wherever that is linked. Related: #3399 Related: #3400 Signed-off-by: Jake Hunsaker <jacob.r.hunsaker@gmail.com>
arif-ali
added a commit
to arif-ali/sos
that referenced
this issue
Nov 7, 2023
New version of juju uses colorisation, and therefore juju status and json.loads doesn't load the juju status correctly. By using --no-color based on the version of juju this should this particular use-case Resolves: sosreport#3399 Resolves: SET-339 Signed-off-by: Arif Ali <arif.ali@canonical.com>
arif-ali
added a commit
to arif-ali/sos
that referenced
this issue
Nov 9, 2023
New version of juju uses colorisation, and therefore juju status and json.loads doesn't load the juju status correctly. By using --no-color based on the version of juju this should fix this particular use-case Resolves: sosreport#3399 Resolves: SET-339 Signed-off-by: Arif Ali <arif.ali@canonical.com>
TurboTurtle
pushed a commit
that referenced
this issue
Nov 16, 2023
New version of juju uses colorisation, and therefore juju status and json.loads doesn't load the juju status correctly. By using --no-color based on the version of juju this should fix this particular use-case Resolves: #3399 Resolves: SET-339 Signed-off-by: Arif Ali <arif.ali@canonical.com>
arif-ali
added a commit
to arif-ali/sos
that referenced
this issue
Nov 24, 2023
With juju versions 3 and above, when collecting the tarballs from machines it will grab them into a strictly confined area. This means that we need to be able to access this area via sudo. In order for this now to be fully supported, we need sudo on the host that is running juju, otherwise sos collect on a juju environment will not work. Related: sosreport#3399 Signed-off-by: Arif Ali <arif.ali@canonical.com>
5 tasks
arif-ali
added a commit
to arif-ali/sos
that referenced
this issue
Nov 24, 2023
With juju versions 3 and above, when collecting the tarballs from machines it will grab them into a strictly confined area. This means that we need to be able to access this area via sudo. In order for this now to be fully supported, we need sudo on the host that is running juju, otherwise sos collect on a juju environment will not work. Related: sosreport#3399 Signed-off-by: Arif Ali <arif.ali@canonical.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi sos team,
I'm trying to use sos collect in a juju environment. I see there is this pull request and this issue so I believe the integration with Juju is implemented? But I'm struggling to get it working.
I'm using:
I have a Juju deployed environment. For example, and have tried something like:
and
authenticates me into the unit. But from the same host (that I used
juju ssh vault/0
from) I can't seem to figure out how to use sos collect. I've tried the following:and other options/combinations but I keep getting the following:
I'm missing something? How do I collect from vault units? Any pointers would be greatly appreciated.
Thanks in advance!
The text was updated successfully, but these errors were encountered: