Bug 1304289

Summary: pulp-admin tasks list has empty Resources on content_applicability_regeneration operation
Product: Red Hat Satellite Reporter: Pavel Moravec <pmoravec>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.1.6CC: bkearney, ktordeur, oshtaier, satellite6-bugs
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-25 12:53:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Pavel Moravec 2016-02-03 09:16:30 UTC
Description of problem:
When troubleshooting content applicability issues ("why Satellite WebUI shows no errata applicable to my host, when yum shows some erratas?"), pulp-admin tasks list should provide information when/if regenerate applicbility task was run for the given host.

But such a task details does not provide any host id - example of task detail:

Operations:  content_applicability_regeneration
Resources:
State:       Successful
Start Time:  2016-01-29T13:20:07Z
Finish Time: 2016-01-29T13:20:07Z
Task Id:     0b261df7-c09b-49e8-8392-a8aee0921dbc


Please fill Resources by the host id (FQDN or rhsm uuid).


Version-Release number of selected component (if applicable):
pulp-admin-client-2.6.0.19-1.el7sat.noarch
pulp-server-2.6.0.19-1.el7sat.noarch


How reproducible:
100%


Steps to Reproduce:
1. Have a Content Host registered to Sat and running goferd (that triggers both candlepin and pulp applicability regeneration)
2. Install pulp-admin per https://access.redhat.com/solutions/1295653
3. pulp-admin tasks list


Actual results:
task list having tasks like:
Operations:  content_applicability_regeneration
Resources:
State:       Successful
Start Time:  2016-01-29T13:20:07Z
Finish Time: 2016-01-29T13:20:07Z
Task Id:     0b261df7-c09b-49e8-8392-a8aee0921dbc

with empty Resources / no identification of the Content Host.


Expected results:
Resources to have some Content Host id.


Additional info:

Comment 2 Pavel Moravec 2016-02-04 15:19:17 UTC
And the cause is... pulp does not write to mongo that information at all.

task_status collection usual entry:

{
        "_id" : ObjectId("56ab67078b238b6b6fd04628"),
        "exception" : null,
        "task_type" : "pulp.server.managers.consumer.applicability.regenerate_applicability_for_consumers",
        "task_id" : "0b261df7-c09b-49e8-8392-a8aee0921dbc",
        "tags" : [
                "pulp:action:content_applicability_regeneration"
        ],
        "finish_time" : "2016-01-29T13:20:07Z",
        "_ns" : "task_status",
        "start_time" : "2016-01-29T13:20:07Z",
        "traceback" : null,
        "spawned_tasks" : [ ],
        "progress_report" : {

        },
        "state" : "finished",
        "worker_name" : "reserved_resource_worker-5.brq.redhat.com",
        "result" : null,
        "error" : null,
        "id" : "56ab6707c44bb23e5a5447e8"
}

lack consumer_id information :-/

Comment 3 Kenny Tordeurs 2016-02-10 14:54:19 UTC
Since the upgrade to 6.1.6 the errata not showing as applicable for any content hosts, when navigating to Content => Errata (Remove the checkbox for applicable) and all errata will show.

Similar/Related BZ for errata not showing as applicable: 
https://bugzilla.redhat.com/show_bug.cgi?id=1302663
https://bugzilla.redhat.com/show_bug.cgi?id=1303958

Comment 4 Bryan Kearney 2016-04-22 21:00:25 UTC
ktordeur can you please verify that the errata are now showing up? You will need to intiate a new sync from the CDN. There was an issue with the metatadate that should now be resolved.

Comment 5 Kenny Tordeurs 2016-04-25 07:12:52 UTC
bkearney I confirm the errata are now showing up.

Thanks
Kenny

Comment 6 Bryan Kearney 2016-04-25 12:53:23 UTC
I am closing this out since it was an issue with the CDN. If you are still seeing the issue, please feel free to re-open.