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 1079154 - 'Publish' and 'promotion' links under 'Tasks' shows redundant info like: {}
Summary: 'Publish' and 'promotion' links under 'Tasks' shows redundant info like: {}
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: Ivan Necas
QA Contact: sthirugn@redhat.com
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-21 05:26 UTC by Sachin Ghai
Modified: 2019-09-26 18:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-11 12:23:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Just {} under Details doesn't make sense. (33.37 KB, image/png)
2014-03-21 05:26 UTC, Sachin Ghai 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 5950 0 None None None 2016-04-22 16:09:51 UTC

Description Sachin Ghai 2014-03-21 05:26:34 UTC 
Created attachment 877125 [details]
Just {} under Details doesn't make sense.

Description of problem:
I created a CV, publish and promoted to next env, when I go to 'Tasks' tab, I found Publish and Promotion links.. I clicked them to get the details.. but looks like either something is missing or it shows redundant info under 'Deatails' like {}

Version-Release number of selected component (if applicable):
snap4
rubygem-katello_api-0.0.8-2.el6sat.noarch
ruby193-rubygem-katello-1.5.0-22.el6sat.noarch
katello-repos-1.5.1-1.git.14.0868bd1.el6.noarch
rubygem-hammer_cli_katello-0.0.3-5.el6sat.noarch
katello-1.5.0-18.el6sat.noarch
katello-certs-tools-1.5.5-1.el6sat.noarch
katello-installer-0.0.28-1.el6sat.noarch
pulp-katello-plugins-0.2-1.el6sat.noarch
katello-ca-1.0-1.noarch
katello-apache-1.0-1.noarch
foreman-selinux-1.5.0-0.develop.el6sat.noarch
rubygem-hammer_cli_foreman-0.0.18-7.el6sat.noarch
foreman-proxy-1.5.3-1.el6sat.noarch
ruby193-rubygem-foreman-tasks-0.4.0-5.el6sat.noarch
rubygem-foreman_api-0.1.11-3.el6sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.1-4.el6sat.noarch
foreman-postgresql-1.5.0.9-1.el6sat.noarch
foreman-1.5.0.9-1.el6sat.noarch
foreman-release-1.5.0-0.develop.201403182248gitdf471c7.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. create a CV
2. Publish it and promote to next env
3. go to 'Tasks' tab, click on 'Publish' and 'Promote' links

Actual results:
{} displayed under 'Details'

Expected results:
Just {} under Details doesn't make sense.

Additional info:
Comment 1 RHEL Program Management 2014-03-21 05:44:27 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Brad Buckingham 2014-05-27 16:49:01 UTC 
Created redmine issue http://projects.theforeman.org/issues/5950 from this bug
Comment 4 Ivan Necas 2014-05-30 07:40:46 UTC 
http://projects.theforeman.org/issues/5950
Comment 5 Ivan Necas 2014-06-04 21:55:14 UTC 
I believe this change made it to the snaps already
Comment 7 sthirugn@redhat.com 2014-09-03 19:58:11 UTC 
Verified. I dont see empty {} anymore.

Version Tested:
GA Snap 7 - Satellite-6.0.4-RHEL-6-20140829.0

* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.23-1.el6_5.noarch
* candlepin-common-1.0.1-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.23-1.el6_5.noarch
* candlepin-tomcat6-0.9.23-1.el6_5.noarch
* elasticsearch-0.90.10-6.el6sat.noarch
* foreman-1.6.0.42-1.el6sat.noarch
* foreman-compute-1.6.0.42-1.el6sat.noarch
* foreman-gce-1.6.0.42-1.el6sat.noarch
* foreman-libvirt-1.6.0.42-1.el6sat.noarch
* foreman-ovirt-1.6.0.42-1.el6sat.noarch
* foreman-postgresql-1.6.0.42-1.el6sat.noarch
* foreman-proxy-1.6.0.30-1.el6sat.noarch
* foreman-selinux-1.6.0.14-1.el6sat.noarch
* foreman-vmware-1.6.0.42-1.el6sat.noarch
* katello-1.5.0-30.el6sat.noarch
* katello-ca-1.0-1.noarch
* katello-certs-tools-1.5.6-1.el6sat.noarch
* katello-installer-0.0.62-1.el6sat.noarch
* openldap-2.4.23-34.el6_5.1.x86_64
* openldap-devel-2.4.23-34.el6_5.1.x86_64
* pulp-katello-0.3-4.el6sat.noarch
* pulp-nodes-common-2.4.1-0.5.rc1.el6sat.noarch
* pulp-nodes-parent-2.4.1-0.5.rc1.el6sat.noarch
* pulp-puppet-plugins-2.4.1-0.5.rc1.el6sat.noarch
* pulp-puppet-tools-2.4.1-0.5.rc1.el6sat.noarch
* pulp-rpm-plugins-2.4.1-0.5.rc1.el6sat.noarch
* pulp-selinux-2.4.1-0.5.rc1.el6sat.noarch
* pulp-server-2.4.1-0.5.rc1.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
Comment 8 Bryan Kearney 2014-09-11 12:23:16 UTC 
This was delivered with Satellite 6.0 which was released on 10 September 2014.
Note You need to log in before you can comment on or make changes to this bug.