mkovacik@redhat.com
- Login: mkovacik@redhat.com
- Email: mkovacik@redhat.com
- Registered on: 02/19/2015
- Last connection: 06/29/2015
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 34 | 34 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| Container Support | Private Access | 12/06/2019 |
| Crane | Private Access | 02/19/2015 |
| Debian Support | Private Access | 02/19/2015 |
| Docker Support | Private Access | 02/19/2015 |
| File Support | Private Access | 07/17/2017 |
| Migration Plugin | Private Access | 01/14/2020 |
| Nectar | Private Access | 02/19/2015 |
| OSTree Support | Private Access | 02/19/2015 |
| Packaging | Private Access | 02/19/2015 |
| Pulp | Private Access | 02/19/2015 |
| Puppet Support | Private Access | 02/19/2015 |
| Python Support | Private Access | 02/19/2015 |
| RPM Support | Private Access | 02/19/2015 |
Activity
06/30/2015
-
This isn't a bug; `auto_publish = True` crept into the test case repository settings.
Mea culpa.
Issue #1095 (CLOSED - NOTABUG): publish-type event handlers called twice with a wildcard rpm-repo http event-listenerA wildcard-type http event listener gets triggered 6 times in total instead of 4 until its repo sync\&publish tasks finish.
How reproducible:
Always
Steps to reproduce:
- "clone" zoo repo
- create a [requestb.in](http://...
06/29/2015
-
Inspecting the requestbin, the event listener callbacks count matches what the test case reports.
Moreover, the requestbin log shows what callbacks were duplicated:
`[mkovacik@zrnko pulp-automation]$ curl http://requestb.in/api/v1/bi... Issue #1095: publish-type event handlers called twice with a wildcard rpm-repo http event-listenerA wildcard-type http event listener gets triggered 6 times in total instead of 4 until its repo sync\&publish tasks finish.
How reproducible:
Always
Steps to reproduce:
- "clone" zoo repo
- create a [requestb.in](http://... -
A wildcard-type http event listener gets triggered 6 times in total instead of 4 until its repo sync\&publish tasks finish.· Closed issue
How reproducible:
Always
Steps to reproduce:
- "clone" zoo repo
- create a [requestb.in](http://...
06/18/2015
-
Issue #1064 (CLOSED - WONTFIX): rpm repo group distributor requires undocumented _repo-type key to be present in repo.notes dictif the `_repo-type` key isn't present in `repo.notes` of particular repo, following error can be seen when a repo group containing this repo gets published:
~~~
Jun 18 07:58:25 ip-172-31-24-137 pulp: celery.worker.job:ERROR: (5962-96...
06/05/2015
-
Issue #1033 (CLOSED - CURRENTRELEASE): Error during build_session does not propagate to importerAn error risen in `threaded.py:build_session` doesn't propagate out of a worker thread causing a repo sync to get stuck.
Actually, I have just a single reproducer using `pulp-admin rpm repo create ... --proxy-host` without specifying ...
06/04/2015
-
Story #1032 (CLOSED - WONTFIX): Allow plain hostname as config.proxy_url in downloadersHaving specified plain hostname as `config.proxy_url`, following traceback can be seen in the logs:
`[root@ip-172-31-24-137 ~]# less /var/log/messages`
~~~text
Jun 4 16:01:17 ip-172-31-24-137 pulp: celery.worker.job:INFO: Task pu...
06/01/2015
-
Issue #1020 (CLOSED - WONTFIX): Scheduled Tasks failure_treshold doesn't workThe scheduler's `failure_threshold` attribute doesn't work --- a Scheduled task failing more times consecutively doesn't get cancelled automatically as opposed to what the [documentation](https://pulp.readthedocs.org/en/latest/dev-guide/...
-
Story #1019 (CLOSED - WONTFIX): Add ScheduleID to Tasks spawned by schedulersAt the moment, one can't link schedule-spawned tasks to their particular [schedule](https://pulp.readthedocs.org/en/latest/dev-guide/conventions/scheduled.html#scheduled-tasks).
As a result, one can't tell easily whether e.g. schedule...
05/27/2015
-
Guys, thanks. I agree. The non-mandatory switch makes most sense.
Story #1005: pulp-admin docker repo create misses mandatory option --feedAt the moment it is possible to create a docker repo without specifying `--feed` on the command line.
Later when synchronizing the repo, it leads to a server-side exception verifying mandatory fields presence:
~~~
[root@ip-172-31-... -
Btw, to stop the logs from appearing issue a `service httpd restart`
Issue #1006: Pulp server REST API status call causes a kombu connection exception to appear in the logs each 10sThis seems to be caused by call to `pulp/server/managers/status.py:get_broker_conn_status` as when I by-pass its block by directly returning `{'connected': True}` I can't reproduce the issue anymore.
Please note there's no exception t...
Also available in: Atom
.