[Expired for cloud-init (Ubuntu) because there has been no activity for
60 days.]
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking this as Incomplete as Ryan has provided next debugging steps.
Please do move it back to New once you've responded!
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
* eoli3n <1907...@bugs.launchpad.net> [2020-12-08 13:30]:
> If i run autoinstall with that user-data file, autoinstall doesn't run
> and subiquity prompt for language setting.
>
> #cloud-config
> runcmd:
> - systemctl daemon-reload
> - systemctl restart gdm3
> autoinstall:
> version: 1
>
>The design is based on the idea of a template image. The Ubuntu server
image is ready to boot and on first boot cloud-init handles the tasks
to "instantiate the image".
>Doesn't the autoinstall input generatea cloud-init config that
configures these things?
As i understand it, autoinstall
If i run autoinstall with that user-data file, autoinstall doesn't run
and subiquity prompt for language setting.
#cloud-config
runcmd:
- systemctl daemon-reload
- systemctl restart gdm3
autoinstall:
version: 1
packages:
- gdm3
locale: fr_FR.UTF-8
user-data:
timezone:
* eoli3n <1907...@bugs.launchpad.net> [2020-12-08 11:50]:
> > I can say that the Ubuntu Server installer isn't typically used to install
> > Ubuntu Desktop.
> I use it because i can't find any netboot installer which supports
> autoinstall and EFI installation. I used legacy netboot (60MB) for
This is log collected after first boot with previous minimal user-data
file (which only set locales, timezone and install lightdm package), i
waited for cloud-config to run.
** Attachment added: "cloud-init.tar.gz"
> installing lightdm brings in over 500 packages and took about 12 minutes to
> install;*
It seems normal to me, it installs a big tree of dependencies because its the
first "graphic" package.
> Some package may require post-install configuration.
I used that method with success for many years
Can you run and attach the output tarball on the target system where you
see this fail:
cloud-init collect-logs
With respect to your use-case; cloud-init does not directly control what
packages do at install time. Some package may require post-install
configuration, or are not typically
Please move this back to New after you've attached the cloud-init
collect-logs output tarball.
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That screenshot show time when those services are ready
- gdm
- cloud-init
- cloud-config
** Attachment added: "screenshot"
https://bugs.launchpad.net/subiquity/+bug/1907107/+attachment/5441963/+files/2020-12-08T13%3A28%3A16%2C955532233+01%3A00.png
--
You received this bug notification
Actually, its gdm which runs on tty1, as i did not enabled lightdm...
but it doesnt change the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907107
Title:
cloud-init runs too late at
You can reproduce with that minimal user-data config
#cloud-config
autoinstall:
version: 1
packages:
- lightdm
locale: fr_FR.UTF-8
user-data:
timezone: Europe/Paris
refresh-installer:
update: yes
identity:
hostname: localhost
username: first
password: changeme
As I manually setup a unit which plays with Before=lightdm.service,
maybe it breaks something, i will test and tell later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907107
Title:
cloud-init
I use autoinstall to get my system installed in a specific state, then i need
to boot that state.
I want my tools to use that state (lightdm for exemple), so if cloud-config
needs to run some tasks it should do it before i can interact with my system.
Is that normal that cloud-config starts
I'm marking the cloud-init task invalid for now.
As mentioned in the other bug[1]; cloud-init is not running too late;
rather scripts not provided to cloud-init are not waiting for cloud-init
to complete its execution. If your scripts are using cloud-init status
--wait before executing or
16 matches
Mail list logo
