test/extended/image_ecosystem.NewSampleRepoTest(): fix django-psql

[nalind]

The template for django-psql-example apps doesn't specify a branch, but the default branch no longer contains anything.

Update the test to supply "2.2.x" as the branch name to use in the https://github.com/sclorg/django-ex.git repository.

[nalind]

There are other references to this repository in examples and samples that I didn't touch. Should they be updated to refer to the same tag that this one uses, where it does?

[nalind]

Rebased. The go-verify-deps is complaining about go.mod mentioning github.com/openshift/api v3.9.0+incompatible, even though go.mod also overrides it with a "replace" directive later on.

[nalind]

/retest

[nalind]

/retest

[nalind]

/retest-required

[openshift-trt]

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New Test Risks for sha: 77539a8

Job Name	New Test Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift	High - "Import the release payload "nightly-arm64" from an external source" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift-serial	High - "Import the release payload "nightly-arm64" from an external source" is a new test that was not present in all runs against the current commit.

New tests seen in this PR at sha: 77539a8

• "Import the release payload "nightly-arm64" from an external source" [Total: 8, Pass: 8, Fail: 0, Flake: 0]

[xueqzhan]

Where is this test exercised? I only saw one multi arch job that failed this. I wonder if I can see the change taking effect in one of the presubmits

[nalind]

This test is used in openshift/builder, in my case openshift/builder#469.

[xueqzhan]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nalind, xueqzhan

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:

• test/extended/image_ecosystem/OWNERS [xueqzhan]

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

[openshift-ci]

@nalind: 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/okd-scos-e2e-aws-ovn	77539a8	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-csi	7fd371e	link	true	/test e2e-aws-csi
ci/prow/e2e-gcp-ovn	7fd371e	link	true	/test e2e-gcp-ovn
ci/prow/e2e-gcp-csi	7fd371e	link	true	/test e2e-gcp-csi
ci/prow/e2e-aws-ovn-fips	7fd371e	link	true	/test e2e-aws-ovn-fips
ci/prow/verify	7fd371e	link	true	/test verify
ci/prow/e2e-aws-ovn-microshift-serial	e812c60	link	true	/test e2e-aws-ovn-microshift-serial
ci/prow/e2e-aws-ovn-microshift	e812c60	link	true	/test e2e-aws-ovn-microshift
ci/prow/e2e-aws-ovn-serial-2of2	7fd371e	link	true	/test e2e-aws-ovn-serial-2of2

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.

[openshift-trt]

Job Failure Risk Analysis for sha: 7fd371e

Job Name	Failure Risk
pull-ci-openshift-origin-main-e2e-aws-csi	IncompleteTests Tests for this run (74) are below the historical average (1929): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-2of2	IncompleteTests Tests for this run (74) are below the historical average (1789): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)