unexpected error decoding rpc.Status when 401

[shaul75]

Description of the bug
When the OTLP HTTP exporter receives 401 unauthorized from the collector:

E, [2022-07-26T16:48:17.742186 #13635] ERROR -- : OpenTelemetry error: unexpected error decoding rpc.Status in OTLP::Exporter#log_status - Error occurred during parsing

The problem seem to be caused by a feature introduced in #1152

I don't understand why is Google::Rpc::Status being used to parse the response in that log method. There's only the HTTP protocol exporter, not the gRPC one?

[fbogsany]

The OTLP/HTTP part of the spec unambiguously states

Response body for all HTTP 4xx and HTTP 5xx responses MUST be a Protobuf-encoded Status message that describes the problem.

Originally, this was not implemented correctly in the OTLP collector. This was fixed in open-telemetry/opentelemetry-collector#1788. Are you using an old version of the collector, or a 3rd-party collector?

[github-actions]

👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this issue will be closed eventually by the stale bot.