[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Indeed, it seems like the kernel linked above breaks dockerd. dmesg with "general protection fault" and stacktrace. all docker commands hang. https://pastebin.ubuntu.com/p/VRbFSmPkPs/ :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Perfect, no need to change tags anymore. Now that at least 2 persons verified the bug is fixed with the -proposed kernel, the SRU process will follow its course now and the fixed linux will land in the archives in due time: there is a mandatory 7 days wait time, so it should hit the archives next week, unless another fix rolled in this SRU breaks something else (I hope not :) ). Thanks for your help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
For all other subscribers to this bug, now is the time to help :) Enable -proposed on affected systems: $ echo "deb http://archive.ubuntu.com/ubuntu/ eoan-proposed main" >> /etc/apt/source.list Update apt sources: $ apt update Install the linux kernel (and friends) from -proposed: $ sudo apt install linux-headers-5.3.0-52 linux-headers-5.3.0-52-generic linux-image-5.3.0-52-generic linux-modules-5.3.0-52-generic linux- modules-extra-5.3.0-52-generic Remove or comment the -proposed line in /etc/apt Reboot. Verify that the bug if fixed (and that nothing else broke), then report here :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
I can confirm that the problem is fix in the -proposed kernel (5.3.0-52-generic). Marking verification-done. ** Tags removed: verification-needed-eoan ** Tags added: 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Reverting the status of that bug to confirmed was a bit premature :)
My previous comment already mentions 5.3.0-51-generic not being fixed
(before it being marked fix commited).
>From IRC:
"we should get a eoan/linux kernel in -proposed at the latest by
tomorrow, when that happens an automated comment will be added to the
bug report"
So, when a package with the comited fix is available ("tomorrow") you
can test it again. 5.3.0-51.44 is not the version containing the patch,
however.
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872001
Title:
5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
For the record, this still happens with the latest Eoan kernel (5.3.0-51-generic). [ 68.285097] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 [ 68.286107] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 76.301387] i915 :00:02.0: Resetting rcs0 for hang on rcs0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854872] Re: sru cloud-init (19.2.36 to 19.3.40) Xenial, Bionic, Disco, Eoan
I have verified the SRU on our platform (Exoscale.com) for the following: - Xenial (19.3-41-gc4735dd3-0ubuntu1~16.04.1) - Bionic (19.3-41-gc4735dd3-0ubuntu1~18.04.1) - Disco (19.3-41-gc4735dd3-0ubuntu1~19.04.1) - Eoan (19.3-41-gc4735dd3-0ubuntu1~19.10.1) A branch to add a scripted sru template will be up for review soon to make this process less manual in the future. Thanks for all the good work! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854872 Title: sru cloud-init (19.2.36 to 19.3.40) Xenial, Bionic, Disco, Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1854872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759519] Re: [SRU] Ensure "minimal" images have "minimal" in their /etc/cloud/build.info
** Branch linked: lp:~tribaal/livecd-rootfs/xenial-proposed-build-info- minimal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759519 Title: [SRU] Ensure "minimal" images have "minimal" in their /etc/cloud/build.info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1759519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759519] [NEW] [SRU] Ensure "minimal" images have "minimal" in their /etc/cloud/build.info
Public bug reported: This is a backport to xenial for changes landed in bionic in https://code.launchpad.net/~tribaal/livecd-rootfs/trunk-minimal-build- info/+merge/342096 /etc/cloud/build.info is the file we write to the (image) disk where we track build information. In the current state of things we hardcode "server" in there as the build type, but should instead write "minimal" for minimal builds. [Impact] * Minimized images will have "minimal" in their /etc/cloud/build.info file. [Test Case] * No new autopkgtest was added, however, it is trivial to check the produced image for the appropriate key. [Regression Potential] * Since minimal images have not had an official release yet, none. [Other Info] (none) ** 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/1759519 Title: [SRU] Ensure "minimal" images have "minimal" in their /etc/cloud/build.info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1759519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754586] Re: [FFe request] Enable booting initrd-less with fallback
It seems like I cannot link the branch for some reason. It can be found here: https://code.launchpad.net/~ubuntu-core- dev/grub/+git/ubuntu/+ref/feature/initrd-less-boot-with-fallback -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754586 Title: [FFe request] Enable booting initrd-less with fallback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1754586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754586] [NEW] [FFe request] Enable booting initrd-less with fallback
Public bug reported: The proposed change allows users to enable "initrd-less" boot for kernels that support it, by setting the GRUB_FORCE_PARTUUID configuration variable in /etc/default/grub. In case the user sets the variable today, the initrd line will not be written, and some kernels will boot this way (faster, usually, since there is no IO involved to lift the initrd from disk. This is particularly relevant to cloud images for example). This change allows the GRUB_FORCE_PARTUUID to be set more agressively, by providing a fallback mechanism: should the initrd-less boot fail, grub will try booting the same kernel with an initrd. To achieve this we set a flag in grubenv, that is then cleaned very early in the userspace boot process. The rest of the behavior does not change. Users not using initrd-less boots are unaffected by this change. Users currently using initrd-less boots will still boot - and get a new fallback in case the kernel they boot does not support initrd-less booting (when upgrading or changing kernel flavor for example). Testing done: - Booting with and without initrd on a kernel that supports it (in this particular case the -gcp kernel) - Booting with and without initrd on a kernel that does *not* support it (ensuring the fallback works) - Tried to test the case where userspace sets "next boot" but it looks like the feature allowing to do so regressed. This is independent of this FFe and will be the subject of another bugreport (it's mentioned here since tangentially relevant). ** Affects: grub2 (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/1754586 Title: [FFe request] Enable booting initrd-less with fallback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1754586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656293] Re: OVF metadata for Ubuntu is wrong
** Changed in: cloud-images Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656293 Title: OVF metadata for Ubuntu is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1656293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752882] [NEW] Systemd sysv install fails with update-rc.d: error: unable to read /etc/init.d/enable
Public bug reported: The bionic builds of cloud images for one of our partners fails when installing/enabling NTP in the image during livecdrootfs build: + chroot mountpoint_gce systemctl --root / enable ntp.service Synchronizing state of ntp.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install --root=/ enable ntp update-rc.d: error: unable to read /etc/init.d/enable On Xnox's request I am filing a bug here and assigning to him. Please let me know if you need further information. ** Affects: systemd (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/1752882 Title: Systemd sysv install fails with update-rc.d: error: unable to read /etc/init.d/enable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1752882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1456238] Re: Rewrite urls to mirror
I have a preliminary solution to this working in ppa:tribaal/squid-deb- proxy Note that while it should improve the hit rate, it is also a little hard to see it working since the existing squid logs mention the URL - not the store ID. Feedback welcome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1456238 Title: Rewrite urls to mirror To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1456238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1456238] Re: Rewrite urls to mirror
** Branch linked: lp:~tribaal/squid-deb-proxy/add-store-id-program -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1456238 Title: Rewrite urls to mirror To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1456238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1456238] Re: Rewrite urls to mirror
I started working on a what I believe is a fix for this - using the
"store_id_program" configuration in squid, all known mirrors will be
remapped internally to the distribution's "main" mirror URL, and
therefore result in a cache hit no matter what the mirror used in the
apt configuration is.
Unknown mirrors (mirrors not listed in /usr/share/python-
apt/templates/*) will continue to behave as today.
** Changed in: squid-deb-proxy (Ubuntu)
Status: Triaged => In Progress
** Changed in: squid-deb-proxy (Ubuntu)
Assignee: (unassigned) => Chris Glass (tribaal)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1456238
Title:
Rewrite urls to mirror
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1456238/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743378] Re: Please merge lowmem 1.45 (main) from Debian unstable (main)
** Patch added: "debdiff_lowmem_debian_1.45_to_ubuntu_1.45.debdiff" https://bugs.launchpad.net/ubuntu/+source/lowmem/+bug/1743378/+attachment/5037338/+files/debdiff_lowmem_debian_1.45_to_ubuntu_1.45.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743378 Title: Please merge lowmem 1.45 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lowmem/+bug/1743378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743378] Re: Please merge lowmem 1.45 (main) from Debian unstable (main)
** Patch added: "debdiff_lowmem_ubuntu_1.44_to_ubuntu_1.45.debdiff" https://bugs.launchpad.net/ubuntu/+source/lowmem/+bug/1743378/+attachment/5037339/+files/debdiff_lowmem_ubuntu_1.44_to_ubuntu_1.45.debdiff ** Changed in: lowmem (Ubuntu) Assignee: Chris Glass (tribaal) => (unassigned) ** Changed in: lowmem (Ubuntu) Status: In Progress => Confirmed ** Description changed: - Filing a merge bug to work on it myself. + Please merge lowmem 1.45 (main) from Debian unstable (main) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743378 Title: Please merge lowmem 1.45 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lowmem/+bug/1743378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743378] [NEW] Please merge lowmem 1.45 (main) from Debian unstable (main)
Public bug reported: Please merge lowmem 1.45 (main) from Debian unstable (main) ** Affects: lowmem (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: lowmem (Ubuntu) Assignee: (unassigned) => Chris Glass (tribaal) ** Changed in: lowmem (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/1743378 Title: Please merge lowmem 1.45 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lowmem/+bug/1743378/+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
** Changed in: xenial-backports Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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 1569237] Re: vagrant xenial box is not provided with vagrant/vagrant username and password
This bug is now fixed in ubuntu/xenial64 v20180112.0.0. Update your vagrant boxes: vagrant box update vagrant up vagrant ssh (notice you're "vagrant"). ** Changed in: cloud-images/x-series Status: Fix Committed => Fix Released ** Changed in: cloud-images/trunk Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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 1569237] Re: vagrant xenial box is not provided with vagrant/vagrant username and password
Quick update: We would normally respin an image build right now to put this to bed once and for all, but since we're in the middle of the Meltdown/Spectre crisis it's best to keep the build system available for security-related work. The vagrant image will be built and pushed along with the rest of the images whenever the build system triggers next (so if security-work needs a respin of cloud images the Vagrant box will be published as well). I'll update this bug and mark it fix released once and image is available. -- 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 1569237] Re: vagrant xenial box is not provided with vagrant/vagrant username and password
** Changed in: cloud-images/x-series Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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 1569237] Re: vagrant xenial box is not provided with vagrant/vagrant username and password
The fix landed in the livecd-rootfs package, so expect to see the fix in the ubuntu/xenial64 images very soon (next image build, or the one after). -- 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 1741887] Re: Kubernetes test suite fails on mainline kernel 4.11+
Looks like the failure there is due to the following commit in the linux kernel: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c6c70f4455d1eda91065e93cc4f7eddf4499b105 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741887 Title: Kubernetes test suite fails on mainline kernel 4.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1741887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741887] Re: Kubernetes test suite fails on mainline kernel 4.11+
Kernel in #27 was good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741887 Title: Kubernetes test suite fails on mainline kernel 4.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1741887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741887] Re: Kubernetes test suite fails on mainline kernel 4.11+
Kernel in #25 is good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741887 Title: Kubernetes test suite fails on mainline kernel 4.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1741887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741887] Re: Kubernetes test suite fails on mainline kernel 4.11+
Kernel in #23 is good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741887 Title: Kubernetes test suite fails on mainline kernel 4.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1741887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741887] Re: Kubernetes test suite fails on mainline kernel 4.11+
Kernel in #21 is bad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741887 Title: Kubernetes test suite fails on mainline kernel 4.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1741887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741887] Re: Kubernetes test suite fails on mainline kernel 4.11+
Kernel in #19 is bad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741887 Title: Kubernetes test suite fails on mainline kernel 4.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1741887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741887] Re: Kubernetes test suite fails on mainline kernel 4.11+
Kernel in #17 is bad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741887 Title: Kubernetes test suite fails on mainline kernel 4.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1741887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741887] Re: Kubernetes test suite fails on mainline kernel 4.11+
Kernel in #14 is good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741887 Title: Kubernetes test suite fails on mainline kernel 4.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1741887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741887] Re: Kubernetes test suite fails on mainline kernel 4.11+
Kernel in #12 is good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741887 Title: Kubernetes test suite fails on mainline kernel 4.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1741887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741887] Re: Kubernetes test suite fails on mainline kernel 4.11+
kernel in #10 is bad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741887 Title: Kubernetes test suite fails on mainline kernel 4.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1741887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741887] Re: Kubernetes test suite fails on mainline kernel 4.11+
kernel from #8 is good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741887 Title: Kubernetes test suite fails on mainline kernel 4.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1741887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741887] Re: Kubernetes test suite fails on mainline kernel 4.11+
kernel from #6 is bad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741887 Title: Kubernetes test suite fails on mainline kernel 4.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1741887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741887] Re: Kubernetes test suite fails on mainline kernel 4.11+
Kernel from #4 is good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741887 Title: Kubernetes test suite fails on mainline kernel 4.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1741887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741887] Re: Kubernetes test suite fails on mainline kernel 4.11+
Kernel from #2 is good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741887 Title: Kubernetes test suite fails on mainline kernel 4.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1741887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1627931] Re: SHA256 checksum for ovf in xenial-server-cloudimg-amd64.ova has incorrect path
** Changed in: cloud-images Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627931 Title: SHA256 checksum for ovf in xenial-server-cloudimg-amd64.ova has incorrect path To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1627931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741887] Re: Kubernetes test suite fails on mainline kernel 4.11+
Just tried with v4.15-rc7 from http://kernel.ubuntu.com/~kernel- ppa/mainline/ and the problem persists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741887 Title: Kubernetes test suite fails on mainline kernel 4.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1741887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741887] [NEW] Kubernetes test suite fails on mainline kernel 4.11+
Public bug reported: The to-be-introduced 4.13 based kernel fails the kubernetes test suite (https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci- kubernetes-e2e-gce-ubuntudev2-k8sbeta-default/15?log#log) After rough bisecting (using kernels from http://kernel.ubuntu.com /~kernel-ppa/mainline/ ), it seems some kernel change introduced in 4.11 breaks those tests (4.10 is good, 4.11+ are bad. 4.11-rc* are bad). The minimal reproducer (doesn't have to be on a cloud image - my bionic desktop reproduces it just as well): sudo apt install docker.io sudo docker run -d gcr.io/kubernetes-e2e-test-images/hostexec-amd64:1.0 (note down returned hash) sudo docker exec -it (first few chars of returned hash) /bin/sh # (Inside the docker prompt) timeout -t 1 cat On kernels exhibiting the problem, the "timeout/cat" command above will terminate the container. On kernels exhibiting the problem, docker logs exhibits: # sudo docker logs (first few chars of returned hash) /bin/sh: can't open /fifo: Interrupted system call Kernels that do not exhibit the problem will not terminate after the "timeout" command and return to a normal command prompt. ** Affects: linux-gke (Ubuntu) Importance: High Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Tags: performing-bisect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741887 Title: Kubernetes test suite fails on mainline kernel 4.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1741887/+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
This is when you all can help: as you can see the proposed fix landed in -proposed: if you know how, feel free to build images yourself using the livecd-rootfs package in -proposed. If you would still like to help testing the change but don't know how to build images with livecd-rootfs, please give the following a try and report if it behaves as you would expect. If you have automated test infrastructures in place, it would help to plug this image in as well and see how it fares. vagrant init tribaal/xenial64 vagrant up Note: the "tribaal/xenial64" box is obviously not a production image so please don't treat it as such. Once the changes are verified and landed in -updates, we will build a "real" xenial image with a vagrant user and will update this bug when that happened. -- 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 1569237] Re: vagrant xenial box is not provided with vagrant/vagrant username and password
It seems those bugs are not affecting the xenial release. They are however important to tackle/investigate. The proposed SRU changes can be tested by using the "tribaal/xenial64" image. The SRU process can go ahead/restart as far as I can tell. ** Description changed: It is Vagrant convention that the default user is named "vagrant"[0], and a whole host of scripts assume this to be the default. The xenial box is substantially less useful to Vagrant users with the "ubuntu" user as the default. [0] Search for "user to SSH" in https://www.vagrantup.com/docs/boxes/base.html. Xenial SRU: [impact] * An additional "vagrant" user is available in the created image once the proposed patch is applied. The normal "ubuntu" user is also available, and is conforming to the "ubuntu experience" (it requires cloud-init or another mechanism to be given keys/a password). * The vagrant boxes produced by livecd-rootfs hooks do not conform to the vagrant community's guidelines for box creation, leading vagrant users to use non-official (unaudited) boxes instead, where a "vagrant" user can be found. * A large portion of vagrant automation (3rd party tools, scripts) rely on the presence of a "vagrant" user conforming to the above guidelines. The official ubuntu images are ones of the very few not conforming to the expected user layout. * The official Ubuntu trusty image previously offered a "vagrant" user, and that was lost or omitted when migrating xenial+ to a new build system. This could be considered a regression, although historical context of that change is unfortunately not available anymore. [test case] From a fresh Ubuntu install: * sudo apt install vagrant * vagrant init ubuntu/xenial64 * vagrant up * vagrant ssh notice the user being logged in as is "ubuntu" With either ubuntu/artful64 or ubuntu/trusty64, the same steps log the user in as "vagrant". + An image with the proposed changes was built and uploaded as + "tribaal/xenial64". + [Regression potential] * Users who worked around this behavior in their automation are the most at-risk. They might not be able to login to their boxes anymore, if they worked around by extracting the ubuntu password from the box metadata. If they worked around the problem using cloud-init, no regression will be visible. * The changes introduce a new insecure user, users having worked around the problem on their own might be be unaware of this. * The general consensus in the vagrant community is to install third- party boxes instead of spending time to try and workaround the problems with the official ubuntu boxes, so it is likely to be a limited real- world impact. * The change might affect exotic systems where people for some reason decided to build a non-vagrant machine out of our official vagrant image Note that these regressions will apply to users upgrading their installations to future releases (artful, bionic, and later). -- 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 1701132] Re: Please use xz instead of pxz
Verified by building cloud images using the proposed package and ensuring the resulting artifacts were satisfactory. ** 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/1701132 Title: Please use xz instead of pxz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1701132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701132] Re: Please use xz instead of pxz
(verified with 2.408.25) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701132 Title: Please use xz instead of pxz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1701132/+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
** Description changed: It is Vagrant convention that the default user is named "vagrant"[0], and a whole host of scripts assume this to be the default. The xenial box is substantially less useful to Vagrant users with the "ubuntu" user as the default. [0] Search for "user to SSH" in https://www.vagrantup.com/docs/boxes/base.html. Xenial SRU: [impact] + * An additional "vagrant" user is available in the created image once + the proposed patch is applied. The normal "ubuntu" user is also + available, and is conforming to the "ubuntu experience" (it requires + cloud-init or another mechanism to be given keys/a password). + * The vagrant boxes produced by livecd-rootfs hooks do not conform to the vagrant community's guidelines for box creation, leading vagrant users to use non-official (unaudited) boxes instead, where a "vagrant" user can be found. * A large portion of vagrant automation (3rd party tools, scripts) rely on the presence of a "vagrant" user conforming to the above guidelines. The official ubuntu images are ones of the very few not conforming to the expected user layout. - * An additional "vagrant" user is available in the created image once - the proposed patch is applied. The normal "ubuntu" user is also - available, and is conforming to the "ubuntu experience" (it requires - cloud-init or another mechanism to be given keys/a password). + * The official Ubuntu trusty image previously offered a "vagrant" user, + and that was lost or omitted when migrating xenial+ to a new build + system. This could be considered a regression, although historical + context of that change is unfortunately not available anymore. [test case] From a fresh Ubuntu install: * sudo apt install vagrant * vagrant init ubuntu/xenial64 * vagrant up * vagrant ssh notice the user being logged in as is "ubuntu" - With either ubuntu/artful64 or ubuntu/bionic64, the same steps log the + With either ubuntu/artful64 or ubuntu/trusty64, the same steps log the user in as "vagrant". [Regression potential] * Users who worked around this behavior in their automation are the most at-risk. They might not be able to login to their boxes anymore, if they worked around by extracting the ubuntu password from the box metadata. If they worked around the problem using cloud-init, no regression will be visible. * The changes introduce a new insecure user, users having worked around the problem on their own might be be unaware of this. * The general consensus in the vagrant community is to install third- party boxes instead of spending time to try and workaround the problems with the official ubuntu boxes, so it is likely to be a limited real- world impact. * The change might affect exotic systems where people for some reason decided to build a non-vagrant machine out of our official vagrant image Note that these regressions will apply to users upgrading their installations to future releases (artful, bionic, and later). -- 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 1569237] Re: vagrant xenial box is not provided with vagrant/vagrant username and password
Not yet. This is currently in the sponsorship queue, so for those not familiar with the procedure, point 6 in https://wiki.ubuntu.com/StableReleaseUpdates#Procedure . As you can see using "rmadison livecd-rootfs" another SRU for livecd- rootfs is under way (for something unrelated to this bug), so we need to wait for it to land or be rejected (the full SRU review queue is here https://people.canonical.com/~ubuntu-archive/pending-sru.html). Once the changes are uploaded to xenial-proposed, we will build a test vagrant box for xenial, push it *somewhere* and let you all know. Then we'll need your help! The change won't move forward without your help testing it. You can already contribute some useful testing today by using "ubuntu/artful64" and checking that it behaves according to what you expect (and commenting on this bug, even as simple as "ubuntu/artful64 works for me"). So once it hits proposed we need people to test the box and report here that it works for them, or not. This part is very important! Once it has been verified (tested), then the SRU team will hopefully promote the change, and once that lands the normal build process will publish new vagrant boxes. At this point you'll see the change appear in the boxes you use in your normal vagrant workflow, and I'll mark the bug as "fix released". This process takes time - and unfortunately the timing with end of year holidays is not going to help, but it's under way :) Besides, changing an LTS release of Ubuntu is slow "by design" - is allows for more testing to occur, as nobody wants bad code to be sent to millions of machines. -- 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 1569237] Re: vagrant xenial box is not provided with vagrant/vagrant username and password
** Description changed: It is Vagrant convention that the default user is named "vagrant"[0], and a whole host of scripts assume this to be the default. The xenial box is substantially less useful to Vagrant users with the - "ubuntu" user as the default, and there is limited benefit to having the - "ubuntu" user. + "ubuntu" user as the default. [0] Search for "user to SSH" in https://www.vagrantup.com/docs/boxes/base.html. Xenial SRU: [impact] * The vagrant boxes produced by livecd-rootfs hooks do not conform to the vagrant community's guidelines for box creation, leading vagrant users to use non-official (unaudited) boxes instead, where a "vagrant" user can be found. * A large portion of vagrant automation (3rd party tools, scripts) rely on the presence of a "vagrant" user conforming to the above guidelines. The official ubuntu images are ones of the very few not conforming to the expected user layout. + + * An additional "vagrant" user is available in the created image once + the proposed patch is applied. The normal "ubuntu" user is also + available, and is conforming to the "ubuntu experience" (it requires + cloud-init or another mechanism to be given keys/a password). [test case] From a fresh Ubuntu install: * sudo apt install vagrant * vagrant init ubuntu/xenial64 * vagrant up * vagrant ssh notice the user being logged in as is "ubuntu" With either ubuntu/artful64 or ubuntu/bionic64, the same steps log the user in as "vagrant". [Regression potential] * Users who worked around this behavior in their automation are the most at-risk. They might not be able to login to their boxes anymore, if they worked around by extracting the ubuntu password from the box metadata. If they worked around the problem using cloud-init, no regression will be visible. * The changes introduce a new insecure user, users having worked around the problem on their own might be be unaware of this. * The general consensus in the vagrant community is to install third- party boxes instead of spending time to try and workaround the problems with the official ubuntu boxes, so it is likely to be a limited real- world impact. * The change might affect exotic systems where people for some reason decided to build a non-vagrant machine out of our official vagrant image Note that these regressions will apply to users upgrading their installations to future releases (artful, bionic, and later). -- 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 1569237] Re: vagrant xenial box is not provided with vagrant/vagrant username and password
Clarified the description by the original bug author. The proposed solution for SRUing does *not* drop the ubuntu@ user, and the ubuntu user behaves exactly the same way as with every other cloud- image we deliver. There is an *additional* default user (the "vagrant" user), that conforms to the community's expectations. Please be kind enough to either keep the conversation civil and adhering to the Ubuntu community's code of conduct, or refrain from making further comments. The behavior is being changed, swearing and calling names won't make it go any faster. -- 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 1258597] Re: Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
I've tried to reproduce this issue, unsuccessfully. I remember being affect by it in the past, however. Could someone please confirm: - That it's still an issue on artful (17.10). - What the current version of grub2 they using is, with the output of "apt-cache policy grub2; apt-cache policy grub2-common" - Please share the contents of /etc/default/grub and /etc/default/grub.d/* (in a pastebin ideally, such as pastebin.ubuntu.com) On my machine running artful (grub2-common 2.02~beta3-4ubuntu7), running update-grub yields: $ sudo update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.13.0-19-generic Found initrd image: /boot/initrd.img-4.13.0-19-generic Found linux image: /boot/vmlinuz-4.13.0-17-generic Found initrd image: /boot/initrd.img-4.13.0-17-generic Found memtest86+ image: /memtest86+.elf Found memtest86+ image: /memtest86+.bin done This looks like the desirable behavior. I would like to understand how my machines are different here (I tried on 16.04, 17.04 and 17.10 on GCE 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/1258597 Title: Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1258597/+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
** Branch linked: lp:~tribaal/livecd-rootfs/xenial-proposed-vagrant- user-changes -- 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 1569237] Re: vagrant xenial box is not provided with vagrant/vagrant username and password
Untargetting vagrant as the bug is not in vagrant at all but in the image creation code instead (livecd-rootfs) ** Changed in: vagrant 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/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 1569237] Re: vagrant xenial box is not provided with vagrant/vagrant username and password
** Description changed: It is Vagrant convention that the default user is named "vagrant"[0], and a whole host of scripts assume this to be the default. The xenial box is substantially less useful to Vagrant users with the "ubuntu" user as the default, and there is limited benefit to having the "ubuntu" user. + [0] Search for "user to SSH" in + https://www.vagrantup.com/docs/boxes/base.html. - [0] Search for "user to SSH" in https://www.vagrantup.com/docs/boxes/base.html. + + + Xenial SRU: + + [impact] + + * The vagrant boxes produced by livecd-rootfs hooks do not conform to + the vagrant community's guidelines for box creation, leading vagrant + users to use non-official (unaudited) boxes instead, where a "vagrant" + user can be found. + + * A large portion of vagrant automation (3rd party tools, scripts) rely + on the presence of a "vagrant" user conforming to the above guidelines. + The official ubuntu images are ones of the very few not conforming to + the expected user layout. + + [test case] + + From a fresh Ubuntu install: + + * sudo apt install vagrant + + * vagrant init ubuntu/xenial64 + + * vagrant up + + * vagrant ssh + + notice the user being logged in as is "ubuntu" + + With either ubuntu/artful64 or ubuntu/bionic64, the same steps log the + user in as "vagrant". + + [Regression potential] + + * Users who worked around this behavior in their automation are the most + at-risk. They might not be able to login to their boxes anymore, if they + worked around by extracting the ubuntu password from the box metadata. + If they worked around the problem using cloud-init, no regression will + be visible. + + * The changes introduce a new insecure user, users having worked around + the problem on their own might be be unaware of this. + + * The general consensus in the vagrant community is to install third- + party boxes instead of spending time to try and workaround the problems + with the official ubuntu boxes, so it is likely to be a limited real- + world impact. + + * The change might affect exotic systems where people for some reason + decided to build a non-vagrant machine out of our official vagrant image + + Note that these regressions will apply to users upgrading their + installations to future releases (artful, bionic, and later). ** 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/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 1731492] Re: [SRU] Release "minimized round 2" changes to Xenial
Built a minimized image with https://launchpad.net/ubuntu/+source /livecd-rootfs/2.408.24 and could confirm that the changes are indeed present and that the image boots and behaves normally. Marking verified. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731492 Title: [SRU] Release "minimized round 2" changes to Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1731492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731492] Re: [SRU] Release "minimized round 2" changes to Xenial
This was fixed in bionic/devel in livecd-rootfs 2.482 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731492 Title: [SRU] Release "minimized round 2" changes to Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1731492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716992] Re: ubuntu-cpc lacks common function to reverse setup_mountpoint
I've successfully built new images with the livecd-rootfs in zesty- proposed. Marking verification-done. ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty ** Tags removed: 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/1716992 Title: ubuntu-cpc lacks common function to reverse setup_mountpoint To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1716992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731492] Re: [SRU] Release "minimized round 2" changes to Xenial
Regression potential section updated. ** Description changed: - [Impact]  * Minimized images have their disk footprint further reduced with these    changes.  * Using minimal images can save bandwidth and system resources and we    would like to make those improvements available for Xenial users,    especially since most if not all of our minimized images users care    mostly about LTS releases. [Test Case]  * No new autopkgtest was added, however, an autopkgtest (minimized)    was previously added to test building minimized images. The test logs show    the generated image sizes for ubuntu-cpc images with and without    minimization and the minimized images have to be smaller. [Regression Potential] -  * The changes should not affect images which are not minimized. The + * If images rely on the presence of a populated /var/cache/apt, that +functionality could now break (no such image is known). + * If images rely on /var/cache/debconf/*-old or /var/lib/dpkg/*-old files to +be present, that functionality cloud now break (no such image is known). +  * The package changes should not affect images which are not minimized. The    minimized images in general may not boot on some systems. This is not a -    regression however, that branch does not make the situation better or +    regression however, this branch does not make the situation better or    worse in this regard. [Other Info] (none) ** Description changed: [Impact]  * Minimized images have their disk footprint further reduced with these    changes.  * Using minimal images can save bandwidth and system resources and we    would like to make those improvements available for Xenial users,    especially since most if not all of our minimized images users care    mostly about LTS releases. [Test Case]  * No new autopkgtest was added, however, an autopkgtest (minimized)    was previously added to test building minimized images. The test logs show    the generated image sizes for ubuntu-cpc images with and without    minimization and the minimized images have to be smaller. [Regression Potential] - * If images rely on the presence of a populated /var/cache/apt, that -functionality could now break (no such image is known). - * If images rely on /var/cache/debconf/*-old or /var/lib/dpkg/*-old files to -be present, that functionality cloud now break (no such image is known). +  * If images rely on the presence of a populated /var/cache/apt, that +    functionality could now break (no such image is known). This is believed +to be a functionally "no-op" change. +  * If images rely on /var/cache/debconf/*-old or /var/lib/dpkg/*-old files to +    be present, that functionality cloud now break (no such image is known). +This is believed to be a functionally "no-op" change.  * The package changes should not affect images which are not minimized. The    minimized images in general may not boot on some systems. This is not a    regression however, this branch does not make the situation better or    worse in this regard. [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/1731492 Title: [SRU] Release "minimized round 2" changes to Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1731492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731492] Re: [SRU] Release "minimized round 2" changes to Xenial
** Description changed: - PLEASE IGNORE UNTIL THIS MESSAGE IS REMOVED - (Description incomplete for now - will complete before subscribing the sru team) [Impact]  * Minimized images have their disk footprint further reduced with these    changes.  * Using minimal images can save bandwidth and system resources and we -    would like to make those improvements available for Xenial users, -especially since most if not all of our minimized images users care -mostly about LTS releases. +    would like to make those improvements available for Xenial users, +    especially since most if not all of our minimized images users care +    mostly about LTS releases. [Test Case]  * No new autopkgtest was added, however, an autopkgtest (minimized)    was previously added to test building minimized images. The test logs show -    the generated image sizes for ubuntu-cpc images with and without -minimization and the minimized images have to be smaller. +    the generated image sizes for ubuntu-cpc images with and without +    minimization and the minimized images have to be smaller. [Regression Potential]  * The changes should not affect images which are not minimized. The    minimized images in general may not boot on some systems. This is not a    regression however, that branch does not make the situation better or    worse in this regard. [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/1731492 Title: [SRU] Release "minimized round 2" changes to Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1731492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731492] Re: [SRU] Release "minimized round 2" changes to Xenial
** Description changed: PLEASE IGNORE UNTIL THIS MESSAGE IS REMOVED (Description incomplete for now - will complete before subscribing the sru team) [Impact]  * Minimized images have their disk footprint further reduced with these    changes.  * Using minimal images can save bandwidth and system resources and we -    would like to make those improvements available for Xenial users, especially -    since most if not all of our minimized images users care mostly about -    LTS releases. +    would like to make those improvements available for Xenial users, +especially since most if not all of our minimized images users care +mostly about LTS releases. [Test Case]  * No new autopkgtest was added, however, an autopkgtest (minimized)    was previously added to test building minimized images. The test logs show -    the generated image sizes for ubuntu-cpc images with and without minimization and the minimized images have to be smaller. +    the generated image sizes for ubuntu-cpc images with and without +minimization and the minimized images have to be smaller. [Regression Potential]  * The changes should not affect images which are not minimized. The    minimized images in general may not boot on some systems. This is not a    regression however, that branch does not make the situation better or    worse in this regard. [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/1731492 Title: [SRU] Release "minimized round 2" changes to Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1731492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731492] Re: [SRU] Release "minimized round 2" changes to Xenial
** Description changed: PLEASE IGNORE UNTIL THIS MESSAGE IS REMOVED (Description incomplete for now - will complete before subscribing the sru team) [Impact] - * Minimized images have their disk footprint further reduced with these -changes. - * Using minimal images can save bandwidth and system resources and we -would like to make those improvements available for Xenial users, especially -since most if not all of our minimized images users care mostly about -LTS releases. + Â * Minimized images have their disk footprint further reduced with these + Â Â Â changes. + Â * Using minimal images can save bandwidth and system resources and we + Â Â Â would like to make those improvements available for Xenial users, especially + Â Â Â since most if not all of our minimized images users care mostly about + Â Â Â LTS releases. [Test Case] - * No new autopkgtest was added, however, a previously autopkgtest (minimized) -was previously added to test building minimized images. The test logs show -the generated image sizes for ubuntu-cpc images with and without minimization -and the minimized images have to be smaller. + Â * No new autopkgtest was added, however, an autopkgtest (minimized) + Â Â Â was previously added to test building minimized images. The test logs show + Â Â Â the generated image sizes for ubuntu-cpc images with and without minimization and the minimized images have to be smaller. [Regression Potential] - * The changes should not affect images which are not minimized. The -minimized images in general may not boot on some systems. This is not a -regression however, that branch does not make the situation better or -worse in this regard. + Â * The changes should not affect images which are not minimized. The + Â Â Â minimized images in general may not boot on some systems. This is not a + Â Â Â regression however, that branch does not make the situation better or + Â Â Â worse in this regard. [Other Info] (none) ** Branch linked: lp:~tribaal/livecd-rootfs/xenial-proposed-minimized- round-two -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731492 Title: [SRU] Release "minimized round 2" changes to Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1731492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731492] [NEW] [SRU] Release "minimized round 2" changes to Xenial
Public bug reported: PLEASE IGNORE UNTIL THIS MESSAGE IS REMOVED (Description incomplete for now - will complete before subscribing the sru team) [Impact] * Minimized images have their disk footprint further reduced with these changes. * Using minimal images can save bandwidth and system resources and we would like to make those improvements available for Xenial users, especially since most if not all of our minimized images users care mostly about LTS releases. [Test Case] * No new autopkgtest was added, however, a previously autopkgtest (minimized) was previously added to test building minimized images. The test logs show the generated image sizes for ubuntu-cpc images with and without minimization and the minimized images have to be smaller. [Regression Potential] * The changes should not affect images which are not minimized. The minimized images in general may not boot on some systems. This is not a regression however, that branch does not make the situation better or worse in this regard. [Other Info] (none) ** 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/1731492 Title: [SRU] Release "minimized round 2" changes to Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1731492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731019] Re: gsutil tracebacks on artful with "ImportError: cannot import name json_format"
Turns out I had rogue pacakges in /usr/local/lib/python2.7/dist- pacakges. Nothing to see here, moving along. ** Changed in: google-cloud-sdk (Ubuntu) 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/1731019 Title: gsutil tracebacks on artful with "ImportError: cannot import name json_format" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-cloud-sdk/+bug/1731019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731019] Re: gsutil tracebacks on artful with "ImportError: cannot import name json_format"
Well, I can't reproduce it in a lxc either. I suppose that must be my local environment being weird somehow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731019 Title: gsutil tracebacks on artful with "ImportError: cannot import name json_format" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-cloud-sdk/+bug/1731019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731019] [NEW] gsutil tracebacks on artful with "ImportError: cannot import name json_format"
Public bug reported: google-cloud-sdk 176.0.0-0ubuntu1 exits with a traceback on artful: $ gsutil Traceback (most recent call last): File "/usr/bin/../lib/google-cloud-sdk/bin/bootstrapping/gsutil.py", line 12, in import bootstrapping File "/usr/lib/google-cloud-sdk/bin/bootstrapping/bootstrapping.py", line 22, in from googlecloudsdk.core.credentials import store as c_store File "/usr/lib/google-cloud-sdk/lib/googlecloudsdk/core/credentials/store.py", line 27, in from googlecloudsdk.core import http File "/usr/lib/google-cloud-sdk/lib/googlecloudsdk/core/http.py", line 31, in from googlecloudsdk.core.resource import session_capturer File "/usr/lib/google-cloud-sdk/lib/googlecloudsdk/core/resource/session_capturer.py", line 31, in from googlecloudsdk.core.resource import yaml_printer File "/usr/lib/google-cloud-sdk/lib/googlecloudsdk/core/resource/yaml_printer.py", line 17, in from googlecloudsdk.core.resource import resource_printer_base File "/usr/lib/google-cloud-sdk/lib/googlecloudsdk/core/resource/resource_printer_base.py", line 38, in from googlecloudsdk.core.resource import resource_projector File "/usr/lib/google-cloud-sdk/lib/googlecloudsdk/core/resource/resource_projector.py", line 34, in from google.protobuf import json_format as protobuf_encoding ImportError: cannot import name json_format ** Affects: google-cloud-sdk (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/1731019 Title: gsutil tracebacks on artful with "ImportError: cannot import name json_format" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-cloud-sdk/+bug/1731019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1696663] Re: grub2-common: update-grub shows Warning because of bad /etc/default/grub
*** This bug is a duplicate of bug 1258597 *** https://bugs.launchpad.net/bugs/1258597 ** This bug has been marked a duplicate of bug 1258597 Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1696663 Title: grub2-common: update-grub shows Warning because of bad /etc/default/grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1696663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726798] Re: rpc.statd is not started
*** This bug is a duplicate of bug 1624715 *** https://bugs.launchpad.net/bugs/1624715 ** This bug has been marked a duplicate of bug 1624715 rpc.statd not started automatically -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726798 Title: rpc.statd is not started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1726798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau on a displayport
A bug has been filed upstream here: https://bugs.freedesktop.org/show_bug.cgi?id=103351 ** Bug watch added: freedesktop.org Bugzilla #103351 https://bugs.freedesktop.org/show_bug.cgi?id=103351 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723619 Title: Ubuntu Desktop ISO fails to boot with nouveau on a displayport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau on a displayport
For the record since I forgot to comment previously: kernel in #21 (mainline kernel with suspicious patch reverted) does boot fine with nouveau. (However just reverting it will probably cause other regressions) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723619 Title: Ubuntu Desktop ISO fails to boot with nouveau on a displayport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau on a displayport
I just tested 4.15-rc5 and the problem still persists. A (bit painful) workaround if you don't have a choice: - Boot liveCD, enable "expert mode" (F6 at boot menu" - Edit the boot line to have "blacklist=nouveau modprobe.blacklist=nouveau" BOTH before AND after the "--" at the end of the line. The second part should transfer to your installed system. - Boot into the live session. You now have horribly low resolution but it should allow you to run ubiquity. - Install Ubuntu normally using horrible graphics - Reboot. Hopefully your kernel cmdline parameters were saved and therefore you will reboot into a happy (still horrible) fresh system. Congratulations. - If your reboot crashes odds are parts of the command line was not carried over. No worries, spam ESC to get in the grub menu then edit the kernel's entry to have both "blacklist=nouveau" and "modprobe.blacklist=nouveau". Boot into your ugly new system as previous point. - Install the nvidia proprietary drivers: "sudo ubuntu-drivers" then install the appropriate nvidia-XXX package (was nvidia-384 in my case but it depends on your hardware). - Reboot into hopefully glorious native resolution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723619 Title: Ubuntu Desktop ISO fails to boot with nouveau on a displayport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau on a displayport
Blacklisting nouveau allows a full boot (at a very low screen resolution, obviously). Kernel at #16 fails to boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723619 Title: Ubuntu Desktop ISO fails to boot with nouveau on a displayport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau on a displayport
The kernel at #14 fails to boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723619 Title: Ubuntu Desktop ISO fails to boot with nouveau on a displayport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau on a displayport
As discussed on IRC kaihengfeng and I will sync up tomorrow and bissect the problem together. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723619 Title: Ubuntu Desktop ISO fails to boot with nouveau on a displayport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau on a displayport
Tested all mainline kernels I could find for 4.13-rc*: - 4.13-rc1: DisplayPort setup boots. Login screen appears. Choosing the default option (wayland) results in broken desktop (https://photos.app.goo.gl/xisx9EgTKTFoLXmJ3). Choosing the xorg fallback works perfectly. - 4.13-rc2: DisplayPort setup boots. Login screen appears. Choosing the default option (wayland) results in broken desktop. Choosing the xorg fallback works perfectly. - 4.13-rc3: DisplayPort setup does NOT boot (https://photos.app.goo.gl/ASCw1tDI6fHD1i6w1) - 4.13-rc4: DisplayPort setup does NOT boot. (could not find a -rc5) - 4.13-rc6: DisplayPort setup does NOT boot. - 4.13-rc7: DisplayPort setup does NOT boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723619 Title: Ubuntu Desktop ISO fails to boot with nouveau on a displayport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau on a displayport
I've done further testing as you suggested. Here's a breakdown of my findings: I tested the following kernel versions on 4k + displayport (installed from launchpad librarian, with their matching -extra package and an "update-grub"): - 4.12.0-12: Boots. System seems to crash after a few seconds on the 4k desktop (cannot switch VTs). Maybe a separate bug however, at least it makes it to login+desktop. - 4.12.0-13: Boots. Same symptoms as previous kernel (crashes after a few seconds on the desktop). - 4.13.0-10: Does not boot. Fails with a slightly different output than initially reported (see below) - 4.13.0-11: Does not boot. Same symptoms. - 4.13.0-12: Does not boot. Same symptoms. Screenshot https://photos.app.goo.gl/ztJvK7Im2LVCK0ss1 - 4.13.0-15: Does not boot. Same symptoms. - 4.13.0-16: Does not boot. Same symptoms. None of the tested kernels exhibit any problematic behavior when the HDMI + 1080p screen is plugged in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723619 Title: Ubuntu Desktop ISO fails to boot with nouveau on a displayport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau
Switching the faulty system to using HDMI + 1080p succeeded. Updating bug description. ** Summary changed: - Ubuntu Desktop ISO fails to boot with nouveau + Ubuntu Desktop ISO fails to boot with nouveau on a displayport ** Description changed: On the latest daily artful image (/current as of 2017-01-14), the following occurs on a system with nVidia graphics (on my system, a - GTX970): https://photos.app.goo.gl/gLUva3Vgvtv0lAmj2 + GTX970) when connected to a 4k display over a displayport: + https://photos.app.goo.gl/gLUva3Vgvtv0lAmj2 Steps to reproduce: - Download latest daily image, check checksums, burn to USB - Boot from USB. - Choose "Install Ubuntu" or "try ubuntu" at the menu. This happens on the livecd, but also upon ugrading the system from a previous daily with a different kernel: my "old" daily booted and installed fine with kernel 4.12.0-12, then failed with same error once dist-upgraded. + + On the faulty system I could test with, it seems to *only* happen over + displayport/on a 4k screen (I don't own a non-4k displayport screen to + test the 4k out). ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723619 Title: Ubuntu Desktop ISO fails to boot with nouveau on a displayport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau
Another machine (GTX950m on an integrated screen) boots as well. >From my limited understanding of the error message in the screenshot - perhaps the problem is that the screen is connected to displayport (the GT 640 uses HDMI). The failing system has a 4k screen connected to displayport. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723619 Title: Ubuntu Desktop ISO fails to boot with nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau
I cannot run apport-collect because the livecd doesn't boot :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723619 Title: Ubuntu Desktop ISO fails to boot with nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau
The livecd boots fine on another machine of mine with a nvidia GT 640 (so, an older generation), fromt eh same daily and same image burn. I am out of extra hardware to try this on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723619 Title: Ubuntu Desktop ISO fails to boot with nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723619] [NEW] Ubuntu Desktop ISO fails to boot with nouveau
Public bug reported: On the latest daily artful image (/current as of 2017-01-14), the following occurs on a system with nVidia graphics (on my system, a GTX970): https://photos.app.goo.gl/gLUva3Vgvtv0lAmj2 Steps to reproduce: - Download latest daily image, check checksums, burn to USB - Boot from USB. - Choose "Install Ubuntu" or "try ubuntu" at the menu. This happens on the livecd, but also upon ugrading the system from a previous daily with a different kernel: my "old" daily booted and installed fine with kernel 4.12.0-12, then failed with same error once dist-upgraded. ** Affects: ubuntu-release-notes Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723619 Title: Ubuntu Desktop ISO fails to boot with nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1606600] Re: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported
More investigation is needed. The path *does* fix the problem, but in a way that feels like it is a side effect. Sorry, I should have commented on this bug before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1606600 Title: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1606600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666912] Re: Invoking openvpn removed option --tls-remote
An even better fix for your configuration is to change the dropdown to "verify name exactly", and then remove the "CN=" part of the field if you previously had one in your subject match. Example: "/CN=example.com" becomes "example.com" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666912 Title: Invoking openvpn removed option --tls-remote To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1666912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666912] Re: Invoking openvpn removed option --tls-remote
For people suffering from this, a clean workaround is to change the VPN configuration as follows: - Edit your VPN connection - "VPN" tab - "Advanced" - "TLS Authentication" tab - Change the "Server certificate check" to something that is *not* "verify subject partially". In my case, "Don't verify certificate identity" was chosen since the server's public key is checked anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666912 Title: Invoking openvpn removed option --tls-remote To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1666912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1606600] Re: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported
I *think* the root of the issue is that the assumption in debian/rules # we do not want to run the init script in the postinst/prerm, its # really only useful on shutdown, see Debian bug #645919 dh_installinit $@ --no-start -- stop 10 0 6 . is wrong. It is not only useful on shutdown but also when dpkg-reconfigure is invoked. As a strawman fix, I've uploaded a fixed (xenial) package to https://launchpad.net/~tribaal/+archive/ubuntu/unattended-upgrades It seems to fix the issue in my limited testing: running "dpkg- reconfigure -fnoninteractive unattended-upgrades" does apply changes passed by debconf-set-selections. I'll attach a debdiff to this bug as well, and open a pull request upsteam. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1606600 Title: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1606600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1606600] Re: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported
This debdiff should fix the problem. ** Patch added: "debdiff for xenial" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1606600/+attachment/4826417/+files/unattended-debdiff.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1606600 Title: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1606600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644153] Re: SSL handshake fails on xenial, yakkety, zesty
Xenial debdiff ** Patch added: "Xenial debdiff" https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+attachment/4784081/+files/xenial.deb.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644153 Title: SSL handshake fails on xenial, yakkety, zesty To manage notifications about this bug go to: https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644153] Re: SSL handshake fails on xenial, yakkety, zesty
Yakkety debdiff ** Patch added: "Yakkety debdiff" https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+attachment/4784079/+files/yakkety.deb.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644153 Title: SSL handshake fails on xenial, yakkety, zesty To manage notifications about this bug go to: https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644153] Re: SSL handshake fails on xenial, yakkety, zesty
I re-ran the outlined test-sequence without adding the juju-stable PPA
(like I originally did) to make sure this bug is not a side-effect of
the PPA.
It is not. It is reproducible on vanilla distro as outlined in the
description.
** Description changed:
[Impact]
* The python Juju client cannot make SSL connections to the server anymore,
because TLS v1.0 was deprecated on the server.
* Switching to TLS v1.2 fixes the problem entirely.
* Example failure: http://pastebin.ubuntu.com/23521446/
[Test case]
Steps to reproduce (works in a container, needs a valid juju
environment):
- * Install juju 1.25, ideally from the juju stable ppa: sudo
add-apt-repository ppa:juju/stable; sudo apt-get update; sudo apt-get install
juju-1-default
+ * Install juju 1.25: sudo apt-get install juju-1-default juju-1.25
* Install the package: sudo apt-get install python-jujuclient
* Set up an environment (ec2 works for instance)
* Bootstrap environment: "juju bootstrap # Note your environment's name"
* Run: python -c 'from jujuclient import Environment;
Environment.connect("")'
[Regression Potential]
* None - the package is completely unusable in its current state
because of server changes. It can't get any worse :)
[Other Info]
* The attached patch is the minimal fix - forcing Python to connect over TLS
1.2 instead of forcing TLS 1.0.
* TLS 1.2 connectivity is available in all targeted releases.
* lp:python-jujuclient (upstream) is not affected by the problem, but the
code is much diverged from the version in the archives, with way too many
changes for a SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644153
Title:
SSL handshake fails on xenial, yakkety, zesty
To manage notifications about this bug go to:
https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644153] Re: SSL handshake fails on xenial, yakkety, zesty
** Description changed:
- Package affected: python-jujuclient 0.50.5-0ubuntu1 (on Xenial)
+ [Impact]
- The python Juju client cannot make SSL connections to the server
- anymore, because TLS v1 was deprecated.
+ * The python Juju client cannot make SSL connections to the server anymore,
because TLS v1.0 was deprecated on the server.
+ * Switching to TLS v1.2 fixes the problem entirely.
+ * Example failure: http://pastebin.ubuntu.com/23521446/
- Switching to TLS v1.2 fixes the problem entirely.
+ [Test case]
- Example failure: http://pastebin.ubuntu.com/23521446/
+ Steps to reproduce (works in a container, needs a valid juju
+ environment):
- lp:python-jujuclient is not affected by the problem, but the code is much
diverged from the version in the archives, way too many changes for a SRU.
- The attached patch is the minimal fix - forcing Python to connect over TLS
1.2 instead of forcing TLS 1.0.
+ * Install juju 1.25, ideally from the juju stable ppa: sudo
add-apt-repository ppa:juju/stable; sudo apt-get update; sudo apt-get install
juju-1-default
+ * Install the package: sudo apt-get install python-jujuclient
+ * Set up an environment (ec2 works for instance)
+ * Bootstrap environment: "juju bootstrap # Note your environment's name"
+ * Run: python -c 'from jujuclient import Environment;
Environment.connect("")'
- TLS 1.2 connectivity is available in all affected releases.
+ [Regression Potential]
- Steps to reproduce (works in a container):
+ * None - the package is completely unusable in its current state
+ because of server changes. It can't get any worse :)
- - Install juju 1.25, ideally from the juju stable ppa: sudo
add-apt-repository ppa:juju/stable; sudo apt-get update; sudo apt-get install
juju-1-default
- - Install the package: sudo apt-get install python-jujuclient
- - Set up an environment (ec2 works for instance)
- - Bootstrap environment: "juju bootstrap # Note your environment's name"
- - Run: python -c 'from jujuclient import Environment;
Environment.connect("")'
+ [Other Info]
+
+ * The attached patch is the minimal fix - forcing Python to connect over TLS
1.2 instead of forcing TLS 1.0.
+ * TLS 1.2 connectivity is available in all targeted releases.
+ * lp:python-jujuclient (upstream) is not affected by the problem, but the
code is much diverged from the version in the archives, with way too many
changes for a SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644153
Title:
SSL handshake fails on xenial, yakkety, zesty
To manage notifications about this bug go to:
https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644153] Re: SSL handshake fails on xenial, yakkety, zesty
** Description changed:
Package affected: python-jujuclient 0.50.5-0ubuntu1 (on Xenial)
The python Juju client cannot make SSL connections to the server
anymore, because TLS v1 was deprecated.
Switching to TLS v1.2 fixes the problem entirely.
Example failure: http://pastebin.ubuntu.com/23521446/
- It seems like lp:python-jujuclient already has the fix.
+ lp:python-jujuclient is not affected by the problem, but the code is
+ much diverged from the version in the archives, way too many changes for
+ a SRU.
+
+ Steps to reproduce (works in a container):
+
+ - Install juju 1.25, ideally from the juju stable ppa: sudo
add-apt-repository ppa:juju/stable; sudo apt-get update; sudo apt-get install
juju-1-default
+ - Install the package: sudo apt-get install python-jujuclient
+ - Set up an environment (ec2 works for instance)
+ - Bootstrap environment: "juju bootstrap "
+ - Run: python -c 'from jujuclient import Environment;
Environment.connect("")'
** Description changed:
Package affected: python-jujuclient 0.50.5-0ubuntu1 (on Xenial)
The python Juju client cannot make SSL connections to the server
anymore, because TLS v1 was deprecated.
Switching to TLS v1.2 fixes the problem entirely.
Example failure: http://pastebin.ubuntu.com/23521446/
lp:python-jujuclient is not affected by the problem, but the code is
much diverged from the version in the archives, way too many changes for
a SRU.
Steps to reproduce (works in a container):
- Install juju 1.25, ideally from the juju stable ppa: sudo
add-apt-repository ppa:juju/stable; sudo apt-get update; sudo apt-get install
juju-1-default
- Install the package: sudo apt-get install python-jujuclient
- Set up an environment (ec2 works for instance)
- - Bootstrap environment: "juju bootstrap "
+ - Bootstrap environment: "juju bootstrap # Note your environment's name"
- Run: python -c 'from jujuclient import Environment;
Environment.connect("")'
** Description changed:
Package affected: python-jujuclient 0.50.5-0ubuntu1 (on Xenial)
The python Juju client cannot make SSL connections to the server
anymore, because TLS v1 was deprecated.
Switching to TLS v1.2 fixes the problem entirely.
Example failure: http://pastebin.ubuntu.com/23521446/
- lp:python-jujuclient is not affected by the problem, but the code is
- much diverged from the version in the archives, way too many changes for
- a SRU.
+ lp:python-jujuclient is not affected by the problem, but the code is much
diverged from the version in the archives, way too many changes for a SRU.
+ The attached patch is the minimal fix - forcing Python to connect over TLS
1.2 instead of forcing TLS 1.0.
+
+ TLS 1.2 connectivity is available in all affected releases.
Steps to reproduce (works in a container):
- Install juju 1.25, ideally from the juju stable ppa: sudo
add-apt-repository ppa:juju/stable; sudo apt-get update; sudo apt-get install
juju-1-default
- Install the package: sudo apt-get install python-jujuclient
- Set up an environment (ec2 works for instance)
- Bootstrap environment: "juju bootstrap # Note your environment's name"
- Run: python -c 'from jujuclient import Environment;
Environment.connect("")'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644153
Title:
SSL handshake fails on xenial, yakkety, zesty
To manage notifications about this bug go to:
https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644153] Re: SSL handshake fails on xenial, yakkety, zesty
Once this gets into zesty I shall open another bug for the SRU into yakkety and xenial. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644153 Title: SSL handshake fails on xenial, yakkety, zesty To manage notifications about this bug go to: https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644153] Re: SSL handshake fails on xenial, yakkety, zesty
** Summary changed: - SSL handshake fails on xenial + SSL handshake fails on xenial, yakkety, zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644153 Title: SSL handshake fails on xenial, yakkety, zesty To manage notifications about this bug go to: https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644153] Re: SSL handshake fails on xenial
Debdiff against the current Ubuntu release (zesty)'s version. ** Patch added: "python-jujuclient-debdiff.diff" https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+attachment/4782000/+files/python-jujuclient-debdiff.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644153 Title: SSL handshake fails on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644153] Re: SSL handshake fails on xenial
(for what it's worth, the systems we use have ppa:juju/stable installed, so adding the fix to that PPA would unblock many users already) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644153 Title: SSL handshake fails on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644153] Re: SSL handshake fails on xenial
Patch against the Xenial package. ** Attachment added: "switch-to-tls12" https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+attachment/4781989/+files/switch-to-tls12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644153 Title: SSL handshake fails on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641664] Re: systemd services starting while plymouth is deactivated
(sorry for the shallow bug report - I intended to fill it up some more but it fell through the cracks) Specific units are: plymouth-read-write.service plymouth-quit.service plymouth-quit-wait.service Measured time spent in these: between 100 and 300ms (depending on I/O, I assume). It's a modest win for boot time, but it's also a very simple patch (https://paste.ubuntu.com/23476239/) Despite being referenced in other services as an "after", it seems (from manually applying above patch) that other services start and normally (Before manual patch: https://paste.ubuntu.com/23479860/, after manual patch: https://paste.ubuntu.com/23479865/ , both taken on a machine with no "splash" in cmdline) It seems like a clear cut case of removing "dead" code conditionally (switching on the cmdline presence of "splash" as for the starting service), but of course I might not have the whole picture. I intend to try the same on a desktop machine with and without a "splash" cmdline, with FDE enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641664 Title: systemd services starting while plymouth is deactivated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1641664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641664] [NEW] systemd services starting while plymouth is deactivated
Public bug reported: A few systemd units are started despite plymouth itself not running (nospash is set in cmdline for instance). This results in boot times slightly longer than necessary for those systems. ** Affects: plymouth (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/1641664 Title: systemd services starting while plymouth is deactivated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1641664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640878] Re: grub2 cannot currently generate configuration without initrd
For the record, the branch patching grub2 is: https://code.launchpad.net/~tribaal/ubuntu/+source/grub2/+git/grub2/+ref /add-partuuid-override -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640878 Title: grub2 cannot currently generate configuration without initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1640878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640878] Re: grub2 cannot currently generate configuration without initrd
cyphermox uploaded patched packages to ppa:cyphermox/grub . Steps to assert this works are as follows: - Boot a Yakkety EC2 image (https://console.aws.amazon.com/ec2/home?region=eu-central-1#launchAmi=ami-b87881d7) - Login - sudo apt-add-repository ppa:cyphermox/grub; sudo apt update; sudo apt-upgrade - reboot (assert the system comes back online with no modifications to the grub config) - login again - Get the PARTUUID for the image's disk: ls /dev/disk/by-partuuid/ (should be 6983c98a-01 on this particular image) - Add "GRUB_FORCE_PARTUUID=6983c98a-01" to /etc/default/grub - sudo update-grub - reboot (assert the system comes back online with a root=PARTUUID config) - login again - Add "GRUB_DISABLE_INITD=true" to /etc/default/grub. - sudo update-grub - reboot (assert the system comes back online with root=PARTUUID and no initrd) Currently the Xenial images we build don't expose partuuids (it's an artifact of CPC transitionning to a new build system, AFAIU). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640878 Title: grub2 cannot currently generate configuration without initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1640878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640878] [NEW] grub2 cannot currently generate configuration without initrd
Public bug reported: As it currently stands grub2 cannot create grub.cfg menu entries that do not use an initrd image if one is present but the user does not desire to use it. Furthermore, root= entries only support UUID and LABEL, but neither is an option if booting the kernel without an initrd. Suggestion: Allow grub2 to create configuration files without an "initrd" line and passing PARTUUID as root= entry by adding configuration knobs. ** Affects: grub2 (Ubuntu) Importance: High Assignee: Chris Glass (tribaal) 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/1640878 Title: grub2 cannot currently generate configuration without initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1640878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported
Could somebody summarize that the instructions to get this working on wily are? Thanks a lot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1383184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
