cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rafael WeingÀrtner <rafaelweingart...@gmail.com>
Subject Re: problem assigning an instance to a different account in a different domain
Date Mon, 09 Nov 2015 22:05:21 GMT
I think that method does not work if the VM is assigned to a Project. I
remember that I tried to use that method once, but that did not work and I
had to do the change manually.

On Mon, Nov 9, 2015 at 7:37 PM, Yiping Zhang <yzhang@marketo.com> wrote:

> The api assignVirtualMachine is for this exact purpose. It seems even to
> be able to move virtual machines into different zones (I never tried this,
> since I have only one zone)
>
> However, there are some limitations:  it does not support advanced
> networking with SecurityGroup enabled.  Since I did not have to move
> instances to different networks,  I just ignored the error. The domain and
> account are assigned properly.
>
> Yiping
>
>
>
>
> On 11/9/15, 12:49 PM, "Stephan Seitz" <s.seitz@secretresearchfacility.com>
> wrote:
>
> >Hi there!
> >
> >If anyone knows, how to get an instance assigned to a different account
> >in a different domain, I'ld be very happy :) Even if it has to be done
> >via DB manipulation...
> >
> >Just if... :)
> >
> >Stephan
> >
> >
> >Am Mittwoch, den 04.11.2015, 15:59 +0100 schrieb Stephan Seitz:
> >> Hi!
> >>
> >> I'm trying to assign instances to a different account in a different
> >> domain. Currently with no success.
> >>
> >> The particular instances have been deployed by the initial "admin"
> >> account in the ROOT domain, and should be assigned to a domain-admin
> >> account.
> >>
> >> id = 0d7a4ee7-5c6f-11e5-a590-3400a30d0aba <--- current domain
> >> path = ROOT
> >> =====================================================================
> >> ===========
> >> id = 4298cfba-aa4d-4baa-8b0e-53e70d0ebbe5 <--- destination domain
> >> path = ROOT/xxxx/yyyyyyyyyyy
> >>
> >>
> >> id = 4b143f31-5c6f-11e5-a590-3400a30d0aba <-- current user in ROOT
> >> account = admin
> >> accountid = 4b14365a-5c6f-11e5-a590-3400a30d0aba
> >> =====================================================================
> >> ===========
> >> id = 54e79c7a-f3de-4b76-8c99-ffc18c555f5d <-- dest. user in dest.
> >> domain
> >> account = zzz@yyyyyyyyyyyyyy
> >> accountid = 76ec77a0-e0ca-459e-b211-eeacce52055c
> >>
> >>
> >> With cloudmonkey (logged in as the admin in ROOT), I got following
> >> result:
> >>
> >> (local) đŸ” > assign virtualmachine
> >> virtualmachineid=9b76aa5a-f97f-4bd0-8e9d-350816e42515
> >> domainid=4298cfba-aa4d-4baa-8b0e-53e70d0ebbe5
> >> account=zzz@yyyyyyyyyyyyyy
> >> Error 530: Failed to move vm
> >> Acct[76ec77a0-e0ca-459e-b211-eeacce52055c-zzz@yyyyyyyyyyyyyy] does
> >> not
> >> have permission to operate within domain
> >> id=0d7a4ee7-5c6f-11e5-a590-3400a30d0aba
> >> cserrorcode = 9999
> >> errorcode = 530
> >> errortext = Failed to move vm
> >> Acct[76ec77a0-e0ca-459e-b211-eeacce52055c-zzz@yyyyyyyyyyyyyy] does
> >> not
> >> have permission to operate within domain
> >> id=0d7a4ee7-5c6f-11e5-a590-3400a30d0aba
> >>
> >>
> >> This looks like, the destination user, who is domain-admin of it's
> >> domain needs to have access to the ROOT domain. I think this makes no
> >> sense, since I wan't to assign the instance TO it.
> >>
> >> Could someone please shed some light how to assign an instance to
> >> another user in another domain?
> >>
> >> Thanks in advance!
> >>
> >> Stephan
> >>
> >>
>



-- 
Rafael WeingÀrtner

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message