Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1528275

Summary:	Content Host : Bulk actions need to be updated to use dynflow
Product:	Red Hat Satellite	Reporter:	Djebran Lezzoum <dlezzoum>
Component:	Hosts - Content	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED NOTABUG	QA Contact:	Katello QA List <katello-qa-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.3.0	CC:	aladke, anerurka, bbuckingham, bkearney, chrobert, cwelton, dlezzoum, ekin.meroglu, fdacunha, fvzwieten, inecas, jalviso, jcall, jsherril, kshirsal, lzap, mgamboap, pmutha, sauchter, snemeth, stbenjam
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1108106	Environment:
Last Closed:	2018-05-02 12:18:53 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:
Embargoed:
Bug Depends On:	1108106
Bug Blocks:

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).