OCPNODE-4037: Move usernamespace test into longrunning

[ngopalak-redhat]

• Moving the usernamespace test into the longrunning test suite.
• The tech preview cluster is not needed in OCP 4.22, hence FEATURE_SET: TechPreviewNoUpgrade is not required.
• Ran payload job OCPNODE-4037: Move usernamespace test into longrunning #30792 (comment)
• The test suite is already configured to run once in 24 hours
• I will remove the release job https://github.com/openshift/release/pull/63161/changes after this is merged

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[ngopalak-redhat]

/payload-job periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-disruptive-longrunning

[openshift-ci]

@ngopalak-redhat: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-disruptive-longrunning

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9c711890-0b9b-11f1-8f1e-d21f31a5a099-0

[openshift-ci-robot]

@ngopalak-redhat: This pull request references OCPNODE-4037 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@ngopalak-redhat: This pull request references OCPNODE-4037 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

• Moving the usernamespace test into the longrunning test suite.
• The tech preview cluster is not needed in OCP 4.22, hence FEATURE_SET: TechPreviewNoUpgrade is not required.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@ngopalak-redhat: This pull request references OCPNODE-4037 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

• Moving the usernamespace test into the longrunning test suite.
• The tech preview cluster is not needed in OCP 4.22, hence FEATURE_SET: TechPreviewNoUpgrade is not required.
• Ran payload job OCPNODE-4037: Move usernamespace test into longrunning #30792 (comment)

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 openshift-eng/jira-lifecycle-plugin repository.

[ngopalak-redhat]

/assign @bitoku
cc: @cpmeadors

[openshift-ci-robot]

@ngopalak-redhat: This pull request references OCPNODE-4037 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

• Moving the usernamespace test into the longrunning test suite.
• The tech preview cluster is not needed in OCP 4.22, hence FEATURE_SET: TechPreviewNoUpgrade is not required.
• Ran payload job OCPNODE-4037: Move usernamespace test into longrunning #30792 (comment)
• The test suite is already configured to run once in 24 hours
• I will remove the release job https://github.com/openshift/release/pull/63161/changes after this is merged

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[bitoku]

I guess we need to add an entry in https://github.com/openshift-eng/ci-test-mapping/blob/6c6550d8691e3db3c364e9c0440ba02ceb8b378d/pkg/components/origin-renames.go

[bitoku]

origin/pkg/testsuites/standard_suites.go

Lines 413 to 422 in 3f849f9

	{
	Name: "openshift/usernamespace",
	Description: templates.LongDesc(`
	This test suite runs tests to validate user namespace functionality.
	`),
	Qualifiers: []string{
	`name.contains("[Suite:openshift/usernamespace")`,
	},
	TestTimeout: 60 * time.Minute,
	},

should be deleted. maybe after changing o/release?

[ngopalak-redhat]

origin/pkg/testsuites/standard_suites.go

Lines 413 to 422 in 3f849f9

	{
	Name: "openshift/usernamespace",
	Description: templates.LongDesc(`
	This test suite runs tests to validate user namespace functionality.
	`),
	Qualifiers: []string{
	`name.contains("[Suite:openshift/usernamespace")`,
	},
	TestTimeout: 60 * time.Minute,
	},

should be deleted. maybe after changing o/release?

/hold
Hold until the release PR is merged openshift/release#75030

[ngopalak-redhat]

I guess we need to add an entry in https://github.com/openshift-eng/ci-test-mapping/blob/6c6550d8691e3db3c364e9c0440ba02ceb8b378d/pkg/components/origin-renames.go

Added openshift-eng/ci-test-mapping#614

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ngopalak-redhat
Once this PR has been reviewed and has the lgtm label, please assign petr-muller for approval. For more information see the Code Review Process.

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

Details

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-robot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[openshift-ci]

@ngopalak-redhat: 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/e2e-aws-ovn-serial-1of2	a69efb4	link	true	/test e2e-aws-ovn-serial-1of2
ci/prow/e2e-gcp-ovn-upgrade	a69efb4	link	true	/test e2e-gcp-ovn-upgrade
ci/prow/e2e-metal-ipi-ovn-ipv6	a69efb4	link	true	/test e2e-metal-ipi-ovn-ipv6

Full PR test history. Your PR dashboard.

Details

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.