harikrishna-patnala commented on issue #7391:
URL: https://github.com/apache/cloudstack/issues/7391#issuecomment-2162164984
> > @rajujith can you please mention your reproduction steps in detail
(step-by-step)? In my testing I found the following scenarios (in a main branch
env):
> >
> > * Both ROOT admin and domain admin can deploy a VM in a network owned by
a user in a subdomain when `user` and `domainid` params are passed for that user
> > * Both ROOT admin and domain admin can **not** deploy a VM in a network
owned by a user in a subdomain when `user` and `domainid` params are not passed
> >
> > My steps:
> >
> > * Create domain `d1` and create a domain-admin account `dadmin` in this
domain
> > * Create subdomain `d11` in domain `d1` and create a normal user account
`user1` in it
> > * Using `user1` deploy an isolated network `n2`
> > * Using ROOT admin `admin` and domain-admin `dadmin` try deploying VMs
in network `n2`
> >
> > cc @andrijapanicsb @weizhouapache
>
> thanks @shwstppr the testing results are expected I think.
I could verify the same scenario and it is working fine. Following are the
cases that I've tested
1. Domain admin can create a VM for a user in a subdomain of it (using
the network created by the user) by passing "account" and "domainid"
parameters. This VM will be owned by that user in that subdomain
2. Domain admin can create a VM in the network created by the user after
setting the corresponding network permission to that domain admin. This VM will
be owned by the domain admin.
@rajujith if you agree for this we can close this issue.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
