[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial
This issue happens to us because libvirt is being used inside a Docker container which share systemd with the host. Therefore, neither of these units exist on the host and as mentioned above, when a non-existing unit is specified in the `After` clause - listed first - the `Before` clause makes systemd fail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529079 Title: Can't start virtual machines with installed systemd-container package on Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial
Just created an issue on libvirt's upstream bug tracker: https://bugzilla.redhat.com/show_bug.cgi?id=1350909 ** Bug watch added: Red Hat Bugzilla #1350909 https://bugzilla.redhat.com/show_bug.cgi?id=1350909 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529079 Title: Can't start virtual machines with installed systemd-container package on Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial
We do experience that issue too on CoreOS. Until CoreOS 1010, it worked just fine (systemd v225), and afterwards (systemd v229), the issue is present. The libvirt code mentioned above did not change since 2014. Therefore, it seems that a change to systemd between 225 and 229 generates that issue. Not sure of the importance of that `Before` close there yet. I need to document myself more. We could try without it and see how it goes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529079 Title: Can't start virtual machines with installed systemd-container package on Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial
I do experience it too in CoreOS+CentOS (docker). Question is why is it a problem now? These lines have been present there since 2014. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529079 Title: Can't start virtual machines with installed systemd-container package on Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 856764] Re: RabbitMQ connections lack heartbeat or TCP keepalives
Any way to have this fixed in Juno too ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/856764 Title: RabbitMQ connections lack heartbeat or TCP keepalives To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/856764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1411564] Re: neutron-vpn-agent should wait for ipsec to start on boot
Actually, for an unknown reason, no environment is created on my end. There is no /var/lib/neutron/ipsec folder. When created manually with the right permissions, the folder remains empty. There is absolutely nothing in /var/log/neutron/vpn_agent.log (Debug/Verbose = True) except the error shown by James. Syslog is blank too. The ipsec service was already started when I started neutron-vpn-agent. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1411564 Title: neutron-vpn-agent should wait for ipsec to start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1411564/+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 1411564] Re: neutron-vpn-agent should wait for ipsec to start on boot
Actually, for an unknown reason, no environment is created on my end. There is no /var/lib/neutron/ipsec folder. When created manually with the right permissions, the folder remains empty. There is absolutely nothing in /var/log/neutron/vpn_agent.log (Debug/Verbose = True) except the error shown by James. Syslog is blank too. The ipsec service was already started when I started neutron-vpn-agent. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1411564 Title: neutron-vpn-agent should wait for ipsec to start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1411564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
