Skip to content

[release-4.17] OCPBUGS-42410: Install ansible using pip instead of rpm #21

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Oct 8, 2024
Merged

[release-4.17] OCPBUGS-42410: Install ansible using pip instead of rpm #21

merged 2 commits into from
Oct 8, 2024

Conversation

openshift-cherrypick-robot
Copy link
Contributor

This is an automated cherry-pick of #20

/assign arkadeepsen

@arkadeepsen
UPSTREAM: <carry>: Update Pipfile and Pipfile.lock for upgrading pack…
252e88d 
…ages with vulnerabilities
@arkadeepsen
UPSTREAM: <carry>: Use pip instead of rpm to build ansible-operator i…
5870a92 
…mage

Add Dockerfile.requirements for generating the requirements.txt and requirments-build.txt files from the upstream Pipfile
Add make target to generate the requirements Add make target to check if the current requirements.txt and requirements-build.txt files are up-to-date
Update Dockerfile to use cachito specific env vars for installing the python modules using pip
Remove unused shell scripts and inline the user creation script in the Dockerfile
Update base images to rhel9 in Dockerfile
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Sep 25, 2024
Merged
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 25, 2024 •
edited by openshift-ci bot
Loading

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: CFE-1124

In response to this:

This is an automated cherry-pick of #20

/assign arkadeepsen

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.

@arkadeepsen
Copy link
Member

/retest

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Sep 25, 2024

@openshift-cherrypick-robot: 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.

@arkadeepsen
Copy link
Member

/retitle [release-4.17] OCPBUGS-42410: Install ansible using pip instead of rpm

@openshift-ci openshift-ci bot changed the title [release-4.17] CFE-1124: Install ansible using pip instead of rpm [release-4.17] OCPBUGS-42410: Install ansible using pip instead of rpm Sep 25, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Sep 25, 2024
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-42410, 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.17.0) matches configured target version for branch (4.17.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-42407 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-42407 targets the "4.18.0" version, which is one of the valid target versions: 4.18.0
  • bug has dependents

Requesting review from QA contact:
/cc @KeenonLee

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

In response to this:

This is an automated cherry-pick of #20

/assign arkadeepsen

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 KeenonLee September 25, 2024 07:53
@joepvd
Copy link

joepvd commented Sep 25, 2024

/hold
Please coordinate timing of merge with Release 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 Sep 25, 2024
@TrilokGeer
Copy link
Contributor

/lgtm

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

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Oct 4, 2024
@arkadeepsen
Copy link
Member

/approve

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Oct 4, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: arkadeepsen, openshift-cherrypick-robot

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 4, 2024
@joepvd
Copy link

joepvd commented Oct 7, 2024

/unhold

@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 7, 2024
@joepvd joepvd mentioned this pull request Oct 7, 2024
Merged
KeenonLee
KeenonLee reviewed Oct 8, 2024
View reviewed changes
Copy link
Member

@KeenonLee KeenonLee left a comment

Choose a reason for hiding this comment

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

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Oct 8, 2024
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-42410, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.17.z) matches configured target version for branch (4.17.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-42407 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-42407 targets the "4.18.0" version, which is one of the valid target versions: 4.18.0
  • bug has dependents

Requesting review from QA contact:
/cc @KeenonLee

In response to this:

This is an automated cherry-pick of #20

/assign arkadeepsen

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 KeenonLee October 8, 2024 07:18
@KeenonLee
Copy link
Member

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Oct 8, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 1d4d62e into openshift:release-4.17 Oct 8, 2024
5 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-42410: All pull requests linked via external trackers have merged:

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

In response to this:

This is an automated cherry-pick of #20

/assign arkadeepsen

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

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-ansible-operator
This PR has been included in build openshift-enterprise-ansible-operator-container-v4.17.0-202410080934.p0.g1d4d62e.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

Reviewers

@arkadeepsen arkadeepsen Awaiting requested review from arkadeepsen

@chiragkyal chiragkyal Awaiting requested review from chiragkyal

@KeenonLee KeenonLee Awaiting requested review from KeenonLee

Assignees

@bandrade bandrade

@arkadeepsen arkadeepsen

@emmajiafan emmajiafan

@KeenonLee KeenonLee

@TrilokGeer TrilokGeer

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-moderate Referenced Jira bug's severity is moderate 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. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

9 participants

@openshift-cherrypick-robot @openshift-ci-robot @arkadeepsen @joepvd @TrilokGeer @KeenonLee @openshift-bot @bandrade @emmajiafan