Apparently this is still happening in Jammy for some reason (maybe a
regression), as according to this [1] bug report claiming that this bug
is the cause of it.
This is the command that I run to hit it (doesn't need anything in
particular for the command to work, can run anywhere such as a fresh
** Also affects: ssl-cert (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: hplip (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: ubuntu
Importance: Undecided
Status: New
** Also affects: Ubuntu Mantic
Importance: Undecided
Status: New
** Also affects: Ubuntu Focal
Importance: Undecided
Status: New
** Also affects: Ubuntu Jammy
Importance: Undecided
Status: New
**
SRU for bug LP#1728031 is now ready as well so it can be picked up and
merged with this one
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055409
Title:
[SRU] config
** Patch added: "lp2055409-focal.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/2055409/+attachment/5758154/+files/lp2055409-focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp2055409-focal-victoria.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/2055409/+attachment/5758153/+files/lp2055409-focal-victoria.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp2055409-focal-wallaby.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/2055409/+attachment/5758152/+files/lp2055409-focal-wallaby.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp2055409-focal-xena.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/2055409/+attachment/5758151/+files/lp2055409-focal-xena.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
actually, this one needs to be SRU'ed back to Ussuri, while LP#1728031
is up to yoga
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055409
Title:
[SRU] config
I have also just fixed bug LP#1728031 and backporting that all the way
to yoga, to it is best to wait for that and combine with a single SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055409
The tag 23.0.1 for zed has been created, so I deleted the jammy-zed
attachment
** Attachment removed: "lp2055409-jammy-zed.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/2055409/+attachment/5752375/+files/lp2055409-jammy-zed.debdiff
--
You received this bug notification because you
** Patch added: "lp2055409-jammy.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/2055409/+attachment/5752376/+files/lp2055409-jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp2055409-lunar.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/2055409/+attachment/5752374/+files/lp2055409-lunar.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp2055409-jammy-zed.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/2055409/+attachment/5752375/+files/lp2055409-jammy-zed.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp2055409-mantic.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/2055409/+attachment/5752373/+files/lp2055409-mantic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As I was creating the debdiffs, I faced some conflicts (just unit tests
though) in Zed due to the tag being very old. I pinged the horizon PTL
and he updated the hash for the next tag. Apparently we could have a new
zed point release very soon [1].
I am attaching all debdiffs either way.
[1]
Fix has merged in Caracal/Noble cycle, has been backported upstream to
Bobcat, Antelope and Zed. It needs to have SRU'ed back to Ussuri.
Bobcat, Antelope and Zed could have Point Releases (as long as there one
new tag upstream), but for Yoga, Xena, Wallaby, Victoria and Ussuri it
will necessary
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => Rodrigo Barbieri (rodrigo-barbieri2010)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904580
Title:
Permissions 0644 for '/var/lib/n
** Tags removed: verification-ussuri-needed
** 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/1948914
Title:
[SRU] Ussuri stable releases
To manage notifications about this bug go
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: cloud-archive
Importance: Undecided
** Attachment added: "1893263_stein_validation.txt"
https://bugs.launchpad.net/nova/+bug/1893263/+attachment/5475444/+files/1893263_stein_validation.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "1893263_train_validation.txt"
https://bugs.launchpad.net/nova/+bug/1893263/+attachment/5475443/+files/1893263_train_validation.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "1893263_focal_ussuri_validation.txt"
https://bugs.launchpad.net/nova/+bug/1893263/+attachment/5475442/+files/1893263_focal_ussuri_validation.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[0] has been fixed through PRs [1] and [2], and master packages built
for focal are available at [3].
I tested them on a new focal-ussuri deployment, therefore already having
the fix from the point release [4], and it works.
Attaching validation for focal-ussuri, and previous validations for
** 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/1906271
Title:
[SRU] November Stable Point Updates
To manage notifications about this bug go to:
Slightly more context on my previous comment: When I said " was able to
fix the issue I was having by forcing the hostname in
/etc/felix/felix.cfg using the property" I was referring to a problem I
was having setting up the environment to validate the SRU, not the main
issue itself.
--
You
I was able to fix the issue I was having by forcing the hostname in
/etc/felix/felix.cfg using the property:
FelixHostname =
I've successfully validated bionic-stein and bionic-train, however, I
cannot install the calico packages on focal:
root@juju-3294b7-calico-ussuri-6:/home/ubuntu#
** 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/1893263
Title:
[SRU] Cannot create instance with multiqueue image and vif_type=tap
(calico)
To manage notifications
** Summary changed:
- Cannot create instance with multiqueue image and vif_type=tap (calico)
+ [SRU] Cannot create instance with multiqueue image and vif_type=tap (calico)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
debdiff for SRU bionic-train
** Patch added: "bionic-train.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1893263/+attachment/5428145/+files/bionic-train.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
debdiff for SRU bionic-stein
** Patch added: "bionic-stein.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1893263/+attachment/5428146/+files/bionic-stein.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
debdiff for SRU focal-ussuri
** Description changed:
When using calico, the vif_type is tap, therefore when the instance is
being created, the method plug_tap() is invoked, which creates the tap
device prior to launching the instance.
That tap device is currently always created
** Description changed:
Environment: Ubuntu Bionic, OpenStack Train, Volume and Backup Driver
Ceph
This bug was also reproduced on Queens.
Steps to reproduce:
1) Create a volume v1 as user demo
2) Create a full backup of v1 as user admin
3) Create an incremental backup of
After speaking to Robie and the customer, we will not be pursuing the
SRU further back to eoan and bionic at this moment. Changing those to
"Won't Fix".
** Changed in: nfs-utils (Ubuntu Eoan)
Status: Incomplete => Won't Fix
** Changed in: nfs-utils (Ubuntu Bionic)
Status:
** Attachment added: "validation_nfs_utils_focal.txt"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+attachment/5384559/+files/validation_nfs_utils_focal.txt
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done
Performed validation according to test case, attached output, updated
tags
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871214
Title:
[SRU] nfsd doesn't start if exports depend on mount
To
** Description changed:
Reproduced in Bionic and Focal, packages 1:1.3.4-2.1ubuntu5.2 and
1:1.3.4-2.5ubuntu3 respectively.
Steps to reproduce:
1) Set up a ISCSI client to a 1GB+ volume, mount it in /data and set fstab to
mount at boot
2) Create a folder in /data like /data/dir1
Hello Robie,
While I investigated this issue, I found workarounds #1 and #2 as you
can see in the description section. I also found the upstream fix which
is the proper implementation of workaround #2 (workaround #2 per se
wouldn't be backportable, hence it needs a "generator" to be dynamic). I
debdiff for groovy
** Patch added: "lp1871214_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+attachment/5363650/+files/lp1871214_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: nfs-utils (Ubuntu Groovy)
Importance: Undecided
Assignee: Rodrigo Barbieri (rodrigo-barbieri2010)
Status: Fix Committed
** Attachment removed: "lp1871214_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+attachment/5363
debdiff for focal
** Also affects: nfs-utils (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: nfs-utils (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nfs-utils (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in:
** Description changed:
Reproduced in Bionic and Focal, packages 1:1.3.4-2.1ubuntu5.2 and
1:1.3.4-2.5ubuntu3 respectively.
Steps to reproduce:
1) Set up a ISCSI client to a 1GB+ volume, mount it in /data and set fstab to
mount at boot
2) Create a folder in /data like /data/dir1
This problem is addressed by commit [0] which requires [1] to compile.
I have created a test package with those changes and confirmed the issue
is addressed.
[0] http://git.linux-nfs.org/?p=steved/nfs-
utils.git;a=commitdiff;h=4776bd0599420f9d073c9e2601ed438062dccd19
[1]
** Summary changed:
- nfsd doesn't start if exports depend on mount
+ [SRU] nfsd doesn't start if exports depend on mount
** Changed in: nfs-utils (Ubuntu)
Assignee: (unassigned) => Rodrigo Barbieri (rodrigo-barbieri2010)
** Changed in: nfs-utils (Ubuntu)
Status: New =&g
** 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/1871214
Title:
nfsd doesn't start if exports depend on mount
To manage notifications about this bug go to:
** Description changed:
Reproduced in Bionic and Focal, packages 1:1.3.4-2.1ubuntu5.2 and
1:1.3.4-2.5ubuntu3 respectively.
Steps to reproduce:
- 1) Set up a ISCSI client to a 1GB+ volume, mount it /data and set fstab to
mount at boot
+ 1) Set up a ISCSI client to a 1GB+ volume, mount
Public bug reported:
Reproduced in Bionic and Focal, packages 1:1.3.4-2.1ubuntu5.2 and
1:1.3.4-2.5ubuntu3 respectively.
Steps to reproduce:
1) Set up a ISCSI client to a 1GB+ volume, mount it in /data and set fstab to
mount at boot
2) Create a folder in /data like /data/dir1 and set up
This is no longer true as of 1:1.3.4-2.1ubuntu5.2 (bionic). Do you need
this fix in xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766126
Title:
exportfs always returns success status
To
verified on disco-stein
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840465
Title:
[SRU] Fails to list security
verified on bionic-queens
** Tags removed: verification-needed-bionic verification-queens-needed
** Tags added: verification-done-bionic verification-queens-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since the system behaves as expected with the updated package installed,
passing the test case, I will mark it as verified.
** Tags removed: verification-rocky-needed
** Tags added: verification-rocky-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I tried to reproduce again in a different deployment unsuccessfully. I
don't know how (and if) it differs from the previous instance I was able
to reproduce it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
While performing validation, I was unable to reproduce the issue in
bionic-rocky deployment. Inspecting the code, the fix was not present. I
added logging, and confirmed that neutron is now including the key
"security_group_rules" in the response, therefore the error is no longer
triggered. I
** 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/1840465
Title:
[SRU] Fails to list security groups if one or more exists without
rules
To manage notifications about
** Changed in: horizon (Ubuntu Bionic)
Status: New => In Progress
** Changed in: horizon (Ubuntu Disco)
Status: New => In Progress
** Changed in: horizon (Ubuntu Eoan)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Attached debdiffs for disco, cosmic and bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840465
Title:
[SRU] Fails to list security groups if one or more exists without
rules
To manage
** Patch added: "lp1840465_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1840465/+attachment/5298453/+files/lp1840465_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1840465_cosmic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1840465/+attachment/5298452/+files/lp1840465_cosmic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Horizon 14.0.2 (rocky)
If a security group without any rules exists the listing of security groups
fails with a KeyError.
Traceback (most recent call last):
- File
"/usr/share/openstack-dashboard/openstack_dashboard/api/rest/utils.py", line
127, in _wrapped
-
** Summary changed:
- Fails to list security groups if one or more exists without rules
+ [SRU] Fails to list security groups if one or more exists without rules
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Xenial Queens verified using [Test Case]. Attached output.
** Attachment added: "xenial-queens-validation.txt"
https://bugs.launchpad.net/nova/+bug/1821594/+attachment/5276539/+files/xenial-queens-validation.txt
** Tags removed: verification-queens-needed
** Tags added:
** Attachment added: "bionic-queens-validation.txt"
https://bugs.launchpad.net/nova/+bug/1821594/+attachment/5275280/+files/bionic-queens-validation.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bionic Queens verified using [Test Case]. Attached output above ^.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags removed: verification-rocky-needed
** Tags added: verification-rocky-done
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821594
Title:
[SRU] Error in confirm_migration leaves stale
Bionic Rocky verified using [Test Case]. Attached output.
** Attachment added: "bionic-rocky-validation.txt"
https://bugs.launchpad.net/nova/+bug/1821594/+attachment/5273646/+files/bionic-rocky-validation.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Cosmic Rocky verified using [Test Case]. Attached output.
** Attachment added: "cosmic-rocky-validation.txt"
https://bugs.launchpad.net/nova/+bug/1821594/+attachment/5273645/+files/cosmic-rocky-validation.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Improved test case with more detailed steps in order to make it easier
to script and validate the output
** Description changed:
Description:
When performing a cold migration, if an exception is raised by the
driver during confirm_migration (this runs in the source node), the
** Description changed:
Description:
When performing a cold migration, if an exception is raised by the
driver during confirm_migration (this runs in the source node), the
migration record is stuck in "confirming" state and the allocations
against the source node are not removed.
69 matches
Mail list logo
