@mfo @james-page
Thanks all!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1994521
Title:
HPE3PAR: Failing to clone a volume having children
To manage notifications about this bug go to:
@mfo
Thanks I had a discussion with dariusz and he mentioned it could be possible
and he uploaded.
After that, he found out below comment.
https://bugs.launchpad.net/cinder/+bug/1988942/comments/23
Do I need to contact openstack team directly about this?
Thanks.
--
You received this bug
** Patch removed: "lp2017748_focal_yoga.debdiff"
https://bugs.launchpad.net/cinder/+bug/1994521/+attachment/5752220/+files/lp2017748_focal_yoga.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: neutron (Ubuntu Jammy)
Assignee: Seyeong Kim (seyeongkim) => (unassigned)
** Changed in: neutron (Ubuntu Focal)
Assignee: Seyeong Kim (seyeongkim) => (unassigned)
** Patch removed: "lp2017748_focal_yoga.debdiff"
https://bugs.launchpad.net/neut
** Description changed:
+ [Impact]
+
+ The customer faced issue when they are using nova with 3par storage.
+ they can't delete volume if there is children and it is attached to vm.
+
+ it makes sense they can't delete it as the children has attachment but
+ nova should expose proper error when
Hello @dgadomski, sorry for making confusion.
For now, upstream review is in progress for zed, 2023.1 ( for yoga is rejected )
I wasn't sure if I can go forward with this situation so I didn't updated
description yet.
But do you think it is possible to SRU in this situation?
Either way, I'll
** Patch added: "lp2017748_focal_yoga.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1994521/+attachment/5752220/+files/lp2017748_focal_yoga.debdiff
** Also affects: cinder (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: cinder (Ubuntu Mantic)
** Patch added: "lp1994521_jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1994521/+attachment/5752219/+files/lp1994521_jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: cinder (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cinder (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Package changed: nova (Ubuntu) => nova
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950186
Title:
Nova doesn't account for hugepages when scheduling VMs
To manage notifications about this bug
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950186
Title:
Nova doesn't account for hugepages when scheduling VMs
To manage notifications about this bug go to:
@ddstreet
yep I've checked that ( [:1] or something else )
This issue is only happening when back storage is LVM.
If it is not lvm, it is ok, only with lvm, pexepct returns weird string
2021-03-17 20:43:34 stderr: [error] Arguments: ([' ',
'<3ef-46ca-87c8-19171950592f --pool
@ddstreet sorry I thought I replied for it.
I've changed it for testing and MAAS didn't work properly.
Normal functionality didn't work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921658
Title:
@ddstreet
Thanks for your advice,
FYI, This symptom is only happening when backend storage is LVM, it is
ok when we just use local storage
And I've checked decoded string before but it was the same (error). LVM
has error, local is ok
But I'm trying to test you mentioned
Thanks
--
You
@ddstreet
Thanks for your remind.
I also researching how to find proper reproducer for this issue
I only checked that this patch fixed the symptom while I'm using MAAS as
I described here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@ddstreet
sorry for late response, I updated description.
Thanks.
** Description changed:
+ [Impact]
+
I can't compose kvm host on maas 2.8.4 ( bionic)
I upgraded twisted and related component with pip but the symptom is the
same.
MaaS 2.9.x in Focal works fine.
in 2.8.x,
New => In Progress
** Changed in: readline (Ubuntu Bionic)
Assignee: (unassigned) => Seyeong Kim (seyeongkim)
** Patch added: "lp1921658_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/readline/+bug/1921658/+attachment/5517702/+files/lp1921658_bionic.debdiff
--
Yo
** Patch removed: "lp1936881_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1936881/+attachment/5511979/+files/lp1936881_bionic.debdiff
** Patch added: "lp1936881_bionic.debdiff"
@Sergio
Thanks for your review, I've uploaded debdiff with dep3(sorry I forgot)
Let me ask the customer if it is possible to test this ppa,
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
- Bionic
+ Bionic, Openstack
The customer reported below issue
+
+ And there are queues which has unconsumed msgs. so wasn't able to create
+ instance.
+
+ they was able to fix this by rebooting nova-compute node.
=CRASH REPORT
** Description changed:
[Impact]
Bionic
The customer reported below issue
=CRASH REPORT 2-Jul-2021::04:30:57 ===
crasher:
initial call: rabbit_reader:init/4
pid: <0.17293.17>
registered_name: []
exception exit: channel_termination_timeout
in function
** Also affects: rabbitmq-server (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: rabbitmq-server (Ubuntu)
Status: New => Fix Released
** Patch added: "lp1936881_bionic.debdiff"
Public bug reported:
[Impact]
Bionic
The customer reported below issue
=CRASH REPORT 2-Jul-2021::04:30:57 ===
crasher:
initial call: rabbit_reader:init/4
pid: <0.17293.17>
registered_name: []
exception exit: channel_termination_timeout
in function
tested pkg in bionic
steps are below ( the same as queens above )
1. deploy bionic env
2. upgrade python-oslo.messaging in nova-compute/0
3. restart neutron-openvswitch-agent ( only )
4. check logs , no error
5. launch instance if it works, no error
ii python-oslo.messaging
tested pkg in queens
test steps are below
1. deploy queens env
2. upgrade python-oslo.messaging in nova-compute/0
3. restart neutron-openvswitch-agent ( only )
4. check logs , no error
5. launch instance if it works, no error
ii python-oslo.messaging 5.35.0-0ubuntu4~cloud0
all
sorry for being late, I'll verify this soon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789177
Title:
RabbitMQ fails to synchronize exchanges under high load (Note for
ubuntu: stein, rocky,
ned) => Seyeong Kim (seyeongkim)
** Changed in: neutron (Ubuntu Bionic)
Status: New => In Progress
** Patch added: "lp1849098_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1849098/+attachment/5494377/+files/lp1849098_bionic.debdiff
**
** Description changed:
[Impact]
systemd-networkd renames nic just after udev renamed it
e.g
kernel: [ 2.827368] vmxnet3 :0b:00.0 ens192: renamed from eth0
kernel: [ 7.562729] vmxnet3 :0b:00.0 eth0: renamed from ens192
systemd-networkd[511]: ens192: Interface name
** Description changed:
[Impact]
systemd-networkd renames nic just after udev renamed it
e.g
kernel: [ 2.827368] vmxnet3 :0b:00.0 ens192: renamed from eth0
kernel: [ 7.562729] vmxnet3 :0b:00.0 eth0: renamed from ens192
systemd-networkd[511]: ens192: Interface name
** Patch added: "lp1923115_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923115/+attachment/5485751/+files/lp1923115_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
)
Importance: Undecided
Status: Fix Released
** Affects: systemd (Ubuntu Bionic)
Importance: Undecided
Assignee: Seyeong Kim (seyeongkim)
Status: In Progress
** Affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: Fix Released
** Tags: sts
** 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 (Queens)
Not affected
Focal
[Test Case]
1. deploy simple rabbitmq cluster
-
Hello Corey
That makes sense to me as well.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789177
Title:
RabbitMQ fails to synchronize exchanges under high load
To manage notifications
** Patch removed: "lp1789177_bionic.debdiff"
https://bugs.launchpad.net/oslo.messaging/+bug/1789177/+attachment/5466823/+files/lp1789177_bionic.debdiff
** Patch removed: "lp1789177_queens.debdiff"
Testing with only 1st patch didn't work , I was able to see the same error as
the description in this LP
Testing with 1st and 3rd with manual configuration(enable_cancel_on_failover =
True ) showed me different error
( mentnioned above )
The different error is happening less time than I assume.
** Patch added: "lp1789177_bionic.debdiff"
https://bugs.launchpad.net/oslo.messaging/+bug/1789177/+attachment/5466823/+files/lp1789177_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1789177_queens.debdiff"
https://bugs.launchpad.net/oslo.messaging/+bug/1789177/+attachment/5466822/+files/lp1789177_queens.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch removed: "lp1789177_queens.debdiff"
https://bugs.launchpad.net/oslo.messaging/+bug/1789177/+attachment/5444721/+files/lp1789177_queens.debdiff
** Patch removed: "lp1789177_xenial.debdiff"
** Patch removed: "lp1789177_bionic.debdiff"
https://bugs.launchpad.net/oslo.messaging/+bug/1789177/+attachment/5444720/+files/lp1789177_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
testing 1st, 3rd commit and manual configuration
enable_cancel_on_failover = True
I did the similar step above with Queens ( as I already made ppa for
this )
and in this case, I see different errors. restarting rabbitmq-server
solved error msgs
=ERROR REPORT 24-Feb-2021::08:07:46 ===
With 2nd try, I also faced the same error with patched component, not
even only openvswitch-agent.
I'm going to try to reproduce with 1st and 3rd commit with manual
configuration( enable_cancel_on_failover)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
after restarting all rabbitmq-server, status are stable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789177
Title:
RabbitMQ fails to synchronize exchanges under high load
To manage
1. deploy rocky
2. installed updated oslo.messaging pkg in below nodes
- neutron-api
- neutron-gateway
- nova-compute
- - restarted openvswitch-agent only
3. tried to reproduce with below config
- created 3000 test queue, exchange, bindings
- juju config rabbitmq-server min-cluster-size=1
- juju
ah sorry corey you already uploaded it to bionic as well. thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789177
Title:
RabbitMQ fails to synchronize exchanges under high load
To manage
I've confirmed that only 1st patch is ok with below steps
1. deploy queens
2. patch nuetron node's oslo.messaging (1st patch only) except nova-compute
node's oslo.messaging
3. trying to create instance and delete
And I keep restarting cinder-scheduler while I blocked one rabbitmq-
server with
I tested below
It was the same scenario I tested
0 deploy test env
- 5.35.0-0ubuntu1~cloud0
1. upgrading olso.messaging in n-ovs
- 5.35.0-0ubuntu2~cloud0 ( from queens-staging launchpad)
2. I got errors
3. upgrading it to new one
- 5.35.0-0ubuntu3~cloud0
it worked fine for me.
I'm trying to
I confirmed that upgrading olso.messaging in n-ovs causes rabbitmq issue
Right after restarted n-ovs-agent, I can see a lot of errors in rabbitmq log[1]
which is the same as the error when rabbitmq failover issue ( the original
issue of this LP )
Then after I upgraded oslo.messaging in
The customer also faced this issue
** Tags added: sts
--
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 about this bug
Verification is done for Bionic
# dpkg -l | grep netplan.io
ii netplan.io 0.99-0ubuntu3~18.04.4
amd64YAML network configuration abstraction for various
backends
Test step
deploy bionic vm
set netplan conf as description said.
** Attachment added: "bionic_ppc64el_artifacts.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1817651/+attachment/5454755/+files/bionic_ppc64el_artifacts.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "bionic_s390x_artifacts.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1817651/+attachment/5454756/+files/bionic_s390x_artifacts.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "bionic_i386_artifacts.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1817651/+attachment/5454754/+files/bionic_i386_artifacts.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "bionic_armhf_artifacts.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1817651/+attachment/5454753/+files/bionic_armhf_artifacts.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "bionic_arm64_artifacts.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1817651/+attachment/5454748/+files/bionic_arm64_artifacts.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "bionic_amd64_artifacts.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1817651/+attachment/5454747/+files/bionic_amd64_artifacts.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hey @slyon
There is no exact version in
https://autopkgtest.ubuntu.com/packages/netplan.io
Does somebody need to upload it to there or I need to do something for
this?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: netplan.io (Ubuntu Bionic)
Status: New => In Progress
** Changed in: netplan.io (Ubuntu Bionic)
Assignee: (unassigned) => Seyeong Kim (seyeongkim)
** Tags added: sts
** Patch added: "lp1817651_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/netplan.i
** Also affects: netplan.io (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu Focal)
Status: New => Fix Released
--
You received this bug notification
actually for bionic and queens, python-oslo.messaging is correct one ,
not python3-oslo.messaging
** Tags removed: verification-queens-needed
** Tags added: verification-queens-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verification done for Queens
ii python-oslo.messaging 5.35.0-0ubuntu2~cloud0
all oslo messaging library - Python 2.x
verification steps ( the same as above )
1. reproduce this issue
2. update all python3-oslo.messaging in test env
3. restart rabbitmq-server
all Channel
Verification done for Bionic
ii python-oslo.messaging 5.35.0-0ubuntu2
all oslo messaging library - Python 2.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.
** Tags
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
** Changed in: python-oslo.messaging (Ubuntu Xenial)
Status: New => In Progress
** Changed in: python-oslo.messaging (Ubuntu Xenial)
Assignee: (unassigned) => Seyeong Kim (seyeongkim)
** Changed in: python-oslo.messaging (Ubuntu Bionic)
Status: New => In Progress
*
** 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.
For Stein and Train
There is already commit 3a5de89dd686dbd9660f140f9c78b20e1632
But no 6fe1aec1c74f112db297cd727d2ea400a292b038
I think we need to fix this for both releases as well.
only one fix cannot be solve this issue.
and Train's functional test is already removed
but Stein's
** 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_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.
** 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.
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 added: "lp1789177_queens.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-oslo.messaging/+bug/1789177/+attachment/5444721/+files/lp1789177_queens.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1789177_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-oslo.messaging/+bug/1789177/+attachment/5444720/+files/lp1789177_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch removed: "lp1789177_bionic.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/1789177/+attachment/5444392/+files/lp1789177_bionic.debdiff
** Patch removed: "lp1789177_queens.debdiff"
** 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
** Patch added: "lp1789177_queens.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-oslo.messaging/+bug/1789177/+attachment/522/+files/lp1789177_queens.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1789177_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-oslo.messaging/+bug/1789177/+attachment/5444392/+files/lp1789177_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: sts
** Description changed:
+ [Impact]
+
+
+ Affected
+ Bionic
+ Not affected
+ Focal
+
+ [Test Case]
+ TBD
+
+
+ [Where problems could occur]
+ TBD
+
+ [Others]
+
+
+ // original description
+
Input:
- - OpenStack Pike cluster with ~500 nodes
- - DVR enabled in
** Also affects: python-oslo.messaging (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-oslo.messaging (Ubuntu)
Assignee: (unassigned) => Seyeong Kim (seyeongkim)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** 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"
###
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
** 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 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.
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.
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.
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"
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
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
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
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
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
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:
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:
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
1 - 100 of 769 matches
Mail list logo
