cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajesh Battala (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-5586) [Hyper-v] Failed to deploy vm with user account
Date Sun, 22 Dec 2013 17:10:51 GMT


Rajesh Battala commented on CLOUDSTACK-5586:

This commit and newly generate systemvm template should resolve this problem
Commit 58aaf6780601117367bdb8d8b7ffec57776c398f in branch refs/heads/4.3 from Rajesh Battala
[;h=58aaf67 ]
CLOUDSTACK-5584 fix the issue to configure the systemvm's in hyperv consistently 

> [Hyper-v] Failed to deploy vm with user account
> -----------------------------------------------
>                 Key: CLOUDSTACK-5586
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Hypervisor Controller, Management Server
>    Affects Versions: 4.3.0
>         Environment: Latest build from 4.3 with commit :
> 197ef921f7b3c80998359f376fe045b13558633c
> Storage: CIFS for both primary and secondary storage
> Hypervisor= Hyper-v
>            Reporter: Sanjeev N
>            Assignee: Rajesh Battala
>            Priority: Critical
>              Labels: hyper-V,
>             Fix For: 4.3.0
>         Attachments: management-server.rar
> [Hyper-v] Failed to deploy vm with user account
> Failed to bring up VR hence failure in vm deployment
> Steps to Reproduce:
> =================
> 1.Bring up CS in advanced zone with hyper-v using cifs for both primary and secondary
> 2.Create an account with role user under Root domain.
> 3.Login with the user account.
> 4.Try to deploy a vm with the user account.
> Actual Result:
> ===========
> VR failed to come up hence vm deployment failed.
> Observations:
> ===========
> During VR boot up observed that boot parameters were not configured on the VR. Hence
management server was not able to reach the VR and stopped it.
> But with the default admin account started the VR(it was in stopped state due to above
failure) from CS UI and it came up without any issues and all the boot parameters were configured

This message was sent by Atlassian JIRA

View raw message