FUEL_ACCESS hash not updated in astute on fuelmaster after changing fuel admin password via Fuel WebUI
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
New
|
Undecided
|
Unassigned |
Bug Description
We have similar bug https:/
How to reproduce:
1) Deploy new fuel
2) By default you should be able to execute:
hash=$(grep -A2 FUEL_ACCESS /etc/fuel/
fuel_pass=$(echo "${hash}" | grep password | cut -d ':' -f2 | cut -d'"' -f2)
keystone --os-username admin --os-password "${fuel_pass}" --os-tenant-name admin --os-auth-url http://
3) goto Fuel WebUI
4) change fuel admin password
5) grep -A2 FUEL_ACCESS /etc/fuel/
You see old credentials
and execution of:
hash=$(grep -A2 FUEL_ACCESS /etc/fuel/
fuel_pass=$(echo "${hash}" | grep password | cut -d ':' -f2 | cut -d'"' -f2)
keystone --os-username admin --os-password "${fuel_pass}" --os-tenant-name admin --os-auth-url http://
won't work anymore as keystone database updated however /etc/fuel/
So if user changes password via WebUI, plugins will not be able to access fuel keystone anymore
Workaround over it - update /etc/fuel/
Expected:
/etc/fuel/
Affected/tested:
FUEL 9 (community)
description: | updated |
description: | updated |
I'm not sure that's exactly the expected behavior here. The file 'astute.yaml' serves as a source for deployment information only. It must not be used by any application (including plugin) as a source of actual auth information for the Nailgun API.
Actual auth credentials are intended to be kept in $HOME/. config/ fuel/fuel_ client. yaml file, or set as an env variable (KEYSTONE_PASS or OS_PASSWORD), orpassed via command line option every time. All applications that want to authenticate for the Nailgun API should rely on those 3 mechanisms.