even though this solution is acceptable  it is still not clear to me the difference in behavior between this approach and raising shareresourcenotfound given the code below  l if you always throw shareresourcenotfound  no if else condition as in your code manager will do exactly what you are doing  it will swallow the exception and proceed  if it is not  deleting path as you are checking for such in share status  it will throw exception  just as are you doing  since manager is only swallowing the exception when deleting the share  the only scenario which i think this is valid is if this library is used outside of manila  which is what i understood based on our irc conversation  but by using share  status here i am assuming it will not be used outside of manila manager code path  so i am still confused as why always throwing shareresourcenotfound does not achieve the same behavior as you are implementing in your driver code  please correct me if i am missing something 