Skip to content

Conversation

@lobziik
Copy link
Contributor

@lobziik lobziik commented Oct 24, 2022

Add possibility to specify release branch for clone mapi e2e test suite.
In case of openshift ci, PR target branch will be using as e2e release branch, which is more correct behaviour.

This need to be backported, will create a bug after initial review.

Add possibility to specify release branch for clone
mapi e2e test suite.
In case of openshift ci, PR target branch will be using
as e2e release branch, which is more correct behaviour.
@openshift-ci openshift-ci bot requested review from Fedosin and JoelSpeed October 24, 2022 14:24
Copy link
Contributor

@JoelSpeed JoelSpeed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

Comment on lines +5 to +6
OPENSHIFT_CI=${OPENSHIFT_CI:-""}
E2E_RELEASE_BRANCH=${E2E_RELEASE_BRANCH:-""}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit, I think the following has the same result

Suggested change
OPENSHIFT_CI=${OPENSHIFT_CI:-""}
E2E_RELEASE_BRANCH=${E2E_RELEASE_BRANCH:-""}
OPENSHIFT_CI=${OPENSHIFT_CI:-}
E2E_RELEASE_BRANCH=${E2E_RELEASE_BRANCH:-}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer to leave it as is, to be honest. Feels more explicit to me and we have the same pattern in other places.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

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:

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 Oct 24, 2022
@lobziik lobziik changed the title Update e2e runner script OCPBUGS-2798: Update e2e runner script Oct 24, 2022
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Oct 24, 2022
@openshift-ci-robot
Copy link
Contributor

@lobziik: This pull request references Jira Issue OCPBUGS-2798, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.12.0) matches configured target version for branch (4.12.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sunzhaohua2

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Add possibility to specify release branch for clone mapi e2e test suite.
In case of openshift ci, PR target branch will be using as e2e release branch, which is more correct behaviour.

This need to be backported, will create a bug after initial review.

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 openshift-ci bot requested a review from sunzhaohua2 October 24, 2022 14:51
@lobziik
Copy link
Contributor Author

lobziik commented Oct 24, 2022

/hold

This does work differently as I thought
https://github.com/openshift/release/blob/62ffd80f52efdde7b6ff90e76fa630c96eec6ca8/ci-operator/config/openshift/machine-api-operator/openshift-machine-api-operator-master.yaml#L83

Only vsphere-operator job is broken now.

Hold till it would be discussed with the team

@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 Oct 24, 2022
@lobziik
Copy link
Contributor Author

lobziik commented Oct 24, 2022

I figured out that only vsphere jobs uses cluster-api-actuator-pkg from the repo. Other jobs uses prebuilt image. Opened openshift/release#33400 to fix this, if it would help. This pr might be closed along with the bug.

@lobziik lobziik changed the title OCPBUGS-2798: Update e2e runner script Update e2e runner script Oct 25, 2022
@lobziik
Copy link
Contributor Author

lobziik commented Oct 25, 2022

I think it still might be useful to merge, despite that original problem was solved another way.

removing bug from this. It can wait till branch will open.

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 25, 2022
@lobziik
Copy link
Contributor Author

lobziik commented Oct 25, 2022

/jira refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 30, 2022

@lobziik: 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-libvirt 10377d6 link false /test e2e-libvirt
ci/prow/e2e-nutanix 10377d6 link false /test e2e-nutanix
ci/prow/e2e-metal-ipi-ovn-ipv6 10377d6 link false /test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-azure-operator 10377d6 link false /test e2e-azure-operator
ci/prow/e2e-gcp-operator 10377d6 link false /test e2e-gcp-operator
ci/prow/e2e-vsphere-upgrade 10377d6 link false /test e2e-vsphere-upgrade
ci/prow/e2e-vsphere-operator 10377d6 link false /test e2e-vsphere-operator
ci/prow/e2e-metal-ipi-sdn 10377d6 link false /test e2e-metal-ipi-sdn
ci/prow/e2e-metal-ipi-virtualmedia 10377d6 link false /test e2e-metal-ipi-virtualmedia
ci/prow/e2e-metal-ipi-ovn-dualstack 10377d6 link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-vsphere-serial 10377d6 link true /test e2e-vsphere-serial
ci/prow/e2e-openstack 10377d6 link false /test e2e-openstack
ci/prow/e2e-metal-ipi-upgrade 10377d6 link false /test e2e-metal-ipi-upgrade
ci/prow/e2e-vsphere-ovn-serial 10377d6 link true /test e2e-vsphere-ovn-serial
ci/prow/e2e-aws-operator 10377d6 link true /test e2e-aws-operator

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

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d 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 Mar 1, 2023
@lobziik
Copy link
Contributor Author

lobziik commented Mar 3, 2023

/close

@openshift-ci openshift-ci bot closed this Mar 3, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2023

@lobziik: Closed this PR.

In response to this:

/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/test-infra 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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants