Failing ES Promotion: Ingest Node Pipelines Pipelines Delete should return an error for any pipelines not sucessfully deleted

[jbudz]

CI Error

How to run against the new snapshot. I'll update if/when this isn't required - we'll promote if the skip gives a green build next.

{ Error: expected { itemsDeleted: [],
  errors: 
   [ { name: 'test_delete_pipeline_1', error: [Object] },
     { name: 'pipeline_does_not_exist', error: [Object] } ] } to sort of equal { itemsDeleted: [ 'test_delete_pipeline_1' ],
  errors: [ { name: 'pipeline_does_not_exist', error: [Object] } ] }
    at Assertion.assert (/dev/shm/workspace/kibana/packages/kbn-expect/expect.js:100:11)
    at Assertion.eql (/dev/shm/workspace/kibana/packages/kbn-expect/expect.js:244:8)
    at Context.it (test/api_integration/apis/management/ingest_pipelines/ingest_pipelines.ts:295:25

looks limited to a formatting change via from elastic/elasticsearch#58207. one moment on shas for skipped tests

[jbudz]

main: 8021616
7.x: 4bc149e
7.9: 32b6244

[elasticmachine]

Pinging @elastic/ingest-management (Team:Ingest Management)

[elasticmachine]

Pinging @elastic/es-ui (Team:Elasticsearch UI)

[cjcenizal]

@alisonelizabeth Could you check this one out please? I suspect we just need to await calls to createPipeline, otherwise it seems like we'd end up with a race condition, which would explain the failure here. Though I could have expected a race condition to yield flaky test results sooner. 🤔

[alisonelizabeth]

I'm not able to reproduce the failure. The ES PR referenced is related to the simulate API and doesn't appear to affect the creation/deletion of a pipeline. I just merged #73289, which should make the tests more robust. I'm going to close this issue for now, but feel free to open if the issue resurfaces.