[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-11 Thread Seyeong Kim
** 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"

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-11 Thread Seyeong Kim
### 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

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-10 Thread Seyeong Kim
** 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.

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-10 Thread Seyeong Kim
** 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.

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-10 Thread Seyeong Kim
** 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.

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-10 Thread Seyeong Kim
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

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-10 Thread Seyeong Kim
** 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.

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-10 Thread Seyeong Kim
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.

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-10 Thread Seyeong Kim
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

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-10 Thread Seyeong Kim
: (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

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-10 Thread Seyeong Kim
** 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"

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-10 Thread Seyeong Kim
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

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-09 Thread Seyeong Kim
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

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-09 Thread Seyeong Kim
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.

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-09 Thread Seyeong Kim
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

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-09 Thread Seyeong Kim
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

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-08 Thread Seyeong Kim
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

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-08 Thread Seyeong Kim
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

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-08 Thread Seyeong Kim
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:

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-08 Thread Seyeong Kim
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:

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-08 Thread Seyeong Kim
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

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-07 Thread Seyeong Kim
** 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

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-07 Thread Seyeong Kim
** 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.

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-07 Thread Seyeong Kim
** 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.

[Bug 1894772] Re: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-07 Thread Seyeong Kim
** 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

[Bug 1894772] [NEW] live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens.

2020-09-07 Thread Seyeong Kim
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

[Bug 1886300] Re: rename.ul refuses to rename links that don't resolve (regression)

2020-07-23 Thread Seyeong Kim
@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

[Bug 1886300] Re: rename.ul refuses to rename links that don't resolve (regression)

2020-07-23 Thread Seyeong Kim
** 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"

[Bug 1886300] Re: rename.ul refuses to rename links that don't resolve (regression)

2020-07-23 Thread Seyeong Kim
** 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.

[Bug 1886300] Re: rename.ul refuses to rename links that don't resolve (regression)

2020-07-21 Thread Seyeong Kim
** 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

[Bug 1886300] Re: rename.ul refuses to rename links that don't resolve (regression)

2020-07-21 Thread Seyeong Kim
** 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

[Bug 1886300] Re: rename.ul refuses to rename links that don't resolve (regression)

2020-07-21 Thread Seyeong Kim
** 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.

[Bug 1886300] Re: rename.ul refuses to rename links that don't resolve (regression)

2020-07-20 Thread Seyeong Kim
** 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

[Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-07-16 Thread Seyeong Kim
@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

[Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-07-14 Thread Seyeong Kim
@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

[Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-07-13 Thread Seyeong Kim
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

[Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-07-06 Thread Seyeong Kim
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

[Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-07-03 Thread Seyeong Kim
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

[Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-06-30 Thread Seyeong Kim
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]

[Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-05-26 Thread Seyeong Kim
** 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

[Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-05-26 Thread Seyeong Kim
** 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

[Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-05-24 Thread Seyeong Kim
** 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.

[Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-05-24 Thread Seyeong Kim
** 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

[Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-05-24 Thread Seyeong Kim
** 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

[Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-05-24 Thread Seyeong Kim
** 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

[Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-05-24 Thread Seyeong Kim
** 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

[Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-05-22 Thread Seyeong Kim
** 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

[Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2020-04-23 Thread Seyeong Kim
** 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:

[Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2020-04-20 Thread Seyeong Kim
** 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:

[Bug 1868215] Re: SRU: [lxd] Drop db collection and introduce lxd.buginfo

2020-04-14 Thread Seyeong Kim
@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

[Bug 1452641] Re: Static Ceph mon IP addresses in connection_info can prevent VM startup

2020-04-09 Thread Seyeong Kim
** 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

[Bug 1868215] Re: SRU: [lxd] Drop db collection and introduce lxd.buginfo

2020-04-07 Thread Seyeong Kim
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

[Bug 1868215] Re: SRU: [lxd] Drop db collection and introduce lxd.buginfo

2020-04-06 Thread Seyeong Kim
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

[Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2020-04-03 Thread Seyeong Kim
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

[Bug 1868215] Re: SRU: [lxd] Drop db collection and introduce lxd.buginfo

2020-03-24 Thread Seyeong Kim
** 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.

[Bug 1868215] Re: SRU: [lxd] Drop db collection and introduce lxd.buginfo

2020-03-24 Thread Seyeong Kim
** 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

[Bug 1868215] Re: SRU: [lxd] Drop db collection and introduce lxd.buginfo

2020-03-24 Thread Seyeong Kim
** 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.

[Bug 1868215] Re: SRU: [lxd] Drop db collection and introduce lxd.buginfo

2020-03-23 Thread Seyeong Kim
** 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

[Bug 1868215] [NEW] SRU: [lxd] Drop db collection and introduce lxd.buginfo

2020-03-20 Thread Seyeong Kim
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

[Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

2020-03-03 Thread Seyeong Kim
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

[Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

2020-02-21 Thread Seyeong Kim
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

[Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

2020-02-21 Thread Seyeong Kim
** 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

[Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

2020-02-19 Thread Seyeong Kim
** 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"

[Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

2020-02-18 Thread Seyeong Kim
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

[Bug 1852599] Re: Cannot delete TLS Terminated listener if container has been deleted in barbican

2020-01-10 Thread Seyeong Kim
** 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

[Bug 1852599] Re: Cannot delete TLS Terminated listener if container has been deleted in barbican

2020-01-08 Thread Seyeong Kim
** 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.

[Bug 1852599] Re: Cannot delete TLS Terminated listener if container has been deleted in barbican

2020-01-07 Thread Seyeong Kim
** 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.

[Bug 1852599] Re: Cannot delete TLS Terminated listener if container has been deleted in barbican

2020-01-07 Thread Seyeong Kim
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

[Bug 1852599] Re: Cannot delete TLS Terminated listener if container has been deleted in barbican

2020-01-07 Thread Seyeong Kim
** Patch added: "lp1852599_stein.debdiff" https://bugs.launchpad.net/charm-octavia/+bug/1852599/+attachment/5318413/+files/lp1852599_stein.debdiff ** Patch removed: "lp1852599_train.debdiff"

[Bug 1852599] Re: Cannot delete TLS Terminated listener if container has been deleted in barbican

2020-01-07 Thread Seyeong Kim
** Patch added: "lp1852599_disco.debdiff" https://bugs.launchpad.net/charm-octavia/+bug/1852599/+attachment/5318411/+files/lp1852599_disco.debdiff ** Patch removed: "lp1852599_stein.debdiff"

[Bug 1852599] Re: Cannot delete TLS Terminated listener if container has been deleted in barbican

2020-01-07 Thread Seyeong Kim
** 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.

[Bug 1852599] Re: Cannot delete TLS Terminated listener if container has been deleted in barbican

2020-01-07 Thread Seyeong Kim
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

[Bug 1852599] Re: Cannot delete TLS Terminated listener if container has been deleted in barbican

2020-01-07 Thread Seyeong Kim
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

[Bug 1852599] Re: Cannot delete TLS Terminated listener if container has been deleted in barbican

2020-01-07 Thread Seyeong Kim
** 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.

[Bug 1852599] Re: Cannot delete TLS Terminated listener if container has been deleted in barbican

2020-01-07 Thread Seyeong Kim
** Patch removed: "lp1852599_stein.debdiff" https://bugs.launchpad.net/charm-octavia/+bug/1852599/+attachment/5318357/+files/lp1852599_stein.debdiff ** Patch added: "lp1852599_stein.debdiff"

[Bug 1852599] Re: Cannot delete TLS Terminated listener if container has been deleted in barbican

2020-01-07 Thread Seyeong Kim
** 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.

[Bug 1852599] Re: Cannot delete TLS Terminated listener if container has been deleted in barbican

2020-01-06 Thread Seyeong Kim
@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

[Bug 1839592] Re: Open vSwitch (Version 2.9.2) goes into deadlocked state

2019-11-05 Thread Seyeong Kim
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

[Bug 1782644] Re: Charm blocked on designate services with Runtime directory is not valid reported in syslog

2019-08-01 Thread Seyeong Kim
@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

[Bug 1782644] Re: Charm blocked on designate services with Runtime directory is not valid reported in syslog

2019-08-01 Thread Seyeong Kim
@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.

[Bug 1782644] Re: Charm blocked on designate services with Runtime directory is not valid reported in syslog

2019-07-29 Thread Seyeong Kim
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

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-04-09 Thread Seyeong Kim
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

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-04-08 Thread Seyeong Kim
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

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-04-08 Thread Seyeong Kim
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

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-04-07 Thread Seyeong Kim
logs in rocky https://pastebin.canonical.com/p/7wT45RzGxM/ -- 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 manage

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-04-07 Thread Seyeong Kim
logs in cosmic https://pastebin.canonical.com/p/YvBsZnSZrS/ -- 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 manage

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-04-04 Thread Seyeong Kim
I tried cosmic again with adding universe multiverse to apt/sources.list and got the same msg as cosmic-rocky -- 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

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-04-04 Thread Seyeong Kim
I can verify this is working after I installed with dpkg from directly download deb pkgs.. I think I need to check this -- 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

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-04-04 Thread Seyeong Kim
When trying to upgrade openstack-dashboard I got below messages. and If I upgrade them all, there are syntax error there. ( pyinotify ) Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: docutils-doc

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-04-04 Thread Seyeong Kim
Hello I've verified this issue for queens. I just did the same test as description. dpkg -l | grep dashboard ii openstack-dashboard 3:13.0.1-0ubuntu5~cloud0 all Django web interface for OpenStack ii openstack-dashboard-ubuntu-theme

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-04-02 Thread Seyeong Kim
while upgrading pkg in cosmic. I faced error with apt command. It seems that dependency issue is there. and newer version of python3 -django-horizon is not there yet. root@node-11:~# apt install python3-django-horizon openstack-dashboard Reading package lists... Done Building dependency tree

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-04-02 Thread Seyeong Kim
Hello I've verified bionic for this. I did the same test as description. dpkg -l | grep dashboard ii openstack-dashboard 3:13.0.1-0ubuntu5 all Django web interface for OpenStack ** Tags removed: verification-needed-bionic ** Tags added:

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-04-02 Thread Seyeong Kim
Hello I've verified pike for this. just did the same test as description. dpkg -l | grep dashboard ii openstack-dashboard 3:12.0.3-0ubuntu1~cloud1 all Django web interface for OpenStack ii openstack-dashboard-ubuntu-theme 3:12.0.3-0ubuntu1~cloud1

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-03-27 Thread Seyeong Kim
Thanks. but this issue is happening from Pike, I tested Ocata but it is ok. though code are the same all of them.. ( I think patch for old one is just fine but can't verify them when it is in -proposed.. ) except that, all seems good. Thanks. -- You received this bug notification because you

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-03-27 Thread Seyeong Kim
ok I'll try to do it. I have a question about that. I think we need to handle them separately but you want to handle them in this case? -- 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:

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-03-27 Thread Seyeong Kim
Hello Sahid Could you please let me know what env you used? I tested pike and queens just now and there is no symptome as you said. It is normally loaded in my case. Thanks. ** Attachment added: "screenshot_login.png"

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-03-18 Thread Seyeong Kim
** 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 {

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-03-18 Thread Seyeong Kim
** 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 {

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-03-18 Thread Seyeong Kim
** Patch added: "lp1818770_rocky.debdiff" https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1818770/+attachment/5247480/+files/lp1818770_rocky.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page

2019-03-18 Thread Seyeong Kim
** Patch added: "lp1818770_queens.debdiff" https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1818770/+attachment/5247479/+files/lp1818770_queens.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

  1   2   3   4   5   6   7   >