skarmark@redhat.com
- Login: skarmark@redhat.com
- Email: skarmark@redhat.com
- Registered on: 12/17/2014
- Last connection: 03/02/2015
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 6 | 6 |
Reported issues | 0 | 7 | 7 |
Projects
Project | Roles | Registered on |
---|---|---|
Docker Support | Contributor | 12/17/2014 |
Pulp | Contributor | 12/17/2014 |
Puppet Support | Contributor | 12/17/2014 |
Python Support | Contributor | 12/17/2014 |
RPM Support | Contributor | 12/17/2014 |
Activity
03/06/2015
-
Reassigning since I still have some QA work to help preethi on my plate. Not sure whether I will be able to get this one fixed. If I get some time during the break, this could be my first PR for Pulp as a community member :).
Issue #666 (NEW): Running a Node bind on a repo that is already bound to the consumer results in the repo showing up twice in the bindingsDescription of problem:
If you run node bind on a repo that is already bound to the consumer, the repo will show up twice in the bindings
Version-Release number of selected component (if applicable):
\[root@rhsm-jenkins \~\]\# r...
03/05/2015
-
https://github.com/pulp/pulp/pull/1698
Story #145 (MODIFIED): As a pulp-admin user, I would like logs to go to stderrRecapping some of the ideas:
RCM typically uses the Pulp API for tasks, but occasionally needs to run multiple pulp-admin commands in parallel. Currently this is impossible due to the way pulp-admin works.
- stop pulp-admin from ...
03/02/2015
-
Task #143 (MODIFIED): Tag pulp-python-0.0.0-1.fc21 into pulp-2.6-fedora21Currently the pulp-2.6-fedora21 target does not exist in Koji, but once it does we need to run this command:
$ koji tag-build pulp-2.6-fedora21 pulp-python-0.0.0-1.fc21
It is important to do this before we release. Otherwise, the P...
03/01/2015
-
This indeed seems to be the problem. Pulp is creating another redundant subdirectory when storing and publishing drpms.
$ sudo ls -l /var/lib/pulp/published/yum/master/yum_distributor/test-drpm/1421108941.15/drpms/drpms
total 72
lrw... Issue #644: yum-presto can't find the drpms, delta rpm filesDescription of problem:
The drpms files are in the wrong sub-directory after a sync and publish .
Version-Release number of selected component (if applicable):
pulp 2.4.3 Product https://repos.fedorapeople.org/repos/pulp/pulp/st... -
\+ This comment was cloned from [Bugzilla #1175332 comment 2]...
02/28/2015
-
Merged above PR. Moving to 3.0.
\+ This comment was cloned from [Bugzilla #1165403 comment 3](https://bugzilla.redhat.com/show_bug.cgi?id=1165403#c3) +
Issue #621: Deprecate the cacert and cakey settings in server.confDescription of problem:
The cacert and cakey settings in server.conf are currently used to configure Pulp to use a CA for signing client certificates generated by Pulp. These settings often confuse our users, as they tend to think it ... -
\+ This comment was cloned from [Bugzilla #1165403 comment 2](https://b... -
We need a little more information about the steps to reproduce. Can you specify which specific puppet publisher did you use in step 3? Also which exact directory in step 4?
\+ This comment was cloned from [Bugzilla #1128270 comment 1](h... Issue #488: Foreman is unable to read puppet modules when permissions in tarfile are 700/600Description of problem:
Some of my puppet modules were created on a system with a umask of 0077 so all of the files have perms of 0700/0600. When pulp preserves the permissions from the tarfile, these are only readable by the apache u... -
We need to raise a validation error with information about why the validation failed instead of a generic traceback.
\+ This comment was cloned from [Bugzilla #1128269 comment 1](https://bugzilla.redhat.com/show_bug.cgi?id=1128269#c1) +
Issue #487: Malformed Puppet Modules Cause Pulp ExceptionDescription of problem: If a puppet module is malformed Pulp shows the user an exception. Malformed could be that the full module name is missing an author (0 dashed is full module name) or that the name portion of the full module name c... -
Merged https://github.com/pulp/pulp/pull/1491. Moving to 3.0 target relase.
\+ This comment was cloned from [Bugzilla #1123509 comment 5](https://bugzilla.redhat.com/show_bug.cgi?id=1123509#c5) +
Issue #475: Deprecate the [server] ssl_ca_certificate setting, replacing with a new CA path settingWe currently have a setting in the \[server\] section of server.conf called ssl_ca_certificate. It must be a path to a specific CA certificate that is used for consumer yum repo files to validate that the Yum repository's SSL certificate...
Also available in: Atom