Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-08-26T12:31:31ZPulp
Planio Debian Support - Issue #9299 (CLOSED - CURRENTRELEASE): Resolve Django 3 async issueshttps://pulp.plan.io/issues/92992021-08-26T12:31:31Zquba42
<p>Pulpcore 3.15 will be based on <code>Django~=3.2.6</code> which does not play nice with the current async implementation.</p> Debian Support - Task #9175 (CLOSED - CURRENTRELEASE): Backport 9162 to 2.14https://pulp.plan.io/issues/91752021-07-29T09:20:22Zquba42
<p><a href="https://github.com/pulp/community/discussions/59" class="external">https://github.com/pulp/community/discussions/59</a></p> Debian Support - Issue #9164 (CLOSED - CURRENTRELEASE): Dropping Python 3.6 and 3.7 from the 2.14...https://pulp.plan.io/issues/91642021-07-28T11:43:11Zquba42
<p>It looks like this was merged prematurely on my part.</p>
<p>Users have reported the following:</p>
<pre><code>I tried to update pulp_deb plugins using ansible but getting error as per below.
TASK [pulp.pulp_installer.pulp_common : Install prerequisites] ******************************************************************************************************************************************************************************
fatal: [pulptest008.karmalab.net]: FAILED! => {"changed": false, "msg": "No package matching 'rh-python38-python' found available, installed or updated", "rc": 126, "results": ["python-setuptools-0.9.8-7.el7.noarch providing python-setuptools is already installed", "No package matching 'rh-python38-python' found available, installed or updated"]}
</code></pre>
<p>Fresh installs are also suffering weird dependency effects where Python 3 is not being installed at all.</p> Debian Support - Task #9162 (CLOSED - CURRENTRELEASE): Comply with orphan clean changes made in p...https://pulp.plan.io/issues/91622021-07-28T08:52:57Zquba42
<p><a href="https://github.com/pulp/community/discussions/59" class="external">https://github.com/pulp/community/discussions/59</a></p> RPM Support - Issue #9107 (CLOSED - CURRENTRELEASE): filelists and changelog metadata is not pars...https://pulp.plan.io/issues/91072021-07-17T22:47:54Zoptiz0r
<p>Versions:</p>
<ul>
<li>Foreman 2.5.2</li>
<li>Katello 4.1.1</li>
<li>pulp-rpm-3.13.3</li>
</ul>
<p>Upstream: <a href="http://lon.mirror.rackspace.com/almalinux/8/BaseOS/x86_64/os/repodata/" class="external">http://lon.mirror.rackspace.com/almalinux/8/BaseOS/x86_64/os/repodata/</a>.</p>
<p>I am seeing filelists not being parsed correctly for Alma Linux repositories. Within Katello UI, I have checked a random sample of packages from all of the Alma repositories I have sync'd (18 in total, x86_64, sources and debug-x86_64 for each of baseos, appstream, highavailability, powertools, extras and devel), and none of them list any files. For comparison, CentOS 8 Stream RPMS do list files.</p>
<p>The generated filelist served up by katello contains each of the packages in the repo but with no package contents. For example, the upstream baseos filelist is 2MB whereas the generated filelist for the katello-hosted repo is just 105KB and looks like the below:</p>
<pre><code class="xml syntaxhl" data-language="xml"><span class="cp"><?xml version="1.0" encoding="UTF-8"?></span>
<span class="nt"><filelists</span> <span class="na">xmlns=</span><span class="s">"http://linux.duke.edu/metadata/filelists"</span> <span class="na">packages=</span><span class="s">"1985"</span><span class="nt">></span>
<span class="nt"><package</span> <span class="na">pkgid=</span><span class="s">"59c2172d6e423d8adc3248c1983146492471678afccdfae8ab0f66e18a1aaaa5"</span> <span class="na">name=</span><span class="s">"kernel-debug"</span> <span class="na">arch=</span><span class="s">"x86_64"</span><span class="nt">></span>
<span class="nt"><version</span> <span class="na">epoch=</span><span class="s">"0"</span> <span class="na">ver=</span><span class="s">"4.18.0"</span> <span class="na">rel=</span><span class="s">"305.el8"</span><span class="nt">/></span>
<span class="nt"></package></span>
<span class="nt"><package</span> <span class="na">pkgid=</span><span class="s">"c8120b541261d0ad425f369b1da5eef0aaad5883760ad0e149137027d102207c"</span> <span class="na">name=</span><span class="s">"avahi"</span> <span class="na">arch=</span><span class="s">"i686"</span><span class="nt">></span>
<span class="nt"><version</span> <span class="na">epoch=</span><span class="s">"0"</span> <span class="na">ver=</span><span class="s">"0.7"</span> <span class="na">rel=</span><span class="s">"20.el8"</span><span class="nt">/></span>
<span class="nt"></package></span>
</code></pre>
<p>This is breaking system installs which use the local mirrored content, because packages included in the kickstart base package set have dependencies specified using files, and these are all unsatisfied due to the empty filelists. I have triggered resyncs from upstream mirrors without any change in behaviour.</p>
<p>May be related to similar-looking issue <a class="issue tracker-1 status-11 priority-6 priority-default closed" title="Issue: Filelists and changlogs not always parsed properly (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/8955">#8955</a> ?</p> Debian Support - Task #8682 (CLOSED - CURRENTRELEASE): Migrate to new Distribution model for pulp...https://pulp.plan.io/issues/86822021-05-03T12:21:35Zquba42Debian Support - Issue #8671 (CLOSED - CURRENTRELEASE): Sync with Main Debian Repo fails on a tra...https://pulp.plan.io/issues/86712021-04-30T08:43:16Ztp-hlawatsch
<p>Hello everybody,</p>
<p>we plan to use pulp as our main tool for repos . We testing at the moment Debian mirroring
Our pulp testinstance is runing with the latest offical docker image</p>
<p>This is the configured remote repo</p>
<p>{
"name": "debian",
"url": "<a href="http://ftp.de.debian.org/debian/" class="external">http://ftp.de.debian.org/debian/</a>",
"ca_cert": null,
"client_cert": null,
"client_key": null,
"tls_validation": false,
"proxy_url": null,
"proxy_username": null,
"proxy_password": null,
"username": null,
"password": null,
"pulp_labels": {},
"download_concurrency": "10",
"policy": "immediate",
"total_timeout": null,
"connect_timeout": null,
"sock_connect_timeout": null,
"sock_read_timeout": null,
"rate_limit": null,
"distributions": "buster",
"components": "main",
"architectures": "amd64",
"sync_sources": false,
"sync_udebs": false,
"sync_installer": false,
"gpgkey": null,
"ignore_missing_package_indices": false
}</p>
<p>the sync run in to the following error</p>
<p>{
"pulp_href": "/pulp/api/v3/tasks/a7bd851b-f001-4f5f-89eb-0e0de529a556/",
"pulp_created": "2021-04-30T07:53:11.537345Z",
"state": "failed",
"name": "pulp_deb.app.tasks.synchronizing.synchronize",
"logging_cid": "00de2125667f4c7e8b8e01554c401eeb",
"started_at": "2021-04-30T07:53:11.648803Z",
"finished_at": "2021-04-30T07:53:19.135647Z",
"error": {
"traceback": " File "/usr/local/lib/python3.6/site-packages/rq/worker.py", line 1008, in perform_job\n rv = job.perform()\n File "/usr/local/lib/python3.6/site-packages/rq/job.py", line 706, in perform\n self._result = self._execute()\n File "/usr/local/lib/python3.6/site-packages/rq/job.py", line 729, in _execute\n result = self.func(*self.args, **self.kwargs)\n File "/usr/local/lib/python3.6/site-packages/pulp_deb/app/tasks/synchronizing.py", line 122, in synchronize\n DebDeclarativeVersion(first_stage, repository, mirror=mirror).create()\n File "/usr/local/lib/python3.6/site-packages/pulpcore/plugin/stages/declarative_version.py", line 149, in create\n loop.run_until_complete(pipeline)\n File "/usr/lib64/python3.6/asyncio/base_events.py", line 484, in run_until_complete\n return future.result()\n File "/usr/local/lib/python3.6/site-packages/pulpcore/plugin/stages/api.py", line 225, in create_pipeline\n await asyncio.gather(*futures)\n File "/usr/local/lib/python3.6/site-packages/pulpcore/plugin/stages/api.py", line 43, in <strong>call</strong>\n await self.run()\n File "/usr/local/lib/python3.6/site-packages/pulpcore/plugin/stages/artifact_stages.py", line 266, in run\n RemoteArtifact.objects.bulk_get_or_create(self._needed_remote_artifacts(batch))\n File "/usr/local/lib/python3.6/site-packages/pulpcore/plugin/stages/artifact_stages.py", line 324, in _needed_remote_artifacts\n msg.format(rp=content_artifact.relative_path, c=d_content.content)\n",
"description": "No declared artifact with relative path "dists/buster/main/i18n/Translation-ml.bz2" for content """
},</p>
<p>We do not see a misconfiguration on our side so I raised this issue here</p>
<p>Regards
Stephan Hlawatsch</p> Pulp - Issue #8625 (CLOSED - CURRENTRELEASE): Remote artifacts are not created for content which ...https://pulp.plan.io/issues/86252021-04-24T15:39:50Zttereshcttereshc@redhat.com
<p>This behavior was introduced with this commit.
<a href="https://github.com/pulp/pulpcore/commit/47e5cc2a69464caaefbb50f994de03d72fb780e4" class="external">https://github.com/pulp/pulpcore/commit/47e5cc2a69464caaefbb50f994de03d72fb780e4</a></p>
<p>It affects RPM sync (because RPM content can have various checksum types) and migration plugin. Probably pulp_deb as well.</p>
<p>To reproduce:</p>
<ul>
<li>trigger on_demand sync for a repo with sha1 checksum type for content, e.g. <a href="https://packagecloud.io/timescale/timescaledb/el/7/x86_64/" class="external">https://packagecloud.io/timescale/timescaledb/el/7/x86_64/</a>
</li>
<li>observe only one remote artifact in the db</li>
</ul>
<pre><code>pulp=> select url from core_remoteartifact;
url
----------------------------------------------------------------------------------------------------
https://packagecloud.io/timescale/timescaledb/el/7/x86_64/timescaledb-tools-0.8.1-0.el7.x86_64.rpm
(1 row)
</code></pre>
<p>If you try to fetch any content other than the one for which you have a remote artifact, you'll get 404.</p> Debian Support - Task #8388 (CLOSED - CURRENTRELEASE): Handle ALLOWED_CONTENT_CHECKSUMS settinghttps://pulp.plan.io/issues/83882021-03-11T14:59:24Zquba42
<p>Right now the pulp_deb plugin is dependend on the following hashs being present on artifacts: md5, sha1, sha256, sha512.</p>
<p>Starting with pulpcore 3.11 will exclude md5 and sha1 from ALLOWED_CONTENT_CHECKSUMS by default.</p>
<p>Pulp deb will need to handle this gracefully. There is still some debate on whether pulp_deb makes sense without md5 feature wise. As a result, the solution may need to include demanding or encouraging a different configuration from pulp_deb users than the pulpcore default configuration.</p>
<p>See the following mailing list threads:</p>
<ul>
<li><a href="https://listman.redhat.com/archives/pulp-dev/2021-February/msg00017.html" class="external">https://listman.redhat.com/archives/pulp-dev/2021-February/msg00017.html</a></li>
<li><a href="https://listman.redhat.com/archives/pulp-dev/2021-March/msg00013.html" class="external">https://listman.redhat.com/archives/pulp-dev/2021-March/msg00013.html</a></li>
</ul> RPM Support - Issue #7116 (CLOSED - CURRENTRELEASE): Modules in errata not exposed by pulp3https://pulp.plan.io/issues/71162020-07-09T15:43:42Zpaji@redhat.compaji@redhat.com
<ol>
<li>Sync the appstream repo</li>
<li>Get the errata reference associated to errata_id = RHBA-2019:1530 or any other modular errata</li>
<li>run (make sure to update the errata id)</li>
</ol>
<pre><code> curl https://`hostname`/pulp/api/v3/content/rpm/advisories/9ff192a4-906f-4efd-ba29-55222eead0d8/ --cert
/etc/pki/katello/certs/pulp-client.crt --key /etc/pki/katello/private/pulp-client.key | jq
</code></pre>
<ol start="4">
<li>Look for pkglist attribute</li>
</ol>
<p>Expected:
pkglist has both module references and package references.</p>
<p>Actual:
Notice that module entries are missing from the package list</p>
<p>Additional Info:</p>
<pre><code> RHBA-2019:1530 is an errata that has the following module in its package list
<update status="final" from="release-engineering@redhat.com" version="1" type="bugfix">
<id>RHBA-2019:1530</id>
......
<pkglist>
<collection short="rhel-8-for-x86_64-appstream-rpms__8_1_virt">
<name>rhel-8-for-x86_64-appstream-rpms__8_1_virt</name>
<module stream="rhel" version="8000020190529063309" arch="x86_64" name="virt" context="55190bc5" />
........
</update>
</code></pre>
<p>Yet pulp does not show me any module name in the custom json</p> RPM Support - Test #4269 (CLOSED - COMPLETE): Recursive and conservative recursive copyhttps://pulp.plan.io/issues/42692018-12-14T17:36:04Zmilan
<a name="Description"></a>
<h2 >Description<a href="#Description" class="wiki-anchor">¶</a></h2>
<p>With the <a href="https://github.com/pulp/pulp_rpm/pull/1226" class="external">fix</a> for the Issue <a class="issue tracker-1 status-11 priority-6 priority-default closed" title="Issue: Regression Pulp 2.17.1: recursive copy of RPMs does not copy partially resolvable dependencies (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/4152">#4152</a>, the default behaviour of recursive copy changes back to the state before 2.17, rendering the test case <a href="https://github.com/PulpQE/Pulp-2-Tests/blob/c9277928c2788bced8d0ae3f630a46b6162fc4c9/pulp_2_tests/tests/rpm/api_v2/test_rich_weak_dependencies.py#L183" class="external">CopyRecursiveUnitsTestCase</a> broken.<br>
The behaviour specified in the <a href="https://github.com/PulpQE/pulp-smash/issues/1090" class="external">pulp smash issue 1090</a>, as requested in the Issue <a class="issue tracker-3 status-11 priority-6 priority-default closed" title="Story: Support more conservative dependency solving (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/2478">#2478</a>, is now optional and can be triggered by providing the <code>"recursive_conservative": true</code> config override instead of the default <code>"recursive": true</code>.<br>
With that setting, the test case <a href="https://github.com/PulpQE/Pulp-2-Tests/blob/c9277928c2788bced8d0ae3f630a46b6162fc4c9/pulp_2_tests/tests/rpm/api_v2/test_rich_weak_dependencies.py#L183" class="external">CopyRecursiveUnitsTestCase</a> should agin pass as is.</p>
<a name="Proposed-solution"></a>
<h2 >Proposed solution<a href="#Proposed-solution" class="wiki-anchor">¶</a></h2>
<p>Split the test case <a href="https://github.com/PulpQE/Pulp-2-Tests/blob/c9277928c2788bced8d0ae3f630a46b6162fc4c9/pulp_2_tests/tests/rpm/api_v2/test_rich_weak_dependencies.py#L183" class="external">CopyRecursiveUnitsTestCase</a> such that it asserts:</p>
<ul>
<li>a failure in the terms described in <a href="https://github.com/PulpQE/pulp-smash/issues/1090" class="external">pulp smash issue 1090</a> with the default <code>"recursive": true</code> config override setting</li>
<li>a success once the non-default <code>"recursive_conservative": true</code> config override setting is provided</li>
</ul> Packaging - Task #2228 (CLOSED - CURRENTRELEASE): Improve nodepool node launch demand calculationhttps://pulp.plan.io/issues/22282016-09-02T19:12:45Zsemyerssean.myers@redhat.com
<p>Because of a needed tweak to nodepool[0] we already running a fork. After chatting with elyezer, there are some further improvements I'd like to include on the fork.</p>
<p>Currently, nodepoold uses a tool called "geard" to determine node launch demand, based on the configure label demands of queued jobs. I believe that when nodepool was first being used, this information was not obtainable via the Jenkins API. Now, however, it is[1]. Furthermore, the geard integration simply doesn't work, afaict, for our use-case, unless we want to go nuts and bring in more pieces of openstack automation (e.g. zuul).</p>
<p>I've already done some preliminary work[2] to try to determine label demand based on the current jenkins build queue, so all that remains is wiring it into the nodepool fork and getting rid of the geard stuff that doesn't meet our needs.</p>
<p>[0]: <a href="https://github.com/seandst/nodepool/commit/1a807c8def36d62e80aaaa0e4e961a176e9ce746" class="external">https://github.com/seandst/nodepool/commit/1a807c8def36d62e80aaaa0e4e961a176e9ce746</a><br>
[1]: <a href="https://python-jenkins.readthedocs.io/en/latest/api.html#jenkins.Jenkins.get_queue_info" class="external">https://python-jenkins.readthedocs.io/en/latest/api.html#jenkins.Jenkins.get_queue_info</a><br>
[2]: <a href="https://gist.github.com/seandst/8e9b62f7b46bb5baa88a8bf5fbb11215" class="external">https://gist.github.com/seandst/8e9b62f7b46bb5baa88a8bf5fbb11215</a></p> Packaging - Issue #2120 (CLOSED - CURRENTRELEASE): Docs don't build on el7 for RPM or Dockerhttps://pulp.plan.io/issues/21202016-08-01T22:37:57Zsemyerssean.myers@redhat.com
<p>An older version of pygments in EPEL 7 apparently means that we don't get to use the 'json' lexer for code blocks:</p>
<p>RPM:</p>
<pre><code>Warning, treated as error:
/builddir/build/BUILD/pulp-rpm-2.10.1/docs/tech-reference/iso-rsync-distributor.rst:14: WARNING: Pygments lexer name u'json' is not known
make: *** [html] Error 1
</code></pre>
<p>Docker:</p>
<pre><code>Warning, treated as error:
/builddir/build/BUILD/pulp-docker-2.1.1/docs/tech-reference/distributor.rst:182: WARNING: Pygments lexer name u'json' is not known
RPM build errors:
make: *** [html] Error 1
</code></pre>
<p>This prevents package builds on master, which is what 2.10 will be based on tomorrow, so it needs to be fixed immediately. Since it blocks the 2.10 release, I'm going to go ahead and triage it as an Urgent but Easy Docs Fix.</p> Docker Support - Issue #1953 (CLOSED - NOTABUG): Migration failing on upgrade from 2.8.3->2.8.4https://pulp.plan.io/issues/19532016-05-27T17:42:30Zpthomas@redhat.com
<p>Database migration is failing for upgrade from 2.8.3 to 2.8.4</p>
<pre><code>
[root@yttrium ~]# rpm -qa |grep pulp
python-kombu-3.0.33-5.pulp.el7.noarch
python-pulp-rpm-common-2.8.4-0.1.beta.el7.noarch
pulp-server-2.8.4-0.1.beta.el7.noarch
pulp-admin-client-2.8.4-0.1.beta.el7.noarch
python-pulp-docker-common-2.0.2-0.1.beta.el7.noarch
python-pulp-bindings-2.8.4-0.1.beta.el7.noarch
pulp-puppet-plugins-2.8.4-0.1.beta.el7.noarch
pulp-puppet-admin-extensions-2.8.4-0.1.beta.el7.noarch
python-pulp-client-lib-2.8.4-0.1.beta.el7.noarch
python-pulp-oid_validation-2.8.4-0.1.beta.el7.noarch
pulp-rpm-plugins-2.8.4-0.1.beta.el7.noarch
pulp-rpm-admin-extensions-2.8.4-0.1.beta.el7.noarch
pulp-docker-plugins-2.0.2-0.1.beta.el7.noarch
pulp-docker-admin-extensions-2.0.2-0.1.beta.el7.noarch
python-pulp-common-2.8.4-0.1.beta.el7.noarch
python-pulp-repoauth-2.8.4-0.1.beta.el7.noarch
pulp-selinux-2.8.4-0.1.beta.el7.noarch
python-isodate-0.5.0-4.pulp.el7.noarch
python-pulp-puppet-common-2.8.4-0.1.beta.el7.noarch
[root@yttrium ~]#
1. Install pulp 2.8.3
2. Populate with content
3. Make sure include rpm, iso, puppet, docker contents
4. Yum update to 2.8.4 beta
5. Run pulp-manage-db
[root@yttrium ~]# sudo -u apache pulp-manage-db
Attempting to connect to localhost:27017
Attempting to connect to localhost:27017
Write concern for Mongo connection: {}
Loading content types.
Loading type descriptors []
Parsing type descriptors
Validating type descriptor syntactic integrity
Validating type descriptor semantic integrity
Loading unit model: puppet_module = pulp_puppet.plugins.db.models:Module
Loading unit model: erratum = pulp_rpm.plugins.db.models:Errata
Loading unit model: distribution = pulp_rpm.plugins.db.models:Distribution
Loading unit model: package_group = pulp_rpm.plugins.db.models:PackageGroup
Loading unit model: package_category = pulp_rpm.plugins.db.models:PackageCategory
Loading unit model: iso = pulp_rpm.plugins.db.models:ISO
Loading unit model: package_environment = pulp_rpm.plugins.db.models:PackageEnvironment
Loading unit model: drpm = pulp_rpm.plugins.db.models:DRPM
Loading unit model: srpm = pulp_rpm.plugins.db.models:SRPM
Loading unit model: rpm = pulp_rpm.plugins.db.models:RPM
Loading unit model: yum_repo_metadata_file = pulp_rpm.plugins.db.models:YumMetadataFile
Loading unit model: docker_blob = pulp_docker.plugins.models:Blob
Loading unit model: docker_manifest = pulp_docker.plugins.models:Manifest
Loading unit model: docker_image = pulp_docker.plugins.models:Image
Loading unit model: docker_tag = pulp_docker.plugins.models:Tag
Updating the database with types []
Found the following type definitions that were not present in the update collection [puppet_module, docker_tag, docker_manifest, docker_blob, erratum, yum_repo_metadata_file, package_group, package_category, iso, package_environment, drpm, srpm, rpm, distribution, docker_image]
Updating the database with types [puppet_module, docker_tag, erratum, docker_blob, docker_manifest, yum_repo_metadata_file, package_group, package_category, iso, package_environment, drpm, distribution, rpm, srpm, docker_image]
Content types loaded.
Ensuring the admin role and user are in place.
Admin role and user are in place.
Beginning database migrations.
Migration package pulp.server.db.migrations is up to date at version 23
The database for migration package pulp_docker.plugins.migrations is at version 2, which is larger than the latest version available, 1.
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 193, in main
return _auto_manage_db(options)
File "/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 256, in _auto_manage_db
migrate_database(options)
File "/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 73, in migrate_database
raise DataError(msg)
DataError: The database for migration package pulp_docker.plugins.migrations is at version 2, which is larger than the latest version available, 1.
[root@yttrium ~]#
From the log
May 27 13:29:09 yttrium.idmqe.lab.eng.bos.redhat.com pulp[23300]: pulp.server.db.manage:INFO: Migration package pulp.server.db.migrations is up to date at version 23
May 27 13:29:09 yttrium.idmqe.lab.eng.bos.redhat.com pulp[23300]: pulp.server.db.manage:CRITICAL: The database for migration package pulp_docker.plugins.migrations is at version 2, which is larger than the latest version available, 1.
May 27 13:29:09 yttrium.idmqe.lab.eng.bos.redhat.com pulp[23300]: pulp.server.db.manage:CRITICAL: (23300-12224) Traceback (most recent call last):
May 27 13:29:09 yttrium.idmqe.lab.eng.bos.redhat.com pulp[23300]: pulp.server.db.manage:CRITICAL: (23300-12224) File "/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 193, in main
May 27 13:29:09 yttrium.idmqe.lab.eng.bos.redhat.com pulp[23300]: pulp.server.db.manage:CRITICAL: (23300-12224) return _auto_manage_db(options)
May 27 13:29:09 yttrium.idmqe.lab.eng.bos.redhat.com pulp[23300]: pulp.server.db.manage:CRITICAL: (23300-12224) File "/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 256, in _auto_manage_db
May 27 13:29:09 yttrium.idmqe.lab.eng.bos.redhat.com pulp[23300]: pulp.server.db.manage:CRITICAL: (23300-12224) migrate_database(options)
May 27 13:29:09 yttrium.idmqe.lab.eng.bos.redhat.com pulp[23300]: pulp.server.db.manage:CRITICAL: (23300-12224) File "/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 73, in migrate_database
May 27 13:29:09 yttrium.idmqe.lab.eng.bos.redhat.com pulp[23300]: pulp.server.db.manage:CRITICAL: (23300-12224) raise DataError(msg)
May 27 13:29:09 yttrium.idmqe.lab.eng.bos.redhat.com pulp[23300]: pulp.server.db.manage:CRITICAL: (23300-12224) DataError: The database for migration package pulp_docker.plugins.migrations is at version 2, which is larger than the latest version available, 1.
May 27 13:29:09 yttrium.idmqe.lab.eng.bos.redhat.com pulp[23300]: pulp.server.db.manage:CRITICAL: (23300-12224)
</code></pre> Pulp - Task #1941 (CLOSED - CURRENTRELEASE): Strict/nitpicky sphinx settings break our rpm buildshttps://pulp.plan.io/issues/19412016-05-23T22:40:42Zsemyerssean.myers@redhat.com
<p>This is a post-mortem report of the task of diagnosing and fixing broken builds.</p>
<hr>
<p>In <a class="issue tracker-2 status-11 priority-6 priority-default closed" title="Task: Consolidate platform and plugin docs into a static site. (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/950">#950</a>, we turned on strict docs builds, but this ended up breaking our builds.</p>
<p>The problem was that there's no internet access inside the mock buildroot, so when sphinx went to download the intersphinx inventory files it would fail. Normally this triggers a warning, but enabling strict mode promotes all build warnings to errors. It's worth pointing out that the intersphinx downloads have always been failing during RPM build, the only thing new was our strictness.</p>
<p>Strict building is good; at the moment work is ongoing in <a class="issue tracker-2 status-11 priority-6 priority-default closed" title="Task: Consolidate platform and plugin docs into a static site. (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/950">#950</a> to modify our docs build process to hopefully (among many other goals) allow us to once again do strict builds with sphinx without breaking the build.</p>