Created attachment 1275892 [details] evm logs Description of problem: Added OpenStack Infra provider and getting errors in "<Excon::Error::NotFound: Expected(200) <=> Actual(404 Not Found)" evm.log Version-Release number of selected component (if applicable): 5.8.0.13-rc2.20170502165848_0f98658 How reproducible:100% Steps to Reproduce: 1. Add OpenStack Infra provider 2. Watch evm.log 3. Actual results: Error in evm.log Expected results: There shouldn't be any error in evm.log Additional info:
Hi! Can I just confirm that the refresh completed, and no errors appeared in the UI?
Hello Tzu-Mainn, Refresh on OpenStack Infra Provider completed without any error in UI. Please tell me if you need any help. Thanks, Satyajit Bulage.
Okay, thanks! What's happening is that the undercloud doesn't have neutron extensions for routers/floatingips installed, so when it tries to refresh those, you see those errors. However, the refresh process catches the errors and proceeds to the finish successfully. We could possibly hide these errors from appearing in the log.
(In reply to Tzu-Mainn Chen from comment #4) > Okay, thanks! What's happening is that the undercloud doesn't have neutron > extensions for routers/floatingips installed, so when it tries to refresh > those, you see those errors. However, the refresh process catches the errors > and proceeds to the finish successfully. > > We could possibly hide these errors from appearing in the log. I think we should not hide it, we just need to think if this is more a warning then an Error in this context.
Right, wrap those errors into a pretty WARN message
I think this is another bug that's resolved by the fix in https://github.com/ManageIQ/manageiq-providers-openstack/pull/156 Most of these 404 errors should now be caught and logged as warnings rather than errors. The PR I linked is included in 5.8.4
The fix linked above, for BZ 1460683 should also resolve the errors reported here, since with the fix they will only be logged as warnings. Closing as a duplicate. *** This bug has been marked as a duplicate of bug 1460683 ***