opendevstack / opendevstack/ods-quickstarters

Agents' builds Failing due to "Unknown repo"

Open
#743 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Shell
Stars
39
Forks
50
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
Several Jenkins Agents are failing to build due to: Error: Unknown repo: 'centos-appstream' / Error: Unknown repo: 'centos-baseos'

To Reproduce
Steps to reproduce the behavior:

  1. Trigger a (re)build in openshift
  2. Look at "Logs"
  3. See error

Expected behavior
Builds should finalize without errors

Screenshots
If applicable, add screenshots to help explain your problem.

Affected version (please complete the following information):

  • OpenDevStack 4.x branch

Log Output (ensure to remove any confidential information like tokens, project names, etc.
Maven, Scala agents:

[...]
Updating Subscription Management repositories.
Unable to read consumer identity
Subscription Manager is operating in container mode.
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Error: Unknown repo: 'centos-appstream'
[...]

Node agent:

Updating Subscription Management repositories.
Unable to read consumer identity
Subscription Manager is operating in container mode.
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Error: Unknown repo: 'centos-baseos'

Additional context
Add any other context about the problem here.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by triggering a build in OpenShift and inspect the Logs for the centos-appstream and centos-baseos errors shown in the report. Trace the affected Maven, Scala, and Node agents to the configuration producing those repository lookups; done means the agent builds finalize without unknown-repository errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
ci-cd, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.