[Bug 2072647] Re: [SRU] virtlogd not rotating logs properly
** Patch added: "lp2072647-libvirt.debdiff" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2072647/+attachment/5795865/+files/lp2072647-libvirt.debdiff ** Description changed: [Impact] - When one enables max_age_days on /etc/libvirt/virtlogd.conf, for + When one enables max_age_days on /etc/libvirt/virtlogd.conf, for example by setting it to max_age_days = 1, the log files are not rotated correctly and we see this error on virtlogd: - [Test Case] 1) Launch a couple of dummy VMs to ensure that there are some logs in /var/log/libvirt 2) Edit /etc/libvirt/virtlogd.conf and ensure that the max_age_days setting is uncommented as per the following: -max_age_days = 1 - 3) Wait 24 hours. (There is no way to accelerate the timer unless one edits the source code) - 4) Verify that logs are cleaned up and there are no errors in syslog or virtlogd journal like the following: -Feb 28 08:58:57 dixie virtlogd[7205]: internal error: Failed to parse rotated index from '' + max_age_days = 1 + 3) sudo systemctl restart virtlogd + 4) Wait 24 hours. (There is no way to accelerate the timer unless one edits the source code) + 5) Verify that logs are cleaned up and there are no errors in syslog or virtlogd journal like the following: + Feb 28 08:58:57 dixie virtlogd[7205]: internal error: Failed to parse rotated index from '' [Where problems could occur] - + There could be some issues with virtlogd, but the code path only executes when max_age_days is different than 0. - In the event of a regression, one could disable the setting by commenting max_age_days. + In the event of a regression, one could disable the setting by commenting max_age_days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072647 Title: [SRU] virtlogd not rotating logs properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2072647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072647] Re: [SRU] virtlogd not rotating logs properly
** Summary changed: - virtlogd not rotating logs properly + [SRU] virtlogd not rotating logs properly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072647 Title: [SRU] virtlogd not rotating logs properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2072647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072647] Re: virtlogd not rotating logs properly
** Description changed: - When one enables max_age_days on /etc/libvirt/virtlogd.conf, for example - by setting it to max_age_days = 1, the log files are not rotated + [Impact] + + When one enables max_age_days on /etc/libvirt/virtlogd.conf, for + example by setting it to max_age_days = 1, the log files are not rotated correctly and we see this error on virtlogd: - Feb 28 08:58:57 dixie virtlogd[7205]: internal error: Failed to parse - rotated index from '' + + [Test Case] - There is a patch upstream [1] with the fix, and this is the placeholder - LP to backport that change into Ubuntu while I work on the backport - effort. + 1) Launch a couple of dummy VMs to ensure that there are some logs in /var/log/libvirt + 2) Edit /etc/libvirt/virtlogd.conf and ensure that the max_age_days setting is uncommented as per the following: +max_age_days = 1 + 3) Wait 24 hours. (There is no way to accelerate the timer unless one edits the source code) + 4) Verify that logs are cleaned up and there are no errors in syslog or virtlogd journal like the following: +Feb 28 08:58:57 dixie virtlogd[7205]: internal error: Failed to parse rotated index from '' - - [1] https://lists.libvirt.org/archives/list/de...@lists.libvirt.org/thread/ZWZ7GFFLZTCMWDUUB3X4FFK4YT5LW4OA/ + [Where problems could occur] + + There could be some issues with virtlogd, but the code path only executes when max_age_days is different than 0. + In the event of a regression, one could disable the setting by commenting max_age_days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072647 Title: virtlogd not rotating logs properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2072647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072647] [NEW] virtlogd not rotating logs properly
Public bug reported: When one enables max_age_days on /etc/libvirt/virtlogd.conf, for example by setting it to max_age_days = 1, the log files are not rotated correctly and we see this error on virtlogd: Feb 28 08:58:57 dixie virtlogd[7205]: internal error: Failed to parse rotated index from '' There is a patch upstream [1] with the fix, and this is the placeholder LP to backport that change into Ubuntu while I work on the backport effort. [1] https://lists.libvirt.org/archives/list/de...@lists.libvirt.org/thread/ZWZ7GFFLZTCMWDUUB3X4FFK4YT5LW4OA/ ** Affects: libvirt (Ubuntu) Importance: Undecided Assignee: David Negreira (dnegreira) Status: New ** Affects: libvirt (Ubuntu Noble) Importance: Undecided Assignee: David Negreira (dnegreira) Status: New ** Also affects: libvirt (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu Noble) Assignee: (unassigned) => David Negreira (dnegreira) ** Changed in: libvirt (Ubuntu) Assignee: (unassigned) => David Negreira (dnegreira) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072647 Title: virtlogd not rotating logs properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2072647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068577] Re: [UBUNTU 24.04] Running sosreport causes the system to crash and produce a dump
We would also like to look at the latest sosreport command that was run before crashing, can you share the latest /tmp/sos. so that we can inspect what is there? Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068577 Title: [UBUNTU 24.04] Running sosreport causes the system to crash and produce a dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2068577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068577] Re: [UBUNTU 24.04] Running sosreport causes the system to crash and produce a dump
Hi, Thank you for the report! Do you mind testing and verify if you run into the same issue with the latest Ubuntu kernel? It should be 6.8.0-35.35 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068577 Title: [UBUNTU 24.04] Running sosreport causes the system to crash and produce a dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2068577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890858] Re: AppArmor profile causes QEMU/KVM - Not Connected
** Also affects: cloud-archive/yoga 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/1890858 Title: AppArmor profile causes QEMU/KVM - Not Connected To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1890858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890858] Re: AppArmor profile causes QEMU/KVM - Not Connected
Backport to focal-yoga adapted with the patch from Christian ** Attachment added: "libvirt_8.0.0-1ubuntu7.7~cloud1_source.changes" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/+attachment/5763330/+files/libvirt_8.0.0-1ubuntu7.7~cloud1_source.changes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890858 Title: AppArmor profile causes QEMU/KVM - Not Connected To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1890858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Description changed: - [IMPACT] + [ Impact ] - The sos team is pleased to announce the release of sos-4.7.0 This - release focused on expanding support in policies for more and multiple - package managers. + * A new sosreport version is available upstream, and following the + https://wiki.ubuntu.com/SosreportUpdates policy for stable release + exception we will now SRU the sosreport 4.7.0 upstream release. - [TEST PLAN] + * This release introduces a couple of new plugins as well as bugfixes + done between the previous Ubuntu 4.5.6 sosreport version and the new + 4.7.0. - Documentation for Special Cases: - https://wiki.ubuntu.com/SosreportUpdates - [WHERE PROBLEMS COULD OCCUR] + [ Test Plan ] - The changes in sosreport are described below. There are a number of - changes related to report, plugins and policy. The changes in sosreport - content may break existing tooling, so that will need extensive testing. + * The detailed test plan can be found on + https://wiki.ubuntu.com/SosreportUpdates and should be tested by a + couple of users. - ## Global Changes - + Added support for `S3` uploads. + [ Where problems could occur ] - ## Policy Changes - + Fixed `dist_version()` for Ubuntu. + * Some plugins might stop working, and this will show when running + sosreport. - ## Report Changes - + Added a new preset for `app_eda` (Ansible Automation Platform Event Drive Ansible). + * Uploading to S3 needs the python3-boto3 dependency installed. - ### Plugin Changes - + New plugins: `aide`, `app_eda`, `coredump`', `infinidat`, `vectordev`. - + The `networking` plugin now uses a predicate for `ss` commands on Ubuntu. - + Enabled the `kubernetes` plugin for Debian. - + Dropped the `atomic` plugin. - + Fixed an issue with the command predicate for the `lxd` plugin when enabled via a snap. - + The `nvme` plugin now collects additional files per nvme drive on the host. + * If there is an issue with a plugin that is causing instability to the + system, this can be disabled by running 'sosreport -n '. - ## Collect Changes - + Added a transport for `Saltstack`. + * Currently running sos collect with Juju 3 is -not- working, even for + the current 4.5.6 Ubuntu version, we are working upstream on a fix + here: https://github.com/sosreport/sos/pull/3422 this is not part of the + core functionality of sos, and one can still run sos report manually on + the nodes. - ## Cleaner Changes - + `clean` will no longer try to obfuscate words that are 3 characters or less in length. - + `clean` will now properly obfuscate the upload password (if provided) in our own logs. + [ Other Info ] + + * Useful plugins that are now part of 4.7.0 and could do some testing: - For full information on the changes contained in this release, please - refer to the Git commit logs. Further release information and tarballs - are available at: - - https://github.com/sosreport/sos/releases/tag/4.7.0 - - Please report any problems to the sos-devel mailing list, or the GitHub - issue tracker: - - https://github.com/sosreport/sos/issues/ - - The team would like to thank everyone who contributed fixes, new - features, testing, and feedback for this release. + * runtime/lxd We have added an LXD runtime so that we can gather data directly from LXD, same with what one would do with k8s. + * plugins/canonical_livepatch_onprem.py will gather data from livepatch-server + * plugins/ceph.py add Reef release commands and gather microceph data + * plugins/coredump.py will capture coredump info from coredumpctl + * plugins/infinidat.py will gather data from servers that make use if the Infinidat storage solution + * plugins/kubernetes.py will now gather container information from microk8s + * plugins/mellanox_firmware.py will gather data from mellanox devices + * plugins/openstack_masakari.py will gather data from openstack masakari + * plugins/openstack_masakarimonitors.py will gather data from openstack masakari monitors + * plugins/vectordev.py will gather the config from vectordev (cos-proxy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
** Description changed: [IMPACT] The sos team is pleased to announce the release of sos-4.7.0 This release focused on expanding support in policies for more and multiple package managers. [TEST PLAN] Documentation for Special Cases: https://wiki.ubuntu.com/SosreportUpdates [WHERE PROBLEMS COULD OCCUR] The changes in sosreport are described below. There are a number of changes related to report, plugins and policy. The changes in sosreport content may break existing tooling, so that will need extensive testing. ## Global Changes + Added support for `S3` uploads. ## Policy Changes + Fixed `dist_version()` for Ubuntu. - + Dropped the `RedHatAtomic` policy. - + Changed the authentication for RHEL uploads to use device auth instead of username/password. ## Report Changes + Added a new preset for `app_eda` (Ansible Automation Platform Event Drive Ansible). ### Plugin Changes + New plugins: `aide`, `app_eda`, `coredump`', `infinidat`, `vectordev`. + The `networking` plugin now uses a predicate for `ss` commands on Ubuntu. + Enabled the `kubernetes` plugin for Debian. + Dropped the `atomic` plugin. + Fixed an issue with the command predicate for the `lxd` plugin when enabled via a snap. + The `nvme` plugin now collects additional files per nvme drive on the host. ## Collect Changes + Added a transport for `Saltstack`. ## Cleaner Changes + `clean` will no longer try to obfuscate words that are 3 characters or less in length. + `clean` will now properly obfuscate the upload password (if provided) in our own logs. For full information on the changes contained in this release, please refer to the Git commit logs. Further release information and tarballs are available at: https://github.com/sosreport/sos/releases/tag/4.7.0 Please report any problems to the sos-devel mailing list, or the GitHub issue tracker: https://github.com/sosreport/sos/issues/ The team would like to thank everyone who contributed fixes, new features, testing, and feedback for this release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917894] Re: [FFe][sync][sru] sos upstream 4.1
My tests were mainly focused on Openstack hence I have run the tests on Bionic and Focal only, I have tested the following application within an OpenStack environment: * ceph-mon * ceph-osd * ceph-radosgw * cinder * cinder-ceph * glance * keystone * mysql * neutron-api * neutron-gateway * neutron-openvswitch * nova-cloud-controller * nova-compute * octavia * openstack-dashboard * placement * rabbitmq-server I have run the following command on each of the applications: sos report -a --all-logs They all returned the expected application data as well as the logs, no errors found. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917894 Title: [FFe][sync][sru] sos upstream 4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1917894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907676] Re: segmentation fault when opening fd
I have run tests on Xenial, Bionic and Focal, exactly the same as on comment #2, this time with the packages from the ubuntu-security- proposed PPA show on comment #9 and I can confirm that this fixes the issues 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/1907676 Title: segmentation fault when opening fd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1907676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907676] Re: segmentation fault when opening fd
Hello, I have tested with the test package 1.6.5ubuntu0.4+testpkg20201220b1 provided by ~slashd on his ppa[1] on bionic with all updates applied and this fixes the segmentation fault issue. Steps to test: 1) On the LDS server, create a package profile that installs a single package, 'hello' is enough. 2) On the LDS server, apply the package profile to a client 3) On the LDS client, verify that there is no segfault message on '/var/log/kern.log' 4) On the LDS server, verify that the activity to apply the package profile ends with success. Before ~slashd fix, step 3) would show a segfault and step 4), the activity would stay 'In Progress' forever. [1] https://launchpad.net/~slashd/+archive/ubuntu/sruverif -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907676 Title: segmentation fault when opening fd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1907676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884293] Re: Update to maintenance release v3.9.1
Finalized testing Focal: Test cases: * Verified 0 sized files * Verified errors on sos.log * Verified automatic uploads * Openstack Run on sosreport on an juju deployed openstack cluster and verified that the relevant information for each unit was present, both on sos_commands/ and /var/log as well as the juju information: ** ceph ** openvswitch ** rabbitmq ** cinder ** glance ** keystone ** neutron-api ** neutron-gateway ** nova-cloud-controller ** nova-compute * juju ** verified that the sensitive information is masked on a controller -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884293 Title: Update to maintenance release v3.9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1884293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884293] Re: Update to maintenance release v3.9.1
@slashd finished testing from my side on Bionic, Focal and Eoan, see my previous updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884293 Title: Update to maintenance release v3.9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1884293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884293] Re: Update to maintenance release v3.9.1
Finalized testing Eoan: Test cases: * Verified 0 sized files * Verified errors on sos.log * Verified automatic uploads * Openstack Run on sosreport on an juju deployed openstack cluster and verified that the relevant information for each unit was present, both on sos_commands/ and /var/log as well as the juju information: ** ceph ** openvswitch ** rabbitmq ** cinder ** glance ** keystone ** neutron-api ** neutron-gateway ** nova-cloud-controller ** nova-compute * juju ** verified that the sensitive information is masked on a controller -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884293 Title: Update to maintenance release v3.9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1884293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884293] Re: Update to maintenance release v3.9.1
Finalized testing Bionic: Test cases: * Verified 0 sized files * Verified errors on sos.log * Verified automatic uploads * Openstack Run on sosreport on an juju deployed openstack cluster and verified that the relevant information for each unit was present, both on sos_commands/ and /var/log as well as the juju information: ** ceph ** openvswitch ** rabbitmq ** cinder ** glance ** keystone ** neutron-api ** neutron-gateway ** nova-cloud-controller ** nova-compute * juju ** verified that the sensitive information is masked on a controller -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884293 Title: Update to maintenance release v3.9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1884293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873803] Re: Unable to create VMs with virt-install
Can confirm that the workaround works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873803 Title: Unable to create VMs with virt-install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1873803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873803] [NEW] Unable to create VMs with virt-install
Public bug reported: When launching a VM with virt-inst on focal it is now failing with the error on the debug output here: https://paste.ubuntu.com/p/jvw3pS6249/ ubuntu@robson:~$ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 ubuntu@robson:~$ apt-cache policy virt-manager virt-manager: Installed: (none) Candidate: 1:2.2.1-3ubuntu2 Version table: 1:2.2.1-3ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages ubuntu@robson:~$ apt-cache policy virtinst virtinst: Installed: 1:2.2.1-3ubuntu2 Candidate: 1:2.2.1-3ubuntu2 Version table: *** 1:2.2.1-3ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: virt-manager (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Unable to create VMs with virt-inst + Unable to create VMs with virt-install -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873803 Title: Unable to create VMs with virt-install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1873803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
Can we backport the fixes to Bionic? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) To manage notifications about this bug go to: https://bugs.launchpad.net/charm-keepalived/+bug/1815101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826811] Re: Valgrind unhandled instruction 0xD5380000 on Aarch64
I tested on an ARM machine with the proposed package and it works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826811 Title: Valgrind unhandled instruction 0xD538 on Aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1826811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843044] Re: firefox crashes on a FIPS enabled machine
Tested the firefox build on Bionic with FIPS enabled and disabled and it is working as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843044 Title: firefox crashes on a FIPS enabled machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843044] Re: firefox crashes on a FIPS enabled machine
Tested the firefox build on Xenial with FIPS enabled and disabled, it works as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843044 Title: firefox crashes on a FIPS enabled machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837734] Re: Firefox crash on a FIPS enabled machine due to libnss3
Test failed on xenial 16.04: https://paste.ubuntu.com/p/qbmkGS5RSB/ Already shared latest info and straces with Vineetha. ** Tags removed: verification-needed-disco verification-needed-xenial ** Tags added: verification-failed-xenial ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837734 Title: Firefox crash on a FIPS enabled machine due to libnss3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1837734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820366] Re: network install of xenial 16.04 fails with linux-generic package error
** Attachment added: "/var/log/syslog from installer" https://bugs.launchpad.net/ubuntu/+bug/1820366/+attachment/5247293/+files/vmlog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820366 Title: network install of xenial 16.04 fails with linux-generic package error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1820366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820366] Re: network install of xenial 16.04 fails with linux-generic package error
I can replicate when doing virt-install using "http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer-amd64/; as --location. I can confirm that adding "d-i base-installer/kernel/image string linux-image-4.4.0-142-generic" to the preseed is a workaround for the time being. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820366 Title: network install of xenial 16.04 fails with linux-generic package error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1820366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815910] Re: Apparmor blocks access to /dev/vhost-net
I am chiming in on behalf of our customer that is affected by this bug and patched his AppArmor profile manually for the time being to solve his issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815910 Title: Apparmor blocks access to /dev/vhost-net To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1815910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815212] Re: [Xenial][Bionic][SRU] Update pci.ids to version 2018.07.21
[VERIFICATION BIONIC] Weird that the Xeon is appearing there, this is a very recent Thinkpad t480. dnegreira@freedom:~ $ diff -u lspci-before lspci-after --- lspci-before2019-02-11 16:55:09.444316078 +0100 +++ lspci-after 2019-02-11 16:57:57.505861734 +0100 @@ -1,15 +1,15 @@ 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) -00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 08) -00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model +00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08) +00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) -00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1) +00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.6 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #7 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1d.2 PCI bridge: Intel Corporation Device 9d1a (rev f1) -00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21) +00:1f.0 ISA bridge: Intel Corporation Intel(R) 100 Series Chipset Family LPC Controller/eSPI Controller - 9D4E (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) @@ -28,4 +28,4 @@ 08:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 09:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) 0b:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) -3d:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a808 +3d:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981 ### The CPU: dnegreira@freedom:~ $ cat /proc/cpuinfo 1 ↵ processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 142 model name : Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz stepping: 10 microcode : 0x9a cpu MHz : 794.544 cache size : 8192 KB physical id : 0 siblings: 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 22 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp flush_l1d bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf bogomips: 3984.00 clflush size: 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815212 Title: [Xenial][Bionic][SRU] Update pci.ids to version 2018.07.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pciutils/+bug/1815212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
