address bld forcepull ext test etc update conflict flake

[gabemontero]

Fixes #17836

@openshift/sig-developer-experience ptal

[bparees]

this doesn't resolve 100% of the problem since conflicts can still occur on the add-cluster-role-to-user call too.

The add needs a retry on conflict loop. Or you can wait for @enj to fix #17596 (which is a dupe of the issue you referenced) properly (add generic retrying to the role management api)

So this is a fine simplification but not the full solution.

/lgtm
/hold
remove the hold when tests pass

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bparees, gabemontero

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

• test/extended/OWNERS [bparees]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[gabemontero]

thanks for the info @bparees

this test passed in extended builds so removing hold tag

will wait a bit on @enj 's progress with #17596 before adding any retry in the forcepull test

/retest

[openshift-merge-robot]

/test all [submit-queue is verifying that this PR is safe to merge]

[openshift-merge-robot]

Automatic merge from submit-queue (batch tested with PRs 17744, 17840, 17874).

[openshift-ci-robot]

@gabemontero: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
ci/openshift-jenkins/extended_conformance_gce	8c6bf4e	link	/test extended_conformance_gce

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.