Thanks to everyone who contributed to this fix. I confirm that it works
for me in testing with Ussuri and Ubuntu Bionic on vmx-enabled GCP VMs;
with fixed qemu packages coming from cloud-archive:ussuri.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I don't believe this is to do with networking-calico, so will mark as
Invalid for networking-calico.
** Changed in: networking-calico
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Python 3 support was added in Calico v3.15
https://docs.projectcalico.org/release-notes/#v3150
The master networking-calico code now supports Python 3, and no longer
Python 2. There is a 'release-v3.15-python2' branch that still supports
Python 2, but we are hoping that maintenance of that branch
Christian, would it be easy for you to build this for Bionic as well? I
run tests with GCP instances as the OpenStack hypervisors, and have hit
this bug, so am keen to test your fix.
(http://lists.openstack.org/pipermail/openstack-
discuss/2020-June/015343.html)
--
You received this bug
Thanks Bence. FYI, in Neutron I believe
https://review.opendev.org/#/c/691874/ has already broken Python 2, so
the ship has now sailed for almost all new OpenStack deployments
(excepting any that are Swift-only, or still using nova-net if that is
possible).
--
You received this bug notification
Vasili, I completely agree with you, and I am trying to schedule time
for the work needed for it. BTW, you can see the work that I have
started, at https://github.com/neiljerram/networking-calico/commits/ci-
fixups. (The next class of problems is where the test code expects
normal strings and
I would guess that this is because pylint.el includes:
(require 'tramp)
and that this is more a problem with Tramp startup, than with pylint.
I've had slow Tramp startup problems in other contexts unrelated to
python.
Possibly relevant references:
@Christian: what does the default /etc/qemu-ifup do?
Although I'm inclined to accept your argument that my recent change to
Nova was a step in the wrong direction, I'm wondering why it seems to
work (at least in my testing) in practice.
Also, if there was now a change in libvirt to interpret ''
Thanks. After upgrading just the Ubuntu virtualbox packages to 5.0.18
-dfsg-2build1, and rebooting: X starts up. Only wrinkle is that display
is not resized (to my monitor) when showing the lightdm login screen.
The display _is_ resized correctly when I log in and my normal X session
starts.
--
I see that that version is now available, so happy in principle to try
this. Do I at the same time need to upgrade my Virtualbox install (on
Windows) to 5.0.18?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I run Ubuntu Xenial as a virtualbox guest on a Windows 10 host. This
morning, after rebooting the guest, I found that X was failing to start
up. (Rebooted several times to confirm this.) I reviewed the packages
that changed yesterday and found that they included upgrading
11 matches
Mail list logo
