fuel-dev team mailing list archive

[Mike Scherbakov <1281555@xxxxxxxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 1277081 ***
    https://bugs.launchpad.net/bugs/1277081

** Changed in: fuel
     Assignee: Fuel Dev (fuel-dev) => Fuel Python Team (fuel-python)

** This bug has been marked a duplicate of bug 1277081
   Role and Name of the node is not discarded after deleting environment if node was in discarded state

-- 
You received this bug notification because you are a member of Fuel Dev,
which is a bug assignee.
https://bugs.launchpad.net/bugs/1281555

Title:
  Nodes don`t dump their names after reset

Status in Fuel: OpenStack installer that works:
  New

Bug description:
  Nodes bootstrap after cluster reset, but their names remain the same.
  If this node is deleted from current (resetted) cluster and is added
  to new cluster, it`s name still remains the same.

  {"ostf_sha": "f86abe5544b5ffcf621e0c450bca15737c92361f",
  "fuelmain_sha": "439577ed2795d86d57351d6e7cec6ed0049101c9",
  "astute_sha": "d6e92bcf35fbc74cc0fff5459f51e7b83cf6f481", "release":
  "4.1", "nailgun_sha": "d0b50679c3444be78ac44848f79eb5fdd5b59013",
  "fuellib_sha": "8e0b1ae5b1c4c137c1dd2a0be06d0d68e99d75bf", "mirantis":
  "no"}

  Steps to reproduce: 
  1. Install iso fuel-stop_reset_ui-17_fix_tab.iso on kvm.
  2. Add 3 slaves. 
  3. Create new cluster with the follwoing configuration: 
  - CentOS simple;
  - nova-network flat dhcp;
  - cinder lvm;
  4. Add the following nodes: 
  - 1 controller
  - 2 computes
  5. Deploy cluster, wait for successful cluster deployment.
  6. Reset cluster after deployment.
  7. If nodes don`t bootstrap, hard-reset them (because of the known libvirt issue).
  8. Go to UI and check the nodes names.
  9. Remove one of the compute nodes.
  10. Create new cluster with any configuration and go to the  "Assign Roles" tab.
  11. Assign node and deploy cluster.

  Expected result:
  Node names are Untitled. When adding node to new cluster its name is Untitled.

  Actual result:
  Node name remains the same as in the deployed cluster (in my case it was: slave-03_compute) and so it remains if we add it to new cluster and deploy it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fuel/+bug/1281555/+subscriptions