Issue #1552
closed
applicable errata regeneration tasks not getting spawned
Status:
CLOSED - CURRENTRELEASE
Description
1) Get the zoo5 repo from -> https://github.com/Katello/runcible/tree/master/test/fixtures/repositories/zoo5 (we just need the repo.) Steps below will assume file:///var/www/repositories/zoo5 is the destination
2)
$ pulp-admin rpm repo create --repo-id=ideate --feed=file:///var/www/repositories/zoo5
3)
Call the content regeneration api with the following rest call.
D, [2016-01-19T12:32:46.797858 #5378] DEBUG -- : RestClient.post "https://<FQDN>/pulp/api/v2/repositories/actions/content/regenerate_applicability//", "{\"repo_criteria\":{\"filters\":{\"id\":{\"$in\":[\"ideate\"]}}}}", "Accept"=>"*/*; q=0.5, application/xml", "Accept-Encoding"=>"gzip, deflate", "Content-Length"=>"68", "accept"=>"application/json", "content_type"=>"application/json"
The response will show that no spawned tasks are created.
- Status changed from NEW to ASSIGNED
- Assignee set to semyers
- Priority changed from Normal to High
- Severity changed from 2. Medium to 3. High
- Platform Release set to 2.8.0
- Triaged changed from No to Yes
This looks a lot like #1448, but given the slew of issues opened about incorrectly mapped inbound fields in criteria, it's possible that this issue is separate. I'll take a closer look and make sure, but right now I'm thinking that this issue is about the tasks not being spawned because no repo will match the criteria POSTed, and #1448 is about the lack of call reports in the response.
I think it's likely that the repo_criteria in the POST data is not being translated correctly, and needs a similar tweak to what's need in issues like #1527 (et al).
Also, and if it's true that the tasks aren't even being spawned because of field translation issues, this would block #1448. In that case, you'll definitely not ever see a useful call report in the response even if we fixed that view to return them, since no tasks will be made to report on.
- Blocked by Issue #1448: Generating repo content applicability doesn't return call report added
- Blocked by deleted (Issue #1448: Generating repo content applicability doesn't return call report)
- Related to Issue #1448: Generating repo content applicability doesn't return call report added
I believe this is currently fixed on master, but it's difficult to be sure unless the fix that was POSTed in #1448 has been applied. Once that issue goes to MODIFIED I'll retest and adjust this issue accordingly.
- Status changed from ASSIGNED to MODIFIED
This was fixed by a combination of #1448 and either #1478 or #1490 (not sure which), and will be released with 2.8.0.
- Status changed from MODIFIED to 5
- Status changed from 5 to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
.