[mos] Button 'Deassociate floating IP' disappeared from Horizon menu
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Won't Fix
|
Low
|
Timur Sufiev | ||
4.1.x |
Won't Fix
|
Low
|
Timur Sufiev | ||
5.0.x |
Won't Fix
|
Low
|
Timur Sufiev | ||
5.1.x |
Won't Fix
|
Low
|
Timur Sufiev | ||
6.0.x |
Won't Fix
|
Low
|
Timur Sufiev | ||
6.1.x |
Won't Fix
|
Low
|
Timur Sufiev | ||
7.0.x |
Won't Fix
|
Low
|
Timur Sufiev | ||
8.0.x |
Won't Fix
|
Low
|
Timur Sufiev |
Bug Description
"build_id": "2014-06-
"mirantis": "yes",
"build_number": "334",
"nailgun_sha": "0828946af6a2e7
"ostf_sha": "3690709d95c1f4
"fuelmain_sha": "7fbe99c86a4fff
"astute_sha": "55df06b2e84fa5
"release": "4.1B",
"fuellib_sha": "c64ffdc5e7bfe7
1. Create new environment (Ubuntu, simple mode)
2. Choose Savanna installation
3. Add compute, controller, cinder
4. Choose debugging
5. Start deployment. It was successful
6. Start OSTF tests. Test "Check network connectivity from instance via floating IP" has failed with error: Floating IP cannot be removed
7. Manually created instance, associate floating IP
8. Button 'Deassociate floating IP' disappeared from menu (see screen)
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Fuel Hardening Team (fuel-hardening) |
Changed in fuel: | |
importance: | Undecided → High |
Changed in fuel: | |
status: | New → Confirmed |
importance: | High → Medium |
Changed in fuel: | |
milestone: | 4.1.1 → 4.1.2 |
tags: | added: low-hanging-fruit |
no longer affects: | fuel/5.1.x |
summary: |
- Button 'Deassociate floating IP' disappeared from Horizon menu + [mos] Button 'Deassociate floating IP' disappeared from Horizon menu |
no longer affects: | fuel |
Changed in mos: | |
assignee: | nobody → Timur Sufiev (tsufiev-x) |
importance: | Undecided → Medium |
status: | New → Confirmed |
milestone: | none → 5.1 |
tags: | added: horizon |
Changed in mos: | |
milestone: | 5.1 → 6.0 |
tags: | added: release-notes |
Changed in mos: | |
milestone: | none → 6.0 |
Changed in mos: | |
milestone: | 6.0 → 6.0.1 |
no longer affects: | fuel/4.1.x |
no longer affects: | fuel/5.0.x |
Changed in mos: | |
status: | Confirmed → Won't Fix |
Changed in mos: | |
milestone: | 6.0.1 → 7.0 |
Changed in mos: | |
status: | Won't Fix → Confirmed |
tags: |
added: release-notes-done removed: release-notes |
Changed in mos: | |
status: | Triaged → Won't Fix |
I have couple of questions about your deployment:
1) VersionConflict: (six 1.4.1 (/usr/lib/ python2. 7/dist- packages) , Requirement. parse(' six<1.4. 1'))
I see this error in logs of several services. Under normal conditions this should not happen. Could you please check why requirements are not installed correctly?
2) Calling method <bound method FloatingIPContr oller.index of <nova.api. openstack. compute. contrib. floating_ ips.FloatingIPC ontroller object at 0x4f478d0>> _process_stack /usr/lib/ python2. 7/dist- packages/ nova/api/ openstack/ wsgi.py: 962 02T12:32: 12.203879+ 00:00 debug: 2014-06-02 12:32:06.626 10393 WARNING nova.openstack. common. db.sqlalchemy. session [req-73182e09- 21b3-4007- 8f70-203760db98 ae 2e53b942929e40e eae094e4a3faadd 2a b3edad09fe40482 29641c1b4b0c543 05] Got mysql server has gone away: (2006, 'MySQL server has gone away')
2014-06-
It seems that Nova API service is getting 'MySQL server has gone away' errors from time to time (>30 errors in log file) Seems that there are some issues with db connection and it may cause failures in many places across openstack. Is it possible that it may be the root of failures here?