[
https://ovirt-jira.atlassian.net/browse/OVIRT-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dusan Fodor updated OVIRT-2821:
-------------------------------
Summary: OST: test for host being in up state should have retries (was:
OST: test for host being in up state should have a retry)
> OST: test for host being in up state should have retries
> --------------------------------------------------------
>
> Key: OVIRT-2821
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2821
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: OST
> Reporter: Dusan Fodor
> Assignee: infra
>
> 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)
_______________________________________________
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/PS7JUS7SFGQX32NIIAQ62FIOSYW25OF6/
