[2.6] Event long doesn't provide a cue that allows users to see start of an action
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Triaged
|
Critical
|
Newell Jensen | ||
Bug Description
The deployment process is like this:
Sat, 27 Apr. 2019 20:22:37 Marking node failed - Internal error while creating KVM pod. (See regiond.log for details.)
Sat, 27 Apr. 2019 20:20:07 Rebooting
Sat, 27 Apr. 2019 20:18:58 Configuring OS
Sat, 27 Apr. 2019 20:18:33 Installing OS
Sat, 27 Apr. 2019 20:18:23 Configuring storage
Sat, 27 Apr. 2019 20:17:51 Loading ephemeral
Sat, 27 Apr. 2019 20:17:34 Performing PXE boot
Sat, 27 Apr. 2019 20:16:40 Powering on
Sat, 27 Apr. 2019 20:11:35 Loading ephemeral
Sat, 27 Apr. 2019 20:11:18 Performing PXE boot
Sat, 27 Apr. 2019 20:10:24 Power cycling
There should be a cue that tells the user what's gonna happen as by looking at this, it doesn't really show what's actually happening:
Sat, 27 Apr. 2019 20:10:24 Starting the deployment of Ubuntu 18.04
| Changed in maas: | |
| milestone: | none → 2.6.0beta2 |
| importance: | Undecided → High |
| status: | New → Triaged |
| assignee: | nobody → Newell Jensen (newell-jensen) |
| Changed in maas: | |
| milestone: | 2.6.0beta2 → 2.6.0rc1 |
| Andres Rodriguez (andreserl) wrote | #1 |
| Changed in maas: | |
| importance: | High → Critical |
In this example, the machine deployed, after deployed we entered rescue mode, and then we exited rescue mode. This actiosn should be in the INFO and not only debug.
Sat, 27 Apr. 2019 21:37:28 Power cycling
Sat, 27 Apr. 2019 21:36:13 Loading ephemeral
Sat, 27 Apr. 2019 21:35:57 Performing PXE boot
Sat, 27 Apr. 2019 21:34:55 Power cycling
Sat, 27 Apr. 2019 21:27:58 Rebooting
Sat, 27 Apr. 2019 21:26:50 Configuring OS
Sat, 27 Apr. 2019 21:26:25 Installing OS
Sat, 27 Apr. 2019 21:26:15 Configuring storage
Sat, 27 Apr. 2019 21:25:42 Loading ephemeral
Sat, 27 Apr. 2019 21:25:25 Performing PXE boot