| 2024-04-04 04:06:11 |
Jacopo Rota |
description |
In 3.5 I got a run where the snap has started but no UI was available. After checking in the maas-log, I found
```
Apr 04 03:50:31 maas-ha-1 maas-log[129195]: maas.service_monitor: [error] Service 'reverse_proxy' failed to restart: Pebble change 3 failed with an error: cannot perform the following tasks:#012- Stop service "http" (cannot stop service while starting)
```
Also, the pebble services seems to be running but still no http endpoints are available
```
# pebble services
Service Startup Current Since
agent disabled inactive -
apiserver enabled active today at 03:50 UTC
bind9 disabled active today at 03:50 UTC
dhcpd disabled inactive -
dhcpd6 disabled inactive -
http disabled active today at 03:50 UTC
ntp disabled active today at 03:50 UTC
proxy disabled active today at 03:50 UTC
rackd enabled active today at 03:50 UTC
regiond enabled active today at 03:50 UTC
syslog disabled active today at 03:50 UTC
temporal disabled active today at 03:50 UTC
temporal-worker disabled active today at 03:50 UTC
``` |
In 3.5 I got a run where the snap has started but no UI was available. After checking in the maas-log, I found
```
Apr 04 03:50:31 maas-ha-1 maas-log[129195]: maas.service_monitor: [error] Service 'reverse_proxy' failed to restart: Pebble change 3 failed with an error: cannot perform the following tasks:#012- Stop service "http" (cannot stop service while starting)
```
Also, the pebble services seems to be running but still no http endpoints are available
```
# pebble services
Service Startup Current Since
agent disabled inactive -
apiserver enabled active today at 03:50 UTC
bind9 disabled active today at 03:50 UTC
dhcpd disabled inactive -
dhcpd6 disabled inactive -
http disabled active today at 03:50 UTC
ntp disabled active today at 03:50 UTC
proxy disabled active today at 03:50 UTC
rackd enabled active today at 03:50 UTC
regiond enabled active today at 03:50 UTC
syslog disabled active today at 03:50 UTC
temporal disabled active today at 03:50 UTC
temporal-worker disabled active today at 03:50 UTC
```
In the regiond and rackd logs there are plenty of
```
Apr 04 04:03:43 maas-ha-1 maas-regiond[129092]: temporalio.activity: [warn] Completing activity as failed ({'activity_id': '1', 'activity_type': 'get-bootresourcefile-endpoints', 'attempt': 14, 'namespace': 'default', 'task_queue': 'region-internal', 'workflow_id': 'sync-b>
Apr 04 04:03:43 maas-ha-1 maas-regiond[129092]: Traceback (most recent call last):
Apr 04 04:03:43 maas-ha-1 maas-regiond[129092]: File "/snap/maas/x1/usr/lib/python3/dist-packages/temporalio/worker/_activity.py", line 439, in _run_activity
Apr 04 04:03:43 maas-ha-1 maas-regiond[129092]: result = await impl.execute_activity(input)
Apr 04 04:03:43 maas-ha-1 maas-regiond[129092]: File "/snap/maas/x1/usr/lib/python3/dist-packages/temporalio/worker/_activity.py", line 694, in execute_activity
Apr 04 04:03:43 maas-ha-1 maas-regiond[129092]: return await input.fn(*input.args)
Apr 04 04:03:43 maas-ha-1 maas-regiond[129092]: File "/snap/maas/x1/lib/python3.10/site-packages/maasserver/workflow/bootresource.py", line 108, in get_bootresourcefile_endpoints
Apr 04 04:03:43 maas-ha-1 maas-regiond[129092]: raise ApplicationError(
Apr 04 04:03:43 maas-ha-1 maas-regiond[129092]: temporalio.exceptions.ApplicationError: Could not retrieve the IP addresses of the region controller 'yfaqya' from the API. This activity will be retried until we have the IP for all the region controllers.
```
and
```
Apr 04 04:05:47 maas-ha-1 maas-rackd[129097]: provisioningserver.rpc.clusterservice: [info] Region not available: Connection was refused by other side: 111: Connection refused. (While requesting RPC info at http://10.0.1.23:5240/MAAS).
```
because the region is not exposing any http service actually |
|
