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 1135574

Summary:

dynflow: 'Destroy Content Host' calls are not associated with a user in UI

Product:

Red Hat Satellite

Reporter:

Corey Welton <cwelton>

Component:

Content Management

Assignee:

Katello Bug Bin <katello-bugs>

Status:

CLOSED CURRENTRELEASE

QA Contact:

Tazim Kolhar <tkolhar>

Severity:

medium

Docs Contact:

Priority:

unspecified

Version:

6.0.3

CC:

bkearney, cwelton, tkolhar

Target Milestone:

Unspecified

Keywords:

Triaged

Target Release:

Unused

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2015-08-12 14:02:01 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:

1208100

Bug Blocks:

Attachments:

Description	Flags
Dyn flow task not associated with user call	none
Dyn flow task associated with user call - user coloumn displayed	none

Description Corey Welton 2014-08-29 16:34:42 UTC

Description of problem:

When "Destroy Content Host" is called, the dynflow UI does not show a user associated with the call. 


Version-Release number of selected component (if applicable):
Satellite-6.0.4-RHEL-7-20140829.0

How reproducible:


Steps to Reproduce:
1.  Initiate a "Destroy Content Host" call -- possibly by reregistering a box, etc.
2.  Monitor > Tasks
3.  View results 

Actual results:

Destroy Content Host system 'qe-blade-04.idmqe.lab.eng.bos.redhat.com'; organization 'Default_Organization'	stopped	success	2014-08-29 15:48:12 UTC	

Expected results:

Destroy Content Host system 'qe-blade-04.idmqe.lab.eng.bos.redhat.com'; organization 'Default_Organization'	stopped	success	2014-08-29 15:48:12 UTC	 admin

Additional info:

Comment 2 Bryan Kearney 2015-04-15 11:58:36 UTC

Per Eric Helms, this should be fixed by https://bugzilla.redhat.com/show_bug.cgi?id=1208100

Comment 4 Tazim Kolhar 2015-04-24 10:55:31 UTC

FAILEDQA:

# rpm -qa | grep foreman
foreman-libvirt-1.7.2.17-1.el6_6sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.10-1.el6_6sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el6_6sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el6_6sat.noarch
foreman-postgresql-1.7.2.17-1.el6_6sat.noarch
foreman-debug-1.7.2.17-1.el6_6sat.noarch
foreman-1.7.2.17-1.el6_6sat.noarch
foreman-ovirt-1.7.2.17-1.el6_6sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.3-1.el6_6sat.noarch
foreman-proxy-1.7.2.4-1.el6_6sat.noarch
qe-sat6-rhel66.usersys.redhat.com-foreman-client-1.0-1.noarch
qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-selinux-1.7.2.13-1.el6_6sat.noarch
rubygem-hammer_cli_foreman-0.1.4.9-1.el6_6sat.noarch
foreman-compute-1.7.2.17-1.el6_6sat.noarch
foreman-vmware-1.7.2.17-1.el6_6sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el6_6sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch
qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-1.0-2.noarch
ruby193-rubygem-foreman_docker-1.2.0.9-1.el6_6sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.7-1.el6_6sat.noarch
foreman-gce-1.7.2.17-1.el6_6sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.9-1.el6_6sat.noarch

steps
1.  Initiate a "Destroy Content Host" call -- possibly by reregistering a box, etc.
2.  Monitor > Tasks
3.  View results 

screen shot attached

Comment 5 Tazim Kolhar 2015-04-24 10:56:18 UTC

Created attachment 1018397 [details]
Dyn flow task not associated with user call

Comment 6 Tazim Kolhar 2015-04-27 07:16:09 UTC

VERIFIED:

# rpm -qa | grep foreman
foreman-libvirt-1.7.2.17-1.el6_6sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.10-1.el6_6sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el6_6sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el6_6sat.noarch
foreman-postgresql-1.7.2.17-1.el6_6sat.noarch
foreman-debug-1.7.2.17-1.el6_6sat.noarch
foreman-1.7.2.17-1.el6_6sat.noarch
foreman-ovirt-1.7.2.17-1.el6_6sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.3-1.el6_6sat.noarch
foreman-proxy-1.7.2.4-1.el6_6sat.noarch
qe-sat6-rhel66.usersys.redhat.com-foreman-client-1.0-1.noarch
qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-selinux-1.7.2.13-1.el6_6sat.noarch
rubygem-hammer_cli_foreman-0.1.4.9-1.el6_6sat.noarch
foreman-compute-1.7.2.17-1.el6_6sat.noarch
foreman-vmware-1.7.2.17-1.el6_6sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el6_6sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch
qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-1.0-2.noarch
ruby193-rubygem-foreman_docker-1.2.0.9-1.el6_6sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.7-1.el6_6sat.noarch
foreman-gce-1.7.2.17-1.el6_6sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.9-1.el6_6sat.noarch

1.  Initiate a "Destroy Content Host" call -- possibly by reregistering a box, etc.
2.  Monitor > Tasks
3.  View result
Destroy Content Host system 'qe-sat6-rhel66.usersys.redhat.com'; organization 'Default Organization' stopped success 2015-04-27 07:12:55 UTC foreman_admin

screenshot attached

Comment 7 Tazim Kolhar 2015-04-27 07:17:39 UTC

Created attachment 1019251 [details]
Dyn flow task associated with user call - user coloumn displayed

Comment 8 Bryan Kearney 2015-08-11 13:27:48 UTC

This bug is slated to be released with Satellite 6.1.

Comment 9 Bryan Kearney 2015-08-12 14:02:01 UTC

This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.