cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (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=16286123#comment-16286123
] 

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

rhtyd commented on issue #2337: CLOUDSTACK-10157: Wrong notification while migration.
URL: https://github.com/apache/cloudstack/pull/2337#issuecomment-350774432
 
 
   Given our current regression testing system does not have GPU capabilties, I'll use travis
test results as verification of the build/code, two reviews/lgtms and merge this PR.

----------------------------------------------------------------
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:
users@infra.apache.org


> 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