`juju run` becomes unresponsive in consecutive runs when previous command passed is `tail -f`
Bug #1640938 reported by
Dean Maniatis
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
| 2.0 |
Won't Fix
|
Undecided
|
Unassigned | ||
| 2.1 |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
I have observed the following strange behavior when trying to debug my LXD bootstrapped node. When using juju run -m controller --machine 0 "tail -f /var/log/
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.1.0 |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| Changed in juju: | |
| importance: | High → Medium |
| milestone: | 2.1-rc2 → none |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
I am seeing this as well: bootstrapped Juju 2.1-rc2 on AWS.
I will mark it as Won't Fix for 2.0 and 2.1. We may address this in future releases.
@Dean,
If you are after the logging activity, check out 'juju help debug-log'.