SUMMARY
Pf9-express failed to deploy a new host with the pf9-cindervolume-base role as it referenced a Keystone token in /tmp/keystone-token.txt that contained an expired token.
ISSUE TYPE
Bug Report
OS / ENVIRONMENT
- Platform9 v5.6
- Ubuntu 20.04
STEPS TO REPRODUCE
These are the steps that took place (I haven't attempted to reproduce yet):
- 8/15/23: Deployed new hosts pf9-express (compute & image library roles only)
- 8/21/23: (almost a week later) Add a single entry to [cinder] in the inventory file with a host that was previously deployed a week prior with the compute/glance role.
- Playbook failed to execute with HTTP 401 Unauthorized error
EXPECTED RESULTS
The playbook to successfully complete by using a token that is valid or one that has been refreshed upon expiration or execution of the playbook.
ACTUAL RESULTS
It was observed that express is referencing a file /tmp/keystone-token.txt that should contain a valid token but is expired. We were able to work around this by updating the /tmp/keystone-token.txt file with a valid token. We had also attempted to delete the file and see if pf9-express would recreate it with a valid token but that didn't work.
SUMMARY
Pf9-express failed to deploy a new host with the pf9-cindervolume-base role as it referenced a Keystone token in
/tmp/keystone-token.txtthat contained an expired token.ISSUE TYPE
Bug Report
OS / ENVIRONMENT
STEPS TO REPRODUCE
These are the steps that took place (I haven't attempted to reproduce yet):
EXPECTED RESULTS
The playbook to successfully complete by using a token that is valid or one that has been refreshed upon expiration or execution of the playbook.
ACTUAL RESULTS
It was observed that express is referencing a file
/tmp/keystone-token.txtthat should contain a valid token but is expired. We were able to work around this by updating the/tmp/keystone-token.txtfile with a valid token. We had also attempted to delete the file and see if pf9-express would recreate it with a valid token but that didn't work.