[13:03] <meena> i have done horrible things to setup.py
[13:03] <meena> looking forward to someone scratching their eyes out when reviewing it.
[13:58] <meena> here we go: https://github.com/canonical/cloud-init/pull/4182
[13:58] -ubottu:#cloud-init- Pull 4182 in canonical/cloud-init "BSD: add dsidentify to early startup scripts" [Open]
[16:31] <tryfan> Hi All, I'm running cloud-init on rhel 9.  cloud-final is running at boot, but for some reason it is skipping running the scripts in runcmd.  It sets network and users fine.  I've tried removing machine-id, cleaning the /var/lib/cloud directory, but nothing seems to work
[16:33] <meena> tryfan: no errors or exceptions? 
[16:34] <tryfan> no, it just seems to think it's rebooted before and doesn't run any of the commands.  terminates successfully
[16:34] <minimal> you've checked /var/log/cloud-init.log with debugging enabled?
[16:35] <minimal> that will show which modules it considers to run at each stage
[16:37] <tryfan> it seems to be running cloud-final but just the commands aren't run, as if per-instance isn't triggered
[16:40] <minimal> are you seeing this from cloud-init.log?
[16:41] <tryfan> I'm seeing it in the cloud-final systemctl, seeing it in cloud-init-output.log as well.  just starts and stops.
[16:42] <tryfan> what I really want to know is how to determine how cloud-init is figuring out whether to run each phase
[16:43] <falcojr> each phase should always get run. Within each phase there are modules run. Some run always, others run only if specific keys in are detected in the provided cloud-config
[16:44] <falcojr> probably easiest to run "cloud-init collect-logs --include-userdata" (remove that --include-userdata flag if you have anything sensitive in your user data), and upload the resulting tarball to a new issue. https://github.com/canonical/cloud-init/issues
[16:46] <minimal> tryfan: that is why I suggested cloud-init.log with DEBUG enabled - that will log the list of enabled modules for each stage and then how cloud-init decides whether to do anything for each of them
[16:47] <tryfan> it's a default cloud.cfg, so runcmd is in cloud_config_modules and scripts_user is in cloud_final_modules
[16:49] <tryfan> The /etc/cloud/cloud.cfg.d/05_logging.cfg is here: https://paste.centos.org/view/cefa0518
[16:57] <minimal> so what does   grep "Running module runcmd " /var/log/cloud-info.log show?
[17:16] <tryfan> minimal: I see under modules-final - config-scripts-user : SUCCESS: config-scripts-user previously run  and here's a screenshot of a runcmd on this template: https://d.pr/i/KfgRTn
[17:17] <tryfan> so runcmd seems to be running, creates the scripts to be run, but scripts-user doesn't execute them
[17:18] <tryfan> I'm off with that customer, just trying to figure their issue out.  other templates they have, rhel 7/8 work fine.  all the templates I've done for EL9 variants, centos9, alma9, rocky9, all have worked fine.  I believe they are doing something to the template, but I haven't been able to identify anything that would cause this kind of issue
[17:35] <minimal> what does   grep "Running module scripts_user " /var/log/cloud-info.log show?