[Bug 1770290] Re: package openssh-server 1:7.6p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Broken pipe)
/etc/ssh/sshd_config: No such file or directory This file is essential to ssh, if you have deleted it the service won't work. That means you either have to remove the service or re-fix it's configuration. To restore that you can find a default in /usr/share/openssh/sshd_config -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770290 Title: package openssh-server 1:7.6p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Broken pipe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1770290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770417] Re: Qemu can not parse long fqdns during drive-mirror
As Daniel asked in [1] making this abug report against Qemu (upstream). [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1568939 ** Bug watch added: Red Hat Bugzilla #1568939 https://bugzilla.redhat.com/show_bug.cgi?id=1568939 ** Also affects: qemu 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/1770417 Title: Qemu can not parse long fqdns during drive-mirror To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1770417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770290] Re: package openssh-server 1:7.6p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Broken pipe)
Thank you for taking the time to report this bug and helping to make Ubuntu better. On upgrading a service this service has to be restarted to pick up the fixes. Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration. But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state. Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart. Therefore the update of that package has to consider itself incomplete. Depending on your particular case there are two solutions: - either remove the offending package if you don't want to continue using it. - Or if you do want to keep it please fix the configuration so that re-starting the service will work. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770290 Title: package openssh-server 1:7.6p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Broken pipe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1770290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770417] Re: Qemu can not parse long fqdns during drive-mirror
Ubuntu task is not actionable until we settled on how to change the parsing code for long strings upstream, so I set it to confirmed but wishlist (until we know what size a patch - or actions a recommendation on handling differently has). ** Changed in: qemu (Ubuntu) Status: New => Confirmed ** Changed in: qemu (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770417 Title: Qemu can not parse long fqdns during drive-mirror To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1770417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603902] Re: qemu-img convert hangs on Ubuntu Server 16.04 with 100% cpu
Thanks Matt, yeah we actually had no similar report in all the time. It is unclear to me if there still is something needed in the kernel, but it is unclear which (if any) qemu change needs to be done as there is no external reproducer. It is good to hear that in your case after working heavily it just resolved itself. ** Changed in: qemu-kvm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603902 Title: qemu-img convert hangs on Ubuntu Server 16.04 with 100% cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86
I re-deployed one of my systems to Xenial. For the complexity of going back I took what kernel is currently active which was 4.4.0-224 With that I spun up the Xubuntu 32 bit iso you referred. For the sake of completeness I also did the same on 4.15.0-20-generic (also with newer qemu of bionic). $ qemu-system-i386 -name xubuntu-18.04-desktop-i386 -m 2047M -cpu host -smp 1 -enable-kvm -machine type=ubuntu,accel=kvm -boot d -cdrom /tmp/xubuntu-18.04-desktop-i386.iso And while the initial loading from the ISO takes quite some time I was easily able to go from the installer into "try Xubuntu" and once the desktop loaded up it was actually quite responsive and just fine. This is true for both kernels/releases that I had tried. Now since we have this yet-unknown relation to the host kernel version, I wanted to ask if you could try the even newer 4.4.0-224 kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767857 Title: Kernel 4.4.0-122 Breaks qemu-system-x86 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758037] Re: LTC Test- Ubuntu18.04: Starting the guest with network filter defined will fail with "cause is unknown".
SRU test builds and tests from PPA worked, pushed for SRU review to X/A/B-unapproved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758037 Title: LTC Test- Ubuntu18.04: Starting the guest with network filter defined will fail with "cause is unknown". To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1758037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668244] Re: systemd-udevd[15087]: Process '/bin/sh -c 'echo 180 >/sys$DEVPATH/device/timeout'' failed with exit code 2.
*** This bug is a duplicate of bug 1741390 *** https://bugs.launchpad.net/bugs/1741390 Interesting - thanks for the check, in that case I'll mark this bug as a dup as your issue will then be solved by the backport we are working on. ** This bug has been marked a duplicate of bug 1741390 Please backport open-vm-tools 2:10.2.0-3 (main) from bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668244 Title: systemd-udevd[15087]: Process '/bin/sh -c 'echo 180 >/sys$DEVPATH/device/timeout'' failed with exit code 2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1668244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741390] Re: Please backport open-vm-tools 2:10.2.0-3 (main) from bionic
The Upload was also tested by the reporter against another bug that will be fixed by the backport. So I dup'ed 1668244 onto this bug here. +1 on the backport adressing more issues :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741390 Title: Please backport open-vm-tools 2:10.2.0-3 (main) from bionic To manage notifications about this bug go to: https://bugs.launchpad.net/xenial-backports/+bug/1741390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770345] Re: libvirt not compatible with netplan
*** This bug is a duplicate of bug 1764314 *** https://bugs.launchpad.net/bugs/1764314 Hi Daniel, thanks for your report. The issue that libvirt can't "see" all devices existed quite a while actually. Whatever you have through networkd or NetworkManager was invisible. This is due to netcf being the driver for the backend and this is - as you already realized - only compatible with ifupdown. bug 1764314 holds a discssion with more details on it so I'll mark yours here as a dup. ** This bug has been marked a duplicate of bug 1764314 libvirt doesn't show all interfaces -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770345 Title: libvirt not compatible with netplan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1770345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239109] Re: aarch64 clock_gettime with CLOCK_REALTIME_COARSE or CLOCK_MONOTONIC_COARSE fails with SIGBUS or SIGSEGV
This bug was fixed in the package libqb - 1.0.3-1 --- libqb (1.0.3-1) unstable; urgency=medium [ Christoph Berg ] * [3e6a1ea] Remove Richard and myself from Uploaders [ Ferenc Wágner ] * [2dbb472] Update old style gbp.conf section names * [c566381] New upstream release (1.0.3) (Closes: #871153, #877562) * [2fa9704] Remove upstreamed/obsoleted patches, refresh the Hurd support patch * [13e68c7] Update symbols file. Remove some internal symbols (see c011b12) and add a new one. * [dc0438b] New patch: hurd: definition of PATH_MAX must be included separately * [737a79d] Update Standards-Version to 4.1.3 (no changes required) * [1fc3d87] Switch to Debhelper compat level 11 * [930dba8] Combat test failures with a world-writeable socket directory. On Linux systems libqb uses abstract sockets by default, which lack access control. However, they aren't available on other platforms. The other option is using file system sockets, by default under /var/run. This directory is only writable by root, though, which makes it inapproriate for unprivileged applications. So use /tmp instead. See also: https://github.com/ClusterLabs/libqb/issues/294 * [b7d5dea] New patch: tests: always run the SHM suite, just expect failures * [419537a] New patch: hurd: the socket tests are expected to fail (Closes: #803777) * [ae9b078] Switch gbp dch to verbose changelog entries * [75fc9d2] Stop repeating the common description * [6e9aa99] Migrate to salsa.debian.org/ha-team * [2093569] Whitespace cleanup in debian/changelog * [5ad582f] Ship example code in the doc package * [c6d7de2] Use secure URI in the Homepage field * [0d73506] Modernize watch file, add signature checking * [343b790] qb-blackbox makes libqb-dev not co-installable * [fe6e555] Lintian does not emit embedded-javascript-library for Doxygen anymore * [42afbde] New patch: Fix spelling: plaform -> platform -- Ferenc Wágner Wed, 14 Mar 2018 12:42:20 +0100 ** Changed in: libqb (Ubuntu) Status: Triaged => Fix Released ** Bug watch added: github.com/ClusterLabs/libqb/issues #294 https://github.com/ClusterLabs/libqb/issues/294 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239109 Title: aarch64 clock_gettime with CLOCK_REALTIME_COARSE or CLOCK_MONOTONIC_COARSE fails with SIGBUS or SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libqb/+bug/1239109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758037] Re: LTC Test- Ubuntu18.04: Starting the guest with network filter defined will fail with "cause is unknown".
Regression- and Case-Tested once more from a ppa and being good. Also pushed to ubuntu libvirt-maintainers git as a new cosmic-4.0 branch Uploaded to Cosmic and completed, now considering SRUs. ** Also affects: libvirt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu Xenial) Status: New => Triaged ** Changed in: libvirt (Ubuntu Artful) Status: New => Triaged ** Changed in: libvirt (Ubuntu Bionic) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758037 Title: LTC Test- Ubuntu18.04: Starting the guest with network filter defined will fail with "cause is unknown". To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1758037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764314] Re: libvirt doesn't show all interfaces
There already was an upload ongoing, but I need to group bug 1758037 on the same run and need to set new branches. ... Integrated that now. Regression- and Case-Tested once more from a ppa and being good. Uploaded to Cosmic - and it already completed. Also pushed to ubuntu libvirt-maintainers git. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764314 Title: libvirt doesn't show all interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1764314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769888] Re: New upstream microreleases 9.3.23, 9.5.13, 9.6.9 and 10.4
Test builds in the referred PPAs are all good. Need some more tests as usual on the MRE for confidence, but other than that all looks good atm. ** Summary changed: - MRE Prep + New upstream microreleases 9.3.23, 9.5.13, 9.6.9 and 10.4 ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769888 Title: New upstream microreleases 9.3.23, 9.5.13, 9.6.9 and 10.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-10/+bug/1769888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1299520] Re: check_mk needs upate to more current version (1.2.4p2)
Xenial is at 1.2.6p12-1ubuntu0.16.04.1 and later release are even newer. This is still true for Trusty so I flagged it that way. ** Also affects: check-mk (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: check-mk (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299520 Title: check_mk needs upate to more current version (1.2.4p2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/check-mk/+bug/1299520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971511] Re: manpage path is incorrect
Hi Adrian (after a long time), I came by clearing or reconsidering old bugs. Checks are at /usr/share/check_mk/checks Docs for them are /usr/share/check_mk/checks-man Both are part of check-mk-server package. The default in the tool is in /usr/share/check_mk/modules/check_mk.py check_manpages_dir = '/usr/share/doc/check_mk/checks' Actually this is configurable via /usr/share/check_mk/modules/defaults but it sets the same path check_manpages_dir = '/usr/share/check_mk/checks-man' So while this bug seems to have been found no direct love/response is was fixed sometime in between then and now. ** Changed in: check-mk (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971511 Title: manpage path is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/check-mk/+bug/971511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741390] Re: Please backport open-vm-tools 2:10.2.0-3 (main) from bionic
1. Upgrade from proposed Binaries usually installed are open-vm-tools and open-vm-tools-desktop I see 10.2.0-3~... in Xenial and Artful, checking if the upgrade works without issues. On the upgrade one sees a list of new dependencies libdrm2, libudev, libxml2 libxmlsec1 libxmlsec1-openssl pciutils and iproute2 - fortunately all are in main - so no undetected component mismatch. Note: as host I used VMWare Workstation 14.1.1 and systems installed from 16.04.4 and 17.10.1 iso as of today. Artful: upgraded without issues Xenial: upgraded withous issues Note: the default console setup can't copy and paste, so no full log here :-/ 2. This bug in particular is about making the new version available. Check vmtoolsd -v for the version being on 10.2 Artful: ok 10.2.0.1608 Xenial: ok 10.2.0.1608 Per above (and the extensive precheck on the content-equal ppa by VMWare) - setting to verified ** Tags removed: verification-needed verification-needed-artful verification-needed-xenial ** Tags added: verification-done verification-done-artful verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741390 Title: Please backport open-vm-tools 2:10.2.0-3 (main) from bionic To manage notifications about this bug go to: https://bugs.launchpad.net/xenial-backports/+bug/1741390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750780] Re: Race with local file systems can make open-vm-tools fail to start
1. Upgrade from proposed - this is the same for all associated bugs, so I only documented details in bug 1741390 2. This bug in particular Running a few restarts and checking $ systemctl status -l open-vm-tools.service This checks if the service rules avoid the issue on these systems with older systemd (older than Bionic where these extra constraints are not needed) Artful: did not expose the issue in 5/5 retries Xenial: did not expose the issue in 5/5 retries Per above (and the extensive precheck on the content-equal ppa by VMWare) - setting to verified ** Tags removed: verification-needed verification-needed-artful verification-needed-xenial ** Tags added: verification-done verification-done-artful verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750780 Title: Race with local file systems can make open-vm-tools fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758428] Re: Subprocesses of StartProgramInGuest fail when creating temporary files
1. Upgrade from proposed - this is the same for all associated bugs, so
I only documented details in bug 1741390
2. This bug in particular
While triggering the raw error throu VMOMI API is complex one can check the
services mountpoints.
E.g. with that we see the issue present in Artful before this upgrade.
$ findmnt -N $(systemctl status open-vm-tools | awk '/Main PID/ {print $3}')
After the upgrade we have
Artful: no private TMP (anymore, the version before this was affected)
Xenial: no private TMP (the upgrade did not add this issue since it is fixed
before the backport)
Per above (and the extensive precheck on the content-equal ppa by
VMWare) - setting to verified
** Tags removed: verification-needed verification-needed-artful
verification-needed-xenial
** Tags added: verification-done verification-done-artful
verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758428
Title:
Subprocesses of StartProgramInGuest fail when creating temporary files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1758428/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758037] Re: LTC Test- Ubuntu18.04: Starting the guest with network filter defined will fail with "cause is unknown".
Started tests for a Cosmic upload and added SRU Template. ** Description changed: + [Impact] + + * nwfilters were not usable if configured to use dhcp based learning + + * Fix by backporting upstream bug + + [Test Case] + + * Add the following to the interface section of a guest description in +libvirt: + + + + Then start the guest. + + Bad case: + error: Failed to start domain VM1 + error: An error occurred, but the cause is unknown + + Fixed: + Guest starts and works. + + [Regression Potential] + + * I thought a while on this. On first sight one might say there is a +regression risk due to increasing the size of the buffer. This risk +would arise on hyperscale environments where the memory consumption per +guest would increase by 2*128Kb*#guest-interfaces (not much, but can +sum up on MANY guests). +But then I realized that this is only true for the use case using +dhcpsnoop which is +a) clearly not the most common case +b) failing to work at all before this fix +So there can't be anyone today with a working setup that then runs OOM, +due to the setup either not using the feature (=no change) or failing +missing this fix. +So I actually think this mem consumption increase is not an issue in +terms of SRU considerations. +Due to that the only remaining regression would be users that had a +self-built libpcap without TPACKET_V3 to drive a workload like the +above, and even then only the rather small size bump is what changes. + + [Other Info] + + * I have added this case and a few deeper checks on the created rules for +iptables to the regression tests + + --- + == Comment: #2 - Mallesh N. Koti - 2018-02-28 05:02:49 == - Guest Xml === ISSUE === Defining a network filter and Starting a VM with this nwfiter in VM's xml is failing with "cause is unknown". == Recreation Steps == 1. Define a network filter as: - virsh nwfilter-define filter.xml + virsh nwfilter-define filter.xml 2. Add nwfilter in guest xml and start guest. - virsh start VM1 + virsh start VM1 It fails with : # virsh start VM1 error: Failed to start domain VM1 error: An error occurred, but the cause is unknown XML used for defining network filter: ``` - -b071-6127-b4ec- - - - + -b071-6127-b4ec- + + + ``` will be attaching the guest xml The issue happens with Ubuntu 18.04 host - where not able to start the guest with network defined with value dhcp. . - Found following commit is not there in 18.04 Ubuntu source. There could be some dependent commit too. we are facing some build issue and hence not able to verify it. - . + Found following commit is not there in 18.04 Ubuntu source. There could be some dependent commit too. we are facing some build issue and hence not able to verify it. + . https://github.com/libvirt/libvirt/commit/e62cb4a9b78c7f4499a206635fb4f06e6ac627e5 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758037 Title: LTC Test- Ubuntu18.04: Starting the guest with network filter defined will fail with "cause is unknown". To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1758037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1404396] Re: [regression] vgabios -> seabios breaks (my) 16-bit applications
Thank you so much Richard! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404396 Title: [regression] vgabios -> seabios breaks (my) 16-bit applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1404396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752271] Re: New upstream microreleases 9.3.22, 9.5.12, 9.6.8 and 10.3
** Changed in: postgresql-10 (Ubuntu Bionic) Status: Triaged => Fix Released ** Changed in: postgresql-10 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752271 Title: New upstream microreleases 9.3.22, 9.5.12, 9.6.8 and 10.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-10/+bug/1752271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203875] Re: Re-enable loop.test and ipc.test
FYI - loop was enabled even longer and ipc was enabled in Feb 2017 1.0.1-1ubuntu1 Currently a sync is in progress which will enable the last test being log that now works as well, but for the scope of this bug description things are already fixed. ** Changed in: libqb (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203875 Title: Re-enable loop.test and ipc.test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libqb/+bug/1203875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1404396] Re: [regression] vgabios -> seabios breaks (my) 16-bit applications
I think we are fine doing that change >=Cosmic if we can confirm it is working now. We have no regression that would make us need a SRU, this is more a request to simplify maintenance and get in sync with upstreams defaults again if they are ok now. I really appreciate your help and your self-reliance on this - if you need me for anything let me know. Otherwise I'll just stay subscribed and wait for your results. Thanks in advance! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404396 Title: [regression] vgabios -> seabios breaks (my) 16-bit applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1404396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86
Hmm, so it is not even burning CPU for anything neither in the Host (usr ~=qemu, sys ~=kernel) nor in the guest itself (~=guest). The KVM exits confirm that, it doesn't do a a lot entry/exit is the pass in/out of guest context and the only meaningful exit means it emulates an instruction. So if it is not hogged on a CPU it is waiting for something. Unfortunately this is too windows and x86-arch specific for me to read, even if you get the info. BTW getting the info what instructions it is spinning on can be done via [1] - this might be helpful for others coming by to help. To bad that I still can't reproduce that locally :-/, but at least I haven't heard of anyone else hitting this yet so it must be sort of special to maybe your guest? Especially I can't see yet how a host kernel update would trigger this :-/ Sorry, but this is up for the kernel Team to consider the changes that happened between those versions in regard to this issue. [1]: https://lkml.org/lkml/2012/6/27/241 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767857 Title: Kernel 4.4.0-122 Breaks qemu-system-x86 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764314] Re: libvirt doesn't show all interfaces
Filed a bug in Debian for the netcf Dependency going forward, linked at the bug tasks. ** Bug watch added: Debian Bug tracker #898194 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898194 ** Also affects: libvirt (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898194 Importance: Unknown Status: Unknown ** No longer affects: libvirt (Debian) ** Also affects: netcf (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898194 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764314 Title: libvirt doesn't show all interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1764314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764314] Re: libvirt doesn't show all interfaces
We had a discussion on this: I have to beg your pardon for all of the Ubuntu community, but we never intended to support write-managing through libvirt in Bionic. Libvirt iface-* never supported networkd or NetworkManager. To manage networks with different backends there is netplan.io. Adding a dependency to ifupdown from netcf could hurt new installs of Bionic by pulling in ifupdown again - there are known issues and races around that that we want to avoid. Upgraders have ifupdown around from their past anyway and new users “insisting” on the old use case can still install ifupdown on their own. It is bad to not have the visibility of all devices in virsh iface-list and virt-manager and such, but since this is the case since at least Xenial and it never was an issue. Compared to the alternatives - we didn’t come up with a way to fix it yet which would not carry a regression risk (or even regression fact) that would be too high. On balance it is not reasonable to be fixed at the moment. If that importance goes up what might come to my mind is a config option in libvirt where users can switch to udev - but that feature isn’t implemented in libvirt at all - so it would be a major effort not matching the severity of this IMHO. Goin forward to Cosmic and beyond we will switch to the udev to fix the visibility For all of the of the above I’ll have to set Bionic to Won’t Fix unless there is a change of severity due to for example more important use- cases we haven’t seen. /me feels bad as Nicolas made a great and valid bug report, but for now this is the right choice ** Also affects: libvirt (Ubuntu Cosmic) Importance: Low Status: Confirmed ** Also affects: netcf (Ubuntu Cosmic) Importance: High Status: Triaged ** Also affects: libvirt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: netcf (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu Cosmic) Status: Confirmed => Triaged ** Changed in: libvirt (Ubuntu Bionic) Status: New => Won't Fix ** Changed in: netcf (Ubuntu Bionic) Status: New => Won't Fix ** Changed in: libvirt (Ubuntu Cosmic) Importance: Low => Medium ** Changed in: netcf (Ubuntu Cosmic) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764314 Title: libvirt doesn't show all interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1764314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769888] [NEW] MRE Prep
*** This bug is a security vulnerability *** Private security bug reported: Postgresql stable update Current versions in supported releases: postgresql-9.3 | 9.3.22-0ubuntu0.14.04 trusty postgresql-9.5 | 9.5.12-0ubuntu0.16.04 xenial postgresql-9.6 | 9.6.8-0ubuntu0.17.10 artful postgresql-10 | 10.3-1bionic postgresql-10 | 10.3-2cosmic Special cases: - Cosmic will be synced from Debian which usually releases fast. So no Cosmic upload by us. Last related stable updates: 9.3.23, 9.5.13, 9.6.9, 10.4 So the todo is to pick: MRE: Trusty 9.3.23 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-9.3.23.tar.gz MRE: Xenial 9.5.13 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-9.5.13.tar.gz MRE: Artful 9.6.9 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-9.6.9.tar.gz MRE: Bionic 10.4 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-10.4.tar.gz Sync: Cosmic 10.4 via Debian auto-sync Standing MRE - Consider last updates as template: - pad.lv/1637236 - pad.lv/1664478 - pad.lv/1690730 - pad.lv/1713979 - pad.lv/1730661 - pad.lv/1747676 - pad.lv/1752271 New - this bug - pad.lv/1769888 ** Affects: postgresql-10 (Ubuntu) Importance: Undecided Status: New ** Affects: postgresql-9.3 (Ubuntu) Importance: Undecided Status: New ** Affects: postgresql-9.5 (Ubuntu) Importance: Undecided Status: New ** Affects: postgresql-9.6 (Ubuntu) Importance: Undecided Status: New ** Affects: postgresql-9.3 (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: postgresql-9.5 (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: postgresql-9.6 (Ubuntu Artful) Importance: Undecided Status: New ** Affects: postgresql-10 (Ubuntu Bionic) Importance: Undecided Status: New ** Information type changed from Public to Private Security ** Description changed: - Prep new MRE + Postgresql stable update + + Current versions in supported releases: + postgresql-9.3 | 9.3.22-0ubuntu0.14.04 trusty + postgresql-9.5 | 9.5.12-0ubuntu0.16.04 xenial + postgresql-9.6 | 9.6.8-0ubuntu0.17.10 artful + postgresql-10 | 10.3-1bionic + postgresql-10 | 10.3-2cosmic + + Special cases: + - Cosmic will be synced from Debian which usually releases fast. + So no Cosmic upload by us. + + Last related stable updates: 9.3.23, 9.5.13, 9.6.9, 10.4 + + So the todo is to pick: + MRE: Trusty 9.3.23 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-9.3.23.tar.gz + MRE: Xenial 9.5.13 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-9.5.13.tar.gz + MRE: Artful 9.6.9 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-9.6.9.tar.gz + MRE: Bionic 10.4 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-10.4.tar.gz + Sync: Cosmic 10.4 via Debian auto-sync + + + Standing MRE - Consider last updates as template: + - pad.lv/1637236 + - pad.lv/1664478 + - pad.lv/1690730 + - pad.lv/1713979 + - pad.lv/1730661 + - pad.lv/1747676 + - pad.lv/1752271 + New - this bug + - pad.lv/1769888 ** Also affects: postgresql-10 (Ubuntu) Importance: Undecided Status: New ** Also affects: postgresql-9.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: postgresql-9.3 (Ubuntu) Importance: Undecided Status: New ** Also affects: postgresql-9.3 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: postgresql-9.5 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: postgresql-9.6 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: postgresql-10 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: postgresql-9.3 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: postgresql-9.5 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: postgresql-9.6 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: postgresql-10 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: postgresql-9.3 (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: postgresql-9.5 (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: postgresql-9.6 (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: postgresql-10 (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: postgresql-9.3 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: postgresql-9.5 (Ubuntu Xenial) Importance: Undecided Status: New ** Als
[Bug 1404396] Re: [regression] vgabios -> seabios breaks (my) 16-bit applications
This is all of such a long time ago, I've read through the old Mail threads and seabios git. As far as I can tell this would still be an issue. I'm a bit concerned we carry this Delta along like forever. To have some hope resolving that I wanted to ask you @Richard if you could still retest it with todays versions. Like on Bionic with seabios >=1.10 and a recent qemu. I could also build you a ppa with the 1.11.1 versions if you want - I'd just need someone that is sure how to test this 16bit UI app issues from the experience on it in the past. So if you think you could re-test this - please let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404396 Title: [regression] vgabios -> seabios breaks (my) 16-bit applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1404396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743637] Re: QEMU vhost-user shutdown suffers from use after free (missing clean shutdown)
This was regression tested already, it was tested by the STS engineer workign on it and we have postive feedback on a affected user - furthermore the former SRU now cleared on last Friday. >Xenial releases are not affected (So no need to think on other releases) and >the change to Xenial LGTM. That said sponsoring your change now ... I see it in X-unapproved, ready for SRU Team review. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743637 Title: QEMU vhost-user shutdown suffers from use after free (missing clean shutdown) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1743637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1769053] Re: Cannot start a guest with more than 1TB of RAM
On Tue, May 8, 2018 at 10:37 AM, Dr. David Alan Gilbert wrote: > * ChristianEhrhardt (1769...@bugs.launchpad.net) wrote: > > > Interesting; I thought this was supposed to work. > > > > Exactly that was my thought when triaging it initially > > Furthermore I assume people working la57 (https://lwn.net/Articles/ > 730925/) and such ran tests on much bigger sizes. > > I assume so, but I've not looked at the detail of that. > > > > Ah right Dan, if you're seeing the 40 bits physical in the guest you > > definitely need to try the flags I suggest in comment 6; host-phys- > > bits=true should work for you. > > > > I tested Bionic to be at least on libvirt 4.0 / qemu 2.11.1 when we want > > to check things under the "supposed to work now" flag. > > > > Defaults: > > Host: address sizes : 46 bits physical, 48 bits virtual > > Guest: address sizes : 40 bits physical, 48 bits virtual > > > > I ensured that with option -cpu host,host-phys-bits=true set I > successfully get what my host can provide in the guest: > > Guest: address sizes : 46 bits physical, 48 bits virtual > > > > Starting a guest with that >1TB (that would be mostly on swap if needed) > works just fine as expected. Here ~1063 GB from /proc/meminfo > > MemTotal: 1114676492 kB > > OK, good - that suggests there's nothing missing. > We enable host-phys-bits=true by default I think (in our machine type?) > Interesting approach, I see your comment about that already in [1] when it was added. I didn't realize some machine types were setting this already - I assume it isn't the general default for migratebility to other hosts (like our 36/39 bit laptops). I assume "we" in this context are RedHat downstream changes to the (some) machine type(s)? I see the benefit for huge guests to work without setting those properties, but I wonder if that caused you trouble in regard to migrations? [1]: https://patchwork.kernel.org/patch/9223999/ > > I also checked a more compatible approach like -cpu qemu64,phys-bits=42 > > and that works as well. > > > > IMHO - if anything - one could argue that libvirt/qemu could be smarter > > about e.g. auto adding those arguments (or print a warning) when > > crossing a certain memory size. > > The problem is there are a whole bunch of things that are hard to deal > with: > a) Cheaper CPUs tend to have smaller phys-bits even in the same > generation; e.g. my laptop is still 36 bits, a lot are 39 bits. I think > the same is true of the Xeon E3- family. It makes it hard to know > what to pick when you're going to allow migration. > > b) Reasoning about the total address size range is difficult; you've > got to take into account PCI address space and hot plug space etc > to know where the upper edge is. > I agree that checking the total address size might have too much false positives for all the complexities around "estimating" that size. /me is giving up this idea :-) > Dave > > > So for now I'd stick to the "actually works" summary and keep the status > > to incomplete. > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/1769053 > > > > Title: > > Cannot start a guest with more than 1TB of RAM > > > > Status in QEMU: > > Incomplete > > Status in qemu package in Ubuntu: > > Incomplete > > > > Bug description: > > Attempting to start a KVM guest with more than 1TB of RAM fails. > > > > It looks like we might need some extra patches: > > https://lists.gnu.org/archive/html/qemu-discuss/2017-12/msg5.html > > > > ProblemType: Bug > > DistroRelease: Ubuntu 18.04 > > Package: qemu-system-x86 1:2.11+dfsg-1ubuntu7 > > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > > Uname: Linux 4.15.0-20-generic x86_64 > > ApportVersion: 2.20.9-0ubuntu7 > > Architecture: amd64 > > CurrentDesktop: Unity:Unity7:ubuntu > > Date: Fri May 4 16:21:14 2018 > > InstallationDate: Installed on 2017-04-05 (393 days ago) > > InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 > (20161012.2) > > MachineType: Dell Inc. XPS 13 9360 > > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic > root=/dev/mapper/ubuntu--vg-root ro quiet splash > transparent_hugepage=madvise vt.handoff=1 > > SourcePackage: qemu > > UpgradeStatus: Upgraded to bionic on 2018-04-30 (3 days ago) > > dmi.bios.date: 02/26/2018 > > dmi.bios.vend
[Bug 1769849] [NEW] Please register Ubuntu 18.10 in postgresql-common
Public bug reported: Without this some autopkgtests break (even the default version is 10 and correct which makes the test work) as it emits messages on STDERR. This is filed as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898166 And already accepted as https://salsa.debian.org/postgresql/postgresql-common/merge_requests/1 As soon as 191 is uploaded and synced plenty of issue like [1] will go away. [1]: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-cosmic/cosmic/amd64/b/bgw- replstatus/20180505_004042_02bad@/log.gz ** Affects: postgresql-common (Ubuntu) Importance: Undecided Status: New ** Affects: postgresql-common (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #898166 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898166 ** Also affects: postgresql-common (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898166 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769849 Title: Please register Ubuntu 18.10 in postgresql-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1769849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767283] Re: nc doesn't support "-s IP" option
1.190-2 is in cosmic-proposed, but right now some tests still fail for 18.10/Cosmic not being fully open (e.g. no autotest/cloud images or missing 18.10 in postgres common. So I have to beg your pardon to wait a bit more :-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767283 Title: nc doesn't support "-s IP" option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668244] Re: systemd-udevd[15087]: Process '/bin/sh -c 'echo 180 >/sys$DEVPATH/device/timeout'' failed with exit code 2.
Thanks Andreas for the ping, yes the update will include the upstream fix [2] to this bug as well. If it fixes the issue of the reporter I'm not 100% sure. The reason for that uncertainty is [1] which mentions the rule changed but not working for some on the Fedora bug. I'd want to keep this separate to the ongoing SRU. There is a related discussion in [5] and a yet contained related fix [4] which might be what we want here eventually. So @Patrick - you can either wait for the SRU to complete to retest or you can test from the ppa [3] so that we know and can go on thinking about this already. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1431376#c21 [2]: https://github.com/vmware/open-vm-tools/commit/94028b39e929b162ebc320f455fb2f5b3af53f04 [3]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3226 [4]: https://github.com/vmware/open-vm-tools/commit/3011466e0f59471292a58ba5124238898d18945a [5]: https://github.com/vmware/open-vm-tools/issues/183 ** Bug watch added: github.com/vmware/open-vm-tools/issues #183 https://github.com/vmware/open-vm-tools/issues/183 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668244 Title: systemd-udevd[15087]: Process '/bin/sh -c 'echo 180 >/sys$DEVPATH/device/timeout'' failed with exit code 2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1668244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741390] Re: Please backport open-vm-tools 2:10.2.0-3 (main) from bionic
Thanks Andreas for the ping, yes this update will include the upstream fix to bug 1668244 as well. If it fixes the issue of the reporter I'm not 100% sure, but I'll update and subscribe to the other bug if not. We really don't need another unrelated bug stopping this backport :-) Actually we only wait for the SRU Team to action for a while now, I'm afraid this SRU being more complex is punted by many for its complexity in favor of other SRUs - I'll ask them once more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741390 Title: Please backport open-vm-tools 2:10.2.0-3 (main) from bionic To manage notifications about this bug go to: https://bugs.launchpad.net/xenial-backports/+bug/1741390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239109] Re: aarch64 clock_gettime with CLOCK_REALTIME_COARSE or CLOCK_MONOTONIC_COARSE fails with SIGBUS or SIGSEGV
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/libqb/+git/libqb/+merge/345212 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239109 Title: aarch64 clock_gettime with CLOCK_REALTIME_COARSE or CLOCK_MONOTONIC_COARSE fails with SIGBUS or SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libqb/+bug/1239109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747411] Re: Change of default database file format to SQL
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/nss/+git/nss/+merge/345213 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747411 Title: Change of default database file format to SQL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/certmonger/+bug/1747411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717790] Re: libibverbs should come from the rdma-core source package
Yeah, forgot to update this one - thanks Stefan for catching this! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717790 Title: libibverbs should come from the rdma-core source package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libibverbs/+bug/1717790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239109] Re: aarch64 clock_gettime with CLOCK_REALTIME_COARSE or CLOCK_MONOTONIC_COARSE fails with SIGBUS or SIGSEGV
This very very likely was fixed a long time ago, but I wanted to be sure.
So I used this simple test program:
#include
#include
#include
#include
void timespec_diff(const struct timespec *start, const struct timespec *stop,
struct timespec *result)
{
if ((stop->tv_nsec - start->tv_nsec) < 0) {
result->tv_sec = stop->tv_sec - start->tv_sec - 1;
result->tv_nsec = stop->tv_nsec - start->tv_nsec + 10UL;
} else {
result->tv_sec = stop->tv_sec - start->tv_sec;
result->tv_nsec = stop->tv_nsec - start->tv_nsec;
}
return;
}
void timecheck(clockid_t clkid, int argc, char **argv)
{
struct timespec start, stop, dur;
if( clock_gettime( clkid, &start) == -1 ) {
perror( "clock gettime" );
exit( EXIT_FAILURE );
}
system( argv[1] );
if( clock_gettime( clkid, &stop) == -1 ) {
perror( "clock gettime" );
exit( EXIT_FAILURE );
}
timespec_diff(&start, &stop, &dur);
printf( "%4ld.%-12ld\n", dur.tv_sec, dur.tv_nsec);
}
int main( int argc, char **argv )
{
timecheck(CLOCK_REALTIME, argc, argv);
timecheck(CLOCK_REALTIME_COARSE, argc, argv);
timecheck(CLOCK_MONOTONIC, argc, argv);
timecheck(CLOCK_MONOTONIC_COARSE, argc, argv);
timecheck(CLOCK_MONOTONIC_RAW, argc, argv);
timecheck(CLOCK_BOOTTIME, argc, argv);
timecheck(CLOCK_PROCESS_CPUTIME_ID, argc, argv);
timecheck(CLOCK_THREAD_CPUTIME_ID, argc, argv);
return( EXIT_SUCCESS );
}
$ gcc -Wall -o test test.c
$ ./test "sleep 0.3s"
All working on aarch64.
That said we can drop this Delta from libqb.
I have used a libqb synced from Debian in a ppa that doesn't have this fix
without issues.
That said we can drop this on the next merge/sync of libqb.
Setting the tasks here to Fix released (the issue reported in this bug no more
exists).
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: libqb (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1239109
Title:
aarch64 clock_gettime with CLOCK_REALTIME_COARSE or
CLOCK_MONOTONIC_COARSE fails with SIGBUS or SIGSEGV
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libqb/+bug/1239109/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239109] Re: aarch64 clock_gettime with CLOCK_REALTIME_COARSE or CLOCK_MONOTONIC_COARSE fails with SIGBUS or SIGSEGV
Actually lets close libqb with the sync then (when the Delta is dropped). ** Changed in: libqb (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239109 Title: aarch64 clock_gettime with CLOCK_REALTIME_COARSE or CLOCK_MONOTONIC_COARSE fails with SIGBUS or SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libqb/+bug/1239109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747411] Re: Change of default database file format to SQL
Corosync is actually a sync for Cosmic, with all Delta dropped: * Merge with Debian unstable (LP: #1747411). Remaining changes: * Dropped Changes: - Properly restart corosync and pacemaker together (LP: #1740892) d/rules: pass --restart-after-upgrade to dh_installinit. (this is default in compat >=10, and the package is 11) - d/control: indicate this version breaks all older pacemaker, to force an upgrade of pacemaker. (Upgrades have gone through Bionic, so we can drop this now) - d/corosync.postinst: if flagged to do so by pacemaker, start pacemaker on upgrade. (Can be dropped after Bionic) - New upstream release 2.4.3 (now in Debian) - Drop upstreamed patches and refresh others. (now in Debian) To get a second opinion on that I opened: https://code.launchpad.net/~paelzer/ubuntu/+source/corosync/+git/corosync/+merge/345184 ** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/corosync/+git/corosync/+merge/345184 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747411 Title: Change of default database file format to SQL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/certmonger/+bug/1747411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747411] Re: Change of default database file format to SQL
For corosync the affected components are corosync-qnetd. I checked and without adaption on install they would be fine as they initialize a new DB and nowhere does anyone specify the type. But as with some other tools on an upgrade we have to assume that the old DBM format will be tried to be read as SQL and then fail. Worth to notice is that Fedora who started all of this in [1] in their NSS build still uses DBM as default :-) corosync 2.4.4-1 of 20th of April made corosync compatible with the nss change. They prefix all calls with dbm to stay compat until the upgrade is handled by upstream. So a merge of this or latter version will address this for corosync. Afterwards nss can be merged dropping the change of the default. [1]: https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747411 Title: Change of default database file format to SQL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/certmonger/+bug/1747411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710077] Re: please sync or merge 6.32-1
Yeah this is a sync now, thanks for spotting - setting fix released. ** Changed in: ipset (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710077 Title: please sync or merge 6.32-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipset/+bug/1710077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769053] Re: Cannot start a guest with more than 1TB of RAM
> Interesting; I thought this was supposed to work. Exactly that was my thought when triaging it initially Furthermore I assume people working la57 (https://lwn.net/Articles/730925/) and such ran tests on much bigger sizes. > Ah right Dan, if you're seeing the 40 bits physical in the guest you definitely need to try the flags I suggest in comment 6; host-phys- bits=true should work for you. I tested Bionic to be at least on libvirt 4.0 / qemu 2.11.1 when we want to check things under the "supposed to work now" flag. Defaults: Host: address sizes : 46 bits physical, 48 bits virtual Guest: address sizes : 40 bits physical, 48 bits virtual I ensured that with option -cpu host,host-phys-bits=true set I successfully get what my host can provide in the guest: Guest: address sizes : 46 bits physical, 48 bits virtual Starting a guest with that >1TB (that would be mostly on swap if needed) works just fine as expected. Here ~1063 GB from /proc/meminfo MemTotal: 1114676492 kB I also checked a more compatible approach like -cpu qemu64,phys-bits=42 and that works as well. IMHO - if anything - one could argue that libvirt/qemu could be smarter about e.g. auto adding those arguments (or print a warning) when crossing a certain memory size. So for now I'd stick to the "actually works" summary and keep the status to incomplete. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769053 Title: Cannot start a guest with more than 1TB of RAM To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1769053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769251] Re: libvirtd group not automatically created when libvirt
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: libvirt (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769251 Title: libvirtd group not automatically created when libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1769251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769251] Re: libvirtd group not automatically created when libvirt
Hi Nur, that is odd the handling is as following. In the past there was a group libvirtd - new packaging in Debian and Ubuntu renamed that to libvirt but the install handles that. In case of a new install you would have those groups for libvirt: libvirt:x:132:paelzer libvirt-qemu:x:64055:libvirt-qemu But if you are on an upgrade form an older version to properly work with old filed created under the old user you'd get: libvirtd:x:132:paelzer libvirt:x:132:paelzer libvirt-qemu:x:64055:libvirt-qemu The GID is the same, and therefore both names are essentially the same group. The snippet for that is in libvirt-daemon-system.postinst and I don't see yet how that would "remove" the libvirtd group. if ! getent group libvirt >/dev/null; then if getent group libvirtd >/dev/null; then gid=`getent group libvirtd | getent group libvirtd | cut -d: -f3` groupadd --system --non-unique --gid "$gid" libvirt else addgroup --quiet --system libvirt fi fi This is this way since yakkety (16.10) and so far was not an issue. So the behavior should be: - new installs since >=Yakkety, you have just group "libvirt" - upgrade <=Xenial have libvirtd, and you get libvirtd AND libvirt on the same GID Nur, could you please outline: - what exact the error was that made your system need the libvirtd group? - a scenario how you'd ever have had a libvirtd group given that you Started with 17.04 after the changes I referred to? If this is a 3rd party automation/script you'd have to adapt to the new group name for new installs. As mentioned upgrades will be handled - but all of this is true since >=16.10. Waiting for your reply ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769251 Title: libvirtd group not automatically created when libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1769251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769511] Re: package libvirt-daemon-system (not installed) failed to install/upgrade: installed libvirt-daemon-system package post-removal script subprocess returned error exit status 128
Hi Ayslinn, thanks for your report. The users are actually only tried to be removed as there might be e.g. running processes or files of them. But it is not an issue if they stay behind, so normally this would be on install -> purge. Removing libvirt-daemon-system (4.0.0-1ubuntu8) ... Warning: Stopping virtlogd.service, but it can still be activated by: virtlogd.socket Removing libvirt-daemon dnsmasq configuration (Reading database ... 56452 files and directories currently installed.) Purging configuration files for libvirt-daemon-system (4.0.0-1ubuntu8) ... userdel: user libvirt-dnsmasq is currently used by process 438 /usr/sbin/deluser: `/usr/sbin/userdel libvirt-dnsmasq' returned error code 8. Exiting. userdel: user libvirt-dnsmasq is currently used by process 438 /usr/sbin/deluser: `/usr/sbin/userdel libvirt-dnsmasq' returned error code 8. Exiting. dpkg: warning: while removing libvirt-daemon-system, directory '/var/lib/libvirt/qemu/channel/target' not empty so not removed dpkg: warning: while removing libvirt-daemon-system, directory '/etc/libvirt/qemu' not empty so not removed Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for systemd (237-3ubuntu10) ... So yeah users are not removed but that is ok - intentional to not break other uses, and better to keep it around. So I wonder why it behaves differently for you than for me as shown above. >From your log: Purging configuration files for libvirt-daemon-system (4.0.0-1ubuntu8) ... /usr/sbin/delgroup: `libvirt-dnsmasq' still has `libvirtd' as their primary group! /usr/sbin/delgroup: `libvirt-dnsmasq' still has `libvirt' as their primary group! userdel: group libvirt-dnsmasq not removed because it is not the primary group of user libvirt-dnsmasq. dpkg: error processing package libvirt-daemon-system (--purge): So this is either a red-herring and the error in your case comes AFTER these messages about the user or something is different in your setup than in "the normal one". I just checked the postrm script, and it really has || bin/true on all these calls for the reasons outlined above. So those calls should never be the reason that this fails. To check what goes on in your case you could (if you want) try to debug it. First of all is the issue reproducible if you do. $ apt install libvirt-daemon-system $ apt remove --purge libvirt-daemon-system If the above reproduces the error then please do $ apt install libvirt-daemon-system # edit /var/lib/dpkg/info/libvirt-daemon-system.postrm # change set -e to set -ex $ apt remove --purge libvirt-daemon-system The latter should then be far more verbose on the console, please report back the full output of that terminal then so that we can think together what it could be. Until that data is available there is not much more I can do atm, so setting to incomplete for now. ** Changed in: libvirt (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769511 Title: package libvirt-daemon-system (not installed) failed to install/upgrade: installed libvirt-daemon-system package post-removal script subprocess returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1769511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764314] Re: libvirt doesn't show all interfaces
Hi rbasak, almost right - just missing a slight twist. Yes to all you said until "leaving the situation as-is for stable releases is appropriate since use case 1 above is far less serious than a potential regression in use case 3." I think we all ack on >=18.10 to select the udev backend and be good (which mean ncf gets demoted btw). But for the SRU "leave as is" is not the right option IMHO. If I fully buy in on the reasons you have given that we can't take away netcf backend from an SRU perspective then at least netcf will need a dependency to ifupdown because it calls ifup/ifdown and relies on that to work - if we can't take it away we have to make it work at least. My personal suggestion to this would therefore be: Cosmic: switch libvirt to udev Cosmic: add the ifupdown dependency to netcf, but also demote it Bionic: add ifupdown dependency to netcf That will remove the issue for >18.10 the right way and OTOH not violate SRU policy but fix netcf where it is still used. But I see from IRC discussions that we need to talk, I'll invite to share arguments and eventually decide on this, to then start fixing it (we have all the options now, just need to agree how to proceed). Note: all verification tests with udev backend are all good btw. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764314 Title: libvirt doesn't show all interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1764314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768864] Re: puppet ressources user and group not doing anything
So could that just have changed over the years upstream? And if so can you now run your config against e.g. a Cloud image which has this use created on first boot and still succeed with a config that dropped allowdupe? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768864 Title: puppet ressources user and group not doing anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1768864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86
For the per thread view use: $ sudo pidstat -t -p For perf to track kvm exits you can install it like: $ sudo apt install linux-tools-common And then run while your guest hangs (or not in the good case) as: $ sudo perf stat -e 'kvm:*' -a sleep 1h More on [1] if you want. [1]: https://www.linux-kvm.org/page/Perf_events -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767857 Title: Kernel 4.4.0-122 Breaks qemu-system-x86 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769053] Re: Cannot start a guest with more than 1TB of RAM
Thanks for your clarification Daniel, I'll mark both tasks incomplete then until you come back with that data. ** Changed in: qemu (Ubuntu) Status: New => Incomplete ** Changed in: qemu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769053 Title: Cannot start a guest with more than 1TB of RAM To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1769053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764314] Re: libvirt doesn't show all interfaces
Thanks Cyphermox for co-testign this with me. Here an example of his better interface overview now: virsh # iface-list Name State MAC Address --- enp3s0 active c8:60:00:6d:8c:07 lxdbr0 active fe:34:73:b4:77:ab maas active c8:60:00:6d:8c:07 staging active c8:60:00:6d:8c:07 Vlans are not always listed, but that still is much better than before. FYI: there is a test build in https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/3251 I did my own tests on this as well, on an upgrade from xenial all that most have in their E/N/I is just "lo" so that is what they see (but nobody wants/needs lo - it is just there because it is listed in E/N/I). $ virsh iface-list Name State MAC Address --- lo active 00:00:00:00:00:00 After the update to the proposed version I got much better output. $ virsh iface-list Name State MAC Address --- enp0s25 active 54:ee:75:61:c1:97 lxdbr0 active fe:24:e7:8e:21:8d wlp4s0 active 94:65:9c:0e:35:12 Btw those are just the active interfaces, you can list passive/inactive ones still (e.g. virt manager shows these greyed out). $ virsh iface-list --all Name State MAC Address --- conjureup0 inactive 12:ab:dc:f1:41:bd enp0s25 active 54:ee:75:61:c1:97 lo inactive 00:00:00:00:00:00 lxdbr0 active fe:24:e7:8e:21:8d strswanbr1 inactive 52:54:00:fc:52:4d strswanbr2 inactive 52:54:00:14:9e:81 virbr0 inactive 52:54:00:f4:ea:12 wlp4s0 active 94:65:9c:0e:35:12 I even see slaves devices on bridges in virt-manager now. Further functions of the iface- API space are good as well, like name<->mac translation. $ virsh iface-name 54:ee:75:61:c1:97 enp0s25 $ virsh iface-mac enp0s25 54:ee:75:61:c1:97 Even XML generation works if you want to use the snippet for other defines (e.g. guest forwards). $ virsh iface-dumpxml enp0s25 Only the define/destroy/edit actions are now (intentionally) blocked. The console calls are ok in the refusal message, just like in virt-manager. $ virsh iface-edit enp0s25 error: this function is not supported by the connection driver: virInterfaceDefineXML Failed. Try again? [y,n,f,?]: >From a "virt-manager" and similar tools perspective making changes now looks >reasonably guarded. If you try to do so you get "Error setting ... this function is not supported by the connection driver: virtInterdaceDefineXML" I also wanted to check a few more corner cases, so I did: - s390x system (for having odd device types) with some defined in E/N/I (was a Xenial upgrade) - a lxd container for udev/containers can be odd - Thanks to cycphermox for his MAAS based tests as well The container looks good, from an empty device view it got to # virsh iface-list --all Name State MAC Address --- eth0 active 00:16:3e:35:78:53 lo inactive 00:00:00:00:00:00 virbr0 inactive 52:54:00:ec:18:e5 Which ist just matching my "ip link" output The s390x system had shown the E/N/I devices before upgrade to the fixed version for being found in E/N/I but missed a few others. $ virsh iface-list --all Name State MAC Address --- encc000 active 02:00:00:8e:1a:31 encc000.2654 active 02:00:00:8e:1a:31 lo active 00:00:00:00:00:00 With udev mode this is much better catching all the others on my system that were formerly forgotten. $ virsh iface-list --all Name State MAC Address --- encc000 active 02:00:00:8e:1a:31 encc000.2654 active 02:00:00:8e:1a:31 encc003 inactive 02:00:00:28:29:a6 lo inactive 00:00:00:00:00:00 lxdbr0 active fe:42:16:55:ae:8b ovs-system inactive 4a:fd:83:ed:05:89 ovsbr0 inactive 52:17:63:0d:4b:ab virbr0 inactive 52:54:00:6e:c3:70 So all that seems good to me to go forward with that approach - and even worst case if we identify issues down the road it seems much better than the current broken state. Furthermore we actually don't want libvirt to try to be another netplan that translates XMLs into different backends. There is a reason why this was broken so long and never anybody complained - this particular subfeature of libvirt is mostly unused. I discussed wi
[Bug 1769053] Re: Cannot start a guest with more than 1TB of RAM
Hi Daniel, might I ask what you expect now? The changes to seabios are not even upstream yet in git://git.seabios.org/seabios.git The changes to qemu are neither upstream in git://git.qemu.org/qemu.git The changes linked also are for a qemu way++ back in time (like pre trusty), so they just don't apply. Some of these changes are handled already, but different like the second qemu change of above mail is in qemu since "6c7c3c21 x86: implement la57 paging mode" which is qemu >=2.9. That said - this one I could track, maybe the other changes are also upstream but in a way different form. At least for myself I currently have no >1TB system to even try this - well I have done this on s390x and there it works fine already but you need x86 here. Even when all of the above would be resolved, the mail above states that even if those are applied they still have issues when going >1TB. I think you'd need a clear this is what I tried and this is what fails with a setup as simple as possible. If it fails in Ubuntu we can build a latest upstream build for you and if failing there we can work with upstream to resolve properly. From there we can think about the backportability of those changes. But the suggested "hey there are these patches, won't work. Please don't get me wrong (I want to help), but so far this appears to me so far as a suggestion of a set of non-upstreamed, non-applicable, non-testable, non-working changes. We need to better sort out how to handle this which is why I ask what you expect to happen now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769053 Title: Cannot start a guest with more than 1TB of RAM To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1769053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768864] Re: puppet ressources user and group not doing anything
# id puppet
uid=112(puppet) gid=119(puppet) groups=119(puppet)
$ puppet resource -e user danisch
user { 'danisch':
ensure => present,
uid=> '1015',
gid=> '119',
comment=> 'Hadmut Danisch',
shell => '/bin/bash',
home => '/home/danisch'
}
When saving that on a bionic tree I get:
# puppet resource -e user danisch
Notice: Compiled catalog for b.lxd in environment production in 0.03 seconds
Info: Applying configuration version '1525418020'
Notice: /Stage[main]/Main/User[danisch]/ensure: created
Notice: Applied catalog in 0.13 seconds
Entries in passwd is
danisch:x:1015:119:Hadmut Danisch:/home/danisch:/bin/bash
Shouldn't that run the same backend code, but it works just fine?
What kind of configuration do you use exactly, could it be that upstream
changed to no more support an old format?
Can you reduce your config to try just the user management and then
check what the differences are to my example above?
Ubuntu makes no delta to upstream puppet in regard to the functionality
discussed here which is why I assume it is due to the newer version, but
maybe we can find the difference and resolve this for you.
** Changed in: puppet (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768864
Title:
puppet ressources user and group not doing anything
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1768864/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615694] Re: [860730] Host experiencing constant session termination and recreation while using jumbo frames
Any updates on testing from upstream (or from newer versions in newer Ubuntu releases) fixing the issue? ** Changed in: open-iscsi (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615694 Title: [860730] Host experiencing constant session termination and recreation while using jumbo frames To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1615694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768698] Re: package mysql-server-5.7 5.7.22-0ubuntu0.16.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 137
Thank you for taking the time to report this bug and helping to make Ubuntu better. On upgrading a service this service has to be restarted to pick up the fixes. Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration. But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state. Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart. Therefore the update of that package has to consider itself incomplete. Depending on your particular case there are two solutions: - either remove the offending package if you don't want to continue using it. - Or if you do want to keep it please fix the configuration so that re-starting the service will work. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: mysql-5.7 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768698 Title: package mysql-server-5.7 5.7.22-0ubuntu0.16.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 137 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1768698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768698] Re: package mysql-server-5.7 5.7.22-0ubuntu0.16.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 137
Hi Rogerio, neither the mysql error log nor the journal that you auto-attached contain useful hints to help you. If anything then I'd wonder about: 2018-05-03T01:48:33.898935Z 0 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.7.22-0ubuntu0.16.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) 2018-05-03T01:48:33.900092Z 2 [Note] Access denied for user 'root'@'localhost' (using password: NO) You said this is a clean install of mysql. So is the problem reproducible if you purge and install it again? $ apt remove --purge mysql-server mysql-server-5.7 mysql-server-core-5.7 $ apt install mysql-server Is that just running into the SAME issue again? If so please share your right after the fail - /var/log/mysql/error.log - the ouput of journalctl -xe - the ouput of your console since you started with the commands above -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768698 Title: package mysql-server-5.7 5.7.22-0ubuntu0.16.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 137 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1768698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86
Hi Skipper, thanks for sharing the qemu cmdline, there is nothing odd in this and I can run a system like that (not a win 10 guest) just fine. What about the per thread stats I asked, which threads are busy and where do they consume time? Depending on your experience you could even check "perf kvm stat" and such to see which exists you trigger (unless it is mostly in guest anyway). @Kernel Team - have you had similar reports? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767857 Title: Kernel 4.4.0-122 Breaks qemu-system-x86 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764314] Re: libvirt doesn't show all interfaces
Thanks for your reply Nicolas, so even for you if udev backend would work it would be preferred (full view of the network). We are evaluating if udev works well for the read-only part and I discussed with upstream how to enable/disable as well as on the approach in general. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764314 Title: libvirt doesn't show all interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1764314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764314] Re: libvirt doesn't show all interfaces
Networks are configured through net-* commands (and respective APIs) and they all work. This is what is commonly used by libvirt users and solutions depending on libvirt. The scope of iface-* commands is to manage the Host network interfaces. This is not really what we'd want libvirt to do. You can use networkd/NetworkManager directly and if you want a great one for all solution use https://netplan.io/ - but we don't really want libvirt "for that task". I see that the virt-manager tab "Connection Details" -> "Network Interfaces" would become a read-only pane then. But considering how long it had partial content and set up things not 100% as they should be set up maybe it is even a fix to stop it from doing so. I'll investigate the feasibility of the udev backend and if we can set that as the default. With some luck we can keep netcf around for those who want to opt into the former behavior, but that has to be checked - and actually I'd vote for getting rid of it if that finds approval. @Nicolas - did you have a specific use case in mind that fully relies on those things, because in discussion we cna't find one. Or did you just find it by checking out virt-manager in 18.04 but are not relying on it to be able to write interface configurations? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764314 Title: libvirt doesn't show all interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1764314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764314] Re: libvirt doesn't show all interfaces
Note: easiest test without compiling is likely $ apt install netcf $ netcftool list ... Related to all of that is bug 1688345. I contacted cyphermox who filed and worked on that to get his opinion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764314 Title: libvirt doesn't show all interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1764314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764314] Re: libvirt doesn't show all interfaces
Hi, after sleeping once about this to sort my thoughts I have this morning revisited most of the code. ## Usage and state of ncf ## In its only user currently being libvirt I checked that usage via: $ git log src/interface/ There were only structural changes (how to allocate, make interface accessible, global renames), but no new features "through netcf" or such post 2015 which matches when major activity there stopped. Once again, I checked former versions this is more or less broken for a long time since NetworkManager configured devices as well as networkd configured devices are not shown. Other drivers it only check for their old style as well - ifcfg- files (suse), and check scripts in /etc/sysconfig/network-scripts/ (redhat). None handled any other (e.g. those through wicked) configuration scheme either. I come back to think those iface-* action in libvirt not being important for many use cases for not having broken on someone before :-/ I was also trying other interface API calls of libvirt through virsh, they are all affected in a similar way (e.g. ifup not found, ...). ## Alternatives for Libvirt ## There is a libvirt udev based interface backend available as well meant for Distribution/Releases with no netcf support. And in some way unless we implement that we are just that now. That switch would need to be tested as well and would effectively make this backend read-only It supports .connectNumOfInterfaces = udevConnectNumOfInterfaces, /* 1.0.0 */ .connectListInterfaces = udevConnectListInterfaces, /* 1.0.0 */ .connectNumOfDefinedInterfaces = udevConnectNumOfDefinedInterfaces, /* 1.0.0 */ .connectListDefinedInterfaces = udevConnectListDefinedInterfaces, /* 1.0.0 */ .connectListAllInterfaces = udevConnectListAllInterfaces, /* 1.0.0 */ .interfaceLookupByName = udevInterfaceLookupByName, /* 1.0.0 */ .interfaceLookupByMACString = udevInterfaceLookupByMACString, /* 1.0.0 */ .interfaceIsActive = udevInterfaceIsActive, /* 1.0.0 */ .interfaceGetXMLDesc = udevInterfaceGetXMLDesc, /* 1.0.0 */ But drops transactions and: .interfaceDefineXML = netcfInterfaceDefineXML, /* 0.7.0 */ .interfaceUndefine = netcfInterfaceUndefine, /* 0.7.0 */ .interfaceCreate = netcfInterfaceCreate, /* 0.7.0 */ .interfaceDestroy = netcfInterfaceDestroy, /* 0.7.0 */ So (if tests confirm to be ok) at the reduced functionality of no write (better than broken write still) one option we have is switching to udev backend in libvirt and completely remove netcf. ## netcf usage and implementation ## Of the netcf API the currently used set is: ncf_change_begin ncf_change_commit ncf_change_rollback ncf_close ncf_define ncf_error ncf_if_down ncf_if_free ncf_if_mac_string ncf_if_name ncf_if_status ncf_if_undefine ncf_if_up ncf_if_xml_desc ncf_if_xml_state ncf_init ncf_list_interfaces ncf_lookup_by_mac_string ncf_lookup_by_name ncf_num_of_interfaces All implementations use augeas to handle the config files for read as well as write. All Debian/Ubuntu code still is on /etc/network/interfaces. One option to consider as long as there will be ifupdown is to just depend on it to get back the support we had since the usage of networkd/NetworkManager - we would get: - iface write support through E/N/I - partial visiblity (devices not created through E/N/I are not visible to libvirt/netcf (as they are for quite a while). Essentially as it was since ~Xenial with nobody complaining so far. => But this would lock in ifupdown forever until effort is taken to e.g. implement a new backend in lbvirt or netcf. After reading through netcf code I decided it is too much to "just switch" to a new implementation via fixes. It is essentially a new backend. Actually worse so - it is NetworkManager / Networkd / neplan backend. Netplan abstracts from the former two for us, but I'm not yet sure we can map all of the API perfectly - so this is a real a.k.a. needs to be jointly planned effort on netcf+netplan. ## TL:DR - Options I see atm ## 1. ifupdown is effectively a hard dependency of netcf, so we must add that dependency in packaging. This will fix and enable support as we had it since ~Xenial Libvirt is seeded, but not part of the default install, so we don't break our "get ifupdown out of the default install" efforts we have made. 2. We likely want to get rid of the ifupdown dependency at some point (later releases), options for that are: 2A) switch in libvirt to udev backend (readonly), drop netcf lib completely (reduced functionality, but if we consider it almost unused anyway...?) 2B) networkd/networkManager/netplan backend for libvirt to drop netcf from Archive
[Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86
Also a per qemu thread view is often useful, you might also add $ pidstat -t -p Further since this is reported as kernel update regression I'll flag it as that for now. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767857 Title: Kernel 4.4.0-122 Breaks qemu-system-x86 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764314] Re: libvirt doesn't show all interfaces
This didn't fully work even pre netplan, in fact it is separate. On my partially E/N/I partially NetworkManager system only the former are accessible to netcf. So this functionality from libvirts POV was reduced for quite a while. While netcf itself can be considered really broken atm. That is why I set low/high severity differently for the two affected packages. ** Changed in: libvirt (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764314 Title: libvirt doesn't show all interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1764314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763468] Re: [Ubuntu 18.04] P8 compat mode migration fails for Ubuntu 16.04.4 P8 Guest from Ubuntu 16.04.4 P8 Host -> Ubuntu 18.04 P9 Host
I wanted to take a look at this again, but TBH at the moment all I've got was crashing my P9 system three times. I'll start a mail thread on it and keep this bug clean of it for now. While resolving that I hope that Bala/Greg will find something about the issue here on their side. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763468 Title: [Ubuntu 18.04] P8 compat mode migration fails for Ubuntu 16.04.4 P8 Guest from Ubuntu 16.04.4 P8 Host -> Ubuntu 18.04 P9 Host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1763468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752797] Re: [Ubuntu 18.04] [Libvirt] virsh qemu-attach fails to add qemu process with libvirt
Following the update to set won't fix here as well ** Changed in: libvirt (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752797 Title: [Ubuntu 18.04] [Libvirt] virsh qemu-attach fails to add qemu process with libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1752797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764314] Re: libvirt doesn't show all interfaces
It is sometimes surprising what extra features libvirt all has - I
haven't touched this for all the time working with it - Feature of 2009
it seems :-)
First of all yes, I also can't see anything on 18.04 boxes (not that on
16.04 I'd have got a lot, only "lo" actually).
There is nothing of the common issues:
- no appamor denie
- no error in a full-debug libvirtd log
Internally this goes through virshInterfaceListCollect ->
virConnectListAllInterfaces ->
conn->interfaceDriver->connectListAllInterfaces
That call to the libvirt daemon succeeds but returns:
(gdb) p *(virshInterfaceListPtr)ifaces
$15 = {ifaces = 0x5580f370, nifaces = 0}
So that is an empty list from the daemon, check what happens over there.
The backend uses netcf through ncf_list_interfaces and gets a count of zero.
The implementation of this is in ncf.
It does a few checks and then goes to drv_list_interfaces which for us is is
implemented in drv_debian.c.
This then calls list_interface_ids with arguments to fill the list (one can set
arg 2/3 to 0 to just get a number).
This then uses list_interfaces to generate a list via uniq_device_names
and checks against some filters.
But uniq_device_names already gets an argument with "how many"
interfaces are to be expected and that is zero.
This number comes from:
aug_fmt_match(ncf, &devs, "%s/iface", network_interfaces_path);
This implementation is based on ENI as network_interfaces_path is essentially
static const char *const network_interfaces_path =
"/files/etc/network/interfaces"
So I think we found a case of ENI -> (pure) networkd transition causing some
issues.
That also explains why on my 16.04 I don't see all interfaces, I have not all
(none but lo) configured via ENI in /etc/network/interfaces.
This is not so much a lbivirt, but much more a netcf issue.
IMHO this was all forgotten in the netplan change :-/ and needs implementation.
Maybe it needs more since it seems to just hang around for quite a while.
A testcase for now looks like that:
$ apt source netcf
$ sudo apt build-dep netcf
$ cd netcf-0.2.8
$ ./configure --with-driver=debian
$ make -j12
$ make check
$ cd tests
$ make test-debian
$ make check
That actually should have tested the function we found breaking - odd.
Instead one can for now use a very simplified netcfConnectListInterfacesImpl:
$ sudo apt install libnetcf1
$ cat >> test.c << EOF
#include
#include
int main()
{
int count = 0;
int status = NETCF_IFACE_ACTIVE | NETCF_IFACE_INACTIVE;
struct netcf *netcf = NULL;
if (ncf_init(&netcf, NULL) != 0) {
printf("Init failed\n");
return -1;
}
count = ncf_num_of_interfaces(netcf, status);
printf("Count is %d\n", count);
return 0;
}
EOF
$ gcc -Wall -o test test.c -lnetcf; ./test
That should return a number matching your /et/network/interfaces on
16.04, but due to lacking it nothing on 18.04
Only good thing for now, it seems only libvirt uses netcf and while iface list
and such fail they are not strictly required (as we can see it only now shows
up for virt-manager centric usage).
Never the less a big issue :-/
There is a udev backend, maybe we should consider switchign instead of
implementing so much in netcf - both ways need a in -depth analysis.
** Changed in: libvirt (Ubuntu)
Importance: Undecided => High
** Also affects: netcf (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netcf (Ubuntu)
Status: New => Triaged
** Changed in: netcf (Ubuntu)
Importance: Undecided => High
** Changed in: libvirt (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764314
Title:
libvirt doesn't show all interfaces
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1764314/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767997] Re: refreshing a pool destroys all volume info in libvirt zfs backend
Opened for a discussion upstream at: https://www.redhat.com/archives/libvir-list/2018-May/msg00043.html I didn't have your email to CC you, but you can track via the WEB UI of the ML. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767997 Title: refreshing a pool destroys all volume info in libvirt zfs backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1767997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764668] Re: guest cleanup script fails to iterate
In fact the MP above is approved by Pitti who sort of owns cockpit. Since neither of us can push this change I'd appreciate if on SRU handling this could be done (as it is ~ubuntu-sru scope). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764668 Title: guest cleanup script fails to iterate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1764668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762769] Re: missing entry at apparmor profile for nova instances
Interesting, I didn't know about the need of that stdio_handler. But still the issue is solved then - great. I'll set the status to invalid then to reflect that (we have no closed). Thanks Stefan! ** Changed in: libvirt (Ubuntu) Status: Incomplete => Invalid ** Changed in: cloud-archive Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762769 Title: missing entry at apparmor profile for nova instances To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1762769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767997] Re: refreshign a pool destroys all volume info in libvirt zfs backend
** Summary changed: - virt-manager destroys all volumes in libvirt zfs pool + refreshign a pool destroys all volume info in libvirt zfs backend ** Summary changed: - refreshign a pool destroys all volume info in libvirt zfs backend + refreshing a pool destroys all volume info in libvirt zfs backend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767997 Title: refreshing a pool destroys all volume info in libvirt zfs backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1767997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764668] Re: guest cleanup script fails to iterate
FYI - we opened [1], and while this needs some processing to be acked an merged I'd ask the SRU team to consider these autopkgtest fails not a blocker to move on with thie SRU here atm. [1]: https://code.launchpad.net/~paelzer/britney/hints-ubuntu-artful- cockpitfails/+merge/344874 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764668 Title: guest cleanup script fails to iterate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1764668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767997] Re: virt-manager destroys all volumes in libvirt zfs pool
I was collecting a summary to report upstream, but then I wondered are there other scenarios where this should not be stripped to the base? Or is there another common use case were the pool is created differently so it works? I followed some other guides and ended up with a non-external created pool: myzfspool zpoolname $ virsh pool-create --build Nzfs.xml Now I have a pool (with the odd name zpoolname) $ sudo zpool list; sudo zfs list NAMESIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT Xzfs 80M 146K 79,9M - 1% 0% 1.00x ONLINE - Yzfs 80M 117K 79,9M - 1% 0% 1.00x ONLINE - zfs 80M 130K 79,9M - 1% 0% 1.00x ONLINE - zfs2 80M 94,5K 79,9M - 1% 0% 1.00x ONLINE - zpoolname 160M 646K 159M - 1% 0% 1.00x ONLINE - NAME USED AVAIL REFER MOUNTPOINT Xzfs 12,6M 27,4M24K /Xzfs Xzfs/images 12,5M 27,4M24K /Xzfs/images Xzfs/images/vol1 12,5M 39,9M12K - Yzfs 108K 39,9M24K /Yzfs Yzfs/images 24K 39,9M24K /Yzfs/images zfs 35,3M 4,67M24K /zfs zfs/vol1 12,5M 17,2M12K - zfs/vol2 22,8M 27,4M12K - zfs278K 39,9M24K /zfs2 zpoolname 84K 79,9M24K /zpoolname >From this libvirt can create volumes. $ virsh vol-create-as --pool myzfspool --name vol1 --capacity 10M Gets me in zfs tools: ... zpoolname/vol112,5M 79,9M12K - And with that libvirt can refresh just fine: $ virsh vol-list --pool myzfspool Name Path vol1 /dev/zvol/zpoolname/vol1 $ virsh pool-refresh myzfspool Pool myzfspool refreshed $ virsh vol-list --pool myzfspool Name Path vol1 /dev/zvol/zpoolname/vol1 So I wonder is this "just" a conflict between how libvirt expects pools to be set up (and as it does by itself) vs the manual set up one? After I learned the above I tried this: $ fallocate -l 100M /tmp/Mzfs $ sudo zpool create Mzfs /tmp/Mzfs $ virsh pool-define-as --name zfs --source-name Mzfs --type zfs $ virsh pool-start zfs $ virsh vol-create-as --pool zfs --name vol1 --capacity 10M $ virsh vol-list --pool zfs Name Path vol1 /dev/zvol/Mzfs/vol1 $ virsh pool-refresh zfs Pool zfs refreshed $ virsh vol-list --pool zfs Name Path vol1 /dev/zvol/Mzfs/vol1 This confirms that if you skip the "zfs create zfs/images" step and define the libvirt pool from the zpool directly then all things seem to work. I'd appreciate a report upstream still, but I think the issue is no more that severe atm. ** Changed in: libvirt (Ubuntu) Importance: High => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767997 Title: virt-manager destroys all volumes in libvirt zfs pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1767997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767997] Re: virt-manager destroys all volumes in libvirt zfs pool
Ok, without apparmor fixes (unlikely soon for reasons outlined in other bug) or you weakening the isolation a bit on your system it won't work then. So lets focus on the clearing of this volume list in this bug - which should not happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767997 Title: virt-manager destroys all volumes in libvirt zfs pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1767997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path
@Tim - Could you check the ntp apparmor profile if it has the change that was made in 1:4.2.8p10+dfsg-5ubuntu4 ? It is a conffile so if depending on your former changes it might have been not updated by default. Essentially if /etc/apparmor.d/usr.sbin.ntpd has flags=(attach_disconnected) ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727202 Title: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767997] Re: virt-manager destroys all volumes in libvirt zfs pool
Flagging as libvirt issue as we ruled out virt-manager -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767997 Title: virt-manager destroys all volumes in libvirt zfs pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1767997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767997] Re: virt-manager destroys all volumes in libvirt zfs pool
Haven't read all your updates in between while I was writing :-) Need to re-read all you posted - thanks for your work on this. You might answer the questions around if that worked for you before or not while I'm doing so ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767997 Title: virt-manager destroys all volumes in libvirt zfs pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1767997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767997] Re: virt-manager destroys all volumes in libvirt zfs pool
Read - I see we both got to the bad zpool call for now. I'm in a hurry and need to drop for now (sorry), but will look at the source and maybe if there are later fixes post 4.0 - if not I'll go deeper and try to create a test version. Thanks for finding "virsh pool-refresh zfs" for this case. ** Package changed: virt-manager (Ubuntu) => libvirt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767997 Title: virt-manager destroys all volumes in libvirt zfs pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1767997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767997] Re: virt-manager destroys all volumes in libvirt zfs pool
Repro without disks or other HW dependency: $ apt install zfsutils-linux $ fallocate -l 100M /tmp/zfs $ sudo zpool create zfs /tmp/zfs $ sudo zfs create -V 10M zfs/vol1 You can use that as a disk just fine: But using disks "through" libvirt pools had a known issue - see bug 1677398 This is a known issue, but implementation is rather complex and benefit low. Those that used it so far added custom rules to allow access as needed. As outlined there (until implemented) you'd usually have the option to either use it without the pool feature or to allow certain paths for your system in the virt related apparmor rules. That said the TL;DR zfs !pools! never worked so far unless you manually configured the above. Therefore I'd not expect zfs-pools to work now as-is. I trying to get to the "volumes seen but then lost" that you described still. $ fallocate -l 100M /tmp/Xzfs $ sudo zpool create Xzfs /tmp/Xzfs $ sudo zfs create Xzfs/images $ virsh pool-define-as --name Xzfs --source-name Xzfs/images --type zfs I ended with the pool not being started (expected after pool-define-as), but then $ virsh pool-start Xzfs $ virsh vol-create-as --pool Xzfs --name vol1 --capacity 10M $ virsh vol-list --pool Xzfs Name Path vol1 /dev/zvol/Xzfs/images/vol1 >From here I: 1. installed virt-manager - still ok 2. started virt manager - breaking it So far I can at least "confirm" your issue already. I found no apparmor issue (the known issue comes later when the guests start not from libvirt). But I found in the libvirt log this: error : virCommandWait:2601 : internal error: Child process (/sbin/zpool get -Hp health,size,free,allocated Xzfs/images) unexpected exit status 1: cannot open 'Xzfs/images': invalid character '/' in pool name I assume this is what virt-manager triggers in libvirt every time, but I don't know the entry point yet. Need to search for it once I'm back (one day out tmrw). I know you had some of your setup before upgrade, did you have tweaked it to work with zfs pools before? If that was the case I'd be much more concerned. in general (even thou I think pools won't work) I'd not want virt-manager to clear the pool view, in fact I'd expect libvirt to keep working and just the start of the qemu to fail (due to the apparmor denial). ** Changed in: virt-manager (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/1767997 Title: virt-manager destroys all volumes in libvirt zfs pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1767997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767997] Re: virt-manager destroys all volumes in libvirt zfs pool
Hi (again) Brian, this is rather unexpected let me try to follow what happened. So far you only triggered this via virt-manager start/refresh so I'll follow that until we know a non virt-manager trigger - usually it only calls libvirt tasks so I'd assume we can identify a virsh or so to trigger the same. Fortunately it seems it "only" seems to forget in libvirt about it quoting you on "All zfs volumes have been forgotten!! Fortunately they still exist in zfs". I should be able to start testing this in an hour or so I hope ... ** Changed in: virt-manager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767997 Title: virt-manager destroys all volumes in libvirt zfs pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1767997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767973] Re: libvirt no longer has support for zfs pools (18.04 regression)
I even had an entry in release notes already: "The packaging now builds libvirt storage drivers as pluggable libraries. This slims down the installation requirements but some drivers of less general interest will now be found in universe. (ex: gluster, sheepdog, zfs)" Extenting that with: "On the other hand that means that some formerly integrated features like rbd or zfs now require you to install the package after upgrade e.g. in this case libvirt-daemon-driver-storage- zfs." Thanks, marking this bug invalid then and I'm happy I could help you! ** Changed in: libvirt (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767973 Title: libvirt no longer has support for zfs pools (18.04 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1767973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763468] Re: [Ubuntu 18.04] P8 compat mode migration fails for Ubuntu 16.04.4 P8 Guest from Ubuntu 16.04.4 P8 Host -> Ubuntu 18.04 P9 Host
Ok, if that was what you had in mind when selecting patches fine. Thanks for taking a look. I'll for tracking eventually fork a bug number for the remaining issue on this then, but this can wait until it is discussed and pre-tested here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763468 Title: [Ubuntu 18.04] P8 compat mode migration fails for Ubuntu 16.04.4 P8 Guest from Ubuntu 16.04.4 P8 Host -> Ubuntu 18.04 P9 Host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1763468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767973] Re: libvirt no longer has support for zfs pools (18.04 regression)
Note - in fact this allows to compile more (instead of fewer as assumed) storage backends as we can deliver some in main (as needed) and the rest in universe [1] instead of having to support all of them - which e.g. failed some security checks for sheepdog. So I'd really hope what I described is your issue so that we can fix it by documentation to help others. [1]: https://help.ubuntu.com/community/Repositories/Ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767973 Title: libvirt no longer has support for zfs pools (18.04 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1767973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767973] Re: libvirt no longer has support for zfs pools (18.04 regression)
Hi Brian, some optional storage backends where separated by Debian a while ago to avoid pulling in too much non-needed code in most of the cases. Now on a upgrade since this dependency is only a suggest (for above) reason isn't installed automatically. Can you try installing (or check if you have installed) package: => libvirt-daemon-driver-storage-zfs If you have not, could you check if installing it resolves your issue? If it does I wonder if I should add a note to the release-notes - I think so. But lets make sure that is your issue - so please report back of your case. ** Changed in: libvirt (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767973 Title: libvirt no longer has support for zfs pools (18.04 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1767973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679704] Re: libvirt profile is blocking global setrlimit despite having no rlimit rule
Per bug 1763427 this is Fix released since 4.15.0-18.19 ** Changed in: apparmor (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679704 Title: libvirt profile is blocking global setrlimit despite having no rlimit rule To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1679704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764668] Re: guest cleanup script fails to iterate
@SRU-Team: Dep8 tests show unrelated issues in cockpit for Artful. I'm in discussion with pitti if we should even mask those tests, considering what fails and what we changed they are really unrelated (and this type of error showed before the changes of this SRU). See the artful column in [1] for its history. So I'd ask you to ignore the three hits on cockpit for artful for this SRU. If pitti and I conclude that this should be a Britney override we will do so independent to this SRU. [1]: http://autopkgtest.ubuntu.com/packages/cockpit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764668 Title: guest cleanup script fails to iterate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1764668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763468] Re: [Ubuntu 18.04] P8 compat mode migration fails for Ubuntu 16.04.4 P8 Guest from Ubuntu 16.04.4 P8 Host -> Ubuntu 18.04 P9 Host
The old title defies my understanding of this case thou, never the less all changes so far were to 18.04. And on confirmation it was 18.04 broken -> 18.04 working after the fix. I'll set up a few systems to try if they are free atm. But a new bug would still be appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763468 Title: [Ubuntu 18.04] P8 compat mode migration fails for Ubuntu 16.04.4 P8 Guest from Ubuntu 16.04.4 P8 Host -> Ubuntu 18.04 P9 Host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1763468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764668] Re: guest cleanup script fails to iterate
As described in testcases I set up a few guests and made sure some of them won't shutdown properly. We want to see 1. all tried to shut down 2. waiting up until timeout for the one that does not shut down ## Pre-Fix ## Xenial: sudo /usr/lib/libvirt/libvirt-guests.sh stop Running guests on default URI: b4, b1, b2, b3 Shutting down guests on default URI... Starting shutdown on guest: b4 Starting shutdown on guest: b1 Waiting for 4 guests to shut down, 120 seconds left Failed to determine state of guest: 83964d03-0d3b-47c3-a17d-fd104e2511f8. Not tracking it anymore. Failed to determine state of guest: 9f11ae0c-b73b-4d4b-abdb-b9acda341e84. Not tracking it anymore. Shutdown of guest b4 complete. Shutdown of guest b1 complete. Starting shutdown on guest: b2 Starting shutdown on guest: b3 Shutdown of guest b2 complete. Shutdown of guest b3 complete. root@x:~# virsh list IdName State 5 b4 running 6 b1 running 7 b2 running 8 b3 running Artful: # sudo /usr/lib/libvirt/libvirt-guests.sh stop Running guests on default URI: b1, b2, b3, b4 Shutting down guests on default URI... Starting shutdown on guest: b1 Starting shutdown on guest: b2 Waiting for 4 guests to shut down, 120 seconds left Failed to determine state of guest: 80ba5ac4-fb68-4ee7-b8d6-313313f29ab4. Not tracking it anymore. Failed to determine state of guest: 688847ca-5510-462d-ae5e-988d322d1471. Not tracking it anymore. Shutdown of guest b1 complete. Shutdown of guest b2 complete. Starting shutdown on guest: b3 Starting shutdown on guest: b4 Shutdown of guest b3 complete. Shutdown of guest b4 complete. root@a:~# virsh list IdName State 1 b1 running 4 b4 running With the fixes from proposed libvirt-bin/artful-proposed 3.6.0-1ubuntu6.6 amd64 [upgradable from: 3.6.0-1ubuntu6.5] libvirt-clients/artful-proposed 3.6.0-1ubuntu6.6 amd64 [upgradable from: 3.6.0-1ubuntu6.5] libvirt-daemon/artful-proposed 3.6.0-1ubuntu6.6 amd64 [upgradable from: 3.6.0-1ubuntu6.5] libvirt-daemon-system/artful-proposed 3.6.0-1ubuntu6.6 amd64 [upgradable from: 3.6.0-1ubuntu6.5] libvirt0/artful-proposed 3.6.0-1ubuntu6.6 amd64 [upgradable from: 3.6.0-1ubuntu6.5] libvirt-bin/xenial-proposed 1.3.1-1ubuntu10.22 amd64 [upgradable from: 1.3.1-1ubuntu10.21] libvirt0/xenial-proposed 1.3.1-1ubuntu10.22 amd64 [upgradable from: 1.3.1-1ubuntu10.21] Xenial: root@x:~# sudo /usr/lib/libvirt/libvirt-guests.sh stop Running guests on default URI: b4, b2, b1, b3 Shutting down guests on default URI... Starting shutdown on guest: b4 Starting shutdown on guest: b2 Waiting for 4 guests to shut down, 120 seconds left Waiting for 4 guests to shut down, 115 seconds left Waiting for 4 guests to shut down, 110 seconds left Waiting for 4 guests to shut down, 105 seconds left Waiting for 4 guests to shut down, 100 seconds left Waiting for 4 guests to shut down, 95 seconds left Waiting for 4 guests to shut down, 90 seconds left Waiting for 4 guests to shut down, 85 seconds left Waiting for 4 guests to shut down, 80 seconds left Shutdown of guest b2 complete. Starting shutdown on guest: b1 Waiting for 3 guests to shut down, 75 seconds left Waiting for 3 guests to shut down, 70 seconds left Waiting for 3 guests to shut down, 65 seconds left Shutdown of guest b1 complete. Starting shutdown on guest: b3 Waiting for 2 guests to shut down, 60 seconds left Waiting for 2 guests to shut down, 55 seconds left Waiting for 2 guests to shut down, 50 seconds left Waiting for 2 guests to shut down, 45 seconds left Waiting for 2 guests to shut down, 40 seconds left Shutdown of guest b3 complete. Waiting for 1 guests to shut down, 35 seconds left Waiting for 1 guests to shut down, 30 seconds left Waiting for 1 guests to shut down, 25 seconds left Waiting for 1 guests to shut down, 20 seconds left Waiting for 1 guests to shut down, 15 seconds left Waiting for 1 guests to shut down, 10 seconds left Waiting for 1 guests to shut down, 5 seconds left Timeout expired while shutting down domains root@x:~# virsh list IdName State 5 b4 running Artful: sudo /usr/lib/libvirt/libvirt-guests.sh stop Running guests on default URI: b4, b2, b3, b1 Shutting down guests on default URI... Starting shutdown on guest: b4 Starting shutdown on guest: b2 Waiting for 4 guests to shut down, 120 seconds left Shutdown of guest b2 complete. Starting shutdown on guest: b3 Shutdown of guest b3 complete. Starting shutdown on guest: b1 Waiting for 2 guests to shut down, 115 seconds left Shutdown of guest b1 complete. Waiting for 1 guests t
[Bug 1763468] Re: [Ubuntu 18.04] P8 compat mode migration fails for Ubuntu 16.04.4 P8 Guest from Ubuntu 16.04.4 P8 Host -> Ubuntu 18.04 P9 Host
Hi Bala, interesting, but not 100% the same case IMHO. The former fix and discussion was about 18.04 on P8 to 18.04 on P9 and it worked fine after the fixes that were pointed out were integrated. I'd ask you to file a new bug (internally for you and your PPC dev's as well as with launchpad for us) to discuss potential needs for 16.04 on P8 to 18.04 on P9. Only then I think tracking and discussions will go well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763468 Title: [Ubuntu 18.04] P8 compat mode migration fails for Ubuntu 16.04.4 P8 Guest from Ubuntu 16.04.4 P8 Host -> Ubuntu 18.04 P9 Host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1763468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705743] Re: qemu-system-x86 crashes when VNC connection is established
Using the repro steps above: 1. as-is in Xenial: ii qemu-system-x86 1:2.5+dfsg-5ubuntu10.25 amd64QEMU full system emulation binaries (x86) $ qemu-system-x86_64 -enable-kvm -vnc unix:/tmp/service/../service/../service/../service/vnc-sock # due to socat in other shell: *** Error in `qemu-system-x86_64': free(): invalid pointer: 0x7f1e3c2bbbd8 *** Once again, from proposed qemu-block-extra/xenial-proposed 1:2.5+dfsg-5ubuntu10.26 amd64 [upgradable from: 1:2.5+dfsg-5ubuntu10.25] qemu-kvm/xenial-proposed 1:2.5+dfsg-5ubuntu10.26 amd64 [upgradable from: 1:2.5+dfsg-5ubuntu10.25] qemu-system-common/xenial-proposed 1:2.5+dfsg-5ubuntu10.26 amd64 [upgradable from: 1:2.5+dfsg-5ubuntu10.25] qemu-system-x86/xenial-proposed 1:2.5+dfsg-5ubuntu10.26 amd64 [upgradable from: 1:2.5+dfsg-5ubuntu10.25] qemu-utils/xenial-proposed 1:2.5+dfsg-5ubuntu10.26 amd64 [upgradable from: 1:2.5+dfsg-5ubuntu10.25] $ qemu-system-x86_64 -enable-kvm -vnc unix:/tmp/service/../service/../service/../service/vnc-sock # Staying alive on socat and the socat gets the Ref as it should: $ socat - UNIX:/tmp/service/vnc-sock RFB 003.008 Per the above, verified. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705743 Title: qemu-system-x86 crashes when VNC connection is established To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1705743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384532] Re: Unable to set AppArmor profile [...] no such file or directory
Hi, sorry for chiming in so late, but I haven't seen this issue before - the last update changed that. Special chars as reported in comment #26 and comment #15 are an issue, but most of them are fixed or at a better error message now. First of all since Ubuntu 17.10 (~=UCA-Pike) all files in generated rules are in quotes which formerly they were not - that allows for some chars like spaces. Further some other chars are just plain forbidden and would break the rule - these are mostly apparmor wilcards so these are now rejected since v3.10.0 by a150b86c instead of later failing when loading the profile. That said it is hard for me to track details of the old issue, but with a recent Ubuntu this should be all fixed. With space a rule will now look as: "/var/lib/uvtool/libvirt/images/a space does not hurt.qcow" rwk, and work just fine. But the actual issue - at least with tolerable special chars is fixed in the latter releases. And the apparmor wildcards do not randomly fail, or work or be a security issue - instead they always fail now. I have to admit the message is still the old misleading one in the remaining failing cases. I spawned bug 1767934 for this - but at low prio. Per above I'd set the bug fix releases at least for the latter releases. Given the long time this bug slumbers before a person is hit by it again and the fact that a simple file rename gets you around makes me not think of SRUs for this atm. So I'll set won't fix for pre-Artful, but hey - discussions welcome. ** Changed in: libvirt (Ubuntu) Status: Confirmed => Fix Released ** Also affects: libvirt (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Bionic) Importance: High Status: Fix Released ** Also affects: libvirt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu Artful) Status: New => Fix Released ** Changed in: libvirt (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: libvirt (Ubuntu Bionic) Importance: High => Medium ** Changed in: libvirt (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: libvirt (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384532 Title: Unable to set AppArmor profile [...] no such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767934] [NEW] breaking the apparmor profile leads to misleading error messages
Public bug reported: Certain cases are mis-debugged for quite a while and users are confused on a bad apparmor profile (for a guest) being reporte as: error: internal error: Process exited prior to exec: libvirt: error : unable to set AppArmor profile 'libvirt-5a0e5825-717b-4edb-857a- b7bab2f7083a' for '/usr/bin/kvm-spice': No such file or directory To reproduce use a forbidden char, so any of the bad chars [1] in e.g. a file name of an image. Then start the domain. The error should be more descriptive to what failed. [1]: https://libvirt.org/git/?p=libvirt.git;a=blobdiff;f=src/security /virt-aa- helper.c;h=07ece730e27d2be4be92adcabb54d788825659f0;hp=ee3913d66ac3a867bae6af71609ebcd25dd25ae2;hb=a150b86c4c3afc82e2d2f591ae19328b1c81bf7e;hpb=a50b45a2971a4c70f005a8e8821ea7a794e87e7b ** Affects: libvirt (Ubuntu) Importance: Low Status: Triaged ** Tags: libvirt-18.10 ** Changed in: libvirt (Ubuntu) Status: New => Triaged ** Changed in: libvirt (Ubuntu) Importance: Undecided => Low ** Tags added: libvirt-18.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767934 Title: breaking the apparmor profile leads to misleading error messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1767934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758037] Re: LTC Test- Ubuntu18.04: Starting the guest with network filter defined will fail with "cause is unknown".
Ok, together we found a fix for this which now is integrated upstream. commit ce5aebeacd10a1c15cb3ee46a59c8b5ff235589e Author: Laine Stump Date: Wed Apr 25 17:12:03 2018 -0400 nwfilter: increase pcap buffer size to be compatible with TPACKET_V3 Bionic+1 is not yet open, so atm it is a bit complex for a few days to push fixes. Furthermore since this never worked I'm not quite sure we want/need to SRU it back to all releases - at least it can't be urgent IMHO. I'd ask for the reporters opinion for it, my plan would be to: 1. wait until 18.10 release opened the Archive 2. fix in 18.10 3. SRU to 18.04, 17.10, 16.04 Would that be ok for you? ** Changed in: libvirt (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758037 Title: LTC Test- Ubuntu18.04: Starting the guest with network filter defined will fail with "cause is unknown". To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1758037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767283] Re: nc doesn't support "-s IP" option
Fix is now available in [1]. But needs to be picked up for 18.10 (once archive is open in a few days) and then prepped as 18.04 SRU. [1]: https://salsa.debian.org/debian/netcat- openbsd/commit/338b1fa7c3db9bd791095f51325b3287330dac7d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767283 Title: nc doesn't support "-s IP" option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767283] Re: nc doesn't support "-s IP" option
Debian bug at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897020 ** Bug watch added: Debian Bug tracker #897020 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897020 ** Also affects: netcat-openbsd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897020 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767283 Title: nc doesn't support "-s IP" option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767283] Re: nc doesn't support "-s IP" option
I'm not an expert on netcat but I hope this initial triage helps the next that will look at it. I reported to Debian as well as they are also affected. Especially since the change came from Guilhem - it might be best to think about a solution together. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767283 Title: nc doesn't support "-s IP" option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767283] Re: nc doesn't support "-s IP" option
In gdb I see it gets to read -s
case 's':
sflag = optarg;
break;
It realizes no more options are there and then ends at
} else if (argv[0] && argv[1]) {
host = argv[0];
uport = &argv[1];
if (pflag || sflag)
usage(1);
And sflag is set, so it reports usage and exits.
The particular check in this path of pflag/sflag didn't exist back then.
I found this comes in via a patch
debian/patches/misc-failures-and-features.patch
That was in Debian and Ubuntu since late 2016
This patch was modified by:
commit 2ebffb014c830e49f6fad600c59cc1b82fe356a4
Author: Guilhem Moulin
Date: Sun Dec 3 22:58:11 2017 +0100
Allow usage of -s with -l for consistency with netcat-traditional.
Since then this is also in Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767283
Title:
nc doesn't support "-s IP" option
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767283] Re: nc doesn't support "-s IP" option
Even the example from the manpage fails: $ nc -s 10.1.2.3 host.example.com 42 ** Changed in: netcat-openbsd (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/1767283 Title: nc doesn't support "-s IP" option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767283] Re: nc doesn't support "-s IP" option
-t in description (typo) mislead me - fixed the description ** Description changed: Hey, - netcat shows a usage error if i try to use the "-t" option: + netcat shows a usage error if i try to use the "-s" option: Example in Bionic: - $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null + $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl] - [-m minttl] [-O length] [-P proxy_username] [-p source_port] - [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w timeout] - [-X proxy_protocol] [-x proxy_address[:port]] [destination] [port] - + [-m minttl] [-O length] [-P proxy_username] [-p source_port] + [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w timeout] + [-X proxy_protocol] [-x proxy_address[:port]][destination] [port] Example in Xenial: - netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null + netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4 - - Manpage shows that the option is still availible and should work. Both systems use openbsd netcat. + Manpage shows that the option is still availible and should work. Both + systems use openbsd netcat. $ type netcat netcat is hashed (/bin/netcat) - $ ls -lah /bin/netcat + $ ls -lah /bin/netcat lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat $ ls -lah /etc/alternatives/netcat lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> /bin/nc.openbsd ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: netcat-openbsd 1.187-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri Apr 27 13:41:20 2018 Dependencies: - gcc-8-base 8-20180414-1ubuntu2 - libbsd0 0.8.7-1 - libc6 2.27-3ubuntu1 - libgcc1 1:8-20180414-1ubuntu2 + gcc-8-base 8-20180414-1ubuntu2 + libbsd0 0.8.7-1 + libc6 2.27-3ubuntu1 + libgcc1 1:8-20180414-1ubuntu2 ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: netcat-openbsd UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767283 Title: nc doesn't support "-s IP" option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767085] Re: package mysql-server-5.7 5.7.22-0ubuntu0.16.04.1 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 1
Hi Fi, Thank you for taking the time to report this bug and helping to make Ubuntu better. On upgrading a service this service has to be restarted to pick up the fixes. Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration. But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state. Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart. Therefore the update of that package has to consider itself incomplete. Depending on your particular case there are two solutions: - either remove the offending package if you don't want to continue using it. - Or if you do want to keep it please fix the configuration so that re-starting the service will work. >From your logs I see: 2018-04-26T08:23:00.237766Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 2018-04-26T08:23:00.237807Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2018-04-26T08:23:00.237830Z 0 [Note] InnoDB: Unable to open the first data file 2018-04-26T08:23:00.237850Z 0 [ERROR] InnoDB: Operating system error number 11 in a file operation. 2018-04-26T08:23:00.237865Z 0 [ERROR] InnoDB: Error number 11 means 'Resource temporarily unavailable' 2018-04-26T08:23:00.237875Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html 2018-04-26T08:23:00.237887Z 0 [ERROR] InnoDB: Cannot open datafile './ibdata1' 2018-04-26T08:23:00.237898Z 0 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data! 2018-04-26T08:23:00.237909Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Cannot open a file So in your case the restart after upgrade fails, due to these issues. That might indicate the DB wasn't shut down cleanly and the lock still is on the file OR that another mysql service is running at the same time having it already locked. If you have no resonable data in your mysql anyway the quickest might just to reinstall it like [1]. Otherwise you might want to look which process has the file open and resolve that as in [2] Setting to incomplete as it appears to be more a misconfig or support request than a bug in ubuntu for now, but I'll subscribe myself to see what you find following the above. [1]: https://askubuntu.com/questions/341943/how-to-uninstal-mysql-5-6-and-reinstall-5-5/428515 [2]: https://serverfault.com/questions/477448/mysql-keeps-crashing-innodb-unable-to-lock-ibdata1-error-11 ** Changed in: mysql-5.7 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767085 Title: package mysql-server-5.7 5.7.22-0ubuntu0.16.04.1 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1767085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
