** Also affects: python-ovsdbapp (Ubuntu)
Importance: Undecided
Status: New
** Also affects: python-ovsdbapp (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/yoga
Comment #58 says "The fix is in Focal and Focal only as that is where the
problem occurs.
As the old bug stated, this doesn't affect later Ubuntu releases." so there is
no need to update the cloud archive (and fwiw to update the Yoga uca you would
first update Jammy but since the Jammy version
** Also affects: horizon (Ubuntu)
Importance: Undecided
Status: New
** Also affects: horizon (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: horizon (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: horizon (Ubuntu Mantic)
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1978489
Title:
libvirt / cgroups v2: cannot boot instance with more than 16 CPUs
** Also affects: octavia
Importance: Undecided
Status: New
** No longer affects: octavia
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/yoga
Importance: Undecided
Status: New
** Also affects: octavia (Ubuntu Jammy)
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/yoga
Importance: Undecided
Status: New
** Also affects: cloud-archive/zed
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Forget to add to ^ that instead of removing the default weight (1024 *
guest.vcpus) might it not have made sense to simply cap it at the max
allowed value? Again, perhaps something that could be proposed to Nova
as a new patch.
--
You received this bug notification because you are a member of
As a recap, this patch addresses the problem of moving vms between hosts
running cgroups v1 (e.g. Ubuntu Focal) and v2 (Ubuntu Jammy) which now
has a cap of 10K [1] for cpu.weight, resulting in vms with > 9 vcpus not
being able to boot if they use the default Nova 1024 * guest.vcpus. The
patch
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: neutron (Ubuntu Jammy)
Both of the patches in the description were backported to 2.13.8 (the
version currently in focal-updates).
** Also affects: openvswitch (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: openvswitch (Ubuntu Focal)
Status: New => Fix Released
** Changed in:
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/antelope
Importance: Undecided
Status: New
** Also affects: cloud-archive/caracal
Importance: Undecided
Status: New
** Also affects: cloud-archive/xena
Importance:
this is releases in all but xena which will be available in the Ubuntu
Cloud Archive in the upcoming 19.0.3 stable release
** Changed in: cloud-archive/xena
Status: Fix Released => New
** Changed in: cloud-archive/yoga
Status: New => Fix Released
** Changed in: neutron (Ubuntu
** Description changed:
The history to this request is as follows; bug 1916024 fixed an issue
that subsequently had to be reverted due to a regression that it
introduced (see bug 1927868) and the original issue can once again
present itself in that keepalived is unable to send GARP on the
Public bug reported:
Sosreports are collecting the systemd journal in two forms which can get
very large i.e. /var/log/journal and sos_commands/logs/journalctl_*. We
would like to disable the sos_commands/logs form since the binary
version is what most/all people use.
** Affects: sosreport
Also, new build of mysql-8.0 soon ready for test -
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971565
Title:
charm
** Also affects: mysql-8.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971565
Title:
charm no longer works with latest mysql-router version
Impish currently has https://bugs.launchpad.net/cloud-
archive/+bug/1962582 in its queue which will need to be released before
the Xena backport (already in unapproved queue for I) can be approves
(and this patch is not yet in an upstream PR hence why an SRU is
needed).
--
You received this bug
Package already released to ussuri uca so marked as Fix Released.
** Changed in: cloud-archive/ussuri
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
While I am aware that not everybody uses the charms to install ceph, I
checked to see how they do this and they are in fact using apt install
to perform an upgrade e.g. the ceph-mon charm does [1] using [2] which I
believe will not behave the same as the "standard" way mentioned in
comment #6 and
I've verified version 4.2-1ubuntu0.20.04.1 from focal-proposed and it
looks good. I generated a sos with 4.1-1ubuntu0.20.04.3 and the newer
version and diffed between them and the contents look sane.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done
** Changed in: cloud-archive/ussuri
Status: Triaged => Fix Released
** Changed in: cloud-archive/victoria
Status: Triaged => Fix Released
** Changed in: cloud-archive/wallaby
Status: Triaged => Fix Released
** Changed in: nova (Ubuntu Focal)
Status: Triaged => Fix
Currently is proposed for focal-updates, victoria and wallaby
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939604
Title:
[SRU] Cannot create 1vcpu instance with multiqueue image, vif_type=tap
bionic-ussuri-proposed verified using [Test Case] and output is:
# apt-cache policy python3-barbican
python3-barbican:
Installed: 1:10.1.0-0ubuntu2~cloud0
Candidate: 1:10.1.0-0ubuntu2~cloud0
Version table:
*** 1:10.1.0-0ubuntu2~cloud0 500
500
Also adding neutron-openvswitch charm since it currently writes the
/etc/default/openvswitch and does not yet support OVS_VSWITCHD_OPTIONS.
** Also affects: charm-neutron-openvswitch
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
/etc/default/openvswitch allows setting OVS_CTL_OPTS but that gets
applies to all daemons. If we want to set ovs-vswitchd specific options
we need a way to pass them through. ovs-ctl [1] has variables like
OVS_VSWITCHD_OPTIONS that get set to '' with no regard for globals so
focal-ussuri-proposed verified using [Test Case] and output is:
# apt-cache policy python3-barbican
python3-barbican:
Installed: 1:10.1.0-0ubuntu2
Candidate: 1:10.1.0-0ubuntu2
Version table:
*** 1:10.1.0-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64
To close the loop somewhat, since fwaas is deprecated in Neutron it has
been removed entirely for Victoria onwards in Ubuntu and the charms now
also have an option to disable it for earlier releases [1].
[1] https://github.com/openstack/charm-neutron-
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/victoria
Importance: Undecided
Status: New
** Also affects: cloud-archive/train
Importance: Undecided
Status: New
** Also affects: cloud-archive/stein
Importance:
** Merge proposal unlinked:
https://code.launchpad.net/~hopem/ubuntu/+source/neutron/+git/neutron/+merge/410049
** Merge proposal linked:
https://code.launchpad.net/~hopem/ubuntu/+source/neutron/+git/neutron/+merge/410648
--
You received this bug notification because you are a member of
** Changed in: ceph (Ubuntu Hirsute)
Status: New => Fix Released
** Changed in: cloud-archive/xena
Status: New => Fix Released
** Changed in: cloud-archive/wallaby
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
We've also found bug 1948656 which means that toggling
explicitly_egress_direct does not remove the flow added when set to
True.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931696
Title:
ovs
@moshele I have re-tested without dvr-snat and these are the results:
(agent_mode=dvr, offload=true, explicitly_egress_direct=False):
switchdev port:
ping between vms same network/separate hypervisors: pass
ping network gateway: fail
ping external address: pass
normal port:
Deployed bionic-victoria with -proposed and looks good to me:
$ juju run -a neutron-api -- dpkg -l| grep fwaas
$ juju run -a neutron-gateway -- dpkg -l| grep fwaas
$ juju run -a neutron-openvswitch -- dpkg -l| grep fwaas
$ juju run -a neutron-api -- dpkg -l| grep neutron-common
ii neutron-common
Deployed bionic-wallaby with -proposed and looks good to me:
$ juju run -a neutron-gateway -- dpkg -l| grep fwaas
$ juju run -a neutron-openvswitch -- dpkg -l| grep fwaas
$ juju run -a neutron-api -- dpkg -l| grep neutron-common
ii neutron-common 2:18.1.1-0ubuntu2~cloud0
Deployed hirsute-wallaby with -proposed and looks good to me:
$ juju run -a neutron-gateway -- dpkg -l| grep fwaas
$ juju run -a neutron-openvswitch -- dpkg -l| grep fwaas
$ juju run -a neutron-api -- dpkg -l| grep neutron-common
ii neutron-common 2:18.1.1-0ubuntu2
** Also affects: cloud-archive/ussuri
Importance: Undecided
Status: New
** Also affects: cloud-archive/victoria
Importance: Undecided
Status: New
** Also affects: barbican (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification
** Description changed:
[Impact]
This SRU corresponds with the following story for upstream barbican
https://storyboard.openstack.org/#!/story/2008335.
The problem is some secrets were stored in plaintext and some were
stored encoded. This resulted in the inability to decode some
@dragon889 thanks for the info. To be clear the patch we are reverting
here is not the patch you reference that introduced
explicitly_egress_direct but actually a subsequent patch that alters
flows for offloaded ports when explicitly_egress_direct=False that
appears to have unintended
** Project changed: maas-deployer => maas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911360
Title:
Nvidia-Graphics-Drivers-460 Causes System To Not Boot
To manage notifications about this bug
** Merge proposal linked:
https://code.launchpad.net/~hopem/ubuntu/+source/neutron/+git/neutron/+merge/410061
** Merge proposal linked:
https://code.launchpad.net/~hopem/ubuntu/+source/neutron/+git/neutron/+merge/410059
** Merge proposal linked:
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/victoria
Importance: Undecided
Status: New
** Also affects: cloud-archive/wallaby
Importance: Undecided
Status: New
** Also affects: cloud-archive/xena
Importance:
ussuri 16.4.1 will be included in https://bugs.launchpad.net/cloud-
archive/+bug/1943712 and victoria 17.2.1 in
https://bugs.launchpad.net/cloud-archive/+bug/1943711
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: cloud-archive/victoria
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915480
Title:
DeviceManager's fill_dhcp_udp_checksums assumes IPv6
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/ussuri
Importance: Undecided
Status: New
** Also affects: cloud-archive/victoria
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu)
Importance:
The neutron package still defines fwaas as a dependency of
neutron-l3-agent which is blocking it from being removed by the charm.
We need to fix that so I will add the package to this bug too.
https://git.launchpad.net/~ubuntu-openstack-
dev/ubuntu/+source/neutron/tree/debian/control#n152
**
There are a set of stable release updates pending which will include
this point release - see bug 1941048
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879798
Title:
designate-manage pool update
@nicolasbock this needs to be SRUd to Focal first before bionic-ussuri
** Changed in: cloud-archive/ussuri
Status: In Progress => New
** Changed in: cloud-archive/ussuri
Assignee: Nicolas Bock (nicolasbock) => (unassigned)
** Changed in: cloud-archive/train
Status: In
Verified rocky-proposed using [Test Plan] with output as follows:
# apt-cache policy nova-common
nova-common:
Installed: 2:18.3.0-0ubuntu1~cloud3
Candidate: 2:18.3.0-0ubuntu1~cloud3
Version table:
*** 2:18.3.0-0ubuntu1~cloud3 500
500 http://ubuntu-cloud.archive.canonical.com/ubuntu
@niedbalski to start the backport sru we will need an updated sru
template in the description of this bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879798
Title:
designate-manage pool update
** Changed in: neutron
Assignee: (unassigned) => Edward Hope-Morley (hopem)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927868
Title:
vRouter not working after update to 16.3.1
To man
@christian-rohmann The problem essentially boils down to the exception
at [1] being raised because prior to that [2] gets called as a result of
a timeout exception but the code is not actually catching the exception.
This was traced to be the result of a privileged call being used as
argument to
Verified bionic-ussuri/proposed using [Test Case]
** Tags removed: verification-ussuri-needed
** Tags added: verification-ussuri-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927868
Title:
managed to get lp branch to upload so deleting the debdiff
** Merge proposal linked:
https://code.launchpad.net/~hopem/ubuntu/+source/horizon/+git/horizon/+merge/406592
** Patch removed: "lp1900851-focal.debdiff"
having issues uploaded my branch of ~ubuntu-openstack-
dev/ubuntu/+source/horizon to lp so using a debdiff for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900851
Title:
[SRU] Cannot Create
** Patch added: "lp1900851-focal.debdiff"
https://bugs.launchpad.net/cloud-archive/ussuri/+bug/1900851/+attachment/5515565/+files/lp1900851-focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+ Fixes python 3.8 compatibility issue with port creation code.
+
+ [Test Plan]
+ * deploy openstack ussuri
+ * create a network port on horizon
+ * ensure creation successful
+
+ [Regression Potential]
+ No unexpected behaviour is anticipated from this
** Changed in: cloud-archive/ussuri
Status: Fix Committed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900851
Title:
Cannot Create Port with Fixed IP Address
To manage
For context this somewhat explains what changes occurred in iputils to
lead to this issue - https://github.com/iputils/iputils/issues/267
** Bug watch added: github.com/iputils/iputils/issues #267
https://github.com/iputils/iputils/issues/267
--
You received this bug notification because you
I just tested arping on Focal and I dont see this issue:
ubuntu@arping:~$ sudo arping -U -I eth0 -c 1 -w 1.5 10.48.98.1
ARPING 10.48.98.1
42 bytes from fe:10:17:12:6a:9c (10.48.98.1): index=0 time=14.516 usec
--- 10.48.98.1 statistics ---
1 packets transmitted, 1 packets received, 0%
Restored the bug description to its original format and updated SRU
info.
** Description changed:
[Impact]
* During periodic task _heal_instance_info_cache the instance_info_caches are
not updated using instance port_ids taken from neutron, but from nova db.
* This causes that existing
Not currently available in an upstream point release prior to Victoria:
$ git branch -r --contains b967e9f706373f1aad6db882c2295fbbe1fadfc9
gerrit/stable/ussuri
$ git tag --contains b967e9f706373f1aad6db882c2295fbbe1fadfc9
$
** Changed in: cloud-archive/victoria
Status: Fix Committed =>
** Tags added: verification-needed-queens
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832021
Title:
Checksum drop of metadata traffic on isolated networks with DPDK
To manage notifications
@coreycb I think we have everything we need to proceed with this SRU
now. Since Queens is the oldest release currently supported on Ubuntu
and support for populating vif attach ordering required to rebuild the
cache has been available since Newton I think the risk of anyone being
impacted is very
I have just re-tested all of this as follows:
* deployed Openstack Train (on Bionic i.e. 2:15.3.3-0ubuntu1~cloud0) with 3
gateway nodes
* created one HA router, one vm with one fip
* can ping fip and confirm single active router
* upgraded neutron-server (api) to 16.3.0-0ubuntu3~cloud0
** Changed in: cloud-archive/xena
Status: New => Fix Released
** Changed in: cloud-archive/wallaby
Status: New => Fix Released
** Changed in: cloud-archive/victoria
Status: New => Fix Released
** Changed in: horizon (Ubuntu Impish)
Status: New => Fix Released
**
** Also affects: cloud-archive/xena
Importance: Undecided
Status: New
** Also affects: cloud-archive/ussuri
Importance: Undecided
Status: New
** Also affects: cloud-archive/victoria
Importance: Undecided
Status: New
** Also affects: cloud-archive/wallaby
I've had a go at deploying Train and upgrading Neutron to latest Ussuri
and I see the same issue. Looking closer what I see is that post-upgrade
Neutron l3-agent has not spawned any keepalived processes hence why no
router goes active. When the agent is restarted it would normally
receive two
This has been released to the ussuri cloud archive (which is currently
on 2:16.3.2-0ubuntu3~cloud0) so marking Fix Released.
** Changed in: cloud-archive/ussuri
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Verified bionic-ussuri-proposed with output:
# apt-cache policy neutron-common
neutron-common:
Installed: 2:16.3.2-0ubuntu3~cloud0
Candidate: 2:16.3.2-0ubuntu3~cloud0
Version table:
*** 2:16.3.2-0ubuntu3~cloud0 500
500 http://ubuntu-cloud.archive.canonical.com/ubuntu
I think the issue here is basically that the new code relies on [1] to
get number of worker threads but that does not include things like rpc
workers.
https://github.com/openstack/neutron/blob/df94641b43964834ba14c69eb4fb17cc45349117/neutron/service.py#L313
--
You received this bug notification
I believe the following bug may also be related -
https://bugs.launchpad.net/neutron/+bug/1927977
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931244
Title:
ovn sriov broken from ussuri onwards
** Changed in: nova/rocky
Status: Fix Committed => New
** Changed in: nova/queens
Status: Fix Committed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892361
Title:
SRIOV
upload to bionic unapproved queue on 11th May -
https://launchpadlibrarian.net/538166201/ceph_12.2.13-0ubuntu0.18.04.8_source.changes
and still awaiting sru team approval.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/queens
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
bionic-ussuri-proposed verified using [Test Plan] and with the following
output:
root@juju-9c4cdb-lp1929832-verify-6:~# apt-cache policy neutron-common
neutron-common:
Installed: 2:16.3.2-0ubuntu2~cloud0
Candidate: 2:16.3.2-0ubuntu2~cloud0
Version table:
*** 2:16.3.2-0ubuntu2~cloud0 500
focal-proposed verified using [Test Plan] and with the following output:
# apt-cache policy neutron-common
neutron-common:
Installed: 2:16.3.2-0ubuntu2
Candidate: 2:16.3.2-0ubuntu2
Version table:
*** 2:16.3.2-0ubuntu2 500
500 http://nova.clouds.archive.ubuntu.com/ubuntu
stable/ussuri backport -
https://review.opendev.org/c/openstack/neutron/+/793417
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929832
Title:
stable/ussuri py38 support for keepalived-state-change
** Changed in: cloud-archive/victoria
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907686
Title:
ovn: instance unable to retrieve metadata
To manage notifications
Since Queens is populating the virtual_interfaces table as standard I
think we should proceed with this SRU -
https://pastebin.ubuntu.com/p/BdCPsVKGk5/ - since it will provide a
clean fix for Queens clouds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: python-cinderclient
Importance: Undecided
Status: New
** No longer affects: python-cinderclient
** Also affects: python-cinderclient
Importance: Undecided
Status: New
** No longer affects: python-cinderclient
** Also affects: charm-cinder
Importance:
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/queens
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
In patch [1] it introduced a binding of DB uniq constraint for L3
agent gateway. In some extreme case the DvrFipGatewayPortAgentBinding
is in DB while the gateway port not. The current code path only checks
the binding existence which will pass a "None" port to the
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/victoria
Importance: Undecided
Status: New
** Also affects: cloud-archive/ussuri
Importance: Undecided
Status: New
** Changed in: cloud-archive/victoria
Status:
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/victoria
Importance: Undecided
Status: New
** Also affects: cloud-archive/ussuri
Importance: Undecided
Status: New
--
You received this bug notification because you are
Hi Pon, if you still need Bionic SRU for this one can you attach a
debdiff for bionic. Thanks.
** Changed in: ceph (Ubuntu Bionic)
Status: In Progress => New
** Changed in: cloud-archive
Assignee: Ponnuvel Palaniyappan (pponnuvel) => (unassigned)
--
You received this bug
All SRU verification completed and performed in
https://bugs.launchpad.net/neutron/+bug/1869808 so please refer to that
LP for the results.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug
All SRU verification completed and performed in
https://bugs.launchpad.net/neutron/+bug/1869808 so please refer to that
LP for the results.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug
All SRU verification completed and performed in
https://bugs.launchpad.net/neutron/+bug/1869808 so please refer to that
LP for the results.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864822
All SRU verification completed and performed in
https://bugs.launchpad.net/neutron/+bug/1869808 so please refer to that
LP for the results.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864822
All SRU verification completed and performed in
https://bugs.launchpad.net/neutron/+bug/1869808 so please refer to that
LP for the results.
** Tags removed: verification-needed verification-needed-bionic
verification-queens-needed verification-rocky-needed
** Tags added: verification-done
All SRU verification completed and performed in
https://bugs.launchpad.net/neutron/+bug/1869808 so please refer to that
LP for the results.
** Tags removed: verification-needed verification-needed-bionic
verification-queens-needed verification-rocky-needed
** Tags added: verification-done
The Victoria and Ussuri backports are released (upstream) as part of
point releases 17.1.1 and 16.3.1 respectively.
** Tags removed: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887405
Verified Bionic Train (uca) using [Test Plan] and the output is as
follows:
https://pastebin.ubuntu.com/p/hHHn6rTwR8/
$ apt-cache policy neutron-common
neutron-common:
Installed: 2:15.3.2-0ubuntu1~cloud1
Candidate: 2:15.3.2-0ubuntu1~cloud1
Version table:
*** 2:15.3.2-0ubuntu1~cloud1 500
Verified Bionic Ussuri using [Test Plan]:
# apt-cache policy neutron-common
neutron-common:
Installed: 2:16.3.0-0ubuntu3~cloud0
Candidate: 2:16.3.0-0ubuntu3~cloud0
Version table:
*** 2:16.3.0-0ubuntu3~cloud0 500
500 http://ubuntu-cloud.archive.canonical.com/ubuntu
Verified Bionic Ussuri (UCA) using [Test Plan] and the output is as
follows:
https://pastebin.ubuntu.com/p/hRmyp6Y6Cc/
$ apt-cache policy neutron-common
neutron-common:
Installed: 2:16.3.0-0ubuntu3~cloud0
Candidate: 2:16.3.0-0ubuntu3~cloud0
Version table:
*** 2:16.3.0-0ubuntu3~cloud0 500
Verified Xenial queens (uca) using [Test Plan] with output as follows:
# apt-cache policy neutron-common
neutron-common:
Installed: 2:12.1.1-0ubuntu4~cloud0
Candidate: 2:12.1.1-0ubuntu4~cloud0
Version table:
*** 2:12.1.1-0ubuntu4~cloud0 500
500
Verified Bionic rocky (uca) using [Test Plan] with output as follows:
# apt-cache policy neutron-common
neutron-common:
Installed: 2:13.0.7-0ubuntu1~cloud3
Candidate: 2:13.0.7-0ubuntu1~cloud3
Version table:
*** 2:13.0.7-0ubuntu1~cloud3 500
500
Verified Bionic queens using [Test Plan] with output as follows:
# apt-cache policy neutron-common
neutron-common:
Installed: 2:12.1.1-0ubuntu4
Candidate: 2:12.1.1-0ubuntu4
Version table:
*** 2:12.1.1-0ubuntu4 500
500 http://nova.clouds.archive.ubuntu.com/ubuntu
Verified Focal Ussuri using [Test Plan]:
# apt-cache policy neutron-common
neutron-common:
Installed: 2:16.3.0-0ubuntu3
Candidate: 2:16.3.0-0ubuntu3
Version table:
*** 2:16.3.0-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
100
Verified Focal Ussuri (UCA) using [Test Plan] and the output is as
follows:
https://pastebin.ubuntu.com/p/Hd2DShbMCX/
# apt-cache policy neutron-common
neutron-common:
Installed: 2:16.3.0-0ubuntu3
Candidate: 2:16.3.0-0ubuntu3
Version table:
*** 2:16.3.0-0ubuntu3 500
500
1 - 100 of 956 matches
Mail list logo
