Alright then I'll have to look at this deeper later and maybe remove this rescue all together. 

The other one can definitely be called and looks nasty in the UI. 


> Am 03.04.2014 um 13:44 schrieb Dominic Cleal <notifications@github.com>:
> 
> In app/models/concerns/orchestration/realm.rb:
> 
> > @@ -23,7 +23,7 @@ def del_realm
> >      logger.info "Delete realm entry for #{name}"
> >      @realm_api.delete name
> >    rescue => e
> > -    failure _("Failed to remove %{name}'s realm entry: %{e}") % { :name => name, :e => proxy_error(e) }
> > +    failure _("Failed to remove %{name}'s realm entry: %{e}") % { :name => name, :e => e.message }
> It should return a ProxyException (which wraps some sort of RestClient exception, which might contain the string "XMLRPC::Fault" from the proxy), at least in the create code below. I don't think the destroy will actually ever fail as there's a rescue true in the proxy API. (Other proxy impls will return a 404 status when the host is unknown, maybe the proxy realm API should too.)
> 
> —
> Reply to this email directly or view it on GitHub.