DRAFT okd-scos test jobs

[omer-vishlitzky]

No description provided.

[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

[omer-vishlitzky]

/test all

[omer-vishlitzky]

/test all

[omer-vishlitzky]

/pj-rehearse pull-ci-openshift-assisted-installer-agent-master-okd-scos-e2e-agent-compact-ipv4 pull-ci-openshift-assisted-service-master-okd-scos-e2e-agent-compact-ipv4 pull-ci-openshift-assisted-installer-master-okd-scos-e2e-agent-compact-ipv4

[openshift-ci-robot]

@omer-vishlitzky: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci-robot]

@omer-vishlitzky, pj-rehearse: failed to create rehearsal jobs ERROR:

failed to ensure imagestreamtags in cluster build05: failed waiting for imagestreamtag origin/scos-4.16:base-stream8 to appear: get failed: client rate limiter Wait returned an error: context deadline exceeded

If the problem persists, please contact Test Platform.

[omer-vishlitzky]

/test all

[omer-vishlitzky]

/pj-rehearse pull-ci-openshift-assisted-installer-agent-master-okd-scos-e2e-agent-compact-ipv4 pull-ci-openshift-assisted-service-master-okd-scos-e2e-agent-compact-ipv4 pull-ci-openshift-assisted-installer-master-okd-scos-e2e-agent-compact-ipv4

[openshift-ci-robot]

@omer-vishlitzky: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[omer-vishlitzky]

/retest ci/prow/ci-operator-registry

[openshift-ci]

@omer-vishlitzky: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

• /test app-ci-config-dry
• /test boskos-config
• /test boskos-config-generation
• /test build-clusters
• /test build01-dry
• /test build02-dry
• /test build03-dry
• /test build04-dry
• /test build05-dry
• /test build09-dry
• /test build10-dry
• /test check-gh-automation
• /test check-gh-automation-tide
• /test ci-operator-config
• /test ci-operator-config-metadata
• /test ci-operator-registry
• /test ci-secret-bootstrap-config-validation
• /test ci-testgrid-allow-list
• /test clusterimageset-validate
• /test config
• /test core-valid
• /test deprecate-templates
• /test generated-config
• /test generated-dashboards
• /test hosted-mgmt-dry
• /test jira-lifecycle-config
• /test openshift-image-mirror-mappings
• /test ordered-prow-config
• /test owners
• /test pr-reminder-config
• /test prow-config
• /test prow-config-filenames
• /test prow-config-semantics
• /test pylint
• /test release-config
• /test release-controller-config
• /test secret-generator-config-valid
• /test services-valid
• /test stackrox-stackrox-stackrox-stackrox-check
• /test step-registry-metadata
• /test step-registry-shellcheck
• /test sync-rover-groups
• /test vsphere02-dry
• /test yamllint

Use /test all to run the following jobs that were automatically triggered:

• pull-ci-openshift-release-check-gh-automation
• pull-ci-openshift-release-master-build-clusters
• pull-ci-openshift-release-master-ci-operator-config
• pull-ci-openshift-release-master-ci-operator-config-metadata
• pull-ci-openshift-release-master-ci-operator-registry
• pull-ci-openshift-release-master-config
• pull-ci-openshift-release-master-core-valid
• pull-ci-openshift-release-master-deprecate-templates
• pull-ci-openshift-release-master-generated-config
• pull-ci-openshift-release-master-ordered-prow-config
• pull-ci-openshift-release-master-owners
• pull-ci-openshift-release-master-prow-config-filenames
• pull-ci-openshift-release-master-prow-config-semantics
• pull-ci-openshift-release-master-release-controller-config
• pull-ci-openshift-release-openshift-image-mirror-mappings
• pull-ci-openshift-release-yamllint

In response to this:

/retest ci/prow/ci-operator-registry

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.

[omer-vishlitzky]

/retest required

[openshift-ci]

@omer-vishlitzky: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

