Upgrading introduces a spurious cluster controller
Bug #1381058 reported by
Adam Collard
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Won't Fix
|
Undecided
|
Unassigned | ||
| maas (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
Upgrading from 1.7.0~beta5+
Cluster 9d39d468-
Cluster master [Warning: this cluster is disconnected.]
Revision history for this message
| Raphaël Badin (rvb) wrote | #1 |
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #2 |
| Changed in maas: | |
| status: | New → Incomplete |
| Changed in maas (Ubuntu): | |
| status: | New → Incomplete |
| Changed in maas: | |
| milestone: | none → 1.7.0 |
| Changed in maas: | |
| milestone: | 1.7.0 → 1.7.1 |
| Changed in maas: | |
| milestone: | 1.7.1 → 1.7.2 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in maas (Ubuntu): | |
| status: | Incomplete → Expired |
| Changed in maas: | |
| milestone: | 1.7.2 → 1.7.3 |
| Changed in maas: | |
| status: | Incomplete → Won't Fix |
To post a comment you must log in.
I can't reproduce this so far, I've upgraded from 1.7.0~beta5+
You said on IRC the upgrade wasn't smooth… can you describe what happened exactly?