apache / apache/cloudstack

use.system.public.ips does nothing when domain doesn't have a range

Open
#7,608 9 comments 0 reactions 1 assignee Claimed by @soreana View on GitHub
component:networking no-issue-activity status:not-a-bug type:improvement
Dominant language
Java
Stars
3.1k
Forks
1.4k
Avg merge
6d 19h
Merged PRs (30d)
32

Description

##### ISSUE TYPE

* Bug Report

##### COMPONENT NAME

~~~
IP assignment
~~~

##### CLOUDSTACK VERSION

~~~
4.17,
4.18,
main (*)
~~~
(*): Although I didn't test that on main branch, the code pard didn't change so it should be there as well.

##### SUMMARY

By default when user use all of their assigned public IPs, they can use system public IPs. Although by using the `use.system.public.ips` setting admins can prevent that action, the setting doesn't have any affect when user doesn't have any reserved range.

##### STEPS TO REPRODUCE

1. Login as a `root admin`
2. Create a domain and a domain admin account for the domain.
3. Set `use.system.public.ips` to `false` in the account, the domain or globally.
4. Assign an IP range to the domain or the account. `[Range 1]`
5. Login as a `domain admin` and create an isolated network in domain.
6. Go to the isolated network page and click on the `Public IP addresses` then click on `Acquire new IP`.
7. The list shows only the IPs in the assinged IP range `[Range 1]`
8. Logout and login as a `root admin` again
9. Remove the `[Range1]` IP range assignment.
10. Repeat step `5`, `6`, and `7`. The output list now includes the system IPs.

##### EXPECTED RESULTS

~~~
User can NOT see the system's public IP addresses.
~~~

##### ACTUAL RESULTS

~~~
User can see the system's public IP addresses.
~~~

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.