aeb2c1f20a
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 <alex.kozyrev@windriver.com> |
||
---|---|---|
api-ref/source | ||
bsp-files | ||
devstack | ||
doc | ||
installer | ||
inventory | ||
kickstart | ||
mtce | ||
mtce-common | ||
mtce-compute | ||
mtce-control | ||
mtce-storage | ||
python-inventoryclient | ||
releasenotes | ||
.gitignore | ||
.gitreview | ||
.zuul.yaml | ||
CONTRIBUTORS.wrs | ||
LICENSE | ||
README.rst | ||
centos_iso_image.inc | ||
centos_pkg_dirs | ||
test-requirements.txt | ||
tox.ini |
README.rst
stx-metal
StarlingX Bare Metal Management