Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2019-08-21T12:47:54ZPulp
Planio RPM Support - Test #5320 (CLOSED - WONTFIX): Module Streams not copying correctly with recursive ...https://pulp.plan.io/issues/53202019-08-21T12:47:54Zbherring
<ol>
<li>
<p>Create and sync the following yum repo (Source) -> <a href="https://partha.fedorapeople.org/test-repos/pteradactyl/" class="external">https://partha.fedorapeople.org/test-repos/pteradactyl/</a></p>
</li>
<li>
<p>Create another repo Dest which will serve as the destination repo</p>
</li>
<li>
<p>Go to mongo and pick up a uuid for the pteradactly:2 module stream. This stream will be copied from source to dest .</p>
</li>
<li>
<p>run the following command</p>
<pre><code>https://<fqdn>/pulp/api/v2/repositories/Dest/actions/associate/: {"source_repo_id":"Source","criteria":{"type_ids":["modulemd"],"filters":{"association":{"unit_id":{"$in":[<$MODULE UUID>]}}}},"override_config":{"recursive":true}}: {"content_type"=>"application/json", "accept"=>"application/json"}
</code></pre>
</li>
<li>
<p>pulp-admin rpm repo list. Check for the number of module mds copied over by the above call.</p>
</li>
<li>
<p>notice that with recursive set to true all the pteradactyl module streams gets copied over, instead of just pteradactly:2 and packages belonging to that</p>
</li>
<li>
<p>Behavior is similar for recursive conservative</p>
</li>
</ol> RPM Support - Test #5055 (CLOSED - DUPLICATE): [EPIC] Ursine RPM Copy dependencies on modular RPM...https://pulp.plan.io/issues/50552019-06-27T15:17:53Zbherring
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2217":<a href="https://github.com/pulp/pulp_rpm/issues/2217" class="external">https://github.com/pulp/pulp_rpm/issues/2217</a></p>
<hr>
<a name="History"></a>
<h2 >History<a href="#History" class="wiki-anchor">¶</a></h2>
<p>There is currently a 'policy decision' that modules in the base repo (of rhel) don't rely on modular rpms, but that it's not an engineering limitation, and that fedora and rhel will likely do so at some point in the future. This is already a consideration for fedora and fedora-updates repos.</p>
<p>At least in Fedora, you can expect that there will be content in the updates-testing repo depending on content in updates-modular and/or fedora-modular.</p>
<p>This means Pulp will <strong>eventually</strong> need to support multiple source repos for copy.</p>
<a name="Problem"></a>
<h2 >Problem<a href="#Problem" class="wiki-anchor">¶</a></h2>
<p>As pulp is delivered today, Ursine RPM deps on modular RPMs are NOT covered by test.</p>
<p>Normal, non-modular (ursine) [0] RPMs can depend on module packages.</p>
<p>As an example, the postgres language RPMs depend on the default stream of the postgresql module.</p>
<p>When this is the case, the default module and all artifacts related to that module and the URSINE RPM are ALL copied to the target repo.</p>
<p>At this time, to account for this scenario, a hybrid repo containing URSINE and MODULAR RPMs with modules will be required.</p>
<a name="Example"></a>
<h2 >Example<a href="#Example" class="wiki-anchor">¶</a></h2>
<a name="Recursive"></a>
<h3 >Recursive<a href="#Recursive" class="wiki-anchor">¶</a></h3>
<a name="Before"></a>
<h4 >Before<a href="#Before" class="wiki-anchor">¶</a></h4>
<ul>
<li>Copy Ursine RPM "zebra-1.0.rpm" from Repo A to B</li>
<li>Zebra requires modular RPM bar-1.0.rpm and has no other dependencies</li>
</ul>
<pre><code>
default module: module-FOO: [foo-1.0.rpm, bar-1.0.rpm, baz-1.0.rpm]
repo A
|
|---- chicken-1.1.rpm
|---- zebra-1.0.rpm
|----module-FOO
|----foo-1.0.rpm
|----bar-1.0.rpm
|----baz-1.0.rpm
repo B
|
|----bar-0.7.rpm
</code></pre>
<a name="After-Copy"></a>
<h4 >After Copy<a href="#After-Copy" class="wiki-anchor">¶</a></h4>
<p>Result of copying ursine RPM zebra-1.0.rpm from repo A to repo B:</p>
<pre><code>repo B
|
|---- zebra-1.0.rpm
|----module-FOO
|----foo-1.0.rpm
|----bar-1.0.rpm
|----baz-1.0.rpm
|----bar-0.7.rpm
All available artifacts are copied, always. There is no way to copy just module on its own,
if any of its artifacts are present in a source repo (repo A).
</code></pre>
<a name="Solution"></a>
<h2 >Solution<a href="#Solution" class="wiki-anchor">¶</a></h2>
<ul>
<li>Add Ursine RPM permutations that exercise this case for recursive and non_recursive Ursine RPM copies in mixed repos with modular RPMs where default streams <strong>are</strong> and <strong>are not</strong> defined.</li>
</ul>
<a name="Note"></a>
<h2 >Note:<a href="#Note" class="wiki-anchor">¶</a></h2>
<ul>
<li>the entire module should be treated as a single content unit to the greatest extent possible. it should copy the module that provides both A and B, all if its artifacts, and, the module default</li>
<li>a module RPM should never be treated as just a normal RPM</li>
<li>If module has multiple streams, ONLY the artifacts associated with the default module and the default module are copied, correct?
<ul>
<li>only the artifacts associated with the default module stream should ever be considered in the first place. if there is no default stream for a module, then RPMs should not be able to depend on it</li>
</ul>
</li>
</ul>
<a name="References"></a>
<h2 >References<a href="#References" class="wiki-anchor">¶</a></h2>
<p>[0] - <a href="https://docs.fedoraproject.org/en-US/modularity/architecture/consuming/dnf-behavior/" class="external">https://docs.fedoraproject.org/en-US/modularity/architecture/consuming/dnf-behavior/</a><br>
[1] - <a href="https://docs.pulpproject.org/plugins/pulp_rpm/user-guide/features.html?highlight=modularity" class="external">https://docs.pulpproject.org/plugins/pulp_rpm/user-guide/features.html?highlight=modularity</a></p> RPM Support - Test #4824 (CLOSED - DUPLICATE): Pulp does not resync yum metadata files on changehttps://pulp.plan.io/issues/48242019-05-15T17:01:53Zbherring
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2215":<a href="https://github.com/pulp/pulp_rpm/issues/2215" class="external">https://github.com/pulp/pulp_rpm/issues/2215</a></p>
<hr>
<p>Pulp uses revision numbers in repomd.xml to determine if contents need to be updated on sync. However "modifyrepo" does not generate new revision numbers for non rpm data.</p>
<p>Steps:<br>
1) Setup the following repo</p>
<pre><code>$ mkdir /tmp/my-data
$ cd /tmp/my-data
$ wget https://partha.fedorapeople.org/test-repos/rpm-with-productid/elephant-0.3-0.8.noarch.rpm
$ createrepo .
$ echo "100000" >> productid
$ modifyrepo --mdtype=productid productid repodata
$ grep revision repodata/repomd.xml
<revision>1554217257</revision>
</code></pre>
<p>2) Sync this repo<br>
3) Now update the repo</p>
<pre><code>$ cd /tmp/my-data
$ echo "100001" >> productid
$ modifyrepo --mdtype=productid productid repodata
$ grep revision repodata/repomd.xml
<revision>1554217257</revision>
</code></pre>
<p>Notice that the revision number did not change even though a metadata file got updated. Try resyncing this change and notice that the productid change will get ignored.</p> Pulp - Test #4823 (CLOSED - DUPLICATE): Modulemd profiles not getting removed from the consumerhttps://pulp.plan.io/issues/48232019-05-15T15:57:41Zbherring
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/1827":<a href="https://github.com/pulp/pulpcore/issues/1827" class="external">https://github.com/pulp/pulpcore/issues/1827</a></p>
<hr>
<p>I have consumer "integration_test_consumer_support" registered to pulp. It has 1 module enabled. When I try to delete all modulemd profiles belonging to this consumer, it simple gets ignored.</p>
<pre><code># before profile delete
$ curl -k -u admin:admin https://localhost/pulp/api/v2/consumers/integration_test_consumer_support/profiles/
[{"profile": [{"context": "deadbeef", "version": "20180730223407", "arch": "noarch", "name": "kangaroo", "stream": "0"}], "_href": "/pulp/api/v2/consumers/integration_test_consumer_support/profiles/modulemd/", "_ns": "consumer_unit_profiles", "profile_hash": "f69375f21b302f40025ff8a2128004e81436407554972029cbfbe445d0a2b563", "consumer_id": "integration_test_consumer_support", "content_type": "modulemd", "_id": {"$oid": "5cab7b49db284e2341a2c0ac"}, "id": "5cab7b49db284e2341a2c0ac"}]
# Delete profile
curl -X "DELETE" -k -u admin:admin https://localhost/pulp/api/v2/consumers/integration_test_consumer_support/profiles/modulemd/
# after profile delete
curl -k -u admin:admin https://localhost/pulp/api/v2/consumers/integration_test_consumer_support/profiles/
[{"profile": [{"context": "deadbeef", "version": "20180730223407", "arch": "noarch", "name": "kangaroo", "stream": "0"}], "_href": "/pulp/api/v2/consumers/integration_test_consumer_support/profiles/modulemd/", "_ns": "consumer_unit_profiles", "profile_hash": "f69375f21b302f40025ff8a2128004e81436407554972029cbfbe445d0a2b563", "consumer_id": "integration_test_consumer_support", "content_type": "modulemd", "_id": {"$oid": "5cab7b49db284e2341a2c0ac"}, "id": "5cab7b49db284e2341a2c0ac"}]
</code></pre> Python Support - Test #4748 (CLOSED - DUPLICATE): Improve Publications functional testshttps://pulp.plan.io/issues/47482019-04-30T12:13:07Zamacdona@redhat.comaustin@redhat.com
<p>The tests written during the feature change are a stopgap, and have some problems:<br>
<a href="https://github.com/pulp/pulp_python/pull/242/" class="external">https://github.com/pulp/pulp_python/pull/242/</a></p>
<p>The tests need to be broken up. Currently they are fragile and fully dependent on each other to pass. Ideally, the preparation should be moved to the setup of each class, but this could cause slow tests since a lot of steps need to be in place before a publication can be created. Please have a look at the utilities, they probably need to be refactored.</p> RPM Support - Test #4730 (CLOSED - WONTFIX): incremental publish of yum_repo_metadata_repo fails ...https://pulp.plan.io/issues/47302019-04-23T19:45:12Zbherring
<p>Steps to reproduce:<br>
1. use Pulp 2.18<br>
2. sync repo with yum_repo_metadata_file (e.g any RHEL repo contains productid which is of the type we need)<br>
3. publish it (in the publish directory there should be a symlink to /var/lib/pulp/published/../../../productid)<br>
4. upgrade to the 2-master (commit c86c4339b9c1b4f158af1e961e8d68492dd2a760)<br>
5. upload any rpm to the repo (to make publish incremental)<br>
6. publish the repo, see the error below:</p>
<pre><code>Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) Traceback (most recent call last):
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) File "/usr/lib/python2.7/site-packages/celery/app/trace.py", line 367, in trace_task
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) R = retval = fun(*args, **kwargs)
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) File "/home/vagrant/devel/pulp/server/pulp/server/async/tasks.py", line 529, in __call__
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) return super(Task, self).__call__(*args, **kwargs)
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) File "/home/vagrant/devel/pulp/server/pulp/server/async/tasks.py", line 107, in __call__
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) return super(PulpTask, self).__call__(*args, **kwargs)
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) File "/usr/lib/python2.7/site-packages/celery/app/trace.py", line 622, in __protected_call__
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) return self.run(*args, **kwargs)
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) File "/home/vagrant/devel/pulp/server/pulp/server/controllers/repository.py", line 1110, in publish
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) result = check_publish(repo_obj, dist_id, dist_inst, transfer_repo, conduit, call_config)
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) File "/home/vagrant/devel/pulp/server/pulp/server/controllers/repository.py", line 1207, in check_publish
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) result = _do_publish(repo_obj, dist_id, dist_inst, transfer_repo, conduit, call_config)
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) File "/home/vagrant/devel/pulp/server/pulp/server/controllers/repository.py", line 1259, in _do_publish
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) publish_report = publish_repo(transfer_repo, conduit, call_config)
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) File "/home/vagrant/devel/pulp/server/pulp/server/async/tasks.py", line 737, in wrap_f
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) return f(*args, **kwargs)
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) File "/home/vagrant/devel/pulp_rpm/plugins/pulp_rpm/plugins/distributors/yum/distributor.py", line 174, in publish_repo
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) return self._publisher.process_lifecycle()
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) File "/home/vagrant/devel/pulp/server/pulp/plugins/util/publish_step.py", line 572, in process_lifecycle
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) super(PluginStep, self).process_lifecycle()
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) File "/home/vagrant/devel/pulp/server/pulp/plugins/util/publish_step.py", line 163, in process_lifecycle
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) step.process()
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) File "/home/vagrant/devel/pulp/server/pulp/plugins/util/publish_step.py", line 239, in process
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) self._process_block(item=item)
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) File "/home/vagrant/devel/pulp/server/pulp/plugins/util/publish_step.py", line 301, in _process_block
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) self.process_main(item=item)
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) File "/home/vagrant/devel/pulp_rpm/plugins/pulp_rpm/plugins/distributors/yum/publish.py", line 527, in process_main
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) shutil.copy2(unit._storage_path, file_path)
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) File "/usr/lib64/python2.7/shutil.py", line 144, in copy2
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) copyfile(src, dst)
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) File "/usr/lib64/python2.7/shutil.py", line 83, in copyfile
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) raise Error("`%s` and `%s` are the same file" % (src, dst))
Apr 10 14:45:22 pulp2.dev pulp[4045]: celery.app.trace:ERROR: [7669f0fa] (4045-84096) Error: `/var/lib/pulp/content/units/yum_repo_metadata_file/46/f013ec598b38b306dfd761b41a3ebf1c496f09f440679a1d7b2d4188145fda/ba86625b825e4bea5f6ab2b3e83c2cb076087507815be7e35da6d8bf697829dd-productid.gz` and `/var/cache/pulp/reserved_resource_worker-0@pulp2.dev/7669f0fa-1fc0-49a9-b834-dda548f0da0f/repodata/ba86625b825e4bea5f6ab2b3e83c2cb076087507815be7e35da6d8bf697829dd-productid.gz` are the same file
</code></pre> RPM Support - Test #4729 (CLOSED - WONTFIX): Migration of modular content can fail (upgrade from ...https://pulp.plan.io/issues/47292019-04-23T19:44:00Zbherring
<p>Hello folks,<br>
Our upgrade of a (albeit smaller but otherwise identical) beta Pulp server went just fine, so this morning I upgraded production which went fine until the database migration.</p>
<p>The migration failed very early at 'Applying migration pulp_rpm.plugins.migrations.0043_add_modulemd_modulemd-defaults failed.' The underlying traceback shows 'IOError: Not a gzipped file'.</p>
<p>Full paste lives here: <a href="https://paste.fedoraproject.org/paste/wEIu5a3Tf8OejEzMNsXN9w" class="external">https://paste.fedoraproject.org/paste/wEIu5a3Tf8OejEzMNsXN9w</a></p>
<p>Packages installed are:<br>
$rpm -qa | egrep 'pulp|qpid|gofer|celery|mongo' | sort<br>
mongodb-2.6.12-6.el7.x86_64<br>
mongodb-server-2.6.12-6.el7.x86_64<br>
pulp-admin-client-2.18.1-2.el7.noarch<br>
pulp-docker-admin-extensions-3.2.2-1.el7.noarch<br>
pulp-docker-plugins-3.2.2-1.el7.noarch<br>
pulp-puppet-admin-extensions-2.18.1-1.el7.noarch<br>
pulp-puppet-plugins-2.18.1-1.el7.noarch<br>
pulp-rpm-admin-extensions-2.18.1-1.el7.noarch<br>
pulp-rpm-plugins-2.18.1-1.el7.noarch<br>
pulp-selinux-2.18.1-2.el7.noarch<br>
pulp-server-2.18.1-2.el7.noarch<br>
python2-celery-4.0.2-7.el7.noarch<br>
python2-qpid-1.37.0-4.el7.noarch<br>
python2-qpid-qmf-1.39.0-1.el7.x86_64<br>
python-gofer-2.12.5-1.el7.noarch<br>
python-gofer-qpid-2.12.5-1.el7.noarch<br>
python-isodate-0.5.0-4.pulp.el7.noarch<br>
python-mongoengine-0.10.5-1.el7.noarch<br>
python-pulp-bindings-2.18.1-2.el7.noarch<br>
python-pulp-client-lib-2.18.1-2.el7.noarch<br>
python-pulp-common-2.18.1-2.el7.noarch<br>
python-pulp-docker-common-3.2.2-1.el7.noarch<br>
python-pulp-oid_validation-2.18.1-2.el7.noarch<br>
python-pulp-puppet-common-2.18.1-1.el7.noarch<br>
python-pulp-repoauth-2.18.1-2.el7.noarch<br>
python-pulp-rpm-common-2.18.1-1.el7.noarch<br>
python-pymongo-3.2-2.el7.x86_64<br>
python-pymongo-gridfs-3.2-2.el7.x86_64<br>
qpid-cpp-client-1.39.0-1.el7.x86_64<br>
qpid-cpp-server-1.39.0-1.el7.x86_64<br>
qpid-cpp-server-linearstore-1.39.0-1.el7.x86_64<br>
qpid-proton-c-0.26.0-1.el7.x86_64<br>
qpid-qmf-1.39.0-1.el7.x86_64<br>
qpid-tools-1.39.0-1.el7.noarch</p>
<p>I'm a bit stumped because I'm not a developer, or a database wiz, so any help in getting our prod instance back up would be very much appreciated! Thanks!</p>
<a name="Summary"></a>
<h3 >Summary<a href="#Summary" class="wiki-anchor">¶</a></h3>
<p>Some repos unexpectedly contain uncompressed modules.yaml metadata.<br>
Pulp should not fail but try to work with uncompressed data instead.</p>
<pre><code>Applying pulp_rpm.plugins.migrations version 43
Loading unit model: puppet_module = pulp_puppet.plugins.db.models:Module
Loading unit model: docker_manifest = pulp_docker.plugins.models:Manifest
Loading unit model: docker_blob = pulp_docker.plugins.models:Blob
Loading unit model: docker_manifest_list = pulp_docker.plugins.models:ManifestList
Loading unit model: docker_image = pulp_docker.plugins.models:Image
Loading unit model: docker_tag = pulp_docker.plugins.models:Tag
Loading unit model: modulemd_defaults = pulp_rpm.plugins.db.models:ModulemdDefaults
Loading unit model: erratum = pulp_rpm.plugins.db.models:Errata
Loading unit model: distribution = pulp_rpm.plugins.db.models:Distribution
Loading unit model: srpm = pulp_rpm.plugins.db.models:SRPM
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: package_langpacks = pulp_rpm.plugins.db.models:PackageLangpacks
Loading unit model: modulemd = pulp_rpm.plugins.db.models:Modulemd
Loading unit model: rpm = pulp_rpm.plugins.db.models:RPM
Loading unit model: yum_repo_metadata_file = pulp_rpm.plugins.db.models:YumMetadataFile
Loading auxiliary model: erratum_pkglists = pulp_rpm.plugins.db.models:ErratumPkglist
Loaded plugin puppet_distributor for types: puppet_module
Loaded plugin puppet_file_distributor for types: puppet_module
Loaded plugin puppet_install_distributor for types: puppet_module
Loaded plugin docker_distributor_web for types: docker_image,docker_blob,docker_manifest,docker_tag
Loaded plugin docker_rsync_distributor for types: docker_image,docker_blob,docker_manifest,docker_tag
Loaded plugin docker_distributor_export for types: docker_image
Loaded plugin yum_distributor for types: rpm,srpm,drpm,erratum,package_group,package_category,distribution,yum_repo_metadata_file
Loaded plugin export_distributor for types: rpm,srpm,drpm,erratum,distribution,package_category,package_group
Loaded plugin rpm_rsync_distributor for types: rpm,srpm,drpm,erratum,package_group,package_category,distribution,yum_repo_metadata_file
Loaded plugin iso_distributor for types: iso
Loaded plugin iso_rsync_distributor for types: iso
Loaded plugin group_export_distributor for types: rpm,srpm,drpm,erratum,distribution,package_category,package_group
Loaded plugin puppet_importer for types: puppet_module
Loaded plugin docker_importer for types: docker_blob,docker_image,docker_manifest,docker_manifest_list,docker_tag
Loaded plugin yum_importer for types: distribution,drpm,erratum,package_group,package_category,rpm,srpm,yum_repo_metadata_file,package_environment,package_langpacks,modulemd,modulemd_defaults
Loaded plugin iso_importer for types: iso
Loaded plugin puppet_whole_repo_profiler for types: puppet_module
Loaded plugin yum_profiler for types: rpm,erratum,modulemd
Loaded plugin yum for types: rpm
Loaded plugin rhui for types: rpm
Applying migration pulp_rpm.plugins.migrations.0043_add_modulemd_modulemd-defaults failed.
Halting migrations due to a migration failure.
Not a gzipped file
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 239, in main
return _auto_manage_db(options)
File "/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 306, in _auto_manage_db
migrate_database(options)
File "/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 135, in migrate_database
update_current_version=not options.test)
File "/usr/lib/python2.7/site-packages/pulp/server/db/migrate/models.py", line 189, in apply_migration
migration.migrate()
File "/usr/lib/python2.7/site-packages/pulp_rpm/plugins/migrations/0043_add_modulemd_modulemd-defaults.py", line 341, in migrate
modulemds, defaults = load(fp, working_dir)
File "/usr/lib/python2.7/site-packages/pulp_rpm/plugins/migrations/0043_add_modulemd_modulemd-defaults.py", line 317, in load
bfr = metadata.read(1024000)
File "/usr/lib64/python2.7/gzip.py", line 261, in read
self._read(readsize)
File "/usr/lib64/python2.7/gzip.py", line 296, in _read
self._read_gzip_header()
File "/usr/lib64/python2.7/gzip.py", line 190, in _read_gzip_header
raise IOError, 'Not a gzipped file'
IOError: Not a gzipped file
</code></pre> Pulp - Test #4728 (CLOSED - WONTFIX): Task Cancellation doesn't interrupt/cancel a running task w...https://pulp.plan.io/issues/47282019-04-23T19:42:43Zbherring
<p>See the upstream PR fix for it here from @rohanpm <a href="https://github.com/celery/kombu/pull/1029" class="external">https://github.com/celery/kombu/pull/1029</a></p>
<p>The fix would be to include ^ PR in the kombu packages Pulp ships.</p> Pulp - Test #4659 (CLOSED - DUPLICATE): Add RHEL to the ansible-pulp molecule CIhttps://pulp.plan.io/issues/46592019-04-09T15:14:09Zamacdona@redhat.comaustin@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/1822":<a href="https://github.com/pulp/pulpcore/issues/1822" class="external">https://github.com/pulp/pulpcore/issues/1822</a></p>
<hr>
<p>Unlike the other OSes that are currently tested, RHEL needs some additional steps, notably, enabling the subscription.</p>
<p>This test will be complete when RHEL is included in the test matrix for the ansible installer.</p> File Support - Test #4538 (CLOSED - DUPLICATE): fetching a published PULP_MANIFEST throws a 404 i...https://pulp.plan.io/issues/45382019-03-13T11:26:29Zbherring
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_file/610":<a href="https://github.com/pulp/pulp_file/issues/610" class="external">https://github.com/pulp/pulp_file/issues/610</a></p>
<hr>
<p>1. Create a repository<br>
2. Create a file publisher<br>
3. Publish the publisher<br>
4. Create a distribution from the publication<br>
5. Fetch PULP_MANIFEST</p>
<p>Receive a 404. According to the docs a PULP_MANIFEST should be created by default for all file publishes (unless the filename has been configured differently in the publisher).</p> Pulp - Test #4468 (CLOSED - WONTFIX): Convert JJB to DSL for Pulp 2/3https://pulp.plan.io/issues/44682019-02-25T16:08:30Zbherring
<a name="Meeting-Notes"></a>
<h2 >Meeting Notes<a href="#Meeting-Notes" class="wiki-anchor">¶</a></h2>
<ul>
<li><a href="https://projects.engineering.redhat.com/browse/RHSMQE-548" class="external">https://projects.engineering.redhat.com/browse/RHSMQE-548</a></li>
<li><a href="https://gitlab.sat.engineering.redhat.com/jmolet/jenkins-dsl-template" class="external">https://gitlab.sat.engineering.redhat.com/jmolet/jenkins-dsl-template</a></li>
</ul> Pulp - Test #4466 (CLOSED - WONTFIX): The streamer needs to try all RemoteArtifact entires relate...https://pulp.plan.io/issues/44662019-02-25T15:13:57Zbherring
<p>The long term design for the streamer was to sort the entries newest to oldest. Then, try them in order and only fail when <strong>all</strong> entries have failed.</p> Docker Support - Test #4129 (CLOSED - COMPLETE): Test sync of a repository that returns a 403 res...https://pulp.plan.io/issues/41292018-11-06T19:56:22Zamacdona@redhat.comaustin@redhat.com
<p>This test will require the creation of a new fixture for pulp_docker that is a corrupted repository. This fixture is primarily intended to test <a href="https://pulp.plan.io/issues/2966" class="external">https://pulp.plan.io/issues/2966</a> (pulp 2) but could also be useful for testing pulp 3.</p>
<p>From 2966, it appears that a 403 can be caused by a missing symlink in the published repository.</p> Docker Support - Test #4128 (CLOSED - COMPLETE): Test sync of a repository that is missing blobshttps://pulp.plan.io/issues/41282018-11-06T19:52:42Zamacdona@redhat.comaustin@redhat.com
<p>This test will require the creation of a new fixture for pulp_docker that is a corrupted repository. This fixture is primarily intended to test <a href="https://pulp.plan.io/issues/2849" class="external">https://pulp.plan.io/issues/2849</a> (pulp 2) but could also be useful for testing pulp 3.</p>
<p>The "corrupted repository" can be a fully published non-corrupt repository that is simply missing one or more Images referenced by or or more of the Image Manifests.</p> Pulp - Test #3634 (CLOSED - COMPLETE): Write functional tests for task delete and cancel codehttps://pulp.plan.io/issues/36342018-04-30T20:59:51Zamacdona@redhat.comaustin@redhat.com
<p>Tests should successfully delete tasks in final states, and should not be able to delete tasks in waiting or running states.</p>
<p>Tests should successfully cancel tasks in waiting and running states, but should not be able to cancel tasks in final states.</p>