Skip to content

[release-4.14] OCPBUGS-66112: BuildConfig inline Dockerfile fails with heredoc syntax#492

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.14from
openshift-cherrypick-robot:cherry-pick-491-to-release-4.14
Dec 19, 2025
Merged

[release-4.14] OCPBUGS-66112: BuildConfig inline Dockerfile fails with heredoc syntax#492
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.14from
openshift-cherrypick-robot:cherry-pick-491-to-release-4.14

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #491

/assign openshift-cherrypick-robot

When writing out the contents of a parsed Dockerfile, attempt to
reproduce heredocs that followed instructions.

Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-65960 has been cloned as Jira Issue OCPBUGS-66112. Will retitle bug to link to clone.
/retitle [release-4.14] OCPBUGS-66112: BuildConfig inline Dockerfile fails with heredoc syntax

Details

In response to this:

This is an automated cherry-pick of #491

/assign openshift-cherrypick-robot

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 changed the title [release-4.14] OCPBUGS-65960: BuildConfig inline Dockerfile fails with heredoc syntax [release-4.14] OCPBUGS-66112: BuildConfig inline Dockerfile fails with heredoc syntax Nov 27, 2025
@openshift-ci-robot openshift-ci-robot added 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 Nov 27, 2025
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-66112, which is invalid:

  • expected dependent Jira Issue OCPBUGS-65960 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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:

This is an automated cherry-pick of #491

/assign openshift-cherrypick-robot

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.

@kunalmemane
Copy link
Copy Markdown
Member

/test e2e-aws-ovn-image-ecosystem

@kunalmemane
Copy link
Copy Markdown
Member

/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 Dec 1, 2025
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@kunalmemane: This pull request references Jira Issue OCPBUGS-66112, 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.14.z) matches configured target version for branch (4.14.z)
  • 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-65960 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-65960 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
  • bug has dependents

Requesting review from QA contact:
/cc @moebasim

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 moebasim December 1, 2025 05:27
@kunalmemane
Copy link
Copy Markdown
Member

/test e2e-aws-ovn-image-ecosystem

@moebasim
Copy link
Copy Markdown
Contributor

moebasim commented Dec 1, 2025

/verified by @moebasim

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Dec 1, 2025
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@moebasim: This PR has been marked as verified by @Moebasim.

Details

In response to this:

/verified by @moebasim

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.

@kunalmemane
Copy link
Copy Markdown
Member

/test e2e-aws-ovn-image-ecosystem

@prabhapa
Copy link
Copy Markdown
Contributor

prabhapa commented Dec 2, 2025

/compliance:analyze-cve CVE-2025-22869

@kunalmemane
Copy link
Copy Markdown
Member

/test e2e-aws-ovn-image-ecosystem

4 similar comments
@moebasim
Copy link
Copy Markdown
Contributor

moebasim commented Dec 5, 2025

/test e2e-aws-ovn-image-ecosystem

@kunalmemane
Copy link
Copy Markdown
Member

/test e2e-aws-ovn-image-ecosystem

@kunalmemane
Copy link
Copy Markdown
Member

/test e2e-aws-ovn-image-ecosystem

@kunalmemane
Copy link
Copy Markdown
Member

/test e2e-aws-ovn-image-ecosystem

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Dec 18, 2025

@openshift-cherrypick-robot: 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/prow/security fb480a1 link false /test security

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.

@kunalmemane
Copy link
Copy Markdown
Member

/test e2e-aws-ovn-image-ecosystem

@prabhapa
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Dec 19, 2025
@prabhapa
Copy link
Copy Markdown
Contributor

/label backport-risk-assessed

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Dec 19, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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 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. labels Dec 19, 2025
@openshift-merge-bot openshift-merge-bot Bot merged commit 57539b8 into openshift:release-4.14 Dec 19, 2025
7 of 8 checks passed
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-66112
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-66112 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

This is an automated cherry-pick of #491

/assign openshift-cherrypick-robot

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-merge-robot
Copy link
Copy Markdown
Contributor

Fix included in accepted release 4.14.0-0.nightly-2025-12-19-150811

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. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants