[doc] File /etc/astute.yaml was not updated after adding new node in the cluster

Bug #1439781 reported by Egor Kotko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Triaged
Medium
Fuel Documentation Team

Bug Description

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "6.1"
  api: "1.0"
  build_number: "261"
  build_id: "2015-04-01_09-01-08"
  nailgun_sha: "51ddbe0a2e379e82af531b1c6d45fd386d2f894e"
  python-fuelclient_sha: "9b0b6ab2f09ff75445550b7210104e21df5d8cd6"
  astute_sha: "7292fc2a673cb1c32a688a46fd4836ca0500a957"
  fuellib_sha: "b9cc8e14e9aadd20c31d31d48287ea46560cd9ce"
  ostf_sha: "1c7f799cb0e159737d1f910b13e4073b16d1eb8c"
  fuelmain_sha: "178812b1971a900c49a8afc1688afd7475a6ffbb"

Steps to reproduce:
1) Deploy cluster Cetos, HA, nova, 1 Controller 1 Compute
2) Add and node with role base OS, deploy cluster

Expected result
atute.yaml on each node will contain entry about aded baseOS node

Actual result:
atute.yaml - on controller and compute does not contain any data dout aded machine

http://paste.openstack.org/show/197951/
http://paste.openstack.org/show/197954/

Revision history for this message
Egor Kotko (ykotko) wrote :
description: updated
Revision history for this message
Sebastian Kalinowski (prmtl) wrote :

Information about nodes is taken from hiera (you can check it using 'hiera nodes'), and all nodes are stored in /etc/hiera/nodes.yaml that is always updated after adding new nodes.

I can see that they are correctly present in your snapshot:
http://paste.openstack.org/show/197959/

Changed in fuel:
status: New → Invalid
Changed in fuel:
status: Invalid → Confirmed
Revision history for this message
Aleksandr Didenko (adidenko) wrote :

When we add new node that does not require deployment on existing nodes (for example new compute node), then /etc/hosts are updated with hosts.pp post-deployment task which pulls new list of nodes via hiera from /etc/hiera/nodes.yaml, just like Sebastian said.
If you add new controller nodes, this will trigger deployment on existing controllers and they will get new astute.yaml with the list of all nodes, so deployment will go just fine. After that, hosts will be updated again via post-deployment tast hosts.pp and /etc/hiera/nodes.yaml.
Marking this bug as invalid.

Revision history for this message
Aleksandr Didenko (adidenko) wrote :

OK, we decided to document this behavior. So I'm forwarding this bug to docs team.

Changed in fuel:
assignee: nobody → Fuel Documentation Team (fuel-docs)
Revision history for this message
Irina Povolotskaya (ipovolotskaya) wrote :

I believe, this belongs to Release Notes.

Changed in fuel:
status: Confirmed → Triaged
summary: - File /etc/astute.yaml was not updated after adding new node in the
+ [doc] File /etc/astute.yaml was not updated after adding new node in the
cluster
tags: added: docs release-notes
removed: nova
Revision history for this message
Sheena Conant (sheena-conant) wrote :

Does this need to be added as a known issue, or is there a workaround?

Changed in fuel:
importance: High → Medium
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.