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

Bug 2089546: [release-4.9] Eliminate use of lookaside cache and move to Cachito #11519

Merged
merged 1 commit into from May 25, 2022

Conversation

vfreex
Copy link
Contributor

@vfreex vfreex commented May 18, 2022

This is a manual cherry-pick of #11497.

Legacy Container First Pipeline will be deprecated on Jun 3, 2022. Images failing to migrate to the new source container workflow by this date will not have their sources shipped to customers and lose the compliance with legal requirements.

To move to the new source container workflow, we need to:

  • Eliminate use of distgit lookaside cache, which is not supported by the new workflow.
  • Use Cachito to track and provide npm dependencies.
  • Use fetch-artifacts-url.yaml to fetch binaries artifacts during the build.

Due to a limitation in Cachito, we also need to give a pseudo name and version to the frontend package. AFAIK the version doesn't need to be unique for every build.
I am not familiar with the code base. Let me know if the change is legitimate.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 18, 2022

@vfreex: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

Eliminate use of lookaside cache and move to Cachito - 4.9

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 added the component/sdk Related to console-plugin-sdk label May 18, 2022
@vfreex
Copy link
Contributor Author

vfreex commented May 18, 2022

Similar to #11497, but for 4.6-4.9 because node-headers is needed in those versions.

@vfreex
Copy link
Contributor Author

vfreex commented May 18, 2022

/cherry-pick release-4.8
/cherry-pick release-4.7
/cherry-pick release-4.6

@openshift-cherrypick-robot

@vfreex: once the present PR merges, I will cherry-pick it on top of release-4.8 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.8
/cherry-pick release-4.7
/cherry-pick release-4.6

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.

@vfreex
Copy link
Contributor Author

vfreex commented May 18, 2022

[Legacy Container First Pipeline][1] will be deprecated on Jun 3, 2022. Images failing to migrate to the new source container workflow by this date will not have their sources shipped to customers and lose the compliance with legal requirements.

To move to the new source container workflow, we need to:
- Eliminate use of distgit lookaside cache, which is not supported by the new workflow.
- Use [Cachito][2] to track and provide npm dependencies.
- Use [fetch-artifacts-url.yaml][3] to fetch binaries artifacts during the build.

Due to a limitation in Cachito, we also need to give a pseudo name and version to the frontend package. AFAIK the version doesn't need to be unique for every build.
I am not familiar with the code base. Let me know if the change is legitimate.

[1]: https://docs.engineering.redhat.com/display/SP/Decommission+of+Legacy+Container+First+Pipeline
[2]: https://github.com/containerbuildsystem/cachito
[3]: https://osbs.readthedocs.io/en/osbs_ocp3/users.html#fetch-artifacts-url-yaml
@vfreex vfreex changed the title Eliminate use of lookaside cache and move to Cachito - 4.9 [release-4.9] Eliminate use of lookaside cache and move to Cachito May 19, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 19, 2022

@vfreex: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.9] Eliminate use of lookaside cache and move to Cachito

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.

@vfreex
Copy link
Contributor Author

vfreex commented May 19, 2022

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 19, 2022

@vfreex: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.9] Eliminate use of lookaside cache and move to Cachito

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

openshift-ci bot commented May 19, 2022

@vfreex: all tests passed!

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

@vfreex: once the present PR merges, I will cherry-pick it on top of release-4.7 release-4.6 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.7 release-4.6

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.

@vfreex
Copy link
Contributor Author

vfreex commented May 19, 2022

/cherry-pick release-4.7

@openshift-cherrypick-robot

@vfreex: once the present PR merges, I will cherry-pick it on top of release-4.7 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.7

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.

@vfreex
Copy link
Contributor Author

vfreex commented May 19, 2022

/cherry-pick release-4.6

@openshift-cherrypick-robot

@vfreex: once the present PR merges, I will cherry-pick it on top of release-4.6 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.6

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.

