Bug 1129391 - Create and Delete Activation keys create incorrect Task names
Summary: Create and Delete Activation keys create incorrect Task names
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Christine Fouant
QA Contact: Roman Plevka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-12 15:59 UTC by sthirugn@redhat.com
Modified: 2019-09-26 16:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 08:43:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1112781 0 unspecified CLOSED Dynflowize activation key delete 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1173091 0 unspecified CLOSED Content View Version destroy task name missing 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2016:1500 0 normal SHIPPED_LIVE Red Hat Satellite 6.2 Base Libraries 2016-07-27 12:24:38 UTC

Internal Links: 1112781 1173091

Description sthirugn@redhat.com 2014-08-12 15:59:55 UTC
Description of problem:
Create and Delete Activation keys does not create meaningful Task names

Version-Release number of selected component (if applicable):
GA Snap 4 - Satellite-6.0.4-RHEL-6-20140806.0

* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.19-1.el6_5.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.9.19-1.el6_5.noarch
* candlepin-tomcat6-0.9.19-1.el6_5.noarch
* elasticsearch-0.90.10-4.el6sat.noarch
* foreman-1.6.0.38-1.el6sat.noarch
* foreman-compute-1.6.0.38-1.el6sat.noarch
* foreman-gce-1.6.0.38-1.el6sat.noarch
* foreman-libvirt-1.6.0.38-1.el6sat.noarch
* foreman-ovirt-1.6.0.38-1.el6sat.noarch
* foreman-postgresql-1.6.0.38-1.el6sat.noarch
* foreman-proxy-1.6.0.23-1.el6sat.noarch
* foreman-selinux-1.6.0.4-1.el6sat.noarch
* foreman-vmware-1.6.0.38-1.el6sat.noarch
* katello-1.5.0-28.el6sat.noarch
* katello-ca-1.0-1.noarch
* katello-certs-tools-1.5.6-1.el6sat.noarch
* katello-installer-0.0.57-1.el6sat.noarch
* openldap-2.4.23-34.el6_5.1.x86_64
* pulp-katello-0.3-3.el6sat.noarch
* pulp-nodes-common-2.4.0-0.30.beta.el6sat.noarch
* pulp-nodes-parent-2.4.0-0.30.beta.el6sat.noarch
* pulp-puppet-plugins-2.4.0-0.30.beta.el6sat.noarch
* pulp-puppet-tools-2.4.0-0.30.beta.el6sat.noarch
* pulp-rpm-plugins-2.4.0-0.30.beta.el6sat.noarch
* pulp-selinux-2.4.0-0.30.beta.el6sat.noarch
* pulp-server-2.4.0-0.30.beta.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
* ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch
* sssd-ldap-1.11.5.1-3.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Create an activation key "ak1" in org "ACME"
2. Delete the activation key "ak1"
3. Navigate to Monitor -> Tasks


Actual results:
Create Organization 'ACME'
Delete Activation Key organization 'ACME'

Expected results:
Create Activation Key 'ak1'; Organization 'ACME'
Delete Activation Key 'ak1'; organization 'ACME'

Additional info:

Comment 1 David Davis 2014-08-12 16:01:36 UTC
This seems to work on master. I'm wondering if it's an outdated version of foreman-tasks?

Comment 3 Christine Fouant 2015-07-20 19:01:20 UTC
Tested on 6.1 Snap 13, could not reproduce this error. Output is as follows:

Create activation key 'ak1'; organization 'ACME'
Delete Activation Key activation key 'ak1'; organization 'ACME'

Comment 4 Roman Plevka 2015-08-05 08:10:01 UTC
VERIFIED
The output is as follows:

Create activation key 'ak1'; organization 'äñøÌóÛÐÉùôóúõüâíÈëÃ'
Delete Activation Key activation key 'ak1'; organization 'äñøÌóÛÐÉùôóúõüâíÈëÃ'

Tested with:
sat6-Satellite-6.1.0-RHEL-7-20150731.1

Comment 7 errata-xmlrpc 2016-07-27 08:43:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1500


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