- Login: bcourt
- Email: firstname.lastname@example.org
- Registered on: 10/16/2014
- Last connection: 02/06/2017
|Docker Support||Private Access, Contributor||12/17/2014|
|Pulp||Private Access, Contributor||12/16/2014|
|Puppet Support||Private Access, Contributor||12/17/2014|
|Python Support||Private Access, Contributor||12/17/2014|
|RPM Support||Private Access, Contributor||12/17/2014|
Task #1213 (MODIFIED): Orphan listing and removal does not work with mongoengine converted modelsIf you have an orphan in your repo and attempt to list it and then remove it and both will fail. For example if testing against the [in-development puppet conversion to mongoengine](https://github.com/pulp/pulp_puppet/compare/master...bm...
Do you have any modifications that you would suggest for the pulp systemd service definitions to ensure that pulp starts after NFS?
Issue #1202: pulp_celerybeat,pulp_resource_manager fail to start on bootI am running a reasonably stock Katello 2.3 on C7 and when I reboot the system celerybeat and resource_maager do not start.
They can be restarted via systemctl and run just fine.
Aug 17 09:23:49 foreman systemd: pulp_celerybeat.ser...
The pulp puppet handler requires the newer version of puppet.
Issue #1194 (CLOSED - NOTABUG): yum groupinstall pulp-consumer-qpid upgrades default puppetIt was recently reported that yum groupinstall pulp-consumer-qpid upgraded puppet version (2.6.7 -\> 2.7.x) on the clients. As a result of which puppet master(2.6.x) s communication with puppet clients. we are not using pulp for puppet d...
The fix will likely affect multiple projects.
Issue #1174: The help text for remove needs to be rewordedHelp text for remove says "remove copied or uploaded modules from a repository"
But we can remove synced content as well.
For rpm it says
remove copied or uploaded modules from a repository
For iso repo it says
Eliminate the lock for individual consumer applicability calculation as part of this.
Issue #1173: Content Applicability Regeneration for individual consumers is sent to a single workerThe same tags are used when calculating applicability for a single consumer \[0\] as for all consumers bound to a specific repo \[1\]. As a result when multiple consumers are registered within a short amount of time, the tasks to generat...
If you would like to open a pull request on http://www.github.com/pulp/pulp_rpm/ we would be happy to merge this change.
Issue #1171: typo in documentation of pulp_rpmThere is in documentation:
pulp-admin rpm repo create --repo-id=zoo--relative-url=zoo
which is obviously wrong (missing space). See attached patch for fix.
This appears to be happening because the web server is redirecting from an http to an ftp url and nectar is not following the protocol change.
Issue #1170: rpm importer does not support switching protocols from http to ftp mid download using a redirect- fails downloading distribution filesI was unsure whether to open this as an issue here, with Nectar or with RPM Support so defaulting to top level.
pulp-admin rpm repo create --relative-url test --feed http://www.gtlib.gatech.edu/pub/centos/6.6/os/x86_6...
Please reopen if this problem re-occurs. Thanks
Issue #1164 (CLOSED - WORKSFORME): pulp sync fails randomlyBellow you can see the same command executed a few times, where the first runs it throws an error. Nothing was changed between runs.
Only one of the pulp servers has this problem.
pulp-server should include a file here that does nothing so the directive will be valid.
Issue #418: pulp does not start if no plugins that place a file in /etc/pulp/vhosts80 are installedDescription of problem:
Updating from Alpha I've encountered a syntax error in \`/etc/httpd/conf.d/pulp.conf\`
It seems to be caused by the wildcard not being able to match anything in the target directory of the Include statement:...
1\) pulp.server.managers.content.upload.ContentUploadManager#import_uploaded_unit should check status from the report generated by the plugin.
2\) All the plugins upload code should raise an exception if the import fails... Issue #1189: Puppet module upload failure error reporting is inconsistent with other tasksUploading a puppet module that fails will lead you with something that looks like:
Also available in: Atom