** Changed in: horizon (Ubuntu Bionic)
Status: New => In Progress
** Changed in: horizon (Ubuntu)
Status: New => In Progress
** Changed in: horizon (Ubuntu Bionic)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
** Changed in: horizon (Ubuntu Cosmic)
** Patch added: "lp1818770_cosmic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1818770/+attachment/5247461/+files/lp1818770_cosmic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
On openstack-dashboard login page(the first pace we face), there is
unexpected graybar on top of the page.
I've been analyzing this page and found below code affects to this
symptom.
body.md-default-theme, body, html.md-default-theme, html {
** Package changed: horizon (Ubuntu) => charm-openstack-dashboard
** Changed in: charm-openstack-dashboard
Assignee: (unassigned) => Seyeong Kim (xtrusia)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://review.openstack.org/#/c/632886/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812148
Title:
openstack-dashboard failed to upgrade with custom theme
To manage notifications about this bug
This issue is happening because there is no 'default' theme in
AVAILABLE_THEME
when custom theme imports default theme's file(scss)
I uploaded patch for this in case someone want to import default theme
rather than creating whole theme seperatly.
** Tags added: sts
--
You received this bug
The same in stsstack
https://pastebin.canonical.com/p/qqXXHRWxfr/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818770
Title:
Unexpected graybar on top of openstack-dashboard login page
To
I verified cosmic for this issue.
apt install openstack-dashboard-common
( apt install openstack-dashboard causes a lot of depenent pkgs)
dpkg -l | grep openstack
ii openstack-dashboard 3:14.0.2-0ubuntu2 all
Django web interface for OpenStack
ii
ok, I found how to upgrade them on rocky and cosmic.
I verified bionic-rocky for this issue.
apt install openstack-dashboard-common(not openstack-dashboard)
oot@juju-41e8e7-default-8:~# dpkg -l | grep openstack-dashboard
ii openstack-dashboard 3:14.0.2-0ubuntu2~cloud0
Hello, the customer faced the similar issue.
Could you please check below log as well?
It is glance node.
https://pastebin.canonical.com/p/VyVVvv3hJS/
** Also affects: charm-glance
Importance: Undecided
Status: New
** Tags added: sts
--
You received this bug notification because
@sahid
I also found the same logs as below issue
https://github.com/lxc/lxd/issues/2004
https://pastebin.canonical.com/p/xcqPR6JShh/
maybe this shows some more clue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@sahid
it is xenial-queens, charm version is below
glance charm version is 271
I'm going to check differences between 271 and latest one.
but Could you please advice me if there is some related patch between them?
Thanks.
** Bug watch added: LXD bug tracker #2004
https://github.com/openvswitch/ovs/commit/2ed1c95e9c80a21a5d81cb760c872b62b32b0733
This seems to be commit for this.
and 2.9.3 has it.
@Camilo, Do you have reproducer for this issue?
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello
I've verified this -proposed pkg on my local.
#2 on description working fine.
xtrusia@ubuntu:~$ dpkg -l | grep network-manager
ii network-manager1.10.6-2ubuntu1.4
amd64network management framework (daemon and userspace
I uploaded patch for bionic sru. but I didn't subscribe sru-sponsors yet
because I'm still confirming reproducer.
I'll update description after reproducing this issue in my local.
Thanks.
** Tags added: sts
** Changed in: network-manager (Ubuntu Bionic)
Assignee: (unassigned) => Seye
why bugproxy keep attaching old debdiff I've changed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not assigned to bond interface is manual ipv6 is
assigned to it
** Description changed:
[Impact]
+
+ In case creating bond interface, IPv4 address is not automatically
+ assigned when IPv6 has manual setting.
+
[Test Case]
+
+ 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as
original description.
+ 2. ipv6 manual, ipv4 auto
** Patch removed: "lp1794478_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1794478/+attachment/5329464/+files/lp1794478_bionic.debdiff
** Patch added: "lp1794478_bionic.debdiff"
** Changed in: cloud-archive/rocky
Status: Triaged => Fix Released
** Changed in: octavia (Ubuntu Focal)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+ octavia lb's listener can't be delete when there is no secret container which
is already deleted.
+
+
+ [Test Case]
+
+ 1. deploy and setup octavia env
+ 2. run below script
+ - https://pastebin.ubuntu.com/p/xPWKnPqFhw/
+ 3. check if there is listener-1 is
@corey
Do we need to backport this or octavia 4.1.1 ( or for the other
releases) will be released soon for UCA ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852599
Title:
Cannot delete TLS
rocky stable point release https://bugs.launchpad.net/cloud-
archive/+bug/1853320
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852599
Title:
Cannot delete TLS Terminated listener if container has
** Patch added: "lp1852599_eoan.debdiff"
https://bugs.launchpad.net/charm-octavia/+bug/1852599/+attachment/5318419/+files/lp1852599_eoan.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1852599_stein.debdiff"
https://bugs.launchpad.net/charm-octavia/+bug/1852599/+attachment/5318413/+files/lp1852599_stein.debdiff
** Patch removed: "lp1852599_train.debdiff"
** Patch added: "lp1852599_disco.debdiff"
https://bugs.launchpad.net/charm-octavia/+bug/1852599/+attachment/5318411/+files/lp1852599_disco.debdiff
** Patch removed: "lp1852599_stein.debdiff"
** Patch added: "lp1852599_train.debdiff"
https://bugs.launchpad.net/charm-octavia/+bug/1852599/+attachment/5318417/+files/lp1852599_train.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
focal has it
** Tags added: sru-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852599
Title:
Cannot delete TLS Terminated listener if container has been deleted in
barbican
To manage
** Patch removed: "lp1852599_stein.debdiff"
https://bugs.launchpad.net/charm-octavia/+bug/1852599/+attachment/5318357/+files/lp1852599_stein.debdiff
** Patch added: "lp1852599_stein.debdiff"
** Patch added: "lp1852599_train.debdiff"
https://bugs.launchpad.net/charm-octavia/+bug/1852599/+attachment/5318375/+files/lp1852599_train.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It seems that rocky already has fix since 1 hour ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852599
Title:
Cannot delete TLS Terminated listener if container has been deleted in
barbican
** Patch added: "lp1852599_stein.debdiff"
https://bugs.launchpad.net/charm-octavia/+bug/1852599/+attachment/5318357/+files/lp1852599_stein.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: nova
Assignee: Seyeong Kim (xtrusia) => (unassigned)
** Changed in: nova (Ubuntu)
Assignee: Seyeong Kim (xtrusia) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
@sil2100 no but I just ran on both Bionic and Eoan.
It shows me "Everything worked!" at the end of string.
but there is /var/tmp/sosreport*.tar*: Cannot open: No such file or directory.
so I changed /var/tmp/* to /tmp/ and ran again. it looks fine.
do you need any output file here?
--
You
** Description changed:
[Impact]
The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
reports the old state when it's called right after rfkill block/unblock.
Adding a sleep before calling nmcli fixes the issue.
ppc64el ADT log from failed testcase:
verified eoan
root@xtrusia:/tmp/sosreport-xtrusia-2020-04-07-xyioxiy/sos_commands/lxd# ll
total 36
drwx-- 2 root root 4096 Apr 7 06:20 ./
drwxr-xr-x 54 root root 4096 Apr 7 06:20 ../
-rw-r--r-- 1 root root 27074 Apr 7 06:20 lxd.buginfo
verified bionic
root@xtrusia:/tmp/sosreport-xtrusia-2020-04-07-ojxtgec/sos_commands/lxd# ll
total 36
drwx-- 2 root root 4096 Apr 7 03:11 ./
drwxr-xr-x 53 root root 4096 Apr 7 03:11 ../
-rw-r--r-- 1 root root 25844 Apr 7 03:11 lxd.buginfo
Hello, I uploaded pkg to ppa
https://launchpad.net/~xtrusia/+archive/ubuntu/lp1733321
and checked ppc64el build and testing.
It worked fine without any issue.
Could you please adjust Kleber's debdiff as well?
Thanks a lot.
--
You received this bug notification because you are a member of
** Patch added: "lp1868215_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1868215/+attachment/5341304/+files/lp1868215_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp18168215_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1868215/+attachment/5341306/+files/lp18168215_bionic.debdiff
** Description changed:
[Impact]
+
+ sosreport doesn't have to collect everything related to lxd which is very
huge and
** Patch added: "lp1868215_eoan.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1868215/+attachment/5341305/+files/lp1868215_eoan.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
reports the old state when it's called right after rfkill block/unblock.
Adding a sleep before calling nmcli fixes the issue.
ppc64el ADT log from failed testcase:
Public bug reported:
[Impact]
[Test Case]
Preparing
[Regression]
[Others]
upstream patch
-
https://github.com/sosreport/sos/pull/1982/commits/bdc5ffdf5b8376ab2014ec8fbd9a878cc9d0d264
** Affects: sosreport (Ubuntu)
Importance: Undecided
Assignee: Seyeong Kim (xtrusia
** Changed in: sosreport (Ubuntu Bionic)
Status: New => In Progress
** Changed in: sosreport (Ubuntu Eoan)
Status: New => In Progress
** Changed in: sosreport (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: neutron (Ubuntu)
Status: New => Fix Released
** Also affects: cloud-archive
Importance: Undecided
Public bug reported:
[Impact]
livemigration of windows 2012 r2 instance with virtio balloon driver
from qemu 2.5(mitaka) to qemu 2.11(queens) is not working properly.
Especially instance keep moving e.g 2.5 -> 2.5 -> 2.11
Then It shows below msg from the 2nd mitaka node.
Migration: [ 94
and the customer said that
windows 2012r2, 2016 has issue but 2019 ( from their image ) is fine.
but we don't know what setting is there actually inside those images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
usually X->X->B is reproducer here. X->B is working fine basically.
Windows guest should have virtio balloon driver.
and I think below setting is needed ( as the customer's xml has it )
virsh dommemstat --domain win2k12r2 --period 10 --config
--
You received this bug notification because you
FYI I think this bug is the same as 1647389
In that LP,
Dave also mentioned commit 4eae2a657d1ff5ada56eb9b4966eae0eff333b0b is needed
but it is too large and changes a lot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
workaround
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1647389/comments/15
didnt work.
I worried that if we patch this to over Q,
I assume that live migration current running instances from current Q to
patched Q
so I've tested some scenario
###
Scenario 1
** Changed in: qemu (Ubuntu Groovy)
Status: Fix Released => In Progress
** Changed in: qemu (Ubuntu Groovy)
Assignee: (unassigned) => Seyeong Kim (seyeongkim)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1894772_ussuri.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1894772/+attachment/5409659/+files/lp1894772_ussuri.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1894772_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1894772/+attachment/5409640/+files/lp1894772_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch removed: "lp1894772_ussuri.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1894772/+attachment/5409659/+files/lp1894772_ussuri.debdiff
** Patch removed: "lp1894772_focal.debdiff"
** Patch added: "lp1894772_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1894772/+attachment/5409639/+files/lp1894772_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
###
Scenario 4
###
Focal <-> Focal
->
Focal( patched ) OK
###
and
-> Focal -> Focal(patched) OK
###
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I've tested above patch on queens qemu. and it works fine.
I don't have to fix Mitaka anymore.
if this patch is viable, we need to put this to every release since
Queens. if not, migration from patched one to unpatched one will not
work as I saw between Mitaka and Queens.
--
You received this
: (unassigned) => Seyeong Kim (seyeongkim)
** Changed in: qemu (Ubuntu Focal)
Status: New => In Progress
** Changed in: qemu (Ubuntu Focal)
Assignee: (unassigned) => Seyeong Kim (seyeongkim)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Patch removed: "lp1894772_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/xenial/+source/qemu/+bug/1894772/+attachment/5408515/+files/lp1894772_xenial.debdiff
** Patch removed: "lp1894772_mitaka.debdiff"
** Description changed:
[Impact]
- livemigration of windows 2012 r2 instance with virtio balloon driver
+ livemigration of windows 2012 r2 instance with virtio balloon driver
from qemu 2.5(mitaka) to qemu 2.11(queens) is not working properly.
Especially instance keep moving e.g
** Description changed:
[Impact]
livemigration of windows 2012 r2 instance with virtio balloon driver
from qemu 2.5(mitaka) to qemu 2.11(queens) is not working properly.
Especially instance keep moving e.g 2.5 -> 2.5 -> 2.11
Then It shows below msg from the 2nd mitaka node.
ah I missed one thing is that
I was able to reproduce this issue with xenial (non UCA, 2.5 ) to
queens-staging. I'll test above case
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894772
Title:
** Patch added: "lp1894772_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1894772/+attachment/5408515/+files/lp1894772_xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1894772_mitaka.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1894772/+attachment/5408516/+files/lp1894772_mitaka.debdiff
** Changed in: qemu (Ubuntu Xenial)
Assignee: (unassigned) => Seyeong Kim (seyeongkim)
--
You received this bug
Hi.
I tested yakkety(2.6.1) -> yakkty -> queens(2.11) and it worked.
so I did bisect then found those commits.
But I didn't test xenial->bionic,
but I'll update case after testing them as well.
Xenial -> Bionic
Mitaka -> Queens -> Ussuri
--
You received this bug notification because you are
Quick test with non UCA X -> X -> B, I can reproduce this the same way
as description and patch fixed issue.
I'm going to test further
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894772
Title:
Hey Christian
Unfortunately, I found an issue between below steps
X(not patched) -> X(patched) -> Q- is working fine
X(not patched) -> X(not patched) -> Q(error)
-> X(patched) -> Q - has the same error as
original
The customer is in the
I think below commit is included inside 2.5 qemu in Xenial but not in
2.11
and I tested it with upstream commit build with migration. but I haven't
tested it yet
I'm going to test them with ubuntu releases as well.
If it is correct, we need patch > queens instead of mitaka
Description: make
Test M M Q U
M M Q is ok
but Q -> U has issue below.
error: internal error: qemu unexpectedly closed the monitor:
qemu-system-x86_64: -realtime mlock=off: warning: '-realtime mlock=...' is
deprecated, please use '-overcommit mem-lock=...' instead
2020-09-09T00:56:27.768574Z
hey paelzer,
ah sorry
libvirt on Bionic was 4.0.0
I installed them libvirt-bin but I missed it is changed to libvirt-
daemon-system
I re-installed libvirt-daemon-system and it is 6.0.0 now,
then M -> M -> Q -> U migration is working fine.
--
You received this bug notification because you
With M-M-Q-U, and I faced issue described above, instance in Q crashed without
special log in qemu
only found msg is below from syslog
Sep 9 04:50:53 colt libvirtd[1311]: 2020-09-09 04:50:53.224+: 1311: error
: qemuMonitorIO:719 : internal error: End of file from qemu monitor
I tried to
** Description changed:
+ [Impact]
+ When using linuxbridge, disable_ipv6 is 1 then I can't create network ipv6
properly.
+
+ [Test Case]
+
+ 1. deploy basic mitaka env
+ 2. create external network(ext-net)
+ 3. create ipv6 network and interface to ext-net
+ 4. check if related bridge has
** Description changed:
[Impact]
- When using linuxbridge, disable_ipv6 is 1 then I can't create network ipv6
properly.
+ When using linuxbridge and after creating network & interface to ext-net,
disable_ipv6 is 1. then linuxbridge-agent doesn't add ipv6 properly to newly
created bridge.
** Tags removed: sru-neede
** Tags added: sts-sru-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662324
Title:
linux bridge agent disables ipv6 before adding an ipv6 address
To manage
** Patch added: "lp1662324_mitaka.debdiff"
https://bugs.launchpad.net/neutron/+bug/1662324/+attachment/5376359/+files/lp1662324_mitaka.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662324
** Patch added: "lp1662324_xenial.debdiff"
https://bugs.launchpad.net/neutron/+bug/1662324/+attachment/5376360/+files/lp1662324_xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662324
** Changed in: cloud-archive/mitaka
Status: New => In Progress
** Changed in: cloud-archive/mitaka
Assignee: (unassigned) => Seyeong Kim (xtrusia)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Changed in: neutron (Ubuntu Xenial)
Status: New => In Progress
** Changed in: neutron (Ubuntu Xenial)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
** Changed in: cloud-archive
Status: New => Fix Released
--
You received this bug notification because you are
I updated regression
Please let me know if I need to put more.
Thanks.
** Description changed:
[Impact]
When using linuxbridge and after creating network & interface to ext-net,
disable_ipv6 is 1. then linuxbridge-agent doesn't add ipv6 properly to newly
created bridge.
[Test Case]
@corey.bryant
Hello. I just checked that even I did "sudo add-apt-repository cloud-
archive:mitaka-proposed"
neutron version is the same as mitaka-staging
neutron-linuxbridge-agent/trusty-proposed,trusty,now
2:8.4.0-0ubuntu7.5~cloud0 all [installed]
--
You received this bug notification
I'm going to verify mitaka this week. building trusty-mitaka env now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662324
Title:
linux bridge agent disables ipv6 before adding an ipv6 address
To
Thanks for your guide
** Description changed:
[Impact]
When using linuxbridge and after creating network & interface to ext-net,
disable_ipv6 is 1. then linuxbridge-agent doesn't add ipv6 properly to newly
created bridge.
[Test Case]
1. deploy basic mitaka env
2. create
** Patch added: "lp1886300_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1886300/+attachment/5395090/+files/lp1886300_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch removed: "lp1886300_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1886300/+attachment/5394575/+files/lp1886300_groovy.debdiff
** Patch removed: "lp1886300_focal.debdiff"
@mfo
Thanks for your advice, re-uploaded patches
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886300
Title:
rename.ul refuses to rename links that don't resolve (regression)
To manage
** Changed in: util-linux (Ubuntu Eoan)
Assignee: (unassigned) => Seyeong Kim (seyeongkim)
** Changed in: util-linux (Ubuntu Focal)
Assignee: (unassigned) => Seyeong Kim (seyeongkim)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Patch added: "lp1886300_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1886300/+attachment/5394575/+files/lp1886300_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1886300_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1886300/+attachment/5394576/+files/lp1886300_focal.debdiff
** No longer affects: util-linux (Ubuntu Eoan)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Description changed:
+ [Impact]
+
+ rename.ul refuses to rename links that don't resolve.
+
+ bionic rename.ul renames links whether or not they resolve (util-linux
+ 2.31.1-0.4ubuntu3.6).
+
+ focal rename.ul refuses to rename links that don't resolve (regression)
+ (util-linux
@corey Thanks.
it works fine as belows. disable_ipv6 is 0
6: ens4f1.1103@ens4f1: mtu 1500 qdisc noqueue
master brqc1308c59-e3 state UP group default
link/ether 52:54:01:97:26:35 brd ff:ff:ff:ff:ff:ff
7: brqc1308c59-e3: mtu 1500 qdisc noqueue
state UP group default
link/ether
Hello
I verified this patch is working fine on testing.
After this patch, disable_ipv6 contains 0 which is proper value for
ipv6.
Thanks a lot.
ii neutron-common2:8.4.0-0ubuntu7.5
all Neutron is a virtual network service for
Verification for Train is done.
ii python3-oslo.messaging 9.7.1-0ubuntu3~cloud1
all oslo messaging library - Python 3.x
verification steps
1. reproduce this issue
2. update all python3-oslo.messaging in test env
3. restart rabbitmq-server
all Channel issue is gone.
Verification for Stein is done.
ii python3-oslo.messaging 9.5.0-0ubuntu1~cloud1
verification steps
1. reproduce this issue
2. update all python3-oslo.messaging in test env
3. restart rabbitmq-server
all Channel issue is gone.
** Tags removed: verification-stein-needed
** Tags
** Description changed:
[Impact]
+ If there are many exchanges and queues, after failing over, rabbitmq-
+ server shows us error that exchanges are cannot be found.
Affected
- Bionic
+ Bionic (Queens)
Not affected
- Focal
+ Focal
+
[Test Case]
- TBD
+
+ 1. deploy simple
I can't reproduce this symptom in Focal though it is 12.1.0
it doesn't have commit 0a432c7fb107d04f7a41199fe9a8c4fbd344d009
I think xenial need fix as well, I can reproduce this in xenial,
I'm preparing debdiff for xenial as well
--
You received this bug notification because you are a member
** Patch removed: "lp1789177_bionic.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/1789177/+attachment/5444392/+files/lp1789177_bionic.debdiff
** Patch removed: "lp1789177_queens.debdiff"
** Patch added: "lp1789177_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-oslo.messaging/+bug/1789177/+attachment/5444730/+files/lp1789177_xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1789177_mitaka.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-oslo.messaging/+bug/1789177/+attachment/5444740/+files/lp1789177_mitaka.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: cloud-archive/mitaka
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.
** Patch added: "lp1789177_train.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-oslo.messaging/+bug/1789177/+attachment/5444808/+files/lp1789177_train.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1789177_stein.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-oslo.messaging/+bug/1789177/+attachment/5444807/+files/lp1789177_stein.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
601 - 700 of 773 matches
Mail list logo
