Some Jenkins nodes fail create_instance integration test due to missing network
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | OpenStack Dashboard (Horizon) |
High
|
Timur Sufiev | ||
Bug Description
Although usually devstack has pre-created network, some Jenkins nodes don't have it. We should keep this possibility in mind when creating an instance in integration test. As a proof, below is a on-failure screenshot that was taken several times in a row for commit https:/
| Timur Sufiev (tsufiev-x) wrote : | #1 |
| Changed in horizon: | |
| importance: | Undecided → High |
| assignee: | nobody → Timur Sufiev (tsufiev-x) |
| Timur Sufiev (tsufiev-x) wrote : | #2 |
Fix proposed to branch: master
Review: https:/
| Changed in horizon: | |
| status: | New → In Progress |
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 5a9413c28b37f9a
Author: Timur Sufiev <email address hidden>
Date: Thu Feb 4 13:02:04 2016 +0300
Zoom out pages in i9n tests
Since Selenium 2.50.1 release it's no longer possible to click
elements which are outside of visible viewport. To keep both tests
working and error screenshots still visible, standard xvfb screensize
is set to 1920x1080 and page scale is set to 67%.
Also temporarily disable create_instance test since it fails on some
nodes due to missing network.
Related-Bug: #1542211
Closes-Bug: #1541876
Change-Id: Ie96606cf52860d
| Changed in horizon: | |
| assignee: | Timur Sufiev (tsufiev-x) → Alexandra (aallakhverdieva) |
| Changed in horizon: | |
| assignee: | Alexandra (aallakhverdieva) → Timur Sufiev (tsufiev-x) |
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 0419b0e2e6a276b
Author: Timur Sufiev <email address hidden>
Date: Fri Feb 5 13:23:21 2016 +0300
Ensure that integration tests are being run in proper project
Admin users run tests in an admin project, regular users run them in a
demo project. That should prevent situations when tests don't have an
access to a resources created in a project different from the current
one.
Closes-Bug: #1542211
Change-Id: I497648ce5126e1
| Changed in horizon: | |
| status: | In Progress → Fix Released |
This issue was fixed in the openstack/horizon 9.0.0.0b3 development milestone.
Upon further investigation of devstack setup logs it seems that node has a network, but an instance is being created in a project different from the one that network belongs to, thus the network is inaccessible during instance creation.