View Issue Details

IDProjectCategoryView StatusLast Update
0003203Rocky-Linux-8Generalpublic2023-05-19 19:15
ReporterAlex Botelho Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Summary0003203: Syncing RL8 PowerTools Repository Warns: "Incoming and existing advisories have the same id but different timestamps and ..."
DescriptionFull error: "Incoming and existing advisories have the same id but different
timestamps and non-intersecting package lists. It is likely that they are from two
different incompatible remote repositories. E.g. RHELX-repo and RHELY-debuginfo repo.
Ensure that you are adding content for the compatible repositories. To allow this
behavior, set ALLOW_AUTOMATIC_UNSAFE_ADVISORY_CONFLICT_RESOLUTION = True (q.v.) in your
configuration. Advisory id: RLSA-2022:1763"

This happens when I sync the repository using Pulp 3.
TagsNo tags attached.

Activities

Lukas Magauer

Lukas Magauer

2023-05-08 13:43

QA   ~0003202

Hi Alex!
Thank you for the hint about this!
Two questions:
- Which repo are you syncing? (/pub/8/x86_64/os/PowerTools?)
- Which pulp 3 version are you using?
Alex Botelho

Alex Botelho

2023-05-08 13:55

reporter   ~0003203

Hopefully the below outputs have all the information you required and more:

[LIVE] fiction1:~ # pulp shell
Starting Pulp3 interactive shell...
pulp> status
{
  "versions": [
    {
      "component": "core",
      "version": "3.23.0",
      "package": "pulpcore",
      "domain_compatible": true
    },
    {
      "component": "ansible",
      "version": "0.16.1",
      "package": "pulp-ansible",
      "domain_compatible": false
    },
    {
      "component": "certguard",
      "version": "1.5.8",
      "package": "pulp-certguard",
      "domain_compatible": false
    },
    {
      "component": "container",
      "version": "2.14.3",
      "package": "pulp-container",
      "domain_compatible": false
    },
    {
      "component": "deb",
      "version": "2.20.1",
      "package": "pulp_deb",
      "domain_compatible": false
    },
    {
      "component": "file",
      "version": "1.12.0",
      "package": "pulp-file",
      "domain_compatible": false
    },
    {
      "component": "maven",
      "version": "0.3.3",
      "package": "pulp-maven",
      "domain_compatible": false
    },
    {
      "component": "python",
      "version": "3.8.0",
      "package": "pulp-python",
      "domain_compatible": false
    },
    {
      "component": "rpm",
      "version": "3.19.1",
      "package": "pulp-rpm",
      "domain_compatible": false
    }
  ],
  "database_connection": {
    "connected": true
  },
  "redis_connection": {
    "connected": false
  },
  "storage": {
    "total": 1029930151936,
    "used": 848088887296,
    "free": 138854281216
  },
  "domain_enabled": false
}

pulp> rpm remote show --name RockyLinux8-PowerTools
{
  "pulp_href": "/pulp/api/v3/remotes/rpm/rpm/c641cbb5-89b1-462b-99fc-f1d53e32b697/",
  "pulp_created": "2022-11-10T15:43:19.621879Z",
  "name": "RockyLinux8-PowerTools",
  "url": "https://mirror.esecuredata.com/rocky-linux/8/PowerTools/x86_64/os/",
  "ca_cert": null,
  "client_cert": null,
  "tls_validation": true,
  "proxy_url": null,
  "pulp_labels": {},
  "pulp_last_updated": "2022-11-10T15:43:19.621939Z",
  "download_concurrency": 30,
  "max_retries": null,
  "policy": "immediate",
  "total_timeout": null,
  "connect_timeout": null,
  "sock_connect_timeout": null,
  "sock_read_timeout": null,
  "headers": null,
  "rate_limit": null,
  "hidden_fields": [
    {
      "name": "client_key",
      "is_set": false
    },
    {
      "name": "proxy_username",
      "is_set": false
    },
    {
      "name": "proxy_password",
      "is_set": false
    },
    {
      "name": "username",
      "is_set": false
    },
    {
      "name": "password",
      "is_set": false
    }
  ],
  "sles_auth_token": null
}

Cheers!
Alex Botelho

Alex Botelho

2023-05-08 13:56

reporter   ~0003204

Looking back at my logs, we did not have this error last week. It appears as if this repo updated on May 4th, so it looks to have been a very recently introduced problem.
Lukas Magauer

Lukas Magauer

2023-05-08 14:16

QA   ~0003205

Thank you for this detailed output, looks like pulp 3.23 got another good check :)
We are / I am using Katello 4.8 for the checks, this is currently using pulp 3.22 with pulp-rpm 3.19.2 and it's not failing on me there,

As far as I understand it, the error says, that the issuing date of the errata must have changed, and this is what pulp sees as an anomaly, hence disallows it.

Will need to either do a quick setup or compare against the history, as I don't really see the issue in the metadata up to now.
Or one of the devs will take a look 👍🏻
Alex Botelho

Alex Botelho

2023-05-08 15:47

reporter   ~0003206

Cheers!

We use the Pulp 3 container, which is fairly good at quickly getting Pulp 3 going.
Lukas Magauer

Lukas Magauer

2023-05-08 17:08

QA   ~0003207

You are for sure right there! Was like half an hour to spin up and sync!

One more question, I guess you are syncing via a schedule, which sync_policy are you using?
Because the default looks to be additive (preserve existing and add), I recently heard from the Katello team, that the preferred option is mirror_complete nowadays for yum repos, I have been using mirror_content_only for a long time, maybe this gives the difference needed. (additive is generally not desired for yum repos)
Alex Botelho

Alex Botelho

2023-05-19 19:15

reporter   ~0003400

Hi Lukas,

Yes scheduled sync is using all the default parameters for syncing, of which additive is the default. For others referencing this bug report: https://docs.pulpproject.org/pulp_rpm/workflows/create_sync_publish.html

Considering distribution repositories like Rocky Linux have proper errata information, I may consider tweaking our sync scripts to enable mirroring for some repos. The problem of course is this parameter is *not* saved in Pulp's database, and I would require storing a separate per-repository/remote configuration file, which is very awkward to manage. I would not want to enable mirroring across the board, as some upstreams are very aggressive in their purging of old package versions, which means they would be cutting off a safe rollback method in case of bad package versions.

Cheers

Issue History

Date Modified Username Field Change
2023-05-08 13:30 Alex Botelho New Issue
2023-05-08 13:43 Lukas Magauer Note Added: 0003202
2023-05-08 13:55 Alex Botelho Note Added: 0003203
2023-05-08 13:56 Alex Botelho Note Added: 0003204
2023-05-08 14:16 Lukas Magauer Note Added: 0003205
2023-05-08 15:47 Alex Botelho Note Added: 0003206
2023-05-08 17:08 Lukas Magauer Note Added: 0003207
2023-05-19 19:15 Alex Botelho Note Added: 0003400