Product Registry is showing community stacks

[kim-tsao]

Which area this feature is related to?

/kind bug

Which area this bug is related to?

/area registry

The product registry is incorrectly displaying the community stacks. It should only be the JBoss ones

What versions of software are you using?

Go project

Operating System and version:

Go Pkg Version:

Node.js project

Operating System and version:

Node.js version:

Yarn version:

Project.json:

Web browser

Operating System and version:

Browser name and version:

Bug Summary

Describe the bug:

To Reproduce:

Expected behavior

Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable

Additional context

Any workaround?

Suggestion on how to fix the bug

[michael-valdron]

Product registry has been reverted to a previous state which has restored the proper stacks. Further investigation of recent changes will be needed under product registry and registry services to resolve why the community stacks were built into this deployment.

[michael-valdron]

In addition, product registry testing will need to be investigated.

[michael-valdron]

Staging of the product registry does show the correct stacks, therefore this could be isolated to production or fixed in the most recent build: https://devfile-registry.stage.redhat.com/viewer

[michael-valdron]

All individuals that would be able to fix this are unavailable for the upcoming sprints due to higher priority items regarding the devfile registry. Fixing this is important so we'll need to keep track of this.

Perhaps we could include this under the upcoming devtools week.

cc: @elsony @mike-hoang @johnmcollier @kim-tsao

[michael-valdron]

Waiting for 2024 to review with the team.

[thepetk]

Moving back to refinement to be reviewed by the team

[github-actions]

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

[michael-valdron]

Since the product registry is planned to be retired #1527 and has no further planned promotions that would introduce this bug into the live service, I will close this issue as not planned.