| 2018-05-16 19:43:39 |
Jason Hobbs |
bug |
|
|
added bug |
| 2018-05-16 19:43:39 |
Jason Hobbs |
attachment added |
|
juju-crashdump-arm64.tar.gz https://bugs.launchpad.net/bugs/1771662/+attachment/5140456/+files/juju-crashdump-arm64.tar.gz |
|
| 2018-05-16 19:44:31 |
Jason Hobbs |
description |
After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'
In my /var/log/nova/nova-compute.log
I'm not sure why this is happening - I don't use enP2p1s0f1 for anything.
Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/
The same bundle works fine for xenial-queens, with the source changed to the cloud-archive. |
After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'
In my /var/log/nova/nova-compute.log
I'm not sure why this is happening - I don't use enP2p1s0f1 for anything.
Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/
The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms. |
|
| 2018-05-16 19:49:03 |
Jason Hobbs |
bug |
|
|
added subscriber Canonical Field High |
| 2018-05-16 19:56:40 |
Jason Hobbs |
description |
After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'
In my /var/log/nova/nova-compute.log
I'm not sure why this is happening - I don't use enP2p1s0f1 for anything.
Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/
The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms. |
After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'
In my /var/log/nova/nova-compute.log
I'm not sure why this is happening - I don't use enP2p1s0f1 for anything.
Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/
The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms.
This is with juju 2.4 beta 2. |
|
| 2018-05-16 20:28:47 |
Jason Hobbs |
description |
After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'
In my /var/log/nova/nova-compute.log
I'm not sure why this is happening - I don't use enP2p1s0f1 for anything.
Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/
The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms.
This is with juju 2.4 beta 2. |
After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'
In my /var/log/nova/nova-compute.log
I'm not sure why this is happening - I don't use enP2p1s0f1 for anything.
There are a lot of interesting messages about that interface in syslog:
http://paste.ubuntu.com/p/8WT8NqCbCf/
Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/
The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms.
This is with juju 2.4 beta 2. |
|
| 2018-05-17 13:53:10 |
Jason Hobbs |
description |
After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'
In my /var/log/nova/nova-compute.log
I'm not sure why this is happening - I don't use enP2p1s0f1 for anything.
There are a lot of interesting messages about that interface in syslog:
http://paste.ubuntu.com/p/8WT8NqCbCf/
Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/
The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms.
This is with juju 2.4 beta 2. |
After deploying openstack on arm64 using bionic and queens (clean deploy of queens on clean 18.04 - no upgrade), no hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'
In my /var/log/nova/nova-compute.log
I'm not sure why this is happening - I don't use enP2p1s0f1 for anything.
There are a lot of interesting messages about that interface in syslog:
http://paste.ubuntu.com/p/8WT8NqCbCf/
Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/
The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms.
This is with juju 2.4 beta 2. |
|
| 2018-05-17 14:24:28 |
Jason Hobbs |
description |
After deploying openstack on arm64 using bionic and queens (clean deploy of queens on clean 18.04 - no upgrade), no hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'
In my /var/log/nova/nova-compute.log
I'm not sure why this is happening - I don't use enP2p1s0f1 for anything.
There are a lot of interesting messages about that interface in syslog:
http://paste.ubuntu.com/p/8WT8NqCbCf/
Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/
The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms.
This is with juju 2.4 beta 2. |
After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'
In my /var/log/nova/nova-compute.log
I'm not sure why this is happening - I don't use enP2p1s0f1 for anything.
There are a lot of interesting messages about that interface in syslog:
http://paste.ubuntu.com/p/8WT8NqCbCf/
Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/
The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms.
This thread has some related info, I think:
https://www.spinics.net/linux/fedora/libvir/msg160975.html
This is with juju 2.4 beta 2. |
|
| 2018-05-17 14:44:20 |
Christian Ehrhardt |
bug task added |
|
libvirt (Ubuntu) |
|
| 2018-05-17 14:51:13 |
Jason Hobbs |
description |
After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'
In my /var/log/nova/nova-compute.log
I'm not sure why this is happening - I don't use enP2p1s0f1 for anything.
There are a lot of interesting messages about that interface in syslog:
http://paste.ubuntu.com/p/8WT8NqCbCf/
Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/
The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms.
This thread has some related info, I think:
https://www.spinics.net/linux/fedora/libvir/msg160975.html
This is with juju 2.4 beta 2. |
After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'
In my /var/log/nova/nova-compute.log
I'm not sure why this is happening - I don't use enP2p1s0f1 for anything.
There are a lot of interesting messages about that interface in syslog:
http://paste.ubuntu.com/p/8WT8NqCbCf/
Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/
The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms.
This thread has some related info, I think:
https://www.spinics.net/linux/fedora/libvir/msg160975.html
This is with juju 2.4 beta 2.
Package versions on affected system: http://paste.ubuntu.com/p/yfQH3KJzng/ |
|
| 2018-05-17 15:09:56 |
Ryan Beisner |
charm-nova-compute: status |
New |
Invalid |
|
| 2018-05-17 17:39:27 |
Jason Hobbs |
removed subscriber Canonical Field High |
|
|
|
| 2018-05-17 17:44:59 |
Steve Langasek |
bug |
|
|
added subscriber Steve Langasek |
| 2018-05-17 18:04:18 |
Ryan Harper |
bug |
|
|
added subscriber Ryan Harper |
| 2018-05-17 19:36:30 |
Jason Hobbs |
attachment added |
|
bionic-logs.tgz https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+attachment/5140998/+files/bionic-logs.tgz |
|
| 2018-05-17 19:42:08 |
Jason Hobbs |
attachment added |
|
bionic-var-log-and-etc.tgz https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+attachment/5141000/+files/bionic-var-log-and-etc.tgz |
|
| 2018-05-18 07:14:54 |
Christian Ehrhardt |
libvirt (Ubuntu): status |
New |
Incomplete |
|
| 2018-05-22 20:26:21 |
Jason Hobbs |
attachment added |
|
xenial-logs-1771662.tgz https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+attachment/5142976/+files/xenial-logs-1771662.tgz |
|
| 2018-05-22 20:26:41 |
Jason Hobbs |
charm-nova-compute: status |
Invalid |
New |
|
| 2018-05-22 20:26:43 |
Jason Hobbs |
libvirt (Ubuntu): status |
Incomplete |
New |
|
| 2018-05-23 20:38:26 |
Ryan Beisner |
charm-nova-compute: status |
New |
Opinion |
|
| 2018-06-07 19:09:32 |
Ryan Beisner |
charm-nova-compute: status |
Opinion |
Incomplete |
|
| 2018-06-27 16:55:54 |
Chris Gregan |
bug |
|
|
added subscriber Canonical Field High |
| 2018-06-28 03:27:52 |
David Britton |
libvirt (Ubuntu): status |
New |
Incomplete |
|
| 2018-06-29 11:22:33 |
Frode Nordahl |
attachment added |
|
libvirt-debug.log https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+attachment/5157735/+files/libvirt-debug.log |
|
| 2018-06-29 11:23:32 |
Frode Nordahl |
charm-nova-compute: status |
Incomplete |
Invalid |
|
| 2018-06-29 11:24:04 |
Frode Nordahl |
bug task added |
|
nova |
|
| 2018-07-02 14:40:15 |
Ryan Beisner |
charm-nova-compute: assignee |
|
Frode Nordahl (fnordahl) |
|
| 2018-07-02 18:50:27 |
Ryan Beisner |
summary |
libvirtError: Node device not found: no node device with matching name |
[bionic] libvirtError: Node device not found: no node device with matching name |
|
| 2018-07-24 15:58:55 |
mahmoh |
bug watch added |
|
https://bugs.linaro.org/show_bug.cgi?id=3778 |
|
| 2018-09-27 14:30:55 |
dann frazier |
attachment added |
|
libvirt-no-thunderx-switchdev.debdiff https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+attachment/5193615/+files/libvirt-no-thunderx-switchdev.debdiff |
|
| 2018-09-27 16:20:21 |
Ubuntu Foundations Team Bug Bot |
tags |
cdo-qa foundations-engine zion |
cdo-qa foundations-engine patch zion |
|
| 2018-10-10 08:40:58 |
Andrew Cloke |
bug |
|
|
added subscriber Andrew Cloke |
| 2018-10-23 19:01:11 |
dann frazier |
bug |
|
|
added subscriber Radosław Biernacki |
| 2019-01-23 15:19:49 |
dann frazier |
libvirt (Ubuntu): status |
Incomplete |
In Progress |
|
| 2019-01-23 16:01:44 |
dann frazier |
nominated for series |
|
Ubuntu Disco |
|
| 2019-01-23 16:01:44 |
dann frazier |
bug task added |
|
libvirt (Ubuntu Disco) |
|
| 2019-01-23 16:01:44 |
dann frazier |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-01-23 16:01:44 |
dann frazier |
bug task added |
|
libvirt (Ubuntu Cosmic) |
|
| 2019-01-23 16:01:44 |
dann frazier |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-01-23 16:01:44 |
dann frazier |
bug task added |
|
libvirt (Ubuntu Bionic) |
|
| 2019-01-23 16:02:50 |
dann frazier |
libvirt (Ubuntu Disco): status |
In Progress |
Triaged |
|
| 2019-01-23 16:02:59 |
dann frazier |
nova: status |
New |
Invalid |
|
| 2019-01-23 16:03:03 |
dann frazier |
libvirt (Ubuntu Cosmic): status |
New |
Triaged |
|
| 2019-01-23 16:03:05 |
dann frazier |
libvirt (Ubuntu Bionic): status |
New |
Triaged |
|
| 2019-01-23 16:37:01 |
Christian Ehrhardt |
tags |
cdo-qa foundations-engine patch zion |
cdo-qa foundations-engine libvirt-19.04 patch zion |
|
| 2019-01-23 16:37:51 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~libvirt-maintainers/ubuntu/+source/libvirt/+git/libvirt/+merge/361960 |
|
| 2019-01-24 16:31:49 |
mahmoh |
bug |
|
|
added subscriber mahmoh |
| 2019-01-27 19:28:31 |
Launchpad Janitor |
libvirt (Ubuntu Disco): status |
Triaged |
Fix Released |
|
| 2019-01-31 09:12:12 |
Christian Ehrhardt |
description |
After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'
In my /var/log/nova/nova-compute.log
I'm not sure why this is happening - I don't use enP2p1s0f1 for anything.
There are a lot of interesting messages about that interface in syslog:
http://paste.ubuntu.com/p/8WT8NqCbCf/
Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/
The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms.
This thread has some related info, I think:
https://www.spinics.net/linux/fedora/libvir/msg160975.html
This is with juju 2.4 beta 2.
Package versions on affected system: http://paste.ubuntu.com/p/yfQH3KJzng/ |
[Impact]
* Libvirt has had the assumption that every VF (virtual function) will
have a PF (physical function) assigned, but that does not hold true on
some special Hardware like the Cavium ThunderX
* Dannf helped some patches initially from Linaro to be accepted upstream
and those we'd want to backport to Bionic and Cosmic
[Test Case]
* Use VF passthrough to a KVM guest on Cavium thunderX
* This needs plenty of setup and special HW, but Jason Hobbs & Dannf are
willing to do the verification in our test lab.
[Regression Potential]
* Review hasn't spotted any issues, but in theory there could be negative
effects to PF/VF pass-through cases. There is some code cleanup
associated that should not, but might cause issues on that.
I'd ask Jason to also run PF/VF workload on the PPA/SRU with other
Hardware as well (like our x86 test environment) to be sure of that
being ok.
[Other Info]
* n/a
---
After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'
In my /var/log/nova/nova-compute.log
I'm not sure why this is happening - I don't use enP2p1s0f1 for anything.
There are a lot of interesting messages about that interface in syslog:
http://paste.ubuntu.com/p/8WT8NqCbCf/
Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/
The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms.
This thread has some related info, I think:
https://www.spinics.net/linux/fedora/libvir/msg160975.html
This is with juju 2.4 beta 2.
Package versions on affected system: http://paste.ubuntu.com/p/yfQH3KJzng/ |
|
| 2019-01-31 16:33:06 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/362544 |
|
| 2019-01-31 16:33:30 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/362545 |
|
| 2019-02-05 15:52:18 |
dann frazier |
description |
[Impact]
* Libvirt has had the assumption that every VF (virtual function) will
have a PF (physical function) assigned, but that does not hold true on
some special Hardware like the Cavium ThunderX
* Dannf helped some patches initially from Linaro to be accepted upstream
and those we'd want to backport to Bionic and Cosmic
[Test Case]
* Use VF passthrough to a KVM guest on Cavium thunderX
* This needs plenty of setup and special HW, but Jason Hobbs & Dannf are
willing to do the verification in our test lab.
[Regression Potential]
* Review hasn't spotted any issues, but in theory there could be negative
effects to PF/VF pass-through cases. There is some code cleanup
associated that should not, but might cause issues on that.
I'd ask Jason to also run PF/VF workload on the PPA/SRU with other
Hardware as well (like our x86 test environment) to be sure of that
being ok.
[Other Info]
* n/a
---
After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'
In my /var/log/nova/nova-compute.log
I'm not sure why this is happening - I don't use enP2p1s0f1 for anything.
There are a lot of interesting messages about that interface in syslog:
http://paste.ubuntu.com/p/8WT8NqCbCf/
Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/
The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms.
This thread has some related info, I think:
https://www.spinics.net/linux/fedora/libvir/msg160975.html
This is with juju 2.4 beta 2.
Package versions on affected system: http://paste.ubuntu.com/p/yfQH3KJzng/ |
[Impact]
* Libvirt has had the assumption that every VF (virtual function) will
have a PF (physical function) assigned, but that does not hold true on
some special Hardware like the Cavium ThunderX
* Dannf helped some patches initially from Linaro to be accepted upstream
and those we'd want to backport to Bionic and Cosmic
[Test Case]
* Verify that virsh nodedev-list shows the onboard NICs:
$ sudo virsh nodedev-list | grep ^net
net_enP2p1s0f1_42_ca_74_64_88_75
net_enP2p1s0f2_42_ca_74_64_88_76
net_enP2p1s0f3_42_ca_74_64_88_77
* This needs plenty of setup and special HW, but Jason Hobbs & Dannf are
willing to do the verification in our test lab.
[Regression Potential]
* Review hasn't spotted any issues, but in theory there could be negative
effects to PF/VF pass-through cases. There is some code cleanup
associated that should not, but might cause issues on that.
I'd ask Jason to also run PF/VF workload on the PPA/SRU with other
Hardware as well (like our x86 test environment) to be sure of that
being ok.
[Other Info]
* n/a
---
After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'
In my /var/log/nova/nova-compute.log
I'm not sure why this is happening - I don't use enP2p1s0f1 for anything.
There are a lot of interesting messages about that interface in syslog:
http://paste.ubuntu.com/p/8WT8NqCbCf/
Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/
The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms.
This thread has some related info, I think:
https://www.spinics.net/linux/fedora/libvir/msg160975.html
This is with juju 2.4 beta 2.
Package versions on affected system: http://paste.ubuntu.com/p/yfQH3KJzng/ |
|
| 2019-02-27 23:28:31 |
Brian Murray |
libvirt (Ubuntu Cosmic): status |
Triaged |
Fix Committed |
|
| 2019-02-27 23:28:35 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-02-27 23:28:37 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2019-02-27 23:28:43 |
Brian Murray |
tags |
cdo-qa foundations-engine libvirt-19.04 patch zion |
cdo-qa foundations-engine libvirt-19.04 patch verification-needed verification-needed-cosmic zion |
|
| 2019-02-27 23:33:23 |
Brian Murray |
libvirt (Ubuntu Bionic): status |
Triaged |
Fix Committed |
|
| 2019-02-27 23:33:32 |
Brian Murray |
tags |
cdo-qa foundations-engine libvirt-19.04 patch verification-needed verification-needed-cosmic zion |
cdo-qa foundations-engine libvirt-19.04 patch verification-needed verification-needed-bionic verification-needed-cosmic zion |
|
| 2019-02-28 17:57:39 |
dann frazier |
tags |
cdo-qa foundations-engine libvirt-19.04 patch verification-needed verification-needed-bionic verification-needed-cosmic zion |
cdo-qa foundations-engine libvirt-19.04 patch verification-done-bionic verification-done-cosmic verification-needed zion |
|
| 2019-02-28 17:57:48 |
dann frazier |
tags |
cdo-qa foundations-engine libvirt-19.04 patch verification-done-bionic verification-done-cosmic verification-needed zion |
cdo-qa foundations-engine libvirt-19.04 patch verification-done verification-done-bionic verification-done-cosmic zion |
|
| 2019-03-07 09:52:29 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-03-07 10:02:29 |
Launchpad Janitor |
libvirt (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
| 2019-03-07 10:05:14 |
Launchpad Janitor |
libvirt (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2022-07-11 14:10:17 |
liguang |
bug |
|
|
added subscriber liguang |
