Project

Profile

Help

Issue #6133

closed

pulp_rpm synchronization failure: day is out of range for month

Added by jdjeffers almost 5 years ago. Updated almost 4 years ago.

Status:
CLOSED - WORKSFORME
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Traceback:



        ---
        pulp_tasks:
        - pulp_href: "/pulp/api/v3/tasks/fef4b7b9-635b-4f6d-9b89-d9ad96bd0bf7/"
          pulp_created: '2020-02-11T18:28:54.861+00:00'
          state: failed
          name: pulp_rpm.app.tasks.synchronizing.synchronize
          started_at: '2020-02-11T18:28:55.057+00:00'
          finished_at: '2020-02-11T18:28:55.416+00:00'
          error:
            traceback: |2
                File "/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/worker.py", line 822, in perform_job
                  rv = job.perform()
                File "/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/job.py", line 605, in perform
                  self._result = self._execute()
                File "/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/job.py", line 611, in _execute
                  return self.func(*self.args, **self.kwargs)
                File "/usr/local/lib/pulp/src/pulp-rpm/pulp_rpm/app/tasks/synchronizing.py", line 150, in synchronize
                  dv.create()
                File "/usr/local/lib/pulp/src/pulpcore/pulpcore/plugin/stages/declarative_version.py", line 149, in create
                  loop.run_until_complete(pipeline)
                File "/usr/lib64/python3.6/asyncio/base_events.py", line 484, in run_until_complete
                  return future.result()
                File "/usr/local/lib/pulp/src/pulpcore/pulpcore/plugin/stages/api.py", line 209, in create_pipeline
                  await asyncio.gather(*futures)
                File "/usr/local/lib/pulp/src/pulpcore/pulpcore/plugin/stages/api.py", line 43, in __call__
                  await self.run()
                File "/usr/local/lib/pulp/src/pulp-rpm/pulp_rpm/app/tasks/synchronizing.py", line 632, in run
                  **UpdateRecord.createrepo_to_dict(update)
                File "/usr/local/lib/pulp/src/pulp-rpm/pulp_rpm/app/models/advisory.py", line 126, in createrepo_to_dict
                  getattr(update, CR_UPDATE_RECORD_ATTRS.UPDATED_DATE)),
            description: day is out of range for month
          worker: "/pulp/api/v3/workers/d7c8be98-cf8b-4bc7-ab59-3465ce27c8ef/"
          progress_reports:
          - message: Parsed Advisories
            code: parsing.advisories
            state: failed
            total: 4
            done: 0
          - message: Downloading Metadata Files
            code: downloading.metadata
            state: failed
            done: 2
          - message: Downloading Artifacts
            code: downloading.artifacts
            state: canceled
            done: 0
          - message: Associating Content
            code: associating.content
            state: canceled
            done: 0
          created_resources: []
          reserved_resources_record:
          - "/pulp/api/v3/repositories/rpm/rpm/2271bfd1-d022-4241-8d58-9e7f2381d5bd/"
          - "/pulp/api/v3/remotes/rpm/rpm/59940668-a5af-43ea-a3d3-a10987227b14/"
        poll_attempts:
          total: 1
          failed: 1

Version data:

versions": [
    {
      "component": "pulpcore",
      "version": "3.0.2.dev0"
    },
    {
      "component": "pulp_file",
      "version": "0.1.2.dev0"
    },
    {
      "component": "pulp_2to3_migration",
      "version": "0.0.1b2.dev0"
    },
    {
      "component": "pulp_container",
      "version": "1.0.1.dev0"
    },
    {
      "component": "pulp_ansible",
      "version": "0.2.0b9.dev0"
    },
    {
      "component": "pulp_rpm",
      "version": "3.0.1.dev0"
    }

createrepo_c-0.10.0-20.el7.x86_64

The repo synchronized was at https://jlsherrill.fedorapeople.org/fake-repos/needed-errata/


Related issues

Related to RPM Support - Issue #8162: syncing a repo with an erratum without an updated date results in a bad date in published metadataCLOSED - CURRENTRELEASEdalleyActions
Actions #1

Updated by ttereshc almost 5 years ago

  • Project changed from Pulp to RPM Support
  • Subject changed from pulp_rpm synchronization failure to pulp_rpm synchronization failure: day is out of range for month

Fixture repo has no updated datetime for advisories and pulp currently expects it to be present.

Actions #2

Updated by ttereshc almost 5 years ago

  • Triaged changed from No to Yes

OpenSUSE repos usually don't have updated datetime as well. Keeping this open to track that.

Actions #3

Updated by dalley about 4 years ago

Would that make this necessary for proper SUSE support? Does it then mean that this should be prioritized higher?

Actions #4

Updated by dalley almost 4 years ago

  • Related to Issue #8162: syncing a repo with an erratum without an updated date results in a bad date in published metadata added
Actions #5

Updated by dalley almost 4 years ago

  • Status changed from NEW to CLOSED - WORKSFORME

There were some fixes to related bugs lately, and I can no longer reproduce this one. Making the assumption that it's now fixed.

Also available in: Atom PDF