[test] [wip] Test delete vw

[skonto]

Fixes JIRA #

Proposed Changes

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: skonto

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [skonto]

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

[skonto]

The ImageStreamTag "4-15:operator-registry" is invalid: from: Error resolving ImageStreamTag 4-15:operator-registry in namespace openshift-marketplace: unable to find latest tagged image

[skonto]

/test 415-upstream-e2e-aws-415

[skonto]

/test 415-operator-e2e-aws-415

[skonto]

The ImageStreamTag "4-15:operator-registry" is invalid: from: Error resolving ImageStreamTag 4-15:operator-registry in namespace openshift-marketplace: unable to find latest tagged image
11:22:40.282 ERROR: 🚨 Error (code: 1) occurred at ./hack/lib/catalogsource.bash:153, with command: oc -n "${OLM_NAMESPACE}" start-build "${name}" --from-dir "${from_dir}" -F

[skonto]

/retest

[skonto]

/test 412-operator-e2e-aws-412

[skonto]

It times out.

  - lastTransitionTime: "2025-01-30T19:37:52Z"
    lastUpdateTime: "2025-01-30T19:37:52Z"
    message: 'installing: waiting for deployment knative-openshift to become ready:
      deployment "knative-openshift" not available: Deployment does not have minimum
      availability.'

Keeps pulling the cli image see here

  Type    Reason          Age    From               Message
  ----    ------          ----   ----               -------
  Normal  Scheduled       5m49s  default-scheduler  Successfully assigned openshift-serverless/knative-openshift-668b88d59d-pms4f to ip-10-0-58-205.ec2.internal
  Normal  AddedInterface  5m49s  multus             Add eth0 [10.130.2.18/23] from ovn-kubernetes
  Normal  Pulling         5m48s  kubelet            Pulling image "registry.ci.openshift.org/openshift/knative-v1.14.0:kn-cli-artifacts"

Pod started :

Node:           ip-10-0-58-205.ec2.internal/10.0.58.205
Start Time:     Thu, 30 Jan 2025 19:32:49 +0000

I think it takes a long time to schedule the pod? 🤔

cc @dsimansk

[openshift-ci]

@skonto: 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/412-upstream-e2e-aws-412	25d1191	link	false	/test 412-upstream-e2e-aws-412
ci/prow/412-operator-e2e-aws-412	25d1191	link	true	/test 412-operator-e2e-aws-412
ci/prow/412-test-upgrade-aws-412	25d1191	link	true	/test 412-test-upgrade-aws-412
ci/prow/412-upstream-e2e-kafka-aws-412	25d1191	link	false	/test 412-upstream-e2e-kafka-aws-412
ci/prow/415-upstream-e2e-aws-415	25d1191	link	false	/test 415-upstream-e2e-aws-415
ci/prow/415-operator-e2e-aws-415	25d1191	link	true	/test 415-operator-e2e-aws-415
ci/prow/415-upstream-e2e-kafka-aws-415	25d1191	link	false	/test 415-upstream-e2e-kafka-aws-415

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.