Previously deleting a network shows an unclear error message
and it is not easy for a user to identify the reason:
Error: Failed to delete network <network_name>
With this fix it will now show proper error message including
the error reason when neutron returns 409 (Conflict) response.
NOTE: This is a fix for the https://review.openstack.org/#/c/140614/
patch, which I couldn't restore.
Change-Id: I5779725f1095d59a012d8e6cf6e47bbd11dda36a
Closes-Bug: #1400667
This has been supported in the keystone API since version 3.6
Although not used in horizon (yet) some third party plugins may
require this.
Closes-Bug: #1729449
Change-Id: I961c1681b757134037ae767ac750afa36476d630
Data formats added for qos panel - this makes the updated and created
date formats legible.
Change-Id: Ib0e364b51de6388395506a1f84454c9d1dc874da
Closes-Bug: #1721502
os-virtual-interfaces is part of nova-network, which Horizon does not support.
No code in Horizon is using this function, and it is no longer necessary.
Change-Id: I118c81db1e581487384677aa0b0020dd35001a29
In Nova Compute API microversion 2.19, you can specify a “description”
attribute when creating, rebuilding, or updating a server instance. This
description can be retrieved by getting server details, or list details
for servers, this patch adds support for this attribute for instance in
horizon.
Change-Id: Ic9217234021d236aee8295915f1a9c3c544396b0
Implement-blueprint: support-description-for-instance
If the 'network_availability_zone'-extension is enabled, this patch adds a
field to the Create Network-workflow named 'Availability Zone Hints'.
Change-Id: Ic4206d5765c2d01afedf0e64f9aa50ffce76b661
Closes-Bug: #1725617
When creating a router, or when setting a gateway on a router - a checkbox
is displayed, which can be unchecked to disable SNAT.
Change-Id: I8bc040018645fe2bde534b7d48e14c17984cc9c4
Closes-bug: #1673076
This patch changes mox to mock for the following test module:
* openstack_dashboard/dashboards/project/volumes/tests.py
The next patch in this series will finish migration to mock in this
moudle with tests refactoring making code cleaner and more supportable.
Change-Id: Icb40ee4d844f34f37839c0e74de29a47c3d3f228
Partially-Implements: blueprint mock-framework-in-unit-tests
This patch changes mox to mock for the following test module:
* openstack_dashboard/dashboards/admin/volumes/tests.py
Change-Id: Id487feb397207b3544c9398a446077e3f6a39b1a
Partially-Implements: blueprint mock-framework-in-unit-tests
It's a first patch in the series mox => mock migration.
This patch changes mox to mock for the following test modules:
* openstack_dashboard/test/api_tests/cinder_tests.py
* openstack_dashboard/test/api_tests/cinder_rest_tests.py
Change-Id: Ic7283f139855c0017b840e8136ded4f05abcde66
Partially-Implements: blueprint mock-framework-in-unit-tests
Previously, updating the quota value for instance on a project that
the user was not currently scoped to would validate the new quota
value by comparing with the usage of the currently scoped project.
The cause of this error was an incorrect use of the server list
parameters.
According to the comment in nova source:
d43d1d6734/nova/api/openstack/compute/servers.py (L277-L280)
and the comments in this bug:
https://bugs.launchpad.net/nova/+bug/1185290
indicate that the tenant_id or project_id flag cannot be used without
the --all-tenants flag.
The fix involves passing the --all-tenants flag when querying instance usage
for any project the user is not currently scoped to. It also removes the
passing of the tenant_id flag when querying the current project.
Tests were also updated to match the new behavior by not passing the
tenant_id to the API call to list servers where the target project is
the currently scoped project.
Change-Id: Iee06bc1c8ccd50f595f4cb274f956c13495c8494
Closes-Bug: #1713724
If the 'network_availability_zone'-extension is enabled, this patch adds a
column in the Networks-table named 'Availability Zones'.
Change-Id: Iea2bac351b922a0d267c4a55e0d74f6c2639d967
Partial-Bug: #1725617