This time, we have the same problem when the undercloud is
containeirized.
This patch is actually setting parity with keystone config from
instack-undercloud, but also raising an actual issue that will be
addressed this cycle.
In the meantime, let's increase the token expiration so we can move
forward with testing the containerized undercloud.
Reviewed: https:/ /review. openstack. org/558922 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=02cacfd53a9 cf168d7e1967fae f3211333800eb6
Committed: https:/
Submitter: Zuul
Branch: master
commit 02cacfd53a9cf16 8d7e1967faef321 1333800eb6
Author: Emilien Macchi <email address hidden>
Date: Wed Apr 4 13:42:41 2018 -0700
undercloud: increase token expiration time
We did it in the past (3 years ago!) in instack-undercloud: /github. com/openstack/ instack- undercloud/ commit/ 43e792c6844d4a7 081b718d7f89b0c 40f5cfb708 /bugzilla. redhat. com/show_ bug.cgi? id=1235908
https:/
in the context of: https:/
This time, we have the same problem when the undercloud is undercloud, but also raising an actual issue that will be
containeirized.
This patch is actually setting parity with keystone config from
instack-
addressed this cycle.
In the meantime, let's increase the token expiration so we can move
forward with testing the containerized undercloud.
Change-Id: Iceaaf53fae44b5 bcda9f6517f1639 39ba6be3d49
Related-Bug: #1761050