MAAS

"Different channel detected" error with an air-gapped deployment

Bug #2017155 reported by Ethan Myers
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Triaged
Medium
Unassigned
MAAS 3.4.x
maas-ui
Triaged
Low
Unassigned
maas-ui 3.4.x

Bug Description

Very similar to https://bugs.launchpad.net/maas/+bug/1961008, but still occurring in 3.2.7 and 3.3.

In this case, I have MAAS installed in an HA config, but I am able to recreate it with single node maas as well. The instructions to recreate are the same as in lp:1961008

my `snap list`:
Name Version Rev Tracking Publisher Notes
core18 20230320 2721 latest/stable canonical base
core20 20230308 1852 latest/stable canonical base
core22 20230325 607 latest/stable canonical base
juju 2.9.42 22345 - canonical classic
juju-crashdump 1.0.2+git120.a838717 266 - jason-hobbs classic
juju-helpers 0.1.1 55 - kennethkoski classic
juju-lint 1.0.6 91 - canonical classic
juju-wait 2.8.4~2.8.4 96 - stub classic
kubectl 1.26.3 2914 - canonical classic
lxd 4.0.9-a29c6f1 24061 4.0/stable/ canonical -
maas 3.2.7-12037-g.c688dd446 26274 - canonical -
maas-cli 0.6.8 79 latest/stable canonical -
openstackclients yoga 338 - canonical -
snapd 2.58.3 18596 latest/stable canonical snapd

All controllers are in an unhealthy state with the error message 'Different channel detected'.

See original description
Adam Collard (adam-collard)
description: updated
Revision history for this message
Alberto Donato (ack) wrote :

Testing with 3.3.2 and a single controller, I get the following error message in the popup: "Different missing-channel detected."

The same happens if the machine is not airgapped, but the snap was installed manually as described in lp:1961008

Backend is reporting "missing-channel" in version issues, which is correct. I think the UI message is a bit confusing, though.

Changed in maas:
milestone: none → 3.4.0
Alberto Donato (ack)
Changed in maas:
importance: Undecided → Medium
Alberto Donato (ack)
Changed in maas:
status: New → Triaged
Changed in maas-ui:
milestone: none → 3.4.0
Alberto Donato (ack)
Changed in maas:
milestone: 3.4.0 → 3.4.x
Revision history for this message
Thorsten Merten (thorsten-merten) wrote :

What message would be appropriate to show in the UI?

Changed in maas-ui:
importance: Undecided → Low
milestone: 3.4.0 → 3.4.x
status: New → Triaged
Revision history for this message
Alberto Donato (ack) wrote :

I'd mention that we can't get the snap channel info. If we can add a longer explanation we can say that either the snap was manually installed or the snap store can't be reached (e.g. airgapped/proxies environments)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.