[ https://ovirt-jira.atlassian.net/browse/OST-137?page=com.atlassian.jira.plug... ] Anton Marchukov reassigned OST-137: ----------------------------------- Assignee: Anton Marchukov (was: infra)

OST: test for host being in up state should have retries --------------------------------------------------------

Key: OST-137 URL: https://ovirt-jira.atlassian.net/browse/OST-137 Project: oVirt system tests Issue Type: Bug Reporter: Dusan Fodor Assignee: Anton Marchukov

When host goes up after installation, it first goes up, then it falls back into (iirc) unknown state, then it goes up for good. This confuses multiple tests that require host to be up (e.g. add storage domain), which wait for at least one host being up, and when they get past the condition, meanwhile host falls back to the unknown state, so following operation which requires host to be up fails. Then it tries fencing, but it cannot start fencing since there is no up host at the moment, which issues more errors... It's same pattern in all such failure, i will paste console output & link to job next time i'll see this. The resolution would be to wait if the host is REALLY up, so e.g. ask if it's up, wait a bit, ask again and if it's up both times, continue with operation.

-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)