Skip to content

Conversation

nalind
Copy link
Member

@nalind nalind commented Apr 3, 2025

When writing out the contents of a parsed Dockerfile, attempt to reproduce the heredocs that followed instructions. Originally encountered by @jlebon while working on openshift/os#1780.

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

Signed-off-by: Nalin Dahyabhai <[email protected]>
@openshift-ci openshift-ci bot requested review from Moebasim and divyansh42 April 3, 2025 17:37
@nalind
Copy link
Member Author

nalind commented Apr 3, 2025

Heredocs were first recognized in buildah 1.33, so I expect that this is applicable to release-4.14 and all later branches.

@nalind
Copy link
Member Author

nalind commented Apr 3, 2025

/retest

jlebon added a commit to jlebon/os that referenced this pull request Apr 4, 2025
The OCP builder API path isn't parsing the heredoc correctly for some
reason:

     error: build error: EOF: unterminated heredoc

This will be fixed by openshift/builder#469.

Anyway, just work around this for now by moving all the logic to
scripts. It does make the Containerfiles cleaner at least now that it
has gotten so larger and we get syntax highlighting, ShellCheck, etc...
so probably for the best.
@GingerGeek
Copy link

We have also been observing this issue within OKD community as well, would appreciate the fix being merged

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 30, 2025
@nalind
Copy link
Member Author

nalind commented Sep 2, 2025

/lifecycle frozen

Copy link
Contributor

openshift-ci bot commented Sep 2, 2025

@nalind: The lifecycle/frozen label cannot be applied to Pull Requests.

In response to this:

/lifecycle frozen

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.

@nalind
Copy link
Member Author

nalind commented Sep 2, 2025

But you said!

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 2, 2025
@kunalmemane
Copy link
Contributor

/retest

@kunalmemane
Copy link
Contributor

/retitle OCPBUGS-62210: BuildConfig inline Dockerfile fails with heredoc syntax

@openshift-ci openshift-ci bot changed the title pkg/build/builder/util/dockerfile.Write: reproduce heredocs OCPBUGS-62210: BuildConfig inline Dockerfile fails with heredoc syntax Oct 10, 2025
@openshift-ci-robot openshift-ci-robot added 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 Oct 10, 2025
@openshift-ci-robot
Copy link
Contributor

@nalind: This pull request references Jira Issue OCPBUGS-62210, 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.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @Moebasim

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

In response to this:

When writing out the contents of a parsed Dockerfile, attempt to reproduce the heredocs that followed instructions. Originally encountered by @jlebon while working on openshift/os#1780.

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.

Copy link
Contributor

openshift-ci bot commented Oct 10, 2025

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: Moebasim.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

@nalind: This pull request references Jira Issue OCPBUGS-62210, 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.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @Moebasim

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

In response to this:

When writing out the contents of a parsed Dockerfile, attempt to reproduce the heredocs that followed instructions. Originally encountered by @jlebon while working on openshift/os#1780.

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.

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.

@Moebasim
Copy link
Contributor

/lgtm

Copy link
Contributor

openshift-ci bot commented Oct 10, 2025

@Moebasim: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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.

@Moebasim
Copy link
Contributor

/label docs-approved
/label px-approved

@openshift-ci openshift-ci bot added docs-approved Signifies that Docs has signed off on this PR px-approved Signifies that Product Support has signed off on this PR labels Oct 10, 2025
@Moebasim
Copy link
Contributor

/lgtm

Copy link
Contributor

openshift-ci bot commented Oct 10, 2025

@Moebasim: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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.

@prabhapa
Copy link
Contributor

/lgtm

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

openshift-ci bot commented Oct 13, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Moebasim, nalind, prabhapa

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 13, 2025
@kunalmemane
Copy link
Contributor

/verified by @kunalmemane

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

@kunalmemane: This PR has been marked as verified by @kunalmemane.

In response to this:

/verified by @kunalmemane

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

/retest-required

Remaining retests: 0 against base HEAD ff595e4 and 2 for PR HEAD bf50699 in total

@kunalmemane
Copy link
Contributor

/test e2e-aws-ovn-image-ecosystem

@nalind
Copy link
Member Author

nalind commented Oct 14, 2025

That e2e-aws-ovn-image-ecosystem test should be fixed by openshift/origin#30376.

@kunalmemane
Copy link
Contributor

/test e2e-aws-ovn-image-ecosystem

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 9ed70da and 1 for PR HEAD bf50699 in total

Copy link
Contributor

openshift-ci bot commented Oct 17, 2025

@nalind: The following tests 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 bf50699 link false /test security
ci/prow/e2e-aws-ovn-image-ecosystem bf50699 link true /test e2e-aws-ovn-image-ecosystem

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.

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. docs-approved Signifies that Docs has signed off on this PR 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. px-approved Signifies that Product Support has signed off on this PR 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