mox doesn't work on Python 3, whereas mox3 works on Python 2 and Python
3. Cinder, Nova and many other projects already replaced mox with mox3.
mox3 is now maintained by OpenStack.
Partial-Implements: blueprint porting-python3
Change-Id: I10e6a9754ebd58a2640d73ec8966527c3aa1fe9a
The projects page is based on tnovacik's regions patches.
Add tests for create, delete project.
Partially implements blueprint: selenium-integration-testing
Change-Id: I89ecc3960ec27259eb2e4666119e6a6f682e1511
The search opts for volume/snapshot list should be 'all_tenants' and
'project_id' instead of 'alltenants' and 'tenant_id'.
Change-Id: I9ab71421447b3f8fb402247df3290fa3066bf8c5
Closes-bug: #1469589
We have COMPRESS_OFFLINE disabled by default in our tests in horizon,
we need to do the same for dashboard. Refer to bug for detailed
explanation.
Change-Id: Ib8480c3a91e6c06fc5b5ad0c08df88aada774b33
Closes-Bug: #1469293
Currently, we have tests for plugin but they are not comprehensive enough.
Considering that we are adding more logic to javascript, we need to ensure
that they are properly injected in these plugin.
Change-Id: Ie9186c445962e3142f2b33027b6556f9eb3b34a5
Closes-bug: #1468547
In the user table, description column is missing when using keystone V3
This patch add the 'Description'column in User table. This also
change to add 'Description' field the user_create and user_update form.
Change-Id: I90bb7a644f8f29ae0055c6c2ffc688a9b709f300
Closes-Bug: #1463247
The tests are failing for different reasons (see the referenced bug),
so skip them for now.
Change-Id: I9622ed1ba7444089fa1ee6d0c915b8d31c752af6
Related-Bug: #1467950
Neutron FWaaS firewall object does not support 'shared' attribute
at now and 'shared' attribute is not included in API response.
This commmit removes 'shared' attribute for firewall object.
For more detail of the background, please see the bug report.
Note that 'shared' attributes for firewall rule and policy
are supported. This commit only affect the firewall object.
Change-Id: I5787529395e0005ce1efee48beb6f0f688c1c736
Closes-Bug: #1465440
In 'LbaasApiTests.test_pool_get' test case 'show_health_monitor' api
is returning wrong value. It should return dict of 'health_monitor' dict.
Actually it is returning dict of 'health_monitors' list, which is wrong.
This patch modifying the test case to return expected value.
Change-Id: Ia68bab3f71a9ebab5018061c76cd8eda6b09e66c
Closes-Bug: #1467516
The tests consistently fails, probably because the availability
of the image in the table is checked too soon. Add a bit of delay
with a new wait method.
Change-Id: I9e39c35fb67455b4e4f3c2b12265b8540420ad01
Closes-Bug: #1466744
Currently we have test_sahara_image_registry failing the gate.
It will require time to investigate and fix it.
While so I suggest we disable it so it wouldn't -1 everyone.
Change-Id: Iaee12246654d085e5a570c02dfde7406dfc12dc2
HORIZON_CONFIG is still being used to set default values for
dashboards and default_dashboard. This method of specifying these
is deprecated. All of these default behaviors are now covered in
the enabled directory. Removing them to remove seeing the
deprecation warning every time tests run.
Closes-Bug: #1466671
Change-Id: Ifd833288f0bf2992bd810a93a74a799232f119ab
This patch adds missing content-length header
param into swift_upload_object() method.
Without it object upload handling could be failed
with "411 Length Required" error if Ceph is used
as an object storage.
Change-Id: Id0813806abb36a6f015efd13ec987492a3701476
Closes-Bug: #1352256
The Default Neutron implementation needs a router with a gateway to associate a
FIP. So by default a topology check will be performed by horizon to list only
VM ports attached to a network which is itself attached to a router with an
external gateway. This is to prevent from setting a FIP to a port which will
fail with an error.
Some Neutron vendors do not require it. Some can even attach a FIP to any port
(e.g.: OpenContrail) owned by a tenant.
This patch adds a setting allowing to bypass the topology check in order to let
the user associate a FIP to an instance on a subnet with no router if the
Neutron backend allows it.
Change-Id: I1bf8bd0113a154c5e0bf0f75065b911f15db3e83
Closes-Bug: #1462902
Add fields missing from CREATE_IMAGE_FORM_FIELDS and are present on actual page.
Reason of test failing is that image creation form of horizon is differ
from the one described in the pageobject. Adding fields to
CREATE_IMAGE_FORM_FIELDS fixes test.
Closes-Bug: #1464651
Partially implements blueprint: selenium-integration-testing
Change-Id: I6baf6c1918f37cb3b6009919bfbe9615c336a101
This original method to retrieve user settings has been
replaced by https://review.openstack.org/#/c/170351/.
Remove old way to prevent confusion.
Change-Id: I4fec94a78168d48fee5b21d24064200b2aefce91
Closes-Bug: #1455246
The associate monitor fails to show monitors to choose from
within horizon. The monitor list code has changed where
you can no longer list monitors with a filter criteria.
This change switches to grab needed monitors one at a time.
Change-Id: Ibc5233028507c66de459e84e91f65c9557940ea5
Closes-bug: #1398754
The file openstack_dashboard/test/jasmine/jasmine_tests.py is not used;
it should be removed.
You can verify this by running the various tests:
./run_tests.sh --only-selenium
or going to <host:port>/jasmine/ in a debug environment
Change-Id: Ieefaf30bfd5612bd3180b67817745a170596b1e5
Closes-Bug: 1454804
We currently have two jasmine tests, one in horizon and one in dashboard.
We currently use two different templates and they are out of sync with each
other. Furthermore, we should extend the sources list, not override it,
because dashboard modules depends on code in horizon.
This patch fixes these issues.
Closes-bug: #1452446
Change-Id: I3fcbb1ea30b5e83a16f94fb31959270bd393593a
The metering forms were using the date picker functionality from the
d3 line chart library, this used to work when it was loaded as a whole
page as the d3 libary would run intending to setup any d3 graphs however
now it is being loaded as a modal the elements that would be affected by
the d3 code do not exist at page load time.
In order to get the date picker events to be added to the elements on
the form when the modal loads, the JS in the forms template has been
extended in this patch to support adding those events.
This patch also changes the data attributes on the form elements so that
they do not conflict with any d3 line chart elements.
Alongside the javascript this patch fixes bug to do with parsing the
dates in metering utils and adds UTs to prevent regression.
Change-Id: I4e239daa03b2f54e434254bac48ba0cceb037b5d
Closes-Bug: 1427756
Rather than hard-code the choices for the job type
dropdown, they are now generated from an api call
that factors-in currently loaded plugins. Also updated
the tests to utilize the new call.
Change-Id: I69f7100335bd35a891f23efd286da784c3d34e9f
Closes-Bug: #1371285
Revert fix from bug #1329050, which adds a plugin panel to its dashboard's
class. Adding a plugin panel to a dashboard whose class has its panels defined
in a tuple will fail because the new plugin cannot be appended to the tuple.
The code errors out before the panel gets added to the dashboard's panel list.
However, at this point, the panel has already been registered with the
dashboard. This causes Dashboard.get_panels() to see the panel in its registry
but not in its panel groups. Consequently, the panel gets put in the "Other"
panel group instead of its configured one, as described in bug #1378558.
By not adding the the plugin panel to its dashboard's class, the panel gets
added to its dashboard's panel list. Now the original issue from bug #1329050
resurfaces. The root cause of that is that every time Dashboard._autodiscover()
is called, it instantiates all its panel group classes, wiping out any panels
previously added to any of the panel groups. Avoid this by always processing
all the plugin panel groups before any of the plugin panels, which also ensures
that the panel groups exist before their panels.
Making this change exposed an issue where the Horizon URLs were being loaded
twice during the plugin infrastructure's unit tests, causing plugin panels to
be added multiple times to their dashboards. Fix that by removing the second,
unnecessary call. Also create a second test plugin panel group and panel to
test the scenarios described in the two bugs addressed here, adding two panel
groups at a time.
Change-Id: Id6a99c3ff18102c8f47431638d4dda98f14ec641
Closes-Bug: 1378558
Currently we using a meter-list for getting a "unit" for metric.
Meter list get all available metric on environment,
it's may be a thousands of records.
It's better to use sample-list for this metric with "limit" 1.
This request gets a 1 sample for queried metric.
Change-Id: I4bf0ab7ebcbcae1ddc90d8ee01d5f5a84ed4fbba
Related-bug: #1444456
This patch adds unit tests for the security group step. These tests are
focused around the controller and its related components (no selenium tests
or view tests).
Change-Id: I14dbc603e3bafdcebcb13b0ef7f77d05a26a2122
Partial-Bug: 1435869
This patch provides the rest API needed to
get settings that allow conditionally
displaying the volume device name
and admin password.
Examples:
settingsService.ifEnabled('setting').then(doThis);
settingsService.ifEnabled('setting', 'expected', 'default').then(doThis, elseThis);
Change-Id: I8d16f4b974786157c5aa562e2675e6e60aabc412
Partial-Bug: #1439906
Partial-Bug: #1439905
Adds support for resource_type, so retrieved namespaces will have
properties with proper prefixes.
Closes-Bug: 1439312
Change-Id: I4c2b450db8189c99624290a1d678fcaf509e1de6