Hey Alex, this is now fixed in glance 2:17.0.0-0ubuntu4.
** Changed in: glance (Ubuntu)
Importance: Low => High
** Changed in: glance (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yeah, this is a pain. cosmic-rocky is going to be a 'thing' though for
our OpenStack releases, so this is going to be awkward to fix if
upstream glance won't take the backport to rocky.
Is it possible to change the package to use py3compile with the -V
option: (from the help):
-V VRANGE
python3.7 isn't installed by default on cosmic, however it gets
installed as a result of python3-glance.
py3.7 gets installed indirectly through the dependnecy chain. 'apt
depends --recurse python3-glance' gives more visibility into this.
Notably the following pull in python3.7:
libapache2-mod-ws
This is a confirmed bug on Cosmic. Triaging with low priority since
production Rocky deployments should be using the Rocky cloud archive on
Bionic rather than using Cosmic directly.
** Changed in: glance (Ubuntu)
Status: New => Triaged
** Changed in: glance (Ubuntu)
Importance: Undecide
This patch is proving to be difficult to maintain in the package and the
upstream PR received a -2. I think we need to look into whether we can
disable py3compile of the py3.7 source for cosmic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
So it appears that /usr/bin/py3compile compiles for all available
versions of py3. I've proposed a backport of the glance async fix to
stable/rocky. As a fix, let's carry that patch in the Ubuntu package for
rocky for now until it lands upstream.
--
You received this bug notification because you
stable/rocky upstream PR: https://review.openstack.org/#/c/605709/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794733
Title:
python3-glance (2:17.0.0-0ubuntu3) isn't installing in cosmic
To mana
The async errors can further be recreated by executing:
py3compile -p python3-glance
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794733
Title:
python3-glance (2:17.0.0-0ubuntu3) isn't installing
Contents of /var/lib/dpkg/info/python3-glance.postinst:
https://paste.ubuntu.com/p/ym5m2rVG9r/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794733
Title:
python3-glance (2:17.0.0-0ubuntu3) isn't i
Apologies for not finishing my last sentence above.
Some further debug of the python3-glance.postinst script. Note that
dh_python3 adds the py3compile bits. After updating the postinst script
with 'set -x' and executing it, the async errors are recreated:
sudo sh /var/lib/dpkg/info/python3-glance
I confirmed this on an install of python3-glance on cosmic. It appears
this is a python3.7-only issue as expected, and confirmed below. Cosmic
and Bionic default to python3.6. For some reason the install of
python3-glance in cosmic does
root@c1:~# python3.6
Python 3.6.6+ (default, Sep 1 2018, 01:
I suspect the reason is that 'async' is now a reserved word, and thus
glance can't use it for a module or submodule name.
In fact, we have a bug filed for this:
https://bugs.launchpad.net/glance/+bug/1781617
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
12 matches
Mail list logo
