RPM Support

For the steps that are not able to be done using pulp-admin, can those be rewritten into httpie[0] commands. You can `pip install httpie` or yum/dnf httpie to get it onto your system. For example, for localhost with admin:admin credentials and having the client not verify the SSL hostname, I think the first one is:

http --verify no --auth admin:admin POST https://localhost/pulp/api/v2/repositories/ id=integration_test_id importer_type_id=yum_importer importer_config:='{"feed": "file:///var/www/repositories/zoo5"}'

FWIW, I also thing this would be accomplished with pulp-admin using:

pulp-admin rpm repo create --repo-id integration_test_id --feed file:///var/www/repositories/zoo5

[0]: https://github.com/jkbrzt/httpie

Was not able to reproduce this, both pulp-admin and API work:

$ pulp-admin -u admin -p admin repo list --repo-id zoo
+----------------------------------------------------------------------+
                              Repositories
+----------------------------------------------------------------------+

Id:                   zoo
Display Name:         None
Description:          None
Content Unit Counts:  
  Erratum:          4
  Package Category: 1
  Package Group:    2
  Rpm:              32

[ipanova@ina pulp]$ pulp-admin -u admin -p admin rpm repo copy all  --from-repo-id zoo --to-repo-id myrepo
This command may be exited via ctrl+c without affecting the request.

[\]
Running...

Copied:
 erratum:
  RHEA-2012:0001
  RHEA-2012:0002
  RHEA-2012:0003
  RHEA-2012:0004
 package_category:
  all
 package_group:
  birds
  mammals
 rpm:
  bear-4.1-1-noarch
  camel-0.1-1-noarch
  cat-1.0-1-noarch
  cheetah-1.25.3-5-noarch
  chimpanzee-0.21-1-noarch
  cockateel-3.1-1-noarch
  cow-2.2-3-noarch
  crow-0.8-1-noarch
  dog-4.23-1-noarch
  dolphin-3.10.232-1-noarch
  duck-0.6-1-noarch
  elephant-8.3-1-noarch
  fox-1.1-2-noarch
  frog-0.1-1-noarch
  giraffe-0.67-2-noarch
  gorilla-0.62-1-noarch
  horse-0.22-2-noarch
  kangaroo-0.2-1-noarch
  lion-0.4-1-noarch
  mouse-0.1.12-1-noarch
  penguin-0.9.1-1-noarch
  pike-2.2-1-noarch
  shark-0.1-1-noarch
  squirrel-0.1-1-noarch
  stork-0.12-2-noarch
  tiger-1.0-4-noarch
  trout-0.12-1-noarch
  walrus-0.71-1-noarch
  walrus-5.21-1-noarch
  whale-0.2-1-noarch
  wolf-9.4-2-noarch
  zebra-0.1-2-noarch

[ipanova@ina pulp]$ pulp-admin -u admin -p admin repo list --repo-id myrepo
+----------------------------------------------------------------------+
                              Repositories
+----------------------------------------------------------------------+

Id:                   myrepo
Display Name:         None
Description:          None
Content Unit Counts:  
  Erratum:          4
  Package Category: 1
  Package Group:    2
  Rpm:              32

$ curl -H "Accept: application/json" -X POST -k -u admin:admin -d '{"source_repo_id": "zoo"}' 'https://localhost/pulp/api/v2/repositories/test/actions/associate/'|python -m json.tool
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   197  100   172  100    25    618     89 --:--:-- --:--:-- --:--:--   620
{
    "error": null,
    "result": null,
    "spawned_tasks": [
        {
            "_href": "/pulp/api/v2/tasks/dde39cdc-910c-406f-b6f4-0be6eb1f983e/",
            "task_id": "dde39cdc-910c-406f-b6f4-0be6eb1f983e"
        }
    ]
}
[ipanova@ina pulp]$ pulp-admin -u admin -p admin repo list --repo-id test
+----------------------------------------------------------------------+
                              Repositories
+----------------------------------------------------------------------+

Id:                   test
Display Name:         None
Description:          None
Content Unit Counts:  
  Erratum:          4
  Package Category: 1
  Package Group:    2
  Rpm:              32

Possibly a duplicate of #1478, but if not it's definitely related.

Edit: I put this on the wrong issue, this comment was meant for #1490

Just saw https://pulp.plan.io/issues/1489#note-2
So I was unable to reproduce this when using pulp-admin. I think the runcible api doesnt set things like notes fields with __repo_type:yum etc. It could be that. I will try to get you the exact params we send over to pulp when we create repo in a few

Actually I think comment #1 completely captures the post request we send to pulp and Dr Bouters' variation should be an accurate repro

Client.post "https://<PULP>/pulp/api/v2/repositories/", "{\"id\":\"integration_test_id\",\"importer_type_id\":\"yum_importer\",\"importer_config\":{\"feed\":\"file:///var/www/repositories/zoo5\"}}", "Accept"=>"*/*; q=0.5, application/xml", "Accept-Encoding"=>"gzip, deflate", "Content-Length"=>"125", "accept"=>"application/json", "content_type"=>"application/json" 

Dr Bouters' variation

http --verify no --auth admin:admin POST https://localhost/pulp/api/v2/repositories/ id=integration_test_id importer_type_id=yum_importer importer_config:='{"feed": "file:///var/www/repositories/zoo5"}'

I don't think anything special in the notes field will matter. That is just a hint for pulp-admin to quickly know what type a repo is.

I'm also not able to reproduce. I'm using the repo you referenced. If you spot any differences in my requests that you think are worth noting, please point them out, but I tried to make near-identical requests.

http --verify no --auth admin:admin POST https://localhost/pulp/api/v2/repositories/ id=integration_test_id importer_type_id=yum_importer importer_config:='{"feed": "file:///home/vagrant/runcible/test/fixtures/repositories/zoo5"}'

http --verify no --auth admin:admin POST https://localhost/pulp/api/v2/repositories/integration_test_id/actions/sync/

http --verify no --auth admin:admin POST https://localhost/pulp/api/v2/repositories/ id=integration_test_id_clone importer_type_id=yum_importer importer_config:='{}'

http --verify no --auth admin:admin POST https://localhost/pulp/api/v2/repositories/integration_test_id_clone/actions/associate/ source_repo_id=integration_test_id

After that, I can see that everything got copied:

$ pulp-admin repo list
+----------------------------------------------------------------------+
                              Repositories
+----------------------------------------------------------------------+

Id:                  integration_test_id
Display Name:        integration_test_id
Description:         None
Content Unit Counts: 
  Distribution:     1
  Erratum:          2
  Package Category: 1
  Package Group:    2
  Rpm:              8

Id:                  integration_test_id_clone
Display Name:        integration_test_id_clone
Description:         None
Content Unit Counts: 
  Distribution:     1
  Erratum:          2
  Package Category: 1
  Package Group:    2
  Rpm:              8

Partha, do you have any suggestions for how we should proceed?

How are you determining that the groups didn't get copied? Maybe there's a bug in that workflow? If runcible was doing a search for groups based on "id", our current open bug #1478 about that attribute being renamed to "group_id" could make runcible think the groups didn't get copied.

So after some time i was able to re-produce the issue with both(CLI and API) methods.
Steps are:

1 create repoA with feed and sync it
2 create repoB
3 copy all units from repoA to repoB
------------------------------------
see all units copied( included package groups and categories)

4 remove repos( but don't clean orphans)
5 re-do steps 1-3( and use same names)
---------------------------------------
see the package groups and categories not copied

There is some issue with situation when unit key is already present and we need a deeper investigation