Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2019-04-01T15:55:03ZPulp
Planio RPM Support - Issue #4617 (CLOSED - CURRENTRELEASE): Migration of modular content can fail (upgra...https://pulp.plan.io/issues/46172019-04-01T15:55:03Zkfiresmithkfiresmith@gmail.com
<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 - Story #2595 (CLOSED - DUPLICATE): Being able to set a retry for failed tasks would make pu...https://pulp.plan.io/issues/25952017-02-21T12:56:15Zkfiresmithkfiresmith@gmail.com
<p>As my pulp installation has expanded out to 140+ repos, failed repo syncs have become a daily occurrence. I currently deal with this manually after being notified by external tools (Splunk alerts) - if I could set a global default and/or a task-type specific delay&retry for failed tasks, that would sort most of the problems I have with failed tasks and make pulp more reliable.</p> Pulp - Issue #2024 (CLOSED - DUPLICATE): Summary listing of RPM repos appears to be brokenhttps://pulp.plan.io/issues/20242016-06-20T17:59:24Zkfiresmithkfiresmith@gmail.com
<pre><code>ERROR - Client-side exception occurred
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/pulp/client/extensions/core.py", line 474, in run
exit_code = Cli.run(self, args)
File "/usr/lib/python2.7/site-packages/okaara/cli.py", line 974, in run
exit_code = command_or_section.execute(self.prompt, remaining_args)
File "/usr/lib/python2.7/site-packages/pulp/client/extensions/extensions.py", line 210, in execute
return self.method(*arg_list, **clean_kwargs)
File "/usr/lib/python2.7/site-packages/pulp/client/commands/repo/cudl.py", line 331, in run
self.display_repository_summaries(**kwargs)
File "/usr/lib/python2.7/site-packages/pulp/client/commands/repo/cudl.py", line 395, in display_repository_summaries
_default_summary_view(repo_list, self.prompt)
File "/usr/lib/python2.7/site-packages/pulp/client/commands/repo/cudl.py", line 535, in _default_summary_view
name_value = repo['display_name'][0:max_name_width]
TypeError: 'NoneType' object has no attribute '__getitem__'
An unexpected error has occurred. More information may be found using the -v
flag.
</code></pre>
<p><a href="http://paste.fedoraproject.org/382230/66444803/" class="external">http://paste.fedoraproject.org/382230/66444803/</a></p> Pulp - Story #1999 (CLOSED - WONTFIX): When ISO plugin is generalized to "FILES", could we please...https://pulp.plan.io/issues/19992016-06-10T20:35:00Zkfiresmithkfiresmith@gmail.com
<p>I understand there are plans to generalize the ISO plugin for Pulp. This is great, because many of us use it to host arbitrary files such as kickstarts, RPM signing keys, and lots of other things.</p>
<p>This works well when the authoritative repository is already under our control, or Pulp is the authoritative repository. But it is impossible to sync a remote file repository because there won't be a 'PULP_MANIFEST' file.</p>
<p>The generalized files plugin (name TBD?), would be much more useful if it could check for a PULP_MANIFEST file, but then fall back to a recursive link-following scheme in the event that no PULP_MANIFEST exists in the feed.</p>
<p>I'm imagining something analogous to 'wget -r', but I'm not sure if libcurl, nectar, or python-requests has such capability.</p> RPM Support - Issue #1971 (CLOSED - WONTFIX): '--retain-old-count' option not retroactivehttps://pulp.plan.io/issues/19712016-06-03T17:34:07Zkfiresmithkfiresmith@gmail.com
<p>If you update the '--retain-old-count=' option on a previously sync'd repo that has a number of RPM versions greater than the new value, the new value is not retroactive. Currently it appears the only way you can reduce the number of old versions is to delete the repo and re-create/re-sync with the new target value.</p>
<p>Steps to reproduce:</p>
<p>pulp-admin rpm repo create --repo-id=epel-test --feed=<a href="http://download-i2.fedoraproject.org/pub/epel/5/x86_64/" class="external">http://download-i2.fedoraproject.org/pub/epel/5/x86_64/</a> --retain-old-count=2 && pulp-admin rpm repo sync run --repo-id=epel-test<br>
pulp-admin rpm repo list --details --repo-id=epel-test | grep 'Rpm'</p>
<p>pulp-admin rpm repo update --repo-id=epel-test --retain-old-count=1 && pulp-admin rpm repo sync run --repo-id=epel-test<br>
pulp-admin rpm repo list --details --repo-id=epel-test | grep 'Rpm'</p>
<p>The RPM count will <strong>not</strong> change, but should be reduced by 1/3.</p> Pulp - Issue #1946 (CLOSED - DUPLICATE): pulp-admin rpm repo update --relative-url doesn't clean ...https://pulp.plan.io/issues/19462016-05-25T17:14:53Zkfiresmithkfiresmith@gmail.com
<p>Folks,<br>
I've discovered that re-organizing pulp RPM repos is not as easy as it would seem using the 'rpm repo update' function. It appears that cruft is left behind in the form of a directory structure with a single file called 'listing' in each segment of said directory path.</p>
<p>Thus if I have a repository published at /pulp/repos/IBM/7/7Server/x86_64/, and I use 'pulp-admin rpm repo update --repo-id=IBM-server-7 --relative-url=thirdparty/IBM', the new directory structure is published as you would expect at /pulp/repos/thirdparty/IBM, but there is an entire (mostly) empty folder structure left behind at /pulp/repos/IBM.</p> Pulp - Issue #1945 (CLOSED - CURRENTRELEASE): pulp 2.8.3 migration fails on unit 0028https://pulp.plan.io/issues/19452016-05-25T16:56:53Zkfiresmithkfiresmith@gmail.com
<p>Halting migrations due to a migration failure.</p>
<pre><code>[Errno 20] Not a directory: u'/var/lib/pulp/content/units/iso/dd/189ab6381d724c0219065338e058dc65e72221c3f7b8da6957f43d78f0c9f6/189ab6381d724c0219065338e058dc65e72221c3f7b8da6957f43d78f0c9f6'
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 124, in migrate_database
update_current_version=not options.test)
File "/usr/lib/python2.7/site-packages/pulp/server/db/migrate/models.py", line 186, in apply_migration
migration.migrate()
File "/usr/lib/python2.7/site-packages/pulp_rpm/plugins/migrations/0028_standard_storage_path.py", line 17, in migrate
migration()
File "/usr/lib/python2.7/site-packages/pulp/plugins/migration/standard_storage_path.py", line 266, in __call__
batch()
File "/usr/lib/python2.7/site-packages/pulp/plugins/migration/standard_storage_path.py", line 112, in __call__
self._migrate()
File "/usr/lib/python2.7/site-packages/pulp/plugins/migration/standard_storage_path.py", line 101, in _migrate
Unit.migrate(item.plan, item.unit_id, item.storage_path, item.new_path)
File "/usr/lib/python2.7/site-packages/pulp/plugins/migration/standard_storage_path.py", line 364, in migrate
shutil.move(path, new_path)
File "/usr/lib64/python2.7/shutil.py", line 301, in move
copy2(src, real_dst)
File "/usr/lib64/python2.7/shutil.py", line 130, in copy2
copyfile(src, dst)
File "/usr/lib64/python2.7/shutil.py", line 83, in copyfile
with open(dst, 'wb') as fdst:
IOError: [Errno 20] Not a directory: u'/var/lib/pulp/content/units/iso/dd/189ab6381d724c0219065338e058dc65e72221c3f7b8da6957f43d78f0c9f6/189ab6381d724c0219065338e058dc65e72221c3f7b8da6957f43d78f0c9f6'
</code></pre> Pulp - Issue #1844 (CLOSED - CURRENTRELEASE): pulp-admin --config and/or api_prefix option appear...https://pulp.plan.io/issues/18442016-04-14T15:02:34Zkfiresmithkfiresmith@gmail.com
<p>Hi Folks,<br>
This is a show-stopper problem for my AD / kerberos integration efforts I'm putting together for 2.9 documentation.</p>
<p>Because pulp-admin cannot work with kerberos tickets, a split authentication scheme must be used to allow both AD accounts and local pulp accounts to log into Pulp. The easiest way we have thought of to allow this is to have two different api paths via WSGIScriptAlias like so:</p>
<p>WSGIScriptAlias /pulp/api /usr/share/pulp/wsgi/webservices.wsgi<br>
WSGIScriptAlias /pulp-local/api /usr/share/pulp/wsgi/webservices.wsgi</p>
<p>Then having a mod_auth_gssapi conf file to protect logins on the normal API path using AD auth:</p>
<p><Location /pulp/api/v2/actions/login></p>
<ol>
<li>Require TLS (nee SSL).<br>
SSLRequireSSL<br>
SSLOptions +StrictRequire</li>
</ol>
<ol>
<li>Use GSSAPI authentication.<br>
AuthType GSSAPI<br>
AuthName "Pulp Login"</li>
</ol>
<ol>
<li>For paranoia, make GSSAPI also require TLS.<br>
GssapiSSLonly On</li>
</ol>
<ol>
<li>Permit password-based authentication for clients that can't do Negotiate.<br>
GssapiBasicAuth On</li>
</ol>
<ol>
<li>Require a valid user.<br>
require valid-user</li>
</ol>
<p></Location></p>
<p>With these settings in place for Apache, a local login should be possible by using an alternate config file that contains the following api_prefix statement:<br>
api_prefix: /pulp-local/api<br>
...and pointing to the alternate config file via:<br>
pulp-admin -v --config=/etc/pulp/admin/admin-local.conf login -u admin -p <some_password></p>
<p>But this does not happen. Instead, the login command is posted to the normal api path as seen in the logs:</p>
<p>==> /var/log/httpd/ssl_access_log <==<br>
10.xx.xx.xx - - [14/Apr/2016:10:22:47 <del>0400] "POST /pulp/api/v2/actions/login/ HTTP/1.1" 401 451 "</del>" "-"</p>
<p>Frustratingly, using strace it's apparent that the admin-client does in fact source the alternate config file, but it doesn't seem to accept the api_prefix option:</p>
<p>$strace pulp-admin <del>v --config=/etc/pulp/admin/admin-local.conf login -u admin -p ----------------</del> 2>&1 | grep admin-local<br>
open("/etc/pulp/admin/admin-local.conf", O_RDONLY) = 3</p>
<p>Because I don't know how to Python, I'm at a loss to figure out what is broken behind the curtain.</p> Pulp - Issue #1728 (CLOSED - CURRENTRELEASE): Please relax input validation on --login for 'pulp-...https://pulp.plan.io/issues/17282016-02-29T19:04:39Zkfiresmithkfiresmith@gmail.com
<p>While working out the process for setting up AD-integration for Pulp to allow SSO logins in pulp-admin, I discovered that '@' is not an allowed character of a login:</p>
<p>$pulp-admin auth user create --login <a href="mailto:jim_bob@AD.COLLEGE.EDU" class="email">jim_bob@AD.COLLEGE.EDU</a><br>
Validation failed for argument [--login]: value must contain only letters,<br>
numbers, underscores, periods and hyphens</p>
<p>This unfortunately is a show-stopper issue for Pulp at our organization. Please relax the input validation so that we can continue working out how to get mod_auth_kerb set up for pulp.</p>
<p>Thanks!</p> Pulp - Story #1677 (CLOSED - WONTFIX): 'pulp-admin repo history sync' needs more filters to be us...https://pulp.plan.io/issues/16772016-02-15T17:36:05Zkfiresmithkfiresmith@gmail.com
<p>Right now I can iterate over a full list of repos to get a snapshot of the state of repo syncs across my pulp server by running this:</p>
<ol>
<li>for i in $(pulp-admin repo list | grep 'Id:' | awk '{print $2}'); do pulp-admin repo history sync --limit=1 --repo-id=$i; done</li>
</ol>
<p>Unfortunately that will return text for all repos regardless of if they have ever been synced (some repos originate from within pulp thus do not sync...), and cannot be set to not return anything if the last sync was successful.</p>
<p>I would very much like to be able to use pulp-admin to return only a list of repos that had errors syncing, so that I can limit the noise in my logging emails.</p>
<p>A setting that would allow me to filter based on the "Result:" field would be swell and could work like this:</p>
<p>pulp-admin repo history sync --limit=1 --repo-id=EPEL7 --result={error,failed,success}</p> Pulp - Story #1665 (CLOSED - WONTFIX): pulp-consumer repo bind input not validated (pitfall!)https://pulp.plan.io/issues/16652016-02-11T18:06:18Zkfiresmithkfiresmith@gmail.com
<p>Running the command 'pulp-consumer rpm bind --repo-id=foo --repo-id=bar --repo-id=zot' would only bind the 'zot' repo. This might be a troublesome pitfall as no error message is generated.</p>
<p>It should be made clear (perhaps via input validation of the command) that only one '--repo-id' entry will be used and all others are discarded.</p> RPM Support - Story #1658 (CLOSED - WONTFIX): Pulp needs some sort of role-grouping or inheritancehttps://pulp.plan.io/issues/16582016-02-10T20:29:12Zkfiresmithkfiresmith@gmail.com
<p>Currently for each new role I come up with, I have to add every user individually. I would like to be able to organize like users by access level, eg: sysadmins, users, etc. Or maybe by department. Then I could just assign users to a limited set of meta-roles that actually just contain other roles.</p>
<p>Right now if I have a bunch of roles like 'repository-viewer', 'repository-manager', 'content-publisher', etc, I must then enumerate a whole class of user logins for each role like so:</p>
<p>for i in bob sue joe jebediah zeke; do pulp-admin auth role user add --login=$i --role-id=repository-viewer; done<br>
for i in bob sue joe jebediah zeke; do pulp-admin auth role user add --login=$i --role-id=repository-manager; done<br>
for i in bob sue joe jebediah zeke; do pulp-admin auth role user add --login=$i --role-id=content-publisher; done</p>
<p>It sure would be swell to group logins into departments 'org-accounting', 'org-labadmins', 'org-mailroom', then assign myriad relevant and growing permission-containing roles under each of those organizational roles so that as people come and go it's much easier than tacking on a million individual roles to each user.</p>
<p>Hopefully that makes sense...</p> Pulp - Story #1628 (CLOSED - WONTFIX): make repo index listings more readable in a web browser (e...https://pulp.plan.io/issues/16282016-02-03T20:49:44Zkfiresmithkfiresmith@gmail.com
<p>Folks,<br>
By default (thanks Apache...), package listings in repos are really not that useful via a web browser because the default is to truncate filenames after the first 20 bytes.</p>
<p>I easily fixed this globally on my Pulp server by augmenting the following line of /etc/httpd/conf.d/autoindex.conf:<br>
- IndexOptions FancyIndexing HTMLTable VersionSort<br>
+ IndexOptions FancyIndexing HTMLTable VersionSort NameWidth=*</p>
<p>...but this can be fixed in the Pulp installation by adding that option to the right places (up to you guys specifically which) in the pulp_rpm.conf or other pulp-provided files. Attached is a visual example of how much nicer listings are without truncation.</p> Pulp - Story #1595 (CLOSED - DUPLICATE): Pulp item download functionality / linkhttps://pulp.plan.io/issues/15952016-01-28T15:53:32Zkfiresmithkfiresmith@gmail.com
<p>I believe it would be very useful for sysadmins who have access to pulp-admin with at least read privs to be able to download content returned in a search of ISO and RPM repositories.</p>
<p>This would save people from having to go to the web interface and browse to what they need. In absence of this functionality, at least having a hyperlink to the item returned in a --detail search would be a big improvement. Optimally, having both aspects of this RFE put in place would give maximum flexibility and choice to the sysadmin who prefers to do as much as possible within pulp-admin.</p>
<p>Below is a simple mockup of my idea for a --detail return with this new feature:</p>
<ol>
<li>pulp-admin iso repo isos --repo-id=IT_Kickstart --detail<br>
Metadata:<br>
Checksum: 85fc7aa085882e5c3df02f54c6d78c1aa914564ec61f1099d4017b4014f89e83<br>
Name: _RHEL7-enterpriseMgmt-template-pup4-01:2:ITS-Department<br>
Size: 16467<br>
Updated: 2016-01-28T15:28:58Z<br>
Repo Id: IT_Kickstart<br>
Created: 2016-01-28T15:28:58Z<br>
Unit Id: be782341-03a3-48b8-9879-2d1da90f43aa<br>
Unit Type Id: iso<br>
Id: 56aa33baa8b2df7b8aab0b8e<br>
Url: <a href="https://pulp.college.edu/pulp/isos/IT_Kickstart/_RHEL7-enterpriseMgmt-template-pup4-01:2:ITS-Department" class="external">https://pulp.college.edu/pulp/isos/IT_Kickstart/_RHEL7-enterpriseMgmt-template-pup4-01:2:ITS-Department</a>
</li>
</ol> Pulp - Story #1588 (CLOSED - WONTFIX): pulp-admin rpm repo list --fields should be able to return...https://pulp.plan.io/issues/15882016-01-27T15:04:34Zkfiresmithkfiresmith@gmail.com
<p>Currently when an admin uses "--fields" to slice output of an RPM repo listing, only "id,description,display_name,content_unit_counts" appear to be able to be used. I believe it would be very useful for pulp-admin to return any of the following fields, which are all displayed when you run the --detail switch:</p>
<p>Id: Display Description: Content Erratum: Package Package Package Rpm: Yum Notes: Importers: Config: Feed: Proxy Proxy SSL SSL SSL Id: Importer Last Repo Scheduled Distributors: Auto Config: Checksum Http: Https: Relative Distributor Id: Last Repo Scheduled Auto Config: Http: Https: Distributor Id: Last Repo Scheduled.</p>
<p>A mockup example of what would be handy follows:</p>
<ol>
<li>pulp-admin rpm repo list --fields="id,display_name,relative_url"<br>
<span><del>--------------------------------------------------------------------</del></span><br>
RPM Repositories<br>
<span><del>--------------------------------------------------------------------</del></span>
</li>
</ol>
<p>Id: EPEL7<br>
Display Name: EPEL7<br>
Relative URL: /epel/7/x86_64/</p>
<p>Id: EPEL6<br>
Display Name: EPEL6<br>
Relative URL: /pub/epel/6/x86_64/</p>