Code Review / apex.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: d75cbb7) | patch
Fixes ensuring VBMCs are actually running 57/52257/2
authorTim Rozet <trozet@redhat.com>
Fri, 16 Feb 2018 19:16:59 +0000 (14:16 -0500)
committerTim Rozet <trozet@redhat.com>
Fri, 16 Feb 2018 19:22:46 +0000 (14:22 -0500)
commit0e2c8a5a3dc5919df7d906be951331372775eeff
treeb137935b91975d336e2d5fdabb7c2c973a6d4417tree | snapshot
parentd75cbb74191e32e3ff996604e30a2954d889687bcommit | diff
Fixes ensuring VBMCs are actually running

We currently start VBMCs using CLI due to issues with the VBMC python
lib.  However when we start them, there is no check to make sure they
are actually changed to 'running' status.  This patch adds logic to
check (up to 5 times) to ensure each VBMC is running or raises an error.
Note this is for virtual deployments only.

JIRA: APEX-527

Change-Id: Iab7ee3b76292d6fc547f18c83f23c04205e9bb2e
Signed-off-by: Tim Rozet <trozet@redhat.com>
apex/tests/test_apex_virtual_utils.py diff | blob | history
apex/virtual/exceptions.py [new file with mode: 0644] blob
apex/virtual/utils.py diff | blob | history