cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gaurav Aradhye (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-7516) test_snapshots.py - VM Deploy failed because the account was using template belonging to different account to deploy the instance
Date Wed, 10 Sep 2014 09:46:29 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-7516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gaurav Aradhye updated CLOUDSTACK-7516:
---------------------------------------
    Status: Reviewable  (was: In Progress)

> test_snapshots.py - VM Deploy failed because the account was using template belonging
to different account to deploy the instance
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7516
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7516
>             Project: CloudStack
>          Issue Type: Test
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation
>    Affects Versions: 4.5.0
>            Reporter: Gaurav Aradhye
>            Assignee: Gaurav Aradhye
>              Labels: automation
>             Fix For: 4.5.0
>
>
> Following test case failed:
> integration.component.test_snapshots.TestCreateVMSnapshotTemplate.test_01_createVM_snapshotTemplate
> Reason:
> Execute cmd: deployvirtualmachine failed, due to: errorCode: 531, errorText:Acct[51d00171-895e-4893-90c8-6630b98f852a-test-TestCreateVMSnapshotTemplate-BJ9XFN]
does not have permission to operate with resource Acct[e7b7973c-3512-11e4-9ac6-1a6f7bb0d0a8-admin]
> Solution:
> Create the template with the api client of the account itself, and not the api client
of root domain account. So that account will have permission to use the resources (template)



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

Mime
View raw message