Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-12-15T17:19:40ZPulp
Planio Maven Plugin - Issue #9640 (CLOSED - DUPLICATE): Missing Rest api link in docshttps://pulp.plan.io/issues/96402021-12-15T17:19:40Zwibbit
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_maven/54":<a href="https://github.com/pulp/pulp_maven/issues/54" class="external">https://github.com/pulp/pulp_maven/issues/54</a></p>
<hr>
<p><a href="https://docs.pulpproject.org/pulp_maven/" class="external">https://docs.pulpproject.org/pulp_maven/</a></p> Migration Plugin - Issue #9191 (CLOSED - DUPLICATE): Migrated advisories with dates-as-timestamps...https://pulp.plan.io/issues/91912021-08-02T19:37:16Zggainey
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp-2to3-migration/issues/483": <a href="https://github.com/pulp/pulp-2to3-migration/issues/483" class="external">https://github.com/pulp/pulp-2to3-migration/issues/483</a></p> RPM Support - Issue #9055 (CLOSED - CURRENTRELEASE): package group pulls in newer version of packagehttps://pulp.plan.io/issues/90552021-07-09T14:43:26Zquartsize
<p>I have a package exclusion filter in Katello to reject newer kernels for which I don't yet have compatible versions of out-of-tree modules, but I end up with the latest versions of the perf and kernel-tools packages because they are listed in the @performance and @core package groups, respectively.</p>
<p>So I'd like to propose that package groups only cause a package to be added if some version of the package wasn't already requested. I'm working on a patch.</p>
<p>I will also say, FWIW, that I wasn't expecting these sort of additions to be processed without depsolving enabled, such that my initial line of investigation started with the assumption that I must be accidentally enabling it somehow.</p> Pulp - Issue #9030 (CLOSED - CURRENTRELEASE): As a user I want consistent naming between the remo...https://pulp.plan.io/issues/90302021-07-08T07:35:13Zquba42
<p>See this community discussion: <a href="https://github.com/pulp/community/discussions/36" class="external">https://github.com/pulp/community/discussions/36</a></p>
<p>Note that while <code>retain_package_versions</code> currently comes from RPM only, <code>retained_versions</code> comes from pulpcore.</p>
<p>The state of the discussion is that renaming <code>retained_versions</code> to <code>retain_repo_versions</code> would be the most meaningful and consistent. Of course this does mean renaming a API option which can break existing scripts? I don't know to what extent it is possible/desirable to retain aliases for backwards compatibility in such cases.</p> Pulp - Issue #8994 (CLOSED - WONTFIX): The API docs for pulp-python on readthedocs.io are brokenhttps://pulp.plan.io/issues/89942021-06-30T14:24:52Zgsulliva
<p>The API docs for pulp-python at <a href="https://pulp-python.readthedocs.io/en/latest/restapi.html" class="external">https://pulp-python.readthedocs.io/en/latest/restapi.html</a> are no longer working due to the removal of the api.json file. The link to this page can be found at <a href="https://pulp-python.readthedocs.io/en/latest/restapi/index.html" class="external">https://pulp-python.readthedocs.io/en/latest/restapi/index.html</a> and the top of <a href="https://pulp-python.readthedocs.io/en/latest/index.html" class="external">https://pulp-python.readthedocs.io/en/latest/index.html</a>.</p> File Support - Issue #8838 (CLOSED - DUPLICATE): pulp file content upload: --chunk-size option sh...https://pulp.plan.io/issues/88382021-05-28T13:25:09Zvk
<p>Following up from IRC, this:</p>
<pre><code>pulp file content upload --chunk-size
</code></pre>
<p>currently takes a value whose unit is assumed to be bytes.</p>
<p>For larger values, it would be extremely useful to allow a unit to be specified, such as 'k', 'm', 'g' (or, if you think differentiating between powers of 10 vs powers of 2 is important, an alternate specifier). A simple approach might be to match nginx (that's how I ran into this, after modifying the client_max_body_size option). I'm new to pulp, so I don't know what other examples there are within pulp.</p> Debian Support - Issue #8645 (CLOSED - CURRENTRELEASE): Deprecation warnings with distributionhttps://pulp.plan.io/issues/86452021-04-28T14:17:39Zknzivid
<p>When I run the latest version of <code>pulp/pulp</code> image from docker, I notice these warnings when I use an apt distribution.</p>
<blockquote>
<p>pulp [None]: pulpcore.deprecation:WARNING: BaseDistribution is deprecated and could be removed as early as pulpcore==3.13; use pulpcore.plugin.models.Distribution instead.</p>
</blockquote>
<p>I am not sure if this is an pulp core issue or something in the pulp_deb plugin.</p> RPM Support - Issue #8287 (CLOSED - WORKSFORME): Rhel8 remote redhat repo showing Malformed repos...https://pulp.plan.io/issues/82872021-02-22T07:42:32Zmidhuhk
<p>Remote repo:
appstream-rhel8</p>
<p>data": {
"reason": "metadata is missing for some packages in filelists.xml and in other.xml"
},
"description": "Malformed repository: metadata is missing for some packages in filelists.xml and in other.xml",</p> Migration Plugin - Issue #8284 (CLOSED - WORKSFORME): pulp2content call with "erratum" as a param...https://pulp.plan.io/issues/82842021-02-19T16:03:39Ziballou
<p>The following API call causes a 500:</p>
<pre>
Feb 19 15:39:30 centos7-katello-devel-2 pulpcore-api: - - [19/Feb/2021:15:39:30 +0000] "GET /pulp/api/v3/pulp2content/?limit=2000&offset=0&pulp2_content_type_id=erratum&pulp2_last_updated__gt=0 HTTP/1.1" 500 27 "-" "OpenAPI-Generator/0.7.0/ruby"
</pre>
<p>It works just fine with "rpm", however.</p>
<p>I noticed this issue on 0.6.0 and 0.7.0.
I'm on pulp-rpm 3.8.0 and pulpcore 3.9.0.</p>
<p>Unfortunately there was no stack trace to go along with the 500.</p>
<p>The issue went away after I reset my environment. I am not sure how the issue could be reproduced since I bet it was related to stale data in my aging pulpcore database. I'm leaving this bug here in case someone hits it in the future.</p> Container Support - Issue #8224 (CLOSED - DUPLICATE): Remove # coding=utf-8 from our testshttps://pulp.plan.io/issues/82242021-02-08T16:36:39Zggainey
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_container/486":<a href="https://github.com/pulp/pulp_container/issues/486" class="external">https://github.com/pulp/pulp_container/issues/486</a></p>
<hr>
<p>Python3 defaults to utf8 now.</p> Pulp - Issue #8001 (CLOSED - DUPLICATE): Warnings when requesting /pulp/api/v3/docs/https://pulp.plan.io/issues/80012020-12-15T23:02:36Zgerrod
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/1954":<a href="https://github.com/pulp/pulpcore/issues/1954" class="external">https://github.com/pulp/pulpcore/issues/1954</a></p>
<hr>
<p>After setting up a fresh pulp3-source-fedora31 vagrant box I tested Pulp's functionality by doing http requests to /pulp/api/v3/status/ and /pulp/api/v3/docs/ and noticed some weird warning messages in pjournal.</p>
<p>For /pulp/api/v3/status/</p>
<pre><code>Dec 15 22:24:25 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: Warning #0: type hint for function "get_pulp_href" is unknown. consider using a type hint or @extend_schema_field. defaulting to string.
Dec 15 22:24:25 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: Warning #1: type hint for function "get_id" is unknown. consider using a type hint or @extend_schema_field. defaulting to string.
Dec 15 22:24:25 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: Warning #2: trying to re-register a schemas component with name PaginatedPermissionResponseList. this might lead to a incorrect schema. Look out for reused names
Dec 15 22:24:25 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: Error #0: Unable to guess serializer for RepairView. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class, if view is under your control. ignoring view for now.
Dec 15 22:24:25 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: Warning #3: trying to re-register a schemas component with name PaginatedRepositoryVersionResponseList. this might lead to a incorrect schema. Look out for reused names
Dec 15 22:24:25 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: pulp [None]: django_guid:INFO: Header `Correlation-ID` was not found in the incoming request. Generated new GUID: 74c3bfda95694f6cb9bd65f87d9fcdb8
Dec 15 22:24:25 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: pulp [74c3bfda95694f6cb9bd65f87d9fcdb8]: 127.0.0.1 - admin [15/Dec/2020:22:24:25 +0000] "GET /pulp/api/v3/status/ HTTP/1.0" 200 1218 "-" "HTTPie/2.3.0"
</code></pre>
<p>For /pulp/api/v3/docs/</p>
<pre><code>Dec 15 22:22:21 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: pulp [None]: django_guid:INFO: Header `Correlation-ID` was not found in the incoming request. Generated new GUID: 27d2817b80814a6e8bbe15194ffbfbe0
Dec 15 22:22:21 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: pulp [27d2817b80814a6e8bbe15194ffbfbe0]: 127.0.0.1 - - [15/Dec/2020:22:22:21 +0000] "GET /pulp/api/v3/docs/ HTTP/1.1" 200 652 "-" "Mozilla/5.0 (X11; Fed
ora; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0"
Dec 15 22:22:21 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: pulp [None]: django_guid:INFO: Header `Correlation-ID` was not found in the incoming request. Generated new GUID: b64a4cc7f5d5472eb587c2b17890dcdb
Dec 15 22:22:22 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: pulp [b64a4cc7f5d5472eb587c2b17890dcdb]: 127.0.0.1 - - [15/Dec/2020:22:22:22 +0000] "GET /pulp/api/v3/docs/api.json HTTP/1.1" 200 525840 "http://localho
st:24817/pulp/api/v3/docs/" "Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0"
Dec 15 22:23:10 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: Warning #0: type hint for function "get_pulp_href" is unknown. consider using a type hint or @extend_schema_field. defaulting to string.
Dec 15 22:23:10 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: Warning #1: type hint for function "get_id" is unknown. consider using a type hint or @extend_schema_field. defaulting to string.
Dec 15 22:23:10 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: Warning #2: trying to re-register a schemas component with name PaginatedPermissionResponseList. this might lead to a incorrect schema. Look out for reu
sed names
Dec 15 22:23:10 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: Error #0: Unable to guess serializer for RepairView. This is graceful fallback handling for APIViews. Consider using GenericAPIView as view base class,
if view is under your control. ignoring view for now.
Dec 15 22:23:10 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: Warning #3: trying to re-register a schemas component with name PaginatedRepositoryVersionResponseList. this might lead to a incorrect schema. Look out
for reused names
Dec 15 22:23:10 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: pulp [None]: django_guid:INFO: Header `Correlation-ID` was not found in the incoming request. Generated new GUID: f892c703764d45f9b29a50b5846b1072
Dec 15 22:23:10 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: pulp [f892c703764d45f9b29a50b5846b1072]: 127.0.0.1 - - [15/Dec/2020:22:23:10 +0000] "GET /pulp/api/v3/docs/ HTTP/1.1" 200 652 "-" "Mozilla/5.0 (X11; Fed
ora; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0"
Dec 15 22:23:11 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: pulp [None]: django_guid:INFO: Header `Correlation-ID` was not found in the incoming request. Generated new GUID: 1384361ebe364c74a3a423afd390525d
Dec 15 22:23:11 pulp3-source-fedora31.localhost.example.com gunicorn[36701]: pulp [1384361ebe364c74a3a423afd390525d]: 127.0.0.1 - - [15/Dec/2020:22:23:11 +0000] "GET /pulp/api/v3/docs/api.json HTTP/1.1" 200 525840 "http://localho
st:24817/pulp/api/v3/docs/" "Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0"
</code></pre>
<p>After repeating the requests the warning messages no longer show up. The requests completed fine and the responses were correct. My Pulp install was using pulpcore 3.10.0.dev0, with Python plugin 3.0.0b13.dev0 and File plugin 1.5.0.dev0</p> Pulp - Issue #7888 (CLOSED - CURRENTRELEASE): Can't update Fields through Rest API We pages (PUT ...https://pulp.plan.io/issues/78882020-11-23T15:20:06Zequipe_serveurs@exane.com
<p>Using rest api on pulp (PUT Request), I current Get the following error raised</p>
<p>{
"detail": "CSRF Failed: CSRF token missing or incorrect."
}</p>
<a name="Investigation"></a>
<h2 >Investigation<a href="#Investigation" class="wiki-anchor">¶</a></h2>
<ol>
<li>
<p>The root cause of this issue comes from the X-CRRFToken been checked but not sent through the Ajax Call</p>
</li>
<li>
<p>Source of this check comes from the authentication scheme in place (SessionAuthentication) (cf settings.py)
'DEFAULT_AUTHENTICATION_CLASSES': [
'rest_framework.authentication.SessionAuthentication',
'rest_framework.authentication.BasicAuthentication',
]</p>
</li>
</ol> Pulp - Issue #7760 (CLOSED - DUPLICATE): Multiple errors in documentation https://pulp.plan.io/issues/77602020-10-28T09:59:57Zlboclboc
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/1939":<a href="https://github.com/pulp/pulpcore/issues/1939" class="external">https://github.com/pulp/pulpcore/issues/1939</a></p>
<hr>
<p>Several errors in the exposing-content.rst document.
Pull-request coming shortly to fix this.</p> Docker Support - Issue #7697 (CLOSED - WONTFIX): docker repo_repository_id name restrictions seem...https://pulp.plan.io/issues/76972020-10-12T20:03:36Zjpasqualetto
<p>While the code states that:</p>
<p>" Docker registry repos are restricted to lower case letters, numbers, hyphens, underscores, and
periods. Additionally, we allow a single slash for namespacing purposes."</p>
<p>pulp is returning error for any docker_registry_id containing this sequence of characters:</p>
<pre><code> _-_
</code></pre>
<p>Example:</p>
<pre><code># pulp-admin docker repo create --repo-id=docker_test --repo-registry-id "my_-_repo"
A validation error occurred.
The value specified for repo-registry-id: 'my_-_repo' is invalid. Registry id
must contain only lower case letters, integers, hyphens, periods, and may
include a single slash.
</code></pre>
<p>Also, the error message doesn't say anything about accepting underscores.</p> Debian Support - Issue #7390 (CLOSED - DUPLICATE): As a user i want to upload package to a reposi...https://pulp.plan.io/issues/73902020-08-25T14:37:40Zmntzn
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_deb/393":<a href="https://github.com/pulp/pulp_deb/issues/393" class="external">https://github.com/pulp/pulp_deb/issues/393</a></p>
<hr>
<p>Current workflow is to:</p>
<ol>
<li>
<p>upload content (package)</p>
</li>
<li>
<p>add content to repo</p>
</li>
<li>
<p>create publication from repo</p>
</li>
<li>
<p>create/update distribution with latest publication</p>
</li>
</ol>
<p>Steps 3, 4 can be omitted and package that have been uploaded to a repository should be immediately available in distribution (as alternative to current workflow)</p>