[Bug 2069125] Re: [SRU] Manila driver error with ONTAP SVM-scoped user
** Patch added: "lp2069125_noble.debdiff" https://bugs.launchpad.net/ubuntu/+source/manila/+bug/2069125/+attachment/5796282/+files/lp2069125_noble.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069125 Title: [SRU] Manila driver error with ONTAP SVM-scoped user To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2069125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069125] Re: [SRU] Manila driver error with ONTAP SVM-scoped user
** Patch added: "lp2069125_mantic.debdiff" https://bugs.launchpad.net/ubuntu/+source/manila/+bug/2069125/+attachment/5796281/+files/lp2069125_mantic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069125 Title: [SRU] Manila driver error with ONTAP SVM-scoped user To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2069125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069125] Re: [SRU] Manila driver error with ONTAP SVM-scoped user
** Patch added: "lp2069125_antelope.debdiff" https://bugs.launchpad.net/ubuntu/+source/manila/+bug/2069125/+attachment/5796280/+files/lp2069125_antelope.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069125 Title: [SRU] Manila driver error with ONTAP SVM-scoped user To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2069125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069125] Re: [SRU] Manila driver error with ONTAP SVM-scoped user
** Patch added: "lp2069125_jammy.debdiff" https://bugs.launchpad.net/ubuntu/+source/manila/+bug/2069125/+attachment/5796279/+files/lp2069125_jammy.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069125 Title: [SRU] Manila driver error with ONTAP SVM-scoped user To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2069125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069125] Re: Manila driver error with ONTAP SVM-scoped user
** Description changed:
- With the same NetApp stanza in the manila.conf file which was used without
any issue in the Zed release was used in the Bobcat release. In the Bobcat
release, the share creation worked normally, but adding access rule was not
worked and couldn't delete the share. Below is the error log that occurs when
adding a rule.
+ ** SRU DESCRIPTION AT THE BOTTOM *
+
+ With the same NetApp stanza in the manila.conf file which was used without
any issue in the Zed release was used in the Bobcat release. In the Bobcat
release, the share creation worked normally, but adding access rule was not
worked and couldn't delete the share. Below is the error log that occurs when
adding a rule.
I set all the roles indicated in NetApp's OpenStack operation guide in
storage
side(https://netapp-openstack-dev.github.io/openstack-docs/bobcat/manila/configuration/ontap_configuration/section_ontap-config.html#ontap-prerequisites).
-
### manila-share.log
2024-05-27 15:43:14.708 19 INFO oslo.messaging.notification.share.create.end
[None req-4b46bc06-9332-40f3-9ef0-57895519228c
c2e47ee4c8295d950db5757f73dfe9b5149947ccf5dc4e4ba3370c210217bcc4
76a637a88d624e3ea80b261a4c66dc2a - - - -] {"message_id":
"d9fcc12a-5449-437c-85a0-eb5bdddab553", "publisher_id":
"share.dc1-infra-rnd-stack-ctrl-01@c400", "event_type": "share.create.end",
"priority": "INFO", "payload": {"share_id":
"68e79de3-5e22-472b-a895-c79e0b677b01", "user_id":
"c2e47ee4c8295d950db5757f73dfe9b5149947ccf5dc4e4ba3370c210217bcc4",
"project_id": "76a637a88d624e3ea80b261a4c66dc2a", "snapshot_id": null,
"share_group_id": null, "size": 20, "name": "asdasd", "description": null,
"proto": "NFS", "is_public": true, "availability_zone": null, "host":
"dc1-infra-rnd-stack-ctrl-01@c400#N1_Data", "status": "creating",
"share_type_id": "40cdd81c-1fa8-4fc6-8f5e-288d0b9f5430", "share_type":
"NFS_VOLUME"}, "timestamp": "2024-05-27 06:43:14.708153"}
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server [None
req-be5d1bf0-c013-47ac-94bc-2de599a3862f
c2e47ee4c8295d950db5757f73dfe9b5149947ccf5dc4e4ba3370c210217bcc4
76a637a88d624e3ea80b261a4c66dc2a - - - -] Exception during message handling:
manila.share.drivers.netapp.dataontap.client.api.NaApiError: NetApp API failed.
Reason - 15661:entry doesn't exist
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server Traceback (most
recent call last):
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server File
"/var/lib/kolla/venv/lib64/python3.9/site-packages/oslo_messaging/rpc/server.py",
line 165, in _process_incoming
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server res =
self.dispatcher.dispatch(message)
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server File
"/var/lib/kolla/venv/lib64/python3.9/site-packages/oslo_messaging/rpc/dispatcher.py",
line 309, in dispatch
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server return
self._do_dispatch(endpoint, method, ctxt, args)
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server File
"/var/lib/kolla/venv/lib64/python3.9/site-packages/oslo_messaging/rpc/dispatcher.py",
line 229, in _do_dispatch
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server result =
func(ctxt, **new_args)
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server File
"/var/lib/kolla/venv/lib64/python3.9/site-packages/manila/share/manager.py",
line 236, in wrapped
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server return f(self,
*args, **kwargs)
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server File
"/var/lib/kolla/venv/lib64/python3.9/site-packages/manila/utils.py", line 481,
in wrapper
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server return
func(self, *args, **kwargs)
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server File
"/var/lib/kolla/venv/lib64/python3.9/site-packages/manila/share/manager.py",
line 4177, in update_access
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server
self.update_access_for_instances(context, [share_instance_id],
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server File
"/var/lib/kolla/venv/lib64/python3.9/site-packages/manila/share/manager.py",
line 4191, in update_access_for_instances
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server
self.access_helper.update_access_rules(
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server File
"/var/lib/kolla/venv/lib64/python3.9/site-packages/manila/share/access.py",
line 299, in update_access_rules
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server
self._update_access_rules(context, share_instance_id,
2024-05-27 15:43:57.077 19 ERROR oslo_messaging.rpc.server File
"/var/lib/kolla/venv/lib64/python3.9/site-packages/manila/share/access.py",
line 336, in _update_access_rules
2024-05-27 15:43:57.077 19 ERROR
[Bug 1999814] Re: [SRU] Allow for specifying common baseline CPU model with disabled feature
** Patch added: "lp1999814_focal.debdiff" https://bugs.launchpad.net/nova/+bug/1999814/+attachment/5795887/+files/lp1999814_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1999814 Title: [SRU] Allow for specifying common baseline CPU model with disabled feature To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1999814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1999814] Re: [SRU] Allow for specifying common baseline CPU model with disabled feature
** Patch added: "lp1999814_jammy.debdiff" https://bugs.launchpad.net/nova/+bug/1999814/+attachment/5795868/+files/lp1999814_jammy.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1999814 Title: [SRU] Allow for specifying common baseline CPU model with disabled feature To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1999814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** Attachment added: "bug_1728031_jammy_antelope_reproduced.png" https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1728031/+attachment/5795838/+files/bug_1728031_jammy_antelope_reproduced.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** Attachment added: "bug_1728031_jammy_antelope_fixed.png" https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1728031/+attachment/5795839/+files/bug_1728031_jammy_antelope_fixed.png ** Tags removed: verification-antelope-needed verification-needed ** Tags added: verification-antelope-done verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** Changed in: cloud-archive/caracal Status: Fix Committed => Fix Released ** 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. https://bugs.launchpad.net/bugs/2055409 Title: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** Attachment added: "bug_2055409_jammy_antelope_verification.txt" https://bugs.launchpad.net/cloud-archive/xena/+bug/2055409/+attachment/5795828/+files/bug_2055409_jammy_antelope_verification.txt ** Tags removed: verification-antelope-needed ** Tags added: verification-antelope-done -- 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 OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1999814] Re: [SRU] Allow for specifying common baseline CPU model with disabled feature
** Description changed:
SRU TEMPLATE AT THE BOTTOM ***
Hello,
This is very similar to pad.lv/1852437 (and the related blueprint at
https://blueprints.launchpad.net/nova/+spec/allow-disabling-cpu-flags),
but there is a very different and important nuance.
A customer I'm working with has two classes of blades that they're
trying to use. Their existing ones are Cascade Lake-based; they are
presently using the Cascadelake-Server-noTSX CPU model via
libvirt.cpu_model in nova.conf. Their new blades are Ice Lake-based,
which is a newer processor, which typically would also be able to run
based on the Cascade Lake feature set - except that these Ice Lake
processors lack the MPX feature defined in the Cascadelake-Server-noTSX
model.
The result of this is evident when I try to start nova on the new blades
with the Ice Lake CPUs. Even if I specify the following in my
nova.conf:
[libvirt]
cpu_mode = custom
cpu_model = Cascadelake-Server-noTSX
cpu_model_extra_flags = -mpx
That is not enough to allow Nova to start; it fails in the libvirt
driver in the _check_cpu_compatibility function:
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service Traceback (most
recent call last):
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service File
"/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 771, in
_check_cpu_compatibility
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service
self._compare_cpu(cpu, self._get_cpu_info(), None)
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service File
"/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 8817, in
_compare_cpu
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service raise
exception.InvalidCPUInfo(reason=m % {'ret': ret, 'u': u})
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service
nova.exception.InvalidCPUInfo: Unacceptable CPU info: CPU doesn't have
compatibility.
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service 0
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service Refer to
http://libvirt.org/html/libvirt-libvirt-host.html#virCPUCompareResult
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service During handling of
the above exception, another exception occurred:
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service Traceback (most
recent call last):
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service File
"/usr/lib/python3/dist-packages/oslo_service/service.py", line 810, in
run_service
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service service.start()
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service File
"/usr/lib/python3/dist-packages/nova/service.py", line 173, in start
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service
self.manager.init_host()
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service File
"/usr/lib/python3/dist-packages/nova/compute/manager.py", line 1404, in
init_host
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service
self.driver.init_host(host=self.host)
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service File
"/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 743, in
init_host
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service
self._check_cpu_compatibility()
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service File
"/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 777, in
_check_cpu_compatibility
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service raise
exception.InvalidCPUInfo(msg)
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service
nova.exception.InvalidCPUInfo: Configured CPU model: Cascadelake-Server-noTSX
is not compatible with host CPU. Please correct your config and try again.
Unacceptable CPU info: CPU doesn't have compatibility.
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service 0
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service Refer to
http://libvirt.org/html/libvirt-libvirt-host.html#virCPUCompareResult
2022-12-15 17:20:59.562 1836708 ERROR oslo_service.service
If I make a custom libvirt CPU map file which removes the "" feature and specify that as the cpu_model instead, I am
able to make Nova start - so it does indeed seem to specifically be that
single feature which is blocking me. However, editing the libvirt CPU
mapping files is probably not the right way to fix this - hence why I'm
filing this bug, for discussion of how to support cases like this.
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** Attachment added: "bug_2055409_bionic_ussuri_verification.txt" https://bugs.launchpad.net/horizon/+bug/2055409/+attachment/5795628/+files/bug_2055409_bionic_ussuri_verification.txt ** Tags removed: verification-ussuri-needed ** Tags added: verification-ussuri-done -- 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 OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** Changed in: cloud-archive/zed Status: Fix Released => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** Changed in: cloud-archive/zed Status: New => Won't Fix ** Changed in: cloud-archive/victoria Status: New => Won't Fix ** Changed in: cloud-archive/wallaby Status: New => Won't Fix ** Changed in: cloud-archive/xena Status: New => Won't Fix -- 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 OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1999814] Re: [SRU] Allow for specifying common baseline CPU model with disabled feature
** Also affects: nova (Ubuntu) Importance: Undecided Status: New ** Also affects: nova (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nova (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nova/victoria Importance: Undecided Status: New ** Also affects: nova/ussuri Importance: Undecided Status: New ** Also affects: nova/xena Importance: Undecided Status: New ** Also affects: nova/yoga Importance: Undecided Status: New ** Also affects: nova/wallaby Importance: Undecided Status: New ** Tags added: sts 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/1999814 Title: [SRU] Allow for specifying common baseline CPU model with disabled feature To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1999814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** Attachment added: "bug_1728031_focal_yoga_fixed.png" https://bugs.launchpad.net/horizon/+bug/1728031/+attachment/5793341/+files/bug_1728031_focal_yoga_fixed.png ** Tags removed: verification-yoga-needed ** Tags added: verification-yoga-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** Attachment added: "bug_1728031_focal_yoga_reproduced.png" https://bugs.launchpad.net/horizon/+bug/1728031/+attachment/5793340/+files/bug_1728031_focal_yoga_reproduced.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** Attachment added: "bug_1728031_jammy_bobcat_fixed.png" https://bugs.launchpad.net/horizon/+bug/1728031/+attachment/5793203/+files/bug_1728031_jammy_bobcat_fixed.png ** Tags removed: verification-bobcat-needed ** Tags added: verification-bobcat-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** Attachment added: "bug_1728031_jammy_bobcat_reproduced.png" https://bugs.launchpad.net/horizon/+bug/1728031/+attachment/5793202/+files/bug_1728031_jammy_bobcat_reproduced.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** Attachment added: "bug_2055409_jammy_bobcat_verification.txt" https://bugs.launchpad.net/horizon/+bug/2055409/+attachment/5793228/+files/bug_2055409_jammy_bobcat_verification.txt ** Tags removed: verification-bobcat-needed verification-yoga-needed ** Tags added: verification-bobcat-done verification-yoga-done -- 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 OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** Attachment added: "bug_2055409_focal_yoga_verification.txt" https://bugs.launchpad.net/horizon/+bug/2055409/+attachment/5793227/+files/bug_2055409_focal_yoga_verification.txt -- 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 OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** Attachment added: "bug_2055409_focal_ussuri_verification.txt" https://bugs.launchpad.net/horizon/+bug/2055409/+attachment/5791239/+files/bug_2055409_focal_ussuri_verification.txt ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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 OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944759] Re: [SRU] confirm resize fails with CPUUnpinningInvalid
** Description changed: * SRU DESCRIPTION BELOW * Nova has a race condition between resize_instance() compute manager call and the update_available_resources periodic job. If they overlap at the right place, when resize_instance calls finish_resize, then periodic job will not track the migration nor the instance on the source host. It causes that the PCPU allocation on the source host is dropped in the resource tracker (not in placement). Then when the resize is confirmed nova tries to free the pinned cpus again on the source host and fails with CPUUnpinningInvalid as they are already freed. I've pushed a reproduction test: https://review.opendev.org/c/openstack/nova/+/810763 It is reproducible at least on master, xena, wallaby, and victoria === SRU DESCRIPTION === [Impact] Due to a race condition the tracking of pinned CPU resources can go off- sync causing "No valid host" errors while being unable to create new instances with CPU pinning, as the previous pinned CPUs were not marked as freed. Part of the reason is addressed in the fix for LP#1953359 where a migration context is not pointing to the proper node during the race condition window, resulting in a CPUPinningInvalid error. This fix complements LP#1953359 by addressing the improper tracking of resources that happens only when the resource tracker periodic job runs in the source node while the flavor registered corresponds to the one of the destination. That is solved by setting the instance.old_flavor so the CPU pinning resources are tracked properly. [Test case] The test case for this was already implemented on non-live functional tests upstream: in nova/tests/functional/libvirt/test_numa_servers.py: - test_resize_dedicated_policy_race_on_dest_bug_1953359 - test_resize_confirm_bug_1944759 - test_resize_revert_bug_1944759 As this is a race condition it is very difficult to validate, even upstream, so the functional tests mock certain parts of the code to simulate the entire scope of the workflow. It is a non-live functional test, so it is more akin to a broader unit test. + The test case that will be run for this SRU is running the charmed- + openstack-tester [1] against the environment containing the upgraded + package (essentially as it would be in a point release SRU) and expect + the test to pass. Test run evidence will be attached to LP. + [Regression Potential] The code is considered stable today in newer releases and the scope of the code affected is fairly limited. Given that it is a race condition that it is difficult to validate, despite the non-live functional tests, the regression potential is moderate. [Other Info] None. + + [1] https://github.com/openstack-charmers/charmed-openstack-tester -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944759 Title: [SRU] confirm resize fails with CPUUnpinningInvalid To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1944759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
All evidence was collected as part of verification for bug https://bugs.launchpad.net/horizon/+bug/2055409 ... please refer to the respective attachments for the verification of that bug for extra details on setting up the env, upgrading package, etc ** Tags removed: verification-needed-jammy verification-needed-mantic verification-needed-noble ** Tags added: verification-done-jammy verification-done-mantic verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** Attachment added: "bug_1728031_noble_caracal_fixed.png" https://bugs.launchpad.net/horizon/+bug/1728031/+attachment/5791148/+files/bug_1728031_noble_caracal_fixed.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** Attachment added: "bug_1728031_noble_caracal_reproduced.png" https://bugs.launchpad.net/horizon/+bug/1728031/+attachment/5791147/+files/bug_1728031_noble_caracal_reproduced.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** Attachment added: "bug_1728031_mantic_bobcat_fixed.png" https://bugs.launchpad.net/horizon/+bug/1728031/+attachment/5791146/+files/bug_1728031_mantic_bobcat_fixed.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** Attachment added: "bug_1728031_mantic_bobcat_reproduced.png" https://bugs.launchpad.net/horizon/+bug/1728031/+attachment/5791145/+files/bug_1728031_mantic_bobcat_reproduced.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** Attachment added: "bug_1728031_jammy_yoga_fixed.png" https://bugs.launchpad.net/horizon/+bug/1728031/+attachment/5791144/+files/bug_1728031_jammy_yoga_fixed.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** Attachment added: "bug_1728031_jammy_yoga_reproduced.png" https://bugs.launchpad.net/horizon/+bug/1728031/+attachment/5791143/+files/bug_1728031_jammy_yoga_reproduced.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** Attachment added: "bug_2055409_mantic_bobcat_verification.txt" https://bugs.launchpad.net/horizon/+bug/2055409/+attachment/5791142/+files/bug_2055409_mantic_bobcat_verification.txt ** Tags removed: verification-needed-jammy verification-needed-mantic ** Tags added: verification-done-jammy verification-done-mantic -- 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 OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** Attachment added: "bug_2055409_jammy_yoga_verification.txt" https://bugs.launchpad.net/horizon/+bug/2055409/+attachment/5791141/+files/bug_2055409_jammy_yoga_verification.txt -- 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 OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** No longer affects: horizon (Ubuntu Focal) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** Description changed: Setting the config option OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES to False successfully allows skipping neutron calls when loading the instance list page, therefore speeding up page loading. However, when clicking on an instance and loading the instance details page it still makes the neutron calls, taking a very long time. The usage of the config option in the code could be adjusted to also be used when loading the instance details page, thus speeding up the page loading there as well. === SRU Description === [Impact] Environments that have too many neutron ports struggle to load the instance list and instance detail pages. The existing config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES allows speeding up the instance list but it is not being used when loading a single instance detail page. By using the config option when loading the instance detail page as well, we speed up instance detail page loading and we have minimal side effects, which are already the same seen when displaying the list (more info about the side effects at [1]) [Test case] 1. Setting up the env 1a. Deploy openstack env with horizon/openstack-dashboard 1b. Declare and set OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES to False in /etc/openstack-dashboard/local_settings.py and restart apache2 2. Prepare to reproduce the bug 2a. Create a single VM successfully 2b. As we cannot easily create enough ports in the lab to replicate the slowness, we will rely on the message being present in the logs. Therefore, at this step we enable debug in horizon to see the messages. Set DEBUG to True in /etc/openstack-dashboard/local_settings.py and restart apache2. 3. Reproducing the bug 3a. Load the instance list page and verify that the following messages are not present in the logs: GET /v2.0/floatingips?port_id=... GET /v2.0/ports?tenant_id=... GET /v2.0/networks?id=... GET /v2.0/subnets 3b. Click on the instance to load the detail page and verify that the following messages ARE present in the logs: GET /v2.0/floatingips?port_id=... GET /v2.0/ports?tenant_id=... GET /v2.0/networks?id=... GET /v2.0/subnets 5. Install package that contains the fixed code 6. Confirm fix 6a. Repeat step 3a. 6b. Click on the instance to load the detail page and verify that the following messages are NOT present in the logs: GET /v2.0/floatingips?port_id=... GET /v2.0/ports?tenant_id=... GET /v2.0/networks?id=... GET /v2.0/subnets - [Regression Potential] + [Where problems could occur] The code has tested in upstream CI (without the addition of bug-specific functional tests) from master(Caracal) to stable/zed without any issue captured. Side effects documented at [1]. The code itself is a simple 2-liner with minimal to none chance of regression due to narrow scope of code change impact. [Other Info] None. [1] https://github.com/openstack/horizon/blob/2b03b44f3adeea7e7a8aaabcccfa00614301/doc/source/configuration/settings.rst#L2410 -- 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 OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** Description changed: After following the security hardening guidelines: https://docs.openstack.org/security-guide/dashboard/checklist.html#check-dashboard-09-is-enforce-password-check-set-to-true After this check is enabled Check-Dashboard-09: Is ENFORCE_PASSWORD_CHECK set to True The user password cannot be changed. The form submission fails by displaying that admin password is incorrect. The reason for this is in keystone.py in openstack_dashboard/api/keystone.py user_verify_admin_password method uses internal url to communicate with the keystone. line 500: endpoint = _get_endpoint_url(request, 'internalURL') This should be changed to adminURL === SRU Description === [Impact] Admins cannot change user's password as it gives an error saying that the admin's password is incorrect, despite being correct. There are 2 causes: 1) due to the lack of user_domain being specified when validating the admin's password, it will always fail if the admin is not registered in the "default" domain, because the user_domain defaults to "default" when not specified. 2) even if the admin user is registered in the "default" domain, it may fail due to the wrong endpoint being used in the request to validate the admin's password. The issues are fixed in 2 separate patches [1] and [2]. However, [2] is introducing a new config option, while [1] alone is also enough to fix the occurrence on some deployments. We are including only [1] in the SRU. [Test case] 1. Setting up the env, ensure ENFORCE_PASSWORD_CHECK is set to True 1a. Deploy openstack env with horizon/openstack-dashboard 1b. Set up admin user in a domain not named "default", such as "admin_domain". 1c. Set up any other user, such as demo. Preferably in the admin_domain as well for convenience. 2. Reproduce the bug 2a. Login as admin and navigate to Identity > Users 2b. On the far right-hand side of the demo user row, click the options button and select Change Password 2c. Type in any new password, repeat it below, and type in the admin password. Click Save and you should see a message "The admin password is incorrect" 3. Install package that contains the fixed code 4. Confirm fix 5a. Repeat steps 2a-2c 5b. The password should now be saved successfully - [Regression Potential] + [Where problems could occur] The code is a 1-line change that was tested in upstream CI (without the addition of bug-specific functional tests) from master(Caracal) to stable/zed without any issue captured. No side effects or risks are foreseen. Usage of fix [1] has also been tested manually without fix [2] - and still worked. + and still worked. Worst case scenario, the ability to change password + that currently does not work will still not work, because the code + change is isolated to the specific function that validates the + authenticity of the password used. [Other Info] None. [1] https://review.opendev.org/c/openstack/horizon/+/913250 [2] https://review.opendev.org/c/openstack/horizon/+/844574 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** Description changed: After following the security hardening guidelines: https://docs.openstack.org/security-guide/dashboard/checklist.html#check-dashboard-09-is-enforce-password-check-set-to-true After this check is enabled Check-Dashboard-09: Is ENFORCE_PASSWORD_CHECK set to True The user password cannot be changed. The form submission fails by displaying that admin password is incorrect. The reason for this is in keystone.py in openstack_dashboard/api/keystone.py user_verify_admin_password method uses internal url to communicate with the keystone. line 500: endpoint = _get_endpoint_url(request, 'internalURL') This should be changed to adminURL === SRU Description === [Impact] Admins cannot change user's password as it gives an error saying that the admin's password is incorrect, despite being correct. There are 2 causes: 1) due to the lack of user_domain being specified when validating the admin's password, it will always fail if the admin is not registered in the "default" domain, because the user_domain defaults to "default" when not specified. 2) even if the admin user is registered in the "default" domain, it may fail due to the wrong endpoint being used in the request to validate the admin's password. The issues are fixed in 2 separate patches [1] and [2]. However, [2] is introducing a new config option, while [1] alone is also enough to fix the occurrence on some deployments. We are including only [1] in the SRU. - [Test case] - 1. Setting up the env + 1. Setting up the env, ensure ENFORCE_PASSWORD_CHECK is set to True 1a. Deploy openstack env with horizon/openstack-dashboard 1b. Set up admin user in a domain not named "default", such as "admin_domain". 1c. Set up any other user, such as demo. Preferably in the admin_domain as well for convenience. 2. Reproduce the bug 2a. Login as admin and navigate to Identity > Users 2b. On the far right-hand side of the demo user row, click the options button and select Change Password 2c. Type in any new password, repeat it below, and type in the admin password. Click Save and you should see a message "The admin password is incorrect" 3. Install package that contains the fixed code 4. Confirm fix 5a. Repeat steps 2a-2c 5b. The password should now be saved successfully [Regression Potential] The code is a 1-line change that was tested in upstream CI (without the addition of bug-specific functional tests) from master(Caracal) to stable/zed without any issue captured. No side effects or risks are foreseen. Usage of fix [1] has also been tested manually without fix [2] and still worked. [Other Info] None. [1] https://review.opendev.org/c/openstack/horizon/+/913250 [2] https://review.opendev.org/c/openstack/horizon/+/844574 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944759] Re: [SRU] confirm resize fails with CPUUnpinningInvalid
** Patch added: "lp1953359_lp1944759_focal.debdiff" https://bugs.launchpad.net/nova/+bug/1944759/+attachment/5776088/+files/lp1953359_lp1944759_focal.debdiff ** Also affects: nova/ussuri Importance: Undecided Status: New ** Also affects: nova (Ubuntu) Importance: Undecided Status: New ** Also affects: nova (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/ussuri Importance: Undecided Status: New ** 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/1944759 Title: [SRU] confirm resize fails with CPUUnpinningInvalid To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1944759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom
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 new container): mellon_create_metadata https://sp.10.5.100.3/mellon https://sp.10.5.100.3/v3/OS- FEDERATION/identity_providers/idp.10.5.100.2/protocols/saml2/auth/mellon It fails silently to create the xml file that it should be creating. It works fine in focal, but doesn't work in jammy. Versions in jammy: libapache2-mod-auth-mellon 0.18.0-1build1 apache2-bin 2.4.52-1ubuntu4.8 openssl 3.0.2-0ubuntu1.15 libssl3:amd64 3.0.2-0ubuntu1.15 libxmlsec1-openssl:amd641.2.33-1build2 versions in focal: libapache2-mod-auth-mellon 0.16.0-1ubuntu0.1 apache2-bin 2.4.41-4ubuntu3.16 openssl 1.1.1f-1ubuntu2.22 libssl1.1:amd64 1.1.1f-1ubuntu2.22 libxmlsec1-openssl:amd64 1.2.28-2 [1] https://bugs.launchpad.net/ubuntu/+source/ssl-cert/+bug/2052795 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945774 Title: openssl: breaks ssl-cert installation: 8022CB35777F:error:127A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1945774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom
** 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. https://bugs.launchpad.net/bugs/1945774 Title: openssl: breaks ssl-cert installation: 8022CB35777F:error:127A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1945774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True
** 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 ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/antelope Importance: Undecided Status: New ** Also affects: cloud-archive/yoga Importance: Undecided Status: New ** Also affects: cloud-archive/bobcat Importance: Undecided Status: New ** Also affects: cloud-archive/zed Importance: Undecided Status: New ** No longer affects: ubuntu ** No longer affects: Ubuntu Focal ** No longer affects: Ubuntu Jammy ** No longer affects: Ubuntu Mantic ** Also affects: horizon (Ubuntu) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
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 OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** 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. https://bugs.launchpad.net/bugs/2055409 Title: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** 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. https://bugs.launchpad.net/bugs/2055409 Title: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** 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. https://bugs.launchpad.net/bugs/2055409 Title: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** 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. https://bugs.launchpad.net/bugs/2055409 Title: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
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 OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
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 Title: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055409 Title: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** 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. https://bugs.launchpad.net/bugs/2055409 Title: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** 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. https://bugs.launchpad.net/bugs/2055409 Title: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** 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. https://bugs.launchpad.net/bugs/2055409 Title: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** 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. https://bugs.launchpad.net/bugs/2055409 Title: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
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] https://review.opendev.org/c/openstack/releases/+/906842 -- 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 OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
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 to merge the diff directly into SRU code. For simplicity, I believe it will be better to not wait for Point releases of Bobcat, Antelope and Zed because just this "waiting for a new tag" period could take months and all the other releases that don't have point releases would have to wait on that to get their SRU started ** Also affects: horizon (Ubuntu) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu Jammy) Importance: Undecided Status: New -- 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 OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904580] Re: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open
** 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/nova/.ssh/id_rsa' are too open To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1904580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948914] Re: [SRU] Ussuri stable releases
** 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 to: https://bugs.launchpad.net/cloud-archive/+bug/1948914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939604] Re: [SRU] Cannot create 1vcpu instance with multiqueue image, vif_type=tap (calico)
** 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 Status: New ** Also affects: cloud-archive/ussuri Importance: Undecided Status: New ** Also affects: cloud-archive/wallaby Importance: Undecided Status: New ** Also affects: cloud-archive/victoria Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939604 Title: [SRU] Cannot create 1vcpu instance with multiqueue image, vif_type=tap (calico) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1939604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893263] Re: [SRU] Cannot create instance with multiqueue image and vif_type=tap (calico)
** 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. https://bugs.launchpad.net/bugs/1893263 Title: [SRU] Cannot create instance with multiqueue image and vif_type=tap (calico) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1893263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893263] Re: [SRU] Cannot create instance with multiqueue image and vif_type=tap (calico)
** 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. https://bugs.launchpad.net/bugs/1893263 Title: [SRU] Cannot create instance with multiqueue image and vif_type=tap (calico) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1893263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893263] Re: [SRU] Cannot create instance with multiqueue image and vif_type=tap (calico)
** 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. https://bugs.launchpad.net/bugs/1893263 Title: [SRU] Cannot create instance with multiqueue image and vif_type=tap (calico) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1893263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893263] Re: [SRU] Cannot create instance with multiqueue image and vif_type=tap (calico)
[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 stein and train that I had done before. [0] https://github.com/projectcalico/calico/issues/4216 [1] https://github.com/projectcalico/networking-calico/pull/48 [2] https://github.com/projectcalico/packaging/pull/39 [3] https://launchpad.net/~project-calico/+archive/ubuntu/master [4] https://bugs.launchpad.net/cloud-archive/+bug/1906271 ** Bug watch added: github.com/projectcalico/calico/issues #4216 https://github.com/projectcalico/calico/issues/4216 -- 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 about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1893263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906271] Re: [SRU] November Stable Point Updates
** 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: https://bugs.launchpad.net/cloud-archive/+bug/1906271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893263] Re: [SRU] Cannot create instance with multiqueue image and vif_type=tap (calico)
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 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 about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1893263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893263] Re: [SRU] Cannot create instance with multiqueue image and vif_type=tap (calico)
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# add-apt-repository ppa:project-calico/calico-3.17 This PPA contains packages for Calico's 3.17.x release series, mainly to support OpenStack-based systems (although the Felix package can be used stand-alone). It will be updated with patch releases for that series. More info: https://launchpad.net/~project-calico/+archive/ubuntu/calico-3.17 Press [ENTER] to continue or Ctrl-c to cancel adding it. Hit:1 http://nova.clouds.archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://nova.clouds.archive.ubuntu.com/ubuntu focal-backports InRelease Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease Ign:5 http://ppa.launchpad.net/project-calico/calico-3.17/ubuntu focal InRelease Err:6 http://ppa.launchpad.net/project-calico/calico-3.17/ubuntu focal Release 404 Not Found [IP: 91.189.95.83 80] Reading package lists... Done E: The repository 'http://ppa.launchpad.net/project-calico/calico-3.17/ubuntu focal Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. -- 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 about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1893263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893263] Re: [SRU] Cannot create instance with multiqueue image and vif_type=tap (calico)
** 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 about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1893263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893263] Re: [SRU] Cannot create instance with multiqueue image and vif_type=tap (calico)
** 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. https://bugs.launchpad.net/bugs/1893263 Title: [SRU] Cannot create instance with multiqueue image and vif_type=tap (calico) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1893263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893263] Re: Cannot create instance with multiqueue image and vif_type=tap (calico)
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. https://bugs.launchpad.net/bugs/1893263 Title: Cannot create instance with multiqueue image and vif_type=tap (calico) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1893263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893263] Re: Cannot create instance with multiqueue image and vif_type=tap (calico)
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. https://bugs.launchpad.net/bugs/1893263 Title: Cannot create instance with multiqueue image and vif_type=tap (calico) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1893263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893263] Re: Cannot create instance with multiqueue image and vif_type=tap (calico)
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 without multiqueue as per [1]. When libvirt creates the instance, the XML definition "queues=" clashes with the fact that the pre-existing tap interface doesn't have multiqueue enabled, and therefore errors out with the exception below. The code at [2] already handles multiqueue, but it is never invoked with multiqueue=True. Alternatively, as a current workaround, if the instance is shutdown through virsh, or rebooted through nova, it causes the tap device to be removed, to be created again by libvirt instead, allowing the tap device to be set up with multiqueue appropriately if its XML is manually edited. This begs the question as why the plug_tap() method needs to pre-create the interface at all, if when the VM rebooted libvirt does so regardless of plug_tap(). Steps to reproduce: 1) Ubuntu bionic + devstack master + follow instructions at [3] 2) wget https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.img 3) openstack image create bionic-mq --file bionic-server-cloudimg-amd64.img --property hw_vif_multiqueue_enabled=True 4) openstack image create bionic --file bionic-server-cloudimg-amd64.img 5) ssh-keygen 6) openstack keypair create key1 --public-key ~/.ssh/id_rsa.pub 7) openstack flavor create --vcpu 2 --ram 1024 --disk 10 --public --id 10 test_flavor 8) openstack server create --network calico --flavor test_flavor --image bionic --key-name key1 no-mq instance is created successfully 9) ip a 6: tapcc353751-13: mtu 1500 qdisc fq_codel state UP group default qlen 1000 10) sudo virsh edit 1 add "" to the interface section 11) openstack server reboot no-mq wait a few secs 12) ip a 7: tapcc353751-13: mtu 1500 qdisc mq state UNKNOWN group default qlen 1000 13) ssh to the instance and run "sudo ethtool -l " Combined: 2 14) openstack server delete no-mq 15) openstack server create --network calico --flavor test_flavor --image bionic-mq --key-name key1 mq instance fails to be created, log shows the below stack trace. - [1] https://github.com/openstack/nova/blob/f521f4dbace0e35bedd089369da6f6969da5ca32/nova/virt/libvirt/vif.py#L701 [2] https://github.com/openstack/nova/blob/f521f4dbace0e35bedd089369da6f6969da5ca32/nova/privsep/linux_net.py#L109 [3] https://docs.projectcalico.org/getting-started/openstack/installation/devstack Aug 27 18:58:38 devstack nova-compute[7968]: ERROR nova.compute.manager [None req-71d40776-0fa7-466e-9060-11472b5bce42 admin admin] [instance: 69a0a527-9c33-432f-8889-c421ae8aebb4] Instance failed to spawn: libvirt.libvirtError: Unable to create tap device tapb6021dd0-fd: Invalid argument Aug 27 18:58:38 devstack nova-compute[7968]: ERROR nova.compute.manager [instance: 69a0a527-9c33-432f-8889-c421ae8aebb4] Traceback (most recent call last): Aug 27 18:58:38 devstack nova-compute[7968]: ERROR nova.compute.manager [instance: 69a0a527-9c33-432f-8889-c421ae8aebb4] File "/opt/stack/nova/nova/compute/manager.py", line 2628, in _build_resources Aug 27 18:58:38 devstack nova-compute[7968]: ERROR nova.compute.manager [instance: 69a0a527-9c33-432f-8889-c421ae8aebb4] yield resources Aug 27 18:58:38 devstack nova-compute[7968]: ERROR nova.compute.manager [instance: 69a0a527-9c33-432f-8889-c421ae8aebb4] File "/opt/stack/nova/nova/compute/manager.py", line 2401, in _build_and_run_instance Aug 27 18:58:38 devstack nova-compute[7968]: ERROR nova.compute.manager [instance: 69a0a527-9c33-432f-8889-c421ae8aebb4] accel_info=accel_info) Aug 27 18:58:38 devstack nova-compute[7968]: ERROR nova.compute.manager [instance: 69a0a527-9c33-432f-8889-c421ae8aebb4] File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 3701, in spawn Aug 27 18:58:38 devstack nova-compute[7968]: ERROR nova.compute.manager [instance: 69a0a527-9c33-432f-8889-c421ae8aebb4] cleanup_instance_disks=created_disks) Aug 27 18:58:38 devstack nova-compute[7968]: ERROR nova.compute.manager [instance: 69a0a527-9c33-432f-8889-c421ae8aebb4] File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 6700, in _create_guest_with_network Aug 27 18:58:38 devstack nova-compute[7968]: ERROR nova.compute.manager [instance: 69a0a527-9c33-432f-8889-c421ae8aebb4] cleanup_instance_disks=cleanup_instance_disks) Aug 27 18:58:38 devstack nova-compute[7968]: ERROR nova.compute.manager [instance: 69a0a527-9c33-432f-8889-c421ae8aebb4] File "/usr/local/lib/python3.6/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ Aug 27 18:58:38 devstack nova-compute[7968]: ERROR nova.compute.manager [instance:
[Bug 1869746] Re: Cinder throws error creating incremental backup from parent in another project
** 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 v1 as user demo 4) Result: Backup is created successfully, but error in logs. Logs do not show INFO message and parent_backup.num_dependent_backups is not incremented [0]. Expectation: Either no error successfully finishing method create_backup, or not creating backup at all, with backup entity set as Error (see below). Using POSIX driver, the backup is not created successfully and backup entity remains in error state. The POSIX driver tries to read backup.parent_id before creating the backup therefore raises the error earlier. Trace: 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server [req-19fccda2-b765-4b68-9663-aeae5cf3002e 3bee8c02ecce4744af287b3b8dd40ca5 9370e1e898214d88bd9eda4f88eccba9 - f883c6315a004471b2ab1b04d8a111d9 f883c6315a004471b2ab1b04d8a111d9] Exception during message handling: cinder.exception.BackupNotFound: Backup 7a15b9ec-7648-483f-ad32-6074567eca2a could not be found. 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/dispatcher.py", line 274, in dispatch 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/dispatcher.py", line 194, in _do_dispatch 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/cinder/backup/manager.py", line 447, in create_backup 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server backup.parent_id) 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/cinder/objects/base.py", line 352, in get_by_id 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server orm_obj = db.get_by_id(context, cls.model, id, *args, **kwargs) 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/cinder/db/api.py", line 1801, in get_by_id 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server return IMPL.get_by_id(context, model, id, *args, **kwargs) 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/cinder/db/sqlalchemy/api.py", line 189, in wrapper 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/cinder/db/sqlalchemy/api.py", line 7125, in get_by_id 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server return _GET_METHODS[model](context, id, *args, **kwargs) 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/cinder/db/sqlalchemy/api.py", line 189, in wrapper 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/cinder/db/sqlalchemy/api.py", line 5154, in backup_get 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server project_only=project_only) 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/cinder/db/sqlalchemy/api.py", line 5165, in _backup_get 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server raise exception.BackupNotFound(backup_id=backup_id) 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server cinder.exception.BackupNotFound: Backup 7a15b9ec-7648-483f-ad32-6074567eca2a could not be found. 2020-03-30 14:53:21.341 25018 ERROR oslo_messaging.rpc.server [0] https://github.com/openstack/cinder/blob/e79b98367bd72f0323258dc0506de28b31c4aa48/cinder/backup/manager.py#L448 + + + + [Impact] + + Whenever an admin creates a backup for a tenant volume, all subsequent + incremental backups will have a silent error during creation when + linking the dependent backup to its parent because the code detects it + has a parent (by listing backups
[Bug 1871214] Re: [SRU] nfsd doesn't start if exports depend on mount
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: Incomplete => Won't Fix -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871214] Re: [SRU] nfsd doesn't start if exports depend on mount
** 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 verification-done-focal -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871214] Re: [SRU] nfsd doesn't start if exports depend on mount
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871214] Re: [SRU] nfsd doesn't start if exports depend on mount
** 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 and set up /etc/exports to export it 3) Reboot 4) Notice nfs-server does not start. Check journalctl and see it was because of "exportfs -r" returning -1 because /data/dir1 is not available. In Xenial (1:1.2.8-9ubuntu12.2), exportfs always returns 0, so this bug is not present there. This can be workaroundable in two ways: 1) Editing nfs-server.service and adding "-" in "ExecStartPre=/usr/sbin/exportfs -r" to be "ExecStartPre=-/usr/sbin/exportfs -r". This will retain xenial behavior. 2) Editing nfs-server.service and removing "Before=remote-fs-pre.target" and adding "RequiresMountsFor=/data". This will cause the systemd service load ordering to change, and nfs-server will wait for /data to be available. #2 is the upstream approach with commit [0] where this new comment identifies mount dependencies and automatically sets up RequiresMountFor. [0] http://git.linux-nfs.org/?p=steved/nfs- utils.git;a=commitdiff;h=4776bd0599420f9d073c9e2601ed438062dccd19 === [Impact] Users attempting to export folders from iSCSI or any remote mounted filesystem will experience their exports not being available at system start up, requiring workarounds or manual intervention. [Test case] 1. Reproducing the bug: 1a. Set up a ISCSI client to a 1GB+ volume 1b. Format /dev/ using mkfs.xfs 1c. Mount it in /data and set fstab as follows to mount at boot UUID="" /data xfs defaults,auto,_netdev 0 0 1d. Create a folder in /data like /data/dir1 and set permissions as follows chmod 777 /data/dir1 chown nobody:nogroup /data/dir1 1e. Set up /etc/exports as follows to export it - data/dir1 *(rw,async,root_squash,subtree_check) + /data/dir1 *(rw,async,root_squash,subtree_check) 1f. Reboot 1g. Notice nfs-server does not start. Running "showmount -e" displays error. 2. No cleanup necessary 3. Install the updated package that contains the fix 4. Confirming the fix: 4a. Reboot - 4b. Notice nfs-server starts sucessfully, "showmount -e" displays the exports. - + 4b. Notice nfs-server starts sucessfully, "showmount -e" displays the exports. [Regression Potential] Regression potential is minimal. The dependency commit only moves code around and the actual fix only introduces an external systemd-generator without changing actual pre-existing code. I tested and confirmed that the fix introduced [0] also covers the fix removed [1], so there should not be any regression on this particular code change as well. [1] http://git.linux-nfs.org/?p=steved/nfs- utils.git;a=commitdiff;h=1e41488f428cd36b200b48b84d31446e38dfdc50 - [Other Info] -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871214] Re: [SRU] nfsd doesn't start if exports depend on mount
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 understand that the fix is a bit complex for a bionic SRU, therefore an alternative could be workaround #1. I tested workaround #1 within the scope of the bug and also a few corner cases that came to my mind, and I can test it more extensively to ensure it is safe for a bionic SRU. What do you think about it? Do you think workaround #1 could be SRU'ed into bionic? Just to add a bit more context to it: in xenial exportfs always returns 0, regardless of any error or what happens, therefore nfsd is always run and is never prevented from running by exportfs failing. This is why the bug doesn't happen in xenial. The motivation that led to exportfs return value changing was so it could be properly scripted (as far as I can tell, it was quite a controversial change, reverted and added back, see [1]). Given that for the SRU of workaround #1 we would be changing just the systemd file to add a "-" to ExecStartPre, the previous (xenial) behavior is maintained in the system boot case, but it could still return != 0 when scripted. The impact is also minor and easier to revert (it is a one-liner) Also, one of the corner cases that I investigated is that, in the xenial behavior, the export can be created by nfsd even though the path is not available. At boot time, the export would be available a few seconds later when the path is available. Anyone trying to mount the path in that short time window will not succeed (or ever if the path fails to be mounted). In xenial, you can end up in the same situation manually by setting up an export that doesn't exist, not necessarily having to be set up at boot time, as this workflow is not prevented at all. [1] http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=history;f=utils/exportfs/exportfs.c;h=a04a78984a6e4eac4321ca9cafcf5a3bace0486c;hb=HEAD -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871214] Re: [SRU] nfsd doesn't start if exports depend on mount
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. https://bugs.launchpad.net/bugs/1871214 Title: [SRU] nfsd doesn't start if exports depend on mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871214] Re: [SRU] nfsd doesn't start if exports depend on mount
** 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/5363647/+files/lp1871214_focal.debdiff ** Patch added: "lp1871214_focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+attachment/5363649/+files/lp1871214_focal.debdiff -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871214] Re: [SRU] nfsd doesn't start if exports depend on mount
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: nfs-utils (Ubuntu Focal) Status: New => In Progress ** Patch added: "lp1871214_focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+attachment/5363647/+files/lp1871214_focal.debdiff -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871214] Re: [SRU] nfsd doesn't start if exports depend on mount
** 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 and set up /etc/exports to export it 3) Reboot 4) Notice nfs-server does not start. Check journalctl and see it was because of "exportfs -r" returning -1 because /data/dir1 is not available. In Xenial (1:1.2.8-9ubuntu12.2), exportfs always returns 0, so this bug is not present there. This can be workaroundable in two ways: 1) Editing nfs-server.service and adding "-" in "ExecStartPre=/usr/sbin/exportfs -r" to be "ExecStartPre=-/usr/sbin/exportfs -r". This will retain xenial behavior. 2) Editing nfs-server.service and removing "Before=remote-fs-pre.target" and adding "RequiresMountsFor=/data". This will cause the systemd service load ordering to change, and nfs-server will wait for /data to be available. #2 is the upstream approach with commit [0] where this new comment identifies mount dependencies and automatically sets up RequiresMountFor. [0] http://git.linux-nfs.org/?p=steved/nfs- utils.git;a=commitdiff;h=4776bd0599420f9d073c9e2601ed438062dccd19 + + === + + [Impact] + + Users attempting to export folders from iSCSI or any remote mounted + filesystem will experience their exports not being available at system + start up, requiring workarounds or manual intervention. + + [Test case] + + 1. Reproducing the bug: + + 1a. Set up a ISCSI client to a 1GB+ volume + 1b. Format /dev/ using mkfs.xfs + 1c. Mount it in /data and set fstab as follows to mount at boot + + UUID="" /data xfs defaults,auto,_netdev 0 0 + + 1d. Create a folder in /data like /data/dir1 and set permissions as + follows + + chmod 777 /data/dir1 + chown nobody:nogroup /data/dir1 + + 1e. Set up /etc/exports as follows to export it + + data/dir1 *(rw,async,root_squash,subtree_check) + + 1f. Reboot + 1g. Notice nfs-server does not start. Running "showmount -e" displays error. + + 2. No cleanup necessary + + 3. Install the updated package that contains the fix + + 4. Confirming the fix: + + 4a. Reboot + 4b. Notice nfs-server starts sucessfully, "showmount -e" displays the exports. + + + [Regression Potential] + + Regression potential is minimal. The dependency commit only moves code + around and the actual fix only introduces an external systemd-generator + without changing actual pre-existing code. + + I tested and confirmed that the fix introduced [0] also covers the fix + removed [1], so there should not be any regression on this particular + code change as well. + + [1] http://git.linux-nfs.org/?p=steved/nfs- + utils.git;a=commitdiff;h=1e41488f428cd36b200b48b84d31446e38dfdc50 + + + [Other Info] -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871214] Re: [SRU] nfsd doesn't start if exports depend on mount
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] http://git.linux-nfs.org/?p=steved/nfs- utils.git;a=commitdiff;h=0386fc1757838a096ae318347bc0bbd3ba94570b -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871214] Re: [SRU] nfsd doesn't start if exports depend on mount
** 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 => Fix Committed -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871214] Re: nfsd doesn't start if exports depend on mount
** 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: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871214] Re: nfsd doesn't start if exports depend on mount
** 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 it in /data and set fstab to mount at boot 2) Create a folder in /data like /data/dir1 and set up /etc/exports to export it 3) Reboot 4) Notice nfs-server does not start. Check journalctl and see it was because of "exportfs -r" returning -1 because /data/dir1 is not available. In Xenial (1:1.2.8-9ubuntu12.2), exportfs always returns 0, so this bug is not present there. This can be workaroundable in two ways: 1) Editing nfs-server.service and adding "-" in "ExecStartPre=/usr/sbin/exportfs -r" to be "ExecStartPre=-/usr/sbin/exportfs -r". This will retain xenial behavior. 2) Editing nfs-server.service and removing "Before=remote-fs-pre.target" and adding "RequiresMountsFor=/data". This will cause the systemd service load ordering to change, and nfs-server will wait for /data to be available. #2 is the upstream approach with commit [0] where this new comment identifies mount dependencies and automatically sets up RequiresMountFor. - [0] http://git.linux-nfs.org/?p=steved/nfs- utils.git;a=commitdiff;h=4776bd0599420f9d073c9e2601ed438062dccd19 -- 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: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871214] [NEW] nfsd doesn't start if exports depend on 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 /etc/exports to export it 3) Reboot 4) Notice nfs-server does not start. Check journalctl and see it was because of "exportfs -r" returning -1 because /data/dir1 is not available. In Xenial (1:1.2.8-9ubuntu12.2), exportfs always returns 0, so this bug is not present there. This can be workaroundable in two ways: 1) Editing nfs-server.service and adding "-" in "ExecStartPre=/usr/sbin/exportfs -r" to be "ExecStartPre=-/usr/sbin/exportfs -r". This will retain xenial behavior. 2) Editing nfs-server.service and removing "Before=remote-fs-pre.target" and adding "RequiresMountsFor=/data". This will cause the systemd service load ordering to change, and nfs-server will wait for /data to be available. #2 is the upstream approach with commit [0] where this new comment identifies mount dependencies and automatically sets up RequiresMountFor. [0] http://git.linux-nfs.org/?p=steved/nfs- utils.git;a=commitdiff;h=4776bd0599420f9d073c9e2601ed438062dccd19 ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New -- 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: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766126] Re: exportfs always returns success status
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1766126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840465] Re: [SRU] Fails to list security groups if one or more exists without rules
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 groups if one or more exists without rules To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1840465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840465] Re: [SRU] Fails to list security groups if one or more exists without rules
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. https://bugs.launchpad.net/bugs/1840465 Title: [SRU] Fails to list security groups if one or more exists without rules To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1840465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840465] Re: [SRU] Fails to list security groups if one or more exists without rules
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 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 this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1840465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840465] Re: [SRU] Fails to list security groups if one or more exists without rules
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. https://bugs.launchpad.net/bugs/1840465 Title: [SRU] Fails to list security groups if one or more exists without rules To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1840465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840465] Re: [SRU] Fails to list security groups if one or more exists without rules
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 added logging to confirm that it was indeed the case, and
got:
[Tue Nov 12 22:32:51.766942 2019] [wsgi:error] [pid 26153:tid
139930429884160] [remote 10.5.0.43:40358] sg: {'id': '40ca8baa-
a3a5-412d-b955-7f9fb3e86e26', 'name': 'test3', 'tenant_id':
'a3ef2c1a2a8e4b628f592e0f87ef3c11', 'description': '',
'security_group_rules': [], 'tags': [], 'created_at':
'2019-11-12T22:11:56Z', 'updated_at': '2019-11-12T22:12:03Z',
'revision_number': 3, 'project_id': 'a3ef2c1a2a8e4b628f592e0f87ef3c11'}
I also re-tested this with a limited user account, same results.
I proceeded to upgrade the package, confirmed the code has been changed
and includes that fix. Ran the test case and saw that it does not cause
any problems. Added additional logging to confirm the new condition (the
fix) is not invoked as it is not necessary and indeed it was not being
invoked.
I briefly checked neutron, python-neutronclient and horizon code, but I
haven't been able to track down the change that caused the key
'security_group_rules' to no longer be missing.
I proceeded to reproduce the problem in xenial-queens to re-confirm the
test case, and I couldn't.
Therefore my conclusion is that the test case needs to be improved, as
it seems to be missing details that are required to reproduce the
problem.
--
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 this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1840465/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840465] Re: [SRU] Fails to list security groups if one or more exists without rules
** 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 this bug go to: https://bugs.launchpad.net/horizon/+bug/1840465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840465] Re: [SRU] Fails to list security groups if one or more exists without rules
** 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, 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 this bug go to: https://bugs.launchpad.net/horizon/+bug/1840465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840465] Re: [SRU] Fails to list security groups if one or more exists without rules
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 notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1840465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840465] Re: [SRU] Fails to list security groups if one or more exists without rules
** 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. https://bugs.launchpad.net/bugs/1840465 Title: [SRU] Fails to list security groups if one or more exists without rules To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1840465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840465] Re: [SRU] Fails to list security groups if one or more exists without rules
** 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. https://bugs.launchpad.net/bugs/1840465 Title: [SRU] Fails to list security groups if one or more exists without rules To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1840465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840465] Re: [SRU] Fails to list security groups if one or more exists without rules
** 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
- data = function(self, request, *args, **kw)
- File
"/usr/share/openstack-dashboard/openstack_dashboard/api/rest/network.py", line
44, in get
- security_groups = api.neutron.security_group_list(request)
- File "/usr/lib/python2.7/site-packages/horizon/utils/memoized.py", line 95,
in wrapped
- value = cache[key] = func(*args, **kwargs)
- File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py",
line 1641, in security_group_list
- return SecurityGroupManager(request).list(**params)
- File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py",
line 372, in list
- return self._list(**params)
- File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py",
line 359, in _list
- return [SecurityGroup(sg) for sg in secgroups.get('security_groups')]
- File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py",
line 240, in __init__
- for rule in sg['security_group_rules']]
+ File
"/usr/share/openstack-dashboard/openstack_dashboard/api/rest/utils.py", line
127, in _wrapped
+ data = function(self, request, *args, **kw)
+ File
"/usr/share/openstack-dashboard/openstack_dashboard/api/rest/network.py", line
44, in get
+ security_groups = api.neutron.security_group_list(request)
+ File "/usr/lib/python2.7/site-packages/horizon/utils/memoized.py", line 95,
in wrapped
+ value = cache[key] = func(*args, **kwargs)
+ File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py",
line 1641, in security_group_list
+ return SecurityGroupManager(request).list(**params)
+ File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py",
line 372, in list
+ return self._list(**params)
+ File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py",
line 359, in _list
+ return [SecurityGroup(sg) for sg in secgroups.get('security_groups')]
+ File "/usr/share/openstack-dashboard/openstack_dashboard/api/neutron.py",
line 240, in __init__
+ for rule in sg['security_group_rules']]
KeyError: 'security_group_rules'
+
+ ===
+
+ [Impact]
+
+ By default, new security groups created through horizon or CLI include 2
+ default security rules. Upon managing those rules and removing them (to
+ perhaps add others or limit traffic completely), the security group page
+ errors out and prevents listing of *all* security groups if the empty
+ security group is within the list to be displayed. Therefore, not only
+ is the empty security group affected, but all others as well, as they
+ cannot be listed. The root cause of the bug is that the payload does not
+ include the expected key "security_group_rules" for that security group
+ when there are no rules.
+
+ A fix has been implemented for Train (from master), Stein, Rocky and
+ Queens releases and should be backported so the issue is addressed on
+ previous those releases. The fix prevents the crash by ensuring the key
+ "security_group_rules" is present with an empty list in case it was not
+ included in the payload.
+
+ [Test Case]
+
+ 1. Reproducing the issue
+
+ 1a. Go to the Security Group section at Project > Network > Security Groups
+ 1b. Create a security group
+ 1c. Click the Manage Rules button for that security group you just created
+ 1d. Delete the two default rules
+ 1e. Go back to the Security Group section at Project > Network > Security
Groups
+ 1f. Security groups are no longer being listed and there will be an error
popup: "Error: Unable to retrieve security groups.".
+
+ 2. Install the package with the fixed code
+
+ 3. Confirm bug has been fixed
+
+ 3a. Repeat step 1a, you will notice that now security groups can be
+ listed, including the empty one you had previously created
+
+ 3b. Repeat steps 1b through 1e, the newly created and emptied security
+ group can also be listed along the others.
+
+ [Regression Potential]
+
+ Given the following indicators:
+
+ a. Upstream CI passed, for all releases the fix is being backported.
+ b. The small scope of the problem: a key error prevents the page from being
rendered. The fix is to make sure the key is always present, since it is always
expected.
+ c. The fix is very simple, and during tests we can see that the other pages
handle an empty list properly as the value for the "security_group_rules".
+
+ We can safely say there the regression potential is negligible.
** 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
[Bug 1840465] Re: [SRU] Fails to list security groups if one or more exists without rules
** 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. https://bugs.launchpad.net/bugs/1840465 Title: [SRU] Fails to list security groups if one or more exists without rules To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1840465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821594] Re: [SRU] Error in confirm_migration leaves stale allocations and 'confirming' migration state
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: verification-queens-done -- 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 allocations and 'confirming' migration state To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1821594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821594] Re: [SRU] Error in confirm_migration leaves stale allocations and 'confirming' migration state
** 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. https://bugs.launchpad.net/bugs/1821594 Title: [SRU] Error in confirm_migration leaves stale allocations and 'confirming' migration state To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1821594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
