Fuel for OpenStack

Verifying network runs for 7 minutes

Bug #1254630 reported by Anastasia Palkina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Medium
Unassigned
Fuel for OpenStack 4.1

Bug Description

"release": "3.2.1",
"nailgun_sha": "26dddea2c1e5ff1a60e06fc337dbf30426515e4f",
"ostf_sha": "b7e1f8ab92ab0bd4bbf0ae8785daa59ac1be116e",
"astute_sha": "df6ddea3abc93fbe1cab9b4534d4d5e9508c95d6",
"fuellib_sha": "387259ed2e3afea8fbd54ed8ac92e20997a84a37"

1. Create new environment (CentOS, simple mode)
2. Choose VLAN segmentation
3. Add controller and compute nodes
4. Move to tab with network settings
5. Change VLAN ID Range: Start = 200, End = 205
6. Click button "Verify Networks"
7. Verifying networks hangs
8. After 7 minutes verification was finished

Revision history for this message
Anastasia Palkina (apalkina) wrote :
summary: - Verify Networks hangs for VLAN segmentation
+ Verifying network runs for 7 minutes
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
importance: Undecided → Medium
Mike Scherbakov (mihgen)
Changed in fuel:
milestone: none → 4.1
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
assignee: Dmitry Pyzhov (lux-place) → Fuel Python Team (fuel-python)
Revision history for this message
Aleksey Kasatkin (alekseyk-ru) wrote :

Cannot reproduce in VirtualBox on 236 iso. I get less than 2 minutes even with 50 VLAN IDs. It's about a minute for 6 VLAN IDs.

Revision history for this message
Aleksey Kasatkin (alekseyk-ru) wrote :

Logs state that deployment was running in parallel.
Please complete the description if this is reproducible yet.

Changed in fuel:
status: New → Incomplete
assignee: Fuel Python Team (fuel-python) → nobody
Revision history for this message
Dima Shulyak (dshulyak) wrote :

I did not manage to find 7 min delay.
But found one that last 3 mins, verify_network, deploy and redhat_release tasks was running in parallel, i assume for different clusters.
Nailgun sended task 2013-11-25 08:49:53, but orchestrator received it only 3 min later.
It seems this issue arise due to multiple tasks running in parallel in naily, and naily has only 3 threaded workers - which will become bottleneck if we would have more parallel tasks for clusters.

Dmitry Borodaenko (angdraug)
Changed in fuel:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.