Automated tests for image validation have now passed for Trusty.
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714299
Title:
walinuxagent update 2.2.16
To
Hi mterry.
RE: test case steps.
This surfaced for me initially while testing on GCE. On GCE NTP servers
are provided via DHCP so the easiest test case is to launch an instance
on GCE without our workaround configured.
One such image is "daily-ubuntu-ntpdebug-1604-xenial-v20170331" in
project "ub
** Description changed:
In 1:4.2.8p3+dfsg-1, the default config was changed to
"Use pool instead of server". This needs a corresponding
update to /etc/dhcp/dhclient-exit-hooks.d/ntp, since the
DHCP specified servers now get added to the default pool
config instead of replacing them.
I have verified that ntp 1:4.2.8p4+dfsg-3ubuntu5.4 in xenial-proposed
passes the test case outlined in the description above.
* Launch GCE instance
* Enabled proposed
* Upgrade ntp
* Reboot
* Confirm `ntpq -p` returns only one entry
** Tags removed: verification-needed
** Tags added: verification
Testing complete and verified for Xenial. Testing of other releases is
still in progress.
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700027
Title:
Update
Testing complete and verified for Zesty. Testing of other releases is
still in progress.
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700027
Title:
Update g
Testing complete and verified for Yakkety. Testing of other releases is
still in progress.
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700027
Title:
Upda
Testing complete and verified for Trusty.
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700027
Trusty, Xenial, Yakkety and Zesty packages have been verified.
All automated tests pass for these suites and manual verification has
also been completed using images built from proposed and also on
instances upgrading packages already installed.
** Tags removed: verification-needed
** Tags added
** Changed in: cloud-images
Milestone: y-2016-07-14 => y-2016-07-28
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581044
Title:
Images ship with modified conffiles
To manage notifications abou
Hi Nish,
lp:1595302 targets Xenial and Yakkety only. The fix needs to be
backported to Trusty too. Patch attached to #3 is for Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581200
Title:
U
smoser has included the fix for this bug in cloud-init for 16.04 but the
attached lp-1581200-gce-metadatafqdn.debdiff patch is still awaiting
sponsorship for inclusion in cloud-init for 14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Hi Max, this is not intentional. I will investigate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581200
Title:
Ubuntu cloud-init expects trailing dot on GCE metadata FQDN
To manage notifications
Hi Max,
When proposed pocket is enabled [1] then 0.7.5-0ubuntu1.20 [2] can be
installed.
This does include the patch.
The cloud-init_0.7.5.orig.tar.gz source archive linked to on [3] is the
source archive before patches are applied.
[1] https://wiki.ubuntu.com/Testing/EnableProposed
[2]
http:/
** Changed in: cloud-images
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581044
Title:
Images ship with modified conffiles
To manage notifications abo
Apologies I forgot to include the version of cloud-init tested.
The version tested was 0.7.5-0ubuntu1.20
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581200
Title:
Ubuntu cloud-init expects trail
I have tested the proposed package and it behaves as expected and fixes
the reported issue.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Changed in: cloud-images
Status: In Progress => 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/1581044
Title:
Images ship with modified conffiles
To manage notifications abou
** Changed in: cloud-images
Milestone: y-2016-06-02 => y-2016-06-16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581044
Title:
Images ship with modified conffiles
To manage notifications abou
** Branch unlinked: lp:~philroche/cloud-init/trunk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581200
Title:
Ubuntu cloud-init expects trailing dot on GCE metadata FQDN
To manage notifications a
** Branch unlinked: lp:~philroche/cloud-init/trunk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581200
Title:
Ubuntu cloud-init expects trailing dot on GCE metadata FQDN
To manage notifications a
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => 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/1581200
Title:
Ubuntu cloud-init expects trailing dot on GCE metadata FQDN
Verification is complete and GCE have given +1 on 20190124 packages
migrating to -updates
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic verification-needed-trusty verification-needed-xenial
** Tags added: verification-done verification-done-bionic
ver
We (CPC) are seeing this issue too when trying to build Trusty non
amd64/i386 images.
When we hit this yesterday Security team confirmed that ESM doesn't
support other arches but we shouldn't block builds because of this
change.
--
You received this bug notification because you are a member of U
** Tags removed: block-proposed-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061017
Title:
lxd-installer: permission error not handled and lxd snap not installed
To manage notifications abo
@sdeziel exactly yes. We will try get the other livecd-rootfs Noble bugs
released now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061017
Title:
lxd-installer: permission error not handled and lx
block-proposed-noble tag removed now as the other Noble livecd-rootfs
bugs have been fix-released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061017
Title:
lxd-installer: permission error not ha
For context the image @jibel tested was https://partner-
images.canonical.com/hyper-v/desktop/oracular/20240522/
@jibel I will start SRU to noble now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064
** Description changed:
The LXD snap is no longer seeded in any images since Noble+ so the
unminimize logic in https://git.launchpad.net/livecd-rootfs/tree/live-
build/auto/build?h=ubuntu/noble#n290 and
https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-
server/hooks/01-unmin
** Description changed:
The LXD snap is no longer seeded in any images since Noble+ so the
unminimize logic in https://git.launchpad.net/livecd-rootfs/tree/live-
build/auto/build?h=ubuntu/noble#n290 and
https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-
server/hooks/01-unmin
** Description changed:
The LXD snap is no longer seeded in non minimal images since Noble+ so
the unminimize logic related to LXD snap @
https://git.launchpad.net/ubuntu/+source/unminimize/tree/unminimize?h=applied/ubuntu/noble#n108
is no longer required.
lxd-installer can remain in
Now in noble unapproved queue
https://launchpad.net/ubuntu/noble/+queue?queue_state=1&queue_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066905
Title:
LXD snap no longer seeded
Now in noble unapproved queue
https://launchpad.net/ubuntu/noble/+queue?queue_state=1&queue_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064280
Title:
Hyperv desktop images no
** Also affects: cloud-images
Importance: Undecided
Status: New
** Changed in: cloud-images
Assignee: (unassigned) => Gauthier Jolly (gjolly)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
MP with catred's proposed changes @
https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd-
rootfs/+merge/463488
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059730
Title:
Focal 5.15 kern
MP with catred's proposed changes @
https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd-
rootfs/+merge/463488
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052789
Title:
AppArmor profil
Focal livecd-rootfs `2.664.53` with these proposed changes now in upload
queue
https://launchpad.net/ubuntu/focal/+queue?queue_state=1&queue_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Focal livecd-rootfs `2.664.53` with these proposed changes now in upload
queue
https://launchpad.net/ubuntu/focal/+queue?queue_state=1&queue_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Verified Focal:
This exact proposed version of livecd-rootfs has been used in cloud
image build for many weeks now and has met all of the steps listed in
the test plan.
GCE daily minimal image daily-ubuntu-minimal-2004-focal-v20240405``
being one such image with snaps and built using this version
Verified Focal:
This exact proposed version of livecd-rootfs has been used in cloud
image build for many weeks now and has met all of the steps listed in
the test plan.
GCE daily minimal image daily-ubuntu-minimal-2004-focal-v20240405``
being one such image with snaps and built using this version
Assignee: Catherine Redfield (catred)
Status: New
** Also affects: livecd-rootfs (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu Noble)
Assignee: (unassigned) => Philip Roche (philroche)
** Changed in: livecd-rootfs (Ubuntu No
Public bug reported:
Recent Mantic cloud image builds fail - see
https://launchpad.net/~cloudware/+livefs/ubuntu/mantic/cpc/+build/604087
build log for an example.
```
+ UBUNTU_STORE_ARCH=amd64 SNAPPY_STORE_NO_CDN=1 snap download
--cohort=MSAqIDE3MTI5MDgwNDcgNWIzNmM3MmIwYjVmNDIyMjQ5Y2NmY2JhNjA4M
This does not affect Noble as we no longer preseed LXD in >=Noble
** Also affects: livecd-rootfs (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu Mantic)
Assignee: (unassigned) => Philip Roche (philroche)
** Description changed:
Public bug reported:
* Canonical Public Cloud discovered that `chronyc -c sources` now fails with
`506 Cannot talk to daemon` with the latest kernels. We are seeing this in
linux-azure and linux-gcp kernels (6.8.0-1005.5)
* Disabling AppArmor (`sudo systemctl stop apparmor`) completely results i
** Also affects: chrony (Ubuntu)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: chrony (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecid
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oracle (Ubuntu)
Importance:
** Changed in: livecd-rootfs (Ubuntu)
Status: Confirmed => 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/2062024
Title:
armhf doesn't build disk-image-uefi
To manage notificati
Public bug reported:
Azure testing has reported an issue following update of the nullboot
package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am informed
included the vendoring of snapd 2.62.
This has caused a regression and TPM backed FDE instances no longer boot
as expected.
There are report
This is a 24.04 release blocking bug as it is a regression and results
in a failure to boot for TPM backed FDE instances.
** Description changed:
Azure testing has reported an issue following update of the nullboot
package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am informed
included t
I have removed references to desktop FDE from the description. Thank you
for testing.
** Description changed:
Azure testing has reported an issue following update of the nullboot
package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am informed
included the vendoring of snapd 2.62.
Thi
** Changed in: snapd (Ubuntu Noble)
Status: New => Invalid
** Changed in: linux-aws (Ubuntu Noble)
Status: New => Fix Released
** Changed in: linux-azure (Ubuntu Noble)
Status: New => Fix Released
** Changed in: linux-gcp (Ubuntu Noble)
Status: New => Fix Released
**
** Also affects: linux-gcp (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063315
Title:
Suspend & Resume functionality broken/timesout in G
Public bug reported:
The recent change in Ubuntu 24.04 and needrestart which results in
services being restarted automatically , details @
https://discourse.ubuntu.com/t/noble-numbat-release-
notes/39890#services-restart-on-unattended-upgrade-26, has resulted in
unexpected behaviour on Google GCE
This issue affects Oracular/24.10 too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061121
Title:
Mantic preseeding of LXD using incorrect track/channel
To manage notifications about this bug go
Verification done for Mantic now.
* Successfully built image with LXD preseeded with these changes
* confirmed LXD is preseeded/installed and works as expected.
* Confirmed that preseeding other snap like google-cloud-cli for example in
the GCE images continues to preseed as expected.
** Tags
oem-config to the new provisioning
stack but this is out of scope of this bug.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
** Affects: livecd-rootfs (Ubuntu Noble)
Importance: Undecided
Assignee: Philip Roche (philroche)
Status: New
** Also
Public bug reported:
Following on from previous similar package update requests @ LP:
#2020762, LP: #1996735, LP: #1938553 and LP: #1911689 this bug is a
request to update the google-osconfig-agent to the upstream version
`20240320.00` @
https://github.com/GoogleCloudPlatform/osconfig/releases/tag
The xenial and bionic target is the ESM repos
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064580
Title:
Please update the package to 20240320.00
To manage notifications about this bug go to:
htt
Public bug reported:
[Impact]
* Unable to build armhf Ubuntu 21.10 cloud images due to 'No space left
on device' errors. See attached build log snippet for details on the
disk space errors.
* The fix has landed upstream in the livecd-rootsfs master branch
https://git.launchpad.net/livecd-
root
MP now created https://code.launchpad.net/~philroche/livecd-
rootfs/+git/livecd-rootfs/+merge/412892
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953609
Title:
[SRU] Bump disk image size for amhf
Test build with this patch was successful - see private build
https://launchpad.net/~cloudware/+livefs/ubuntu/impish/cpc/+build/314665
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953609
Title:
[S
** Description changed:
[Impact]
- * Unable to build armhf Ubuntu 21.10 cloud images due to 'No space left
+ * Unable to build armhf Ubuntu 21.10 cloud images due to 'No space left
on device' errors. See attached build log snippet for details on the
disk space errors.
- * The fix ha
As verification I have successfully built and published Ubuntu 21.10
Impish armhf cloud images with this patch applied as in -proposed.
http://cloud-images.ubuntu.com/impish/20211208.1/
Note that armhf downloads are present and have passed all available
testing.
** Tags removed: verification-nee
Subscribing ubuntu-release as per FFE policy. This bug affects noble
cloud image release
** Also affects: ubuntu-advantage-desktop-daemon (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Subscribing ubuntu-release as per FFE policy. This bug affects noble
cloud image release
** Also affects: software-properties (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Subscribing ubuntu-release as per FFE policy. This bug affects noble
cloud image release
** Also affects: wsl-pro-service (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Subscribing ubuntu-release as per FFE policy. This bug affects noble
cloud image release
** Also affects: update-manager (Ubuntu Noble)
Importance: Wishlist
Assignee: Calvin Mwadime Makokha (calvinmwadime)
Status: Triaged
--
You received this bug notification because you are a mem
Test plan updated for Jammy too
** Description changed:
After the kernel roll to linux-gcp-5.15 to version
5.15.0-1051.59_20.04.1 the public cloud team pre publication test were
failing on our snap_preseed_optimized test which checks to ensure that
snaps are preseeded correctly
This
@holmanb
> google-startup-scripts.service starts well after the network is online
You are correct. I have updated the bug description now.
> due to configuration via cloud-init not being fully completed, apt
sources for example, when startup scripts are run
** Description changed:
- New GCP da
** Also affects: google-guest-agent (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: google-guest-agent (Ubuntu Noble)
Importance: Undecided
Status: Confirmed
** Also affects: google-guest-agent (Ubuntu Mantic)
Importance: Undecided
Status: New
**
Now uploaded to Jammy queue @
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052789
Title:
AppArmor profiles missing
Jammy fix is still awaiting review @
https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd-
rootfs/+merge/460929
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052789
Title:
AppArmor profi
Public bug reported:
[ Impact ]
* It is not possible to upgrade or re-install python-apt using pip from
the git+ssh://git.launchpad.net/ubuntu/+source/python-apt git repo if
already installed and if wheel installed too.
* On initial install it also is assigned version `0.0.0` which is
incorre
Subscribing ubuntu-release as per FFE policy. This bug will block noble
cloud image release
** Also affects: livecd-rootfs (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Based on vorlon's comments above and so as not to delay SRU I am marking
this as verified
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
I have created a test noble minimal cloud image with the -proposed
livecd-rootfs 24.04.71 and also successfully confirmed that `unminimize`
no longer attempts to install the LXD snap.
I built the cloud image in launchpad and tested using qemu.
Marking as verification-done
** Tags removed: verifi
Adding `block-proposed-noble` tag as the changes in
https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd-
rootfs/+merge/466388 actually remove all of unminimize calls - not just
the lxd specific changes. I will create bug to track this.
** Tags added: block-proposed-noble
--
You recei
Public bug reported:
There was a change made by me in
https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd-
rootfs/+merge/466388 as part of LP: #2066905 to remove references to LXD
in the unminimize scripts but I also removed the calls to `unminimize`
in error.
This still needs to run
** Summary changed:
- Revert removal of yes /usr/local/sbin/unminimize call in server builds
+ Revert removal of unminimize call in server builds
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069828
** Also affects: livecd-rootfs (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: livecd-rootfs (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu Jammy)
Status: New => In Progress
** Changed in: livecd-rootfs (Ubuntu
I have marked Oracular "Invalid" as this is specific to the 6.5 which is
not available in oracular
** Changed in: livecd-rootfs (Ubuntu Oracular)
Status: New => Won't Fix
** Changed in: livecd-rootfs (Ubuntu Oracular)
Status: Won't Fix => Invalid
--
You received this bug notificat
I have marked Oracular "Invalid" as this is specific to the releases
prior to Noble where preseeding of LXD was still supported
** Changed in: livecd-rootfs (Ubuntu Oracular)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
LP: #2069828 (https://bugs.launchpad.net/ubuntu/+source/livecd-
rootfs/+bug/2069828) was created to track the regression. The fix to LP:
#2069828 is now in version 24.04.72 which is now in -proposed and will
be verified. As such I am removing `block-proposed-noble` tag as lack of
verification of 24
Based on vorlon's comments above and so as not to delay SRU I am marking
this as verified
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
From ubuntu-server daily live image build 20240628 @
https://cdimage.ubuntu.com/ubuntu-server/noble/daily-live/20240628/ with
amd64 build @ https://launchpad.net/~ubuntu-
cdimage/+livefs/ubuntu/noble/ubuntu-server-live/+build/642557 with these
changes and I can confirm:
* from the build log that 2
From ubuntu-server daily live image build 20240628 @
https://cdimage.ubuntu.com/ubuntu-server/noble/daily-live/20240628/ with
amd64 build @ https://launchpad.net/~ubuntu-
cdimage/+livefs/ubuntu/noble/ubuntu-server-live/+build/642557 with these
changes and I can confirm:
* from the build log that 2
I have verified again - using livecd-rootfs 24.04.72 which is currently
in -proposed.
I built test image on launchpad and created a VM in Hyper-V manager.
I went through oem-config, the desktop environment started. I could
update and install package. The machine also rebooted successfully.
Marki
** Changed in: livecd-rootfs (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052789
Title:
AppArmor profiles missing in kernel 5.15.0-1051+ relea
The changes proposed here in Noble lxd-installer 4ubuntu0.1 have caused
server builds to fail
```
Invoking LXD so that it can be installed by the lxd-installer's script..
Unable to trigger the installation of the LXD snap.
Please make sure you're a member of the 'lxd' system group.
```
This is be
Full failing build log @
https://launchpadlibrarian.net/731241044/buildlog_ubuntu_noble_amd64_ubuntu-
server-live_BUILDING.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061017
Title:
lxd-ins
Mantic livecd-rootfs 23.10.60 has now been uploaded to SRU queue @
https://launchpad.net/ubuntu/mantic/+queue?queue_state=1&queue_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20629
Jammy livecd-rootfs 2.765.42 has now been uploaded to SRU queue @
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062929
@sdeziel thank you for debugging.
+1 on moving to `/usr/sbin/lxd` instead of `/sbin/lxd` if possible thus
removing the need for any livecd-rootfs changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
The LXD snap is no longer seeded in non minimal images since Noble+ so
the unminimize logic related to LXD snap @
https://git.launchpad.net/ubuntu/+source/unminimize/tree/unminimize?h=applied/ubuntu/noble#n108
is no longer required.
lxd-installer can remain installed.
This a
Public bug reported:
The LXD snap is no longer seeded in non minimal images since Noble+ so
the unminimize logic in https://git.launchpad.net/livecd-
rootfs/tree/live-build/auto/build?h=ubuntu/noble#n290 and
https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-
server/hooks/01-unminimize
Does the solution to this bug include making the SBOMs public @
https://cloud-images.ubuntu.com/ ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077105
Title:
cloud-images do not produce sboms
To
That is unfortunate. Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077105
Title:
cloud-images do not produce sboms
To manage notifications about this bug go to:
https://bugs.launchpad.net/c
101 - 197 of 197 matches
Mail list logo
