Where did you configure “FQDN”?
Where did you configure that?
It’s in /etc/hosts file
if you change it and use another name like test, does it work? (note that you might have to re-initialize MAAS)
Can you please explain where to check this name like test?
Will initialize the maas again.
Can you please explain where to check this name like test?
What do you mean?
“if you change it and use another name like test , does it work?”
- as per your comment, where to check the name?
I don’t understand what do you mean by “check”. If you have a DNS server and you want to assign a record that resolves to that machine IP you can use any hostname on the machine.
I think you have to provide more details about your setup, otherwise it’s impossible to help you.
maas status
Service Startup Current Since
agent disabled inactive -
apiserver enabled active today at 07:38 UTC
bind9 disabled active today at 07:38 UTC
dhcpd disabled inactive -
dhcpd6 disabled inactive -
http disabled active today at 07:38 UTC
ntp disabled active today at 07:38 UTC
proxy disabled active today at 07:38 UTC
rackd enabled active today at 07:38 UTC
regiond enabled active today at 07:38 UTC
syslog disabled active today at 07:38 UTC
temporal disabled active today at 07:38 UTC
temporal-worker disabled active today at 07:38 UTC
cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
172.25.92.179 single-master-92-179.ucpa-sc-hv.com
Above mentioned comments I have executed.
What do you have there? How is MAAS using that?
should i remove it from /etc/hosts file ?
I don’t know what’s your environment, what’s running on that host and who put it there, so how can I say?
I don’t see why and how that thing could break MAAS if it’s not even using it.
Can you explain how to debug that why maas-agent stopped for this instance?
And how to enable this maas-agent?
I will try to figure out the root cause of this issue.
I don’t know by heart. Your issue looks very similar to the known limitation that MAAS 3.5 snap runs only on Ubuntu hosts.
But since you confirmed that you are running Ubuntu you have to look at the logs and your setup to understand what’s wrong
I am getting this error in the log and maas agent in backoff state for the vm which configured with fqdn,
error logs–
Dec 18 00:50:19 single-master-92-179.ucpa-sc-hv.com maas-agent[2270]: ERR Workflow configure-agent failed error=“workflow execution error (type: configure-agent, workflowID: e1d6a60e-322b-41f7-81f1-5d93655415ea, runID: a3592549-45d5-4de7-a1e0-56c42bd24e2e): child workflow execution error (type: configure-httpproxy-service, workflowID: configure-httpproxy-service:cbste4, runID: b6252674-b351-4126-8bcf-e370808c99a8, initiatedEventID: 14, startedEventID: 15): targets cannot be empty”
Dec 18 00:50:19 single-master-92-179.ucpa-sc-hv.com maas.pebble[1502]: 2024-12-18T05:50:19.421Z [pebble] Service “agent” stopped unexpectedly with code 1
temporalio.activity: [warn] Completing activity as failed ({‘activity_id’: ‘1’, ‘activity_type’: ‘get-bootresourcefile-endpoints’, ‘attempt’: 6, ‘namespace’: ‘default’, ‘task_queue’: ‘region-internal’, ‘workflow_id’: ‘sync-boot-resources:streams’, ‘workflow_run_id’: ‘1e105fdd-9119-4fc0-a0d1-73b301dec628’, ‘workflow_type’: ‘sync-bootresources’})
Dec 18 00:50:45 single-master-92-179.ucpa-sc-hv.com maas-regiond[1617]: Traceback (most recent call last):
Dec 18 00:50:45 single-master-92-179.ucpa-sc-hv.com maas-regiond[1617]: File “/snap/maas/37259/usr/lib/python3/dist-packages/temporalio/worker/_activity.py”, line 439, in _run_activity
Dec 18 00:50:45 single-master-92-179.ucpa-sc-hv.com maas-regiond[1617]: result = await impl.execute_activity(input)
Dec 18 00:50:45 single-master-92-179.ucpa-sc-hv.com maas-regiond[1617]: File “/snap/maas/37259/usr/lib/python3/dist-packages/temporalio/worker/_activity.py”, line 694, in execute_activity
Dec 18 00:50:45 single-master-92-179.ucpa-sc-hv.com maas-regiond[1617]: return await input.fn(*input.args)
Dec 18 00:50:45 single-master-92-179.ucpa-sc-hv.com maas-regiond[1617]: File “/snap/maas/37259/lib/python3.10/site-packages/maasserver/workflow/bootresource.py”, line 159, in get_bootresourcefile_endpoints
Dec 18 00:50:45 single-master-92-179.ucpa-sc-hv.com maas-regiond[1617]: raise ApplicationError(
Dec 18 00:50:45 single-master-92-179.ucpa-sc-hv.com maas-regiond[1617]: temporalio.exceptions.ApplicationError: Could not retrieve the IP addresses of the region controller ‘cbste4’ from the API. This activity will be retried until we have the IP for all the region controllers.
Please let me know, if you have some clue based on the error log I posted.
Can you post the output of
sudo cat /var/snap/maas/current/regiond.conf
and
sudo cat /var/snap/maas/current/agent.yaml
and
sudo cat /var/snap/maas/current/rackd.conf
please
Please find the following details,
sudo cat /var/snap/maas/current/regiond.conf
database_host: localhost
database_name: maasdb
database_pass: maaspass
database_port: 5432
database_user: maas
maas_url: http://single-master-92-179.ucpa-sc-hv.com:5240/MAAS
sudo cat /var/snap/maas/current/agent.yaml
WARNING: MAAS will overwrite any changes made here.
controllers:
- single-master-92-179.ucpa-sc-hv.com
httpproxy:
cache_dir: /var/snap/maas/common/maas/cache/httpproxy
cache_size: 5015112499.2
log_level: info
maas_uuid: 1549f7ba-5319-4072-ac04-d266759680a3
secret: fa4ad90348ad7042b68fc04e782f54f7
system_id: cbste4
sudo cat /var/snap/maas/current/rackd.conf
maas_url: http://single-master-92-179.ucpa-sc-hv.com:5240/MAAS
Please let me know, if I am missing something.
If your settings are still the same your machine has the ip 172.25.20.211 and you configured /etc/hosts with 172.25.92.179 single-master-92-179.ucpa-sc-hv.com instead of 172.25.20.211 single-master-92-179.ucpa-sc-hv.com