horizon on vip__public becames unavailable after warm reboot of primary controller

Bug #1657532 reported by Ekaterina Khomyakova
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
High
Igor Gajsin
Mitaka
Confirmed
High
Igor Gajsin

Bug Description

Fuel 9.2 #771, dvs 3.1 #229

Steps to reproduce:
  1. Prepare master (on 10.109.5.2 (as the second env)) with plugin, configure vCenter
  2. Add nodes with the following roles:
       * Controller
       * Controller
       * Controller
       * Compute + Cinder
       * Cinder-VMWare
  3. Deploy environment
  4. Try to access the Horizon by following the link on Dashboard

Actual result:
  * Fuel redirects to http://10.109.8.6/ and it returns 503 Service Unavailable
  * `openstack servers list` (and much others) doesn't work from console (but e.g. `nova list` works)
  * Sanity OSTF (and all others) fail

Expected results:
  * Fuel redirects to http://10.109.6.3/, where the Horizon is actually is
  * openstack works
  * OSTF pass

summary: - v_public becames unavailable after warm reboot of primary controller
+ horizon on vip__public becames unavailable after warm reboot of primary
+ controller
Changed in fuel:
importance: Undecided → High
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

Please provide diagnostic snapshot or env.

Changed in fuel:
status: New → Incomplete
Revision history for this message
Ekaterina Khomyakova (ekhomyakova) wrote :
Revision history for this message
Ekaterina Khomyakova (ekhomyakova) wrote :
Revision history for this message
Ekaterina Khomyakova (ekhomyakova) wrote :
Revision history for this message
Ekaterina Khomyakova (ekhomyakova) wrote :
Revision history for this message
Ekaterina Khomyakova (ekhomyakova) wrote :
Revision history for this message
Ekaterina Khomyakova (ekhomyakova) wrote :

Env was provided.

Changed in fuel:
status: Incomplete → New
Changed in fuel:
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
Igor Gajsin (igajsin)
Changed in fuel:
assignee: Fuel Sustaining (fuel-sustaining-team) → Igor Gajsin (igajsin)
Igor Gajsin (igajsin)
Changed in fuel:
status: New → Confirmed
Revision history for this message
Igor Gajsin (igajsin) wrote :

Looks like there is the problem whithin our virtual infrastructure. There was no connectivity between the haproxy netns and b-mgmt. Now I can't reproduce that bug and wait when it reproduces.

Changed in fuel:
status: Confirmed → Incomplete
Igor Gajsin (igajsin)
Changed in fuel:
status: Incomplete → Confirmed
Revision history for this message
Igor Gajsin (igajsin) wrote :

Please forget that I told before. The reason of that bug is absence of the route* for the managemnt network in the netns haproxy.

So I keep research of the wrong behaviour of the ocf script ns_IPaddr2

---------
* - like 10.109.1.0/24 via 240.0.0.1 dev hapr-ns metric 10000

Revision history for this message
Igor Gajsin (igajsin) wrote :

At least we have workaround: # crm resource restart clone_p_haproxy

tags: added: release-notes
Revision history for this message
Maria Zlatkova (mzlatkova) wrote :
tags: added: release-notes-done
removed: release-notes
Roman Vyalov (r0mikiam)
Changed in fuel:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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