Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MCO-1470: Incorporates upstream devex helper changes for OCL testing #4753

Conversation

cheesesashimi
Copy link
Member

@cheesesashimi cheesesashimi commented Dec 12, 2024

- What I did

This takes @dkhater-redhat's work in #4718 and incorporates changes I had to make to my helpers repository in order to make the tests pass for openshift/release#58241.

This also repackages the helpers slightly into a devex/ folder in the MCO repo's root and removes a few of the hack/ scripts that the devex/ helpers replace.

This is intended to land after #4718 does.

- How to verify it

The unit test suite provides some test coverage for the devex helpers. Additionally, the verify target will compile the helpers in CI as a smoke test.

- Description for the changelog
Incorporates upstream devex helper changes for OCL testing

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 12, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 12, 2024

@cheesesashimi: This pull request references MCO-1470 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.19.0" version, but no target version was set.

In response to this:

- What I did

This takes @dkhater-redhat's work in #4718 and incorporates changes I had to make to my helpers repository in order to make the tests pass for openshift/release#58241.

This also repackages the helpers slightly into a devex/ folder in the MCO repo's root and removes a few of the hack/ scripts that the devex/ helpers replace.

- How to verify it

The unit test suite provides some test coverage for the devex helpers. Additionally, the verify target will compile the helpers in CI as a smoke test.

- Description for the changelog
Incorporates upstream devex helper changes for OCL testing

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 openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 12, 2024
Copy link
Contributor

openshift-ci bot commented Dec 12, 2024

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 12, 2024
@cheesesashimi cheesesashimi changed the title MCO-1470: incorporates upstream changes to helpers MCO-1470: Incorporates upstream devex helper changes for OCL testing Dec 12, 2024
@cheesesashimi
Copy link
Member Author

/test verify
/test unit

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 12, 2024

@cheesesashimi: This pull request references MCO-1470 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.19.0" version, but no target version was set.

In response to this:

- What I did

This takes @dkhater-redhat's work in #4718 and incorporates changes I had to make to my helpers repository in order to make the tests pass for openshift/release#58241.

This also repackages the helpers slightly into a devex/ folder in the MCO repo's root and removes a few of the hack/ scripts that the devex/ helpers replace.

This is intended to land after #4718 does.

- How to verify it

The unit test suite provides some test coverage for the devex helpers. Additionally, the verify target will compile the helpers in CI as a smoke test.

- Description for the changelog
Incorporates upstream devex helper changes for OCL testing

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.

@cheesesashimi
Copy link
Member Author

/test verify
/test unit

1 similar comment
@cheesesashimi
Copy link
Member Author

/test verify
/test unit

@cheesesashimi cheesesashimi force-pushed the zzlotnik/incorporate-changes-to-helpers branch from 307e622 to 0a62de0 Compare December 13, 2024 15:11
@cheesesashimi
Copy link
Member Author

/test verify
/test unit

@cheesesashimi cheesesashimi force-pushed the zzlotnik/incorporate-changes-to-helpers branch from 0a62de0 to 2b3b340 Compare December 13, 2024 17:46
@cheesesashimi
Copy link
Member Author

/test verify
/test unit

@cheesesashimi cheesesashimi marked this pull request as ready for review December 13, 2024 18:37
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 13, 2024
Copy link
Contributor

@dkhater-redhat dkhater-redhat left a comment

Choose a reason for hiding this comment

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

looks good to me. I just had a question about devex containerfile maintenance, but nothing that needs to be edited. nice job with the retry stuff for MCP completion.

@@ -0,0 +1,11 @@
FROM registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.22-builder-multi-openshift-4.18 AS builder
Copy link
Contributor

Choose a reason for hiding this comment

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

question: is this something we are going to manually update every release?

Copy link
Member Author

@cheesesashimi cheesesashimi Dec 13, 2024

Choose a reason for hiding this comment

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

For now, probably. The good news is that for the CI use-case, the CI system should keep that up-to-date for us and we're not depending on anything else being in the image (aside from oc, which the CI system will inject for us anyway).

It's also worth mentioning that I intend for this Containerfile to only be used by CI for right now. For the average MCO developers' use-case, one can use the make install-helpers command to build / install the helpers. That said, I still want to have a way to produce prebuilt versions of these binaries as well as container images. That's a separate concern for right now, in my opinion.

Copy link
Member Author

Choose a reason for hiding this comment

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

Another solution is that we could replace these with fedora:latest or whatever since all we really need is a Golang toolchain. I only chose the OCP builder image because I knew it has everything we need.

@@ -97,6 +101,20 @@ func WaitForAllMachineConfigPoolsToComplete(cs *framework.ClientSet, timeout tim
return err
}

// Waits for the MachineConfigPool to complete. This does not consider
Copy link
Contributor

Choose a reason for hiding this comment

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

nice!

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks! A lot of the code that these specific helpers use was either written for our e2e test suite -or- was written here and then used in our e2e test suite. There's the potential for some future deduplication here.

@dkhater-redhat
Copy link
Contributor

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 13, 2024
Copy link
Contributor

openshift-ci bot commented Dec 13, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cheesesashimi, dkhater-redhat

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:
  • OWNERS [cheesesashimi,dkhater-redhat]

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

/retest-required

Remaining retests: 0 against base HEAD 4c5faab and 2 for PR HEAD 2b3b340 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD cd22882 and 1 for PR HEAD 2b3b340 in total

Copy link
Contributor

openshift-ci bot commented Dec 14, 2024

@cheesesashimi: 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 2b3b340 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-azure-ovn-upgrade-out-of-change 2b3b340 link false /test e2e-azure-ovn-upgrade-out-of-change

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-merge-bot openshift-merge-bot bot merged commit 36e2d57 into openshift:master Dec 14, 2024
18 of 20 checks passed
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-machine-config-operator
This PR has been included in build ose-machine-config-operator-container-v4.19.0-202412140855.p0.g36e2d57.assembly.stream.el9.
All builds following this will include this PR.

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants