OK, it sounds like cloud-init is behaving as we expect it to, so I'm
going to mark our task as Invalid. Do comment (and change status to
New, if you can) if you think that's incorrect.
** Changed in: cloud-init
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1879103
Title:
Unattended installation user data conflict
Status in cloud-init:
Invalid
Status in subiquity:
Fix Committed
Bug description:
When passing user-data to the 20.04 unattended installation through an
iso described at
https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls/QuickStart,
user creation doesn't happen. This is because /dev/sr1 takes priority
over /var/lib/cloud/seed/nocloud-net/.
The simple workaround for anyone experiencing this issue is to add the
following to their user-data script:
late-commands:
- "eject /dev/sr1"
I experienced this using Hyper-V.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1879103/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
