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 1318026 - auto-attach on a content host throws js error
Summary: auto-attach on a content host throws js error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Roman Plevka
URL: http://projects.theforeman.org/issues...
Whiteboard:
: 1335068 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-15 19:14 UTC by Tom McKay
Modified: 2019-09-26 16:22 UTC (History)
5 users (show)

Fixed In Version: rubygem-katello-3.0.0.53-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:26:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 14217 0 None None None 2016-04-22 16:23:34 UTC

Description Tom McKay 2016-03-15 19:14:47 UTC
<pre>
TypeError: Cannot read property 'host' of undefined
    at Scope.$scope.autoAttachSubscriptions (content-host-base-subscriptions.controller.self.js?body=1:37)
</pre>

Clicking auto-attach on a content host subscriptions UI page is incorrectly referencing host

<pre>

        $scope.autoAttachSubscriptions = function () {
            $scope.subscription.workingMode = true;
            HostSubscription.autoAttach({id: $scope.contentHost.host.id}, success, failure);
        };
</pre>

Comment 1 Tom McKay 2016-03-15 19:14:49 UTC
Created from redmine issue http://projects.theforeman.org/issues/14217

Comment 3 Bryan Kearney 2016-04-18 22:08:13 UTC
Upstream bug assigned to ehelms

Comment 4 Bryan Kearney 2016-05-17 18:23:49 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/14217 has been closed

Comment 5 Walden Raines 2016-06-06 19:38:31 UTC
*** Bug 1335068 has been marked as a duplicate of this bug. ***

Comment 6 Roman Plevka 2016-06-30 13:10:05 UTC
VERIFIED
on sat6.2.0 ga18.1

The error is gone, auto attach works.

Comment 7 Prakash Ghadge 2016-07-14 16:45:35 UTC
One of my customer faced the same issue on latest "Chrome - 51.0.2704.103 m".

Steps to Reproduce:
1. Register the system against satellite in CLI.
2. Login satellite web UI and auto attach the system:
Hosts -> Content Hosts-> Select the system -> Subscriptions -> Subscriptions -> click 'Run Auto-Attach' button.
3. Wait 10 minutes and check the consumed subscriptions: 
1)The status of web UI is not change.
2)no consumed subscriptions are listed in CLI.

Comment 8 Bryan Kearney 2016-07-27 11:26:34 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:1501


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