adietrich-ussignal opened a new issue, #9482:
URL: https://github.com/apache/cloudstack/issues/9482
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
UI, ISOs/Templates
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.19.0.2
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
N/A
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
N/A
##### SUMMARY
<!-- Explain the problem/feature briefly -->
When attempting to share access of an ISO or template to an account in a
sub-domain, an error is raised about "Unable to grant a launch permission to
account '<account name' in domain id=<domain id>, account not found."
This creates two problems:
1. There is no way to effectively share an ISO or template from a parent
domain to a sub-domain, which can lead to duplicate ISOs or templates required
for each sub-domain. Sharing the templates or ISOs publicly is not desired in a
multi-tenant cloud service provider environment.
2. Setting `share.public.templates.with.other.domains` to false permits a
parent domain to create a public template only visible to that domain. The
account in the parent domain can then assign an instance created with said
template or ISO to an account in a sub-domain. The issue is, the template or
ISO is not visible for provisioning new instances within the account of the
sub-domain.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
1. Have a domain with at least one sub-domain.
2. Have an account created in each of these domains.
3. Create a non-public ISO or template in the parent domain.
4. Select "Update Template Permissions" from the template window.
5. Select "Share With: Account".
6. Select the account in the sub-Domain.
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
The account in the sub-domain is able to access the ISO or template.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
Error below is recevied.
~~~
<img width="1098" alt="Screenshot 2024-08-02 at 12 41 31 PM"
src="https://github.com/user-attachments/assets/a8e29b50-08a8-4096-a379-050690f29468">
--
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]