STAKE_POOLS_JOIN_01

[KtorZ]

Context

https://buildkite.com/input-output-hk/cardano-wallet/builds/8707#bfb3375e-aed3-4c46-ab57-763b9d4c5c02

Test Case

STAKE_POOLS_JOIN_01, in src/Test/Integration/Scenario/API/Shelley/StakePools.hs:123:15

Failure / Counter-example

      1) API Specifications STAKE_POOLS_JOIN_01 - Cannot join existant stakepool with wrong password
           expected: Status {statusCode = 403, statusMessage = "Forbidden"}
            but got: Status {statusCode = 404, statusMessage = "Not Found"}

from the following response: Left (DecodeFailure "Error in $: parsing Cardano.Wallet.Api.Types.ApiTransaction(ApiTransaction) failed, key \"id\" not found: Response {responseStatus = Status {statusCode = 404, statusMessage = \"Not Found\"}, responseVersion = HTTP/1.1, responseHeaders = [(\"Transfer-Encoding\",\"chunked\"),(\"Date\",\"Tue, 30 Jun 2020 00:48:40 GMT\"),(\"Server\",\"Warp/3.3.5\")], responseBody = \"{\\\"code\\\":\\\"no_such_pool\\\",\\\"message\\\":\\\"I couldn't find any stake pool with the given id: 1b3dc19c6ab89eaffc8501f375bb03c11bf8ed5d183736b1d80413d6\\\"}\", responseCookieJar = CJ {expose = []}, responseClose' = ResponseClose}")

---

Resolution

Seems like that somehow, one of the cluster's pools isn't listed anymore, but only during this scenario. It could be a momentary rollback but the pools scenarios are running quite late in the test suite, and thus the corresponding pool should already exist in the immutable part.

---

QA