[04:29] <beantaxi> smoser: Re your comments on PR #745 ... you requested I hook my part handlers in via stages.py. My part handlers would not represent a new stage; they would be used as part of user-data handling. Would I still need to hook them in via stages.py?
[04:40] <beantaxi> smoser: Looking at the code, I suppose you might be referring to creating some singleton-esque instances in stages._default_handlers(). If so, I'm unsure when I would add a handler to opts.sub_handlers, as is done to a couple handlers including shellscript_handler
[16:22] <Dacesilian> Hello, can you please help me with cloud-init on Debian? Problem is that it's waiting for DHCP, but I have static IP set in config file.
[16:22] <Dacesilian> I'm preparing configuration with cloud-localds -v --dsmode=local --network-config=138-network.yml seed-138.img 138-user.yml
[16:24] <Dacesilian> I've also tried to build own image with build-openstack-debian-image --release buster, but it isn't working with genericcloud image either.
[16:47] <minimal> Decesilian: is this a v1 or v2 network config file?
[16:48] <minimal> Dacesilian: is this a v1 or v2 network config file?
[16:51] <minimal> The cloud-localds options I use typically are "--disk-format raw --filesystem iso9660 --network-config=network-config-v2.yaml seed.img"
[16:56] <Dacesilian> It's v2 config file. I just want to try renderer to eni and see if it helps (I doubt)
[16:57] <Dacesilian> [  OK  ] Started Initial cloud-init job (pre-networking).
[16:57] <Dacesilian> and stuck [*     ] A start job is running for Raise network interfaces (37s / 5min 1s)
[16:58] <Dacesilian> after a while, network is configured right. But why is there this DHCP delay?
[17:15] <minimal> have you turning on cloud-init debugging and then checked the logfile to see what happened during boot? what ends up in your /etc/network/interfaces files after cloud-init runs?