Skip to content

opentelemetry-collector/0.123.0 package update #48690

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

Merged
merged 2 commits into from
Apr 1, 2025

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Mar 31, 2025

@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 Mar 31, 2025
Copy link
Contributor Author

octo-sts bot commented Mar 31, 2025

⚠️ EXPERIMENTAL

Please use 👍 or 👎 on this comment to indicate if you agree or disagree with the recommendation.

To provide more detailed feedback please comment on the recommendation prefixed with /ai-verify:

e.g. /ai-verify partially helpful but I also added bash to the build environment

Gen AI suggestions to solve the build error:

• Detected Error:

curl: (22) The requested URL returned error: 404

• Error Category: Build Configuration

• Failure Point:
Initial pipeline step attempting to download manifest.yaml from opentelemetry-collector-releases repository

• Root Cause Analysis:
The build is failing because it cannot find the manifest file at the specified URL. This is likely because the repository structure has changed or the version-specific path is incorrect.

• Suggested Fix:

  1. Check the correct manifest URL in the opentelemetry-collector-releases repository:
pipeline:
  - runs: |
      set -x
      # Update to use the correct manifest path
      curl --fail -o builder-config.yaml https://raw.githubusercontent.com/open-telemetry/opentelemetry-collector-releases/main/distributions/otelcol/manifest.yaml

Or alternatively, use the release tag specific manifest:

pipeline:
  - runs: |
      set -x
      curl --fail -o builder-config.yaml https://raw.githubusercontent.com/open-telemetry/opentelemetry-collector-releases/collector-v${{package.version}}/distributions/otelcol/manifest.yaml

• Explanation:
The OpenTelemetry releases repository uses a different tagging scheme than expected. The manifest file is either in the main branch or under a tag prefixed with "collector-". The fix adjusts the URL to match the actual repository structure.

• Additional Notes:

  • The OpenTelemetry project often uses different tag prefixes for different components
  • The manifest file might be maintained in the main branch rather than release tags
  • Consider caching the manifest file in the package repository if the upstream location is unstable

• References:

@octo-sts octo-sts bot added the ai/skip-comment Stop AI from commenting on PR label Mar 31, 2025
@debasishbsws
Copy link
Member

The Upstream has prepare release for open-telemetry/opentelemetry-collector-releases : open-telemetry/opentelemetry-collector-releases#898

We have to re run CI when we got a new tag for https://github.com/open-telemetry/opentelemetry-collector-releases

@debasishbsws debasishbsws self-assigned this Apr 1, 2025
@debasishbsws
Copy link
Member

They release 5 min ago. re running the CI

@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 Apr 1, 2025
@debasishbsws debasishbsws requested a review from a team April 1, 2025 15:42
@OddBloke OddBloke merged commit 61199c7 into main Apr 1, 2025
21 checks passed
@OddBloke OddBloke deleted the wolfictl-33f35daa-83bd-448a-941c-afd5463df55e branch April 1, 2025 15:43
MickeyPvX pushed a commit to MickeyPvX/wolfi-dev-os that referenced this pull request Apr 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ai/skip-comment Stop AI from commenting on PR 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.

3 participants