The 'Attached To' column in the Volumes table was inconsistent with
the rest of the columns in that it did not display anything when a
particular volume was not attached to any instances.
This change results in displaying the status of 'None' on the
'Attached To' column as a dash[-].
The status is 'None' when a particular volume is not attached to any
instance.
Closes-Bug: #1743226
Change-Id: Ife6221351c02b222b326b06cb45c685bd3cffbdf
During deleting, instance have interphases like task=deleting
or status=deleted. During the test assertion can happen that
instance is still correctly in the deleting process but the
test fail because of expectation is that instance from sdk is
None
Change-Id: Ic11b6d23aac2cfb309f4ca23b137bb3458154935
The pymongo library is required only when profiler middleware is
enabled. The middleware is meant for development (The module path
contains developer) and is not for production.
Also it's not directly imported but used via osprofiler. In case
a different backend is used in osprofiler then the library is not at
all used. Users should install the appropriate library according to
the backend actually used, based on the extra dependencies of
osprofiler.
Change-Id: I1258a3e3c86c98a3b35ee413ae113f1eb7dcf00b
These are detected as errors since the clean up was done[1] in
the requirements repository.
[1] 314734e938f107cbd5ebcc7af4d9167c11347406
Also remove the note about old pip's behavior because resolver in
recent pip does not require specific order.
Change-Id: Ic8a34616a5723517cad880da3d9b75d03808c265
Make the placement API client respect the OPENSTACK_SSL_NO_VERIFY and
OPENSTACK_SSL_CACERT configuration options, so that it can work properly
in TLS-everywhere deployments.
Change-Id: Id0bb085bdf411eef240c3d50da56016c0a1d075c
Allow port_get to fail when listing all floating ips as not all users
are allowed to get ports from all other users such as admin.
Change-Id: Ieeddc2451adb79405fe3ac72fdf5900ca7c5f628
Compound sorting is an existing feature on the Horizon dashboard.
It is not obvious, however.
This change should bring this feature to the attention of users.
It should also guide users into how to use the feature when sorting.
Horizon DataTables.
DocImpact
Closes-Bug: #1287418
Implements: compound sorting
Change-Id: I810e863e01ca54f6751e1608e99ce97833597aff
CSV generation is not fully sanitized to prevent CSV injection.
According to https://owasp.org/www-community/attacks/CSV_Injection,
we have to use the following sanitization:
- Wrap each cell field in double quotes
- Prepend each cell field with a single quote
- Escape every double quote using an additional double quote
The patch https://review.opendev.org/c/openstack/horizon/+/679161
takes care of the double quotes. This patch adds a single quote to
the cell fields beginning with specific characters, so their content
will be read by a spreadsheet editor as text, not a formula.
Closes-Bug: #2048106
Change-Id: I882fe376613ff1dc13a61f38b59d2a2567dbba7d
Add file to the reno documentation build to show release notes for
stable/2024.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.
Sem-Ver: feature
Change-Id: Ifef27c7828301a8d726442dd759c7e867e172724
Previous change I8438bedaf7cead452fc499e484d23690b48894d9
attempted to address bug LP#1728031 by improving upon
patch https://review.opendev.org/854005 but missed the
line that allows the keystone client to properly
authenticate a cloud admin user that IS NOT in the
default domain.
Without this 1-line fix, a cloud admin that is not
in the default domain will face an "incorrect admin
password" error in the UI (despite the admin password
being correct) and an authentication error in the logs,
regardless of the endpoint type used (adminURL,
internalURL or publicURL).
Closes-bug: #1728031
Change-Id: I018e7d9cb84fd6ce8635c9054e15052ded7e9368
This patch updates default policy-in-code rules in horizon based on
nova/neutron/cinder/keystone RC deliverables. It doesn't update policy
rules for glance as I have found no changes in their policy rules.
Horizon needs to update default policy-in-code rules for all backend
services before releasing the horizon[1].
[1] https://docs.openstack.org/horizon/latest/contributor/policies/releasing.html#things-to-do-before-releasing
Change-Id: I7437b3a46377c18f026db103237b4d107dc787cb
The list of users assigned to a project becomes invisible when a domain context
is set in Horizon. If a domain context is set, the user list call should
provide a list of users within the specified domain context, rather than users
within the user's own domain.
Groups tab of project also has the same problem.
Change-Id: Ia778317acc41fe589765e6cd04c7fe8cad2360ab
Closes-Bug: #2054799
Zuul
OpenStack Release Bot