Description of problem: Router creation template should contain the sentence based on the actual use-case. Version-Release number of selected component (if applicable): Current How reproducible: Every time. Actual results: Currently, the template contains following sentence. openstack_dashboard/dashboards/project/routers/templates/routers/ports/_create.html ~~~ 22 {% trans "The default IP address of the interface created is a gateway of the selected subnet. You can specify another IP address of the interface here. You must select a subnet t 22 o which the specified IP address belongs to from the above list." %} ~~~ This sentence should be improved with actual use-case. For example, if the router connected to the private network which has router already, the ip address has to be specified for the new router. Expected results: We think following sentence will reduce the confusion in user side. ~~~ If you don't specify the IP address, the IP address of the newly created interface for the router will be the IP address which is defined as the gateway for the selected subnet. If you need to use another IP address, for example the IP address has already been in use, please specify another IP address here. You must specify an IP address which belogs to the selected subnet. ~~~ Additional info:
The more sophisticated explanation might be below. ~~~ If you don't specify an IP address here, the gateway's IP address of the subnet will be assigned to the newly created interface of the router. If you need to use another IP address or the gateway's IP address has already been in use, please specify another IP address here. You must specify an IP address which belogs to the selected subnet. ~~~
The sentence has been discussed in an upstream patch and ended up as the following to reduce confusion for users: "If you don't specify an IP address here, the gateway's IP address of the selected subnet will be used as the IP address of the newly created interface of the router. If the gateway's IP address is in use, you must use a different address which belongs to the selected subnet." This has now merged into the upstream codebase.
The template contains the requested information, as per comment #7.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462