** Changed in: ubuntu-meta (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-image (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It worked! I must have flashed the wrong image, Thank you so much for
taking the time! And Thanks to everyone that worked on this!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
@noahod I've just tried this with the current
https://cdimage.ubuntu.com/ubuntu-server/daily-
preinstalled/current/jammy-preinstalled-server-arm64+raspi.img.xz image
(downloaded today) and with just your growpart config (I didn't try the
resize_rootfs key), the card booted without resizing the
I tried
growpart:
mode: off
devices: ['/']
and separately:
resize_rootfs: false
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth on first boot on
Did you disable it in user-data?
cloud-initramfs-growroot is no longer installed per the manifest
https://cdimage.ubuntu.com/ubuntu-server/daily-
preinstalled/current/jammy-preinstalled-server-amd64.manifest
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ah never mind I looked at the amd64 image manifest, not raspi :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth on first boot on impish for raspberry pi
Should these changes be in the daily's already?
I just checked with https://cdimage.ubuntu.com/ubuntu-server/daily-
preinstalled/current/jammy-preinstalled-server-arm64+raspi.img.xz
downloaded today,
And got the same result as before, growroot runs and expands the
partition..
--
You received
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth on first boot on impish for
Not an expert in seeds, but the changes made sense. Merged and pushed!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth on first boot on impish for raspberry
** Tags added: fr-2147
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth on first boot on impish for raspberry pi
To manage notifications about this bug go
Thank you so much! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth on first boot on impish for raspberry pi
To manage notifications about this bug go
** Merge proposal linked:
https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/417157
** Merge proposal linked:
https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/417158
--
You received this bug notification because you are a member of
Sorry, this slipped off my radar -- I'll get on with the required PRs
today
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth on first boot on impish for
I'm worried about this being baked into the 22.04 LTS and then I can't
use a stable LTS Raspberry Pi distro I can use for another 3 years or
so..
Is there anything I can do to help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@xnox Ah, that makes sense, thanks. I'll propose some seed updates in a
bit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth on first boot on impish for
systemd stuff did either partition or fs but not both.
we used the cloud initramfs implementation on the desktop, because yes,
it doesn't do cloud-init.
probably moving that out of the common seed will help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hmmm, I wonder if this is in the seeds, given we *finally* got around to
using the platform seeds to build the impish image (the intention was to
do this in hirsute, and they were ready but for some reason they were
never activated on that release).
Ah ha! Here's the culprit:
@noahod, I'm looking into it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth on first boot on impish for raspberry pi
To manage notifications about this
Thanks, I understand that cloud-init package isn't doing anything wrong.
I've cross-posted here in the hopes that someone can give me a lead as
to where to find what changed between releases and how to proceed.
https://github.com/snapcore/pi-gadget/issues/85
Cheers
** Bug watch added:
@Noah,
cloud-init isn't doing anything wrong. Its working as designed.
'growroot', which is provided by cloud-initramfs-tools (upstream [1],
package [2]) also didn't do anything wrong. It's sole purpose in the
initramfs is to do what it is doing.
I'm not sure what code creates the image you've
Thanks for looking into this!
I was hoping to create an IoT package that was agnostic of which device
I deploy it on to, and cloud-init is great for this because it gives me
a universal API for provisioning that's supposed to work across all
ubuntu flavors and even other distros...
So for
> I thought cloud-initramfs-growroot was solely used with old kernels that
> can't resize mounted
> filesystems but I could be wrong. Wondering though why we install that
> package all of a sudden.
that is another option, to remove cloud-initramfs-growroot from the
image/initrd.
The problem
@Noah,
The image you pointed at there has the package 'cloud-initramfs-growroot'
in its initramfs. cloud-initramfs-growroot is going to run growpart on the
root filesystem during the initramfs unless one of the following files
exists on the root filesystem:
/var/lib/cloud/instance/root-grown
The reason for this behavior is that cloud-initramfs-growroot is
installed since Impish which adds an initramfs hook to do the resizing,
long before cloud-init runs. Disabling it in user-data won't do
anything.
I thought cloud-initramfs-growroot was solely used with old kernels that
can't resize
I tried this again on the latest Raspberry Pi daily for Jammy, downloaded from
here today (20210216):
https://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/current/jammy-preinstalled-server-arm64+raspi.img.xz
The issue persists. Can anyone suggest how I can get this assigned to
the right
** 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.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth on first boot on impish for raspberry pi
linux-raspi is the kernel package but this isn't a kernel problem
** Changed in: linux-raspi (Ubuntu)
Status: New => Invalid
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => New
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
27 matches
Mail list logo
