cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-10157) Wrong notification while migration
Date Mon, 11 Dec 2017 16:21:01 GMT

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

ASF subversion and git services commented on CLOUDSTACK-10157:
--------------------------------------------------------------

Commit 8c6fb0e3120e80e0682b5666b13e70d640e58daf in cloudstack's branch refs/heads/master from
[~nitinkumar.maharana]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=8c6fb0e ]

CLOUDSTACK-10157: Wrong notification while migration (#2337)

Root Cause:
Earlier, it was failing with ArrayIndexOutOfBoundsException, when the list is empty and accessing
the first element.
The error was only observed in Log, but was not showing in UI as it was not throwing any exception.
Hence the API call was in turn successful.

Solution:
Added the empty check before sending device details.
Which says either the required GPU device is not available or out of capacity.

> Wrong notification while migration
> ----------------------------------
>
>                 Key: CLOUDSTACK-10157
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10157
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>    Affects Versions: 4.11.0.0
>            Reporter: Nitin Kumar Maharana
>              Labels: GPU
>             Fix For: 4.11.0.0
>
>
> RETRO STEPS:
> 1. Had three hosts in one cluster, two of them with GPU cards NVIDIA GRID K1 and K2 and
one normal host.
> 2. Deployed a VM with K2 vgpu.
> 3. Stopped the VM and tried starting it on a different host. (Expected it to fail as
there is only one host supporting that particular vgpu type)
> 4. The log showed it as failed operation, VM remained in the stopped state, yet the notification
showed "Start Instance" as successful and no error message was displayed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message