@vfreex vfreex changed the title [release-4.9] Eliminate use of lookaside cache and move to Cachito Bug 2089546: [release-4.9] Eliminate use of lookaside cache and move to Cachito May 24, 2022
@openshift-ci openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels May 24, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 24, 2022

@vfreex: This pull request references Bugzilla bug 2089546, which is invalid:

  • expected dependent Bugzilla bug 2088304 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
  • expected dependent Bugzilla bug 2089547 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
  • expected dependent Bugzilla bug 2088304 to target a release in 4.10.0, 4.10.z, but it targets "4.11.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 2089546: [release-4.9] Eliminate use of lookaside cache and move to Cachito

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.

@vfreex
Copy link
Contributor Author

vfreex commented May 24, 2022

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 24, 2022

@vfreex: This pull request references Bugzilla bug 2089546, which is invalid:

  • expected dependent Bugzilla bug 2088304 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
  • expected dependent Bugzilla bug 2089547 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
  • expected dependent Bugzilla bug 2088304 to target a release in 4.10.0, 4.10.z, but it targets "4.11.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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.

@jupierce jupierce added approved Indicates a PR has been approved by an approver from all required OWNERS files. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels May 24, 2022
@jupierce
Copy link
Contributor

This change was approved by Sam for 4.11, so I'm helping it along to unblock ART.

@jupierce
Copy link
Contributor

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 24, 2022

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: jupierce, vfreex

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 lgtm Indicates that a PR is ready to be merged. label May 24, 2022
@vfreex
Copy link
Contributor Author

vfreex commented May 25, 2022

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 25, 2022

@vfreex: This pull request references Bugzilla bug 2089546, which is invalid:

  • expected dependent Bugzilla bug 2089547 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 25, 2022

@openshift-bot: This pull request references Bugzilla bug 2089546, which is invalid:

  • expected dependent Bugzilla bug 2089547 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

@vfreex
Copy link
Contributor Author

vfreex commented May 25, 2022

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 25, 2022

@vfreex: This pull request references Bugzilla bug 2089546, which is invalid:

  • expected dependent Bugzilla bug 2089547 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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.

@jupierce
Copy link
Contributor

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 25, 2022

@jupierce: This pull request references Bugzilla bug 2089546, which is invalid:

  • expected dependent Bugzilla bug 2089547 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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.

@jupierce jupierce added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels May 25, 2022
@jupierce
Copy link
Contributor

These are non functional changes and must merge as soon as we can get them in for compliance reasons. Overriding valid bug.

@openshift-merge-robot openshift-merge-robot merged commit c28f128 into openshift:release-4.9 May 25, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 25, 2022

@vfreex: All pull requests linked via external trackers have merged:

Bugzilla bug 2089546 has been moved to the MODIFIED state.

In response to this:

Bug 2089546: [release-4.9] Eliminate use of lookaside cache and move to Cachito

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

@vfreex: new pull request created: #11573

In response to this:

/cherry-pick release-4.8
/cherry-pick release-4.7
/cherry-pick release-4.6

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

@vfreex: new pull request created: #11574

In response to this:

/cherry-pick release-4.7

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

@vfreex: #11519 failed to apply on top of branch "release-4.6":

Applying: Eliminate use of lookaside cache and move to Cachito
Using index info to reconstruct a base tree...
M	Dockerfile.product
M	frontend/package.json
M	frontend/packages/console-plugin-sdk/src/codegen/plugin-resolver.ts
Falling back to patching base and 3-way merge...
Auto-merging frontend/packages/console-plugin-sdk/src/codegen/plugin-resolver.ts
Auto-merging frontend/package.json
Auto-merging Dockerfile.product
CONFLICT (content): Merge conflict in Dockerfile.product
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Eliminate use of lookaside cache and move to Cachito
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.6

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/severity-high Referenced Bugzilla bug's severity is high 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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. component/sdk Related to console-plugin-sdk lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants