MAAS Server version: 3.6.0-17541-g.561fe1a3e 39328 3.6/stable
Deploy os version: Ubuntu 24.04.2 LTS (GNU/Linux 6.8.0-62-lowlatency x86_64)
When deploy any machine if using cloud-init script for most of module will resulted failed scripts_user then no maas_hardware_sync.timer is founded.
cloud-init-output.log
Failed to start maas_hardware_sync.timer: Unit maas_hardware_sync.timer not found.
Failed to enable unit: Unit file maas_hardware_sync.timer does not exist.
2025-06-29 05:09:54,450 - cc_scripts_user.py[WARNING]: Failed to run module scripts_user (scripts in /var/lib/cloud/instance/scripts)
2025-06-29 05:09:54,450 - log_util.py[WARNING]: Running module scripts_user (<module 'cloudinit.config.cc_scripts_user' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_scripts_user.py'>) failed
the module I’ve tested include write_files using uri and runcmd for wget file even just a simple echo character.
#cloud-config
write_files:
- source:
uri: <any url>
path: /run/test.sh
permissions: '0700'
defer: true
#cloud-config
runcmd:
- [sh, -c, echo a]
If need any more information I will upload for more investigate.
Hi there, thanks for posting! Let me try and understand your issue a bit better. Can I confirm the following please?
- I presume you are running into this issue when deploying with enable_hw_sync=true, for example something like:
maas admin machine deploy <system-id> osystem=ubuntu distro_series=noble enable_hw_sync=true
Do you get this error when deploying a node with enable_hw_sync=false?
- I’m not sure why this would happen, but MAAS should add the file
maas_hardware_sync.timer to the node if hw sync is enabled. This error looks like it’s not being created. Just to be sure, can you confirm this by running the following on the node which the deployment has failed:
ls -l /lib/systemd/system/maas_hardware_sync*
I presume there will be no output when there should be maas_hardware_sync.timer and maas_hardware_sync.service present.
I’m using GUI
1.
Following settings are
OS : Ubuntu
Kernel : ga-24.04-lowlatency
#cloud-config
runcmd:
- [sh, -c, echo a]
Periodically sync hardware : False
No, there is no obvious in cloud-init.log or cloud-init-output.log.
Following settings are
OS : Ubuntu
Kernel : ga-24.04-lowlatency
Cloud-init Code:
#cloud-config
runcmd:
- [sh, -c, echo a]
Periodically sync hardware : True
for your information.
~$ ls -l /lib/systemd/system/maas_hardware_sync*
-rw-r--r-- 1 root root 439 Jul 2 04:02 /lib/systemd/system/maas_hardware_sync.service
-rw-r--r-- 1 root root 253 Jul 2 04:02 /lib/systemd/system/maas_hardware_sync.timer
~$ systemctl list-timers --all
NEXT LEFT LAST PASSED UNIT ACTIVATES
Wed 2025-07-02 09:30:00 UTC 43s Wed 2025-07-02 09:20:20 UTC 8min ago sysstat-collect.timer sysstat-collect.service
Wed 2025-07-02 09:36:15 UTC 6min Wed 2025-07-02 08:49:33 UTC 39min ago fwupd-refresh.timer fwupd-refresh.service
Wed 2025-07-02 15:54:52 UTC 6h Wed 2025-07-02 06:08:44 UTC 3h 20min ago motd-news.timer motd-news.service
Thu 2025-07-03 00:00:00 UTC 14h - - dpkg-db-backup.timer dpkg-db-backup.service
Thu 2025-07-03 00:00:00 UTC 14h - - logrotate.timer logrotate.service
Thu 2025-07-03 00:07:00 UTC 14h - - sysstat-summary.timer sysstat-summary.service
Thu 2025-07-03 04:05:50 UTC 18h Wed 2025-07-02 04:05:50 UTC 5h 23min ago update-notifier-download.timer update-notifier-download.service
Thu 2025-07-03 04:15:50 UTC 18h Wed 2025-07-02 04:15:50 UTC 5h 13min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service
Thu 2025-07-03 05:26:32 UTC 19h Wed 2025-07-02 06:08:13 UTC 3h 21min ago apt-daily.timer apt-daily.service
Thu 2025-07-03 06:22:30 UTC 20h Wed 2025-07-02 06:07:30 UTC 3h 21min ago apt-daily-upgrade.timer apt-daily-upgrade.service
Thu 2025-07-03 10:44:02 UTC 1 day 1h - - man-db.timer man-db.service
Sun 2025-07-06 03:10:50 UTC 3 days - - e2scrub_all.timer e2scrub_all.service
Mon 2025-07-07 01:22:09 UTC 4 days - - fstrim.timer fstrim.service
Thu 2025-07-10 00:52:08 UTC 1 week 0 days - - update-notifier-motd.timer update-notifier-motd.service
- - - - apport-autoreport.timer apport-autoreport.service
- - - - snapd.snap-repair.timer snapd.snap-repair.service
- - - - ua-timer.timer ua-timer.service
With those settings there no obvious in cloud-init.log or cloud-init-output.log, but still no hardware sync from machine.
