Description of problem: If a call to REST-API fails because a triggered command does not get a lock, REST-API returns HTTP status 409 CONFLICT and no machine-readable hint if the conflict is permanent or temporary. If the client would know that this is a temporary problem, he automatically could try again and the call may succeed. Version-Release number of selected component (if applicable): How reproducible: Try to import an external network from a provider during the provider is locked, e.g. by auto sync. Steps to Reproduce: 1. 2. 3. Actual results: REST-API returns HTTP status 409 CONFLICT and no machine-readable hint that the conflict is temporary. Expected results: REST-API returns HTTP status 409 CONFLICT and a machine-readable hint that the conflict is temporary, e.g. as a member of the REST Fault data structure or as a http header, maybe like "Retry-After". Additional info:
As import an external network has decided to wait internally, there is no other API call which request this feature, closing for now.