[14:42] <tryfan> Good day all, I have an interesting problem where I have the same user-data/meta-data on CentOS versions 7.7, 7.8 and 7.9.  On 7.7, cloud-init is version 18.5-3.el7.centos, 7.8 and 7.9: 18.5-6.el7.centos.5.  On 7.7, cloud-init status is done and cloud-final has been run.  on 7.8 and 7.9, status still says running, and cloud-final has not been run.  I'll paste the analyze dumps
[14:45] <tryfan> https://paste.centos.org/view/941d595a
[15:35] <Odd_Bloke> tryfan: Each cloud-init stage is executed at a different point in boot by your init system; if the final stage hasn't run, that suggests that your boot is stuck in something other than cloud-init.
[15:38] <tryfan> Odd_Bloke: wasn't sure if it was triggered by the system or by cloud-init if it detected a new instance.  cloud-final was disabled (not by me) in cent 7.8, 7.9  I enabled cloud-final in the image creation and it's now running.  I'm doing some reboot tests to make sure it doesn't run continually
[15:44] <tryfan> it seems ok now, I guess redhat have hidden enabling cloud-final somewhere in their documentation I couldn't find
[17:06] <blackboxsw> community-notice: we've been remiss in hosting frequent cloud-init office hours. We plan on being available every two weeks at 17:15 UTC  (in +10 mins) I expect we can setup a bot to remind us (and hopefully update the irc topic automatically for us too. So, that this time/date availability is not forgotten come next office hours.
[17:18] <blackboxsw> #startmeeting cloud-init office hours
[17:18] <meetingology> Meeting started at 17:18:36 UTC.  The chair is blackboxsw.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[17:18] <meetingology> Available commands: action, commands, idea, info, link, nick
[17:18] <Odd_Bloke> o/
[17:19] <blackboxsw> community notice: hi folks. We are resuming our much anticipated office hours. Every two weeks at this time. The IRC topic will host our upcoming expected office-hours meeting time.
[17:19] <blackboxsw> \o Odd_Bloke thx
[17:19] <blackboxsw> t
[17:20] <blackboxsw> This meeting will provide an opportunity with multiple upstream cloud-init devs available to discuss bugs, features, ongoing development or answer your existential questions :)
[17:20] <blackboxsw> We hope to continue this meeting with regular cadence (and calendar reminders) to make sure we hold this time and frequency.
[17:22] <blackboxsw> I'll send an email to the mailing list (again) announcing this cadence. Again this time if for any discussions, questions or dev/feature topics that folks would like to gab about.
[17:23] <blackboxsw> We just published a high-level update of what's been happening in the cloud-init space, https://discourse.ubuntu.com/t/cloud-init-status-02-23-2021/21069.
[17:25] <blackboxsw> As seen on the mailinglist, Odd_Bloke and falcojr have been trying to tidy up things for the upstream 21.1 timed release. Thanks both of you for driving this work. I believe 21.1 landed, was uploaded to Ubuntu 21.04 (Hirsute).
[17:26] <blackboxsw> We are also planning on SRUing(StableReleaseUpdate - Ubuntu-speak for uploading) 21.1 plus a feature fix for OVS support into Xenial, Bionic, Focal and Groovy within the next week or two.
[17:26] <Odd_Bloke> Yep, I'm currently working through the release announcement process.
[17:30] <blackboxsw> great Dan. So, TLDR is watch the mailinglist cloud-init@lists.launchpad.net and discourse https://discourse.ubuntu.com/c/server/cloud-init for announcements and updates
[17:30] <blackboxsw> #link https://discourse.ubuntu.com/c/server/cloud-init
[17:58] <blackboxsw> I think we've about rounded out the office-hours. (I spent that time walking through a sopel-irc bot setup to test out some of the features to see if we can't add some structure to this office-hours engagement (and frankly release announcements too )
[17:59] <blackboxsw> Let's set that next office hours for +2 weeks-45 mins from now
[18:00] <blackboxsw> hopefully by then we have an automated announcer kicking off the notification.
[18:00] <blackboxsw> Thanks all!
[18:00] <blackboxsw> #endmeeting
[18:00] <meetingology> Meeting ended at 18:00:28 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-02-23-17.18.moin.txt
[20:18] <ninjitsu> Hey all.  I'm new to cloud-init and am currently working a project using it.  I am having a problem when passing in "accept" as the value to the "chef_license" parameter.  I've shown the erorr here: https://github.com/number5/cloud-init/issues/16
[20:20] <ninjitsu> Basically this line here: https://github.com/number5/cloud-init/blob/a64b73808857fa7b4f262422ce2c87eedbce10d5/cloudinit/config/cc_chef.py#L443 - looks in the "CHEF_RB_TPL_PATH_KEYS" array, finds "chef_license", and then proceeds to attempt to strip the filename ("accept") while keeping what it believes is the path "''" which it then tries to ensure exists with the call to util.ensure_dirs
[20:24] <Odd_Bloke> ninjitsu: o/ This sounds like https://bugs.launchpad.net/cloud-init/+bug/1912424 to me.  Does that sound right?
[20:24] <ninjitsu> sec let me check
[20:25] <ninjitsu> yes that user is experiencing the exact same issue
[20:25] <ninjitsu> and his suggested fix is kind of exactly what i was thinking
[20:27] <Odd_Bloke> I've commented there, hopefully they'll see and pick it up.
[20:28] <ninjitsu> Thanks Dan :D I'll watch that thread.
[21:29] <ninjitsu> Hey so I have a question - so the "chef" module runs as part of the "final" stage, according to the docs I'm reading, and "runcmd" runs as part of the "config" stage which is supposed to occur prior to the "final" stage.  Is this order accurate? Because I have a "chef-client --chef-license accept" command listed in "runcmd" and it seems to execute AFTER the chef client is installed. While I like this behavior, idk if I'm readin
[21:44] <rharper> ninjitsu: so  runcmd runs during cloud-config stage (ci goes init-local, init, config, final).  runcmd will emit the commands to run into a script which will be executed during final, specifically when it runs scripts_user stage) ... the chef module allows you to accept the license via cloud-config ... maybe you've already got that in there?
[21:47] <rharper> the chef module will run before scripts user  ... so your runcmds run after anything that the check cloud-config module does
[21:49] <rharper> the module looks to install chef and render templates, and optionally run chef ;  this would execute before runcmd script executes (even though runcmd stage is rendered earlier in boot);  yes that's confusing; the docs for runcmd do say "run at rc.local time" which is effective when cloud-final runs as well.
[22:21] <Odd_Bloke> Just published 21.1 to the el-testing repo at https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/