Comment 2 for bug 1631976

Revision history for this message
Ryan Hallisey (rthall14) wrote :

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.