delete_host was allowing the remote call for cluster membership to raise
a RemoteProcedureCallException. This exception was being caught and
handled returning a 404. However, when a host has no cluster membership
the host was being deleted yet a 404 was returned to the client. This
adds a narrow try/except around the cluster membership logic and handles
the exception properly.
ashcrow
commented
7 years ago 
delete_hostwas allowing the remote call for cluster membership to raise aRemoteProcedureCallException. This exception was being caught and handled returning a404. However, when a host has no cluster membership the host was being deleted yet a404was returned to the client. This adds a narrowtry/exceptaround the cluster membership logic and handles the exception properly.This issue was found during e2e testing.