pylxd cannot start containers with LXD 2.0.11
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
Undecided
|
Unassigned | ||
Newton |
Fix Released
|
Critical
|
James Page | ||
Ocata |
Fix Released
|
Critical
|
James Page | ||
python-pylxd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Critical
|
Colin Watson |
Bug Description
The LXD 2.0.11 SRU in xenial broke pylxd and hence broke Launchpad builds, as visible here:
https:/
/usr/
key, self.__
/usr/
key, self.__
Traceback (most recent call last):
File "/usr/share/
sys.
File "/usr/share/
return args.operation.
File "/usr/lib/
self.
File "/usr/lib/
container
File "/usr/lib/
wait=wait)
File "/usr/lib/
self.sync()
File "/usr/lib/
setattr(self, key, val)
File "/usr/lib/
return super(Model, self)._
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:/
[Test Case]
>>> from pylxd import Client
>>> client = Client()
>>> container = client.
>>> container.
[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.
Changed in python-pylxd (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Critical |
assignee: | nobody → Colin Watson (cjwatson) |
Changed in cloud-archive: | |
status: | New → Fix Released |
tags: |
added: verification-newton-done verification-ocata-done removed: verification-newton-needed verification-ocata-needed |
Hello Colin, or anyone else affected,
Accepted python-pylxd into xenial-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ python- pylxd/2. 0.5-0ubuntu1. 2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification- needed- xenial to verification- done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- xenial. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!