So yes, this is bad, but unfortunately the fingerprint you gave tags:"screen-n-cpu.txt" AND message:"oslo.messaging.rpc.dispatcher UnexpectedTaskStateError: Unexpected task state: expecting (u'powering-off',) but the actual state is None" hits successful jobs more then failed jobs. My guess is this is either not the root cause, or this bug only causes tempest to fail in specific cases and not every time.
So yes, this is bad, but unfortunately the fingerprint you gave tags:"screen- n-cpu.txt" AND message: "oslo.messaging .rpc.dispatcher UnexpectedTaskS tateError: Unexpected task state: expecting (u'powering-off',) but the actual state is None" hits successful jobs more then failed jobs. My guess is this is either not the root cause, or this bug only causes tempest to fail in specific cases and not every time.