The capabilities filter gets incorrectly blamed for a lot of
deployment failures because on a retry of a node deployment the
filter has to fail because there is only one node that can match
when using predictable placement. However, we don't have any
logging to help determine why the filter fails. This adds logging
to explain why nodes fell through, which will hopefully help with
debugging these problems.
Change-Id: I702209e9b5a1e546bf8cb784eec8bdc3c97c63eb
Closes-Bug: 1718502
(cherry picked from commit e5d16155364c1dae2db238506f236194e2dfb1dc)
Reviewed: https:/ /review. openstack. org/566296 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=9a29b4d052e f487b057a3c8ffe ea0bb5d7faf229
Committed: https:/
Submitter: Zuul
Branch: stable/ocata
commit 9a29b4d052ef487 b057a3c8ffeea0b b5d7faf229
Author: Ben Nemec <email address hidden>
Date: Wed Sep 13 16:40:41 2017 +0000
Add logging to capabilities filter
The capabilities filter gets incorrectly blamed for a lot of
deployment failures because on a retry of a node deployment the
filter has to fail because there is only one node that can match
when using predictable placement. However, we don't have any
logging to help determine why the filter fails. This adds logging
to explain why nodes fell through, which will hopefully help with
debugging these problems.
Change-Id: I702209e9b5a1e5 46bf8cb784eec8b dc3c97c63eb e2db238506f2361 94e2dfb1dc)
Closes-Bug: 1718502
(cherry picked from commit e5d16155364c1da