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

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

Github user DaanHoogland commented on a diff in the pull request:

    https://github.com/apache/cloudstack/pull/666#discussion_r36576679
  
    --- Diff: 
server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java ---
    @@ -2627,7 +2627,7 @@ public boolean postStateTransitionEvent(final 
StateMachine2.Transition<State, Vi
                     s_logger.info("Schedule a router reboot task as router " + 
vo.getId() + " is powered-on out-of-band. we need to reboot to refresh network 
rules");
    --- End diff --
    
    @koushik-das The problem is probably not solved in the most elegant way. 
The bit (vo.getType() == VirtualMachine.Type.DomainRouter) could have been 
pulled up in an extra containing if block.
    In the end the only the reprovision_out_of_band is making the final choice 
between alerting and rebooting


> 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
>            Assignee: 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