Public bug reported:
when uploading same package with different package id then VNF
termination is failing for VNF which was onboarded with first vnf
package
navum_public@instance-vnfm-2nd-20210413:~$ openstack vnf package create
Reviewed: https://review.opendev.org/c/openstack/neutron/+/790352
Committed:
https://opendev.org/openstack/neutron/commit/f192153b449877e00c57c2b2a1b8ce89c9c733da
Submitter: "Zuul (22348)"
Branch:master
commit f192153b449877e00c57c2b2a1b8ce89c9c733da
Author: yangjianfeng
Date: Sun May 9
Public bug reported:
I believe that patch
https://review.opendev.org/c/openstack/neutron/+/789255 might have
broken some functionality, eg. this happens:
http://paste.openstack.org/show/805541/
** Affects: neutron
Importance: Undecided
Status: New
** Tags: ovn
--
You received
Reviewed: https://review.opendev.org/c/openstack/neutron/+/791492
Committed:
https://opendev.org/openstack/neutron/commit/7b59b5069b1402730602b430416a15b1609253ea
Submitter: "Zuul (22348)"
Branch:master
commit 7b59b5069b1402730602b430416a15b1609253ea
Author: Slawek Kaplonski
Date: Fri
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1928794
Title:
[OVN] DHCP agent fails to update network
Status in neutron:
Public bug reported:
Since [1], the VLAN segment allocation using
"get_random_unallocated_segment" does not enforce a priority in the
physical network selection, depending on the configuration order. All
available physical network segments can be selected randomly; that means
any physical network
Reviewed: https://review.opendev.org/c/openstack/manila/+/792303
Committed:
https://opendev.org/openstack/manila/commit/6ace54c2601770a0e06418ce5b98c756c86f6a51
Submitter: "Zuul (22348)"
Branch:master
commit 6ace54c2601770a0e06418ce5b98c756c86f6a51
Author: Goutham Pacha Ravi
Date: Wed
7 matches
Mail list logo