chore: Update from ubi8-minimal:8.10-1086 to ubi8-minimal:8.10-1130

[che-bot]

trafficstars

Signed-off-by: Nick Boldt [email protected]

[ibuziuk]

/retest

[ibuziuk]

@artaleks9 please, review - looks like there were a few failing tests

[artaleks9]

It seems, there was a common infrastructure problem, because all fail tests have a similar error status 502 Bad Gateway, status code 502:

could not run steps: step gitlab-no-pat-oauth-flow-ssh-url failed: failed to acquire lease for "che-aws-quota-slice": status 502 Bad Gateway, status code 502 

So, the /retest is correct solution

[artaleks9]

ci/prow/v14-gitlab-with-oauth-setup-flow was still fail by the same reason:

could not run steps: step gitlab-with-oauth-setup-flow failed: failed to acquire lease for "che-aws-quota-slice": status 502 Bad Gateway, status code 502 

Trying /retest again

[artaleks9]

/retest

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: artaleks9, che-bot, ibuziuk

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

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci[bot]]

@che-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/v19-azure-no-pat-oauth-flow-raw-devfile-url	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-azure-no-pat-oauth-flow-raw-devfile-url
ci/prow/v19-gitlab-with-oauth-setup-flow	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-gitlab-with-oauth-setup-flow
ci/prow/v19-github-no-pat-oauth-flow-raw-devfile-url	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-github-no-pat-oauth-flow-raw-devfile-url
ci/prow/v19-gitea-with-pat-setup-flow	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-gitea-with-pat-setup-flow
ci/prow/v19-gitea-no-pat-oauth-flow	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-gitea-no-pat-oauth-flow
ci/prow/v19-github-no-pat-oauth-flow-ssh-url	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-github-no-pat-oauth-flow-ssh-url
ci/prow/v19-bitbucket-no-pat-oauth-flow	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-bitbucket-no-pat-oauth-flow
ci/prow/v19-github-no-pat-oauth-flow	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-github-no-pat-oauth-flow
ci/prow/v19-gitlab-no-pat-oauth-flow-raw-devfile-url	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-gitlab-no-pat-oauth-flow-raw-devfile-url
ci/prow/v19-azure-no-pat-oauth-flow-ssh-url	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-azure-no-pat-oauth-flow-ssh-url
ci/prow/v19-bitbucket-no-pat-oauth-flow-raw-devfile-url	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-bitbucket-no-pat-oauth-flow-raw-devfile-url
ci/prow/v19-bitbucket-no-pat-oauth-flow-ssh-url	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-bitbucket-no-pat-oauth-flow-ssh-url
ci/prow/v19-che-smoke-test	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-che-smoke-test
ci/prow/v19-azure-no-pat-oauth-flow	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-azure-no-pat-oauth-flow
ci/prow/v19-azure-with-pat-setup-flow	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-azure-with-pat-setup-flow
ci/prow/v19-gitlab-with-pat-setup-flow	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-gitlab-with-pat-setup-flow
ci/prow/v19-github-with-pat-setup-flow	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-github-with-pat-setup-flow
ci/prow/v19-gitlab-no-pat-oauth-flow-ssh-url	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-gitlab-no-pat-oauth-flow-ssh-url
ci/prow/v19-gitlab-no-pat-oauth-flow	5000cf789befa0dcce6ca01069fe045602ca3731	link	true	/test v19-gitlab-no-pat-oauth-flow

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.