• /test app-ci-config-dry
• /test boskos-config
• /test boskos-config-generation
• /test build-clusters
• /test build01-dry
• /test build02-dry
• /test build03-dry
• /test build04-dry
• /test build05-dry
• /test build09-dry
• /test build10-dry
• /test check-gh-automation
• /test check-gh-automation-tide
• /test ci-operator-config
• /test ci-operator-config-metadata
• /test ci-operator-registry
• /test ci-secret-bootstrap-config-validation
• /test ci-testgrid-allow-list
• /test clusterimageset-validate
• /test config
• /test core-valid
• /test deprecate-templates
• /test generated-config
• /test generated-dashboards
• /test hosted-mgmt-dry
• /test jira-lifecycle-config
• /test openshift-image-mirror-mappings
• /test ordered-prow-config
• /test owners
• /test pr-reminder-config
• /test prow-config
• /test prow-config-filenames
• /test prow-config-semantics
• /test pylint
• /test release-config
• /test release-controller-config
• /test secret-generator-config-valid
• /test services-valid
• /test stackrox-stackrox-stackrox-stackrox-check
• /test step-registry-metadata
• /test step-registry-shellcheck
• /test sync-rover-groups
• /test vsphere02-dry
• /test yamllint

Use /test all to run the following jobs that were automatically triggered:

• pull-ci-openshift-release-check-gh-automation
• pull-ci-openshift-release-master-build-clusters
• pull-ci-openshift-release-master-ci-operator-config
• pull-ci-openshift-release-master-ci-operator-config-metadata
• pull-ci-openshift-release-master-ci-operator-registry
• pull-ci-openshift-release-master-config
• pull-ci-openshift-release-master-core-valid
• pull-ci-openshift-release-master-deprecate-templates
• pull-ci-openshift-release-master-generated-config
• pull-ci-openshift-release-master-ordered-prow-config
• pull-ci-openshift-release-master-owners
• pull-ci-openshift-release-master-prow-config-filenames
• pull-ci-openshift-release-master-prow-config-semantics
• pull-ci-openshift-release-master-release-controller-config
• pull-ci-openshift-release-openshift-image-mirror-mappings
• pull-ci-openshift-release-yamllint

In response to this:

/retest 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 kubernetes/test-infra repository.

[omer-vishlitzky]

/retest-required

[omer-vishlitzky]

/pj-rehearse pull-ci-openshift-assisted-installer-agent-master-okd-scos-e2e-agent-compact-ipv4 pull-ci-openshift-assisted-service-master-okd-scos-e2e-agent-compact-ipv4 pull-ci-openshift-assisted-installer-master-okd-scos-e2e-agent-compact-ipv4

[openshift-ci-robot]

@omer-vishlitzky: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[omer-vishlitzky]

/test all

[omer-vishlitzky]

/test ci-operator-registry

[openshift-ci]

@omer-vishlitzky: 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/rehearse/openshift/assisted-installer/master/okd-scos-e2e-agent-compact-ipv4	81c4ce0	link	unknown	/pj-rehearse pull-ci-openshift-assisted-installer-master-okd-scos-e2e-agent-compact-ipv4
ci/rehearse/openshift/assisted-service/master/okd-scos-e2e-agent-compact-ipv4	81c4ce0	link	unknown	/pj-rehearse pull-ci-openshift-assisted-service-master-okd-scos-e2e-agent-compact-ipv4
ci/rehearse/openshift/assisted-installer-agent/master/okd-scos-e2e-agent-compact-ipv4	81c4ce0	link	unknown	/pj-rehearse pull-ci-openshift-assisted-installer-agent-master-okd-scos-e2e-agent-compact-ipv4

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: omer-vishlitzky
Once this PR has been reviewed and has the lgtm label, please assign jupierce for approval. For more information see the Kubernetes Code Review Process.

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

[omer-vishlitzky]

/test all

[openshift-merge-robot]

PR needs rebase.

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.

[openshift-ci-robot]

@omer-vishlitzky, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

couldn't prepare candidate: couldn't rebase candidate onto master: %!w(<nil>)

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci-robot]

@omer-vishlitzky, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

couldn't prepare candidate: couldn't rebase candidate onto master: %!w(<nil>)

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci-robot]

@omer-vishlitzky, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

couldn't prepare candidate: couldn't rebase candidate onto master: %!w(<nil>)

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.