Fuel for OpenStack

Public vip is incorrect after primary controller removal

Bug #1396016 reported by Sergey Kolekonov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Fuel Library (Deprecated)
Fuel for OpenStack 6.1
5.1.x
Won't Fix
Medium
Fuel Library (Deprecated)
Fuel for OpenStack 5.1.1-updates
6.0.x
Won't Fix
Medium
Unassigned
Fuel for OpenStack 6.0-updates
6.1.x
Confirmed
Medium
Fuel Library (Deprecated)
Fuel for OpenStack 6.1

Bug Description

  release: "5.1.1"
  api: "1.0"
  build_number: "34"
  build_id: "2014-11-23_21-01-00"
  astute_sha: "dade74af41d4972fe05a1c16ae1db2a2e60c6715"
  fuellib_sha: "444339cae21c369c1d95e96c1059d4099077138e"
  ostf_sha: "64cb59c681658a7a55cc2c09d079072a41beb346"
  nailgun_sha: "7580f6341a726c2019f880ae23ff3f1c581fd850"
  fuelmain_sha: "0fe3db7475b9f8b287c5b59cba94c9a40a8d8101"

Steps to reproduce:

- Deploy HA cluster with 1 controller and 1 compute
- Add another controller
- Remove primary controller
- Add a controller again

Actual result:
- After primary controller removal puppet on a new controller gets old public vip from astute.yaml, so Neutron API is unaccessible

Revision history for this message
Sergey Kolekonov (skolekonov) wrote :
Alexander Ignatov (aignatov)
Changed in fuel:
assignee: nobody → Fuel Library Team (fuel-library)
importance: Undecided → High
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

Could be a dup of https://bugs.launchpad.net/fuel/+bug/1390397

Changed in fuel:
milestone: none → 5.1.1
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

I'm not sure, if out current deployment approach supports re-assignment of the primary controller role. And looks like related bug is about the same. Nailgun team, could you please elaborate?

Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

I would conclude that we do not support such a use case right now. When you remove the controller, you change cluster state to unquorate, thus there is no guarantee that galera or rabbitmq will handle this situation and corresponding API requests will succeed. I will move it to 6.1 and mark it as medium bug.

Changed in fuel:
milestone: 6.0 → 6.1
importance: High → Medium
status: Incomplete → Confirmed
Revision history for this message
Nastya Urlapova (aurlapova) wrote :

Vladimir, we have to add this case to release notes in 6.0?

Fuel Devops McRobotson (fuel-devops-robot)
no longer affects: fuel/6.0.x
Changed in fuel:
status: Confirmed → New
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

This bug has no high deployment impact and has a medium priority in 6.1 and it should be the same for 5.x as well. According to comment #4 such case is not supported and should be addressed in next release.

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.