Migrate Suse Scores importer to advisory V2

[ziadhany]

Issue:

• VCIO-API-V2: Migrate Suse Scores importer to advisory V2 #2041

[ziadhany]

Importing data using suse_importer_v2
INFO 2026-01-02 18:14:51.627834 UTC Pipeline [SUSESeverityScoreImporterPipeline] starting
INFO 2026-01-02 18:14:51.627965 UTC Step [fetch_advisories] starting
INFO 2026-01-02 18:14:57.055676 UTC Step [fetch_advisories] completed in 5 seconds
INFO 2026-01-02 18:14:57.055831 UTC Step [collect_and_store_advisories] starting
INFO 2026-01-02 18:14:57.057833 UTC Collecting 25,736 advisories
INFO 2026-01-02 18:15:15.518451 UTC Progress: 10% (2574/25736) ETA: 166 seconds (2.8 minutes)
INFO 2026-01-02 18:15:34.700664 UTC Progress: 20% (5148/25736) ETA: 151 seconds (2.5 minutes)
INFO 2026-01-02 18:15:52.247506 UTC Progress: 30% (7721/25736) ETA: 129 seconds (2.1 minutes)
INFO 2026-01-02 18:16:10.067302 UTC Progress: 40% (10295/25736) ETA: 110 seconds (1.8 minutes)
INFO 2026-01-02 18:16:28.339920 UTC Progress: 50% (12868/25736) ETA: 91 seconds (1.5 minutes)
INFO 2026-01-02 18:16:46.313951 UTC Progress: 60% (15442/25736) ETA: 73 seconds (1.2 minutes)
INFO 2026-01-02 18:17:04.554662 UTC Progress: 70% (18016/25736) ETA: 55 seconds
INFO 2026-01-02 18:17:23.851496 UTC Progress: 80% (20589/25736) ETA: 37 seconds
INFO 2026-01-02 18:17:44.424970 UTC Progress: 90% (23163/25736) ETA: 19 seconds
INFO 2026-01-02 18:18:05.084409 UTC Progress: 100% (25736/25736)
INFO 2026-01-02 18:18:05.092544 UTC Successfully collected 25,736 advisories
INFO 2026-01-02 18:18:05.092633 UTC Step [collect_and_store_advisories] completed in 188 seconds (3.1 minutes)
INFO 2026-01-02 18:18:05.092688 UTC Pipeline completed in 193 seconds (3.2 minutes)

from vulnerabilities.models import AdvisoryV2
from django.db.models import Count
duplicates = (
    AdvisoryV2.objects
    .values('avid')
    .annotate(count=Count('id'))
    .filter(count__gt=1)
)
len(duplicates)
Out[2]: 0
AdvisoryV2.objects.count()
Out[3]: 25817

[ziadhany]

@TG1999 We can’t create an advisory without a summary, affected_packages, or references, so we should at least include a reference.

[TG1999]

@ziadhany we should change this logic then, severities are also a good data point to capture, so if an advisory have a severity we should be able to create it.

[ziadhany]

Okay, I will create an issue for that.

[ziadhany]

@TG1999 @keshav-space The problem in this issue

• Update Advisory Logic to Allow Creation with Only CVE ID and Severity #2105
  is in the compute_content_id function. We are missing advisory_id and patches, and we also lack a check for severities or patches, which is required to compute the hash correctly I think.