Bug 1590828
| Summary: | Associate Floating Ip to instance should not show already assigned IP in the list | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Niladri Roy <niroy> | ||||||
| Component: | Providers | Assignee: | Gilles Dubreuil <gdubreui> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Dave Johnson <dajohnso> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 5.9.0 | CC: | asad.rao, cpelland, gblomqui, gdubreui, jfrey, jhardy, jocarter, jprause, lavenel, maufart, niroy, obarenbo, pmukhedk, simaishi | ||||||
| Target Milestone: | GA | ||||||||
| Target Release: | 5.9.4 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-06-27 23:27:49 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | Openstack | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1595269 | ||||||||
| Attachments: |
|
||||||||
|
Description
Niladri Roy
2018-06-13 12:46:19 UTC
I'm taking over this one and will provide an update ASAP. I confirm the issue, working on a patch. Created attachment 1454904 [details]
Floating IP Reallocation
Let's take a step back. This is actually normal behaviour. On OpenStack, being able to reallocate an already attached floating IP is default behaviour. A project owner of instances can therefore directly move a floating IP without having to de-allocate the IP before allocating it to another instance (see attachment https://bugzilla.redhat.com/attachment.cgi?id=1454904). There is nothing wrong from the latter and that doesn't break anything inside OpenStack. When allocating a floating IP, if the allocated IPs have disappeared from the list of available addresses then we're going to break the default feature. And therefore I wouldn't recommend it. Alternatively, we could request a confirmation windows when the floating IP is already assigned. This could be submitted as an RFE. Giles, Thanks for looking into this. I would disagree if it's a default behaviour because what you have shown is achievable from the OSP CLI only. From horizon dashboard the dropdown only lists the available (unassigned floating IPs) Please see attachment which shows the behaviour - I had two floating IPs 10.x.x.48 and 10.x.x.49 - I assigned 10.x.x.48 to niroy-1 instance - while assigning floating IP to niroy-2 instance only 10.x.x.49 is shown in the dropdown Apart from this I see other issues with the network manager when we assign floating IP via CloudForms. It would be best if we can have a BJ session so that I show you the issue Created attachment 1454970 [details]
Floating IP assignment via horizon dashboard
Niladri, Thank you for your prompt feedback. Whether a floating IP can be reallocated directly or not is a feature choice. The fact that currently a Floating IP can be re-allocated directly is not a bug. I understand Horizon has made a different choice. If we want to change the current behaviour then that would have to go as an Request For Enhancement (RFE). Let's keep one specific issue per BZ. If you're facing any other new issue please create a BZ accordingly. Thanks Hello, I have raised RFE 1595767 as per your suggestion. Clearing needinfo Thanks for creating and following up upon BZ#1595767. |