Systemd networking broken on user phase

[sormy]

Systemd networking broken on user phase

[sormy]

Could you please provide error log

[AZMCode]

Sadly there is none. I just get failed to resolve domain name error on user phase, and upon inspection through SSH, the chroot's resolv conf is a dangling symlink.

Edit: Excuse my previous confusion, I thought this was on my failed PR

[sormy]

I mean, what it the error if you won't comment this ln -sf command? Please also share details about what stage, region, profile were used?

[AZMCode]

I believe I specified the error in the PR, name resolution is broken. Same with the stage, it happens on stage 3, in the user phase. I'm currently running the script in the sa-east-1 region, with the default instance type, using the amd64-systemd profile.

[sormy]

I just tried ./gentoo-ami-builder.sh --update-world no --gentoo-stage3 amd64-systemd --key-pair "..." on us-east-1 and it has completed without issues. Could you please share logs for failed build. Unfortunately, there are no logs for the issue in this ticket and in related closed ticket as well.

[AZMCode]

That's weird. I literally have no logs to share in this respect, as everything worked out fine up until the user phase. I understand if you have to close the issue due to lack of repro.

[sormy]

Please share command line you run. What is printed on the screen when script fails and may be at least partial content of user phase script. Please remove any personal information from logs, user phase script and command line.

[AZMCode]

As of now I'm busy getting my current user phase script to work using the fix described, but I might come back to this and provide the log and further experimentation to see what causes the bug.

[frostynova]

Met this problem too

CLI: ./gentoo-ami-builder.sh --region ap-southeast-1 --key-pair gentoo --spot-instance false --gentoo-stage3 amd64-systemd --gentoo-profile default/linux/amd64/17.1/systemd

No error output during script execution. But using this ami to boot a new instance, "/run/systemd/resolve/resolv.conf" is missing.

After "systemctl restart systemd-resolved", everything is ok.

[sormy]

might be related to ap-southeast-1, reopening, but will test after holidays

[sormy]

Seems like it is working now, feel free to reopen with more details