Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle absent of lease SD when starting ha vm #660

Merged
merged 1 commit into from
Sep 21, 2022

Commits on Sep 21, 2022

  1. core: handle absent of lease SD when starting ha vm

    This patch looks like a hack but as we don't have enough time
    to do that more cleanly for 4.5.3, we go this way in order to
    address a significant issue with disaster recovery:
    When registering an highly avilable VM on the secondary site
    and trying to start it, the latter operation may fail due to
    filtering hosts that didn't report a proper state for the
    storage domain on which the VM lease was created.
    
    The proposed solution is to add the VM to HaAutoStartVmsRunner
    so we would keep trying to start it in that case. Specifically,
    when we fail to find a host due to the filterng that is done
    by VmLeasesReadyFilterPolicyUnit on an attempt to start the
    VM by a request we get from outside (i.e., not internal
    execution), we switch the VM to Down state with exit reason
    that reflects an Error and then add it to the aforementioned
    runner service.
    
    Bug-Url: https://bugzilla.redhat.com/1974535
    Signed-off-by: Arik Hadas <ahadas@redhat.com>
    ahadas committed Sep 21, 2022
    Configuration menu
    Copy the full SHA
    37bd968 View commit details
    Browse the repository at this point in the history