Controllers have different versions with latest 3.3.x versions

I have this issue in my test env.

Controllers have different versions error pops up.
The leading 1: in front of the version randomly appears and dissapears.

image

That was supposed to have been fixed in 3.2 Controllers have different versions. Perhaps a regression?

Yes, I saw that also. I have this issue with latest deb version and had it with N-1 as well. Decided to bring this up here as I updated everything today and this issues still exists. Seems to be more of an annoyance than having real impact, but nevertheless, it’s there.

Hi @mitzone

So this happens only with deb version of MAAS? Did you have a chance to check if the same issue exists if MAAS installed via snap?

Also, may I ask you to file a bug report at https://bugs.launchpad.net/maas?

I have the same issue on 3.3.4

regiond versions:

ii  maas-cli                              1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1  all          MAAS client and command-line interface
ii  maas-common                           1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1  all          MAAS server common files
ii  maas-proxy                            1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1  all          MAAS Caching Proxy
ii  maas-region-api                       1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1  all          Region controller API service for MAAS
ii  maas-region-controller                1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1  all          Region Controller for MAAS
ii  python3-django-maas                   1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1  all          MAAS server Django web framework (Python 3)
ii  python3-maas-client                   1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1  all          MAAS python API client (Python 3)
ii  python3-maas-provisioningserver       1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1  all          MAAS server provisioning libraries (Python 3)

rackd versions

ii  maas-cli                              1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1  all          MAAS client and command-line interface
ii  maas-common                           1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1  all          MAAS server common files
ii  maas-dhcp                             1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1  all          MAAS DHCP server
ii  maas-proxy                            1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1  all          MAAS Caching Proxy
ii  maas-rack-controller                  1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1  all          Rack Controller for MAAS
ii  python3-maas-client                   1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1  all          MAAS python API client (Python 3)
ii  python3-maas-provisioningserver       1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1  all          MAAS server provisioning libraries (Python 3)

The same issue with:

ii  maas                                  1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1      all          "Metal as a Service" is a physical cloud and IPAM
ii  maas-cli                              1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1      all          MAAS client and command-line interface
ii  maas-common                           1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1      all          MAAS server common files
ii  maas-dhcp                             1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1      all          MAAS DHCP server
ii  maas-proxy                            1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1      all          MAAS Caching Proxy
ii  maas-rack-controller                  1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1      all          Rack Controller for MAAS
ii  maas-region-api                       1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1      all          Region controller API service for MAAS
ii  maas-region-controller                1:3.3.4-13189-g.f88272d1e-0ubuntu1~22.04.1      all          Region Controller for MAAS