** Changed in: cloud-archive
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to vlan in Ubuntu.
https://bugs.launchpad.net/bugs/1856279
Title:
demote vlan to universe in 20.04
To manage
This bug was fixed in the package libvirt - 4.0.0-1ubuntu8.15~cloud0
---
libvirt (4.0.0-1ubuntu8.15~cloud0) xenial-queens; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
libvirt (4.0.0-1ubuntu8.15) bionic; urgency=medium
.
*
It doesn't appear to be part of the openstack dependency chain so it's
not needed by openstack.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to python-tx-tftp in Ubuntu.
https://bugs.launchpad.net/bugs/1869366
Title:
RM: python-tx-tftp
I've just released 1.3.1-1ubuntu10.29~cloud0 to mitaka-updates.
** Changed in: cloud-archive/mitaka
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to libvirt in Ubuntu.
According to [1], cinder autopkgtests ran successfully for
2:14.0.2-0ubuntu1, therefore I'm going to tag this as verified for disco
(autopkgtest fix was provided in version 2:14.0.1-0ubuntu3).
[1]
http://autopkgtest.ubuntu.com/packages/c/cinder/disco/amd64
** Also affects: cloud-archive/queens
Importance: Undecided
Status: New
** Changed in: cloud-archive/queens
Status: New => Incomplete
** Changed in: cloud-archive/queens
Importance: Undecided => Low
** Changed in: cloud-archive
Status: New => Fix Released
--
You
** Changed in: nova (Ubuntu)
Status: New => Triaged
** Changed in: cloud-archive
Status: New => Triaged
** Changed in: cloud-archive
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to vlan in
@Christian, I've added a card for verification of bug 1838691 to our
trello board.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1845321
Title:
cinder-daemons autopkgtest must override
This is fixed in Disco (Stein) as of cinder 2:14.0.1-0ubuntu3
** Changed in: cinder (Ubuntu Disco)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
Thanks for checking! Disco fix is in the unapproved queue:
https://launchpad.net/ubuntu/disco/+queue?queue_state=1_text=cinder
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1845321
Title:
@Christian, thanks for the patch! I'll get that applied and uploaded.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1845321
Title:
cinder-daemons autopkgtest must override driver to use
I've uploaded 2:14.0.1-0ubuntu3 to the disco unapproved queue which
includes 2:14.0.1-0ubuntu2 and provides a fix for disco autopkgtest
failure. Note that autopkgtests were successfully executed as this was
uploaded via https://bileto.ubuntu.com/#/ticket/3813.
--
You received this bug
This is also fixed in the latest upload to eoan.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1845321
Title:
cinder-daemons autopkgtest must override driver to use pymysql
To manage
Public bug reported:
In eoan python-swiftclient binary package has been removed. Once
simplestreams drops it's BD it should allow python-swiftclient source
package to migrate out of eoan-proposed.
** Affects: simplestreams (Ubuntu)
Importance: High
Status: Confirmed
--
You
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.40~cloud0
---
qemu (1:2.5+dfsg-5ubuntu10.40~cloud0) trusty-mitaka; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
qemu (1:2.5+dfsg-5ubuntu10.40) xenial; urgency=medium
.
* Restore patches that
Hello Dan, or anyone else affected,
Accepted qemu into mitaka-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
** Also affects: cloud-archive/mitaka
Importance: Undecided
Status: New
** Changed in: cloud-archive/mitaka
Status: New => In Progress
** Changed in: cloud-archive/mitaka
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: cloud-archive
Assignee:
This bug was fixed in the package qemu - 1:2.8+dfsg-3ubuntu2.9~cloud6
---
qemu (1:2.8+dfsg-3ubuntu2.9~cloud6) xenial-ocata; urgency=medium
.
* SECURITY UPDATE: Add support for exposing md-clear functionality
to guests
- d/p/ubuntu/enable-md-clear.patch
-
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
Hello Dan, or anyone else affected,
Accepted qemu into ocata-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
** Also affects: cloud-archive/mitaka
Importance: Undecided
Status: New
** Also affects: cloud-archive/ocata
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Invalid
** Changed in: cloud-archive/ocata
Status: New => Triaged
**
This bug was fixed in the package qemu - 1:2.8+dfsg-3ubuntu2.9~cloud5.1
---
qemu (1:2.8+dfsg-3ubuntu2.9~cloud5.1) xenial-ocata; urgency=medium
.
* d/p/lp1823458/add-VirtIONet-vhost_stopped-flag-to-prevent-multiple.patch,
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.37~cloud0
---
qemu (1:2.5+dfsg-5ubuntu10.37~cloud0) trusty-mitaka; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
qemu (1:2.5+dfsg-5ubuntu10.37) xenial; urgency=medium
.
*
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
Hello Dan, or anyone else affected,
Accepted qemu into mitaka-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
Hello Dan, or anyone else affected,
Accepted qemu into ocata-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
** Also affects: cloud-archive/ocata
Importance: Undecided
Status: New
** Changed in: cloud-archive/ocata
Importance: Undecided => Medium
** Changed in: cloud-archive/ocata
Status: New => Triaged
** Changed in: cloud-archive
Status: New => Fix Released
--
You
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/mitaka
Importance: Undecided
Status: New
** Changed in: cloud-archive/mitaka
Importance: Undecided => Medium
** Changed in: cloud-archive/mitaka
Status: New => Triaged
Hello Heitor, or anyone else affected,
Accepted qemu into mitaka-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
Hello Heitor, or anyone else affected,
Accepted qemu into ocata-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
** Changed in: cloud-archive/mitaka
Importance: Undecided => High
** Changed in: cloud-archive/mitaka
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1818880
** Changed in: cloud-archive/pike
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1818880
Title:
Deadlock when detaching network interface
To manage
Heiter, please if fixes are needed for ocata or pike can you provide us
with patches? We need to be careful not to skip cloud archive releases
(ie. if this is fixed in xenial but not the ocata and pike cloud
archive).
--
You received this bug notification because you are a member of Ubuntu
I've just accepted qemu version 1:2.11+dfsg-1ubuntu7.12~cloud0 into
queens-proposed however the changelog doesn't mention (LP: #1818880)
anywhere. Seeing that bionic is marked as fix released I assume queens
can be marked as fix released.
** Changed in: cloud-archive/queens
Status: Triaged
The Stein cloud archive has qemu 1:3.1+dfsg-2ubuntu3~cloud0 which
corresponds to the current version in disco, so I'm marking this as fix
released for Stein.
** Changed in: cloud-archive/stein
Status: Triaged => Fix Released
--
You received this bug notification because you are a member
We don't have qemu in the rocky cloud archive so this is fixed via
bionic.
** Changed in: cloud-archive/rocky
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
This is fixed in rocky with keystone version 2:14.0.1-0ubuntu3.
** Changed in: keystone/rocky
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to python-ldappool in Ubuntu.
** Also affects: cloud-archive/ocata
Importance: Undecided
Status: New
** Also affects: cloud-archive/pike
Importance: Undecided
Status: New
** Changed in: cloud-archive/stein
Importance: Undecided => High
** Changed in: cloud-archive/stein
Status: Confirmed =>
** Changed in: cloud-archive/stein
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to python-ldappool in Ubuntu.
https://bugs.launchpad.net/bugs/1798184
Title:
[SRU] PY3: python3-ldap does not
This bug was fixed in the package keystone - 2:14.0.1-0ubuntu3~cloud0
---
keystone (2:14.0.1-0ubuntu3~cloud0) bionic-rocky; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
keystone (2:14.0.1-0ubuntu3) cosmic; urgency=medium
.
* d/control,
This has been verified successfully on cosmic-proposed and rocky-
proposed. I've added testing details to the other bug that is
accompanying this fix at:
https://bugs.launchpad.net/keystone/+bug/1820333/comments/7
https://bugs.launchpad.net/keystone/+bug/1820333/comments/8
** Tags removed:
** Changed in: cloud-archive
Status: Fix Released => Fix Committed
** Changed in: cloud-archive/rocky
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to python-ldappool in Ubuntu.
Verification on cosmic-proposed failed (See bug in comment #19). I'm
working on a fix for that.
** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-failed verification-failed-cosmic
--
You received this bug notification because you are a member of Ubuntu
Targeting qemu for input from that end.
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1816170
Title:
KVM
** Summary changed:
- PY3: python3-ldap does not allow bytes for DN/RDN/field names
+ [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names
** Description changed:
+ [Impact]
+ Keystone LDAP backend doesn't work for PY3.
+
Under Python 2, python-ldap uses bytes by default.
** Changed in: python-ldappool (Ubuntu Disco)
Status: Triaged => Fix Released
** Changed in: keystone (Ubuntu Disco)
Status: Triaged => Fix Released
** Changed in: cloud-archive/stein
Status: Triaged => Fix Released
--
You received this bug notification because you are a
This is fixed for nova in 2:19.0.0~b1~git2019013113.33aad0fe41-0ubuntu2.
** Changed in: nova (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to websockify in Ubuntu.
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nova (Ubuntu)
Status: New => Triaged
** Changed in: nova (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server, which is
Marked as fix released for upstream ldappool as this is fixed in 2.3.1
** Also affects: keystone (Ubuntu)
Importance: Undecided
Status: New
** Also affects: keystone (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: keystone (Ubuntu Cosmic)
Importance:
Ok no problem, and thank you for responding back with details.
** Changed in: python-boto (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to python-boto in Ubuntu.
Architectures trimmed for formatting:
$ rmadison libssl1.1
libssl1.1 | 1.1.0g-2ubuntu4 | bionic
libssl1.1 | 1.1.0g-2ubuntu4.3 | bionic-security
libssl1.1 | 1.1.0g-2ubuntu4.3 | bionic-updates
libssl1.1 | 1.1.1-1ubuntu2 | cosmic
libssl1.1 | 1.1.1-1ubuntu2.1 | cosmic-security
libssl1.1 |
I'm not sure where libssl1.1 version
1.1.1a-2+ubuntu18.04.1+deb.sury.org+1 is coming from.
Where are you getting libssl1.1 from? What does 'apt policy libssl1.1'
show?
Here are the current versios in bionic+ Ubuntu archives:
$ rmadison libssl1.1
libssl1.1 | 1.1.0g-2ubuntu4 | bionic
Hi tomtom,
Thanks for reporting this and making Ubuntu better. I was able to
install python-boto 2.44.0-1ubuntu2 successfully with apt. Is this still
a problem if you use apt to install from the bionic archive?
Thanks,
Corey
** Changed in: python-boto (Ubuntu)
Status: New => Incomplete
** Changed in: qemu (Ubuntu)
Status: Expired => New
** Changed in: ceph (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1674481
Title:
memory
Hi again Slawek,
Just for some further details, the new versions of keepalived came about due
to:
https://bugs.launchpad.net/cloud-archive/+bug/1744062. In particular, see
https://bugs.launchpad.net/cloud-archive/+bug/1744062/comments/14 for the
descriptions of the commits that are included
Slawek, Thank you for reporting this issue. The new keepalived versions
include a cherry-pick of
https://github.com/acassen/keepalived/commit/e90a633c34fbe6ebbb891aa98bf29ce579b8b45c.
I'm currently building a new xenial version of keepalived in a PPA for
testing purposes with this patch removed.
Slawek, for stable/queens, can you confirm the version of keepalived
that your tests are running with? The queens cloud archive has
keepalived 1:1.3.9-1ubuntu0.18.04.1~cloud0, however I'm wondering if
you're running with the base xenial version of
1:1.2.24-1ubuntu0.16.04.1.
--
You received this
This bug was fixed in the package keepalived - 1:1.3.9-1ubuntu0.18.04.1~cloud0
---
keepalived (1:1.3.9-1ubuntu0.18.04.1~cloud0) xenial-queens; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
keepalived (1:1.3.9-1ubuntu0.18.04.1) bionic; urgency=medium
.
*
The verification of the Stable Release Update for keepalived has
completed successfully and the package has now been released to
-updates. In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update
The verification of the Stable Release Update for keepalived has
completed successfully and the package has now been released to
-updates. In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update
This bug was fixed in the package keepalived - 1:1.2.24-1ubuntu0.16.04.1~cloud0
---
keepalived (1:1.2.24-1ubuntu0.16.04.1~cloud0) trusty-mitaka; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
keepalived (1:1.2.24-1ubuntu0.16.04.1) xenial; urgency=medium
This bug was fixed in the package keepalived - 1:1.2.24-1ubuntu0.16.04.1~cloud0
---
keepalived (1:1.2.24-1ubuntu0.16.04.1~cloud0) trusty-mitaka; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
keepalived (1:1.2.24-1ubuntu0.16.04.1) xenial; urgency=medium
The verification of the Stable Release Update for keepalived has
completed successfully and the package has now been released to
-updates. In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update
Hello Corey, or anyone else affected,
Accepted keepalived into mitaka-proposed. The package will build now and
be available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
Hello Corey, or anyone else affected,
Accepted keepalived into mitaka-proposed. The package will build now and
be available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
I've just asked for a review in #ubuntu-release.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1744062
Title:
[SRU] L3 HA: multiple agents are active at the same time
To manage
I've uploaded keepalived 1:1.2.24-1ubuntu0.16.04.1 to the xenial review
queue where it is awaiting SRU team review. This xenial fix is paired
with https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1783583.
--
You received this bug notification because you are a member of Ubuntu
Server,
I've uploaded keepalived 1:1.2.24-1ubuntu0.16.04.1 to the xenial review
queue where it is awaiting SRU team review.
** Also affects: keepalived (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: keepalived (Ubuntu)
Status: New => Invalid
** Changed in: keepalived
** No longer affects: cloud-archive/pike
** No longer affects: cloud-archive/ocata
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1744062
Title:
[SRU] L3 HA: multiple agents are
Public bug reported:
[Impact]
This release sports mostly bug-fixes and we would like to make sure all of our
supported customers have access to these improvements.
[Test Case]
The following SRU process was followed:
https://wiki.ubuntu.com/OpenStackUpdates
In order to avoid regression of
I've deleted the keepalived versions from ocata-staging and pike-
staging. We should be able to fix this in xenial with a new stable point
release and patch backport.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to keepalived in Ubuntu.
Hello Corey, or anyone else affected,
Accepted keepalived into queens-proposed. The package will build now and
be available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
I've uploaded new versions of keepalived to cosmic, bionic (awaiting SRU
team review), pike-staging, and ocata-staging. I need to confirm with
other cloud archive admins that this is ok to backport to pike/ocata
cloud archives prior to promoting to pike-proposed/ocata-proposed. In
the mean time if
Moving back to New for neutron for the time being since we think this
may be fixed in keepalived.
** Description changed:
+ [Impact]
+
This is the same issue reported in
https://bugs.launchpad.net/neutron/+bug/1731595, however that is marked
as 'Fix Released' and the issue is still
** Summary changed:
- L3 HA: multiple agents are active at the same time
+ [SRU] L3 HA: multiple agents are active at the same time
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to keepalived in Ubuntu.
It appears the following commits are required to fix this for
keepalived:
commit e90a633c34fbe6ebbb891aa98bf29ce579b8b45c
Author: Quentin Armitage
Date: Fri Dec 15 21:14:24 2017 +
Fix removing left-over addresses if keepalived aborts
Issue #718 reported that if keepalived
As reported by Xav in https://bugs.launchpad.net/ubuntu/+bug/1731595:
"Comment for the folks that are noticing this as 'fix released' but
still affected - see
https://github.com/acassen/keepalived/commit/e90a633c34fbe6ebbb891aa98bf29ce579b8b45c
for the rest of this fix, we need keepalived to be
Since this bug is already marked as fix released for the cloud-archive,
let's please track this issue in the following bug:
https://bugs.launchpad.net/ubuntu/+bug/1744062
** No longer affects: keepalived (Ubuntu)
** No longer affects: keepalived (Ubuntu Xenial)
** No longer affects: keepalived
Xav, I just checked and the patch you referenced can be backported
fairly cleanly to at least keepalived 1:1.2.19-1 (xenial/mitaka) and
above.
** Changed in: keepalived (Ubuntu Xenial)
Importance: Undecided => Critical
** Changed in: keepalived (Ubuntu Xenial)
Status: New => Triaged
** No longer affects: keepalived (Ubuntu Zesty)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1731595
Title:
L3 HA: multiple agents are active at the same time
To manage
** Also affects: keepalived (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: keepalived (Ubuntu Artful)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1731595
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
This bug was fixed in the package qemu - 1:2.10+dfsg-0ubuntu3.8~cloud1
---
qemu (1:2.10+dfsg-0ubuntu3.8~cloud1) xenial-pike; urgency=medium
.
* d/p/s390x-fix-storage-attrs-migration-for-non-small-guests.patch:
Backported from upstream 2.11.1 release to enable successful
Thanks for testing. Tagging verification-pike-done according to comment
#4 results.
** Tags added: verification-pike-done
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1779162
Title:
Hello bugproxy, or anyone else affected,
Accepted qemu into pike-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
** Changed in: cloud-archive/pike
Assignee: (unassigned) => Corey Bryant (corey.bryant)
** Changed in: cloud-archive
Assignee: Corey Bryant (corey.bryant) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qem
This would be a Build-Depend and no longer needed. Thanks.
** Changed in: python-nosehtmloutput (Ubuntu)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to python-nosehtmloutput in Ubuntu.
-compute-kvm -> ipxe-qemu to ensure that required
ROM's are installed for all architectures (LP: #1754015).
.
[ Corey Bryant ]
* New stable point release for OpenStack Pike (LP: #1758046).
* d/p/aarch64-libvirt-compat.patch: Rebased and updated to mock
os.path.exists return va
Nish,
Thanks very much for the update. I successfully performed some testing
with a keystone cluster. The results are in the following paste:
https://paste.ubuntu.com/p/Wtwnyvn8XZ/
Thanks,
Corey
--
You received this bug notification because you are a member of Ubuntu
Server, which is
Regression testing for trusty-mitaka has successfully passed:
==
Totals
==
Ran: 102 tests in 1037.8303 sec.
- Passed: 94
- Skipped: 8
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each test: 622.6697 sec.
** Tags removed: verification-mitaka-needed
** Changed in: cloud-archive/ocata
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1744882
Title:
Add SPEC_CTRL and IBRS changes
To manage
I've marked this incomplete until we can recreate it.
** Changed in: python-cryptography (Ubuntu Bionic)
Status: Fix Released => Incomplete
** No longer affects: python-cryptography (Ubuntu Artful)
** No longer affects: python-cryptography (Ubuntu)
** No longer affects:
Hi Graham,
I don't think this is a dependency issue. I'm going to back out the
changes I made earlier as I pulled the trigger too quickly with those.
What would be good to know is what 'buf' is set to in your scenario.
Here's a little script that hits the same path your traceback goes down.
It
Graham, thanks that would be great. This will get you the new version:
sudo add-apt-repository ppa:ubuntu-cloud-archive/queens-staging
sudo apt update
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cryptography in Ubuntu.
Graham, would you mind testing with a PPA? If you can let me know what
release combination you're working with and I can get a PPA built.
I've unsubscribed the SRU team for now as Tristan mentioned in the
Debian bug that he didn't immediately see what the stack trace in the
Ubuntu bug report has
I've uploaded a new fixed version of the python-cryptography to all
affected releases. The Xenial (Mitaka) and Artful (Pike) versions will
need to be reviewed by the SRU team before they are accepted into
proposed and backported to the cloud-archive.
--
You received this bug notification because
I think our long-term fix will come from the Debian maintainer's
approach to adding dependencies. I'm going to fix this in Ubuntu for now
by adding python-cffi to debian/control Depends.
** Summary changed:
- keystone requires cffi to be installed for fernat tokens
+ python-cryptography missing
I've opened the following bug against the Debian package:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892112
** Bug watch added: Debian Bug tracker #892112
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892112
--
You received this bug notification because you are a member of Ubuntu
1 - 100 of 467 matches
Mail list logo
