[Touch-packages] [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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1529079
Title:
Can't start virtual machines with installed systemd-container package
on Xenial
Status in libvirt package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
Invalid
Bug description:
Can't start virtual machines after upgrade to Xenial.
On Ubuntu Server 16.04:
# virsh start testserver
Cannot set property Before, or unknown property.
On Kubuntu 16.04:
Cannot set property Before, or unknown property.
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in
do_install
guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: Cannot set property Before, or unknown property.
At this moment there is no libvirt or systemd-related error messages in
syslog when this error appear on the screen (or virsh output). Both systems was
upgraded from 15.10.
---
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 16.04
Package: libvirt (not installed)
ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial
quiet nomdmonddf nomdmonisw
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=C
SHELL=/bin/bash
Tags: xenial
Uname: Linux 4.3.3-040303-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
mtime.conffile..etc.libvirt.qemu.networks.default.xml:
2015-02-27T11:49:59.773560
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1529079
Title:
Can't start virtual machines with installed systemd-container package
on Xenial
Status in libvirt package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
Invalid
Bug description:
Can't start virtual machines after upgrade to Xenial.
On Ubuntu Server 16.04:
# virsh start testserver
Cannot set property Before, or unknown property.
On Kubuntu 16.04:
Cannot set property Before, or unknown property.
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in
do_install
guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: Cannot set property Before, or unknown property.
At this moment there is no libvirt or systemd-related error messages in
syslog when this error appear on the screen (or virsh output). Both systems was
upgraded from 15.10.
---
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 16.04
Package: libvirt (not installed)
ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial
quiet nomdmonddf nomdmonisw
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=C
SHELL=/bin/bash
Tags: xenial
Uname: Linux 4.3.3-040303-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
mtime.conffile..etc.libvirt.qemu.networks.default.xml:
2015-02-27T11:49:59.773560
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1529079
Title:
Can't start virtual machines with installed systemd-container package
on Xenial
Status in libvirt package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
Invalid
Bug description:
Can't start virtual machines after upgrade to Xenial.
On Ubuntu Server 16.04:
# virsh start testserver
Cannot set property Before, or unknown property.
On Kubuntu 16.04:
Cannot set property Before, or unknown property.
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in
do_install
guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: Cannot set property Before, or unknown property.
At this moment there is no libvirt or systemd-related error messages in
syslog when this error appear on the screen (or virsh output). Both systems was
upgraded from 15.10.
---
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 16.04
Package: libvirt (not installed)
ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial
quiet nomdmonddf nomdmonisw
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=C
SHELL=/bin/bash
Tags: xenial
Uname: Linux 4.3.3-040303-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
mtime.conffile..etc.libvirt.qemu.networks.default.xml:
2015-02-27T11:49:59.773560
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1529079
Title:
Can't start virtual machines with installed systemd-container package
on Xenial
Status in libvirt package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
Invalid
Bug description:
Can't start virtual machines after upgrade to Xenial.
On Ubuntu Server 16.04:
# virsh start testserver
Cannot set property Before, or unknown property.
On Kubuntu 16.04:
Cannot set property Before, or unknown property.
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in
do_install
guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: Cannot set property Before, or unknown property.
At this moment there is no libvirt or systemd-related error messages in
syslog when this error appear on the screen (or virsh output). Both systems was
upgraded from 15.10.
---
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 16.04
Package: libvirt (not installed)
ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial
quiet nomdmonddf nomdmonisw
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=C
SHELL=/bin/bash
Tags: xenial
Uname: Linux 4.3.3-040303-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
mtime.conffile..etc.libvirt.qemu.networks.default.xml:
2015-02-27T11:49:59.773560
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
