[Bug 1971141] Re: Cannot create /dev/disk/azure/resource softlinks in Gen2 VM
This has been validated for B,F,I,J: https://pastebin.ubuntu.com/p/cmK87VJwVB/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971141 Title: Cannot create /dev/disk/azure/resource softlinks in Gen2 VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1971141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973114] Re: Key trust verification fails on Ubuntu 22.04
Validation of package in Kinetic. The validation was run on Jammy with the Kinetic package installed: I have confirmed the bug on a 22.04 image running on AWS: Jammy stock ec2-instance-connect ssh -vvv output: https://pastebin.ubuntu.com/p/jDCnKrGRFM/plain/ When upgrading the package on the same instance with the one from Kinetic (with backported fix), it works: Jammy upgraded (kinetic) ec2-instance-connect ssh -vvv output: https://pastebin.ubuntu.com/p/bkvGwzZDYB/plain/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973114 Title: Key trust verification fails on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1973114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908090] Re: ubuntu 20.04 kdump fails
** Package changed: kexec-tools (Ubuntu) => kdump-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908090 Title: ubuntu 20.04 kdump fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1908090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966338] Re: openjdk11 update breaks customers
@ludo, this package update may have taken a day or two to be reflected in https://packages.ubuntu.com/bionic/openjdk-11-jdk As you can see, it is there now: openjdk-11-jdk (11.0.14.1+1-0ubuntu1~18.04) And available in the repositories: openjdk-11-jdk | 11.0.14.1+1-0ubuntu1~18.04 | bionic-security | amd64, arm64, armhf, i386, ppc64el, s390x openjdk-11-jdk | 11.0.14.1+1-0ubuntu1~18.04 | bionic-updates | amd64, arm64, armhf, i386, ppc64el, s390x openjdk-11-jdk | 11.0.14.1+1-0ubuntu1~20.04 | focal-security | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x openjdk-11-jdk | 11.0.14.1+1-0ubuntu1~20.04 | focal-updates | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x openjdk-11-jdk | 11.0.14.1+1-0ubuntu1~21.10 | impish-security | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x openjdk-11-jdk | 11.0.14.1+1-0ubuntu1~21.10 | impish-updates | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966338 Title: openjdk11 update breaks customers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1966338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline
For anyone that finds this in a search: Bionic LP tracking this commit release: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963717 Focal: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964422 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965723 Title: audit: improve audit queue handling when "audit=1" on cmdline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958926] Re: CVE escalation request
I've seen the issues with backporting the upstream fix into 2.2 and it does not look like something that is recommended. I'm working with the customer to see if the workaround of using `--disable- luks2-reencryption` to mitigate their security concerns is a good solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958926 Title: CVE escalation request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1958926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958926] [NEW] CVE escalation request
Public bug reported: This bug is to request the Security team address a CVE. The information required is located in the following document: https://docs.google.com/document/d/1pnH9UIQwgTYMKOB__xTEOyPy4K3BGK8OAbMpPwtjUqc/ I don't have the option to select the checkbox for "This bug is a security vulnerability". I added the flag to the URL when I created the bug, so I'm hoping it will be tagged correctly. If it is not, please forward this to the Security team. Thanks, Chris ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4122 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958926 Title: CVE escalation request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1958926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
Works for me as well. Thank you for the quick fix. I thought I was going to have a run a -proposed kernel package for a few weeks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
@Kelsey, thank you for the quick proposed kernel. I installed it in my system here and it solved my amdgpu errors completely. It boots quickly again into the graphical login screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time
Same here with AMD Ryzen 5 3400G on kernel 5.13.0-23-generic It never gets to the graphical login screen. I tested with xorg on 21.10, I did not test wayland. I expect that to be the same. I can do Ctrl+Alt+F4 to get to a text login screen a few mins after booting. This screen is where I saw the "failed to write reg" error. Rolling back to 5.13.0-22 solved this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956386] [NEW] CVE patch request
Public bug reported: This bug is a security vulnerability. I'm reporting this list of CVEs escalated by AWS according to the CVE escalation policy. They are requesting that CVE-2021-44224 and CVE-2021-44790 be reclassified as High as per the NVD rating. The spreadsheet with the official request is: https://docs.google.com/document/d/1ZhTGZIx- Ffnu8G2NyhGQ-cExKsmx1pl4NNR4Ubloh5I/ Thanks, Chris ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: community-security ** Tags added: community-security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956386 Title: CVE patch request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1956386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939255] Re: dhclient triggers systemd-resolved start limit when processing more than 5 interfaces at once
I have tested this on both Focal and Bionic VMs. I ensured that the systemd-resolved unit was in a failed state, restarted it, added the PPA, updated the systemd packages, and rebooted. After every reboot the systemd-resolved was in an "active" state. I tested this with at least 10 reboots on each affected Ubuntu release (b and f). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939255 Title: dhclient triggers systemd-resolved start limit when processing more than 5 interfaces at once To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1939255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935559] [NEW] Cron script uses up all space in /run
Public bug reported: The /etc/cron.daily/aide script sets a variable $TMPBASE to "/run/aide". Each time this script is run (daily), it moves the current data in /run/aide/cron.daily to a directory with a random name: /run/aide/cron.daily.old.XX. When doing this, it preserves all the data from the previous run and adds approximately the same amount of data from the current run. Eventually, all this data will fill up the /run filesystem. This bug will affect anyone that has run the CIS hardening scripts on their systems. We would like this to be fixed so that this is not the default behavior. root@my-server:/run# df -h /run Filesystem Size Used Avail Use% Mounted on tmpfs 796M 796M 0 100% /run root@my-server:/run# du -sch * | grep -vE '^0|K' 794M aide 1.3M udev 796M total root@my-server:/run# du -sch aide/* | grep -vE '^0|K' 99M aide/cron.daily 100M aide/cron.daily.old.1MV71MCH2b 100M aide/cron.daily.old.6Vli33Nc11 99M aide/cron.daily.old.CECwDp5c8s 100M aide/cron.daily.old.HxbiTwfaIW 100M aide/cron.daily.old.lZEPrqsxkR 794M total ** Affects: aide (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/1935559 Title: Cron script uses up all space in /run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1935559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931254] Re: Google Confidential Compute fails to boot with 1.47
** Summary changed: - Google Confidnetial Compute fails to boot with 1.47 + Google Confidential Compute fails to boot with 1.47 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931254 Title: Google Confidential Compute fails to boot with 1.47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1931254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913739] Re: aws: properly support instance types with > 255 cpu cores
Validation results. Proper number of vpus did show up in Bionic, Focal, Groovy, and Xenial-4.15. The Xenial 4.4 kernel only saw 256 vcpus. ubuntu@ip-172-31-5-48:~$ uname -r && nproc 4.4.0-1121-aws 144 ubuntu@ip-172-31-5-48:~$ uname -r && nproc 4.4.0-1122-aws 256 ubuntu@ip-172-31-5-48:~$ uname -r && nproc 4.15.0-1094-aws 448 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913739 Title: aws: properly support instance types with > 255 cpu cores To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1913739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872118] Re: DHCP Cluster crashes after a few hours
Running over a day with the packages from the PPA in place: ● isc-dhcp-server.service - ISC DHCP IPv4 server Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2020-08-04 16:23:19 UTC; 1 day 1h ago Docs: man:dhcpd(8) Main PID: 592 (dhcpd) Tasks: 4 (limit: 4620) Memory: 6.4M CGroup: /system.slice/isc-dhcp-server.service └─592 dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf root@unique-macaw:/home/ubuntu# dpkg -l | grep ppa1 ii isc-dhcp-client 4.4.1-2.1ubuntu6~ppa1 amd64DHCP client for automatically obtaining an IP address ii isc-dhcp-common 4.4.1-2.1ubuntu6~ppa1 amd64common manpages relevant to all of the isc-dhcp packages ii isc-dhcp-server 4.4.1-2.1ubuntu6~ppa1 amd64ISC DHCP server for automatic IP address assignment ii libdns-export11091:9.11.16+dfsg-3~ppa1 amd64Exported DNS Shared Library ii libirs-export161 1:9.11.16+dfsg-3~ppa1 amd64Exported IRS Shared Library ii libisc-export1105:amd64 1:9.11.16+dfsg-3~ppa1 amd64Exported ISC Shared Library ii libisccfg-export163 1:9.11.16+dfsg-3~ppa1 amd64Exported ISC CFG Shared Library -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872118 Title: DHCP Cluster crashes after a few hours To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1872118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886128] Re: walinuxagent blocks DNS fallback to TCP
Issue filed against walinuxagent on GitHub: https://github.com/Azure/WALinuxAgent/issues/1673 ** Bug watch added: github.com/Azure/WALinuxAgent/issues #1673 https://github.com/Azure/WALinuxAgent/issues/1673 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886128 Title: walinuxagent blocks DNS fallback to TCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1886128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
@pandeyvinod.india: Can you help us try to understand why your instances are still panicing? - Do you have a copy of the panic string? - How did you update to the 0.11-4ubuntu2.6 package? - Did you reboot the instance after the package was installed? - Have any of the instances that previously paniced had a second panic? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
@jfirebaugh: According to https://usn.ubuntu.com/4360-2/ The CVE fix is in the latest version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
FYI, version 0.11-4ubuntu2.5 was recently released. If you are still experiencing this issue, the following steps will correct it: 1. Remove the postinst file from the affected package (version 0.11-4ubuntu2.1): sudo rm /var/lib/dpkg/info/libjson-c2\:amd64.postinst 2. Re-run the package configure step to correct its half-installed status: sudo dpkg --configure -a 3. Update the package list from the repository: sudo apt update 4. Upgrade the affected package to the latest version: sudo apt install libjson-c2 5. Reboot to activate the new package: sudo reboot Any user running a version of the libjson-c2 package not equal to 0.11-4ubuntu2.1 will not have to go through these steps and updating the package to the new version will be done the normal way; either through unattended-updates or manual apt upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
@cekkent: Did you reboot between the "dpkg --unpack..." and "sudo apt install -f" steps? That reboot is incredibly important since it switches out the init process from the faulty one in 2.1 to the one in the 2.2 package. The "apt install -f" is intended to run the pre/post install scripts for the package to get it out if the half-installed state. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876334] Re: [Focal] zsys does not clear out old snapshots, potentially filling up bpool
** Attachment added: "zfs_list_-o_space_-r_bpool" https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1876334/+attachment/5364538/+files/zfs_list_-o_space_-r_bpool -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876334 Title: [Focal] zsys does not clear out old snapshots, potentially filling up bpool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1876334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876334] Re: [Focal] zsys does not clear out old snapshots, potentially filling up bpool
** Attachment added: "zfs_list_-t_snap_-r_rpool" https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1876334/+attachment/5364536/+files/zfs_list_-t_snap_-r_rpool -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876334 Title: [Focal] zsys does not clear out old snapshots, potentially filling up bpool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1876334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876334] Re: [Focal] zsys does not clear out old snapshots, potentially filling up bpool
** Attachment added: "zfs_list_-t_snap_-r_bpool" https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1876334/+attachment/5364537/+files/zfs_list_-t_snap_-r_bpool -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876334 Title: [Focal] zsys does not clear out old snapshots, potentially filling up bpool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1876334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876334] Re: [Focal] zsys does not clear out old snapshots, potentially filling up bpool
** Attachment added: "Sosreport from laptop with same symptom" https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1876334/+attachment/5364535/+files/sosreport-neuromancer-2020-05-01-mejivuj.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876334 Title: [Focal] zsys does not clear out old snapshots, potentially filling up bpool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1876334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876334] [NEW] [Focal] zsys does not clear out old snapshots, potentially filling up bpool
Public bug reported: I had been running Focal since the March 4th and installed it via the daily ISO at that time. I opted for ZFS root during the installation process. It was mostly the reason why I went with Focal in the first place. I ran my frequent, almost daily, apt upgrades to get the latest packages and was happy to see a lot of fixes going in during that period until the release date. This frequent apt upgrade cadence created a snapshot in rpool/bpool every time. This feature proved useful for me since I was able to restore to a usable state using this once in the past. I was aware of the rpool snapshots, so I was cleaning them out as they built up, but I did not consider the bpool snapshots. Eventually the small 2GB bpool will fill up with /boot changes and this did happen to me on 30-APR-2020 when I was attempting to upgrade to the latest kernel release. It gave me a cryptic error when trying to run update-initramfs, so I did a G search on the error and it pointed to a disk full situation. When I checked, I saw that only 14MB was free on bpool. I then removed all snapshots that didn't have a coordinating snapshot in rpool and that freed up about 1.2GB in bpool. I will upload the /var/log/apt/term.log file for the time that I attempted the kernel upgrade and it failed. I will also upload a sosreport from my laptop (which has the same issue at this time without me doing any intervention). It didn't get as many apt updates, so it has free space in bpool still. I will leave my laptop in the current state in case you need more information. I will probably send snapshot lists from both bpool and rpool on that laptop. (Once again, I did clean up rpool snapshots manually on the laptop). Let me know if you need more information, log files, command outputs. Great work on this package so far! Chris ** Affects: zsys (Ubuntu) Importance: Undecided Status: New ** Attachment added: "term.log.1" https://bugs.launchpad.net/bugs/1876334/+attachment/5364533/+files/term.log.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876334 Title: [Focal] zsys does not clear out old snapshots, potentially filling up bpool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1876334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869761] Re: Failed to hibernate, reason: Command '/bin/systemctl hibernate' returned non-zero exit status 1
sosreport from an instance launched to reproduce this ** Attachment added: "sosreport-ip-172-31-0-228.hibernate-debugging-20200401165040.tar.xz" https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1869761/+attachment/5358706/+files/sosreport-ip-172-31-0-228.hibernate-debugging-20200401165040.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869761 Title: Failed to hibernate, reason: Command '/bin/systemctl hibernate' returned non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1869761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868169] Re: Cannot build nvidia driver via dkms because compiler doesn't match kernel
cnewcome@wintermute:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" cnewcome@wintermute:~$ cat /proc/version Linux version 5.3.0-42-generic (buildd@lcy01-amd64-019) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 cnewcome@wintermute:~$ gcc --version gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868169 Title: Cannot build nvidia driver via dkms because compiler doesn't match kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868169] Re: Cannot build nvidia driver via dkms because compiler doesn't match kernel
gcc package upgraded in 18.04 and new kernel compiled with that version hasn't been released yet. ** Package changed: gcc-defaults (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Bionic) 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/1868169 Title: Cannot build nvidia driver via dkms because compiler doesn't match kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866407] Re: GPU Driver extension issue (NVIDIA)
** Changed in: walinuxagent (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866407 Title: GPU Driver extension issue (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1866407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866407] Re: GPU Driver extension issue (NVIDIA)
** Attachment added: "repository file created by following the manual Nvidia instructions" https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1866407/+attachment/5337036/+files/cuda-manual.list -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866407 Title: GPU Driver extension issue (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1866407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866407] Re: GPU Driver extension issue (NVIDIA)
Adding repository files from each instance ** Attachment added: "repository file created by walinuxagent" https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1866407/+attachment/5337035/+files/cuda.list -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866407 Title: GPU Driver extension issue (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1866407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866407] Re: GPU Driver extension issue (NVIDIA)
The issue I found is that the walinuxagent Extension installs the 16.04 cuda drivers on Ubuntu 18.04. The issue here is the driver has changed a bit with the inclusion of libglx-mesa0 in Ubuntu 18.04, where it was not previously in 16.04. This causes the failure to install nvidia-driver-* package. It should have the "/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0" library in the nvidia-driver-* package for 16.04, but not for 18.04 since this is already included in the libglx-mesa0 package. If you install the 18.04 Nvidia drivers, using the following instructions, it will succeed: https://developer.nvidia.com/cuda-downloads?target_os=Linux_arch=x86_64_distro=Ubuntu_version=1804_type=debnetwork ** Package changed: linux-azure (Ubuntu) => walinuxagent (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866407 Title: GPU Driver extension issue (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1866407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867460] [NEW] [Focal] 'virsh domcapabilities' fails unless 'virsh capabilites' is run first
Public bug reported: This is affecting my MAAS installation to be able to create VMs through the pods interface. cnewcome@neuromancer:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu Focal Fossa (development branch)" cnewcome@neuromancer:~$ virsh domcapabilities error: failed to get emulator capabilities error: invalid argument: unable to find any emulator to serve 'x86_64' architecture cnewcome@neuromancer:~$ virsh capabilities ... cnewcome@neuromancer:~$ virsh domcapabilities ... cnewcome@neuromancer:~$ dpkg -l | grep libvirt ii gir1.2-libvirt-glib-1.0:amd64 2.0.0-2 amd64GObject introspection files for the libvirt-glib library ii libvirt-clients6.0.0-0ubuntu5 amd64Programs for the libvirt library ii libvirt-daemon 6.0.0-0ubuntu5 amd64Virtualization daemon ii libvirt-daemon-driver-qemu 6.0.0-0ubuntu5 amd64Virtualization daemon QEMU connection driver ii libvirt-daemon-driver-storage-rbd 6.0.0-0ubuntu5 amd64Virtualization daemon RBD storage driver ii libvirt-daemon-system 6.0.0-0ubuntu5 amd64Libvirt daemon configuration files ii libvirt-daemon-system-systemd 6.0.0-0ubuntu5 amd64Libvirt daemon configuration files (systemd) ii libvirt-glib-1.0-0:amd64 2.0.0-2 amd64libvirt GLib and GObject mapping library ii libvirt0:amd64 6.0.0-0ubuntu5 amd64library for interfacing with different virtualization systems ii python3-libvirt6.0.0-0ubuntu3 amd64libvirt Python 3 bindings cnewcome@neuromancer:~$ ** Affects: libvirt (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/1867460 Title: [Focal] 'virsh domcapabilities' fails unless 'virsh capabilites' is run first To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1867460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848739] Re: [linux-azure] Patch to prevent possible data corruption
We had similar behavior on GCE by running Elasticsearch through the following suite of unit tests: https://github.com/elastic/rally-eventdata-track The test suite takes about 5 days to run fully and any corruption can be found by running: zgrep CorruptIndexException /var/log/elasticsearch/elasticsearch.log I was able to reproduce the corruption on all 4.15 kernels, but not on any 5.0 kernels. I was provided a test kernel with the commits mentioned above for 4.15.0-1051-gcp and I ran it through 3 different test iterations without a single report of corruption. As a control, I used the 4.15.0-1051-gcp kernel that is currently available from the proposed pocket (without the commits referenced in this LP) and the testing logged corruption on the 3rd day of tests. Thanks, Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848739 Title: [linux-azure] Patch to prevent possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1848739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853712] [NEW] linux-cloud-tools-*-azure package is not installed when installing linux-azure-edge
Public bug reported: While installing linux-azure package, it installs linux-cloud-tools- azure Bionic + linux-azure The following NEW packages will be installed: linux-azure linux-azure-cloud-tools-5.0.0-1024 linux-azure-headers-5.0.0-1024 linux-azure-tools-5.0.0-1024 linux-cloud-tools-5.0.0-1024-azure linux-cloud-tools-azure linux-headers-5.0.0-1024-azure linux-headers-azure linux-image-5.0.0-1024-azure linux-image-azure linux-modules-5.0.0-1024-azure linux-tools-5.0.0-1024-azure linux-tools-azure 0 upgraded, 13 newly installed, 0 to remove and 280 not upgraded. But during linux-azure-edge package installation, it does not install linux-cloud-tools-azure Bionic + linux-azure-edge The following NEW packages will be installed: crda iw libnl-genl-3-200 linux-azure-5.3-headers-5.3.0-1006 linux-azure-edge linux-headers-5.3.0-1006-azure linux-headers-azure-edge linux-image-5.3.0-1006-azure linux-image-azure-edge linux-modules-5.3.0-1006-azure linux-modules-extra-5.3.0-1006-azure wireless-regdb 0 upgraded, 12 newly installed, 0 to remove and 280 not upgraded. Can we have linux-cloud-tools-azure package included as well. Let me know, if you have any questions. Thank you. ** Affects: linux-azure (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/1853712 Title: linux-cloud-tools-*-azure package is not installed when installing linux-azure-edge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1853712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851590] Re: crypto error/warning when running update-initramfs on 5.0.0-34.36
I don't believe this is anything new with the -34 kernel. I accidentally installed the -32 kernel because I didn't save the sources.list file with -proposed enabled and it gave me the same error. It appears to be because the image is not set up for encryption and the cryptsetup- initramfs package is installed. This appears to be more of an OS image issue than kernel. Console output: root@disco:/home/ubuntu# apt update Get:1 http://security.ubuntu.com/ubuntu disco-security InRelease [97.5 kB] ... Get:47 http://archive.ubuntu.com/ubuntu disco-backports/multiverse amd64 c-n-f Metadata [116 B] Fetched 17.1 MB in 5s (3111 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 43 packages can be upgraded. Run 'apt list --upgradable' to see them. root@disco:/home/ubuntu# uname -a Linux disco 5.0.0-31-generic #33-Ubuntu SMP Mon Sep 30 18:51:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@disco:/home/ubuntu# apt install linux-generic Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: amd64-microcode crda intel-microcode iucode-tool iw libdbus-glib-1-2 libnl-genl-3-200 linux-firmware linux-headers-5.0.0-32 linux-headers-5.0.0-32-generic linux-headers-generic linux-headers-virtual linux-image-5.0.0-32-generic linux-image-generic linux-image-virtual linux-modules-5.0.0-32-generic linux-modules-extra-5.0.0-32-generic linux-virtual thermald wireless-regdb Suggested packages: fdutils linux-doc-5.0.0 | linux-source-5.0.0 linux-tools The following NEW packages will be installed: amd64-microcode crda intel-microcode iucode-tool iw libdbus-glib-1-2 libnl-genl-3-200 linux-firmware linux-generic linux-headers-5.0.0-32 linux-headers-5.0.0-32-generic linux-image-5.0.0-32-generic linux-image-generic linux-modules-5.0.0-32-generic linux-modules-extra-5.0.0-32-generic thermald wireless-regdb The following packages will be upgraded: linux-headers-generic linux-headers-virtual linux-image-virtual linux-virtual 4 upgraded, 17 newly installed, 0 to remove and 24 not upgraded. Need to get 148 MB of archives. After this operation, 796 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 libnl-genl-3-200 amd64 3.4.0-1 [11.1 kB] Get:2 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 wireless-regdb all 2018.05.09-0ubuntu1 [11.0 kB] Get:3 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 iw amd64 5.0.1-1 [87.7 kB] Get:4 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 crda amd64 3.18-1build1 [63.5 kB] Get:5 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 iucode-tool amd64 2.3.1-1 [45.6 kB] Get:6 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 libdbus-glib-1-2 amd64 0.110-4 [58.7 kB] Get:7 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-firmware all 1.178.3 [78.2 MB] Get:8 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-modules-5.0.0-32-generic amd64 5.0.0-32.34 [13.8 MB] Get:9 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-image-5.0.0-32-generic amd64 5.0.0-32.34 [8424 kB] Get:10 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-modules-extra-5.0.0-32-generic amd64 5.0.0-32.34 [33.5 MB] Get:11 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 intel-microcode amd64 3.20190618.0ubuntu0.19.04.1 [1922 kB] Get:12 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 amd64-microcode amd64 3.20181128.1ubuntu1 [32.3 kB] Get:13 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-image-generic amd64 5.0.0.32.33 [2368 B] Get:14 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-virtual amd64 5.0.0.32.33 [1860 B] Get:15 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-image-virtual amd64 5.0.0.32.33 [2344 B] Get:16 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-headers-virtual amd64 5.0.0.32.33 [1844 B] Get:17 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-headers-5.0.0-32 all 5.0.0-32.34 [10.8 MB] Get:18 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-headers-5.0.0-32-generic amd64 5.0.0-32.34 [1246 kB] Get:19 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-headers-generic amd64 5.0.0.32.33 [2324 B] Get:20 http://nova.clouds.archive.ubuntu.com/ubuntu disco-updates/main amd64 linux-generic amd64 5.0.0.32.33 [1868 B] Get:21 http://nova.clouds.archive.ubuntu.com/ubuntu disco/main amd64 thermald amd64 1.8.0-1ubuntu1 [187 kB] Fetched 148 MB in 5s (32.1 MB/s) Selecting previously unselected package libnl-genl-3-200:amd64. (Reading database ... 60203 files and directories
[Bug 1847641] Re: fdatasync performance regression on 5.0 kernels
Disco verification: SUCCESS (except for crypt error not seen on Eoan when running update-initramfs) The package did experience a crypt error while the finish scripts were running update-initramfs: update-initramfs: Generating /boot/initrd.img-5.0.0-34-generic cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. I1107 01:20:47.416048 1 iotest.go:34] Starting loop... I1107 01:20:47.416130 1 iotest.go:38] Generating chunk done. Took: 35.664µs I1107 01:20:47.416180 1 iotest.go:45] Writing chunk done. Took: 39.66µs I1107 01:20:47.418845 1 iotest.go:49] Fdatasync done. Took: 2.655269ms I1107 01:20:48.419035 1 iotest.go:34] Starting loop... I1107 01:20:48.419118 1 iotest.go:38] Generating chunk done. Took: 35.264µs I1107 01:20:48.419179 1 iotest.go:45] Writing chunk done. Took: 48.533µs I1107 01:20:48.421913 1 iotest.go:49] Fdatasync done. Took: 2.717937ms I1107 01:20:49.422100 1 iotest.go:34] Starting loop... I1107 01:20:49.422178 1 iotest.go:38] Generating chunk done. Took: 28.414µs I1107 01:20:49.42 1 iotest.go:45] Writing chunk done. Took: 31.93µs I1107 01:20:49.424807 1 iotest.go:49] Fdatasync done. Took: 2.5748ms I1107 01:20:50.425013 1 iotest.go:34] Starting loop... I1107 01:20:50.425100 1 iotest.go:38] Generating chunk done. Took: 26.333µs I1107 01:20:50.425153 1 iotest.go:45] Writing chunk done. Took: 35.647µs I1107 01:20:50.429562 1 iotest.go:49] Fdatasync done. Took: 4.399009ms I1107 01:20:51.429771 1 iotest.go:34] Starting loop... I1107 01:20:51.429857 1 iotest.go:38] Generating chunk done. Took: 35.83µs I1107 01:20:51.429900 1 iotest.go:45] Writing chunk done. Took: 30.646µs I1107 01:20:51.432736 1 iotest.go:49] Fdatasync done. Took: 2.828024ms # uname -a Linux cnewcomer-1573089286 5.0.0-34-generic #36-Ubuntu SMP Wed Oct 30 05:16:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847641 Title: fdatasync performance regression on 5.0 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847641] Re: fdatasync performance regression on 5.0 kernels
Eoan Verification: SUCCESS Eoan: I1107 01:13:14.719551 1 iotest.go:34] Starting loop... I1107 01:13:14.719636 1 iotest.go:38] Generating chunk done. Took: 29.737µs I1107 01:13:14.719693 1 iotest.go:45] Writing chunk done. Took: 44.206µs I1107 01:13:14.723320 1 iotest.go:49] Fdatasync done. Took: 3.616042ms I1107 01:13:15.723595 1 iotest.go:34] Starting loop... I1107 01:13:15.723664 1 iotest.go:38] Generating chunk done. Took: 26.125µs I1107 01:13:15.723709 1 iotest.go:45] Writing chunk done. Took: 32.533µs I1107 01:13:15.726895 1 iotest.go:49] Fdatasync done. Took: 3.177235ms I1107 01:13:16.727150 1 iotest.go:34] Starting loop... I1107 01:13:16.727263 1 iotest.go:38] Generating chunk done. Took: 17.628µs I1107 01:13:16.727331 1 iotest.go:45] Writing chunk done. Took: 37.676µs I1107 01:13:16.730810 1 iotest.go:49] Fdatasync done. Took: 3.468056ms I1107 01:13:17.731056 1 iotest.go:34] Starting loop... I1107 01:13:17.731140 1 iotest.go:38] Generating chunk done. Took: 36.62µs I1107 01:13:17.731186 1 iotest.go:45] Writing chunk done. Took: 33.776µs I1107 01:13:17.734490 1 iotest.go:49] Fdatasync done. Took: 3.294855ms I1107 01:13:18.734697 1 iotest.go:34] Starting loop... I1107 01:13:18.734782 1 iotest.go:38] Generating chunk done. Took: 28.668µs I1107 01:13:18.734832 1 iotest.go:45] Writing chunk done. Took: 36.553µs I1107 01:13:18.737912 1 iotest.go:49] Fdatasync done. Took: 3.070391ms # uname -a Linux cnewcomer-1573088148 5.3.0-21-generic #22-Ubuntu SMP Tue Oct 29 22:55:51 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847641 Title: fdatasync performance regression on 5.0 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846485] Re: lttng causes crash with 5.0 based kernel
This was reproduced with the linux-generic kernels. The generic kernels
that experience this behavior are: 5.0.0-31-generic and
5.3.0-16-generic.
This behavior was corrected when the following upstream commits were added to
the lttng-modules package in Bionic:
2ca0c84f0b ("Fix: mm: create the new vm_fault_t type (v5.1)")
d6cd2c9598 ("Fix: pipe: stop using ->can_merge (v5.1)")
1b7b9c650e ("Fix: Remove start and number from syscall_get_arguments() args
(v5.1)")
d88e2fe5c3 ("fix: timer/trace: Improve timer tracing (v5.2)")
36ac1139f0 ("fix: mm/vmscan: drop may_writepage and classzone_idx from direct
reclaim begin template (v5.2)")
a6a26911cc ("fix: random: only read from /dev/random after its pool has
received 128 bits (v5.2)")
** Package changed: linux-azure (Ubuntu) => lttng-modules (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846485
Title:
lttng causes crash with 5.0 based kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1846485/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843036] Re: [regression] SNMP missing disks in hrStorageTable
VALIDATION: BIONIC: PASSED See attached typescript output. The snmpd package works as intended on Bionic. The snmpwalk returns the data expected and it doesn't force direct-mapped autofs filesystems to mount every time you run the snmpwalk. ** Attachment added: "bionic_validate.txt" https://bugs.launchpad.net/ubuntu/bionic/+source/net-snmp/+bug/1843036/+attachment/5287619/+files/bionic_validate.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843036 Title: [regression] SNMP missing disks in hrStorageTable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1843036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843036] Re: [regression] SNMP missing disks in hrStorageTable
VALIDATION: XENIAL: PASSED See attached typescript output. The snmpd package works as intended on Xenial. The snmpwalk returns the data expected and it doesn't force direct-mapped autofs filesystems to mount every time you run the snmpwalk. ** Attachment added: "xenial_validate.txt" https://bugs.launchpad.net/ubuntu/bionic/+source/net-snmp/+bug/1843036/+attachment/5287618/+files/xenial_validate.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843036 Title: [regression] SNMP missing disks in hrStorageTable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1843036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843036] Re: [regression] SNMP missing disks in hrStorageTable
VALIDATION: DISCO: PASSED See attached typescript output. The snmpd package works as intended on Disco. The snmpwalk returns the data expected and it doesn't force direct-mapped autofs filesystems to mount every time you run the snmpwalk. ** Attachment added: "disco_validate.txt" https://bugs.launchpad.net/ubuntu/bionic/+source/net-snmp/+bug/1843036/+attachment/5287620/+files/disco_validate.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843036 Title: [regression] SNMP missing disks in hrStorageTable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1843036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843036] Re: [regression] SNMP missing disks in hrStorageTable
I also tested the test package, 5.7.3+dfsg-1.8ubuntu3.2+testpkg20190906b3, in a direct-mapped autofs environment that was the basis for the fix that caused this regression. The test package does fix the original autofs "mount everything" issue and allows for snmpwalk to monitor the mounted disks as well. I even tested it with a single autofs directory mounted and it worked with that as well. root@test1:~# df Filesystem 1K-blocksUsed Available Use% Mounted on udev 989468 0989468 0% /dev tmpfs 204136 672203464 1% /run /dev/vda1 10254592 3972248 5742084 41% / tmpfs1020664 0 1020664 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs1020664 0 1020664 0% /sys/fs/cgroup tmpfs 204132 0204132 0% /run/user/1000 root@test1:~# patch /etc/snmp/snmpd.conf < /var/tmp/snmpd.conf.patch patching file /etc/snmp/snmpd.conf root@test1:~# systemctl restart snmpd root@test1:~# snmpwalk -v2c -cpublic localhost 1.3.6.1.2.1.25.2.3.1.3 iso.3.6.1.2.1.25.2.3.1.3.1 = STRING: "Physical memory" iso.3.6.1.2.1.25.2.3.1.3.3 = STRING: "Virtual memory" iso.3.6.1.2.1.25.2.3.1.3.6 = STRING: "Memory buffers" iso.3.6.1.2.1.25.2.3.1.3.7 = STRING: "Cached memory" iso.3.6.1.2.1.25.2.3.1.3.8 = STRING: "Shared memory" iso.3.6.1.2.1.25.2.3.1.3.10 = STRING: "Swap space" iso.3.6.1.2.1.25.2.3.1.3.31 = STRING: "/" iso.3.6.1.2.1.25.2.3.1.3.37 = STRING: "/run" iso.3.6.1.2.1.25.2.3.1.3.39 = STRING: "/dev/shm" iso.3.6.1.2.1.25.2.3.1.3.40 = STRING: "/run/lock" iso.3.6.1.2.1.25.2.3.1.3.41 = STRING: "/sys/fs/cgroup" iso.3.6.1.2.1.25.2.3.1.3.63 = STRING: "/run/user/1000" iso.3.6.1.2.1.25.2.3.1.3.63 = No more variables left in this MIB View (It is past the end of the MIB tree) root@test1:~# dpkg -l | grep snmpd ii snmpd 5.7.3+dfsg-1.8ubuntu3.2+testpkg20190906b3 amd64SNMP (Simple Network Management Protocol) agents ### WITH 1 AUTOFS DIRECTORY MOUNTED: /media/test100 ### root@test1:~# ls /media/test100 root@test1:~# snmpwalk -v2c -cpublic localhost 1.3.6.1.2.1.25.2.3.1.3 iso.3.6.1.2.1.25.2.3.1.3.1 = STRING: "Physical memory" iso.3.6.1.2.1.25.2.3.1.3.3 = STRING: "Virtual memory" iso.3.6.1.2.1.25.2.3.1.3.6 = STRING: "Memory buffers" iso.3.6.1.2.1.25.2.3.1.3.7 = STRING: "Cached memory" iso.3.6.1.2.1.25.2.3.1.3.8 = STRING: "Shared memory" iso.3.6.1.2.1.25.2.3.1.3.10 = STRING: "Swap space" iso.3.6.1.2.1.25.2.3.1.3.31 = STRING: "/" iso.3.6.1.2.1.25.2.3.1.3.37 = STRING: "/run" iso.3.6.1.2.1.25.2.3.1.3.39 = STRING: "/dev/shm" iso.3.6.1.2.1.25.2.3.1.3.40 = STRING: "/run/lock" iso.3.6.1.2.1.25.2.3.1.3.41 = STRING: "/sys/fs/cgroup" iso.3.6.1.2.1.25.2.3.1.3.63 = STRING: "/run/user/1000" iso.3.6.1.2.1.25.2.3.1.3.162 = STRING: "/media/test100" iso.3.6.1.2.1.25.2.3.1.3.162 = No more variables left in this MIB View (It is past the end of the MIB tree) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843036 Title: [regression] SNMP missing disks in hrStorageTable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1843036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835818] Re: snmpd causes autofs mount points to be mounted on service start/restart
** Attachment added: "Bionic typescript output" https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1835818/+attachment/5286499/+files/bionic_validate.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835818 Title: snmpd causes autofs mount points to be mounted on service start/restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1835818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835818] Re: snmpd causes autofs mount points to be mounted on service start/restart
** Attachment added: "Disco typescript output" https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1835818/+attachment/5286500/+files/disco_validate.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835818 Title: snmpd causes autofs mount points to be mounted on service start/restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1835818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835818] Re: snmpd causes autofs mount points to be mounted on service start/restart
Validation: I can confirm the fix for these is working on xenial, bionic, and disco. I will include typescript outputs of each Ubuntu version. ** Attachment added: "Xenial typescript output" https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1835818/+attachment/5286498/+files/xenial_validate.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835818 Title: snmpd causes autofs mount points to be mounted on service start/restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1835818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834681] [NEW] Enable napi_tx for GCP/GKE kernels
Public bug reported: Background: Napi_tx is a Linux kernel feature that makes the virtio driver call the skb destructor after the packets are actually “out” (i.e., at TX completion interrupt), as opposed to immediately after the packets are enqueued. This provides socket backpressure and is critical for features such as TSQ. Enabling napi_tx in Cloud guests is an indispensable link in the chain of end-to-end backpressure from USPS all the way up to the guest applications. It would help reduce bufferbloat, packet drops and/or avoid HoL blocking when the traffic from the VMs are rate limited (due to congestion/BwE/etc). The GCP networking engineering teams have asked us to include and enable napi_tx on the major guest OS's on the platform. They have 6 months of performance and regression testing and are comfortable moving forward with this broadly. The main request is to change this module parameter: +++ b/drivers/net/virtio_net.c @@ -26,7 +26,7 @@ static int napi_weight = NAPI_POLL_WEIGHT; module_param(napi_weight, int, 0444); -static bool csum = true, gso = true, napi_tx; +static bool csum = true, gso = true, napi_tx = true; That is either the above kernel change or a configuration change at module load. Note that that also gives us a simple resolution in the unlikely case that this causes a regression on some workloads. Besides the main switch, kernels need these other prerequisite patches: The main feature, in 4.12-rc1: 1d11e732e7d50 virtio-net: use netif_tx_napi_add for tx napi 78a57b482aa53 virtio-net: on tx, only call napi_disable if tx napi is on bdb12e0d2ffc8 virtio-net: keep tx interrupts disabled unless kick 7b0411ef4aa69 virtio-net: clean tx descriptors from rx napi ea7735d97ba90 virtio-net: move free_old_xmit_skbs b92f1e6751a6a virtio-net: transmit napi e4e8452a4ab30 virtio-net: napi helper functions Virtio-net queue affinity, in 4.19-rc1: 2ca653d607ce5 virtio_net: Stripe queue affinities across cores. 19e226e8cc5da virtio: Make vp_set_vq_affinity() take a mask. 9af18e56d43ca cpumask: make cpumask_next_wrap available without smp A nice to have is ethtool support to test whether the feature is enabled, in 5.1-rc1: 133bbb18ab1a2 virtio-net: per-queue RPS config ** Affects: linux-gcp (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/1834681 Title: Enable napi_tx for GCP/GKE kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1834681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834235] [NEW] Request backport of ceph commits into bionic Edit
Public bug reported: Our internal cluster has run into a few ceph client related issues, which were root caused to be resolved by the following commits: https://github.com/ceph/ceph-client/commit/f42a774a2123e6b29bb0ca296e166d0f089e9113 https://github.com/ceph/ceph-client/commit/093ea205acd4b047cf5aacabc0c6ffecf198d2a9 Can you please backport these into bionic? 3e1d0452edcee ceph: avoid iput_final() while holding mutex or in dispatch thread 1cf89a8dee5e6 ceph: single workqueue for inode related works ** Affects: linux (Ubuntu) Importance: High Assignee: Connor Kuehl (connork) Status: New ** Description changed: - Our internal DGX cluster has run into a few ceph client related issues, which were root caused to be resolved by the following commits: + Our internal cluster has run into a few ceph client related issues, which were root caused to be resolved by the following commits: https://github.com/ceph/ceph-client/commit/f42a774a2123e6b29bb0ca296e166d0f089e9113 https://github.com/ceph/ceph-client/commit/093ea205acd4b047cf5aacabc0c6ffecf198d2a9 Can you please backport these into bionic? 3e1d0452edcee ceph: avoid iput_final() while holding mutex or in dispatch thread 1cf89a8dee5e6 ceph: single workqueue for inode related works -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834235 Title: Request backport of ceph commits into bionic Edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830740] Re: [linux-azure] Delay during boot of some instance sizes
** Attachment added: "cloud-init collect-logs" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+attachment/5271884/+files/cloud-init.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830740 Title: [linux-azure] Delay during boot of some instance sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830740] Re: [linux-azure] Delay during boot of some instance sizes
I created a test instance and was able to produce most of the data requested. Attachments incoming. ** Attachment added: "cloud-init analyze show" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+attachment/5271877/+files/ci-analyze-show.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830740 Title: [linux-azure] Delay during boot of some instance sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830740] Re: [linux-azure] Delay during boot of some instance sizes
** Attachment added: "cloud-init analyze blame" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+attachment/5271879/+files/ci-analyze-blame.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830740 Title: [linux-azure] Delay during boot of some instance sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830740] Re: [linux-azure] Delay during boot of some instance sizes
** Attachment added: "cloud-init analyze dump" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+attachment/5271878/+files/ci-analyze-dump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830740 Title: [linux-azure] Delay during boot of some instance sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830740] Re: [linux-azure] Delay during boot of some instance sizes
This sosreport contains the systemd analyze blame output. It is from a test instance that I was able to reproduce this issue on. ** Attachment added: "sosreport-cnewcomer-1559258602-20190530234322.tar.xz" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+attachment/5271880/+files/sosreport-cnewcomer-1559258602-20190530234322.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830740 Title: [linux-azure] Delay during boot of some instance sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
I have a laptop that exhibits this behavior. The switching of the ttys will hang about 95% of the time (1 in 20). With this test package, it now works 100% of the time as long as I don't switch to tty1. I tested it 5 times in a row with a reboot between each. I can Ctrl+Alt+F# without any issue. If I run "sudo chvt 1", it will not switch out of that tty again until I reboot my laptop again. Using 2 through 12 all work and switch the display to that tty. Thanks, Chris Newcomer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817738 Title: Can't change virtual terminal when auto-login is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1817738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775195] Re: [sync][sru]sosreport v3.6
[ VERIFICATION COSMIC ] libvirt VM: $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.10 DISTRIB_CODENAME=cosmic DISTRIB_DESCRIPTION="Ubuntu 18.10" $ dpkg -l | grep sosreport ii sosreport 3.6-1ubuntu0.18.10.1 amd64Set of tools to gather troubleshooting data from a system $ sudo sosreport sosreport (version 3.6) This command will collect system configuration and diagnostic information from this Ubuntu system. An archive containing the collected information will be generated in /tmp/sos.3wnd3fwh. For more information on Ubuntu visit: http://www.ubuntu.com/ The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Press ENTER to continue, or CTRL-C to quit. Please enter the case id that you are generating this report for []: Setting up archive ... Setting up plugins ... Running plugins. Please wait ... Finishing plugins [Running: ubuntu] Finished running plugins Creating compressed archive... Your sosreport has been generated and saved in: /tmp/sosreport-test2.-20181116002912.tar.xz The checksum is: d09c4ddd96bc6d4b88e7aa1a5ca5b663 Please send this file to your support representative. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775195 Title: [sync][sru]sosreport v3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1775195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775195] Re: [sync][sru]sosreport v3.6
[ VERIFICATION XENIAL ] libvirt VM: $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS" $ dpkg -l | grep sosreport ii sosreport 3.6-1ubuntu0.16.04.1 amd64Set of tools to gather troubleshooting data from a system $ sudo sosreport sosreport (version 3.6) This command will collect system configuration and diagnostic information from this Ubuntu system. An archive containing the collected information will be generated in /tmp/sos.it_zntr5. For more information on Ubuntu visit: http://www.ubuntu.com/ The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Press ENTER to continue, or CTRL-C to quit. Please enter the case id that you are generating this report for []: Setting up archive ... Setting up plugins ... Running plugins. Please wait ... Starting 1/64 acpid [Running: acpid] Starting 2/64 apache [Running: apache] Starting 3/64 apparmor[Running: apache apparmor] Starting 4/64 apport [Running: apache apparmor apport] Starting 5/64 apt [Running: apache apparmor apport apt] Starting 6/64 ata [Running: apache apparmor apt ata] Starting 7/64 block [Running: apache apparmor apt block] Starting 8/64 boot[Running: apparmor apt block boot] Starting 9/64 btrfs [Running: apparmor apt block btrfs] Starting 10/64 ceph[Running: apt block btrfs ceph] Starting 11/64 cgroups [Running: apt block ceph cgroups] Starting 12/64 cron[Running: apt block cgroups cron] Starting 13/64 crypto [Running: apt block cgroups crypto] Starting 14/64 date[Running: apt block cgroups date] Starting 15/64 dbus[Running: apt block cgroups dbus] Starting 16/64 devicemapper[Running: apt block cgroups devicemapper] Starting 17/64 devices [Running: apt block cgroups devices] Starting 18/64 dpkg[Running: apt block cgroups dpkg] Starting 19/64 filesys [Running: apt block cgroups filesys] Starting 20/64 hardware[Running: apt cgroups filesys hardware] Starting 21/64 host[Running: apt cgroups filesys host] Starting 22/64 i18n[Running: apt cgroups host i18n] Starting 23/64 iscsi [Running: apt cgroups host iscsi] Starting 24/64 java[Running: apt cgroups iscsi java] Starting 25/64 kernel [Running: apt cgroups java kernel] Starting 26/64 last[Running: apt cgroups kernel last] Starting 27/64 libraries [Running: apt cgroups kernel libraries] Starting 28/64 libvirt [Running: apt cgroups kernel libvirt] Starting 29/64 logrotate [Running: apt cgroups kernel logrotate] Starting 30/64 logs[Running: apt cgroups kernel logs] Starting 31/64 lvm2[Running: apt cgroups kernel lvm2] Starting 32/64 lxd [Running: apt cgroups lvm2 lxd] Starting 33/64 maas[Running: apt cgroups lxd maas] Starting 34/64 md [Running: apt cgroups maas md] Starting 35/64 memory [Running: apt cgroups maas memory] Starting 36/64 multipath [Running: apt cgroups maas multipath] Starting 37/64 named [Running: apt cgroups maas named] Starting 38/64 networking [Running: apt cgroups maas networking] Starting 39/64 ntp [Running: apt cgroups maas ntp] Starting 40/64 openssl [Running: apt maas ntp openssl] Starting 41/64 pam [Running: apt maas ntp pam] Starting 42/64 pci [Running: apt maas pam pci] Starting 43/64 perl[Running: apt maas pci perl] Starting 44/64 postgresql [Running: apt maas pci postgresql] Starting 45/64 procenv [Running: apt maas pci procenv] Starting 46/64 process [Running: apt maas pci process] Starting 47/64 processor [Running: apt maas process processor] Starting 48/64 python [Running: apt maas process python] Starting 49/64 release
[Bug 1775195] Re: [sync][sru]sosreport v3.6
[ VERIFICATION BIONIC ] Bare metal: $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" $ dpkg -l | grep sosreport ii sosreport 3.6-1ubuntu0.18.04.1 amd64Set of tools to gather troubleshooting data from a system $ sudo sosreport sosreport (version 3.6) This command will collect system configuration and diagnostic information from this Ubuntu system. An archive containing the collected information will be generated in /tmp/sos.ojmc_spl. For more information on Ubuntu visit: http://www.ubuntu.com/ The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Press ENTER to continue, or CTRL-C to quit. Please enter the case id that you are generating this report for []: Setting up archive ... Setting up plugins ... Running plugins. Please wait ... Starting 1/64 acpid [Running: acpid] Starting 2/64 anacron [Running: anacron] Starting 3/64 apparmor[Running: anacron apparmor] Starting 4/64 apport [Running: anacron apparmor apport] Starting 5/64 apt [Running: anacron apparmor apport apt] Starting 6/64 ata [Running: apparmor apport apt ata] Starting 7/64 block [Running: apparmor apport apt block] Starting 8/64 boot[Running: apparmor apt block boot] Starting 9/64 btrfs [Running: apparmor apt block btrfs] Starting 10/64 canonical_livepatch [Running: apparmor apt block canonical_live Starting 11/64 ceph[Running: apt block canonical_livepatch ceph]Starting 12/64 cgroups [Running: apt block ceph cgroups]Starting 13/64 cron[Running: apt block cgroups cron]Starting 14/64 crypto [Running: apt block cgroups crypto] Starting 15/64 cups[Running: apt block cgroups cups]Starting 16/64 date[Running: apt block cgroups date]Starting 17/64 dbus[Running: apt block cgroups dbus]Starting 18/64 devicemapper[Running: apt block cgroups devicemapper]Starting 19/64 devices [Running: apt block cgroups devices] Starting 20/64 dpkg[Running: apt block cgroups dpkg]Starting 21/64 filesys [Running: apt block cgroups filesys] Starting 22/64 hardware[Running: apt cgroups filesys hardware] Starting 23/64 host[Running: apt cgroups hardware host] Starting 24/64 i18n[Running: apt cgroups host i18n] Starting 25/64 java[Running: apt cgroups host java] Starting 26/64 kernel [Running: apt cgroups host kernel] Starting 27/64 kvm [Running: apt cgroups kernel kvm]Starting 28/64 last[Running: apt cgroups kernel last] Starting 29/64 libraries [Running: apt cgroups kernel libraries] Starting 30/64 libvirt [Running: apt cgroups kernel libvirt]Starting 31/64 logrotate [Running: apt cgroups kernel logrotate] Starting 32/64 logs[Running: apt cgroups kernel logs] Starting 33/64 lvm2[Running: cgroups kernel logs lvm2] Starting 34/64 md [Running: cgroups kernel lvm2 md]Starting 35/64 memory [Running: cgroups kernel lvm2 memory]Starting 36/64 multipath [Running: cgroups kernel memory multipath] Starting 37/64 mysql [Running: cgroups kernel multipath mysql]Starting 38/64 networking [Running: cgroups kernel mysql networking] Starting 39/64 networkmanager [Running: cgroups kernel networking networkmana Starting 40/64 openssl [Running: cgroups networking networkmanager ope Starting 41/64 pam [Running: cgroups networking networkmanager pam Starting 42/64 pci [Running: cgroups networking pam pci]Starting 43/64 perl[Running: cgroups networking pci perl] Starting 44/64 ppp [Running: cgroups networking perl ppp] Starting 45/64 procenv [Running: cgroups networking ppp procenv]Starting 46/64 process [Running: cgroups networking procenv process]Starting 47/64 processor [Running: cgroups networking process processor] Starting 48/64 python [Running: cgroups process processor python] Starting 49/64 release
[Bug 1686437] Re: [SRU] glance sync: need keystone v3 auth support
I forgot to include my test cloud info: Openstack Queens running on Xenial | 458939d4dc404a47a8a496b7d513a5ab | RegionOne | keystone | identity | True| internal | http://10.5.0.18:5000/v3 | | 930b5cf107724f87845a645fc625fc07 | RegionOne | keystone | identity | True| admin | http://10.5.0.18:35357/v3 | | b7fec4dbcddf42e8867d2750f95378fc | RegionOne | keystone | identity | True| public| http://10.5.0.18:5000/v3 | juju status output is attached ** Attachment added: "juju status output" https://bugs.launchpad.net/simplestreams/+bug/1686437/+attachment/5211513/+files/juju-status.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686437 Title: [SRU] glance sync: need keystone v3 auth support To manage notifications about this bug go to: https://bugs.launchpad.net/simplestreams/+bug/1686437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686437] Re: [SRU] glance sync: need keystone v3 auth support
Hi, I've had a chance to test the fix for this. I was able to confirm that the 1.2 version of the package had an issue with the v3 keystone API. I then installed the 1.4 version of the package and it was able to successfully sync the images. glance-simplestreams-sync log file included ** Attachment added: "simplestreams log file for both 1.2 and 1.4 versions" https://bugs.launchpad.net/simplestreams/+bug/1686437/+attachment/5211508/+files/glance-simplestreams-sync.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686437 Title: [SRU] glance sync: need keystone v3 auth support To manage notifications about this bug go to: https://bugs.launchpad.net/simplestreams/+bug/1686437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775195] Re: [sync][sru]sosreport v3.6
Testing results: LXD containers: Xenial: ran and created an output file that looked fine. It outputted a single seemingly harmless error during run: [plugin:kvm] debugfs not mounted and mount attempt failed Bionic: ran with no errors, output file appeared fine Cosmic: ran with no errors, output file appeared fine Bare metal Bionic: ran with no errors, output file appeared fine KVM VM Xenial with MAAS: ran with no errors, output file appeared fine KVM VM Xenial with snap juju: ran with no errors, juju plugin did not run. Reported in https://github.com/sosreport/sos/issues/1475 and fixed in https://github.com/sosreport/sos/pull/1476 KVM VM Xenial with package juju: ran with no errors. Since it ran with sudo, it collected the juju status data, but it changed the controllers.yaml file to root-owned. This is a known juju problem and documented at: https://bugs.launchpad.net/juju/+bug/1747357 KVM VM with Xenial running live-patch: ran with no errors, output file appeared fine There are no outstanding issues that I have found that should hold this up. ** Bug watch added: github.com/sosreport/sos/issues #1475 https://github.com/sosreport/sos/issues/1475 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775195 Title: [sync][sru]sosreport v3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1775195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734983] Re: Request to backport sosreport v3.5
Ran 3.5 version for Trusty, Xenial, and Artful on a VM that was MAAS- deployed. I have not been able to discover any issues. I also installed it on a bare-metal server running Xenial with no problems 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/1734983 Title: Request to backport sosreport v3.5 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1734983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719671] Re: [SRU] include recent version containing fips and livepatch
Trusty:
NOTE: This is a pass for the ubuntu-advantage-tools script. The
duplicate machine-id issue I had was traced back to the canonical-
livepatch snap.
root@test4:~# dpkg -l ubuntu-advantage-tools
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=-=-=-===
ii ubuntu-advantage-tools 10ubuntu0.14.04.2 all management tools for Ubuntu
Advantage
root@test4:~# ubuntu-advantage enable-livepatch
Installing missing dependency snapd... OK
Installing the canonical-livepatch snap.
This may take a few minutes depending on your bandwidth.
canonical-livepatch 7.24 from 'canonical' installed
Your currently running kernel (3.13.0-135-generic) is too old to
support snaps. Version 4.4.0 or higher is needed.
Please reboot your system into a supported kernel version
and run the following command one more time to complete the
installation:
sudo ubuntu-advantage enable-livepatch
root@test4:~# ubuntu-advantage enable-fips chris-8k:
Sorry, but Canonical FIPS 140-2 Modules is not supported on trusty
root@test4:~# ubuntu-advantage enable-livepatch
Enabling Livepatch with the given token, stand by...
2017/11/07 19:16:15 Error executing enable?auth-token=
This machine ID is already enabled with a different key or is non-unique.
Either "sudo canonical-livepatch disable" on the other machine, or regenerate a
unique /etc/machine-id on this machine with "sudo rm /etc/machine-id
/var/lib/dbus/machine-id && sudo systemd-machine-id-setup" : {"error":
"Conflicting machine-id"}
root@test4:~# ubuntu-advantage status
livepatch: disabled
esm: disabled (not available)
fips: disabled (not available)
root@test4:~# sudo rm /etc/machine-id /var/lib/dbus/machine-id && sudo
systemd-machine-id-setup
Initializing machine ID from KVM UUID.
root@test4:~# ubuntu-advantage enable-livepatch
Enabling Livepatch with the given token, stand by...
Successfully enabled device. Using machine-token:
0192b423f4374c21a1892ebb74593743
Use "canonical-livepatch status" to verify current patch status.
root@test4:~# ubuntu-advantage status
livepatch: enabled
client-version: "7.23"
architecture: x86_64
cpu-model: Intel Core Processor (Haswell, no TSX)
last-check: 2017-11-07T19:17:36.506320725Z
boot-time: 2017-11-07T19:15:15Z
uptime: 2m58s
status:
- kernel: 4.4.0-100.123~14.04.1-generic
running: true
livepatch:
checkState: checked
patchState: nothing-to-apply
version: ""
fixes: ""
esm: disabled (not available)
fips: disabled (not available)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719671
Title:
[SRU] include recent version containing fips and livepatch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1719671/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719671] Re: [SRU] include recent version containing fips and livepatch
Trusty:
NOTE: This is a pass for the ubuntu-advantage-tools script. The
duplicate machine-id issue I had was traced back to the canonical-
livepatch snap.
root@test4:~# dpkg -l ubuntu-advantage-tools
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=-=-=-===
ii ubuntu-advantage-tools 10ubuntu0.14.04.2 all management tools for Ubuntu
Advantage
root@test4:~# ubuntu-advantage enable-livepatch
Installing missing dependency snapd... OK
Installing the canonical-livepatch snap.
This may take a few minutes depending on your bandwidth.
canonical-livepatch 7.24 from 'canonical' installed
Your currently running kernel (3.13.0-135-generic) is too old to
support snaps. Version 4.4.0 or higher is needed.
Please reboot your system into a supported kernel version
and run the following command one more time to complete the
installation:
sudo ubuntu-advantage enable-livepatch
root@test4:~# ubuntu-advantage enable-fips chris-8k:
Sorry, but Canonical FIPS 140-2 Modules is not supported on trusty
root@test4:~# ubuntu-advantage enable-livepatch
Enabling Livepatch with the given token, stand by...
2017/11/07 19:16:15 Error executing enable?auth-token=
This machine ID is already enabled with a different key or is non-unique.
Either "sudo canonical-livepatch disable" on the other machine, or regenerate a
unique /etc/machine-id on this machine with "sudo rm /etc/machine-id
/var/lib/dbus/machine-id && sudo systemd-machine-id-setup" : {"error":
"Conflicting machine-id"}
root@test4:~# ubuntu-advantage status
livepatch: disabled
esm: disabled (not available)
fips: disabled (not available)
root@test4:~# sudo rm /etc/machine-id /var/lib/dbus/machine-id && sudo
systemd-machine-id-setup
Initializing machine ID from KVM UUID.
root@test4:~# ubuntu-advantage enable-livepatch
Enabling Livepatch with the given token, stand by...
Successfully enabled device. Using machine-token:
Use "canonical-livepatch status" to verify current patch status.
root@test4:~# ubuntu-advantage status
livepatch: enabled
client-version: "7.23"
architecture: x86_64
cpu-model: Intel Core Processor (Haswell, no TSX)
last-check: 2017-11-07T19:17:36.506320725Z
boot-time: 2017-11-07T19:15:15Z
uptime: 2m58s
status:
- kernel: 4.4.0-100.123~14.04.1-generic
running: true
livepatch:
checkState: checked
patchState: nothing-to-apply
version: ""
fixes: ""
esm: disabled (not available)
fips: disabled (not available)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719671
Title:
[SRU] include recent version containing fips and livepatch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1719671/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719671] Re: [SRU] include recent version containing fips and livepatch
Trusty:
NOTE: I tested it on a machine without the HWE kernel necessary and the
tool installed the kernel, but livepatch wasn't enabled after the reboot
into the new kernel. I had to remove the machine-id in order to get
live-patch working.
Once I did that, it worked as expected.
root@test4:~# dpkg -l ubuntu-advantage-tools
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture
Description
+++-=-=-=-===
ii ubuntu-advantage-tools10ubuntu0.14.04.2 all
management tools for Ubuntu Advantage
root@test4:~# ubuntu-advantage enable-livepatch
Installing missing dependency snapd... OK
Installing the canonical-livepatch snap.
This may take a few minutes depending on your bandwidth.
canonical-livepatch 7.24 from 'canonical' installed
Your currently running kernel (3.13.0-135-generic) is too old to
support snaps. Version 4.4.0 or higher is needed.
Please reboot your system into a supported kernel version
and run the following command one more time to complete the
installation:
sudo ubuntu-advantage enable-livepatch
root@test4:~# ubuntu-advantage enable-fips chris-8k:B0hFSljTCnzKZGbH7fjq
Sorry, but Canonical FIPS 140-2 Modules is not supported on trusty
root@test4:~# ubuntu-advantage enable-livepatch
Enabling Livepatch with the given token, stand by...
2017/11/07 19:16:15 Error executing
enable?auth-token=48a07d71a2e445479083665874b769ae.
This machine ID is already enabled with a different key or is non-unique.
Either "sudo canonical-livepatch disable" on the other machine, or regenerate a
unique /etc/machine-id on this machine with "sudo rm /etc/machine-id
/var/lib/dbus/machine-id && sudo systemd-machine-id-setup" : {"error":
"Conflicting machine-id"}
root@test4:~# ubuntu-advantage status
livepatch: disabled
esm: disabled (not available)
fips: disabled (not available)
root@test4:~# sudo rm /etc/machine-id /var/lib/dbus/machine-id && sudo
systemd-machine-id-setup
Initializing machine ID from KVM UUID.
root@test4:~# ubuntu-advantage enable-livepatch
Enabling Livepatch with the given token, stand by...
Successfully enabled device. Using machine-token:
0192b423f4374c21a1892ebb74593743
Use "canonical-livepatch status" to verify current patch status.
root@test4:~# ubuntu-advantage status
livepatch: enabled
client-version: "7.23"
architecture: x86_64
cpu-model: Intel Core Processor (Haswell, no TSX)
last-check: 2017-11-07T19:17:36.506320725Z
boot-time: 2017-11-07T19:15:15Z
uptime: 2m58s
status:
- kernel: 4.4.0-100.123~14.04.1-generic
running: true
livepatch:
checkState: checked
patchState: nothing-to-apply
version: ""
fixes: ""
esm: disabled (not available)
fips: disabled (not available)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719671
Title:
[SRU] include recent version containing fips and livepatch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1719671/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719671] Re: [SRU] include recent version containing fips and livepatch
Artful verification: root@test1:~# dpkg -l ubuntu-advantage-tools Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-===-===- ii ubuntu-advantage-tools10ubuntu0.17.10.1 all management tools for Ubuntu Advantage root@test1:~# ubuntu-advantage enable-livepatch Sorry, but Canonical Livepatch is not supported on artful root@test1:~# ubuntu-advantage enable-fips chris-8k: Sorry, but Canonical FIPS 140-2 Modules is not supported on artful root@test1:~# ubuntu-advantage status livepatch: disabled (not available) esm: disabled (not available) fips: disabled (not available) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719671 Title: [SRU] include recent version containing fips and livepatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1719671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719671] Re: [SRU] include recent version containing fips and livepatch
Zesty verification: root@test2:~# dpkg -l ubuntu-advantage-tools Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--=-=-= ii ubuntu-advantage-tools 10ubuntu0.17.04.1 all management tools for Ubuntu Advantage root@test2:~# ubuntu-advantage enable-livepatch Sorry, but Canonical Livepatch is not supported on zesty root@test2:~# ubuntu-advantage enable-fips chris-8k: Sorry, but Canonical FIPS 140-2 Modules is not supported on zesty root@test2:~# ubuntu-advantage status livepatch: disabled (not available) esm: disabled (not available) fips: disabled (not available) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719671 Title: [SRU] include recent version containing fips and livepatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1719671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719671] Re: [SRU] include recent version containing fips and livepatch
Xenial Verification: root@test3:/home/ubuntu# dpkg -l ubuntu-advantage-tools Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==-==-=== ii ubuntu-advantage-to 10ubuntu0.16.0 allmanagement tools for Ubuntu Advantage root@test3:/home/ubuntu# ubuntu-advantage enable-livepatch Installing the canonical-livepatch snap. This may take a few minutes depending on your bandwidth. 2017-11-07T16:35:23Z INFO Waiting for restart... canonical-livepatch 7.24 from 'canonical' installed Enabling Livepatch with the given token, stand by... Successfully enabled device. Using machine-token: Use "canonical-livepatch status" to verify current patch status. root@test3:/home/ubuntu# ubuntu-advantage enable-fips chris-8k: Running apt-get update... OK Ubuntu FIPS PPA repository enabled. Installing FIPS packages (this may take a while)... OK Configuring FIPS... Updating grub to enable fips... OK Successfully configured FIPS. PLEASE REBOOT to complete FIPS enablement. ubuntu@test3:~$ uname -r 4.4.0-1002-fips ubuntu@test3:~$ ubuntu-advantage status livepatch: enabled client-version: "7.23" architecture: x86_64 cpu-model: Intel Core Processor (Haswell, no TSX) last-check: 2017-11-07T16:51:03.482519271Z boot-time: 2017-11-07T16:45:05Z uptime: 6m36s status: - kernel: 4.4.0-1002.2-fips running: true livepatch: checkState: checked patchState: nothing-to-apply version: "" fixes: "" esm: disabled (not available) fips: enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719671 Title: [SRU] include recent version containing fips and livepatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1719671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720887] Re: Default settings for virtlogd results in "too many open files" errors
Christian, The customer that I was working with has changed their environment, so I cannot go back to them. I will have to deploy openstack in our test lab to verify the default settings. It will take some time for me to get this checked out. I will reply back when I get it running. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720887 Title: Default settings for virtlogd results in "too many open files" errors To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1720887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720887] Re: Default settings for virtlogd results in "too many open files" errors
This is the data that led me to believe the default setting was low. I gathered this from a customer: ubuntu@x:~$ virsh list | wc -l 212 ubuntu@x:~$ sudo lsof -p $(pgrep virtlogd) | wc -l 893 ubuntu@x:~$ sudo grep "open files" /proc/$(pgrep virtlogd)/limits Max open files 1024 4096 files This is with 212 VMs and when the lsof output gets over 1024, it throws errors. Thanks, Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720887 Title: Default settings for virtlogd results in "too many open files" errors To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1720887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687126] [NEW] sosreport does not collect /sys/fs/pstore contents
Public bug reported: Release: Ubuntu 14.04.5 LTS Package, version, and arch: sosreport 3.1-1ubuntu2.2 amd64 Expected: Have sosreport collect /sys/fs/pstore data. What happened instead: sosreport did not collect /sys/fs/pstore Justificaton: The pstore data should be collected upon sosreport run for all architecture (currently only enabled in powerpc.py) because the data there will include any past oops event and/or panic events. This data would assist diagnosing panics with little other data available. Also, the data included is a few kb in size, so it will not add much size to the output of the report. ** Affects: sosreport (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/1687126 Title: sosreport does not collect /sys/fs/pstore contents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1687126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
