[03:52] <bryceh> nibbon_, no ETA but I did start working on it prior to vacation.  FF-critical items are higher priority but I am feeding the backports ppa with attention in between things.  This is my first time handling the backports myself so it may take longer than normal.
[07:26] <nibbon_> bryceh: ack, is there anything I can do to help you with backporting these packages?
[09:58] <webmind> Anyone here ever done ubuntu 22.04 server on encrypted lvm on raid? after installation it doesn't find the root partition, doesn't ask for a password.
[09:58] <webmind> wondering what goes wrong.
[10:28] <webmind> 3rd attempt, with 22.04, looks like this is just broken.
[10:54] <Moha> in `sudo snap install openstack --channel 2023.1`, what does "2023.1" stands for? Ref: https://microstack.run/docs/single-node | Is it the stable version?
[10:57] <Moha> Answred! I run it without 2023, and it itself started with the channel `2023.1/stable`.
[14:09] <effendy[m]> Hello. I'm cloning an ubuntu cloud image to create a template with packer on vSphere. I'm just injecting a basic cloud-init configuration (user configuratiom, shell). This is where I'm getting the cloud images from: http://cloud-images.ubuntu.com/jammy/current/ My problem is that the virtual machine created from these cloud images always reboot once after the first boot. And I've no idea what triggers this reboot. This hinders my
[14:09] <effendy[m]> provisioning process (packer/terraform) and I would just like it not to reboot. I've had lengthy conversation on the cloud-init channels and the developers there told me that this is not related to cloud-init, given that there's no power_state stage which is executed in cloud-init. So something else triggers this reboot, I just can't figure out what it is.
[14:09] <effendy[m]> I've searched in syslog, cloud-init log too, of course, but to no avail.
[14:15] <rbasak> Can you reproduce this without using packer?
[14:19] <effendy[m]> Good question, I haven't tried it. I could just manually enter the base64 string inserted in user-data (through vApp Options on vSphere). I'll try to decode it first, to make sure there's no weird stuff there.
[14:20] <effendy[m]> But I don't think packer is doing much else than injecting that base64 string (which looks innocuous) and waiting to connect to the VM through ssh. It starts provisioning stuff with ansible and the connection is cut off my this reboot.
[14:30] <effendy[m]> I think I've found out where the problem is. It seems to be vSphere-specific, related to the vmware tools/guest agent. There's a service there that watches cloud-init and it reboots automatically after cloud-init finishes. This relationship with cloud-init made me believe that cloud-init was the issue.
[14:30] <effendy[m]> info] sSkipReboot: 'false', forceSkipReboot 'false'. / info] Do not trigger reboot if cloud-init is executing.
[14:47] <rbasak> Great - thank you for reporting back!
[15:23] <effendy[m]> It seems to be related to this, in case anyone's interested: https://kb.vmware.com/s/article/59557