Skip to content

OCPBUGS-36363: Install yq manually if not found in installer image#53838

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
Shilpa-Gokul:add-yq
Jul 4, 2024
Merged

OCPBUGS-36363: Install yq manually if not found in installer image#53838
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
Shilpa-Gokul:add-yq

Conversation

@Shilpa-Gokul
Copy link
Copy Markdown
Contributor

Added code to install yq manually until yq-v4 package is backported to the 4.14 installer code.

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

@Shilpa-Gokul: This pull request references Jira Issue OCPBUGS-36363, which is invalid:

  • expected the bug to target either version "4.17." or "openshift-4.17.", but it targets "4.14.z" instead

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.

Details

In response to this:

Added code to install yq manually until yq-v4 package is backported to the 4.14 installer code.

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-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jul 1, 2024
@Shilpa-Gokul
Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@Shilpa-Gokul: This pull request references Jira Issue OCPBUGS-36363, which is invalid:

  • expected the bug to target only the "4.17.0" version, but multiple target versions were set

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.

Details

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.

@Shilpa-Gokul
Copy link
Copy Markdown
Contributor 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 Jul 1, 2024
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@Shilpa-Gokul: This pull request references Jira Issue OCPBUGS-36363, 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.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)

Requesting review from QA contact:
/cc @juliemathew

Details

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 juliemathew July 1, 2024 08:22
@Shilpa-Gokul
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-ovn-ppc64le-powervs

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@Shilpa-Gokul: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci openshift-ci Bot requested review from clnperez and jaypoulz July 1, 2024 08:22
@Shilpa-Gokul Shilpa-Gokul changed the title OCPBUGS-36363: Install yq manually if not found in installer image [WIP]: OCPBUGS-36363: Install yq manually if not found in installer image Jul 1, 2024
@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 Jul 1, 2024
@Shilpa-Gokul
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-multiarch-master-nightly-4.15-ocp-e2e-ovn-ppc64le-powervs-original

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@Shilpa-Gokul: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@Shilpa-Gokul
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-ovn-ppc64le-powervs

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@Shilpa-Gokul: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@Shilpa-Gokul
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-ovn-ppc64le-powervs

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@Shilpa-Gokul: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@Shilpa-Gokul
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-ovn-ppc64le-powervs

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@Shilpa-Gokul: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@Shilpa-Gokul
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-ovn-ppc64le-powervs

@Shilpa-Gokul Shilpa-Gokul changed the title [WIP]: OCPBUGS-36363: Install yq manually if not found in installer image OCPBUGS-36363: Install yq manually if not found in installer image Jul 2, 2024
@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 Jul 2, 2024
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 2, 2024
@tvardema
Copy link
Copy Markdown
Contributor

tvardema commented Jul 2, 2024

/approve

@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 2, 2024
@Shilpa-Gokul
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-ovn-ppc64le-powervs

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@Shilpa-Gokul: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot removed the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jul 2, 2024
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@Shilpa-Gokul: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-installer-master-altinfra-e2e-powervs-capi-ovn openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.18-altinfra-e2e-powervs-capi-ovn openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.17-altinfra-e2e-powervs-capi-ovn openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.16-altinfra-e2e-powervs-capi-ovn openshift/installer presubmit Registry content changed
periodic-ci-openshift-openshift-tests-private-release-4.15-ppc64le-nightly-powervs-ipi-f7 N/A periodic Registry content changed
periodic-ci-openshift-multiarch-master-nightly-4.16-ocp-e2e-ovn-ppc64le-powervs-original N/A periodic Registry content changed
periodic-ci-openshift-release-master-ci-4.16-e2e-powervs-ovn-techpreview N/A periodic Registry content changed
periodic-ci-openshift-multiarch-master-nightly-4.15-ocp-e2e-ovn-ppc64le-powervs-original N/A periodic Registry content changed
periodic-ci-openshift-openshift-tests-private-release-4.16-ppc64le-nightly-powervs-ipi-f7 N/A periodic Registry content changed
periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-serial-ovn-ppc64le-powervs N/A periodic Registry content changed
periodic-ci-openshift-multiarch-master-nightly-4.17-ocp-e2e-ovn-ppc64le-powervs-capi N/A periodic Registry content changed
periodic-ci-openshift-openshift-tests-private-release-4.15-ppc64le-nightly-powervs-ipi-f7-destructive N/A periodic Registry content changed
periodic-ci-openshift-openshift-tests-private-release-4.16-ppc64le-nightly-powervs-ipi-f7-destructive N/A periodic Registry content changed
periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-ovn-ppc64le-powervs N/A periodic Registry content changed
periodic-ci-openshift-multiarch-master-nightly-4.13-ocp-e2e-ovn-ppc64le-powervs N/A periodic Registry content changed
periodic-ci-openshift-multiarch-master-nightly-4.13-ocp-e2e-serial-ovn-ppc64le-powervs N/A periodic Registry content changed
periodic-ci-openshift-multiarch-master-nightly-4.17-ocp-e2e-ovn-ppc64le-powervs-original N/A periodic Registry content changed
periodic-ci-openshift-release-master-nightly-4.16-e2e-powervs-ovn-techpreview N/A periodic Registry content changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@tvardema
Copy link
Copy Markdown
Contributor

tvardema commented Jul 2, 2024

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 2, 2024
@Shilpa-Gokul
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-ovn-ppc64le-powervs

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@Shilpa-Gokul: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

1 similar comment
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@Shilpa-Gokul: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@Shilpa-Gokul
Copy link
Copy Markdown
Contributor Author

/pj-rehearse ack

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@Shilpa-Gokul: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jul 4, 2024
Copy link
Copy Markdown
Contributor

@r4f4 r4f4 left a comment

Choose a reason for hiding this comment

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

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 4, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: r4f4, Shilpa-Gokul, tvardema

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 Jul 4, 2024
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 4, 2024

@Shilpa-Gokul: The following test 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/rehearse/periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-ovn-ppc64le-powervs 203eff7 link unknown /pj-rehearse periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-ovn-ppc64le-powervs

Full PR test history. Your PR dashboard.

Details

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 2aa3f0f into openshift:master Jul 4, 2024
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@Shilpa-Gokul: Jira Issue OCPBUGS-36363: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

Details

In response to this:

Added code to install yq manually until yq-v4 package is backported to the 4.14 installer code.

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.

aviavraham pushed a commit to aviavraham/openshift_release that referenced this pull request Jul 5, 2024
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-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. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants