[pod, feature, b1] Enable console logging to disk by default on KVM Pod VM's.
Bug #1713556 reported by
Jason Hobbs
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Low
|
Newell Jensen |
Bug Description
Sometimes console output is required to debug issues (see bug 1707999). MAAS should configure VMs it creates to log console output to disk, otherwise console output is ephemeral and can't be collected for debug.
Related branches
~newell-jensen/maas:lp1713556
Merged
into
maas:master
- MAAS Lander: Needs Fixing
- Mike Pontillo (community): Approve
- Andres Rodriguez (community): Approve
-
Diff: 297 lines (+164/-4)4 files modifiedsrc/maasserver/api/pods.py (+5/-0)
src/maasserver/api/tests/test_pods.py (+107/-1)
src/maasserver/forms/pods.py (+44/-1)
src/provisioningserver/drivers/pod/virsh.py (+8/-2)
summary: |
- [FeatureRequest] Log console by default on MAAS created VMs + [FeatureRequest] Enable console by default on KVM Pod VM's. |
summary: |
- [FeatureRequest] Enable console by default on KVM Pod VM's. + [FeatureRequest] Enable console logging to disk by default on KVM Pod + VM's. |
Changed in maas: | |
importance: | Undecided → Low |
status: | New → Triaged |
milestone: | 2.4.x → 2.4.0alpha1 |
Changed in maas: | |
milestone: | 2.4.0alpha1 → 2.4.0alpha2 |
Changed in maas: | |
milestone: | 2.4.0alpha2 → 2.4.x |
Changed in maas: | |
assignee: | nobody → Newell Jensen (newell-jensen) |
summary: |
- [FeatureRequest] Enable console logging to disk by default on KVM Pod - VM's. + [pod, FeatureRequest] Enable console logging to disk by default on KVM + Pod VM's. |
Changed in maas: | |
milestone: | 2.4.x → 2.4.0beta1 |
summary: |
- [pod, FeatureRequest] Enable console logging to disk by default on KVM - Pod VM's. + [pod, feature, b1] Enable console logging to disk by default on KVM Pod + VM's. |
Changed in maas: | |
milestone: | 2.4.0beta1 → 2.4.0beta2 |
Changed in maas: | |
milestone: | 2.4.0beta2 → 2.4.0beta3 |
Changed in maas: | |
status: | Triaged → In Progress |
status: | In Progress → Triaged |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Triaged |
Changed in maas: | |
milestone: | 2.4.0beta3 → 2.4.0beta4 |
Changed in maas: | |
milestone: | 2.4.0beta4 → 2.4.x |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
milestone: | 2.4.x → 2.5.0beta2 |
tags: | added: sprint track |
Changed in maas: | |
status: | In Progress → Triaged |
Changed in maas: | |
milestone: | 2.5.0beta2 → 2.5.0rc1 |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | 2.5.0rc1 → 2.5.0beta4 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Marking this as duplicate of #1688066 (although it is probably invalid).
MAAS creates VM's with console logging, but you need to add console=ttyS0 to the kernel command line. What you are looking for is probably spice, wich is why I duplicated this bug.