Under some circumstances the keystone verify process might fail
but we are able to proceed because it's client setting error,
so we don't need to report an exception log in the log file to
confuse admin, instead, use an info log.
In the reported bug, the issue is that nova is configured for
the 'internal' identity endpoint but the nova code does not
pass an interface, so KSA defaults to 'public' which fails.
This is fixed with I2204c8bed8936d5bed0f410284d2a563f84e7100
but not something we can backport, so this is a simple change
to make the logging less annoying.
Reviewed: https:/ /review. openstack. org/513243 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=1606467b299 69eb45efbb56c1b 148a4a6f53c5cf
Committed: https:/
Submitter: Zuul
Branch: master
commit 1606467b29969eb 45efbb56c1b148a 4a6f53c5cf
Author: jichenjc <email address hidden>
Date: Wed Oct 18 11:20:51 2017 +0800
Downgrade log for keystone verify client fail
Under some circumstances the keystone verify process might fail
but we are able to proceed because it's client setting error,
so we don't need to report an exception log in the log file to
confuse admin, instead, use an info log.
In the reported bug, the issue is that nova is configured for 5bed0f410284d2a 563f84e7100
the 'internal' identity endpoint but the nova code does not
pass an interface, so KSA defaults to 'public' which fails.
This is fixed with I2204c8bed8936d
but not something we can backport, so this is a simple change
to make the logging less annoying.
Closes-Bug: 1716344
Change-Id: I67c9f648f85de3 64de443e2a0535d dd361c14661