[Bug 1965523] Re: Server Team Backports PPA: latest upgrades to libvirt shuts down domains without restarting them
I can confirm that the upgrade now works as anticipated with VMs staying up, thanks for the quick turnaround! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965523 Title: Server Team Backports PPA: latest upgrades to libvirt shuts down domains without restarting them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1965523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965523] Re: Server Team Backports PPA: latest upgrades to libvirt shuts down domains without restarting them
I got some coffee in me and narrowed down the problem: the postinst file in libvirt-daemon-system was changed from just starting libvirt- guests.service to restarting libvirt-guests.service. libvirt- guests.service now shuts down all VMs but the autostart mechanism of libvirtd doesn't kick in because it was only a service restart, not a system restart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965523 Title: Server Team Backports PPA: latest upgrades to libvirt shuts down domains without restarting them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1965523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965523] Re: Server Team Backports PPA: latest upgrades to libvirt shuts down domains without restarting them
I should add that I believe this actually started happening with 7.6.0, package: 0ubuntu1.1~backport20.04-202203140809~ubuntu20.04.1 but I initially thought it was a one-off problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965523 Title: Server Team Backports PPA: latest upgrades to libvirt shuts down domains without restarting them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1965523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965523] [NEW] Server Team Backports PPA: latest upgrades to libvirt shuts down domains without restarting them
Public bug reported: My focal host recently patched itself to the newest libvirt version available in the Server Team Backports PPA (https://launchpad.net/~canonical-server/+archive/ubuntu/server- backports) which caused all my domains to shutdown and **not** restart despite being marked for autostart. # lsb_release -rd Description:Ubuntu 20.04.4 LTS Release:20.04 Excerpt from my /var/log/apt/history.log Start-Date: 2022-03-18 07:02:13 Commandline: /usr/bin/unattended-upgrade Upgrade: libvirt-daemon-system-systemd:amd64 (7.6.0-0ubuntu1.1~backport20.04-202203140809~ubuntu20.04.1, 7.6.0-0ubuntu1.1~backport20.04-202203171551~ubuntu20.04.1), libvirt-daemon-config-network:amd64 (7.6.0-0ubuntu1.1~backport20.04-202203140809~ubuntu20.04.1, 7.6.0-0ubuntu1.1~backport20.04-202203171551~ubuntu20.04.1), libvirt-clients:amd64 (7.6.0-0ubuntu1.1~backport20.04-202203140809~ubuntu20.04.1, 7.6.0-0ubuntu1.1~backport20.04-202203171551~ubuntu20.04.1), libvirt-daemon-driver-storage-rbd:amd64 (7.6.0-0ubuntu1.1~backport20.04-202203140809~ubuntu20.04.1, 7.6.0-0ubuntu1.1~backport20.04-202203171551~ubuntu20.04.1), libvirt-daemon-driver-qemu:amd64 (7.6.0-0ubuntu1.1~backport20.04-202203140809~ubuntu20.04.1, 7.6.0-0ubuntu1.1~backport20.04-202203171551~ubuntu20.04.1), libvirt-daemon-system:amd64 (7.6.0-0ubuntu1.1~backport20.04-202203140809~ubuntu20.04.1, 7.6.0-0ubuntu1.1~backport20.04-202203171551~ubuntu20.04.1), libvirt0:amd64 (7.6.0-0ubuntu1.1~backport20.04-202203140809~ubuntu20.04.1, 7.6.0-0ubuntu1.1~backport20.04-202203171551~ubuntu20.04.1), libvirt-daemon-config-nwfilter:amd64 (7.6.0-0ubuntu1.1~backport20.04-202203140809~ubuntu20.04.1, 7.6.0-0ubuntu1.1~backport20.04-202203171551~ubuntu20.04.1), libvirt-daemon:amd64 (7.6.0-0ubuntu1.1~backport20.04-202203140809~ubuntu20.04.1, 7.6.0-0ubuntu1.1~backport20.04-202203171551~ubuntu20.04.1) End-Date: 2022-03-18 07:02:46 Excerpt from journalctl -u libvirtd: Mar 18 07:02:20 REDACTED systemd[1]: Stopping Virtualization daemon... Mar 18 07:02:20 REDACTED systemd[1]: libvirtd.service: Succeeded. Mar 18 07:02:20 REDACTED systemd[1]: Stopped Virtualization daemon. Mar 18 07:02:20 REDACTED systemd[1]: libvirtd.service: Found left-over process 9913 (virtiofsd) in control group while starting unit. Ignoring. Mar 18 07:02:20 REDACTED systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 18 07:02:20 REDACTED systemd[1]: libvirtd.service: Found left-over process 10299 (virtiofsd) in control group while starting unit. Ignoring. Mar 18 07:02:20 REDACTED systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 18 07:02:20 REDACTED systemd[1]: libvirtd.service: Found left-over process 19444 (virtiofsd) in control group while starting unit. Ignoring. Mar 18 07:02:20 REDACTED systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 18 07:02:20 REDACTED systemd[1]: libvirtd.service: Found left-over process 19917 (virtiofsd) in control group while starting unit. Ignoring. Mar 18 07:02:20 REDACTED systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 18 07:02:20 REDACTED systemd[1]: libvirtd.service: Found left-over process 27108 (virtiofsd) in control group while starting unit. Ignoring. Mar 18 07:02:20 REDACTED systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 18 07:02:20 REDACTED systemd[1]: libvirtd.service: Found left-over process 27660 (virtiofsd) in control group while starting unit. Ignoring. Mar 18 07:02:20 REDACTED systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 18 07:02:20 REDACTED systemd[1]: Starting Virtualization daemon... Mar 18 07:02:20 REDACTED systemd[1]: Started Virtualization daemon. Mar 18 07:02:21 REDACTED systemd[1]: Stopping Virtualization daemon... Mar 18 07:02:24 REDACTED systemd[1]: libvirtd.service: Main process exited, code=dumped, status=11/SEGV Mar 18 07:02:24 REDACTED systemd[1]: libvirtd.service: Failed with result 'core-dump'. Mar 18 07:02:24 REDACTED systemd[1]: Stopped Virtualization daemon. Mar 18 07:02:24 REDACTED systemd[1]: libvirtd.service: Found left-over process 9913 (virtiofsd) in control group while starting unit. Ignoring. Mar 18 07:02:24 REDACTED systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 18 07:02:24 REDACTED systemd[1]: libvirtd.service: Found left-over process 10299 (virtiofsd) in control group while starting unit. Ignoring. Mar 18 07:02:24 REDACTED systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 18 07:02:24 REDACTED systemd[1]: libvirtd.service: Found left-over process 19444
[Bug 1879083] Re: [SRU] default sssd.conf after ipa-client-install crashes sssd
This is still affecting Ubuntu 20.04(.4), would it be possible to get this patch backported to Focal as a SRU? ** Description changed: - Notice + + [Impact] + + Users of FreeIPA on 20.04 currently experience broken SSSD child-service + sockets resulting in systemd labeling the system as degraded. + + Original bug report: + + Notice ipa-client-install creates /etc/sssd/sssd.conf but changes in the sssd process's socket approach calls for that file to change /etc/sssd.conf from ... [sssd] services = nss, pam, ssh, sud ... to [sssd] #services = nss, pam, ssh, sud otherwise the sssd service either won't start or complains. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: freeipa-client 4.8.6-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 16 12:51:21 2020 InstallationDate: Installed on 2020-05-13 (2 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: freeipa UpgradeStatus: No upgrade log present (probably fresh install) + + + [Test Plan] + + Run the unpatched ipa-client-install, reboot the host, and observe + numerous sssd child-service socket errors. + + Once the patch is applied, run the patched ipa-client install, reboot + the host, and ensure there are no sssd-related service failures. + + [Where problems could occur] + The potential problems here are low given that this patch has now been applied for about 17 months. The affected services are currently crashing today so no one is depending on the (broken) present behavior. + + + [Other Info] + + This bug was fixed in groovy at this patch: + https://git.launchpad.net/ubuntu/+source/freeipa/commit/?h=applied/ubuntu/groovy=2711b62a915961c8f76903846953828c2e6c7bb1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879083 Title: [SRU] default sssd.conf after ipa-client-install crashes sssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1879083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879083] Re: [SRU] default sssd.conf after ipa-client-install crashes sssd
** Summary changed: - default sssd.conf after ipa-client-install crashes sssd + [SRU] default sssd.conf after ipa-client-install crashes sssd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879083 Title: [SRU] default sssd.conf after ipa-client-install crashes sssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1879083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887177] Re: [SRU] ovsdb-server.service needs a depedency on local-fs.target
I checked proposed and the amd64 versions finally built. I installed v2.13.1-0ubuntu0.20.04.1, removed my temporary fix, rebooted, and am pleased to report that ovsdb-server is now waiting for ZFS to mount. Manual inspection using "systemctl list-dependencies ovsdb- server.service --after" shows dependencies on the relevant ZFS mounts as well. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887177 Title: [SRU] ovsdb-server.service needs a depedency on local-fs.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1887177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887177] Re: [SRU] ovsdb-server.service needs a depedency on local-fs.target
I'm not entirely sure what happened but it appears the build completely broke on amd64 with a majority of the tests failing. I fear the unrelated minor version bump (2.13.0 to 2.13.1) may have really gotten things in a bad state. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887177 Title: [SRU] ovsdb-server.service needs a depedency on local-fs.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1887177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825755] Re: apt-mirror in all versions (including disco and last from github) doesn't mirror Commands-* files
Just ran into this issue on with a Focal host mirroring Focal repositories with Focal clients. Some searching led me to https://github.com/Stifler6996/apt-mirror which I can confirm works (i.e. fixes cnf, icons, and compression-related problems). I don't know the politics behind how maintainers get chosen but I'm happy to help however I can. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825755 Title: apt-mirror in all versions (including disco and last from github) doesn't mirror Commands-* files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/1825755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892526] Re: dpkg-reconfigure grub-pc no longer prompts for grub-pc/install_devices
I looked through the regression log and the "issue" is due to https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1831789 which added the dis_ucode_ldr flag to GRUB recovery options. This just triggered an obvious change from the expected lines which did not have that option. I tested v2.04-1ubuntu26.4 of grub-common, grub-pc-bin, grub-pc, and grub2-common and can confirm that "dpkg-reconfigure grub-pc" now prompts for the destination hard drives. I also received the same number of "Installing for i386-pc platform" message as the number of hard drives I selected. I think it's fixed! ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892526 Title: dpkg-reconfigure grub-pc no longer prompts for grub-pc/install_devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1892526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887177] Re: ovsdb-server.service needs a depedency on local-fs.target
Is this something that can be released to Focal as a SRU? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887177 Title: ovsdb-server.service needs a depedency on local-fs.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1887177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892526] Re: dpkg-reconfigure grub-pc no longer prompts for grub-pc/install_devices
Is this queued up for a SRU release for Focal? It looks like the right people are involved but I wasn't sure if there was something specific I need to do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892526 Title: dpkg-reconfigure grub-pc no longer prompts for grub-pc/install_devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1892526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893169] [NEW] "pip3 debug" fails due to now-fixed upstream bug
Public bug reported:
In Focal, the command "pip3 debug" fails with the following output:
$ pip3 debug
Traceback (most recent call last):
File "/usr/bin/pip3", line 11, in
load_entry_point('pip==20.0.2', 'console_scripts', 'pip3')()
File "/usr/lib/python3/dist-packages/pip/_internal/cli/main.py", line 73, in
main
command = create_command(cmd_name, isolated=("--isolated" in cmd_args))
File "/usr/lib/python3/dist-packages/pip/_internal/commands/__init__.py",
line 96, in create_command
module = importlib.import_module(module_path)
File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 671, in _load_unlocked
File "", line 783, in exec_module
File "", line 219, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/pip/_internal/commands/debug.py", line
11, in
from pip._vendor.certifi import where
ModuleNotFoundError: No module named 'pip._vendor.certifi'
This appears to be the exact problem that has been fixed upstream in
Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958396
Requested info:
$ lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
$ apt-cache policy python3-pip
python3-pip:
Installed: 20.0.2-5ubuntu1
Candidate: 20.0.2-5ubuntu1
Version table:
*** 20.0.2-5ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status
** Affects: python-pip (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893169
Title:
"pip3 debug" fails due to now-fixed upstream bug
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1893169/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892526] [NEW] dpkg-reconfigure grub-pc no longer prompts for grub-pc/install_devices
Public bug reported: I recently had a RAID-5 disk failure and was greeted by an inoperable grub due to not having installed grub on all the disks. I temporarily fixed this problem by manually running "grub-install" on the other disks in the array and got my system working. Previously it was advised to run "dpkg-reconfigure grub-pc" and select the relevant disks to ensure that future grub updates installed on all the disks in the array. This command no longer prompts for the install disks due to the changed introduced by https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556. In /var/lib/dpkg/info/grub-pc.postinst, the following elif block immediately precedes the elif block that prompts for grub- pc/install_devices and short circuits on all recent grub versions: elif dpkg --compare-versions "$2" ge 2.04-1ubuntu26; then # Avoid the possibility of breaking grub on SRU update # due to ABI change : I can confirm this issue is present on 20.04.1 and it appears to be present on 18.04.4 per https://askubuntu.com/questions/1212569/dpkg- reconfigure-grub-pc-no-option-to-select-boot-device ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892526 Title: dpkg-reconfigure grub-pc no longer prompts for grub-pc/install_devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1892526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887177] [NEW] ovsdb-server.service needs a depedency on local-fs.target
Public bug reported: I recently just did a from-scratch install of Ubuntu 20.04 server edition and ran into issues with Open vSwitch and ZFS. I attempted to use ZFS for all of /var only to find that ovsdb-server pre-empted my ZFS /var mount which caused it to crash when trying to read its configuration DB at/var/lib/openvswitch/conf.db After much troubleshooting, the problem basically boils down to ovsdb- server.service needing a requirement on local-fs.target I then found a blog post on Open Cloud Blog (https://www.opencloudblog.com/?p=240) that contained a fix: The "After" line /lib/systemd/system/ovsdb-server.service needs the following changes: [Unit] Description=Open vSwitch Database Unit After=syslog.target network-pre.target dpdk.service local-fs.target Before=network.target networking.service PartOf=openvswitch-switch.service DefaultDependencies=no [Service] LimitNOFILE=1048576 Type=forking Restart=on-failure EnvironmentFile=-/etc/default/openvswitch ExecStart=/usr/share/openvswitch/scripts/ovs-ctl \ --no-ovs-vswitchd --no-monitor --system-id=random \ start $OPTIONS ExecStop=/usr/share/openvswitch/scripts/ovs-ctl --no-ovs-vswitchd stop ExecReload=/usr/share/openvswitch/scripts/ovs-ctl --no-ovs-vswitchd \ --no-monitor restart $OPTIONS RuntimeDirectory=openvswitch RuntimeDirectoryMode=0755 ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887177 Title: ovsdb-server.service needs a depedency on local-fs.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1887177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802628] Re: winbind name resolution fails when remote host has multiple IPs
I can confirm that this issue still exists in Focal: # apt info winbind Package: winbind Version: 2:4.11.6+dfsg-0ubuntu1.1 $ nmblookup server-without-vbox 192.168.x.y server-without-vbox<00> $ ping -c 1 server-without-vbox PING server-without-vbox(192.168.x.y) 56(84) bytes of data. 64 bytes from 192.168.x.y (192.168.x.y): icmp_seq=1 ttl=64 time=0.612 m $ nmblookup desktop-with-vbox 192.168.x.z desktop-with-vbox<00> 192.168.8.1 desktop-with-vbox<00> $ ping desktop-with-vbox ping: desktop-with-vbox: System error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802628 Title: winbind name resolution fails when remote host has multiple IPs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1802628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802628] [NEW] winbind name resolution fails when remote host has multiple IPs
Public bug reported: Description:Ubuntu 18.04.1 LTS Release:18.04 winbind: Installed: 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 Candidate: 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 Version table: *** 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2:4.7.6+dfsg~ubuntu-0ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages This is essentially a confirmation of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825380 I had the combination of smb and autofs working in Ubuntu 16.04 and then recently upgraded to 18.04. I hadn't checked my back-up logs that used autofs+smb for a while but today noticed that autofs claimed that it could not resolve my Win10 hostname (the remote backup endpoint). I found the above Debian bug report and can confirm that the issue is present in 18.04. Steps to reproduce: # ping abcomputer ping: abcomputer : System error # nmblookup abcomputer 192.168.1.8 abcomputer<00> 192.168.5.1 abcomputer<00> Note the 192.168.5.1 IP is a Virtualbox host-only interface on the Win10 machine. I then remove the host-only interface from the Win10 computer # nmblookup abcomputer 192.168.1.8 abcomputer<00> # ping hyperion PING abcomputer (192.168.1.8) 56(84) bytes of data. 64 bytes from 192.168.1.8 (192.168.1.8): icmp_seq=1 ttl=128 time=0.533 ms ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802628 Title: winbind name resolution fails when remote host has multiple IPs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1802628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1704473] Re: Traceback when using typing.Optional[Type] on xenial
I just ran into this yesterday and was going to submit a bug report. Given that this is a one-line fix, can we get this backported? I'm happy to make the patch file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1704473 Title: Traceback when using typing.Optional[Type] on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.5/+bug/1704473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448254] Re: openvswitch systemd unit file ordering wrong
James, This bug seems to be weird to reproduce. My physical Xenial server worked for months without the proposed patch then last week it suddenly stopped receiving DHCP lease 2 days ago. After much troubleshooting I remembered I was on this bug report, used the proposed patch, and it works like a charm. Without it my server would never try to get a DHCP lease on startup but ifup worked fine once the machine was up. I tried to recreate using a VM but the VM has no such issue; it grabs a DHCP lease without any problems. I don't know if it's some weird race condition or what. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448254 Title: openvswitch systemd unit file ordering wrong To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448254] Re: openvswitch systemd unit file ordering wrong
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448254 Title: openvswitch systemd unit file ordering wrong To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448254] Re: openvswitch systemd unit file ordering wrong
I was one of the people that helped get this fixed in Trusty and now, in a major case of deja vu, hit this same issue now with Xenial. It looks like Mark Dunn's fix above matches http://www.opencloudblog.com/?p=240 and I can confirm it fixed the problem on Xenial. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448254 Title: openvswitch systemd unit file ordering wrong To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1596704] [NEW] Xenial pylint3 version doesn't support Python 3.5 feature set
Public bug reported: Pylint 1.5.2, the version bundled with Xenial, doesn't support the asnycio syntax that was introduced with Python 3.5, which is also bundled in Xenial. This problem was remedied in Pylint 1.5.3 (see https://github.com/PyCQA/pylint/issues/767) and it would be great if Xenial could bump to at least Pylint 1.5.3 to pick up this support. Here's a basic example: async def foo(bar): return bar Running pylint3 gives the following error: E: 2,11: Undefined variable 'bar' (undefined-variable) It's non-intuitive what's going on from this particular error message. ** Affects: pylint (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596704 Title: Xenial pylint3 version doesn't support Python 3.5 feature set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pylint/+bug/1596704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314887] Re: ifupdown hook is missing in upstart script
I can confirm that openvswitch-switch 2.0.2-ubuntu0.14.04.3 fixes the problem on a fully patched Trusty box. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314887 Title: ifupdown hook is missing in upstart script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314887] Re: ifupdown hook is missing in upstart script
I can confirm that openvswitch-switch 2.0.2-ubuntu0.14.04.3 fixes the problem on a fully patched Trusty box. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1314887 Title: ifupdown hook is missing in upstart script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1314887] Re: ifupdown hook is missing in upstart script
[Impact] The documentation included in both upstream Open vSwitch (ovs) 2.0.2 and the version distributed by Ubuntu states that it supports configuring ovs using /etc/network/interfaces (see /usr/share/doc/openvswitch- switch/README.Debian). Moreover, /etc/init.d/openvswitch-switch contains the necessary logic to support parsing /etc/network/interfaces but that logic is completely missing in the Upstart /etc/init /openvswitch-switch.conf script. The result of this issue is a user can properly configure their network in /etc/network/interfaces, test it with ifup/ifdown, reboot, and have no network configured with the machine comes back up. If the user is unaware that Upstart is being used and not classic init.d scripts, a manual call using /etc/init.d/openvswitch-switch works as expected. Without boot integration, users can't easily use Open vSwitch to configure their "main" interface and have a system work on boot. The fix in this thread basically adds support for using the normal config files (/etc/network/interfaces and /etc/network/interfaces.d/*) to configure the network on boot. [Test Case] After running `apt-get install -y openvswitch-switch`, add a stanza to /etc/network/interfaces like the following: allow-ovs br0 iface br0 inet static ovs_type OVSBridge address 172.16.0.1 network 255.255.255.0 Try `ifup br0` and `ifdown br0` and notice how the interface is correctly controlled. Try `/etc/init.d/openvswitch-switch restart` and note how the interface comes up. Reboot the machine and note how br0 is not correctly configured. [Regression Potential] This problem is recognized by the user community (see http://www.opencloudblog.com/?p=240, http://blog.scottlowe.org/2012/08/17/installing-kvm-and-open-vswitch-on- ubuntu/, etc) and people have been manually patching their systems for years to get the desired capability. It's conceivable people's odd ways of fixing this problem could conflict with the potential patch. Double ifup'ing or ifdown'ing an interface shouldn't break any systems but error messages may be emitted. The other unlikely issue is that users have interfaces correctly configured in /etc/network/interfaces and are deliberately depending on the interfaces *not* coming up on boot. This patch would cause these boot-dormant interfaces to come up unexpectedly but, again, I think this problem unlikely. [Other Info] This patch aligns the boot behavior both with what's expected and what the documentation states. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1314887 Title: ifupdown hook is missing in upstart script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1314887] Re: ifupdown hook is missing in upstart script
[Impact] The documentation included in both upstream Open vSwitch (ovs) 2.0.2 and the version distributed by Ubuntu states that it supports configuring ovs using /etc/network/interfaces (see /usr/share/doc/openvswitch- switch/README.Debian). Moreover, /etc/init.d/openvswitch-switch contains the necessary logic to support parsing /etc/network/interfaces but that logic is completely missing in the Upstart /etc/init /openvswitch-switch.conf script. The result of this issue is a user can properly configure their network in /etc/network/interfaces, test it with ifup/ifdown, reboot, and have no network configured with the machine comes back up. If the user is unaware that Upstart is being used and not classic init.d scripts, a manual call using /etc/init.d/openvswitch-switch works as expected. Without boot integration, users can't easily use Open vSwitch to configure their "main" interface and have a system work on boot. The fix in this thread basically adds support for using the normal config files (/etc/network/interfaces and /etc/network/interfaces.d/*) to configure the network on boot. [Test Case] After running `apt-get install -y openvswitch-switch`, add a stanza to /etc/network/interfaces like the following: allow-ovs br0 iface br0 inet static ovs_type OVSBridge address 172.16.0.1 network 255.255.255.0 Try `ifup br0` and `ifdown br0` and notice how the interface is correctly controlled. Try `/etc/init.d/openvswitch-switch restart` and note how the interface comes up. Reboot the machine and note how br0 is not correctly configured. [Regression Potential] This problem is recognized by the user community (see http://www.opencloudblog.com/?p=240, http://blog.scottlowe.org/2012/08/17/installing-kvm-and-open-vswitch-on- ubuntu/, etc) and people have been manually patching their systems for years to get the desired capability. It's conceivable people's odd ways of fixing this problem could conflict with the potential patch. Double ifup'ing or ifdown'ing an interface shouldn't break any systems but error messages may be emitted. The other unlikely issue is that users have interfaces correctly configured in /etc/network/interfaces and are deliberately depending on the interfaces *not* coming up on boot. This patch would cause these boot-dormant interfaces to come up unexpectedly but, again, I think this problem unlikely. [Other Info] This patch aligns the boot behavior both with what's expected and what the documentation states. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314887 Title: ifupdown hook is missing in upstart script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314887] Re: ifupdown hook is missing in upstart script
I realize it's a poor reason but I mimicked the network_interfaces function /etc/init.d/openvswitch-switch. Want me to switch it over to use ifquery? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314887 Title: ifupdown hook is missing in upstart script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314887] Re: ifupdown hook is missing in upstart script
I realize it's a poor reason but I mimicked the network_interfaces function /etc/init.d/openvswitch-switch. Want me to switch it over to use ifquery? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1314887 Title: ifupdown hook is missing in upstart script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1505222] [NEW] strongSwan AppArmor prevents CRL caching
Public bug reported: If configured to do so, strongSwan will cache CRLs to /etc/ipsec.d/crls but AppArmor blocks the creation of the file. Here is the relevant syslog line: kernel: [400994.988829] audit: type=1400 audit(1444649911.842:37): apparmor="DENIED" operation="mknod" profile="/usr/lib/ipsec/charon" name="/etc/ipsec.d/crls/REDACTED.crl" pid=6098 comm="charon" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 Attached is a patch that gives charon r/w access to the /etc/ipsec.d/crls directory. Package info: strongswan: Installed: 5.1.2-0ubuntu2.3 Candidate: 5.1.2-0ubuntu2.3 Ubuntu info: Description:Ubuntu 14.04.3 LTS Release:14.04 ** Affects: strongswan (Ubuntu) Importance: Undecided Status: New ** Patch added: "allow-crl-cache.patch" https://bugs.launchpad.net/bugs/1505222/+attachment/4492434/+files/allow-crl-cache.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to strongswan in Ubuntu. https://bugs.launchpad.net/bugs/1505222 Title: strongSwan AppArmor prevents CRL caching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1505222/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1505222] [NEW] strongSwan AppArmor prevents CRL caching
Public bug reported: If configured to do so, strongSwan will cache CRLs to /etc/ipsec.d/crls but AppArmor blocks the creation of the file. Here is the relevant syslog line: kernel: [400994.988829] audit: type=1400 audit(1444649911.842:37): apparmor="DENIED" operation="mknod" profile="/usr/lib/ipsec/charon" name="/etc/ipsec.d/crls/REDACTED.crl" pid=6098 comm="charon" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 Attached is a patch that gives charon r/w access to the /etc/ipsec.d/crls directory. Package info: strongswan: Installed: 5.1.2-0ubuntu2.3 Candidate: 5.1.2-0ubuntu2.3 Ubuntu info: Description:Ubuntu 14.04.3 LTS Release:14.04 ** Affects: strongswan (Ubuntu) Importance: Undecided Status: New ** Patch added: "allow-crl-cache.patch" https://bugs.launchpad.net/bugs/1505222/+attachment/4492434/+files/allow-crl-cache.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1505222 Title: strongSwan AppArmor prevents CRL caching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1505222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314887] Re: ifupdown hook is missing in upstart script
Went ahead and created a new (and simpler) patch that uses ifquery. See attached ** Patch added: "amended-fix-for-1314887.patch" https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+attachment/4492519/+files/amended-fix-for-1314887.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314887 Title: ifupdown hook is missing in upstart script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314887] Re: ifupdown hook is missing in upstart script
Went ahead and created a new (and simpler) patch that uses ifquery. See attached ** Patch added: "amended-fix-for-1314887.patch" https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+attachment/4492519/+files/amended-fix-for-1314887.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1314887 Title: ifupdown hook is missing in upstart script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1314887] Re: ifupdown hook is missing in upstart script
Following up on my previous comment, the propose fix actually causes the upstart script to fail to start if there are no OVS interfaces present (the ifup errors which I believe causes the pre-start script section to error which then causes upstart to kill the process). I submitted a bit longer fix at https://code.launchpad.net/~brian- turek/ubuntu/trusty/openvswitch/fix-for-1314887/+merge/261912 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1314887 Title: ifupdown hook is missing in upstart script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1314887] Re: ifupdown hook is missing in upstart script
Following up on my previous comment, the propose fix actually causes the upstart script to fail to start if there are no OVS interfaces present (the ifup errors which I believe causes the pre-start script section to error which then causes upstart to kill the process). I submitted a bit longer fix at https://code.launchpad.net/~brian- turek/ubuntu/trusty/openvswitch/fix-for-1314887/+merge/261912 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314887 Title: ifupdown hook is missing in upstart script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314887] Re: ifupdown hook is missing in upstart script
I can confirm this is still present in a fully patched 14.04.2 install and the proposed fix does work. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1314887 Title: ifupdown hook is missing in upstart script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1314887] Re: ifupdown hook is missing in upstart script
I can confirm this is still present in a fully patched 14.04.2 install and the proposed fix does work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314887 Title: ifupdown hook is missing in upstart script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
