Skip to content
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

juju run --all usage prevents juju-crashdump from working with blocked hooks #28

Open
dshcherb opened this issue Jan 20, 2019 · 1 comment

Comments

@dshcherb
Copy link
Contributor

juju run command is equivalent to a hook execution which makes this command hang if a hook is blocked on something and does not progress forward (meaning that a child process of a unit agent never exits).

Avoiding juju run and iterating over all units via juju ssh should be considered instead.

@jhobbs
Copy link
Contributor

jhobbs commented Jun 18, 2019

This also causes issues when a machine agent is down.

marosg42 added a commit to marosg42/juju-crashdump that referenced this issue Jul 23, 2019
When unit is in error or blocked state juju run will not connect.
Using ssh instead allows to collect data regardless of juju agent
status.

solves juju#28 amd juju#26
marosg42 added a commit to marosg42/juju-crashdump that referenced this issue Jul 23, 2019
When unit is in error or blocked state juju run will not connect.
Using ssh instead allows to collect data regardless of juju agent
status.

solves juju#28 amd juju#26
marosg42 added a commit to marosg42/juju-crashdump that referenced this issue Jul 23, 2019
When unit is in error or blocked state juju run will not connect.
Using ssh instead allows to collect data regardless of juju agent
status.

solves juju#28 amd juju#26
marosg42 added a commit to marosg42/juju-crashdump that referenced this issue Jul 23, 2019
When unit is in error or blocked state juju run will not connect.
Using ssh instead allows to collect data regardless of juju agent
status.

solves juju#28 amd juju#26
marosg42 added a commit to marosg42/juju-crashdump that referenced this issue Jul 23, 2019
When unit is in error or blocked state juju run will not connect.
Using ssh instead allows to collect data regardless of juju agent
status.

solves juju#28 amd juju#26
marosg42 added a commit to marosg42/juju-crashdump that referenced this issue Jul 25, 2019
When unit is in error or blocked state juju run will not connect.
Using ssh instead allows to collect data regardless of juju agent
status.

solves juju#28 amd juju#26
marosg42 added a commit to marosg42/juju-crashdump that referenced this issue Aug 20, 2019
When unit is in error or blocked state juju run will not connect.
Using ssh instead allows to collect data regardless of juju agent
status.

solves juju#28 amd juju#26
marosg42 added a commit to marosg42/juju-crashdump that referenced this issue Aug 20, 2019
When unit is in error or blocked state juju run will not connect.
Using ssh instead allows to collect data regardless of juju agent
status.

solves juju#28 amd juju#26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants