Fix for MTCE race condition in BMC secret handling
There is intermittent issue in getting BMC password in MTCE.
The process of obtaining a secret from Barbican stops after
a secret reference is received. No attempts to retrieve the
actual payload is atempted. This happens when the secret
reference reply is received right after BMC queries are
initiated. It was fine before when we had an one-stage
process of getting a password from keyring. We cannot
allow it now because of a two-stage Barbican process.
Change-Id: I381f69ab6a1a54118b22dd31feefcd93698120ad
Closes-bug: 1818284
Signed-off-by: Alex Kozyrev <email address hidden>
Reviewed: https:/ /review. openstack. org/649988 /git.openstack. org/cgit/ openstack/ stx-metal/ commit/ ?id=aeb2c1f20af 84047803533de18 73d8887722501b
Committed: https:/
Submitter: Zuul
Branch: master
commit aeb2c1f20af8404 7803533de1873d8 887722501b
Author: Alex Kozyrev <email address hidden>
Date: Thu Apr 4 09:14:27 2019 -0400
Fix for MTCE race condition in BMC secret handling
There is intermittent issue in getting BMC password in MTCE.
The process of obtaining a secret from Barbican stops after
a secret reference is received. No attempts to retrieve the
actual payload is atempted. This happens when the secret
reference reply is received right after BMC queries are
initiated. It was fine before when we had an one-stage
process of getting a password from keyring. We cannot
allow it now because of a two-stage Barbican process.
Change-Id: I381f69ab6a1a54 118b22dd31feefc d93698120ad
Closes-bug: 1818284
Signed-off-by: Alex Kozyrev <email address hidden>