[Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Promotion from -proposed sure would be nice. I see verification has been done but a update excuses shows an netplan.io regression[1]. I'm not sure if the test is flaky but I see that seb retried it a few times[2] last week and it failed consistently, so maybe not. I'm just curious if there's any status on the test failure. (Also, I started writing this thinking it had been a month but it's been less than a week and I can't tell time. I know it wouldn't be promoted with less than a week in -proposed anyway.) [1] https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#wpa [2] https://autopkgtest.ubuntu.com/packages/netplan.io/jammy/arm64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Thank you Seb, I had the issue reported in this bug in a WeWork today (first time connecting since updating to Jammy) and the package in -proposed resolved the issue for me as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962018] [NEW] pypy3compile errors during postinst confuses user
Public bug reported: Could you add some clarifying output in the postinst around pypy3compile failures to give context to an end user? The errors as they stand don't indicate that this is pyp3 specific and can be concerning (they also give the impression that QA isn't catching basic python bugs which isn't the case). pypy3 support was added to dh-python3 towards the end of 2018 as "WIP" such that postinst will call `pypy3compile $PACKAGE || true` to ignore errors if pypy3 is installed. I was talking with a user that saw this fail when installing an update for python3-software-properties and the error message was cause for concern and confusion, for that package it looked like this: Setting up python3-software-properties (0.99.19) ... Failed to byte-compile /usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py: File "/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", line 436 def __init__(self, sourceslist=None, /, files=None): ^ SyntaxError: invalid syntax (expected ')') That's all fine, the author has introduced the positional-only parameter (PEP570) new to python 3.8 and that's supported in cpython shipped by default in the distro, but it isn't supported by pypy3. I think it's reasonable for the maintainer of a package to decide that they want to use new features and that they might not have testing with pypy3 installed as a requirement. The fact that the failure is pypy3compile and not python3compile isn't communicated for the failure nor that it's optional. The user might think that the package is broken for the default interpreter. Would you consider adding a message before each compilation step to call out which interpreter is byte-compiling the module as well as pypy3 being optional/best-effort and may fail? Preferably you might also indicate the impact (i.e. the package is usable with the system python3 interpreter but pypy3) to set expectations with the end user. Thank you Piotr! ** Affects: dh-python (Ubuntu) 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/1962018 Title: pypy3compile errors during postinst confuses user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1962018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923832] Re: Provide generic preinstalled images for arm64, amd64
Where are you expecting to ship these images from? I'm concerned about the hard-coded password and I want to ensure people know what they're getting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923832 Title: Provide generic preinstalled images for arm64, amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1923832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881006] Re: Incorrect ESP mount options
The autopkgtest regression noted in comment #17 was due to an ephemeral failure trying to reach people.canonical.com for seeds: ! Could not open (any of): ! http://people.canonical.com/~ubuntu-archive/seeds/ubuntu.focal/desktop-minimal-zh ! http://people.canonical.com/~ubuntu-archive/seeds/ubuntu.focal/languages/desktop-minimal-zh ! http://people.canonical.com/~ubuntu-archive/seeds/platform.focal/desktop-minimal-zh A retry of the build succeeded, SRU should proceed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881006 Title: Incorrect ESP mount options To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1881006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Milestone: None => ubuntu-21.04 ** Tags added: rls-hh-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919177 Title: Azure: issues with accelerated networking on Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1919177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915345] Re: [SRU] eic_harvest_hostkeys fails in local zones
I've left a comment in the upstream bug https://github.com/aws/aws-ec2 -instance-connect-config/issues/28#issuecomment-816650597 regarding my SRU test feedback. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915345 Title: [SRU] eic_harvest_hostkeys fails in local zones To manage notifications about this bug go to: https://bugs.launchpad.net/ec2-instance-connect/+bug/1915345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915345] Re: [SRU] eic_harvest_hostkeys fails in local zones
I have tested in AWS local zone us-west-2-lax-1a
xenial:
image: ami-008b09448b998a562
build serial: 20201014
ec2-instance-connect 1.1.12+dfsg1-0ubuntu3~16.04.2
bionic:
image: ami-02701bcdc5509e57b
build serial: 20210224
ec2-instance-connect 1.1.12+dfsg1-0ubuntu3~18.04.2
focal:
image: ami-0ca5c3bd5a268e7db
build serial: 20210223
ec2-instance-connect 1.1.12+dfsg1-0ubuntu3.20.04.1
groovy:
image: ami-0c1204e0c5e73ef4c
build serial: 20210325
ec2-instance-connect 1.1.12+dfsg1-0ubuntu3.20.10.1
Are you sure this is right? Yes, the systemd unit no longer fails
because the patch ignored the script failure, but does it *work*? The
package update has no changes to /usr/share/ec2-instance-
connect/eic_harvest_hostkeys to match the string format for a local zone
still. So while the feature is available in local and wavelength zones
the package in -proposed fails to address the underlying failure and so
ec2-instance-connect still broken in those zones (just silently now).
Again, here is the failure:
$ sudo sh -x /usr/share/ec2-instance-connect/eic_harvest_hostkeys 2>&1 | tail -9
+ /usr/bin/curl -s -f -m 1 -H X-aws-ec2-metadata-token:
AQAEAF6AxckVUQFPqe3ivPjLa0b7dlvf4To2TaAReHD-lMpqgvuXBQ==
http://169.254.169.254/latest/meta-data/placement/availability-zone/
+ zone=us-west-2-lax-1b
+ zone_exit=0
+ [ 0 -ne 0 ]
+ /bin/echo us-west-2-lax-1b
+ /usr/bin/head -n 1
+ /bin/grep -Eq ^([a-z]+-){2,3}[0-9][a-z]$
+ exit 255
+ rm -rf /dev/shm/eic-hostkey-WZBt1Vck
Please look at the grep on line 101 of the script:
# Validate the zone
/bin/echo "${zone}" | /usr/bin/head -n 1 | /bin/grep -Eq
"^([a-z]+-){2,3}[0-9][a-z]$" || exit 255
The script needs to handle matches to the existing regex, but also local
zones like 'us-west-2-lax-1b' and wavelength zones like 'us-west-2-wl1
-den-wlz-1'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915345
Title:
[SRU] eic_harvest_hostkeys fails in local zones
To manage notifications about this bug go to:
https://bugs.launchpad.net/ec2-instance-connect/+bug/1915345/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915345] Re: [SRU] eic_harvest_hostkeys fails in local zones
** Tags removed: verification-needed verification-needed-focal verification-needed-groovy verification-needed-xenial ** Tags added: verification-failed verification-failed-focal verification-failed-groovy verification-failed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915345 Title: [SRU] eic_harvest_hostkeys fails in local zones To manage notifications about this bug go to: https://bugs.launchpad.net/ec2-instance-connect/+bug/1915345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920043] Re: Latest Focal Minimal disk images from livecd-rootfs do not boot
This is fixed in devel in changes that span multiple commits and this bit was omitted from the backport of those changes (which broke focal images) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920043 Title: Latest Focal Minimal disk images from livecd-rootfs do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1920043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902103] Re: Ensure default fstab options are sane and consistent across all images
@gjolly, I've taken a look at the 'Where problems could occur' section of the SRU template and I'm concerned about the risk of regression for users altering mount options for the root file system. My concerns involve the root filesystem line alone. I think 'discard' is nice-to-have but not worth the risk of breaking users that alter the line via code. I'm not convinced we should change the error option from 'continue' to 'remount-ro' in an SRU either; first because it could break automation that users have to change the line and second it changes behavior for error handling that could break user assumptions of systems already in production should they deploy with a newly built image and they'll be unlikely to have image qualification tests that trigger an IO error. I recommend SRU'ing without the changes for the root filesystem. The change to the fstab line for the EFI file system pertains to a security improvement which I like to see. I think the risk is much lower that a user has automation changing mount options for this file system. The other risk is one of behavior. Will users have a non-root user accessing the EFI mountpoint and be broken by this change? Given the contents of the file system I don't believe it's unlikely most users would be accessing this directly. I believe the benefit from the change justifies the umask SRU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902103 Title: Ensure default fstab options are sane and consistent across all images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1902103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902103] Re: Ensure default fstab options are sane and consistent across all images
** Description changed: [Impact] * In cloud images, the ESP is currently mounted with default (0755) permissions. This means anyone can read the ESP partition. This can cause security issues as sensitive data might be put in this partition[0] * The root filesystem partition uses defaults mount options. In case of filesystem error, it is safer to use `remount-ro`. Also for cloud usage (where storage can be expensive) it makes sense to mount the root filesystem with `discard`. This will also align cloud images fstab with what we have elsewhere. [Test Plan] - * Start a GCE or a KVM instance + * Build an uefi image from the ubuntu-cpc project in livecd-rootfs + + * Launch in KVM * Check `/etc/fstab` content + + * Check that mount options are reflected in 'mount' command output + + * Ensure a non-root user can not access /boot/efi + + * Check 'tune2fs -l $root_fs_dev' output for 'Error behavior' to match + remount-ro [Where problems could occur] * Some users can have automation in place change those defaults. This change might break their automation. * `error=remount-ro` might create issues for certain user. Especially if the filesystem superblock default was set to `error=continue`. For those users, any error that was previously ignored will make the filesystem read-only. * `discard` parameter might have an impact on i/o throughput and reduce read/write speed. Also some particular disk might have issues with TRIM commands[1]. [original description] The default fstab entries for ubuntu cloud images are: LABEL=cloudimg-rootfs / ext4 defaults 0 0 LABEL=UEFI /boot/efi vfat defaults 0 0 These entries do not align with the defaults that we use elsewhere. We should decide on the defaults for fstab, and apply those consistently across all Ubuntu images. -- quoted from ~xnox: I expect [these entries] to be: LABEL=cloudimg-rootfs / ext4 discard,errors=remount-ro 0 1 LABEL=UEFI /boot/efi vfat umask=0077 0 1 - [0] https://bugs.launchpad.net/cloud-images/+bug/1881006/comments/11 [1] https://wiki.debian.org/SSDOptimization#WARNING ** Description changed: [Impact] * In cloud images, the ESP is currently mounted with default (0755) permissions. This means anyone can read the ESP partition. This can cause security issues as sensitive data might be put in this partition[0] * The root filesystem partition uses defaults mount options. In case of filesystem error, it is safer to use `remount-ro`. Also for cloud usage (where storage can be expensive) it makes sense to mount the root filesystem with `discard`. This will also align cloud images fstab with what we have elsewhere. [Test Plan] - * Build an uefi image from the ubuntu-cpc project in livecd-rootfs + * Build an uefi image from the ubuntu-cpc project in livecd-rootfs * Launch in KVM * Check `/etc/fstab` content - * Check that mount options are reflected in 'mount' command output + * Check that mount options are reflected in 'mount' command output - * Ensure a non-root user can not access /boot/efi - - * Check 'tune2fs -l $root_fs_dev' output for 'Error behavior' to match - remount-ro + * Ensure a non-root user can not access /boot/efi [Where problems could occur] * Some users can have automation in place change those defaults. This change might break their automation. * `error=remount-ro` might create issues for certain user. Especially if the filesystem superblock default was set to `error=continue`. For those users, any error that was previously ignored will make the filesystem read-only. * `discard` parameter might have an impact on i/o throughput and reduce read/write speed. Also some particular disk might have issues with TRIM commands[1]. [original description] The default fstab entries for ubuntu cloud images are: LABEL=cloudimg-rootfs / ext4 defaults 0 0 LABEL=UEFI /boot/efi vfat defaults 0 0 These entries do not align with the defaults that we use elsewhere. We should decide on the defaults for fstab, and apply those consistently across all Ubuntu images. -- quoted from ~xnox: I expect [these entries] to be: LABEL=cloudimg-rootfs / ext4 discard,errors=remount-ro 0 1 LABEL=UEFI /boot/efi vfat umask=0077 0 1 [0] https://bugs.launchpad.net/cloud-images/+bug/1881006/comments/11 [1] https://wiki.debian.org/SSDOptimization#WARNING ** Description changed: [Impact] * In cloud images, the ESP is currently mounted with default (0755) permissions. This means anyone can read the ESP partition. This can cause security issues as sensitive data might be put in this partition[0] * The root filesystem partition uses defaults mount options. In case of filesystem error, it is safer to use `
[Bug 1918190] Re: Enabling/Disabling VPN crashes window manager
@3v1n0 (Marco Trevisan) has pointed out
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1651 as a
possible fix
** Description changed:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description: Ubuntu Hirsute Hippo (development branch)
Release: 21.04
$ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk
-F= '{print $2}'
wayland
$ apt-cache policy network-manager
network-manager:
Installed: 1.30.0-1ubuntu1
Candidate: 1.30.0-1ubuntu1
Version table:
*** 1.30.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy gnome-shell
gnome-shell:
- Installed: 3.38.3-3ubuntu1
- Candidate: 3.38.3-3ubuntu1
- Version table:
- *** 3.38.3-3ubuntu1 500
- 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
- 100 /var/lib/dpkg/status
+ Installed: 3.38.3-3ubuntu1
+ Candidate: 3.38.3-3ubuntu1
+ Version table:
+ *** 3.38.3-3ubuntu1 500
+ 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
+ 100 /var/lib/dpkg/status
+
+ $ dpkg-query -W|grep mutter
+ gir1.2-mutter-7:amd64 3.38.3-3ubuntu1
+ libmutter-7-0:amd64 3.38.3-3ubuntu1
+ mutter3.38.3-3ubuntu1
+ mutter-common 3.38.3-3ubuntu1
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 8 14:12:44 2021
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-04-21 (1416 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
RebootRequiredPkgs:
libssl1.1
libssl1.1
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.30.0 connected started full enabled enabled
disabled enabled enabled
** Also affects: mutter (Ubuntu)
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/1918190
Title:
Enabling/Disabling VPN crashes window manager
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918190/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918190] Re: Enabling/Disabling VPN crashes window manager
As a workaround for anyone, you can use nmcli to bring up a VPN connection. Run `nmcli c` to get a list of connections, once you have the name you can enable it with `nmcli c up $name` or disable it with `nmcli c down $name`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918190 Title: Enabling/Disabling VPN crashes window manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918190] Re: Enabling/Disabling VPN crashes window manager
This looks to be around the time of the issue where I disabled a VPN
connection (from syslog):
Mar 8 14:11:54 splat gnome-shell[677801]: **
Mar 8 14:11:54 splat gnome-shell[677801]:
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
assertion failed: (!clutter_actor_get_reactive (actor))
Mar 8 14:11:54 splat gnome-shell[677801]: Bail out!
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
assertion failed: (!clutter_actor_get_reactive (actor))
Mar 8 14:11:54 splat gnome-shell[677801]: GNOME Shell crashed with signal 6
Mar 8 14:11:54 splat gnome-shell[677801]: == Stack trace for context
0x556edc56f150 ==
Mar 8 14:11:54 splat gnome-shell[677801]: #0 556edea1ffc0 i
resource:///org/gnome/shell/ui/popupMenu.js:390 (1162dc8fad80 @ 138)
Mar 8 14:11:54 splat gnome-shell[677801]: #1 556edea1ff18 i
resource:///org/gnome/shell/ui/status/network.js:1429 (2ab06bf803d0 @ 171)
Mar 8 14:11:54 splat gnome-shell[677801]: #2 556edea1fe80 i
resource:///org/gnome/shell/ui/status/network.js:171 (2ab06bf82560 @ 111)
Mar 8 14:11:54 splat gnome-shell[677801]: #3 7ffef0da2770 b
self-hosted:850 (b5d5c736d80 @ 454)
Mar 8 14:11:54 splat gnome-shell[677801]: #4 556edea1fde0 i
resource:///org/gnome/shell/ui/popupMenu.js:411 (1162dc8face0 @ 56)
Mar 8 14:11:54 splat gnome-shell[677801]: #5 556edea1fd48 i
resource:///org/gnome/shell/ui/popupMenu.js:398 (1162dc8fad30 @ 41)
Mar 8 14:11:54 splat gnome-shell[677801]: #6 556edea1fca8 i
resource:///org/gnome/shell/ui/popupMenu.js:138 (1162dc8fb4c0 @ 88)
Mar 8 14:11:54 splat systemd[1]: Starting Network Manager Script Dispatcher
Service...
Mar 8 14:11:54 splat dbus-daemon[1286]: [system] Successfully activated
service 'org.freedesktop.nm_dispatcher'
** Attachment added: "journal"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1918190/+attachment/5474636/+files/journal
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description: Ubuntu Hirsute Hippo (development branch)
Release: 21.04
$ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk
-F= '{print $2}'
wayland
$ apt-cache policy network-manager
network-manager:
- Installed: 1.30.0-1ubuntu1
- Candidate: 1.30.0-1ubuntu1
+ Installed: 1.30.0-1ubuntu1
+ Candidate: 1.30.0-1ubuntu1
+ Version table:
+ *** 1.30.0-1ubuntu1 500
+ 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
+ 100 /var/lib/dpkg/status
+
+ $ apt-cache policy gnome-shell
+ gnome-shell:
+ Installed: 3.38.3-3ubuntu1
+ Candidate: 3.38.3-3ubuntu1
Version table:
- *** 1.30.0-1ubuntu1 500
+ *** 3.38.3-3ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 8 14:12:44 2021
IfupdownConfig:
- # interfaces(5) file used by ifup(8) and ifdown(8)
- auto lo
- iface lo inet loopback
+ # interfaces(5) file used by ifup(8) and ifdown(8)
+ auto lo
+ iface lo inet loopback
InstallationDate: Installed on 2017-04-21 (1416 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
RebootRequiredPkgs:
- libssl1.1
- libssl1.1
+ libssl1.1
+ libssl1.1
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
- RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
- running 1.30.0 connected started full enabled enabled
disabled enabled enabled
+ RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
+ running 1.30.0 connected started full enabled enabled
disabled enabled enabled
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918190
Title:
Enabling/Disabling VPN crashes window manager
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918190/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918190] [NEW] Enabling/Disabling VPN crashes window manager
Public bug reported:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description:Ubuntu Hirsute Hippo (development branch)
Release:21.04
$ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F=
'{print $2}'
wayland
$ apt-cache policy network-manager
network-manager:
Installed: 1.30.0-1ubuntu1
Candidate: 1.30.0-1ubuntu1
Version table:
*** 1.30.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 8 14:12:44 2021
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-04-21 (1416 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
RebootRequiredPkgs:
libssl1.1
libssl1.1
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI
WWAN-HW WWAN
running 1.30.0 connected started full enabled enabled
disabled enabled enabled
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug hirsute wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918190
Title:
Enabling/Disabling VPN crashes window manager
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1918190/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917926] Re: Window focus issues for Xorg sessions in 3.38.3-3ubuntu1
I'm using xorg because wayland has bug #1918189 (can't share terminals in Google Meet) blocking me from using wayland as a daily driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917926 Title: Window focus issues for Xorg sessions in 3.38.3-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918189] [NEW] Can not share gnome-terminal in Google Meet under xwayland
Public bug reported: When running xwayland in Hirsute I am unable to share gnome-terminal windows from Google Meet. In Google Meet running in Chrome v89.0.4389.82 when I select the share a window I do not see my gnome- terminal windows listed as an option to share. Here is what I am running with, I can provide additional package info $ lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 $ apt-cache policy xwayland xwayland: Installed: 2:1.20.10-3ubuntu3 Candidate: 2:1.20.10-3ubuntu3 Version table: *** 2:1.20.10-3ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status I'd be nice to be able to use wayland and have features on par with xorg and right now I have to do this because of bug #1917926 making xorg unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xwayland 2:1.20.10-3ubuntu3 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:03:30 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.10.0-14-generic, x86_64: installed v4l2loopback, 0.12.5, 5.8.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 RebootRequiredPkgs: libssl1.1 libssl1.1 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.M0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.4-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.3.4-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Mon Oct 15 10:44:00 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu2 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute reproducible single-occurrence ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918189 Title: Can not share gnome-terminal in Google Meet under xwayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1918189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915345] Re: eic_harvest_hostkeys fails in local zones
Wavelength zones are described @ https://aws.amazon.com/wavelength/features/#Locations -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915345 Title: eic_harvest_hostkeys fails in local zones To manage notifications about this bug go to: https://bugs.launchpad.net/ec2-instance-connect/+bug/1915345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915345] Re: eic_harvest_hostkeys fails in local zones
And I haven't tested, but this would also fail in Wavelength zones with names in the form `us-east-1-wl1-bos-wlz-1`. Even if instance connect isn't supported in wavelength zones I rather not have the service fail and mark the system status as degraded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915345 Title: eic_harvest_hostkeys fails in local zones To manage notifications about this bug go to: https://bugs.launchpad.net/ec2-instance-connect/+bug/1915345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915345] Re: eic_harvest_hostkeys fails in local zones
** Bug watch added: github.com/aws/aws-ec2-instance-connect-config/issues #28 https://github.com/aws/aws-ec2-instance-connect-config/issues/28 ** Also affects: ec2-instance-connect via https://github.com/aws/aws-ec2-instance-connect-config/issues/28 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915345 Title: eic_harvest_hostkeys fails in local zones To manage notifications about this bug go to: https://bugs.launchpad.net/ec2-instance-connect/+bug/1915345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915345] Re: eic_harvest_hostkeys fails in local zones
This is a problem with "# Validate the zone" logic @ https://git.launchpad.net/ubuntu/+source/ec2-instance- connect/tree/src/bin/eic_harvest_hostkeys?h=applied/ubuntu/hirsute#n92 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915345 Title: eic_harvest_hostkeys fails in local zones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1915345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915345] [NEW] eic_harvest_hostkeys fails in local zones
Public bug reported:
ec2-instance-connect breaks during host key harvesting for instances
launched in local zones[1]. Here are is the relevant debug data:
$ systemctl is-system-running
degraded
$ systemctl list-units --failed
UNIT LOAD ACTIVE SUBDESCRIPTION
● ec2-instance-connect.service loaded failed failed EC2 Instance Connect Host
Key Harvesting
$ journalctl --unit ec2-instance-connect
-- Logs begin at Wed 2021-02-10 22:47:47 UTC, end at Wed 2021-02-10 22:55:46
UTC. --
Feb 10 22:48:16 ip-172-31-51-82 systemd[1]: Starting EC2 Instance Connect Host
Key Harvesting...
Feb 10 22:48:16 ip-172-31-51-82 systemd[1]: ec2-instance-connect.service: Main
process exited, code=exited, status=255/EXCEPTION
Feb 10 22:48:16 ip-172-31-51-82 systemd[1]: ec2-instance-connect.service:
Failed with result 'exit-code'.
Feb 10 22:48:16 ip-172-31-51-82 systemd[1]: Failed to start EC2 Instance
Connect Host Key Harvesting.
$ dpkg-query -l ec2-instance-connect
ii ec2-instance-connect 1.1.13-0ubuntu1 all Configures ssh daemon to
accept EC2 Instance Connect ssh keys
$ lsb_release -c
Codename: hirsute
$ cat /etc/cloud/build.info
build_name: server
serial: 20210208
$ ec2metadata --availability-zone --ami-id
us-west-2-lax-1a
ami-098f71a7a25a0f1f2
$ bash -x /usr/share/ec2-instance-connect/eic_harvest_hostkeys
...
++ /usr/bin/curl -s -f -m 1 -H 'X-aws-ec2-metadata-token:
AQAEAEvStI0Ugwz1C3GQh7oubFTah7bXQllCmFU6BtMI6b6l5zMkVQ=='
http://169.254.169.254/latest/meta-data/placement/availability-zone/
+ zone=us-west-2-lax-1a
+ zone_exit=0
+ '[' 0 -ne 0 ']'
+ /bin/echo us-west-2-lax-1a
+ /bin/grep -Eq '^([a-z]+-){2,3}[0-9][a-z]$'
+ /usr/bin/head -n 1
+ exit 255
[1] https://aws.amazon.com/about-aws/global-infrastructure/localzones/
** Affects: ec2-instance-connect (Ubuntu)
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/1915345
Title:
eic_harvest_hostkeys fails in local zones
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1915345/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914445] Re: Buildd tarball images do not include package manifests
** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Robert C Jennings (rcj) ** Changed in: livecd-rootfs (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914445 Title: Buildd tarball images do not include package manifests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1914445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912595] Re: unminimize shoud run apt with -–no-install-recommends
Based on my prior reply I've marked this as "Won't Fix" as it doesn't match with our plans for the unminimized script per policy on 'recommends'. ** Changed in: cloud-images Status: New => Won't Fix ** Changed in: livecd-rootfs (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912595 Title: unminimize shoud run apt with -–no-install-recommends To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1912595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912595] Re: unminimize shoud run apt with -–no-install-recommends
I've discussed this issue in #ubuntu-devel on IRC[1] and the feedback is that recommends, by policy, are installed for a reason and overriding that should not be part of the unminimize tool. But for your use case there is a solution that could meet your needs. You can set the following in /etc/apt/apt.conf.d/: APT::Install-Recommends "false"; By making this change your image will install without recommends for all apt operations which would give the behavior you're intending for unminimize and your software stack. Leaving that set in the image which you give to developers would have the effect that they would install new packages in the way that you might intend to install them in your builds. You can verify your configuration with the command: $ apt-config dump | grep Install-Recommends APT::Install-Recommends "false"; Recommends are installed by default (since Lucid)[2] while 'suggests' are not installed by default. "Recommends" by debian policy[3][4] is used to "declares a strong, but not absolute, dependency. The Recommends field should list packages that would be found together with this one in all but unusual installations." [1] https://irclogs.ubuntu.com/2021/01/21/%23ubuntu-devel.html [2] https://askubuntu.com/a/18553 [3] https://unix.stackexchange.com/a/77076 [4] https://www.debian.org/doc/debian-policy/ch-relationships.html#binary-dependencies-depends-recommends-suggests-enhances-pre-depends -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912595 Title: unminimize shoud run apt with -–no-install-recommends To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1912595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912595] Re: unminimize shoud run apt with -–no-install-recommends
I've moved this to the livecd-rootfs project which builds the images and contains the unminimize script code. Background: Ubuntu images themselves do install recommends for packages in the base, so re-installing recommends was seen as appropriate to make a stock minimized image look like the unminimized image on which it is based. But I understand your request that you've built atop the minimized image, installing packages with -no-install-recommends and then from that master image you want to create a un-minimized image. We could add an option to the unminimize script to give you --no-install-recommends to match your additions, though that would mean the base contents would not match. I'm going to add a few people to this bug to discuss the design and a solution. ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Project changed: livecd-rootfs => cloud-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912595 Title: unminimize shoud run apt with -–no-install-recommends To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1912595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902103] Re: Ensure default fstab options are sane and consistent across all images
Adding the cloud-images project so that a test can be added once this change lands in livecd-rootfs ** Also affects: cloud-images 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/1902103 Title: Ensure default fstab options are sane and consistent across all images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1902103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896755] Re: Backport snap-preseed work from groovy to focal
With snapd 2.48 in the store and in the archive we have built test images from the ubuntu-cpc project and verified that snaps are preseeded in the image resulting in reduced seed times during first boot. I'm removing the block and marking this as verification done. ** Tags removed: block-proposed-focal verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896755 Title: Backport snap-preseed work from groovy to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1896755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
** Also affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: open-vm-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: open-vm-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: open-vm-tools (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: open-vm-tools (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: open-vm-tools (Ubuntu Xenial) ** No longer affects: open-vm-tools (Ubuntu Bionic) ** No longer affects: open-vm-tools (Ubuntu Focal) ** No longer affects: open-vm-tools (Ubuntu Groovy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893898 Title: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1893898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901033] Re: google-startup-scripts service no longer waits for cloud-init/snapd.seeded
** Description changed: We have a cloud-images qualification test for google startup scripts to ensure that cloud-init customizations are available before the user startup script is run. That test is failing and investigation shows that we have a functional regression from gce-compute-image-packages to the new google-guest-agent. Without waiting for cloud-final and snapd.seeded we won't present a consistent system for users to run scripts that have archive mirrors set up, GCE's google-cloud-sdk snap installed, users in the proper groups, or other customizations owned by those services. We are not holding groovy release on this bug, but we would like this treated with priority and it is a blocker for SRU. /usr/lib/systemd/system/google-startup-scripts.service in focal from gce-compute-image-packages: [Unit] Description=Google Compute Engine Startup Scripts After=network-online.target network.target rsyslog.service After=google-instance-setup.service google-network-daemon.service After=cloud-final.service multi-user.target Wants=cloud-final.service After=snapd.seeded.service Wants=snapd.seeded.service /usr/lib/systemd/system/google-startup-scripts.service in groovy from google-guest-agent: [Unit] Description=Google Compute Engine Startup Scripts Wants=network-online.target rsyslog.service After=network-online.target rsyslog.service google-guest-agent.service Before=apt-daily.service + + === + Workaround: + + As a work-around users can add cloud-init status --wait to the beginning + of their startup script (as cloud-init does wait for snap seeding to + complete). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901033 Title: google-startup-scripts service no longer waits for cloud- init/snapd.seeded To manage notifications about this bug go to: https://bugs.launchpad.net/google-guest-agent/+bug/1901033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901033] Re: google-startup-scripts service no longer waits for cloud-init/snapd.seeded
** Bug watch added: github.com/GoogleCloudPlatform/guest-agent/issues #84 https://github.com/GoogleCloudPlatform/guest-agent/issues/84 ** Also affects: google-guest-agent via https://github.com/GoogleCloudPlatform/guest-agent/issues/84 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901033 Title: google-startup-scripts service no longer waits for cloud- init/snapd.seeded To manage notifications about this bug go to: https://bugs.launchpad.net/google-guest-agent/+bug/1901033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901033] [NEW] google-startup-scripts service no longer waits for cloud-init/snapd.seeded
Public bug reported: We have a cloud-images qualification test for google startup scripts to ensure that cloud-init customizations are available before the user startup script is run. That test is failing and investigation shows that we have a functional regression from gce-compute-image-packages to the new google-guest-agent. Without waiting for cloud-final and snapd.seeded we won't present a consistent system for users to run scripts that have archive mirrors set up, GCE's google-cloud-sdk snap installed, users in the proper groups, or other customizations owned by those services. We are not holding groovy release on this bug, but we would like this treated with priority and it is a blocker for SRU. /usr/lib/systemd/system/google-startup-scripts.service in focal from gce-compute-image-packages: [Unit] Description=Google Compute Engine Startup Scripts After=network-online.target network.target rsyslog.service After=google-instance-setup.service google-network-daemon.service After=cloud-final.service multi-user.target Wants=cloud-final.service After=snapd.seeded.service Wants=snapd.seeded.service /usr/lib/systemd/system/google-startup-scripts.service in groovy from google-guest-agent: [Unit] Description=Google Compute Engine Startup Scripts Wants=network-online.target rsyslog.service After=network-online.target rsyslog.service google-guest-agent.service Before=apt-daily.service ** Affects: google-guest-agent (Ubuntu) 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/1901033 Title: google-startup-scripts service no longer waits for cloud- init/snapd.seeded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/1901033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1493188] Re: "overlayfs" no longer exists
@chad.smith I have used the cloud-utils in your ppa to build Xenial maas-images on a bionic host to confirm that things are working now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1493188 Title: "overlayfs" no longer exists To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1493188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1493188] Re: "overlayfs" no longer exists
With the move to Bionic host kernels on the builders, the Xenial MAAS images fail to build. This is because cloud-utils mount-image-callback remains unfixed in Xenial while the Bionic kernel does not have the overlayfs kernel module. The following patch at minimum is required in Xenial: https://bazaar.launchpad.net/~smoser/cloud- utils/trunk.lp1493188/revision/303 Could we have this fix SRUed to Xenial please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1493188 Title: "overlayfs" no longer exists To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1493188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
Thank you for the bug report. I have confirmed this issue and flagged the correct project, livecd-rootfs, for this work. ** Changed in: livecd-rootfs (Ubuntu) Status: New => Confirmed ** Changed in: cloud-images Status: New => Confirmed ** Changed in: livecd-rootfs (Ubuntu) Milestone: None => ubuntu-20.10 ** Changed in: open-vm-tools (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893898 Title: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1893898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
So we need to fix livecd-rootfs to correctly add the tools version field to the vmdk header *and* add a check that it got there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893898 Title: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1893898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
But that function is sed'ing the file created by python3-vmdkstream so we'll look into it. The vmdk-stream-converter source package has had a minor change between focal and groovy but it doesn't explain this issue. ** Also affects: cloud-images 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/1893898 Title: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1893898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
Okay, the vmdk lacks the version in bionic, focal, and groovy. The ddb.comment field that toolsVersion uses is missing: # Disk Descriptor File # Created by VMDKstream version=1 CID=7e5b80a7 parentCID= createType="streamOptimized" # Extent description RDONLY 20971520 SPARSE "call-me-stream.vmdk" #DDB ddb.adapterType = "lsilogic" # 20971520 / 63 / 255 rounded up ddb.geometry.cylinders = "1306" ddb.geometry.heads = "255" ddb.geometry.sectors = "63" ddb.longContentID = "8f15b3d0009d9a3f456ff7b28d324d2a" ddb.virtualHWVersion = "7"^@^@^@^ ** Also affects: livecd-rootfs (Ubuntu) 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/1893898 Title: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1893898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
The OVA we're providing[1] is built with this[2] binary hook in livecd- rootfs which wraps up the VMDK created using the create_vmdk[3] function. That function calls modify_vmdk_header to set the tools version; this code is unchanged from when it was added in early 2017. [1] https://cloud-images.ubuntu.com/groovy/current/groovy-server-cloudimg-amd64.ova [2] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-cpc/hooks.d/base/vmdk-ova-image.binary [3] https://git.launchpad.net/livecd-rootfs/tree/live-build/functions#n229 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893898 Title: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1893898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738400] Re: Vagrant bionic 64 with virtualbox image doesn't start network correctly
A backport of https://github.com/hashicorp/vagrant/pull/9338 could resolve this and allow bionic to launch Focal and later vagrant boxes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738400 Title: Vagrant bionic 64 with virtualbox image doesn't start network correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1738400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889470] Re: snap seed with channel breaks ubuntu-cpc:minimized builds on focal
** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889470 Title: snap seed with channel breaks ubuntu-cpc:minimized builds on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1889470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889556] Re: grub-install failure does not fail package upgrade (and does not roll back to matching modules)
** Merge proposal linked: https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/388423 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889556 Title: grub-install failure does not fail package upgrade (and does not roll back to matching modules) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889509] Re: grub boot error : "symbol 'grub_calloc' not found
@marin-n & @hggdh2,
I see that you have both reported failures on Azure. @marin-n, from
your grub versions it looks like you're on focal. I'd like to learn
more so I can recreate and get this addressed.
I would like to find out:
- which image release and build you are running:
$ cat /etc/lsb-release
$ cat /etc/cloud/build.info
- the image source (publisher/offer) and the vmSize:
$ curl --silent -H Metadata:true
"http://169.254.169.254/metadata/instance/compute/?api-version=2017-08-01"; |
python3 -c 'import json,sys;
data=json.load(sys.stdin);print("\n".join([data["vmSize"], data["publisher"],
data["offer"]]));'
- anything special you've done with your config that would be relevant.
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/1889509
Title:
grub boot error : "symbol 'grub_calloc' not found
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889509/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889556] Re: grub-install failure does not fail package upgrade (and does not roll back to matching modules)
My recreate is with an AWS EC2 instance with an NVMe root device as that is one known way to trigger an error in cloud-init cc_grub_dpkg so that it does not write a valid debconf for grub-pc install_devices, however this is broader than NVMe root with cloud-init. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889556 Title: grub-install failure does not fail package upgrade (and does not roll back to matching modules) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889556] [NEW] grub-install failure does not fail package upgrade (and does not roll back to matching modules)
*** This bug is a security vulnerability *** Public security bug reported: Failure to install new grub core to the specified device does not correctly prevent upgrade to incompatible modules (LP: #1889509) $ sudo debconf-get-selections |grep sda grub-pc grub-pc/install_devices_disks_changed multiselect /dev/sda grub-pc grub-pc/install_devices multiselect /dev/sda $ mount|grep nvme /dev/nvme0n1p1 on / type ext4 (rw,relatime,discard,data=ordered) $ ls /dev/sda ls: cannot access '/dev/sda': No such file or directory $ sudo env DEBIAN_FRONTEND=noninteractive apt full-upgrade -y ... Get:10 http://us-west-2.ec2.archive.ubuntu.com/ubuntu xenial-updates/main amd64 grub-pc-bin amd64 2.02~beta2-36ubuntu3.26 [891 kB] ... Installing for i386-pc platform. grub-install: error: cannot find a GRUB drive for /dev/sda. Check your device.map. Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.4.0--aws Found linux image: /boot/vmlinuz-4.4.0-1109-aws Found initrd image: /boot/initrd.img-4.4.0-1109-aws done ... # update-grub failed during the install but the return code is 0 $ echo $? 0 # The package is installed without apparent error, but the instance will fail to reboot (LP: #1889509) $ dpkg -l|grep grub-pc ii grub-pc 2.02~beta2-36ubuntu3.26 amd64GRand Unified Bootloader, version 2 (PC/BIOS version) ii grub-pc-bin 2.02~beta2-36ubuntu3.26 amd64GRand Unified Bootloader, version 2 (PC/BIOS binaries) # If I reboot it will fail to boot: Booting from Hard Disk 0... error: symbol `grub_calloc' not found. Entering rescue mode... grub rescue> _ --- Xenial in AWS (us-west-2 ami-060d1be0dd4526759 built on 20200611) The debconf for grub was not set to the correct device when cloud-init first ran (LP: #1877491) or when the fix for that was applied (LP: #1889555) The fact that grub-install fails during the upgrade but does not fail the package install (and cause a rollback) means that how we have a mismatch between grub core and modules which breaks boot (LP: #1889509). ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Affects: grub2 (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: grub2 (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: grub2 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: grub2 (Ubuntu Groovy) Importance: Undecided Status: New ** Tags: regression-release regression-security regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889556 Title: grub-install failure does not fail package upgrade (and does not roll back to matching modules) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889556] Re: grub-install failure does not fail package upgrade (and does not roll back to matching modules)
I'm attaching a full log from the recreate that shows additional details ** Attachment added: "grub_bug_log" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556/+attachment/5397176/+files/grub_bug_log ** Description changed: Failure to install new grub core to the specified device does not correctly prevent upgrade to incompatible modules (LP: #1889509) $ sudo debconf-get-selections |grep sda grub-pc grub-pc/install_devices_disks_changed multiselect /dev/sda grub-pc grub-pc/install_devices multiselect /dev/sda $ mount|grep nvme /dev/nvme0n1p1 on / type ext4 (rw,relatime,discard,data=ordered) $ ls /dev/sda ls: cannot access '/dev/sda': No such file or directory $ sudo env DEBIAN_FRONTEND=noninteractive apt full-upgrade -y ... Get:10 http://us-west-2.ec2.archive.ubuntu.com/ubuntu xenial-updates/main amd64 grub-pc-bin amd64 2.02~beta2-36ubuntu3.26 [891 kB] ... Installing for i386-pc platform. grub-install: error: cannot find a GRUB drive for /dev/sda. Check your device.map. Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.4.0--aws Found linux image: /boot/vmlinuz-4.4.0-1109-aws Found initrd image: /boot/initrd.img-4.4.0-1109-aws done ... # update-grub failed during the install but the return code is 0 $ echo $? 0 # The package is installed without apparent error, but the instance will fail to reboot (LP: #1889509) $ dpkg -l|grep grub-pc ii grub-pc 2.02~beta2-36ubuntu3.26 amd64GRand Unified Bootloader, version 2 (PC/BIOS version) ii grub-pc-bin 2.02~beta2-36ubuntu3.26 amd64GRand Unified Bootloader, version 2 (PC/BIOS binaries) # If I reboot it will fail to boot: Booting from Hard Disk 0... error: symbol `grub_calloc' not found. Entering rescue mode... grub rescue> _ --- Xenial in AWS (us-west-2 ami-060d1be0dd4526759 built on 20200611) The debconf for grub was not set to the correct device when cloud-init first ran (LP: #1877491) or when the fix for that was applied (LP: #1889555) - The fact that grub-install fails during the upgrade but does not fail the package install (and cause a rollback) means that how we have a mismatch between grub core and modules which breaks boot. + The fact that grub-install fails during the upgrade but does not fail the package install (and cause a rollback) means that how we have a mismatch between grub core and modules which breaks boot (LP: #1889509). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889556 Title: grub-install failure does not fail package upgrade (and does not roll back to matching modules) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889470] Re: snap seed with channel breaks ubuntu-cpc:minimized builds on focal
** Merge proposal linked: https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/388320 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889470 Title: snap seed with channel breaks ubuntu-cpc:minimized builds on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1889470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889470] Re: snap seed with channel breaks ubuntu-cpc:minimized builds on focal
** Description changed: + [Impact] + + * Focal ubuntu-cpc:minimized builds fail (see Original Description) + + [Test Case] + + * detailed instructions how to reproduce the bug + + * these should allow someone who is not familiar with the affected +package to reproduce the bug and verify that the updated package fixes +the problem. + + [Regression Potential] + + * discussion of how regressions are most likely to manifest as a result + of this change. + + * It is assumed that any SRU candidate patch is well-tested before +upload and has a low overall risk of regression, but it's important +to make the effort to think about what ''could'' happen in the +event of a regression. + + * This both shows the SRU team that the risks have been considered, +and provides guidance to testers in regression-testing the SRU. + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + + [Original Description] + The seed now specifies the lxd snap in focal as 'lxd=4.0/stable/ubuntu-20.04' which doesn't match the expectations of the code with looks for lxd as the only snap in the seed for minimized images. This patch updates the pattern to accept 'lxd' or 'lxd=*'. The failure we see in the build is: W: No seed matching task cloud-image snap: considering required snap: considering minimal snap: considering standard snap: considering server snap: found lxd=4.0/stable/ubuntu-20.04 Unexpected seeded snap for ubuntu-cpc:minimized build: lxd=4.0/stable/ubuntu-20.04 Build failed ** Description changed: [Impact] - * Focal ubuntu-cpc:minimized builds fail (see Original Description) + * Focal ubuntu-cpc:minimized builds fail (see Original Description) [Test Case] - * detailed instructions how to reproduce the bug - - * these should allow someone who is not familiar with the affected -package to reproduce the bug and verify that the updated package fixes -the problem. + * build ubuntu-cpc:minimized + * autopkgtest will catch this now, but didn't previously because the seed had yet to change [Regression Potential] - * discussion of how regressions are most likely to manifest as a result - of this change. - - * It is assumed that any SRU candidate patch is well-tested before -upload and has a low overall risk of regression, but it's important -to make the effort to think about what ''could'' happen in the -event of a regression. - - * This both shows the SRU team that the risks have been considered, -and provides guidance to testers in regression-testing the SRU. + * This is a very low risk change that is only in the code path ubuntu- + cpc:minimized and the regression would require us to add a seeded snap + that had a lxd=something that wasn't lxd, however the snap store doesn't + allow '=' in name, so I think we're good. [Other Info] - - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance + + * None [Original Description] The seed now specifies the lxd snap in focal as 'lxd=4.0/stable/ubuntu-20.04' which doesn't match the expectations of the code with looks for lxd as the only snap in the seed for minimized images. This patch updates the pattern to accept 'lxd' or 'lxd=*'. The failure we see in the build is: W: No seed matching task cloud-image snap: considering required snap: considering minimal snap: considering standard snap: considering server snap: found lxd=4.0/stable/ubuntu-20.04 Unexpected seeded snap for ubuntu-cpc:minimized build: lxd=4.0/stable/ubuntu-20.04 Build failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889470 Title: snap seed with channel breaks ubuntu-cpc:minimized builds on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1889470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889470] [NEW] snap seed with channel breaks ubuntu-cpc:minimized builds on focal
Public bug reported: [Impact] * Focal ubuntu-cpc:minimized builds fail (see Original Description) [Test Case] * detailed instructions how to reproduce the bug * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. [Regression Potential] * discussion of how regressions are most likely to manifest as a result of this change. * It is assumed that any SRU candidate patch is well-tested before upload and has a low overall risk of regression, but it's important to make the effort to think about what ''could'' happen in the event of a regression. * This both shows the SRU team that the risks have been considered, and provides guidance to testers in regression-testing the SRU. [Other Info] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance [Original Description] The seed now specifies the lxd snap in focal as 'lxd=4.0/stable/ubuntu-20.04' which doesn't match the expectations of the code with looks for lxd as the only snap in the seed for minimized images. This patch updates the pattern to accept 'lxd' or 'lxd=*'. The failure we see in the build is: W: No seed matching task cloud-image snap: considering required snap: considering minimal snap: considering standard snap: considering server snap: found lxd=4.0/stable/ubuntu-20.04 Unexpected seeded snap for ubuntu-cpc:minimized build: lxd=4.0/stable/ubuntu-20.04 Build failed ** Affects: livecd-rootfs (Ubuntu) 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/1889470 Title: snap seed with channel breaks ubuntu-cpc:minimized builds on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1889470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885571] Re: Can't set boot kernel in GRUB on focal image
Adding 'grub' project to verify and provide assistance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885571 Title: Can't set boot kernel in GRUB on focal image To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1885571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878225] Re: Please remove lxd.snap from lxd images, as it fails to seed thus failing the first boot - snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64
@xnox wrote: > It sounds like we must remove seeded snaps from our LXD images, and not > install > any seeded snaps inside our container. And like only install the lxd stub deb. > Cause it looks like seeding snaps is not supported inside classic lxd > containers. Let's remember that these aren't just LXD images, they are generic squashfs images from cloud-images.ubuntu.com. This raises the issue that if the generic cloud squashfs is run in any environment where snap seeding can not complete then boot is stuck and the instance is broken without cloud-init completing. This might mean no ssh keys and difficulties debugging. So I'll reiterate that this is not an acceptable solution and note that the issue is broader than even just unprivileged LXD containers. Removing all snaps from the squashfs feels like a significant lost opportunity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878225 Title: Please remove lxd.snap from lxd images, as it fails to seed thus failing the first boot - snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1878225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
Speaking of cloud-images generally I propose the following: * Images in the ubuntu-cpc project by default should boot with an initramfs. * Revert the livecd-rootfs change which "Unconditionally set GRUB_FORCE_PARTUUID in cloud images" * Images with custom kernels can boot without an initramfs * Set GRUB_FORCE_PARTUUID as part of livefs-rootfs:live-build/functions replace_kernel() as this is used by the ubuntu-cpc project for each image that ships an optimized kernel intended to boot without initramfs. Steve, I agree with everything you said in comment #21 about removing not this functionality from Azure images. I think there is room to improve the experience for users that change their kernel and encounter this behavior. The panic/reboot behavior is unexpected and the mapping of GRUB_FORCE_PARTUUID to initramfs-less boot is non-obvious to the end user. I don't immediately have suggestions to smooth this rough edge but I feel that we need to take some time on this before completely closing this bug out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754350] Re: Add an editor to the minimized image
I've opened a track for livecd-rootfs where the minimal image is defined and I'm going to close the cloud-images portion. But I will add that the images themselves set the expectation about what it is to be considered minimal as: "This system has been minimized by removing packages and content that are not required on a system that users do not log into." So I do not expect that an editor would be added. ** Changed in: cloud-images Status: Invalid => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754350 Title: Add an editor to the minimized image To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1754350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881217] Re: arm64v8 focal: lintian will get stuck with it
I added a -d flag to the invocation of perl in the shebang line of
/usr/share/lintian/frontend/dplint Here is what I got:
# lintian --help
Loading DB routines from perl5db.pl version 1.55
Editor support available.
Enter h or 'h h' for help, or 'man perldebug' for more help.
main::(/usr/bin/lintian:55):};
DB<1> c
^CIO::Async::Loop::Epoll::loop_once(/usr/share/perl5/IO/Async/Loop/Epoll.pm:181):
181: return undef if !defined $ret and $! != EINTR;
DB<1> T
@ = DB::DB called from file '/usr/share/perl5/IO/Async/Loop/Epoll.pm' line 181
. = IO::Async::Loop::Epoll::loop_once(ref(IO::Async::Loop::Epoll)) called from
file '/usr/share/perl5/IO/Async/Loop.pm' line 642
. = IO::Async::Loop::await(ref(IO::Async::Loop::Epoll), ref(IO::Async::Future))
called from file '/usr/share/perl5/Lintian/Util.pm' line 691
$ = Lintian::Util::safe_qx('nproc') called from file
'/usr/share/perl5/Lintian/Internal/FrontendUtil.pm' line 123
@ = Lintian::Internal::FrontendUtil::default_parallel() called from file
'/usr/share/lintian/commands/lintian.pm' line 82
$ = require '/usr/share/lintian/commands/lintian.pm' called from file
'/usr/bin/lintian' line 36
. = eval {...} called from file '/usr/bin/lintian' line 36
. =
main::__ANON__[/usr/bin/lintian:55]('/usr/share/lintian/commands/lintian.pm')
called from file '/usr/bin/lintian' line 120
. = dplint::run_tool('/usr/bin/lintian', 'lintian') called from file
'/usr/bin/lintian' line 299
. = dplint::main() called from file '/usr/bin/lintian' line 383
I also ran with tracing and that's attached here as
** Attachment added: "lintian debug output"
https://bugs.launchpad.net/cloud-images/+bug/1881217/+attachment/5379498/+files/lintian.output
** Also affects: lintian (Ubuntu)
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/1881217
Title:
arm64v8 focal: lintian will get stuck with it
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1881217/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881217] Re: arm64v8 focal: lintian will get stuck with it
I'm moving this from cloud-images to lintian, this is not an issue specific to the image itself. ** Changed in: cloud-images Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881217 Title: arm64v8 focal: lintian will get stuck with it To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1881217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881217] Re: arm64v8 focal: lintian will get stuck with it
Eoan arm64 container on focal amd64 host does not recreate this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881217 Title: arm64v8 focal: lintian will get stuck with it To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1881217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569237] Re: vagrant xenial box is not provided with vagrant/vagrant username and password
** No longer affects: cloud-images/trunk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569237 Title: vagrant xenial box is not provided with vagrant/vagrant username and password To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1569237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875068] Re: Focal docker ARM32 builds are failing due to libc6 package installation
** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-images Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875068 Title: Focal docker ARM32 builds are failing due to libc6 package installation To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1875068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875882] Re: debconf attempts interactive configuration; breaks Docker image builds
** Changed in: cloud-images Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875882 Title: debconf attempts interactive configuration; breaks Docker image builds To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1875882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1876139] Re: Groovy cloud-images failing during growpart
On Thu, Apr 30, 2020 at 2:50 PM Steve Langasek wrote: > On Thu, Apr 30, 2020 at 05:27:49PM -, Dimitri John Ledkov wrote: > > Looking at seeds, it seems like maybe "cloud-image" should have fdisk > > seeded in both focal & groovy. > > I think this belongs in the server seed, not just cloud-image. >From the changelog you dropped fdisk to avoid having it in chroots and squashfs'. Adding it to the seed would negate that without then removing it again from those images, which feels fragile. I read the removal of fdisk as direction for the OS generally and will note the chroots and squashfs still carry gdisk/sgdisk (Although now I can't figure out how that gets into the image). But why wouldn't we leave it out of the seeds and if the user needs fdisk in addition to gdisk then they must now explicitly install it? > But given that fdisk is no longer part of the essential set, packages that > invoke it should also be fixed to declare a dependency on it. > +1 on packages explicitly declaring a dependency. Is this being worked for cloud-utils? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876139 Title: Groovy cloud-images failing during growpart To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1876139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874834] Re: Xenial builds with core18-based snaps pre-seed core snap instead
Built ubuntu-cpc images and tested that images with core or core18 based snaps build as expected. The core snap was pulled in for snaps without an explicit base while core18 & snapd were pulled in for snaps with an explicit core18 base, and were there were both we have core and core18 without snapd. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done 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/1874834 Title: Xenial builds with core18-based snaps pre-seed core snap instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1874834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874834] Re: Xenial builds with core18-based snaps pre-seed core snap instead
I've looked at the ubuntu-image autopkgtest failure on ppc64el. The failure was a network timeout on a 'pip' command. Re-running the test has passed and this seems acceptable. I will continue testing the SRU per the testcase in the template and update this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874834 Title: Xenial builds with core18-based snaps pre-seed core snap instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1874834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874834] Re: Xenial builds with core18-based snaps pre-seed core snap instead
** Also affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Xenial) Assignee: (unassigned) => Robert C Jennings (rcj) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874834 Title: Xenial builds with core18-based snaps pre-seed core snap instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1874834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874834] Re: Xenial builds with core18-based snaps pre-seed core snap instead
** Description changed: - A xenial image that preseeds a snap based on core18 will end up with - core instead and preseeding on boot will fail. + [Impact] + + * A xenial image that preseeds a snap based on core18 will +end up with core instead and preseeding on boot will fail. + + + [Test Case] + + * Add a binary hook that pre-seeds lxd (which recently moved to a +core18 base). Ensure the snapd and core18 are pulled in by the +build and core is not present. Boot the image and ensure +pre-seeding is successful. + + [Regression Potential] + + * Images with pre-seeded snaps regress in some fashion. We will need +to check these builds but there are no pre-seeded snaps in the +livecd-rootfs tree for Xenial so this is a low risk change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874834 Title: Xenial builds with core18-based snaps pre-seed core snap instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1874834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874834] [NEW] Xenial builds with core18-based snaps pre-seed core snap instead
Public bug reported: A xenial image that preseeds a snap based on core18 will end up with core instead and preseeding on boot will fail. ** Affects: livecd-rootfs (Ubuntu) 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/1874834 Title: Xenial builds with core18-based snaps pre-seed core snap instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1874834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873528] Re: sshd overrides from /etc/ssh/sshd_config.d/*conf apply in reverse lexographic order
Drat, I see that now in sshd_config. I think I tried searching for "first" and maybe by that point I was just looking at sshd's man page. Okay, well then this is fine for me It's documented and stable. We can comfortably make this change for cloud-images. Thanks Colin! ** Changed in: openssh (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873528 Title: sshd overrides from /etc/ssh/sshd_config.d/*conf apply in reverse lexographic order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1873528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873809] Re: disk-kvm.img aren't UEFI bootable
@colin-king, Can we get that config option added for this kernel? ** Also affects: linux-kvm (Ubuntu) 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/1873809 Title: disk-kvm.img aren't UEFI bootable To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871919] Re: images with only core18-based snaps fail to build
I have used livecd-rootfs 2.620.2 from proposed to build ec2 and gce images. EC2 currently has a mix of core and core18 based snaps while GCE has only core18 based snaps. I confirmed that snapd was seeded when core18 was the only core snap present. Boot testing each of these images confirmed that snap preseeding is working and snaps are usable. I'm going to mark this as verification-done ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871919 Title: images with only core18-based snaps fail to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1871919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873528] [NEW] sshd overrides from /etc/ssh/sshd_config.d/*conf apply in reverse lexographic order
Public bug reported: I am looking at the addition of 'Include /etc/ssh/sshd_config.d/*conf' for use in Ubuntu cloud images. I wanted to add a config file and see if I had done things correctly. I assumed that the files were sourced lexographically (based on use of glob() in readconf.h) so that I could document how users could override our tuning. But it appears from 'sshd -T' output and observed behavior that the first file in /etc/sshd_config.d/ to define a parameter wins. I see in 'sshd -ddd' output that they are parsed lexographically but it seems that their settings apply in reverse (or whichever comes first) if that makes sense. I'd like to understand if this is correct behavior and get it documented. Steps to reproduce on focal with openssh-server 1:8.2p1-4: 1. Create the following files in /etc/ssh/sshd_config.d/ with the content shown below: 40-cloudimg-settings.conf: ClientAliveInterval 110 PasswordAuthentication yes PermitRootLogin no 50-cloudimg-settings.conf: ClientAliveInterval 120 PermitRootLogin yes 60-cloudimg-settings.conf: ClientAliveInterval 180 2. Check what sshd thinks the values will be with 'sshd -T|grep -i clientaliveinterval' and 'sshd -T|grep permitrootlogin' clientaliveinterval 110 permitrootlogin no (The tuning I cared about was ClientAliveInterval for my work but PermitRootLogin is easier to demonstrate) 3. Run '/usr/sbin/sshd -ddd' to check debug output for config file parsing behavior: debug2: load_server_config: filename /etc/ssh/sshd_config debug2: load_server_config: done config len = 296 debug2: parse_server_config_depth: config /etc/ssh/sshd_config len 296 debug2: /etc/ssh/sshd_config line 13: new include /etc/ssh/sshd_config.d/*.conf debug2: /etc/ssh/sshd_config line 13: including /etc/ssh/sshd_config.d/40-cloudimg-settings.conf debug2: load_server_config: filename /etc/ssh/sshd_config.d/40-cloudimg-settings.conf debug2: load_server_config: done config len = 71 debug2: parse_server_config_depth: config /etc/ssh/sshd_config.d/40-cloudimg-settings.conf len 71 debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:1 setting ClientAliveInterval 110 debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:2 setting PasswordAuthentication yes debug3: /etc/ssh/sshd_config.d/40-cloudimg-settings.conf:3 setting PermitRootLogin no debug2: /etc/ssh/sshd_config line 13: including /etc/ssh/sshd_config.d/50-cloudimg-settings.conf debug2: load_server_config: filename /etc/ssh/sshd_config.d/50-cloudimg-settings.conf debug2: load_server_config: done config len = 46 debug2: parse_server_config_depth: config /etc/ssh/sshd_config.d/50-cloudimg-settings.conf len 46 debug3: /etc/ssh/sshd_config.d/50-cloudimg-settings.conf:1 setting ClientAliveInterval 120 debug3: /etc/ssh/sshd_config.d/50-cloudimg-settings.conf:2 setting PermitRootLogin yes debug2: /etc/ssh/sshd_config line 13: including /etc/ssh/sshd_config.d/60-cloudimg-settings.conf debug2: load_server_config: filename /etc/ssh/sshd_config.d/60-cloudimg-settings.conf debug2: load_server_config: done config len = 25 debug2: parse_server_config_depth: config /etc/ssh/sshd_config.d/60-cloudimg-settings.conf len 25 debug3: /etc/ssh/sshd_config.d/60-cloudimg-settings.conf:1 setting ClientAliveInterval 180 4. Set a root password and unlock the account. 5. Attempt to ssh as root to the instance with a password. Observation: * Root password login is denied if PermitRootLogin is 'no' in 40-foo.conf and 'yes' in 50-foo.conf * Root password login is allowed if PermitRootLogin is 'yes' in 40-foo.conf and 'no' in 50-foo.conf It appears in 'sshd -ddd' output that files are parsed in lexographic order (40-foo.conf before 50-foo.conf) but the behavior observed indicates that the value set in 40-foo.conf overrides 50-foo.conf which is counter to expectations. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: champagne -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873528 Title: sshd overrides from /etc/ssh/sshd_config.d/*conf apply in reverse lexographic order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1873528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873373] Re: livecd-rootfs must stop using manual seeds, and always use `snap prepare-image --classic`
This is great and I'd love to see us move to this from what we are doing. Parallel builds for the ubuntu-cpc project have an absolute requirement for cohort support; so that requirement will need to be driven with snapd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873373 Title: livecd-rootfs must stop using manual seeds, and always use `snap prepare-image --classic` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1873373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871919] Re: images with only core18-based snaps fail to build
** Also affects: livecd-rootfs (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Eoan) Assignee: (unassigned) => Robert C Jennings (rcj) ** Changed in: livecd-rootfs (Ubuntu Eoan) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871919 Title: images with only core18-based snaps fail to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1871919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863024] Re: SRU: bootable buildd images for all releases
** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863024 Title: SRU: bootable buildd images for all releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1863024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871919] Re: images with only core18-based snaps fail to build
** Description changed: [Impact] - * Building an ubuntu-cpc minimal image by default would have no snaps + * Building an ubuntu-cpc minimal image by default would have no snaps installed. When a binary hook seeds a snap that has a core18 base the build will fail when calling 'snap debug validate-seed' because the snapd snap is missing. - * Additionally, an image with snaps that only depend on core18 (which + * Additionally, an image with snaps that only depend on core18 (which isn't in the ubuntu-cpc:minimized project) would still ship 'core'. This was found by code inspection and reported in bug #1871912. - [Test Case] - * Build with ubuntu-cpc:minimized with a binary hook which adds lxd - (now that it is based on core18). With the proposed fix the image build - should succeed with lxd, core18, and snapd preseeded. The build should - not fail and should not include core. + * Build with ubuntu-cpc as that seeds lxd (now that it is based on + core18). With the proposed fix the image build should succeed with lxd, + core18, and snapd preseeded. The build should not fail and should not + include core. [Regression Potential] - * Image builds fail in some fashion related to snap preseeding. It is + * Image builds fail in some fashion related to snap preseeding. It is unlikely to build an image that fails to pre-seed when booted as we call 'snap debug validate-seed' in the build, which is catching the current bug of omitting snapd with core18. [Other Info] - - * None + + * None [Original description] Building an ubuntu-cpc minimal image by default would have no snaps installed. When a binary hook seeds a snap that has a core18 base the build will fail when calling 'snap debug validate-seed' because the snapd snap is missing. Additionally, an image with snaps that only depend on core18 (which isn't in the ubuntu-cpc:minimized project) would still ship 'core'. This was found by code inspection and reported in bug #1871912. We want to build images that only contain the appropriate core image and when that is not core it should have snapd preseeded. The _snap_post_process function is meant to install snapd if core18 is the only core snap installed or remove snapd if core is installed and snapd was not explicitly installed. But the current logic in _snap_preseed will never call _snap_post_process. $core_name will never be empty with the existing logic, and even if it were that would only be for the 'core' snap and we'd miss using the 'core18' logic that pulls in snapd. Given the case statement in _snap_post_process can handle doing the right thing given any snap we can just call it unconditionally. Seeding any snap via snap_preseed will evaluate the base for each snap and seed the appropriate base. There should be no reason to explicitly seed the 'core' snap and with snaps moving to 'core18' this will add 'core' without need. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871919 Title: images with only core18-based snaps fail to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1871919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871919] Re: images with only core18-based snaps fail to build
** Description changed: + [Impact] + + * Building an ubuntu-cpc minimal image by default would have no snaps + installed. When a binary hook seeds a snap that has a core18 base + the build will fail when calling 'snap debug validate-seed' because + the snapd snap is missing. + + * Additionally, an image with snaps that only depend on core18 (which + isn't in the ubuntu-cpc:minimized project) would still ship 'core'. + This was found by code inspection and reported in bug #1871912. + + + [Test Case] + + * Build with ubuntu-cpc:minimized with a binary hook which adds lxd + (now that it is based on core18). With the proposed fix the image build + should succeed with lxd, core18, and snapd preseeded. The build should + not fail and should not include core. + + [Regression Potential] + + * Image builds fail in some fashion related to snap preseeding. It is + unlikely to build an image that fails to pre-seed when booted as we call + 'snap debug validate-seed' in the build, which is catching the current + bug of omitting snapd with core18. + + [Other Info] + + * None + + [Original description] + Building an ubuntu-cpc minimal image by default would have no snaps - installed. When I binary hook seeds a snap that has a core18 base + installed. When a binary hook seeds a snap that has a core18 base the build will fail when calling 'snap debug validate-seed' because the snapd snap is missing. Additionally, an image with snaps that only depend on core18 (which isn't in the ubuntu-cpc:minimized project) would still ship 'core'. This was found by code inspection and reported in bug #1871912. We want to build images that only contain the appropriate core image and when that is not core it should have snapd preseeded. The _snap_post_process function is meant to install snapd if core18 is the only core snap installed or remove snapd if core is installed and snapd was not explicitly installed. But the current logic in _snap_preseed will never call _snap_post_process. $core_name will never be empty with the existing logic, and even if it were that would only be for the 'core' snap and we'd miss using the 'core18' logic that pulls in snapd. Given the case statement in _snap_post_process can handle doing the right thing given any snap we can just call it unconditionally. Seeding any snap via snap_preseed will evaluate the base for each snap and seed the appropriate base. There should be no reason to explicitly seed the 'core' snap and with snaps moving to 'core18' this will add 'core' without need. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871919 Title: images with only core18-based snaps fail to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1871919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863024] Re: SRU: bootable buildd images for all releases
** 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.net/bugs/1863024 Title: SRU: bootable buildd images for all releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1863024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872485] Re: virtualbox-guest-utils fails to install on 20.04
systemd-timesyncd is conflicting with virtualbox-guest-utils but
virtualbox-guest-utils isn't providing time-daemon... debian/control in
virtualbox contains:
Package: virtualbox-guest-utils
Architecture: amd64 i386
Depends: adduser,
pciutils,
virtualbox-guest-dkms (= ${source:Version}) | virtualbox-guest-source
(= ${source:Version}) | virtualbox-guest-modules,
${misc:Depends},
${shlibs:Depends}
#Conflicts: time-daemon, ntp
#Provides: time-daemon
#Replaces: time-daemon
** No longer affects: apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872485
Title:
virtualbox-guest-utils fails to install on 20.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1872485/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872485] Re: virtualbox-guest-utils fails to install on 20.04
** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872485 Title: virtualbox-guest-utils fails to install on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872145] Re: explicit key offered after all agent keys, auth can fail before explicit key used
** Summary changed: - explicit key offered after all agent keys, auth fails before explicit key used + explicit key offered after all agent keys, auth can fail before explicit key used -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872145 Title: explicit key offered after all agent keys, auth can fail before explicit key used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1872145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872145] [NEW] explicit key offered after all agent keys, auth fails before explicit key used
Public bug reported: A user creates an ssh key and specifies it on the cmdline with 'ssh -i new_key user@host'. The connection fails with the message "Too many authentication failures" displayed to the user. This would lead the user to believe that they failed to put the public portion of the new key on the destination and it will probably be hard for the average user to debug this. The root of this issue is that the user has a number of keys in ~/.ssh/ registered with their ssh agent. The ssh command is offering each of these keys from the agent to the remote system before trying the explicit key from the command line. There are enough agent keys to reach the failure limit (usually 5 keys) with the remote before they get to the explicit key. The solution today for the user is to head down into the ssh_config man page to find '-o IdentitiesOnly=yes' to skip the agent keys and only use the specified key. But they're unlikely to do this because '-i' in the ssh man page doesn't suggest this and they'd only look for this if they actually understood the root cause of the problem, which is a bit cruel. We should consider changing the order of the keys offered to the remote to use explicit keys first followed by agent keys. It would seem to me that this would honor the users intent of explicitly specifying a key to use. The current order makes this difficult for anyone fielding a user's authentication failure report as they must double check that ssh managed to actually try the key the user specified before it raised an error message about authentication failures. ** Affects: openssh (Ubuntu) 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/1872145 Title: explicit key offered after all agent keys, auth fails before explicit key used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1872145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871919] Re: images with only core18-based snaps fail to build
** Changed in: livecd-rootfs (Ubuntu) Status: Triaged => 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/1871919 Title: images with only core18-based snaps fail to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1871919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871451] Re: powerpc segfault on exponential of negative in python
This would be an issue for the package, I will close the track for cloud-images. ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-images Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871451 Title: powerpc segfault on exponential of negative in python To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1871451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869963] Re: Unable to install chromium-browser 20.04
** Also affects: chromium (Ubuntu) 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/1869963 Title: Unable to install chromium-browser 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1869963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871919] [NEW] images with only core18-based snaps fail to build
Public bug reported: Building an ubuntu-cpc minimal image by default would have no snaps installed. When I binary hook seeds a snap that has a core18 base the build will fail when calling 'snap debug validate-seed' because the snapd snap is missing. Additionally, an image with snaps that only depend on core18 (which isn't in the ubuntu-cpc:minimized project) would still ship 'core'. This was found by code inspection and reported in bug #1871912. We want to build images that only contain the appropriate core image and when that is not core it should have snapd preseeded. The _snap_post_process function is meant to install snapd if core18 is the only core snap installed or remove snapd if core is installed and snapd was not explicitly installed. But the current logic in _snap_preseed will never call _snap_post_process. $core_name will never be empty with the existing logic, and even if it were that would only be for the 'core' snap and we'd miss using the 'core18' logic that pulls in snapd. Given the case statement in _snap_post_process can handle doing the right thing given any snap we can just call it unconditionally. Seeding any snap via snap_preseed will evaluate the base for each snap and seed the appropriate base. There should be no reason to explicitly seed the 'core' snap and with snaps moving to 'core18' this will add 'core' without need. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Assignee: Robert C Jennings (rcj) Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871919 Title: images with only core18-based snaps fail to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1871919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871919] Re: images with only core18-based snaps fail to build
** Description changed: Building an ubuntu-cpc minimal image by default would have no snaps installed. When I binary hook seeds a snap that has a core18 base the build will fail when calling 'snap debug validate-seed' because the snapd snap is missing. Additionally, an image with snaps that only depend on core18 (which isn't in the ubuntu-cpc:minimized project) would still ship 'core'. - This was found by code inspection. + This was found by code inspection and reported in bug #1871912. We want to build images that only contain the appropriate core image and when that is not core it should have snapd preseeded. The _snap_post_process function is meant to install snapd if core18 is the only core snap installed or remove snapd if core is installed and snapd was not explicitly installed. But the current logic in _snap_preseed will never call _snap_post_process. $core_name will never be empty with the existing logic, and even if it were that would only be for the 'core' snap and we'd miss using the 'core18' logic that pulls in snapd. Given the case statement in _snap_post_process can handle doing the right thing given any snap we can just call it unconditionally. Seeding any snap via snap_preseed will evaluate the base for each snap and seed the appropriate base. There should be no reason to explicitly seed the 'core' snap and with snaps moving to 'core18' this will add 'core' without need. ** Merge proposal linked: https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/382041 ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Robert C Jennings (rcj) ** Changed in: livecd-rootfs (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871919 Title: images with only core18-based snaps fail to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1871919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871912] Re: images should have core18+snapd, not core
*** This bug is a duplicate of bug 1871919 *** https://bugs.launchpad.net/bugs/1871919 ** This bug has been marked a duplicate of bug 1871919 images with only core18-based snaps fail to build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871912 Title: images should have core18+snapd, not core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1871912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833435] Re: RFC: Add url/urls/mirrors attribute for product items
** Changed in: simplestreams Status: Triaged => 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/1833435 Title: RFC: Add url/urls/mirrors attribute for product items To manage notifications about this bug go to: https://bugs.launchpad.net/simplestreams/+bug/1833435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835114] Re: [MIR] ec2-instance-connect
@raharper, Your statement that this will be opt-in (disabled by default) does not reflect our intentions with this package. Upon review, my earlier statement was not as clear as I wish it was. In comment #31 I said: > CPC (public cloud team) will continue with our baseline testing and for > releases earlier than focal where we will be pre-installing the package > in AWS images with the service disabled (opt-in) we will test that the > service is correctly disabled. The goal is to ship this in all supported Ubuntu images on AWS enabled by default for releases where it can be added prior to release. We would ship disabled (opt-in) for releases that are already supported in the field so as not to change behavior mid-release. So my statement regarding being disabled "for releases earlier than focal" reflects the goal of shipping enabled by default in Focal were this MIR accepted prior to Focal's release. I want to ensure this is reviewed with that intent in mind. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835114 Title: [MIR] ec2-instance-connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1835114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863024] Re: SRU: bootable buildd images for all releases
** Changed in: livecd-rootfs (Ubuntu Bionic) 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/1863024 Title: SRU: bootable buildd images for all releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1863024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869761] Re: Failed to hibernate, reason: Command '/bin/systemctl hibernate' returned non-zero exit status 1
Please provide details on the steps needed to recreate including AMI- id/region and package version for ec2-hibinit-agent. Once you have recreated please collect logs with 'sosreport -a' and attach the result. Thank you. ** Changed in: ec2-hibinit-agent (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/1869761 Title: Failed to hibernate, reason: Command '/bin/systemctl hibernate' returned non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1869761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863024] Re: SRU: bootable buildd images for all releases
** Changed in: livecd-rootfs (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863024 Title: SRU: bootable buildd images for all releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1863024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863024] Re: SRU: bootable buildd images for all releases
** No longer affects: livecd-rootfs (Ubuntu Eoan) ** Merge proposal unlinked: https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/378931 ** Merge proposal linked: https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/378975 ** Description changed: - We want to backport bootable enabling bootable buildd images to eoan, - bionic, and xenial. + We want to backport bootable enabling bootable buildd images to bionic + and xenial. [Impact] * We don't have bootable buildd images, and we need them for Multipass. [Test Case] * Perform livefs build with project ubuntu-base and subproject buildd * Boot .img file using Multipass, confirm it boots * Perform a livecd-rootfs build using the generated buildd lxd tarball [Regression Potential] * Break existing artifacts in the buildd subproject * Cause buildd subproject to fail to build [Other Info] * None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863024 Title: SRU: bootable buildd images for all releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1863024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866159] Re: SRU: Use a snap cohort key for consistent parallel builds in Xenial
This has been verified using 2.408.58 in xenial-proposed. I have built the qcow2 image target of the ubuntu-cpc project with and without a cohort key. I added the following to the qcow2 binary hook: . /build/config/binary mkdir qcowmp mount_disk_image binary/boot/disk-uefi.ext4 qcowmp snap_preseed qcowmp/ lxd umount_disk_image qcowmp rmdir qcowmp Booting the resulting livecd.ubuntu-cpc.uefi1.img which came out of the builds with/without the snap cohort key shows that both boot and 'systemctl is-system-running' gets to 'running' (no failed units). The output of 'snap list' shows lxd and core as expected and 'snap info --verbose' run against each of the snaps in either image confirms that the cohort key did not persist into the resulting image as expected. Based on this testing I will mark the bug as verification-done. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done 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/1866159 Title: SRU: Use a snap cohort key for consistent parallel builds in Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1866159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863145] Re: arm64 cloud image contains flash-kernel which leads to apt errors on upgrade
Dave, using the latest focal daily lxd container (serial 20200313) I can remove and install flash-kernel to see the "flash-kernel: /boot/vmlinuz- or /boot/initrd.img- missing; expecting future run" failure and confirm that installing from the ppa (3.98ubuntu12~ppa1) gives the same output as above for my bionic test. Still, I'd like Stephan to confirm that this was the error he was seeing when he filed the case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863145 Title: arm64 cloud image contains flash-kernel which leads to apt errors on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1863145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863145] Re: arm64 cloud image contains flash-kernel which leads to apt errors on upgrade
I have a questionable recreate and maybe Stephan Fabel can confirm if this is what he's seeing. I have launched an arm64 VM on AWS and on that VM I have started an 18.04 container from the 'ubuntu:' remote. The container has a build serial of 20190307. Running 'apt update; apt upgrade -y' from this older image is enough to find an update for flash-kernel (3.98ubuntu11~18.04.1). During the upgrade I see the following message: flash-kernel: /boot/vmlinuz- or /boot/initrd.img- missing; expecting future run But the exit code from the upgrade is 0 and there are no broken packages. Stephan, is this the extent of the failure that you have seen? I was going to help validate the fix from Dave but I want to ensure I'm seeing the same failure first. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863145 Title: arm64 cloud image contains flash-kernel which leads to apt errors on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1863145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863145] Re: arm64 cloud image contains flash-kernel which leads to apt errors on upgrade
If that is the issue that Stephan is seeing then I have not seen the issue with the bionic package in Dave's PPA: $ lxc launch ubuntu:08e14ca27965 b $ lxc shell b $ apt-add-repository ppa:waveform/flash-kernel $ apt install -y flash-kernel Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: flash-kernel 1 upgraded, 0 newly installed, 0 to remove and 182 not upgraded. Need to get 62.0 kB of archives. After this operation, 11.3 kB of additional disk space will be used. Get:1 http://ppa.launchpad.net/waveform/flash-kernel/ubuntu bionic/main arm64 flash-kernel arm64 3.98ubuntu11~18.04.2~ppa1 [62.0 kB] Fetched 62.0 kB in 1s (84.8 kB/s) Preconfiguring packages ... (Reading database ... 28535 files and directories currently installed.) Preparing to unpack .../flash-kernel_3.98ubuntu11~18.04.2~ppa1_arm64.deb ... Unpacking flash-kernel (3.98ubuntu11~18.04.2~ppa1) over (3.90ubuntu3.18.04.2) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Setting up flash-kernel (3.98ubuntu11~18.04.2~ppa1) ... Installing new version of config file /etc/flash-kernel/bootscript/bootscr.uboot-generic ... Installing new version of config file /etc/initramfs/post-update.d/flash-kernel ... Installing new version of config file /etc/kernel/postinst.d/zz-flash-kernel ... Installing new version of config file /etc/kernel/postrm.d/zz-flash-kernel ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863145 Title: arm64 cloud image contains flash-kernel which leads to apt errors on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1863145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863145] Re: arm64 cloud image contains flash-kernel which leads to apt errors on upgrade
For others that would like to attempt a recreate, the image I'm using is: $ lxc image info ubuntu:08e14ca27965 Fingerprint: 08e14ca2796594a0a52f62a1974774db6f4ecfbb2a3da7f3a5c1e2e0abff7362 Size: 161.48MB Architecture: aarch64 Public: yes Timestamps: Created: 2019/03/07 00:00 UTC Uploaded: 2019/03/07 00:00 UTC Expires: 2023/04/26 00:00 UTC Last used: never Properties: architecture: arm64 label: release serial: 20190307 description: ubuntu 18.04 LTS arm64 (release) (20190307) os: ubuntu release: bionic version: 18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863145 Title: arm64 cloud image contains flash-kernel which leads to apt errors on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1863145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835114] Re: [MIR] ec2-instance-connect
On the topic of testing raised in earlier comments. CPC will continue with our baseline testing and for releases earlier than focal where we will be pre-installing the package in AWS images with the service disabled (opt-in) we will test that the service is correctly disabled. This testing is performed on images which contain packages from -updates, not -proposed. Further conversation regarding SRU testing needs to be had with the AWS instance connect development team to iron out the process and then document[1] the test plan. I believe that team should be involved in SRU testing from -proposed as we have with other packages which enable cloud-specific features. [1] https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835114 Title: [MIR] ec2-instance-connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1835114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866616] Re: 2nd display stopped working
Attaching the 2nd display via DisplayPort rather than DVI allows me to use it again, so I happen to have a solution, but not everyone may be so lucky. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866616 Title: 2nd display stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1866616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866616] Re: 2nd display stopped working
The log shows "open /dev/dri/card0: No such file or directory" but it does exist: $ ls -l /dev/dri/card0 crw-rw+ 1 root render 226, 0 Mar 9 06:12 /dev/dri/card0 Unplugging the display from DVI-D-0 and plugging it back in does not result in showing up in xrandr output. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866616 Title: 2nd display stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1866616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
