Bug 1528275 - Content Host : Bulk actions need to be updated to use dynflow
Summary: Content Host : Bulk actions need to be updated to use dynflow
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts - Content
Version: 6.3.0
Hardware: All
OS: Linux
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On: 1108106
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-21 12:11 UTC by Djebran Lezzoum
Modified: 2020-12-14 10:57 UTC (History)
21 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1108106
Environment:
Last Closed: 2018-05-02 12:18:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 4 Brad Buckingham 2018-01-04 18:39:05 UTC
Are the bulk actions being executed via Remote Execution or katello-agent?

If by katello-agent, that will not generate a task today as indicated by https://bugzilla.redhat.com/show_bug.cgi?id=1108106#c15.  Another bug (bug 1418993) was raised as an RFE to add that support.

If using katello-agent, I'd recommend marking this as a duplicate of bug 1418993.

Comment 5 Djebran Lezzoum 2018-01-10 09:45:54 UTC
The bulk actions are executed via katello-agent, as per https://bugzilla.redhat.com/show_bug.cgi?id=1528275#c2 the original cause is not to show the task status, the problem is that the bulk package install is not working, and cloned this bug as the original bug was flagged as duplicate to https://bugzilla.redhat.com/show_bug.cgi?id=1108106, if I mark this bug as duplicate, I have to create an other bug for bulk package install.

What do you think?

Comment 6 Brad Buckingham 2018-03-21 12:46:20 UTC
Djebran,

Thanks for the clarification.  As mentioned, when doing the bulk operations using katello-agent, no task is created in Satellite for the request.  Since there are no errors in the production.log, it could be that an error occurred in pulp or when interacting with the client.  If so, this could be a bug or configuration issue.

I would recommend increasing the log level in Satellite to capture the REST calls between katello-pulp, run the scenario and capture all logs (e.g foreman-debug) for the server and the client (e.g. gofer agent.log).  It may also be useful to confirm that the client is connecting properly to the server (e.g. restart goferd on the client and ensure that AMQP is reporting as 'connected' in the agent.log).


Note You need to log in before you can comment on or make changes to this bug.