cloud-init output not redirected to a file
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Undecided
|
Unassigned | ||
| 1.2 |
Won't Fix
|
Wishlist
|
Unassigned | ||
| 1.4 |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
When debugging an enlistment, commissionig or curtin install, output of programs run by cloud-init is important.
By default in ubuntu images < 14.04, output of commands cloud-init runs go only to /dev/console.
since it seems quite common that we do not log a nodes /dev/console, the next best option is getting /var/log/
Right now it seems we're only doing that for enlistment.
We need to make sure that the following cloud-config is passed into cloud-init in commissioning and curtin stages:
output: {all: '| tee -a /var/log/
This is less ideal than collecting consoles as /var/log/ will be on the tmpfs and thus writes will consume real memory.
This is the shorter path to somethign sane than getting cloud-init output going to rsyslog and back to maas.
| summary: |
- maas should redirect cloud-init output to file whenever possible + cloud-init output not redirected to a file |
| Changed in maas: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| Julian Edwards (julian-edwards) wrote | #1 |
| Scott Moser (smoser) wrote | #2 |
| Changed in maas: | |
| status: | Triaged → Invalid |
| importance: | Wishlist → Undecided |
| Scott Moser (smoser) wrote | #3 |
> By default in ubuntu images < 14.04, output of commands cloud-init runs go only to /dev/console
Is this another way of saying that this doesn't/won't happen in 14.04 when released?