| 2017-12-05 14:52:03 |
Colin Watson |
bug |
|
|
added bug |
| 2017-12-05 14:54:10 |
Colin Watson |
python-pylxd (Ubuntu): status |
New |
In Progress |
|
| 2017-12-05 14:54:12 |
Colin Watson |
python-pylxd (Ubuntu): importance |
Undecided |
Critical |
|
| 2017-12-05 14:54:14 |
Colin Watson |
python-pylxd (Ubuntu): assignee |
|
Colin Watson (cjwatson) |
|
| 2017-12-05 15:05:01 |
Colin Watson |
description |
The LXD 2.0.11 SRU in xenial broke pylxd and hence broke Launchpad builds, as visible here:
https://launchpadlibrarian.net/348160479/buildlog_snap_ubuntu_xenial_arm64_core_BUILDING.txt.gz
/usr/lib/python2.7/dist-packages/pylxd/model.py:113: UserWarning: Attempted to set unknown attribute "used_by" on instance of "Profile"
key, self.__class__.__name__
/usr/lib/python2.7/dist-packages/pylxd/model.py:113: UserWarning: Attempted to set unknown attribute "description" on instance of "Container"
key, self.__class__.__name__
Traceback (most recent call last):
File "/usr/share/launchpad-buildd/slavebin/in-target", line 27, in <module>
sys.exit(main())
File "/usr/share/launchpad-buildd/slavebin/in-target", line 23, in main
return args.operation.run()
File "/usr/lib/python2.7/dist-packages/lpbuildd/target/lifecycle.py", line 40, in run
self.backend.start()
File "/usr/lib/python2.7/dist-packages/lpbuildd/target/lxd.py", line 380, in start
container.start(wait=True)
File "/usr/lib/python2.7/dist-packages/pylxd/container.py", line 163, in start
wait=wait)
File "/usr/lib/python2.7/dist-packages/pylxd/container.py", line 151, in _set_state
self.sync()
File "/usr/lib/python2.7/dist-packages/pylxd/model.py", line 154, in sync
setattr(self, key, val)
File "/usr/lib/python2.7/dist-packages/pylxd/model.py", line 135, in __setattr__
return super(Model, self).__setattr__(name, value)
AttributeError: 'Container' object has no attribute 'description'
I initially thought this would require reverting LXD, but on inspection it's just adding some new attributes and it's really not its fault that pylxd is unnecessarily strict. This was fixed in pylxd upstream a while ago (https://github.com/lxc/pylxd/pull/234), and the fix is in 2.2.4 so >=artful is already fixed. zesty in principle requires the fix but I can't actually reproduce the bug there, so it's probably best to leave it alone for the time being. However, xenial's pylxd is currently broken.
[Test Case]
>>> from pylxd import Client
>>> client = Client()
>>> client.profiles.get('default') # should produce no warnings
>>> container = client.containers.create({"name": "test", "architecture": "x86_64", "profiles": ["default"], "source": {"type": "image", "mode": "pull", "server": "https://cloud-images.ubuntu.com/releases", "protocol": "simplestreams", "alias": "xenial"}}, wait=True)
>>> container.start(wait=True) # should produce no warnings or exceptions
[Regression Potential]
The fix is to the code that marshals objects between the LXD server and the Python client code, so anything around there could in principle go wrong. I think running launchpad-buildd against it ought to exercise it fairly well. |
The LXD 2.0.11 SRU in xenial broke pylxd and hence broke Launchpad builds, as visible here:
https://launchpadlibrarian.net/348160479/buildlog_snap_ubuntu_xenial_arm64_core_BUILDING.txt.gz
/usr/lib/python2.7/dist-packages/pylxd/model.py:113: UserWarning: Attempted to set unknown attribute "used_by" on instance of "Profile"
key, self.__class__.__name__
/usr/lib/python2.7/dist-packages/pylxd/model.py:113: UserWarning: Attempted to set unknown attribute "description" on instance of "Container"
key, self.__class__.__name__
Traceback (most recent call last):
File "/usr/share/launchpad-buildd/slavebin/in-target", line 27, in <module>
sys.exit(main())
File "/usr/share/launchpad-buildd/slavebin/in-target", line 23, in main
return args.operation.run()
File "/usr/lib/python2.7/dist-packages/lpbuildd/target/lifecycle.py", line 40, in run
self.backend.start()
File "/usr/lib/python2.7/dist-packages/lpbuildd/target/lxd.py", line 380, in start
container.start(wait=True)
File "/usr/lib/python2.7/dist-packages/pylxd/container.py", line 163, in start
wait=wait)
File "/usr/lib/python2.7/dist-packages/pylxd/container.py", line 151, in _set_state
self.sync()
File "/usr/lib/python2.7/dist-packages/pylxd/model.py", line 154, in sync
setattr(self, key, val)
File "/usr/lib/python2.7/dist-packages/pylxd/model.py", line 135, in __setattr__
return super(Model, self).__setattr__(name, value)
AttributeError: 'Container' object has no attribute 'description'
I initially thought this would require reverting LXD, but on inspection it's just adding some new attributes and it's really not its fault that pylxd is unnecessarily strict. This was fixed in pylxd upstream a while ago (https://github.com/lxc/pylxd/pull/234), and the fix is in 2.2.4 so >=artful is already fixed. zesty in principle requires the fix but I can't actually reproduce the bug there, so it's probably best to leave it alone for the time being. However, xenial's pylxd is currently broken.
[Test Case]
>>> from pylxd import Client
>>> client = Client()
>>> container = client.containers.create({"name": "test", "architecture": "x86_64", "profiles": ["default"], "source": {"type": "image", "mode": "pull", "server": "https://cloud-images.ubuntu.com/releases", "protocol": "simplestreams", "alias": "xenial"}}, wait=True)
>>> container.start(wait=True) # should produce no warnings or exceptions
[Regression Potential]
The fix is to the code that marshals objects between the LXD server and the Python client code, so anything around there could in principle go wrong. I think running launchpad-buildd against it ought to exercise it fairly well. |
|
| 2017-12-05 15:06:43 |
Colin Watson |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-12-05 15:06:43 |
Colin Watson |
bug task added |
|
python-pylxd (Ubuntu Xenial) |
|
| 2017-12-05 15:07:00 |
Colin Watson |
python-pylxd (Ubuntu Xenial): status |
New |
In Progress |
|
| 2017-12-05 15:07:02 |
Colin Watson |
python-pylxd (Ubuntu Xenial): importance |
Undecided |
Critical |
|
| 2017-12-05 15:07:05 |
Colin Watson |
python-pylxd (Ubuntu Xenial): assignee |
|
Colin Watson (cjwatson) |
|
| 2017-12-05 15:07:07 |
Colin Watson |
python-pylxd (Ubuntu): status |
In Progress |
Fix Released |
|
| 2017-12-05 15:07:12 |
Colin Watson |
python-pylxd (Ubuntu): importance |
Critical |
Undecided |
|
| 2017-12-05 15:07:14 |
Colin Watson |
python-pylxd (Ubuntu): assignee |
Colin Watson (cjwatson) |
|
|
| 2017-12-05 15:07:47 |
Colin Watson |
attachment added |
|
python-pylxd_2.0.5-0ubuntu1.2.debdiff https://bugs.launchpad.net/ubuntu/+source/python-pylxd/+bug/1736454/+attachment/5018816/+files/python-pylxd_2.0.5-0ubuntu1.2.debdiff |
|
| 2017-12-05 15:45:36 |
Łukasz Zemczak |
python-pylxd (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2017-12-05 15:45:38 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-12-05 15:45:40 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2017-12-05 15:45:43 |
Łukasz Zemczak |
tags |
|
verification-needed verification-needed-xenial |
|
| 2017-12-05 17:52:19 |
Colin Watson |
description |
The LXD 2.0.11 SRU in xenial broke pylxd and hence broke Launchpad builds, as visible here:
https://launchpadlibrarian.net/348160479/buildlog_snap_ubuntu_xenial_arm64_core_BUILDING.txt.gz
/usr/lib/python2.7/dist-packages/pylxd/model.py:113: UserWarning: Attempted to set unknown attribute "used_by" on instance of "Profile"
key, self.__class__.__name__
/usr/lib/python2.7/dist-packages/pylxd/model.py:113: UserWarning: Attempted to set unknown attribute "description" on instance of "Container"
key, self.__class__.__name__
Traceback (most recent call last):
File "/usr/share/launchpad-buildd/slavebin/in-target", line 27, in <module>
sys.exit(main())
File "/usr/share/launchpad-buildd/slavebin/in-target", line 23, in main
return args.operation.run()
File "/usr/lib/python2.7/dist-packages/lpbuildd/target/lifecycle.py", line 40, in run
self.backend.start()
File "/usr/lib/python2.7/dist-packages/lpbuildd/target/lxd.py", line 380, in start
container.start(wait=True)
File "/usr/lib/python2.7/dist-packages/pylxd/container.py", line 163, in start
wait=wait)
File "/usr/lib/python2.7/dist-packages/pylxd/container.py", line 151, in _set_state
self.sync()
File "/usr/lib/python2.7/dist-packages/pylxd/model.py", line 154, in sync
setattr(self, key, val)
File "/usr/lib/python2.7/dist-packages/pylxd/model.py", line 135, in __setattr__
return super(Model, self).__setattr__(name, value)
AttributeError: 'Container' object has no attribute 'description'
I initially thought this would require reverting LXD, but on inspection it's just adding some new attributes and it's really not its fault that pylxd is unnecessarily strict. This was fixed in pylxd upstream a while ago (https://github.com/lxc/pylxd/pull/234), and the fix is in 2.2.4 so >=artful is already fixed. zesty in principle requires the fix but I can't actually reproduce the bug there, so it's probably best to leave it alone for the time being. However, xenial's pylxd is currently broken.
[Test Case]
>>> from pylxd import Client
>>> client = Client()
>>> container = client.containers.create({"name": "test", "architecture": "x86_64", "profiles": ["default"], "source": {"type": "image", "mode": "pull", "server": "https://cloud-images.ubuntu.com/releases", "protocol": "simplestreams", "alias": "xenial"}}, wait=True)
>>> container.start(wait=True) # should produce no warnings or exceptions
[Regression Potential]
The fix is to the code that marshals objects between the LXD server and the Python client code, so anything around there could in principle go wrong. I think running launchpad-buildd against it ought to exercise it fairly well. |
The LXD 2.0.11 SRU in xenial broke pylxd and hence broke Launchpad builds, as visible here:
https://launchpadlibrarian.net/348160479/buildlog_snap_ubuntu_xenial_arm64_core_BUILDING.txt.gz
/usr/lib/python2.7/dist-packages/pylxd/model.py:113: UserWarning: Attempted to set unknown attribute "used_by" on instance of "Profile"
key, self.__class__.__name__
/usr/lib/python2.7/dist-packages/pylxd/model.py:113: UserWarning: Attempted to set unknown attribute "description" on instance of "Container"
key, self.__class__.__name__
Traceback (most recent call last):
File "/usr/share/launchpad-buildd/slavebin/in-target", line 27, in <module>
sys.exit(main())
File "/usr/share/launchpad-buildd/slavebin/in-target", line 23, in main
return args.operation.run()
File "/usr/lib/python2.7/dist-packages/lpbuildd/target/lifecycle.py", line 40, in run
self.backend.start()
File "/usr/lib/python2.7/dist-packages/lpbuildd/target/lxd.py", line 380, in start
container.start(wait=True)
File "/usr/lib/python2.7/dist-packages/pylxd/container.py", line 163, in start
wait=wait)
File "/usr/lib/python2.7/dist-packages/pylxd/container.py", line 151, in _set_state
self.sync()
File "/usr/lib/python2.7/dist-packages/pylxd/model.py", line 154, in sync
setattr(self, key, val)
File "/usr/lib/python2.7/dist-packages/pylxd/model.py", line 135, in __setattr__
return super(Model, self).__setattr__(name, value)
AttributeError: 'Container' object has no attribute 'description'
I initially thought this would require reverting LXD, but on inspection it's just adding some new attributes and it's really not its fault that pylxd is unnecessarily strict. This was fixed in pylxd upstream a while ago (https://github.com/lxc/pylxd/pull/234), and the fix is in 2.2.4 so >=artful is already fixed. zesty in principle requires the fix but I can't actually reproduce the bug there, so it's probably best to leave it alone for the time being. However, xenial's pylxd is currently broken.
[Test Case]
>>> from pylxd import Client
>>> client = Client()
>>> container = client.containers.create({"name": "test", "architecture": "x86_64", "profiles": ["default"], "source": {"type": "image", "mode": "pull", "server": "https://cloud-images.ubuntu.com/releases", "protocol": "simplestreams", "alias": "xenial"}}, wait=True)
>>> container.start(wait=True) # should produce no exceptions
[Regression Potential]
The fix is to the code that marshals objects between the LXD server and the Python client code, so anything around there could in principle go wrong. I think running launchpad-buildd against it ought to exercise it fairly well. |
|
| 2017-12-05 17:52:51 |
Colin Watson |
tags |
verification-needed verification-needed-xenial |
verification-done-xenial |
|
| 2017-12-05 18:18:03 |
Launchpad Janitor |
python-pylxd (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-12-05 18:18:06 |
Stéphane Graber |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-12-07 11:06:03 |
James Page |
bug task added |
|
cloud-archive |
|
| 2017-12-07 11:06:10 |
James Page |
nominated for series |
|
cloud-archive/newton |
|
| 2017-12-07 11:06:10 |
James Page |
bug task added |
|
cloud-archive/newton |
|
| 2017-12-07 11:06:29 |
James Page |
cloud-archive/newton: status |
New |
Triaged |
|
| 2017-12-07 11:06:32 |
James Page |
cloud-archive/newton: importance |
Undecided |
Critical |
|
| 2017-12-07 11:06:35 |
James Page |
cloud-archive: status |
New |
Fix Released |
|
| 2017-12-07 11:07:49 |
James Page |
nominated for series |
|
cloud-archive/ocata |
|
| 2017-12-07 11:07:49 |
James Page |
bug task added |
|
cloud-archive/ocata |
|
| 2017-12-07 11:07:54 |
James Page |
cloud-archive/ocata: status |
New |
Triaged |
|
| 2017-12-07 11:07:56 |
James Page |
cloud-archive/ocata: importance |
Undecided |
Critical |
|
| 2017-12-07 11:14:25 |
James Page |
cloud-archive/newton: assignee |
|
James Page (james-page) |
|
| 2017-12-07 11:14:27 |
James Page |
cloud-archive/ocata: assignee |
|
James Page (james-page) |
|
| 2017-12-07 11:14:29 |
James Page |
cloud-archive/newton: status |
Triaged |
In Progress |
|
| 2017-12-07 11:14:31 |
James Page |
cloud-archive/ocata: status |
Triaged |
In Progress |
|
| 2017-12-07 11:36:15 |
James Page |
cloud-archive/ocata: status |
In Progress |
Fix Committed |
|
| 2017-12-07 11:36:15 |
James Page |
tags |
verification-done-xenial |
verification-done-xenial verification-ocata-needed |
|
| 2017-12-07 11:36:41 |
James Page |
cloud-archive/newton: status |
In Progress |
Fix Committed |
|
| 2017-12-07 11:36:42 |
James Page |
tags |
verification-done-xenial verification-ocata-needed |
verification-done-xenial verification-newton-needed verification-ocata-needed |
|
| 2017-12-07 12:17:57 |
James Page |
tags |
verification-done-xenial verification-newton-needed verification-ocata-needed |
verification-done-xenial verification-newton-done verification-ocata-done |
|
| 2017-12-07 12:27:28 |
James Page |
cloud-archive/newton: status |
Fix Committed |
Fix Released |
|
| 2017-12-07 12:27:32 |
James Page |
cloud-archive/ocata: status |
Fix Committed |
Fix Released |
|
| 2017-12-07 16:22:41 |
James Page |
cloud-archive/ocata: status |
Fix Released |
Fix Committed |
|
| 2017-12-07 16:22:43 |
James Page |
tags |
verification-done-xenial verification-newton-done verification-ocata-done |
verification-done-xenial verification-newton-done verification-ocata-needed |
|
| 2017-12-07 17:10:46 |
James Page |
cloud-archive/ocata: status |
Fix Committed |
Fix Released |
|
