Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2017-05-17T19:52:24ZPulp
Planio RPM Support - Issue #2761 (CLOSED - WONTFIX): Iso repo with basic auth does not report sync progresshttps://pulp.plan.io/issues/27612017-05-17T19:52:24Zpthomas@redhat.com
<p>When syncing a file repo (iso repo) with basic auth, the sync progress is being reported.</p>
<p>1. Create a repo with basic auth<br>
2. Run repo sync</p>
<pre><code>
[root@qe-blade-12 ~]# rpm -qa |grep pulp sort
grep: sort: No such file or directory
[root@qe-blade-12 ~]#
[root@qe-blade-12 ~]#
[root@qe-blade-12 ~]# rpm -qa |grep pulp |sort
pulp-admin-client-2.13.1-0.1.beta.el7.noarch
pulp-docker-admin-extensions-2.4.0-0.2.rc.el7.noarch
pulp-docker-plugins-2.4.0-0.2.rc.el7.noarch
pulp-ostree-admin-extensions-1.2.1-1.2.rc.el7.noarch
pulp-ostree-plugins-1.2.1-1.2.rc.el7.noarch
pulp-puppet-admin-extensions-2.13.1-0.1.beta.el7.noarch
pulp-puppet-plugins-2.13.1-0.1.beta.el7.noarch
pulp-python-admin-extensions-2.0.0-0.3.rc.el7.noarch
pulp-python-plugins-2.0.0-0.3.rc.el7.noarch
pulp-rpm-admin-extensions-2.13.1-0.1.beta.el7.noarch
pulp-rpm-plugins-2.13.1-0.1.beta.el7.noarch
pulp-selinux-2.13.1-0.1.beta.el7.noarch
pulp-server-2.13.1-0.1.beta.el7.noarch
python-isodate-0.5.0-4.pulp.el7.noarch
python-kombu-3.0.33-6.pulp.el7.noarch
python-pulp-bindings-2.13.1-0.1.beta.el7.noarch
python-pulp-client-lib-2.13.1-0.1.beta.el7.noarch
python-pulp-common-2.13.1-0.1.beta.el7.noarch
python-pulp-docker-common-2.4.0-0.2.rc.el7.noarch
python-pulp-oid_validation-2.13.1-0.1.beta.el7.noarch
python-pulp-ostree-common-1.2.1-1.2.rc.el7.noarch
python-pulp-puppet-common-2.13.1-0.1.beta.el7.noarch
python-pulp-python-common-2.0.0-0.3.rc.el7.noarch
python-pulp-repoauth-2.13.1-0.1.beta.el7.noarch
python-pulp-rpm-common-2.13.1-0.1.beta.el7.noarch
python-pulp-streamer-2.13.1-0.1.beta.el7.noarch
[root@qe-blade-12 ~]# pulp-admin iso repo create --repo-id protected-file --feed http://<authenticated-repo>
Successfully created repository [protected-file]
[root@qe-blade-12 ~]#
[root@qe-blade-12 ~]#
[root@qe-blade-12 ~]#
[root@qe-blade-12 ~]# pulp-admin rpm repo sync run --repo-id protected-file
+----------------------------------------------------------------------+
Synchronizing Repository [protected-file]
+----------------------------------------------------------------------+
This command may be exited via ctrl+c without affecting the request.
Task Failed
Importer indicated a failed response
[root@qe-blade-12 ~]# pulp-admin rpm repo update --repo-id protected-file --basicauth-user <username> --basicauth-pass <password> --feed http://<protected-repo>
Repository [protected-file] successfully updated
[root@qe-blade-12 ~]#
[root@qe-blade-12 ~]#
[root@qe-blade-12 ~]#
[root@qe-blade-12 ~]# pulp-admin rpm repo sync run --repo-id protected-file
+----------------------------------------------------------------------+
Synchronizing Repository [protected-file]
+----------------------------------------------------------------------+
This command may be exited via ctrl+c without affecting the request.
Task Succeeded
Task Succeeded
[root@qe-blade-12 ~]# pulp-admin iso repo list
+----------------------------------------------------------------------+
ISO Repositories
+----------------------------------------------------------------------+
Id: protected-file
Display Name: None
Description: None
Content Unit Counts:
Iso: 3
</code></pre> Pulp - Issue #2170 (CLOSED - WONTFIX): Getting a 500 instead of 400 when using a string in criter...https://pulp.plan.io/issues/21702016-08-11T19:00:12Zpthomas@redhat.com
<p>Getting a 500 instead of 400 when using a string in criteria instead of dict</p>
<p>[root@tigger ~]# http --verify no --auth admin:admin POST <a href="https://localhost/pulp/api/v2/repositories/zoo1/actions/associate/" class="external">https://localhost/pulp/api/v2/repositories/zoo1/actions/associate/</a> source_repo_id=zoo criteria='{'type_ids' : ['rpm'],'filters' : {'unit' : {'$and': [{'name': {'$regex': 'c*.*'}}, {'version': {'$gt': '1.0'}}] }}} }'<br>
/usr/lib/python2.7/site-packages/urllib3/connectionpool.py:769: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: <a href="https://urllib3.readthedocs.org/en/latest/security.html" class="external">https://urllib3.readthedocs.org/en/latest/security.html</a><br>
InsecureRequestWarning)<br>
HTTP/1.1 500 INTERNAL SERVER ERROR<br>
Connection: close<br>
Content-Length: 1591<br>
Content-Type: application/json; charset=utf-8<br>
Date: Thu, 11 Aug 2016 17:36:31 GMT<br>
Server: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.1e-fips mod_wsgi/3.4 Python/2.7.5</p>
<p>{<br>
"_href": "/pulp/api/v2/repositories/zoo1/actions/associate/",<br>
"error_message": "'str' object has no attribute 'pop'",<br>
"exception": [<br>
"AttributeError: 'str' object has no attribute 'pop'\n"<br>
],<br>
"http_request_method": "POST",<br>
"http_status": 500,<br>
"traceback": [<br>
" File \"/usr/lib/python2.7/site-packages/django/core/handlers/base.py\", line 112, in get_response\n response = wrapped_callback(request, *callback_args, **callback_kwargs)\n",<br>
" File \"/usr/lib/python2.7/site-packages/django/views/generic/base.py\", line 69, in view\n return self.dispatch(request, *args, **kwargs)\n",<br>
" File \"/usr/lib/python2.7/site-packages/django/views/generic/base.py\", line 87, in dispatch\n return handler(request, *args, **kwargs)\n",<br>
" File \"/usr/lib/python2.7/site-packages/pulp/server/webservices/views/decorators.py\", line 241, in _auth_decorator\n return _verify_auth(self, operation, super_user_only, method, *args, **kwargs)\n",<br>
" File \"/usr/lib/python2.7/site-packages/pulp/server/webservices/views/decorators.py\", line 195, in _verify_auth\n value = method(self, *args, **kwargs)\n",<br>
" File \"/usr/lib/python2.7/site-packages/pulp/server/webservices/views/util.py\", line 130, in wrapper\n return func(*args, **kwargs)\n",<br>
" File \"/usr/lib/python2.7/site-packages/pulp/server/webservices/views/repositories.py\", line 1159, in post\n criteria = UnitAssociationCriteria.from_client_input(criteria_body)\n",<br>
" File \"/usr/lib/python2.7/site-packages/pulp/server/db/model/criteria.py\", line 260, in from_client_input\n type_ids = query.pop('type_ids', None)\n"<br>
]<br>
}</p>
<p>[root@tigger ~]#</p> RPM Support - Story #1980 (CLOSED - WONTFIX): As a user, I see a warning message when I upload La...https://pulp.plan.io/issues/19802016-06-07T13:27:37Zpthomas@redhat.com
<p>Langpacks upload overwrite the previous upload. I would like to see a, message warning the user that the upload will overwrite any previous langpacks in the repository.</p>
<p>This should be extended to any other metadata types which allows only one associated with a repository.</p>
<p>Following is an example for langpacks upload.</p>
<p>1. Create a repository<br>
2. Upload langpacks A<br>
3. Upload a second langpacks</p>
<p>$ pulp-admin rpm repo create --repo-id=repo_1 \<br>
--feed=<a href="http://repos.fedorapeople.org/repos/pulp/pulp/demo_repos/pulp_unittest/" class="external">http://repos.fedorapeople.org/repos/pulp/pulp/demo_repos/pulp_unittest/</a><br>
Successfully created repository [repo_1]</p>
<p>$ pulp-admin rpm repo sync run --repo-id=repo_1</p>
<p>Now let's build two package groups for our demo repo test files:</p>
<p>$ pulp-admin rpm repo uploads group --repo-id=repo_1 \<br>
--group-id=pulp_test_packages --name="Pulp Test Packages" \<br>
--description="A package group of Pulp test files." \<br>
--mand-name=pulp-dot-2.0-test --mand-name=pulp-test-package</p>
<p>$ pulp-admin rpm repo uploads group --repo-id=repo_1 \<br>
--group-id=pulp_dotted_name_packages --name="Pulp Dotted Name Packages" \<br>
--description="A group of packages that have dots in their names." \<br>
--mand-name=pulp-dot-2.0-test</p>
<p>And now we can create a package environment that is a collection of these two groups:</p>
<p>$ pulp-admin rpm repo uploads environment --repo-id repo_1 --environment-id test-env \<br>
--name test-env --description test-env --group pulp_dotted_name_packages \<br>
--group pulp_test_packages</p>
<p><span><del>--------------------------------------------------------------------</del></span><br>
Unit Upload<br>
<span><del>--------------------------------------------------------------------</del></span></p>
<p>Extracting necessary metadata for each request...<br>
... completed</p>
<p>Creating upload requests on the server...<br>
[==================================================] 100%<br>
Initializing upload<br>
... completed</p>
<p>Starting upload of selected units. If this process is stopped through ctrl+c,<br>
the uploads will be paused and may be resumed later using the resume command or<br>
canceled entirely using the cancel command.</p>
<p>Importing into the repository...<br>
This command may be exited via ctrl+c without affecting the request.</p>
<p>[\]<br>
Running...</p>
<p>Task Succeeded</p>
<p>Deleting the upload request...<br>
... completed</p>
<p>The package environment details can be listed as well:</p>
<p>$ pulp-admin rpm repo content environment --repo-id repo_1 --match id=test-env</p>
<p>Description: test-env<br>
Group Ids: pulp_dotted_name_packages, pulp_test_packages<br>
Id: test-env<br>
Name: test-env<br>
Options:</p>
<p>Note</p>
<p>Package environments will also be created and associated with a repository if they are specified in a comps file and you Upload a comps.xml file.<br>
Copying Package Environments</p>
<p>Like package groups, environments can be copied between repos, which will bring along their groups. Assuming you've performed the steps from the :ref:`creating_package_environments` section, let's begin by creating an empty second repo:</p>
<p>$ pulp-admin rpm repo create --repo-id=repo_2<br>
Successfully created repository [repo_2]</p>
<p>Now let's copy test-env from repo_1 to repo_2:</p>
<p>$ pulp-admin rpm repo copy environment --match id=test-env \<br>
--from-repo-id=repo_1 --to-repo-id=repo_2<br>
Progress on this task can be viewed using the commands under "repo tasks".</p>
<p>Note</p>
<p>Use the --recursive flag to copy any dependencies of units being copied from the source repo into the destination repo.</p>
<p>Observe that repo_2 contains newly copied package environment:</p>
<p>$ pulp-admin repo list --repo-id repo_2</p>
<p><span><del>--------------------------------------------------------------------</del></span><br>
Repositories<br>
<span><del>--------------------------------------------------------------------</del></span></p>
<p>Id: repo_2<br>
Display Name: None<br>
Description: None<br>
Content Unit Counts:<br>
Package Environment: 1</p>
<p>Package Langpacks<br>
Creating Package Langpacks</p>
<p>You can also define your own package langpacks with the :command:`pulp_admin` utility. Let's create and sync a repo:</p>
<p>$ pulp-admin rpm repo create --repo-id=repo_1</p>
<p>Now let's build a package langpacks entry for the hyphen package:</p>
<p>$ pulp-admin rpm repo uploads langpacks <del>i hyphen -n hyphen</del>%s --repo-id repo_1<br>
<span><del>--------------------------------------------------------------------</del></span><br>
Unit Upload<br>
<span><del>--------------------------------------------------------------------</del></span></p>
<p>Extracting necessary metadata for each request...<br>
... completed</p>
<p>Creating upload requests on the server...<br>
[==================================================] 100%<br>
Initializing upload<br>
... completed</p>
<p>Starting upload of selected units. If this process is stopped through ctrl+c,<br>
the uploads will be paused and may be resumed later using the resume command or<br>
canceled entirely using the cancel command.</p>
<p>Importing into the repository...<br>
... completed</p>
<p>Deleting the upload request...<br>
... completed</p>
<p>We can see that the package langpacks is now part of our repo:</p>
<p>$ pulp-admin rpm repo content langpacks --repo-id=repo_1<br>
Matches:<br>
Install: hyphen<br>
Name: hyphen-%s</p>
<p>[root@ibm-x3550m3-12 ~]# pulp-admin rpm repo uploads langpacks <del>i test1 -n test1</del>%s --repo-id repo_1<br>
<span><del>--------------------------------------------------------------------</del></span><br>
Unit Upload<br>
<span><del>--------------------------------------------------------------------</del></span></p>
<p>Extracting necessary metadata for each request...<br>
... completed</p>
<p>Creating upload requests on the server...<br>
[==================================================] 100%<br>
Initializing upload<br>
... completed</p>
<p>Starting upload of selected units. If this process is stopped through ctrl+c,<br>
the uploads will be paused and may be resumed later using the resume command or<br>
canceled entirely using the cancel command.</p>
<p>Importing into the repository...<br>
This command may be exited via ctrl+c without affecting the request.</p>
<p>[\]<br>
Running...</p>
<p>Task Succeeded</p>
<p>[root@ibm-x3550m3-12 ~]# pulp-admin rpm repo content langpacks --repo-id=repo_1<br>
Matches:<br>
Install: test<br>
Name: test-%s</p> Packaging - Issue #1401 (CLOSED - WONTFIX): Dead link for installation doc https://pulp.plan.io/issues/14012015-12-07T21:00:49Zpthomas@redhat.com
<p>The following page does not exist<br>
<a href="https://pulp-user-guide.readthedocs.org/en/latest/installation.html" class="external">https://pulp-user-guide.readthedocs.org/en/latest/installation.html</a></p>
<p>But is referenced from</p>
<p>The following link is referenced from <a href="https://github.com/pulp/pulp_packaging/blob/master/dockerfiles/docker-quickstart.rst#deployment-options" class="external">https://github.com/pulp/pulp_packaging/blob/master/dockerfiles/docker-quickstart.rst#deployment-options</a></p> Pulp - Task #1333 (CLOSED - WONTFIX): Document that syncs give up if network failshttps://pulp.plan.io/issues/13332015-10-23T16:25:59Zpthomas@redhat.com
<p>As shown below, if a network error occurs during a sync and several requests fail, the sync will skip the rest of its downloads. This is good, because trying to make thousands more requests to a struggling or missing remote service could take a lot of time, could make that remove service's problems worse, and is unlikely to succeed.</p>
<p>It would be helpful to document that behavior. I think this logic is in nectar, so most importers will behave this way. Here is an example of that behavior "in the wild":</p>
<pre><code>[root@ibm-x3550m3-06 ~]# rpm -qa pulp-server
pulp-server-2.7.0-0.7.beta.el7.noarch
[root@ibm-x3550m3-06 ~]#
</code></pre>
<pre><code>[root@ibm-x3550m3-06 ~]# pulp-admin node sync run --node-id node1
This command may be exited via ctrl+c without affecting the request.
[-]
Accepted...
(1/1) Repository: centos
[==== ] 9%
Error occurred during synchronization, check the child node logs for details
+----------------------------------------------------------------------+
Child Node Synchronization
+----------------------------------------------------------------------+
Repository:
Action: Merged
Content Sources:
Downloads:
Source Id: Parent Node
Total Failed: 4611
Total Succeeded: 490
Total Sources: 0
Id: centos
Units:
Added: 490
Removed: 0
Updated: 0
+----------------------------------------------------------------------+
The following [4611] errors were reported
+----------------------------------------------------------------------+
- 01: Received error [A connection error occurred] while downloading a unit file
at URL
[https://ibm-x3550m3-06.lab.eng.brq.redhat.com/pulp/nodes/https/repos/centos/con
tent/rpm/evolution-mapi-devel/3.8.5/6.el7/i686/ec7af664520b926516f473cf086388373
14ad9d5bc2a03af79d945228d49f7ca/evolution-mapi-devel-3.8.5-6.el7.i686.rpm] for
repository [centos]. The cause could be that the repository has not been
published.
- 02: Received error [Download skipped] while downloading a unit file at URL
[https://ibm-x3550m3-06.lab.eng.brq.redhat.com/pulp/nodes/https/repos/centos/con
tent/rpm/OpenEXR/1.7.1/7.el7/x86_64/4abca5307be39571089dd481eeb307bcf29fbb473629
005cae5721079108546a/OpenEXR-1.7.1-7.el7.x86_64.rpm] for repository [centos].
The cause could be that the repository has not been published.
- 03: Received error [Download skipped] while downloading a unit file at URL
[https://ibm-x3550m3-06.lab.eng.brq.redhat.com/pulp/nodes/https/repos/centos/con
tent/rpm/texlive-charter-doc/svn15878.0/32.el7/noarch/e068aee3536f1e724610ebe09b
d9c077fa82275d147df9a45e55abead8e18ddd/texlive-charter-doc-svn15878.0-32.el7.noa
rch.rpm] for repository [centos]. The cause could be that the repository has not
been published.
- 04: Received error [Download skipped] while downloading a unit file at URL
[https://ibm-x3550m3-06.lab.eng.brq.redhat.com/pulp/nodes/https/repos/centos/con
tent/rpm/mythes-uk/1.6.5/6.el7/noarch/753a0d54ce20196ac1cc61914258f38f8f3cd13f9d
a280fc562f59c9b503062a/mythes-uk-1.6.5-6.el7.noarch.rpm] for repository
[centos]. The cause could be that the repository has not been published.
- 05: Received error [Download skipped] while downloading a unit file at URL
[https://ibm-x3550m3-06.lab.eng.brq.redhat.com/pulp/nodes/https/repos/centos/con
tent/rpm/libbluray-devel/0.2.3/5.el7/x86_64/424fbab8446ab76bab7454ddac4b98daa6aa
b71f461ec672cdaf0de84c8c99a5/libbluray-devel-0.2.3-5.el7.x86_64.rpm] for
repository [centos]. The cause could be that the repository has not been
published.
- 06: Received error [Download skipped] while downloading a unit file at URL
[https://ibm-x3550m3-06.lab.eng.brq.redhat.com/pulp/nodes/https/repos/centos/con
tent/rpm/libgnome/2.32.1/9.el7/i686/59c0d5006cc901129acecaee16f7cfdda57873d8c520
ace99c63ac6036124203/libgnome-2.32.1-9.el7.i686.rpm] for repository [centos].
The cause could be that the repository has not been published.
- 07: Received error [Download skipped] while downloading a unit file at URL
[https://ibm-x3550m3-06.lab.eng.brq.redhat.com/pulp/nodes/https/repos/centos/con
tent/rpm/alsa-plugins-vdownmix/1.0.27/3.el7/i686/ffd0f28a6540ec51b9abc6843caa1f3
a461554097b5bf49044f0f55bb8fe18ca/alsa-plugins-vdownmix-1.0.27-3.el7.i686.rpm]
for repository [centos]. The cause could be that the repository has not been
published.
</code></pre> Pulp - Issue #1247 (CLOSED - WONTFIX): Updating the feed still publishes the repo to the old feedhttps://pulp.plan.io/issues/12472015-09-11T13:22:00Zpthomas@redhat.com
<p>Created a repo with an invalid feed and tried to sync the repo. The sync failed. Now updated the repo to the correct feed and synced repo again. The relative path it published the repo to is still the old one.</p>
<p>[root@mgmt4 ~]#<br>
[root@mgmt4 ~]# rpm -qa pulp-server<br>
pulp-server-2.7.0-0.4.beta.el7.noarch<br>
[root@mgmt4 ~]#</p>
<p>Steps</p>
<p>1. create a repo with<br>
pulp-admin rpm repo create --repo-id rhel6 --feed n.redhat.com/content/dist/rhel/server/6/6.6/x86_64/ --feed-ca-cert CDN/cdn.redhat.com-chain.crt --feed-cert CDN/b655c0445cf57cef7e75ba574e48f26a.crt --feed-key CDN/b655c0445cf57cef7e75ba574e48f26a.key</p>
<p>2. Run repo sync</p>
<p>Repo sync fails</p>
<p>3. pulp-admin rpm repo update --repo-id rhel6 --feed <a href="https://cdn.redhat.com/content/dist/rhel/server/6/6.6/x86_64/os" class="external">https://cdn.redhat.com/content/dist/rhel/server/6/6.6/x86_64/os</a></p>
<p>Run repo sync</p>
<p>4. [root@mgmt4 ~]# ls <del>l /var/lib/pulp/published/yum/https/repos/<br>
total 4<br>
-rw-r--r-</del>. 1 apache apache 18 Sep 11 08:47 listing<br>
drwxr-x---. 3 apache apache 34 Sep 11 08:47 n.redhat.com<br>
drwxr-x---. 3 apache apache 31 Sep 10 12:10 repos<br>
[root@mgmt4 ~]#</p> Pulp - Issue #1174 (CLOSED - WONTFIX): The help text for remove needs to be rewordedhttps://pulp.plan.io/issues/11742015-08-12T14:14:35Zpthomas@redhat.com
<p>Help text for remove says "remove copied or uploaded modules from a repository"</p>
<p>But we can remove synced content as well.</p>
<p>For rpm it says</p>
<p>remove copied or uploaded modules from a repository</p>
<p>For iso repo it says</p>
<p>remove copied or uploaded units from a repository</p> Pulp - Task #1130 (CLOSED - NOTABUG): File a bug against EPEL7: Mongodb not starting with selinux...https://pulp.plan.io/issues/11302015-07-09T17:29:45Zpthomas@redhat.com
<p>mongodb fails to start with selinux enabled on el7</p>
<pre><code>[root@lenovo-x3850-02 ~]# rpm -qa |grep mongo
mongodb-server-2.6.9-1.el7.x86_64
python-mongoengine-0.9.0-1.el7.noarch
python-pymongo-gridfs-2.7.2-1.el7.x86_64
python-pymongo-2.7.2-1.el7.x86_64
[root@lenovo-x3850-02 ~]#
</code></pre>
<pre><code>2015-07-08T13:24:02.305-0400 [initandlisten] ERROR: listen(): bind() failed errno:13 Permission denied for socket: /var/run/mongodb/mongodb-27017.sock
< type=AVC msg=audit(1436377400.894:300): avc: denied { setattr } for pid=29959 comm="mongod" name="mongodb-27017.sock" dev="tmpfs" ino=111763 scontext=system_u:system_r:mongod_t:s0 tcontext=system_u:object_r:mongod_var_run_t:s0 tclass=sock_file
</code></pre> Pulp - Issue #1057 (CLOSED - WONTFIX): CLI returns unclear error for nonexistant role-id in permi...https://pulp.plan.io/issues/10572015-06-16T14:04:30Zpthomas@redhat.com
<pre><code>[root@celeno ~]# rpm -qa pulp-server
pulp-server-2.7.0-0.3.beta.el6.noarch
[root@celeno ~]#
</code></pre>
<p>The property name in the help for permission grant/revoke is role-id but gives the invalid property error.</p>
<pre><code> manipulated
--login - login of the user to which access to given resource is being
granted
--role-id - id of the role to which access to given resource is being granted
-o - (required) type of permissions being granted, valid permissions:
create, read, update, delete, execute
[root@celeno ~]# pulp-admin auth permission grant --role-id test --resource / -o READ
Invalid properties: ['role_id']
[root@celeno ~]# pulp-admin auth permission grant --role_id test --resource / -o READ
Command: grant
Description: grants resource permissions to given user or given role
Usage: you can specify either login or role-id in this command; both cannot be
specified at the same time
Available Arguments:
--resource - (required) resource REST API path whose permissions are being
manipulated
--login - login of the user to which access to given resource is being
granted
--role-id - id of the role to which access to given resource is being granted
-o - (required) type of permissions being granted, valid permissions:
create, read, update, delete, execute
The following options were specified but do not exist on the command:
--role_id
</code></pre>
<pre><code>[root@celeno ~]# pulp-admin auth permission revoke --role_id test --resource / -o READ
Command: revoke
Description: revokes resource permissions from given user or given role
Usage: you can specify either login or role-id in this command; both cannot be
specified at the same time
Available Arguments:
--resource - (required) resource REST API path whose permissions are being
manipulated
--login - login of the user from which access to given resource is being
revoked
--role-id - id of the role from which access to given resource is being
revoked
-o - (required) type of permissions being revoked, valid permissions:
create, read, update, delete, execute
The following options were specified but do not exist on the command:
--role_id
[root@celeno ~]# pulp-admin auth permission revoke --role-id test --resource / -o READ
Invalid properties: ['role_id']
</code></pre> Pulp - Issue #667 (CLOSED - CURRENTRELEASE): orphan remove by type does not validate the type pr...https://pulp.plan.io/issues/6672015-02-28T23:19:49Zpthomas@redhat.com
<p>Description of problem:</p>
<p>orphan remove --type does not validate the --type</p>
<p>Version-Release number of selected component (if applicable):<br>
[root@rhsm-jenkins ~]# rpm -qa pulp-server<br>
pulp-server-2.5.2-0.3.beta.el6.noarch<br>
[root@rhsm-jenkins ~]#</p>
<p>How reproducible:</p>
<p>Steps to Reproduce:<br>
1. Delete a repo that has some content<br>
2. Try to run orphan remove by --type but provide a random name for the type<br>
3.</p>
<p>Actual results:<br>
[root@rhsm-jenkins ~]# pulp-admin orphan remove --type foo<br>
This command may be exited via ctrl+c without affecting the request.</p>
<p>[\]<br>
Running...</p>
<p>Task Succeeded</p>
<p>Expected results:</p>
<p>Additional info:</p>
<p>+ This bug was cloned from <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1183072" class="external">Bugzilla Bug #1183072</a> +</p> Pulp - Issue #665 (CLOSED - CURRENTRELEASE): rpm recipe doc has --erratum_id instead of erratum-idhttps://pulp.plan.io/issues/6652015-02-28T23:19:40Zpthomas@redhat.com
<p>Document URL:<br>
<a href="https://pulp-rpm-user-guide.readthedocs.org/en/latest/recipes.html" class="external">https://pulp-rpm-user-guide.readthedocs.org/en/latest/recipes.html</a></p>
<p>Section Number and Name:</p>
<p><a href="https://pulp-rpm-user-guide.readthedocs.org/en/latest/recipes.html#create-your-own-errata" class="external">https://pulp-rpm-user-guide.readthedocs.org/en/latest/recipes.html#create-your-own-errata</a></p>
<p>Describe the issue:</p>
<p>The command is --erratum-id but the sample command says --erratum_id</p>
<p>Suggestions for improvement:</p>
<p>Additional information:</p>
<p>+ This bug was cloned from <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1183045" class="external">Bugzilla Bug #1183045</a> +</p> RPM Support - Story #251 (CLOSED - WONTFIX): [RFE] rpm uploads resume should be able to ignore ba...https://pulp.plan.io/issues/2512015-02-19T01:19:12Zpthomas@redhat.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1144081" class="external">Bugzilla Bug #1144081</a> +</span>+</p>
<p>Description of problem:</p>
<p>Description of problem: Attempting to resume or cancel a paused upload causes an unexpected error to occur</p>
<p>Version-Release number of selected component (if applicable):</p>
<p>pulp-server-2.5.0-0.1.alpha.el7.noarch<br>
pulp-admin-client-2.5.0-0.1.alpha.el7.noarch</p>
<p>How reproducible: Every time</p>
<p>Steps to Reproduce:<br>
1. Create a repo<br>
2. Start an rpm upload with 'pulp-admin rpm repo uploads rpm --repo-id= --file='<br>
3. Pause the upload with Ctrl+C<br>
4. Attempt to resume the upload with 'pulp-admin rpm repo uploads resume'<br>
5. Attempt to cancel</p>
<p>Actual results:<br>
[jcline@jcline ~]$ pulp-admin rpm repo uploads resume<br>
<span><del>--------------------------------------------------------------------</del></span><br>
Upload Requests<br>
<span><del>--------------------------------------------------------------------</del></span></p>
<p>An unexpected error has occurred. More information can be found in the client<br>
log file ~/.pulp/admin.log.</p>
<p>Expected results</p>
<p>Additional info:<br>
2014-09-18 10:44:12,929 - ERROR - Client-side exception occurred<br>
Traceback (most recent call last):<br>
File "/usr/lib/python2.7/site-packages/pulp/client/extensions/core.py", line 478, in run<br>
exit_code = Cli.run(self, args)<br>
File "/usr/lib/python2.7/site-packages/okaara/cli.py", line 974, in run<br>
exit_code = command_or_section.execute(self.prompt, remaining_args)<br>
File "/usr/lib/python2.7/site-packages/pulp/client/extensions/extensions.py", line 224, in execute<br>
return self.method(*arg_list, **clean_kwargs)<br>
File "/usr/lib/python2.7/site-packages/pulp/client/commands/repo/upload.py", line 647, in run<br>
source_filenames = [os.path.basename(u.source_filename) for u in non_running_uploads]<br>
File "/usr/lib64/python2.7/posixpath.py", line 121, in basename<br>
i = p.rfind('/') + 1<br>
AttributeError: 'NoneType' object has no attribute 'rfind'</p>
<p>--- Additional comment from <a href="mailto:pthomas@redhat.com" class="email">pthomas@redhat.com</a> at 09/18/2014 15:19:27 ---</p>
<p>This is the same issue as in which was reported in 2.3</p>
<p><a href="https://bugzilla.redhat.com/show_bug.cgi?id=973670" class="external">https://bugzilla.redhat.com/show_bug.cgi?id=973670</a></p>
<p>--- Additional comment from <a href="mailto:amacdona@redhat.com" class="email">amacdona@redhat.com</a> at 11/07/2014 18:16:30 ---</p>
<p>When I attempted this the first time, I saw a different error in the log.</p>
<p>2014-11-07 13:01:33,153 - ERROR - Client-side exception occurred<br>
Traceback (most recent call last):<br>
File "/home/austin/code/pulp/client_lib/pulp/client/extensions/core.py", line 478, in run<br>
exit_code = Cli.run(self, args)<br>
File "/usr/lib/python2.7/site-packages/okaara/cli.py", line 974, in run<br>
exit_code = command_or_section.execute(self.prompt, remaining_args)<br>
File "/home/austin/code/pulp/client_lib/pulp/client/extensions/extensions.py", line 224, in execute<br>
return self.method(*arg_list, **clean_kwargs)<br>
File "/home/austin/code/pulp/client_lib/pulp/client/commands/repo/upload.py", line 523, in run<br>
uploads = self.upload_manager.list_uploads()<br>
File "/home/austin/code/pulp/client_lib/pulp/client/upload/manager.py", line 319, in list_uploads<br>
tracker_file = UploadTracker.load(full_filename)<br>
File "/home/austin/code/pulp/client_lib/pulp/client/upload/manager.py", line 468, in load<br>
status_file = pickle.load(f)<br>
File "/usr/lib64/python2.7/pickle.py", line 1378, in load<br>
return Unpickler(file).load()<br>
File "/usr/lib64/python2.7/pickle.py", line 858, in load<br>
dispatch[key](self)<br>
File "/usr/lib64/python2.7/pickle.py", line 1147, in load_dup<br>
self.append(self.stack[-1])<br>
IndexError: list index out of range</p>
<p>I determined that the problem was that one of the files in ~/.pulp/uploads/rpm was invalid. The offending file was a single line:</p>
<p>~/.pulp/uploads/rpm/01e134c5-12fe-4892-bf02-bdc7e427572a</p>
<p>25602</p>
<p>After I moved this file, resume and cancel worked as expected. I could not reproduce the creation of this file, so I am not sure what caused it, perhaps an artifact from working with a previous bug? If that is the case, the errors could be different based on the invalid file.</p>
<p>I think that the way forward might be an additional flag for cancel, like one of these options:</p>
<pre><code>$ pulp-admin rpm repo uploads cancel --force
$ pulp-admin rpm repo uploads cancel --skip-invalid
</code></pre>
<p>Force on cancel would delete the invalid files.</p>
<p>If that is the way forward, I think that would mean no earlier than 2.6.</p>
<p>--- Additional comment from <a href="mailto:amacdona@redhat.com" class="email">amacdona@redhat.com</a> at 11/07/2014 22:26:30 ---</p>
<p>I am curious if you still are still getting this error. If so, could you try moving all your files in the ~/.pulp/uploads/repo directory and see if that solves it?</p>
<p>--- Additional comment from <a href="mailto:pthomas@redhat.com" class="email">pthomas@redhat.com</a> at 11/25/2014 15:30:10 ---</p>
<p>I was not able to reproduce it now with 2.5. But I do like your suggestions above since this has been an issue since 2.3</p> RPM Support - Story #198 (CLOSED - CURRENTRELEASE): [RFE] Need a cli option for copy/remove Yum R...https://pulp.plan.io/issues/1982015-02-19T01:11:23Zpthomas@redhat.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=976396" class="external">Bugzilla Bug #976396</a> +</span>+</p>
<p>Description of problem:</p>
<p>Description of problem:</p>
<p>It would be nice to have a cli copy/remove for the Yum Repo Metadata File content unit.</p>
<p>Version-Release number of selected component (if applicable):<br>
[root@ibm-x3550m3-13 ~]# rpm -q pulp-server<br>
pulp-server-2.2.0-0.4.beta.fc18.noarch<br>
[root@ibm-x3550m3-13 ~]#</p>
<p>How reproducible:</p>
<p>Steps to Reproduce:<br>
[root@ibm-x3550m3-13 ~]# pulp-admin rpm repo copy<br>
Usage: pulp-admin [SUB_SECTION, ..] COMMAND<br>
Description: copies one or more content units between repositories</p>
<p>Available Commands:<br>
all - copy all content units from one repository to another<br>
category - copy package categories from one repository to another<br>
distribution - copy distributions from one repository to another<br>
errata - copy errata from one repository to another<br>
group - copy package groups from one repository to another<br>
rpm - copy RPMs from one repository to another<br>
[root@ibm-x3550m3-13 ~]# pulp-admin rpm repo remove<br>
Usage: pulp-admin [SUB_SECTION, ..] COMMAND<br>
Description: remove copied or uploaded modules from a repository</p>
<p>Available Commands:<br>
category - remove package categories from a repository<br>
distribution - remove distributions from a repository<br>
drpm - remove DRPMs from a repository<br>
errata - remove errata from a repository<br>
group - remove package groups from a repository<br>
rpm - remove RPMs from a repository<br>
srpm - remove SRPMs from a repository<br>
[root@ibm-x3550m3-13 ~]#</p>
<p>Actual results:</p>
<p>Expected results:</p>
<p>Additional info:</p> Pulp - Story #193 (CLOSED - WONTFIX): [RFE] consumer group CLI should support errata and package ...https://pulp.plan.io/issues/1932015-02-19T01:11:04Zpthomas@redhat.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=969045" class="external">Bugzilla Bug #969045</a> +</span>+</p>
<p>Description of problem:</p>
<p>Description of problem:<br>
Looks like there is no support for errata and package group install on consumer group.</p>
<p>Version-Release number of selected component (if applicable):</p>
<p>pulp-server-2.1.2-0.1.beta.el6.noarch<br>
How reproducible:<br>
always</p>
<p>Steps to Reproduce:<br>
1.<br>
2.<br>
3.</p>
<p>Actual results:</p>
<p>Expected results:</p>
<p>Additional info:</p>
<p>--- Additional comment from <a href="mailto:pthomas@redhat.com" class="email">pthomas@redhat.com</a> at 05/30/2013 19:04:50 ---</p>
<p>Looks like the REST API is workig. CLI is missing though. Changing it for CLI</p>
<p>Here is POST for package group and errata install on consumer groups</p>
<p>pic.POST ('/v2/consumer_groups/consumer-grp/actions/content/install/',body={'units':[{'unit_key':{'name':'haskell'},'type_id':'package_group'}], 'options':{} })</p>
<p>pic.POST ('/v2/consumer_groups/consumer-grp/actions/content/install/',body={'units':[{'unit_key':{'id':'grinder_test_4'},'type_id':'erratum'}], 'options':{} })</p>
<p>--- Additional comment from <a href="mailto:jason.dobies@redhat.com" class="email">jason.dobies@redhat.com</a> at 06/05/2013 15:50:22 ---</p>
<p>Mike - I'm not sure this is a Katello blocker; it was recharacterized as a client only bug.</p>
<p>--- Additional comment from <a href="mailto:mmccune@redhat.com" class="email">mmccune@redhat.com</a> at 06/18/2013 22:14:43 ---</p>
<p>cleared sat6-blocker</p> Docker Support - Story #115 (CLOSED - WONTFIX): As a user, I can resume a paused upload for dockerhttps://pulp.plan.io/issues/1152015-01-20T02:10:56Zpthomas@redhat.com
<p>Docker uploads can be paused by Ctrl+C but there is no option available to resume the upload</p>
<p>[root@cloud-qe-17 docker]# pulp-admin docker repo create --repo-id busybox<br>
Repository [busybox] successfully created</p>
<p>[root@cloud-qe-17 docker]# pulp-admin docker repo uploads upload --repo-id=busybox --dir /root/docker/ -v<br>
<span>----------------------------------------------------------------------</span><br>
Unit Upload<br>
<span><del>--------------------------------------------------------------------</del></span></p>
<p>Extracting necessary metadata for each request...<br>
[==================================================] 100%<br>
Analyzing: busybox.tar<br>
... completed</p>
<p>Files to be uploaded:<br>
busybox.tar</p>
<p>Creating upload requests on the server...<br>
[==================================================] 100%<br>
Initializing: busybox.tar<br>
... completed</p>
<p>Starting upload of selected units. If this process is stopped through ctrl+c,<br>
the uploads will be paused and may be resumed later using the resume command or<br>
cancelled entirely using the cancel command.</p>
<p>Uploading: busybox.tar<br>
[=================== ] 39%<br>
1048576/2666496 bytes<br>
^CUploading paused</p>
<p>[root@cloud-qe-17 docker]# pulp-admin repo list<br>
<span><del>--------------------------------------------------------------------</del></span><br>
Repositories<br>
<span><del>--------------------------------------------------------------------</del></span></p>
<p>Id: epel5_1<br>
Display Name: epel5_1<br>
Description: None<br>
Content Unit Counts:<br>
Erratum: 1998<br>
Package Category: 5<br>
Package Group: 36<br>
Rpm: 6848<br>
Yum Repo Metadata File: 1</p>
<p>Id: busybox<br>
Display Name: busybox<br>
Description: None<br>
Content Unit Counts:</p>