[Ppal Node]: Retries for connecting to sgx.enigma.co about enigma-core

[lacabra]

@elichai: I have seen this error thrown by core as well. Upon retry, the request would succeed, but there are not retries built in.

[fredfortier]

@lacabra There principal node isn't explicitly retrying these requests. It is calling equote::get_report. You are correct that get_report does not implement any retry mechanism. Do you suggest that the ppal node should retry or including the retry logic in equote::get_report? The latter seems more appropriate to me unless we have reasons to do otherwise.

[lacabra]

@fredfortier As I mentioned above both core and the KeyMgmt suffer from the same issue, so I would suggest to implement the retry in their common code, presumably in equote::get_report as you suggest

[AvishaiW]

@lacabra are you still experiencing this issue? I'm interested in making order in the KM issues. Thanks!

[lacabra]

I have not experienced this particular issue recently, but I don't think this has been addressed either, and in my opinion is worth improving: adding retrials for both core and the km to get the report from our IAS proxy. We are trying to avoid that if for any reason the first attempt fails, either piece of code would crash and bring down the node.

[lacabra]

@AvishaiW (Cc: @moriaab): I have experienced this issue twice right now, once with core and once with the km on different runs. Then it went away. It appears that the Remote Attestation proxy was momentarily unreachable. Can you implement a retry (ideally with an exponential backoff like we have in other parts of contract and p2p for other requests that depend on fetching requests across the network)?

As far as I can tell it is hard to reproduce because it depends on sgx.enigma.co being temporarily down.