| === nikolay_ is now known as hjckr | ||
| NNautCC | I'm hoping this is the correct place to ask, but, in my PXE clients, after booting the basic environment the console shows "connecting...\nwaiting for cloud-init...\nAn error occurred. Press enter to start a shell" when I enter the shell and go through all the steps in the "How to debug cloud-init" everything checks out | 15:10 |
|---|---|---|
| NNautCC | I'd love any suggestions as to where I might need to look next . I've validated my nocloud autoinstall schema with cloud-init schema | 15:11 |
| NNautCC | dmesg has no errors warnings, etc | 15:12 |
| minimal | NNautCC: you mentioned "autoinstall", so this is Ubuntu with Subiquity? | 15:19 |
| NNautCC | yes | 15:20 |
| minimal | so perhaps it might be best to ask in either the #ubuntu-cloud or #ubuntu-server channels? | 15:20 |
| NNautCC | Sure thing, thanks. | 15:21 |
| holmanb | sbraz: interesting question. We have something like that in place for the apt configure module but not a more generic implementation of the request. | 16:33 |
| holmanb | sbraz: feel free t ofile a feature request on github if you'd like to see something like that | 16:33 |
| holmanb | @minimal ping | 16:34 |
| holmanb | minimal: have you seen this issue? https://github.com/canonical/cloud-init/issues/5380 | 16:35 |
| -ubottu:#cloud-init- Issue 5380 in canonical/cloud-init "add an option to disable dhcpv6 on fallback" [Open] | 16:35 | |
| holmanb | The reporter is using ifupdown and Ubuntu, but curious if ifupdown-ng has the same issue. | 16:36 |
| minimal | holman: looks at a Alpine box with dhcpc where eni has "iface eth0 inet6 dhcp" when /etc/init.d/networking is run the dhcpc output includes "eth0: soliciting an IPv6 router" but there's no problem that only DHCPv4 server is available | 16:40 |
| minimal | I'd have to check how it behaves with either dhclient or udhcpc | 16:40 |
| minimal | holmanb: ^^^ | 16:41 |
| holmanb | hmm, interesting | 16:41 |
| holmanb | thanks for checking minimal | 16:41 |
| minimal | that's with NoCloud on Virtualbox where I haven't enabled VBox's IPv6 support | 16:42 |
| minimal | Alpine 3.18 has the original ifupdown package (in addition ot ifupdown-ng), I could check that | 16:44 |
| holmanb | where is it configured to use dhcpcd? | 16:45 |
| minimal | also I could check Busybox's own ifupdown as | 16:45 |
| holmanb | oh I didn't realize that Busybox had its own ifupdown implementation | 16:45 |
| minimal | holmanb: one of ifupdown-ng's script does a "which" for dhcpc, dhclient, and udhcpc in sequence to determine which is available | 16:45 |
| holmanb | you've spelled it the same way twice now starting to wonder if dhcpc != dhcpcd | 16:46 |
| holmanb | that would be really helpful | 16:46 |
| minimal | oops dhcpcd | 16:47 |
| holmanb | all good :-) | 16:47 |
| holmanb | just wanted to be sure | 16:47 |
| minimal | it's hard to remember to spell both the dhcpcd daemon *AND* the udhcpc client correct in the same sentence lol | 16:47 |
| holmanb | yeah, it breaks my brain too | 16:47 |
| minimal | https://github.com/ifupdown-ng/ifupdown-ng/blob/main/executor-scripts/linux/dhcp#L7-L9 | 16:48 |
| holmanb | based on your check, it sounds like the dhcp6 addition didn't break ifupdown-ng + dhcpcd | 16:48 |
| holmanb | but that likely ifupdown (debian's) + dhclient is broken (based on that report) | 16:49 |
| minimal | I should be able to test dhclient + ifupdown (not -ng) on Alpine 3.18 fairly easily | 16:50 |
| minimal | just tests dhclient with ifupdown-ng (NOT ifupdown) and no problem with eni having dhcpv6 specified | 17:11 |
| minimal | I've had a thought - you do know that dhclient only runs as EITHER a dhcpv4 or a dhcpv6 client (via "-4" and "-6" options)? | 17:12 |
| minimal | with "-4" being the assumed default if neither is specified | 17:12 |
| holmanb | thanks for checking that | 17:18 |
| holmanb | yeah, I'm aware of that | 17:18 |
| minimal | it could perhaps be related to the config script that their dhclient is using (/etc/dhclient-script in Alpine) | 17:19 |
| minimal | I'll test "normal" ifupdown with dhclient shortly | 17:19 |
| holmanb | hmm, that could be | 17:22 |
| holmanb | I just asked for clarification on that | 17:23 |
| holmanb | since they reported using 22.04 and 24.04, but on 24.04 dhcpcd is the default dhcp client | 17:24 |
| holmanb | minimal: did the check you did include the "auto" keyword on eth0? | 19:19 |
| holmanb | nevermind that shouldn't matter | 19:39 |
| holmanb | misread the docs | 19:39 |
| sbraz | holmanb: thanks, will do | 19:57 |
| minimal | holmanb: testing Alpine with ifupdown (not ifupdown-ng) and dhclient - seeing that dhclient is repeatedly soliciting an IP address with incremental backoff retries | 23:32 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!