AttributeError: 'int' object has no attribute 'status'

[asqui]

New failure mode that might also be arising from unexpected responses from the REST API (hard to tell for certain because the inner exception detail is lost when it gets re-raised -- perhaps that is a separate issue that needs attention?)

  File "/opt/ecn/python_3rd_party/opsgenie_sdk/api/alert/__init__.py", line 2166, in list_alerts
    (data) = self.list_alerts_with_http_info(**kwargs)  # noqa: E501
  File "/opt/ecn/python_3rd_party/opsgenie_sdk/api/alert/__init__.py", line 2261, in list_alerts_with_http_info
    collection_formats=collection_formats)
  File "/opt/ecn/python_3rd_party/opsgenie_sdk/api_client.py", line 432, in call_api
    _preload_content, _request_timeout, _host)
  File "/opt/ecn/python_3rd_party/opsgenie_sdk/api_client.py", line 222, in __call_api
    raise exception
AttributeError: 'int' object has no attribute 'status'

This error happened only once and then went away, so that supports the hypothesis that it was some sort of strange REST response that caused it. If so, this will be the third recent example of API failure due to unexpected REST responses.

Maybe what is needed is a holistic approach to processing REST responses that triggers retries if any expectation about a normal REST response is not met?

[shilobar]

I'm seeing a similar exception several times a day:

  File "/usr/local/lib/python3.7/site-packages/opsgenie_sdk/api/alert/__init__.py", line 1136, in create_alert
    (data) = self.create_alert_with_http_info(create_alert_payload, **kwargs)  # noqa: E501
  File "/usr/local/lib/python3.7/site-packages/opsgenie_sdk/api/alert/__init__.py", line 1211, in create_alert_with_http_info
    collection_formats=collection_formats)
  File "/usr/local/lib/python3.7/site-packages/opsgenie_sdk/api_client.py", line 428, in call_api
    _preload_content, _request_timeout, _host)
  File "/usr/local/lib/python3.7/site-packages/opsgenie_sdk/api_client.py", line 218, in __call_api
    raise exception
  File "/usr/local/lib/python3.7/site-packages/opsgenie_sdk/api_client.py", line 202, in __call_api
    _request_timeout=_request_timeout)
  File "/usr/local/lib/python3.7/site-packages/tenacity/__init__.py", line 430, in __call__
    do = self.iter(retry_state=retry_state)
  File "/usr/local/lib/python3.7/site-packages/tenacity/__init__.py", line 367, in iter
    return fut.result()
  File "/usr/local/lib/python3.7/concurrent/futures/_base.py", line 428, in result
    return self.__get_result()
  File "/usr/local/lib/python3.7/concurrent/futures/_base.py", line 384, in __get_result
    raise self._exception
  File "/usr/local/lib/python3.7/site-packages/tenacity/__init__.py", line 433, in __call__
    result = fn(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/opsgenie_sdk/api_client.py", line 473, in request
    body=body)
  File "/usr/local/lib/python3.7/site-packages/opsgenie_sdk/rest.py", line 313, in POST
    body=body)
  File "/usr/local/lib/python3.7/site-packages/opsgenie_sdk/rest.py", line 264, in request
    exception = exceptions.build_exception(response=r)
  File "/usr/local/lib/python3.7/site-packages/opsgenie_sdk/exceptions.py", line 237, in build_exception
    exception.status = response.status
AttributeError: 'int' object has no attribute 'status'

[mhamzak008]

Hi @shilobar which version of the SDK are you using?

[shilobar]

@mhamzak008 I'm using opsgenie-sdk==2.1.3

[asqui]

This looks to be due to a bug in the implementation of build_exception() where it is doing a dictionary lookup to find an exception instance, but the default return value is the integer -100.

I guess what was intended was to have ApiException() as the default value.

opsgenie-python-sdk/opsgenie_sdk/exceptions.py

Lines 211 to 242 in bb718ae

	def build_exception(response):
	http_error_code = response.status
	exception = {
	400: ConfigurationException(reason="Invalid JSON body"),
	401: AuthenticationException(reason="apiKey is invalid or integration is disabled"),
	402: AuthenticationException(
	reason="apiKey is valid but the account cannot do this action because of subscription plan"),
	403: AuthenticationException(
	reason="apiKey is valid but the apiKey cannot do this operation because of permissions"),
	404: ApiException(reason="Resource or handler not found"),
	405: AuthenticationException(reason="URL is valid but HTTP method not supported"),
	406: ConfigurationException(reason="Requested format is not supported (Accept header)"),
	409: ConfigurationException(
	reason="ID or name conflicts with another entity. E.g. integration name already exists"),
	410: ConfigurationException(reason="Feature is deprecated"),
	415: ConfigurationException(reason="Request body format is not supported (Content-Type header)"),
	416: ConfigurationException(reason="The given range is not supported."),
	422: ConfigurationException(reason="Semantic errors in request body"),
	428: ConfigurationException(reason="Entity is used by another entity (schedule,escalation,team,etc)"),
	429: ApiException(reason="Throttling"),
	500: ServerErrorException(reason="Internal Server Error"),
	501: ServerErrorException(reason="Not Implemented"),
	503: ServerErrorException(reason="Back-end servers are at capacity"),
	-100: ApiException()
	}.get(http_error_code, -100)
	exception.status = response.status
	exception.reason = response.reason + ": " + exception.reason
	exception.body = response.data
	exception.headers = response.getheaders()
	return exception

[asqui]

I think this is now resolved by PR #55