[Pulp-list] Issues with Pulp

Claer claer at claer.hammock.fr
Tue Jun 18 09:41:55 UTC 2013


Hello list,

I'm discovering pulp and tried to match my needs to replace my old mrepo
setup. Here are my needs :

- Sync repositories for internal use
   - Sync RHEL{5,6} repos daily
   - Sync external repos (EPEL, Pulp, Foreman,..)

- Create repositories
   - Custom repo for custom rpms
   - Repo with erratas only
   - create repos rhel per minor version

- List hosts that need patches/erratas
   - push updates to groups of hosts

- Schedules on few reposotories to update daily.
- Schedules erratas installation
- verify that everything is ok

I successfully installed pulp 2.1 from the documentation on RHEL6 and CentOS6 
platforms.

Here are issues I encountered, please advice me how to use Pulp to resolve those.

* UI :
- Sync errors are not readable. For Example :
2013-06-17 11:23:25,232 - ERROR - Client-side exception occurred
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/pulp/client/extensions/core.py", line 478, in run
    exit_code = Cli.run(self, args)
  File "/usr/lib/python2.6/site-packages/okaara/cli.py", line 967, in run
    exit_code = command_or_section.execute(self.prompt, remaining_args)
  File "/usr/lib/python2.6/site-packages/pulp/client/extensions/extensions.py", line 224, in execute
    return self.method(*arg_list, **clean_kwargs)
  File "/usr/lib/python2.6/site-packages/pulp/client/commands/repo/sync_publish.py", line 101, in run
    status.display_group_status(self.context, self.renderer, task_group_id)
  File "/usr/lib/python2.6/site-packages/pulp/client/commands/repo/status/status.py", line 63, in display_group_status
    _display_status(context, renderer, task_list)
  File "/usr/lib/python2.6/site-packages/pulp/client/commands/repo/status/status.py", line 95, in _display_status
    _display_task_status(context, renderer, task.task_id, quiet_waiting=quiet_waiting)
  File "/usr/lib/python2.6/site-packages/pulp/client/commands/repo/status/status.py", line 122, in _display_task_status
    renderer.display_report(response.response_body.progress)
  File "/usr/lib/python2.6/site-packages/pulp_rpm/extension/admin/status.py", line 67, in display_report
    self.render_metadata_step(progress_report)
  File "/usr/lib/python2.6/site-packages/pulp_rpm/extension/admin/status.py", line 93, in render_metadata_step
    self.prompt.render_failure_message(progress_report['yum_importer']['metadata']['error'])
KeyError: 'error'
 
Expected : Could not contact proxy server
 
- How can I list all schedules?
- How can I list all bindings for a group?
  # pulp-admin bindings search --help
  => no group information
  # pulp-admin consumer list
  => no group information
  # pulp-admin rpm  consumer group list
  => no binding information
- How can I schedule a group package update?
  # pulp-admin rpm consumer group package update
  => no schedule option
- How can I install all erratas for a host, for a group
  # pulp-admin rpm consumer errata install run
  => pulp ask for errata id
  # pulp-admin rpm consumer group
  => no errata option
 
* Bugs :

- Copying rpm of erratas form a repository to another leads to no RPM in the 
  destination directory :

# pulp-admin rpm repo create --repo-id "RHEL5-updates-x86_64" --feed=https://cdn.redhat.com/content/dist/rhel/server/5/5Server/x86_64/os --relative-url=RHEL5-updates-x86_64 --proxy-url=http://127.0.0.1 --proxy-port=8080 --feed-ca-cert=/etc/rhsm/ca/redhat-uep.pem --feed-cert=/etc/pki/entitlement/1111111111111111111.pem --feed-key=/etc/pki/entitlement/1111111111111111111-key.pem
# pulp-admin rpm repo sync run --repo-id "RHEL5-updates-x86_64"
# pulp-admin rpm repo create --repo-id RHEL5-security-updates-x86_64 --relative-url=RHEL5-security-updates-x86_64
# pulp-admin rpm repo copy errata --copy-children true --from-repo-id RHEL5-updates-x86_64 --to-repo-id RHEL5-security-updates-x86_64
# pulp-admin rpm repo content rpm --repo-id RHEL5-security-updates-x86_64
#
 
- schedule a publishing
  # pulp-admin rpm repo publish schedules not available
- schedule a copy (when point 1 is working)
- after updating a repo for --serve-http(s) true|false you need to publish it,
  even with autopublish
- updates all packages on a node
  # pulp-admin rpm consumer package update run --all --consumer-id rerz02
Command: run
Description: triggers an immediate package update on a consumer
 
Available Arguments:
 
  --consumer-id - (required) unique identifier; only alphanumeric, -, and _
                  allowed
  --name, -n    - (required) package name; may repeat for multiple packages
  --no-commit   - test the transaction without committing it
  --reboot      - reboot after a successful transaction
  --import-keys - import GPG keys as needed
  --all, -a     - update all content units
The following options are required but were not specified:
  --name
  #

- Update all packages for a group
  # pulp-admin rpm consumer group package update --all --consumer-group-id inge_rhel6
Consumer Group [<built-in function id>] not found
  #
 
- after updating a repo for --serve-http(s) true|false you need to publish it, even with autopublish

Shall I switch to beta pulp to be able to solve some or all issues I'm getting ?
Did I misunderstood something?


Regards,

Claer
 




More information about the Pulp-list mailing list