Fuel for OpenStack

Nodes not removed from /etc/hosts

Bug #1467655 reported by Roman Sokolkov
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
Medium
MOS Maintenance
Fuel for OpenStack 7.0
6.0.x
Won't Fix
Medium
MOS Maintenance
Fuel for OpenStack 6.0-updates
6.1.x
Won't Fix
Medium
MOS Maintenance
Fuel for OpenStack 6.1-updates
7.0.x
Won't Fix
Medium
MOS Maintenance
Fuel for OpenStack 7.0
8.0.x
Confirmed
Medium
Fuel Library (Deprecated)
Fuel for OpenStack 8.0

Bug Description

Description:
/etc/hosts contains entries for nodes that were removed from cluster (or redeployed)

Environment:
- MOS 6.0
- any deployment mode
- any OS

How to reproduce:
1) Deploy cluster with 2 nodes (controller, compute).
2) Remove compute node from cluster (and push "Deploy changes")
3) Add same node to cluster (and push "Deploy changes")
4) Login to controller and check /etc/hosts
Expected result:
it will contain TWO entities (i.e. node-1, node-3)

Actual result:
it contains THREE entities (node-[1,2,3])

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "6.0"
  api: "1.0"
  build_number: "58"
  build_id: "2014-12-26_14-25-46"
  astute_sha: "16b252d93be6aaa73030b8100cf8c5ca6a970a91"
  fuellib_sha: "fde8ba5e11a1acaf819d402c645c731af450aff0"
  ostf_sha: "a9afb68710d809570460c29d6c3293219d3624d4"
  nailgun_sha: "5f91157daa6798ff522ca9f6d34e7e135f150a90"
  fuelmain_sha: "81d38d6f2903b5a8b4bee79ca45a54b76c1361b8"

See original description
Tags: feature
Revision history for this message
Sebastian Kalinowski (prmtl) wrote :

Please remember to add VERSION and diagnostic snapshot.

Roman Sokolkov (rsokolkov)
description: updated
Alexander Kislitsky (akislitsky)
Changed in fuel:
assignee: nobody → Fuel Library Team (fuel-library)
milestone: none → 6.0.2
OpenStack Infra (hudson-openstack)
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Dmitry Ilyin (idv1985)
status: Confirmed → In Progress
Vitaly Sedelnik (vsedelnik)
Changed in fuel:
status: In Progress → Won't Fix
Revision history for this message
Sergey Vasilenko (xenolog) wrote :

looks like after any add-remove node operation
setup /etc/hosts task should be executed on each node on ENV.

Question: What should be happen if some ENV nodes are down at this time?

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

Good point. This also applies to any of the generic questions like "What if node X is down then the node Y was removed and how to retry this update operation for the component Z?" where Z is actually everything: /etc/hosts, corosync cluster, CEPH cluster, galera, AMQP etc.

So. how should we retry life-cycle management tasks? This cannot be fixed as a bug, this requires a separate lify management blueprint. There are probably some component should exist which would track pending update actions and accomplish them of report failed, eventually.

Nastya Urlapova (aurlapova)
Changed in fuel:
importance: Low → Medium
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

This functionality would work automatically if this bug was fixed: https://bugs.launchpad.net/fuel/+bug/1485505
Marking as duplicate.

tags: added: feature
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on fuel-library (master)

Change abandoned by Dmitry Ilyin (<email address hidden>) on branch: master
Review: https://review.openstack.org/197963

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.