Cost analytics for Openstack failing

[James Smith]

Cost analytics wasn't working for me at all until I updated gevent on my scalr server. Now cost analytics is working for AWS, but not for Openstack.

I'm seeing the following error in python-analytics_poller.log for all my openstack environments:

[22/Nov/2016 22:14:40][    analytics_poller][  6490]    WARNING platform: 'openstack', environments: [11]. Reason: <class 'libcloud.common.exceptions.BaseHTTPError'> {"error": {"message": "The resource could not be found.", "code": 404, "title": "Not Found"}}

[22/Nov/2016 22:14:40][    analytics_poller][  6490]    WARNING platform: 'openstack', environments: [9]. Reason: <class 'libcloud.common.exceptions.BaseHTTPError'> {"error": {"message": "The resource could not be found.", "code": 404, "title": "Not Found"}}

[22/Nov/2016 22:14:40][    analytics_poller][  6490]    WARNING platform: 'openstack', environments: [8]. Reason: <class 'libcloud.common.exceptions.BaseHTTPError'> {"error": {"message": "The resource could not be found.", "code": 404, "title": "Not Found"}}

[22/Nov/2016 22:14:40][    analytics_poller][  6490]    WARNING platform: 'openstack', environments: [13, 14]. Reason: <class 'libcloud.common.exceptions.BaseHTTPError'> {"error": {"message": "The resource could not be found.", "code": 404, "title": "Not Found"}}

[22/Nov/2016 22:14:40][    analytics_poller][  6490]    WARNING platform: 'openstack', environments: [12]. Reason: <class 'libcloud.common.exceptions.BaseHTTPError'> {"error": {"message": "The resource could not be found.", "code": 404, "title": "Not Found"}}

[22/Nov/2016 22:14:40][    analytics_poller][  6490]    WARNING platform: 'openstack', environments: [15]. Reason: <class 'libcloud.common.exceptions.BaseHTTPError'> {"error": {"message": "The resource could not be found.", "code": 404, "title": "Not Found"}}

[22/Nov/2016 22:14:40][    analytics_poller][  6490]    WARNING platform: 'openstack', environments: [4]. Reason: <class 'libcloud.common.exceptions.BaseHTTPError'> {"error": {"message": "The resource could not be found.", "code": 404, "title": "Not Found"}}

[22/Nov/2016 22:14:40][    analytics_poller][  6490]    WARNING platform: 'openstack', environments: [10]. Reason: <class 'libcloud.common.exceptions.BaseHTTPError'> {"error": {"message": "The resource could not be found.", "code": 404, "title": "Not Found"}}

The error is generated by a libcloud call from the _openstack function in scalrpy/analytics_poller.py:

service_catalog = _libcloud_get_service_catalog(driver)

I haven't managed to track down exactly where in the libcloud calls everything is falling apart, though. Has anyone experienced this issue with scalr/openstack? 

[Marc O'Brien]

Hi James,

Manual update of gevent should not have been necessary.  It sounds like there may be configuration or networking issues with your installation.  Can you send a screenshot of your OpenStack Cloud Credentials configuration along with a confirmation of your OpenStack version?

Many thanks,
Wm. Marc O'Brien
Scalr Technical Support

[James Smith]

Prior to the gevent upgrade, I was getting SSL errors in the analytics_poller log that a quick internet search suggested was a gevent bug. Upgrading gevent resolved that issue.

Attached is a screenshot of the openstack credentials screen, as requested. We're running Openstack Mitaka on CentOS 7. Please let me know if there's any other information you need!

[Gianni Acciarri]

Hi James,

I've been having the same problem and not being a Python developer I am having issues upgrading gevent to 1.0.2. I looked online but no luck so far  :( Can you tell me how you updated gevent on your scalr instance?

Thanks

[James Smith]

'find /opt/scalr-server -name gevent* -type d' to verify that gevent needs to be upgraded

'/opt/scalr-server/embedded/bin/pip install --upgrade --install-option='--prefix=/opt/scalr-server/embedded/' gevent==1.0.2' to upgrade to gevent 1.0.2

[Gianni Acciarri]

Thank you James! Worked perfectly. Apparently errors are still generated for GCE accounts (could be a permissions thing) but as far as AWS goes updating gevent to 1.0.2 fixes the issue. Cheers!