Confirmed. This seems to be a regression in 9.20160110ubuntu0.1. I
couldn't reproduce in a container that I'd already tested 9.20160110.
Perhaps a compiled module got left behind on update? But it does affect
new Xenial containers that have 9.20160110ubuntu0.1 installed fresh (not
upgraded). This impacts server use cases where people deploy new cattle
instead of upgrading pets.
** Tags added: regression-update
** Changed in: lsb (Ubuntu)
Importance: Undecided => Critical
** Changed in: lsb (Ubuntu)
Status: Confirmed => Triaged
** Also affects: lsb (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: lsb (Ubuntu Xenial)
Status: New => Triaged
** Changed in: lsb (Ubuntu Xenial)
Importance: Undecided => Critical
** Changed in: lsb (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596638
Title:
python2 cannot import lsb_release on yakkety and now xenial
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1596638/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
