Project

Profile

Help

Issue #1620

closed

Newly created errata does not get associated to repository

Added by pthomas@redhat.com about 8 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
Platform Release:
2.8.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

When you create a errata on pulp, the newly created errata does not get associated to the repo.

1. Create a repo

2. Create an errata

pulp-admin rpm repo create --repo-id=repo

[root@sparks ~]# pulp-admin rpm repo uploads erratum --erratum-id=DEMO_ID_2   --title="1: pulp-test-package bit conservation"   --description="1: pulp-test-package now conserves your precious bits."   --version=1 --release="el6" --type="bugzilla" --status="final"   --updated="`date`" --issued="`date`"   --pkglist-csv=package_list.csv --from=pulp-list@redhat.com --repo-id=upload
+----------------------------------------------------------------------+
                              Unit Upload
+----------------------------------------------------------------------+

Extracting necessary metadata for each request...
... completed

Creating upload requests on the server...
[==================================================] 100%
Initializing upload
... completed

Starting upload of selected units. If this process is stopped through ctrl+c,
the uploads will be paused and may be resumed later using the resume command or
canceled entirely using the cancel command.

Importing into the repository...
This command may be exited via ctrl+c without affecting the request.

[\]
Running...

Task Succeeded

Deleting the upload request...
... completed

[root@sparks ~]# pulp-admin orphan list
+----------------------------------------------------------------------+
                                Summary
+----------------------------------------------------------------------+

Distribution:            0
Docker Blob:             0
Docker Image:            0
Docker Manifest:         0
Docker Tag:              0
Drpm:                    0
Erratum:                 2
Iso:                     0
Package Category:        0
Package Environment:     0
Package Group:           0
Puppet Module:           0
Rpm:                     0
Srpm:                    0
Yum Repo Metadata File:  0
Total:                   2

Related issues

Copied to RPM Support - Issue #1623: Newly created package group does not get associated to repository CLOSED - CURRENTRELEASEjortel@redhat.comActions

Also available in: Atom PDF