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

opentelemetry-collector/0.115.0 package update #35785

Merged
merged 1 commit into from
Dec 8, 2024

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Dec 4, 2024

@octo-sts octo-sts bot added request-version-update request for a newer version of a package automated pr P1 This label indicates our scanning found High, Medium or Low CVEs for these packages. labels Dec 4, 2024
Copy link
Contributor Author

octo-sts bot commented Dec 4, 2024

Gen AI suggestions to solve the build error:

• Detected Error: The build appears to complete downloading dependencies but fails silently after "Sources created"

• Error Category: Build Configuration

• Failure Point: During the execution of the OpenTelemetry Collector Builder (ocb) with builder-config.yaml

• Root Cause Analysis: The curl command is only retrieving 14 bytes for the builder-config.yaml file, suggesting the manifest file URL is not returning the expected content. The builder then fails because it doesn't have proper configuration.

• Suggested Fix:

  1. Modify the pipeline step to use the correct manifest URL:
  - runs: |
      set -x
      curl -L -o builder-config.yaml https://raw.githubusercontent.com/open-telemetry/opentelemetry-collector-releases/main/distributions/otelcol/manifest.yaml

Or alternatively, embed the manifest directly in the melange.yaml:

  - runs: |
      set -x
      cat > builder-config.yaml <<EOF
dist:
  name: otelcol
  description: Local OpenTelemetry Collector
  output_path: ./_build
  otelcol_version: 0.115.0
EOF

• Explanation:

  • The current URL pattern with v0.115.0 isn't returning the full manifest file
  • The manifest file is essential for the builder to know which components to include
  • Either using the main branch manifest or providing a minimal configuration should allow the build to proceed

• Additional Notes:

  • The builder requires a valid manifest file to determine which components to include in the build
  • The minimal configuration provided will build a basic collector with default components
  • You may want to customize the manifest further based on which components you need

• References:

@mamccorm mamccorm force-pushed the wolfictl-bbad36a0-4516-40a3-957b-21d144a14a10 branch from 3dbe026 to 0318cae Compare December 8, 2024 17:41
@octo-sts octo-sts bot added the bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. label Dec 8, 2024
@mamccorm mamccorm self-assigned this Dec 8, 2024
@mamccorm mamccorm merged commit 0955264 into main Dec 8, 2024
15 checks passed
@mamccorm mamccorm deleted the wolfictl-bbad36a0-4516-40a3-957b-21d144a14a10 branch December 8, 2024 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated pr bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. P1 This label indicates our scanning found High, Medium or Low CVEs for these packages. request-version-update request for a newer version of a package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants