setUp must be called on a fixture's parent first
setUp must be called on a fixture's parent first

There is some odd behavior when a fixture's setUp fails before it has a
change to call the parent's setUp. It causes an error in the error
handling and the original exception is lost. The bug has been reported
upstream:
  https://bugs.launchpad.net/python-fixtures/+bug/1299502

Change-Id: I27cbfbe2c8ae34e72950361f8d0d7d8d3e249f8c

maestro-hybrid-cloud/keystone,dims/keystone,himanshu-setia/keystone,openstack/keystone,reeshupatel/demo,nuxeh/keystone,ging/keystone,nuxeh/keystone,jonnary/keystone,promptworks/keystone,cernops/keystone,vivekdhayaal/keystone,mahak/keystone,ajayaa/keystone,MaheshIBM/keystone,jamielennox/keystone,UTSA-ICS/keystone-kerberos,idjaw/keystone,rajalokan/keystone,blueboxgroup/keystone,idjaw/keystone,blueboxgroup/keystone,takeshineshiro/keystone,dstanek/keystone,jamielennox/keystone,mahak/keystone,rajalokan/keystone,jonnary/keystone,dims/keystone,openstack/keystone,dstanek/keystone,rushiagr/keystone,ilay09/keystone,ging/keystone,nuxeh/keystone,jumpstarter-io/keystone,klmitch/keystone,roopali8/keystone,ilay09/keystone,takeshineshiro/keystone,cernops/keystone,himanshu-setia/keystone,jumpstarter-io/keystone,maestro-hybrid-cloud/keystone,ajayaa/keystone,vivekdhayaal/keystone,UTSA-ICS/keystone-kerberos,mahak/keystone,reeshupatel/demo,promptworks/keystone,ilay09/keystone,jumpstarter-io/keystone,openstack/keystone,rushiagr/keystone,reeshupatel/demo,dstanek/keystone,promptworks/keystone,rodrigods/keystone,rajalokan/keystone,rodrigods/keystone,rushiagr/keystone,vivekdhayaal/keystone,MaheshIBM/keystone,klmitch/keystone,roopali8/keystone