lxc container tests
Bug #1192587 reported by
Barry Warsaw
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu system image |
Won't Fix
|
Wishlist
|
Stéphane Graber | ||
Bug Description
We want to test the full stack (client + updater) in an lxc container, including reboot sequencing.
| Changed in ubuntu-system-image: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: client |
| tags: | added: updater |
| Changed in ubuntu-system-image: | |
| assignee: | nobody → Stéphane Graber (stgraber) |
Revision history for this message
| Barry Warsaw (barry) wrote | #1 |
| Changed in ubuntu-system-image: | |
| importance: | High → Low |
| Changed in ubuntu-system-image: | |
| importance: | Low → Wishlist |
| tags: | added: tech-debt |
Revision history for this message
| Barry Warsaw (barry) wrote | #2 |
| Changed in ubuntu-system-image: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
Once it's possible to test through containers, we'll run the real reboot command: `reboot -f recovery`