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

[release-4.18] OCPBUGS-49833: Backport extensions/Dockerfile: Get extensions rpm list #1732

Merged

Conversation

ravanelli
Copy link
Member

  • Generate JSON file listing installed extension packages;
  • Use dnf repoquery to list 'name: version,' for each RPM and generates a JSON file at /tmp/extensions.json. Where the build volume is mounted;
  • It is needed to generated the extensions package list in meta.json.

Signed-off-by: Renata Ravanelli [email protected]
(cherry picked from commit 128a6b9)

 - Generate JSON file listing installed extension packages;
 - Use dnf repoquery to list 'name: version,' for each RPM
and generates a JSON file at `/tmp/extensions.json`. Where the
build volume is mounted;
 - It is needed to generated the extensions package list in meta.json.

Signed-off-by: Renata Ravanelli <[email protected]>
(cherry picked from commit 128a6b9)
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 31, 2025
@dustymabe
Copy link
Member

/retest

Copy link
Contributor

openshift-ci bot commented Feb 1, 2025

@ravanelli: 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-sigs/prow repository. I understand the commands that are listed here.

@mike-nguyen
Copy link
Member

/label backport-risk-assessed
/label cherry-pick-approved
/lgtm

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. labels Feb 4, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 4, 2025
Copy link
Contributor

openshift-ci bot commented Feb 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mike-nguyen, ravanelli

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 [mike-nguyen,ravanelli]

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

@ravanelli ravanelli changed the title [release-4.18] Backport extensions/Dockerfile: Get extensions rpm list [release-4.18] OCPBUGS-49833 Backport extensions/Dockerfile: Get extensions rpm list Feb 4, 2025
@ravanelli ravanelli changed the title [release-4.18] OCPBUGS-49833 Backport extensions/Dockerfile: Get extensions rpm list [release-4.18] OCPBUGS-49833: Backport extensions/Dockerfile: Get extensions rpm list Feb 4, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 4, 2025
@openshift-ci-robot
Copy link

@ravanelli: This pull request references Jira Issue OCPBUGS-49833, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

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

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

In response to this:

  • Generate JSON file listing installed extension packages;
  • Use dnf repoquery to list 'name: version,' for each RPM and generates a JSON file at /tmp/extensions.json. Where the build volume is mounted;
  • It is needed to generated the extensions package list in meta.json.

Signed-off-by: Renata Ravanelli [email protected]
(cherry picked from commit 128a6b9)

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.

@ravanelli
Copy link
Member Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 4, 2025
@openshift-ci-robot
Copy link

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-49831 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-49831 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
  • bug has dependents

Requesting review from QA contact:
/cc @mike-nguyen

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from mike-nguyen February 4, 2025 15:43
@openshift-merge-bot openshift-merge-bot bot merged commit 2b39864 into openshift:release-4.18 Feb 4, 2025
5 checks passed
@openshift-ci-robot
Copy link

@ravanelli: Jira Issue OCPBUGS-49833: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-49833 has been moved to the MODIFIED state.

In response to this:

  • Generate JSON file listing installed extension packages;
  • Use dnf repoquery to list 'name: version,' for each RPM and generates a JSON file at /tmp/extensions.json. Where the build volume is mounted;
  • It is needed to generated the extensions package list in meta.json.

Signed-off-by: Renata Ravanelli [email protected]
(cherry picked from commit 128a6b9)

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.

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-low Referenced Jira bug's severity is low 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. 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