Hello there,
I upgraded MAAS 3.5.0 (on Ubuntu 22.04.4).
$ dpkg -l maas
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-==========================================-============-=================================================
ii maas 1:3.3.7-13246-g.2341ebf5d-0ubuntu1~22.04.1 all "Metal as a Service" is a physical cloud and IPAM
$ sudo apt-add-repository ppa:maas/3.5
$ sudo apt-get -y update
$ sudo apt-get -y dist-upgrade maas
$ sudo reboot
Then the following screen seems to be displayed, but nothing else is displayed.
Also, you will not be able to resolve the name by MAAS DNS.
Is there a workaround?
P.S.
I was able to restore it to normal operation with the original MAAS 3.3.7 by restoring from the snapshot of Linux KVM.
1 Like
r00ta
2
Could you please look at the logs to check what happened?
journalctl -t maas-regiond
Also, how long did you wait before giving up?
Thanks r00ta.
Journalctl outputs No entries.
$ journalctl -t maas-regiond
-- No entries --
$ journalctl -t maas-rackd
-- No entries --
Region is not advertising RPC endpoints. It is displayed.
$ sudo systemctl status maas-rackd.service
β maas-rackd.service - MAAS Rack Controller
Loaded: loaded (/lib/systemd/system/maas-rackd.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2024-07-16 07:25:52 UTC; 45s ago
Docs: https://maas.io/docs
Process: 9196 ExecStartPre=/bin/rm -f /var/lib/maas/dhcpd.sock /var/lib/maas/dhcpd.conf /var/lib/maas/dhcpd6.conf (code=e>
Main PID: 9197 (rackd)
Tasks: 7 (limit: 9388)
Memory: 105.8M
CPU: 4.975s
CGroup: /system.slice/maas-rackd.service
ββ9197 /usr/bin/python3 /usr/sbin/rackd
ββ9278 /usr/bin/python3 /usr/lib/maas/maas-common observe-beacons ens3
ββ9304 sudo -n /usr/lib/maas/beacon-monitor ens3
ββ9305 /usr/bin/tcpdump -Z root --interface ens3 --direction=in --no-promiscuous-mode --packet-buffered --immedi>
Jul 16 07:26:34 maas4 rackd[9197]: provisioningserver.rpc.clusterservice: [info] Region is not advertising RPC endpoints. (Wh>
Jul 16 07:26:35 maas4 rackd[9197]: provisioningserver.rpc.clusterservice: [info] Region is not advertising RPC endpoints. (Wh>
Jul 16 07:26:35 maas4 rackd[9197]: provisioningserver.rpc.clusterservice: [info] Region is not advertising RPC endpoints. (Wh>
Jul 16 07:26:35 maas4 rackd[9197]: provisioningserver.rpc.clusterservice: [info] Region is not advertising RPC endpoints. (Wh>
Jul 16 07:26:36 maas4 rackd[9197]: provisioningserver.rpc.clusterservice: [info] Region is not advertising RPC endpoints. (Wh>
Jul 16 07:26:36 maas4 rackd[9197]: provisioningserver.rpc.clusterservice: [info] Region is not advertising RPC endpoints. (Wh>
Jul 16 07:26:36 maas4 rackd[9197]: provisioningserver.rpc.clusterservice: [info] Region is not advertising RPC endpoints. (Wh>
Jul 16 07:26:37 maas4 rackd[9197]: provisioningserver.rpc.clusterservice: [info] Region is not advertising RPC endpoints. (Wh>
Jul 16 07:26:37 maas4 rackd[9197]: provisioningserver.rpc.clusterservice: [info] Region is not advertising RPC endpoints. (Wh>
Jul 16 07:26:37 maas4 rackd[9197]: provisioningserver.rpc.clusterservice: [info] Region is not advertising RPC endpoints. (Wh>
$ sudo systemctl status maas-regiond.service
β maas-regiond.service - MAAS Region Controller
Loaded: loaded (/lib/systemd/system/maas-regiond.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2024-07-16 07:25:41 UTC; 1min 3s ago
Docs: https://maas.io/docs/
Main PID: 9155 (regiond)
Tasks: 2 (limit: 9388)
Memory: 1.0G
CPU: 40.310s
CGroup: /system.slice/maas-regiond.service
ββ9155 /usr/bin/python3 /usr/sbin/regiond
Jul 16 07:25:48 maas4 regiond[9155]: maasserver.models.signals.staticipaddress: [info] Removed orphan DNS record 'win-vvu5qf9>
Jul 16 07:25:48 maas4 regiond[9155]: maasserver.models.signals.staticipaddress: [info] Removed orphan DNS record 'win-ti2grms>
Jul 16 07:25:48 maas4 regiond[9155]: maasserver.models.signals.staticipaddress: [info] Removed orphan DNS record 'rtemplate.m>
Jul 16 07:25:48 maas4 regiond[9155]: maasserver.models.signals.staticipaddress: [info] Removed orphan DNS record 'rhel9-demo.>
Jul 16 07:25:48 maas4 regiond[9155]: maasserver.models.signals.staticipaddress: [info] Removed orphan DNS record 'storage-tes>
Jul 16 07:25:48 maas4 regiond[9155]: maasserver.models.signals.staticipaddress: [info] Removed orphan DNS record 'storage-tes>
Jul 16 07:25:48 maas4 regiond[9155]: maasserver.models.signals.staticipaddress: [info] Removed orphan DNS record 'storage-tes>
Jul 16 07:25:48 maas4 regiond[9155]: maasserver.models.signals.staticipaddress: [info] Removed orphan DNS record 'ubuntu-serv>
Jul 16 07:25:48 maas4 regiond[9155]: maasserver.models.signals.staticipaddress: [info] Removed orphan DNS record 'ubuntu-serv>
Jul 16 07:25:48 maas4 regiond[9155]: maasserver.models.signals.staticipaddress: [info] Removed orphan DNS record 'mx-one.maas
Ping canβt solve the fqdn address.
% ping maas4.maas
ping: cannot resolve maas4.maas: Unknown host
I didnβt answer this question.
Also, how long did you wait before giving up?
I waited for about 5-6 minutes.
Oh!
After waiting for about 15 minutes, the MAAS dashboard was displayed.
r00ta
6
FYI in 3.5.0 we moved the images from the DB to the disk of the regions and this might require some time immediately after the upgrade.
Also, I noticed now that you are using deb. For debs the logs are under
journalctl -t regiond
while for snaps are under
journalctl -t maas-regiond
Thank you for reporting back that everything looks fine atm. In case you hit issues, please let us know!
2 Likes
