Skip to content

Add conformance with tech-preview for hcp#64184

Closed
enxebre wants to merge 1 commit intoopenshift:masterfrom
enxebre:hcp-conformance-tech-preview
Closed

Add conformance with tech-preview for hcp#64184
enxebre wants to merge 1 commit intoopenshift:masterfrom
enxebre:hcp-conformance-tech-preview

Conversation

@enxebre
Copy link
Copy Markdown
Member

@enxebre enxebre commented Apr 23, 2025

No description provided.

@enxebre
Copy link
Copy Markdown
Member Author

enxebre commented Apr 23, 2025

/pj-rehearse pull-ci-openshift-api-master-e2e-aws-ovn-hypershift-conformance-techpreview

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@enxebre: job(s): pull-ci-openshift-api-master-e2e-aws-ovn-hypershift-conformance-techpreview either don't exist or were not found to be affected, and cannot be rehearsed

@enxebre
Copy link
Copy Markdown
Member Author

enxebre commented Apr 23, 2025

/pj-rehearse pull-ci-openshift-api-release-4.19-e2e-aws-ovn-hypershift-conformance-techpreview

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

@enxebre
Copy link
Copy Markdown
Member Author

enxebre commented Apr 23, 2025

/hold

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 23, 2025
@enxebre enxebre force-pushed the hcp-conformance-tech-preview branch from ff5a2f1 to 3fa5fb2 Compare April 23, 2025 12:59
@enxebre
Copy link
Copy Markdown
Member Author

enxebre commented Apr 23, 2025

/pj-rehearse pull-ci-openshift-api-release-4.30-e2e-aws-ovn-hypershift-conformance-techpreview

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@enxebre: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-api-master-e2e-aws-ovn-hypershift-conformance-techpreview openshift/api presubmit Presubmit changed
pull-ci-openshift-api-release-4.20-e2e-aws-ovn-hypershift-conformance-techpreview openshift/api presubmit Presubmit changed
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 list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

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
Copy link
Copy Markdown
Contributor

@enxebre: job(s): pull-ci-openshift-api-release-4.30-e2e-aws-ovn-hypershift-conformance-techpreview either don't exist or were not found to be affected, and cannot be rehearsed

@JoelSpeed
Copy link
Copy Markdown
Contributor

/approve
/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 23, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: enxebre, JoelSpeed

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 23, 2025
@enxebre
Copy link
Copy Markdown
Member Author

enxebre commented Apr 23, 2025

/pj-rehearse pull-ci-openshift-api-release-4.20-e2e-aws-ovn-hypershift-conformance-techpreview

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

@JoelSpeed
Copy link
Copy Markdown
Contributor

/pj-rehearse ack

The test suite is configured correctly, but I think is picking up a legitimate issue with MCN

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Apr 23, 2025
@sjenning
Copy link
Copy Markdown
Contributor

sjenning commented Apr 24, 2025

New tests added 4/18 for MCN are failing in the rehearsal. Added in openshift/origin#29683

@JoelSpeed
Copy link
Copy Markdown
Contributor

That should be resolved by openshift/origin#29712

The MCN isn't deployed on HyperShift so the intention is to skip those tests in HCP

@sjenning
Copy link
Copy Markdown
Contributor

openshift/origin#29712 merged

/pj-rehearse pull-ci-openshift-api-release-4.20-e2e-aws-ovn-hypershift-conformance-techpreview

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

@JoelSpeed
Copy link
Copy Markdown
Contributor

/pj-rehearse pull-ci-openshift-api-release-4.20-e2e-aws-ovn-hypershift-conformance-techpreview

Still running the MCN tests in the last iteration, lets try that again

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 25, 2025

@enxebre: The following test 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/api/release-4.20/e2e-aws-ovn-hypershift-conformance-techpreview 3fa5fb2 link unknown /pj-rehearse pull-ci-openshift-api-release-4.20-e2e-aws-ovn-hypershift-conformance-techpreview

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.

@JoelSpeed
Copy link
Copy Markdown
Contributor

MCN issues are out of the way, there's still a CSI issue, anyone familiar?

@sjenning
Copy link
Copy Markdown
Contributor

Seems that VolumeGroupSnapshottable should create snapshots for multiple volumes in a pod is still failing

  I0425 09:34:03.704083 25925 volume_group_snapshot.go:61] VolumeGroupSnapshot group-snapshot-wpv6p found but is not ready.
    [INTERRUPTED] in [It] - k8s.io/kubernetes/test/e2e/storage/testsuites/volume_group_snapshottable.go:173 @ 04/25/25 09:34:03.892
    ------------------------------
    Interrupted by User
    First interrupt received; Ginkgo will run any cleanup and reporting nodes but will skip all remaining specs.  Interrupt again to skip cleanup.
    Here's a current progress report:
      [sig-storage] OCP CSI Volumes [Driver: csi-hostpath-groupsnapshot] [OCPFeatureGate:VolumeGroupSnapshot] [Testpattern:  (delete policy)] volumegroupsnapshottable [Feature:volumegroupsnapshot] VolumeGroupSnapshottable  should create snapshots for multiple volumes in a pod (Spec Runtime: 14m59.479s)
        k8s.io/kubernetes/test/e2e/storage/testsuites/volume_group_snapshottable.go:173
        In [It] (Node Runtime: 14m59.058s)
          k8s.io/kubernetes/test/e2e/storage/testsuites/volume_group_snapshottable.go:173
          At [By Step] Waiting for group snapshot to be ready (Step Runtime: 14m33.343s)
            k8s.io/kubernetes/test/e2e/storage/framework/volume_group_snapshot_resource.go:96

@sjenning
Copy link
Copy Markdown
Contributor

@lihongan
Copy link
Copy Markdown

/pj-rehearse pull-ci-openshift-api-release-4.20-e2e-aws-ovn-hypershift-conformance-techpreview

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

@openshift-merge-robot
Copy link
Copy Markdown
Contributor

PR needs rebase.

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.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 13, 2025
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@lihongan: job(s): pull-ci-openshift-api-release-4.20-e2e-aws-ovn-hypershift-conformance-techpreview either don't exist or were not found to be affected, and cannot be rehearsed

@openshift-bot
Copy link
Copy Markdown
Contributor

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 12, 2025
@openshift-bot
Copy link
Copy Markdown
Contributor

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 27, 2025
@openshift-bot
Copy link
Copy Markdown
Contributor

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci Bot closed this Jul 12, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 12, 2025

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants