After changing nailgun password astute.yaml wasn't updated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Julia Aranovich | ||
7.0.x |
Won't Fix
|
High
|
MOS Maintenance | ||
8.0.x |
Won't Fix
|
High
|
MOS Maintenance | ||
Mitaka |
Fix Released
|
High
|
Vitaly Kramskikh |
Bug Description
Detailed bug description:
Changing fuel user's password does not updates astute.
Steps to reproduce:
1 Deploy 7.0 Fuel
2 Change password for "admin" user using "fuel user change-password" command
3 Apply host-only manifest
OR
3 Apply maintenance update old way (using bootstrap_
Expected results:
No errors, fuel is operable
Actual result:
Manifest set up wrong password into environment variable which leads to "Unauthorized" error at "fuel rel --sync-
http://
(trace http://
Reproducibility:
Any run
Workaround:
Fix astute.yaml manually then apply a manifest/MU
Impact:
Real-world maintenance update.
Description of the environment:
Versions of components: Fuel 7.0 Release ISO (#301), Fuel 8.0 Release ISO (#570)
summary: |
- After cnahging nailgun password astute.yaml wasn't updated + After changing nailgun password astute.yaml wasn't updated |
tags: | added: area-python |
Changed in fuel: | |
status: | Confirmed → In Progress |
Changed in fuel: | |
milestone: | 9.0 → 10.0 |
tags: | added: on-verification |
This can be solved by one of two ways: deployment- tasks --dir /etc/puppet/" command to use the admin token which isn't changed. fuel/fuel_ client. yaml
1 - We can change the "fuel rel --sync-
2 - Make a documentation update and inform the user that he or she should update ~/.config/
As a follow up, the error message to update /etc/fuel/ client/ config. yaml is not very helpful since we don't write to that file any more.