cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-10246) VM HA issues
Date Wed, 14 Mar 2018 18:27:00 GMT


ASF GitHub Bot commented on CLOUDSTACK-10246:

DaanHoogland commented on issue #2474: CLOUDSTACK-10246 Fix Host HA and VM HA issues
   @Slair1 I have no easy way to put this. You have four (4) PRs out and all fail all travis
runs. It must be that travis doesn't like your github handle, or so. Can you think of something
you have/do that might cause this. In the same period other PRs have passed travis runs...?

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> VM HA issues
> ------------
>                 Key: CLOUDSTACK-10246
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions:
>         Environment: My setup is CentOS 7 Management server with 3 CentOS 7 KVM HVs,
NFS as primary and secondary storages.
>            Reporter: Nux
>            Priority: Major
> VM HA fails to kick in when one of the hypervisors goes down.
> It even fails to restart the system VMs which remain down along with the instances until
the affected HV comes back online.
> When I crash or power off the HV the system marks it in the hosts list as "Alert" or
"Disconnected" respectively. It should get changed to "Down" after that, but this never happens.
> I have tried various combinations of setups (Adv, Basic), none succeeded.
> My instances use HA enabled offerings.
> Management server DEBUG logs here:
> []

This message was sent by Atlassian JIRA

View raw message