Handle failed VIM API responses in sysinv conductor k8s check
If the VIM is not running or is slower than 5 seconds to respond
to a sw-update query, the sysinv conductor logs get many
stacktraces logged as the periodic task that checks this
fails over and over.
Reviewed: https:/ /review. opendev. org/749506 /git.openstack. org/cgit/ starlingx/ config/ commit/ ?id=1e773021753 605fcafaec404a6 b8215a6dd24e55
Committed: https:/
Submitter: Zuul
Branch: master
commit 1e773021753605f cafaec404a6b821 5a6dd24e55
Author: albailey <email address hidden>
Date: Wed Sep 2 09:03:38 2020 -0500
Handle failed VIM API responses in sysinv conductor k8s check
If the VIM is not running or is slower than 5 seconds to respond
to a sw-update query, the sysinv conductor logs get many
stacktraces logged as the periodic task that checks this
fails over and over.
Now the check is more robust.
Change-Id: I5a9b06d5852dc3 00cc43501cfa46b b1393701d99
Closes-Bug: 1893948
Signed-off-by: albailey <email address hidden>