Story #3885
closedAs a user, I can specify distributor_id via pulp-admin during publish
0%
Description
Good morning all.
I'm currently creating rpm repo's via the api, and attach distributors as part of the process.
We are naming these distributors based on "the release" they represent, but of course, they are of distributor_type yum_distributor.
I've noticed that if I create a repo via the above approach, the pulp-admin tools can not be used to publish the repository, as they are expecting to have a distributor to be present with distributo_id: yum_distributor.
running a pulp-admin rpm repo sync successfully syncs, and publishes the repo.
Is there a reason that on a publish request, we would not be publishing based on distributor_type, as opposed to distributore_id?
Example repo
[dfurlong@chlv-repo01 ~]$ pulp-admin repo list --details --repo-id=upstream_sles12.2-pool
+----------------------------------------------------------------------+
Repositories
+----------------------------------------------------------------------+
Id: upstream_sles12.2-pool
Display Name: pool
Description: None
Content Unit Counts:
Rpm: 3683
Yum Repo Metadata File: 2
Notes:
Parent: None
Platform: sles12.2
Release: upstream
Scratchpad:
Checksum Type: sha256
Importers:
Config:
Feed: https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP2/x
86_64/product
Num Retries: 5
Query Auth Token: myeSwPPGvfUqdMgBHlNWhOsog-xa4FbM4vn95es-W2qLIxrAks0jY8XnYQ
UwqDDbwTJJGJ_FBjw3DmZrQxF22zTdsj6eH0dqad1C0Oi55V3a_6CyiKyI
Pqil7vNrvIp8kYqJppZc3OgBgTmAcQ
Validate: True
Id: yum_importer
Importer Type Id: yum_importer
Last Override Config:
Type Skip List: iso, distribution
Last Sync: 2018-07-27T08:26:34Z
Last Updated: 2018-07-26T15:17:06Z
Repo Id: upstream_sles12.2-pool
Scratchpad:
Repomd Revision: 1477945506
Distributors:
Auto Publish: True
Config:
Generate Sqlite: True
Http: True
Https: True
Relative URL: sles12.2/upstream/sles12.2-pool/
Repoview: True
Distributor Type Id: yum_distributor
Id: upstream
Last Override Config:
Last Publish: None
Last Updated: 2018-07-30T09:36:51Z
Repo Id: upstream_sles12.2-pool
Scratchpad:
[dfurlong@chlv-repo01 ~]$ pulp-admin rpm repo publish run --repo-id=upstream_sles12.2-pool
+----------------------------------------------------------------------+
Publishing Repository [upstream_sles12.2-pool]
+----------------------------------------------------------------------+
This command may be exited via ctrl+c without affecting the request.
Task Failed
Missing resource(s): repo_id=upstream_sles12.2-pool,
distributor_id=yum_distributor
Updated by ttereshc over 5 years ago
- Tracker changed from Issue to Story
- Subject changed from pulp-admin rpm repo publish - requires distributor_id to As a user, I can specify distributor_id via pulp-admin during publish
- % Done set to 0
There could be multiple distributors of the same type for a repo, so we can't use distributor_type in pulp-admin.
pulp-admin works for simple basic cases, and if one create a repo via pulp-admin they don't have a choice for a distributor.
It's unfortunate but currently it is possible to work with custom distributors only via API.
Converting this issue to a story (RFE) to be able to specify distributor_id in pulp-admin
Updated by wibbit over 5 years ago
Funnily enough I was talking to my colleague about this earlier today, and said just that.
If this is an RFE, I think it would be worth while expanding the scope slightly, as there are numerous places that this issue comes up, not just with the publish.
I'll let people know that for now, and the foreseeable future, we'll need to ensure that we implement every thing in our own code.
Updated by bmbouter about 5 years ago
- Status changed from NEW to CLOSED - WONTFIX