[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661731#comment-14661731
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8709:
--------------------------------------------

GitHub user remibergsma opened a pull request:

    https://github.com/apache/cloudstack/pull/666

    CLOUDSTACK-8709 No out of band migrate alert for non-routers

    This prevents the out-of-band migrate alerts being generated for 
non-routers.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/remibergsma/cloudstack fix-CLOUDSTACK-8709

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/666.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #666
    
----
commit 836fe6a0f55c0e52cb6c972f2c437800cd150d24
Author: Remi Bergsma <[email protected]>
Date:   2015-08-07T11:55:36Z

    CLOUDSTACK-8709 No out of band migrate alert for non-routers

----


> Received out-of-band alert from migrating user instance
> -------------------------------------------------------
>
>                 Key: CLOUDSTACK-8709
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8709
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.4.4
>         Environment: Seen on KVM and ACS 4.4.4
>            Reporter: Remi Bergsma
>             Fix For: 4.6.0
>
>
> When migrating an instance using migrateVirtualMachine API call, this alert 
> is generated:
> 2015-08-05 14:53:03,057 WARN  [apache.cloudstack.alerts] 
> (Work-Job-Executor-2:ctx-58ebe691 job-803495/job-803497 ctx-7eb41cc0)  
> alertType:: 9 // dataCenterId:: 2 // podId:: 4 // clusterId:: null // 
> message:: Router has been migrated out of band: i-625-20061-VM
> Problem:
> - this is not a router
> - there is a migrate in progress, that leads to a VM that is running on 
> multiple hypervisors for a short while.
> - this could also happen when one migrates a router to another hypervisor
> Not verified on master yet.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to