Skip to content

feat(iop): csaf eval, cpes, release graph - #752

Open
vkrizan wants to merge 2 commits into
theforeman:masterfrom
vkrizan:feat-iop-enable-csaf-eval
Open

feat(iop): csaf eval, cpes, release graph#752
vkrizan wants to merge 2 commits into
theforeman:masterfrom
vkrizan:feat-iop-enable-csaf-eval

Conversation

@vkrizan

@vkrizan vkrizan commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Why are you introducing these changes? (Problem description, related links)

Enabling the CVE's without errata feature in VMaas.

This requires additional data syncs of CPEs and Release Graphs.

What are the changes introduced in this pull request?

  • Enables CSAF_UNFIXED_EVAL_ENABLED on VMaaS web app
  • Enables reposcan to import CPE and release graphs data through/from IoP Gateway

How to test this pull request

Steps to reproduce:

Checklist

  • Tests added/updated (if applicable)
  • Documentation updated (if applicable)

@vkrizan
vkrizan marked this pull request as ready for review August 17, 2026 10:06
Enables VMaaS Reposcan to import CPE and Release Graph metadata
through/from IoP Gateway.
@vkrizan
vkrizan force-pushed the feat-iop-enable-csaf-eval branch from b18461d to 9091252 Compare August 24, 2026 09:27
@vkrizan vkrizan changed the title feat(iop): enable csaf eval in vmaas feat(iop): csaf eval, cpes, release graph Aug 24, 2026
@vkrizan

vkrizan commented Aug 24, 2026

Copy link
Copy Markdown
Contributor Author

@ehelms @jeremylenz Please review. 🙏

SYNC_CSAF: "yes"
SYNC_RELEASES: "no"
SYNC_RELEASE_GRAPH: "no"
SYNC_RELEASE_GRAPH: "yes"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would unfortunately be available only in downstream. Should I flip this to "no" here?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is it?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mapping of Product Versions to CPEs for accurate reporting. @jdobes can give more details if you want.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does it trigger to happen? or put another way, will this causes errors if there is no access?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The import is part of reposync (either manual through the trigger script, or timed within the process). If there is no access (or malformed response), then it would fail just the part of release graphs import (with a log entry).

We can flip this to "no" here for the upstream. Then the REPOLIST_GIT URL (to vmaas-assets) would not matter.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it fails without a bunch of noise, I'm OK with it.

@ehelms

ehelms commented Aug 24, 2026

Copy link
Copy Markdown
Member

Enabling the CVE's without errata feature in VMaas.

RHINENG-30000 RHINENG-27931

This can seem quite random and unclear what they are to anyone in the community. Not to mention they are private once you realize they are Red Hat Jira issues. Please try to avoid including that kind of info in the description or commit message.

KATELLO_URL: "http://iop-core-gateway:9090"
REDHAT_CVEMAP_URL: "http://iop-core-gateway:9090/pub/iop/data/meta/v1/cvemap.xml"
CPE_DICT_URL: http://iop-core-gateway:9090/pub/iop/data/meta/v1/cpe-dictionary.xml
REPOLIST_GIT: http://iop-core-gateway:9090/static/vmaas-assets/.git

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A hidden folder? Is this a standard git repo config folder? What creates it?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a bare git folder that is generated during build. Reposcan works with git at the moment, so we've chosen this workaround. We are planning to remove the dependency on git in our services...

This is related to SYNC_RELEASE_GRAPH=yes. See also comment #752 (comment).

@vkrizan

vkrizan commented Aug 24, 2026

Copy link
Copy Markdown
Contributor Author

Enabling the CVE's without errata feature in VMaas.
RHINENG-30000 RHINENG-27931

This can seem quite random and unclear what they are to anyone in the community. Not to mention they are private once you realize they are Red Hat Jira issues. Please try to avoid including that kind of info in the description or commit message.

Let's discuss this outside of the PR. I'd love your thoughts to improve this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants