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 Yahoo!
Engineering Team, which is subscribed to cloud-init.
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
Public bug reported:
With Ussuri I'm hitting this in the neutron server:
2020-06-15 14:41:44.209 21931 ERROR neutron.plugins.ml2.managers
[req-6160aa90-b69e-451b-9774-07b6d840f41f 088d04a2122548c5acb628348db93c40
11447be9beda4bf78dab27cdb75058e2 - default default] Mechanism driver 'calico'
Public bug reported:
This merge -
https://opendev.org/openstack/neutron/commit/a6fb2faaa5d46656db9085ad6bcfc65ded807871
- to the Neutron stable/rocky branch on April 23rd, has broken my team's
Neutron plugin, by requiring 3rd party LinuxInterfaceDriver subclasses
to take a new 'link_up' argument
I don't see value in this for networking-calico.
** No longer affects: networking-calico
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1082248
Title:
Use uuidutils instead of
programs iptables with these 'duplicates'
removed, and thereby breaks Calico's iptables.
** Affects: neutron
Importance: Undecided
Assignee: Neil Jerram (neil-jerram)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Tea
The corresponding Neutron agent code is also still using dhcp_domain in
stable/newton and current master.
** Summary changed:
- Calico DHCP agent should use DEFAULT/dns_domain instead of DEFAULT/dhcp_domain
+ DHCP agent should use DEFAULT/dns_domain instead of DEFAULT/dhcp_domain
** Project
If I understand correctly, this is not an independent bug. Rather, it
only arises when changes are made in networking-calico to address
another bug (1541490). And the only proposed change for _this_ bug is
now also in networking-calico.
Therefore it doesn't make sense for this bug to have an
Public bug reported:
Please could you tag and release networking-calico, as it currently
stands at:
https://git.openstack.org/cgit/openstack/networking-calico
neil@nj-ubuntu:~/calico/networking-calico$ git log -1
commit 792f1cf63e63ce4660f837d261e9c2bb66434f7b
Author: Neil Jerram <neil.
Public bug reported:
This is a problem I'm seeing in a 3 node DevStack system, stacked today
(14th October 2015). I click on Hypervisors in the System section of
the Horizon UI, to see hypervisor information. Horizon shows an error
box "Unable to retrieve hypervisor information".
the current Neutron API), and it will be a
major help to both them and us if it is possible, as of the Liberty
release, to do this with a vanilla Neutron release.
** Affects: neutron
Importance: Undecided
Assignee: Neil Jerram (neil-jerram)
Status: New
** Tags: rfe
** Changed
Public bug reported:
This RFE bug describes and proposes a type of Neutron network in
which connectivity between the VMs attached to that network is
provided by L3 routing. This type of network provides full (subject
to security policy) IP connectivity between VMs in that and other
routed
12 matches
Mail list logo
