Something is happening during the update in the tripleoclient that is causing the token to be 'x'. The deployment works fine where the token exists, but after running `openstack undercloud update` the issue occurs.
Something is happening during the update in the tripleoclient that is causing the token to be 'x'. The deployment works fine where the token exists, but after running `openstack undercloud update` the issue occurs.