| Summary: | Floating IP Associate / Dis-asociate doesn't work with an OpenStack Instance | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Sreejith Anujan <sanujan> | ||||
| Component: | UI - OPS | Assignee: | Tzu-Mainn Chen <tzumainn> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Ola Pavlenko <opavlenk> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 5.7.0 | CC: | cpelland, dajohnso, hkataria, jhardy, mpovolny, obarenbo, sanujan | ||||
| Target Milestone: | GA | Flags: | tzumainn:
needinfo?
(sanujan) |
||||
| Target Release: | 5.7.1 | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | openstack:fip:sdn | ||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-12-07 06:35:27 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: | |||||
| Attachments: |
|
||||||
What input was used for the IP address? It looks like it may have simply been "1", which is an illegal IP address, in which case the error message here is appropriate. The floating ip address was a proper 32 bit one, 192.168.122.212. Incidentally, I can associate the floating ip from Horizon dashboard. Can you attach evm.log and fog.log? evm.log is 100M in size and fog.log around 15M. Pasting the relevant error messages from both the files here as they're short. evm.log ------- [root@cfme42 ~]# grep -i error /var/www/miq/vmdb/log/evm.log | grep -i float [----] E, [2016-11-27T12:16:59.487658 #2882:1833730] ERROR -- : MIQ(ManageIQ::Providers::Openstack::CloudManager::Vm#raw_associate_floating_ip) vm=[cirros0002], floating_ip=[1], error: Expected([200, 202]) <=> Actual(400 Bad Request) [----] E, [2016-11-27T12:16:59.488118 #2882:1833730] ERROR -- : MIQ(vm_cloud_controller-associate_floating_ip_vm): Unable to associate Floating IP 1 with Instance "cirros0002": Invalid input for field/attribute address. Value: 1. u'1' is not valid under any of the given schemas [----] E, [2016-11-27T12:29:12.471688 #2805:17bd120] ERROR -- : MIQ(ManageIQ::Providers::Openstack::CloudManager::Vm#raw_disassociate_floating_ip) vm=[cirros0002], floating_ip=[1], error: Expected([200, 202]) <=> Actual(400 Bad Request) [----] E, [2016-11-27T12:29:12.472003 #2805:17bd120] ERROR -- : MIQ(vm_cloud_controller-disassociate_floating_ip_vm): Unable to disassociate Floating IP 1 from Instance "cirros0002": Invalid input for field/attribute address. Value: 1. u'1' is not valid under any of the given schemas [----] E, [2016-11-29T14:58:57.717398 #2815:bd1d0c] ERROR -- : MIQ(ManageIQ::Providers::Openstack::CloudManager::Vm#raw_associate_floating_ip) vm=[cirros-vol1], floating_ip=[1], error: Expected([200, 202]) <=> Actual(400 Bad Request) [----] E, [2016-11-29T14:58:57.717594 #2815:bd1d0c] ERROR -- : MIQ(vm_cloud_controller-associate_floating_ip_vm): Unable to associate Floating IP 1 with Instance "cirros-vol1": Invalid input for field/attribute address. Value: 1. u'1' is not valid under any of the given schemas fog.log -------- [----] E, [2016-11-29T14:58:57.717398 #2815:bd1d0c] ERROR -- : MIQ(ManageIQ::Providers::Openstack::CloudManager::Vm#raw_associate_floating_ip) vm=[cirros-vol1], floating_ip=[1], error: Expected([200, 202]) <=> Actual(400 Bad Request) [----] E, [2016-11-29T14:58:57.717594 #2815:bd1d0c] ERROR -- : MIQ(vm_cloud_controller-associate_floating_ip_vm): Unable to associate Floating IP 1 with Instance "cirros-vol1": Invalid input for field/attribute address. Value: 1. u'1' is not valid under any of the given schemas FYI, I just checked this with Beta2 version of appliance and the error exists there as well. |
Created attachment 1224756 [details] Screenshot of Floating IP associate error Description of problem: Floating IP address cannot be associated/dis-associated to an OpenStack Instance Version-Release number of selected component (if applicable): Version 5.7.0.10-beta3.20161109111947_9a61b18 How reproducible: Steps to Reproduce: 1. Select an available OpenStack Instance 2. Try to associate / dis-associate a floating ip 3. Attached Error in screenshots appear. Actual results: Expected results: The Floating IP should be associated / dis-associated to/from the instance. Additional info: This is from CFME4.2 Beta 3 RHOS Appliance.