Controllers show different versions when installed with debs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Triaged
|
Low
|
Unassigned |
Bug Description
Hello!
I'm opening this bug report on behalf of the couple of related Discourse posts on the issue[1][2], as I didn't see one having been opened in here. If there already has been, apologies for the duplication and please feel free to close this one.
Folks are seeing the MAAS UI complain about controllers being on different versions incorrectly. As described in [1], it would seem that MAAS is not consistently ignoring the "1:" epoch from the debian package, and considering it a version mismatch. This was supposedly fixed in 3.2, but but has since resurfaced in 3.3.x as evidenced by [2]. That post shows v3.3.1, but I've also seen it reported against 3.3.5 as well.
It's unclear if MAAS will behave any differently if it thinks (erroneously or otherwise) that the controller versions don't match, but it would be nice in any case to see this issue corrected!
Thank you!
[1] https:/
[2] https:/
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Low |
milestone: | none → 3.5.x |
Changed in maas: | |
milestone: | 3.5.x → 3.6.0 |
milestone: | 3.6.0 → 3.6.x |