Comment 0 for bug 1557562

Revision history for this message
Dmitriy Stremkovskiy (dstremkouski) wrote :

How to reproduce:
1) Create fuel plugin
2) environment_config.yaml should contain:
attributes:
  metadata:
    pregenerated_password:
      generator: "password"
Plugin should create new role.
3) build plugin and install it on the fuel master
4) create environment
5) assign 2+ nodes to new role
6) do not assign openstack controller roles to any node.
Your deploy could not be run from WebUI, however it could be started from CLI

Now you have new envirnoment with 2+ nodes with plugin role.

If you run:
fuel deploy-changes --env N
you will be able to get equal astute.yaml files with the same pregenerated_password
If you reset environment and call tasks manualy, like:
fuel node --node-id A --provision
fuel node --node-id B --provision
fuel node --node-id C --provision
fuel node --node-id A --deploy
fuel node --node-id B --deploy
fuel node --node-id C --deploy
you will get different astute.yaml files
In that case pregenerated_password variable will contain different values and dependent services will fail to synchronise.

Affected/tested fuel versions: fuel 9