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 1192500

Summary:	Couldn't enable redhat repos on sat6 after stopping goferd on capsule
Product:	Red Hat Satellite	Reporter:	Sachin Ghai <sghai>
Component:	WebUI	Assignee:	Justin Sherrill <jsherril>
WebUI sub component:	Katello	QA Contact:	Tazim Kolhar <tkolhar>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	bbuckingham, bkearney, cwelton, tkolhar
Version:	6.1.0	Keywords:	Triaged
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/10229
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-12 14:02:17 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:
Bug Blocks:	1176157

Description Sachin Ghai 2015-02-13 14:57:13 UTC

Description of problem:
I stopped goferd on capsule and tried to enable and sync redhat repo, but when I enable the repo from 'Redhat repositories', the spinner keeps on rotating. No error in production.log but firebug raises this error:

--
25
TypeError: data is undefined
	

...a(this,str_data);data.w=w!==undefined?w:elem.width(),data.h=h!==undefined?h:elem...

--

Version-Release number of selected component (if applicable):
sat6 on 6.0.8 errata

How reproducible:
always

Steps to Reproduce:
1.  Install a capsule and associate it with library
2.  Shut down the capsule 
3.  Attempt to enable and sync a repo on sat6

Actual results:
Couldn't enable redhat repo on sat6 after stopping goferd on capsule

Expected results:
repo should be enabled and synced on sat6 successfully when capsule is disconnected.

Additional info:
Please refer https://bugzilla.redhat.com/show_bug.cgi?id=1176157

Comment 2 Justin Sherrill 2015-04-21 18:49:14 UTC

Created redmine issue http://projects.theforeman.org/issues/10229 from this bug

Comment 3 Bryan Kearney 2015-04-29 14:04:57 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/10229 has been closed
-------------
Justin Sherrill
Applied in changeset commit:katello|d0761a9cb05c68ced7da8298924d6d34a529fea1.

Comment 6 Tazim Kolhar 2015-05-12 09:24:47 UTC

VERIFIED:

# rpm -qa | grep foreman
ruby193-rubygem-foreman_docker-1.2.0.11-1.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.11-1.el7sat.noarch
foreman-proxy-1.7.2.4-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch
foreman-1.7.2.19-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.13-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch
foreman-libvirt-1.7.2.19-1.el7sat.noarch
foreman-postgresql-1.7.2.19-1.el7sat.noarch
ibm-hs22-05.rhts.eng.brq.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-debug-1.7.2.19-1.el7sat.noarch
foreman-compute-1.7.2.19-1.el7sat.noarch
foreman-vmware-1.7.2.19-1.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch
foreman-ovirt-1.7.2.19-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.5-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.9-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
ibm-hs22-05.rhts.eng.brq.redhat.com-foreman-client-1.0-1.noarch
ibm-hs22-05.rhts.eng.brq.redhat.com-foreman-proxy-1.0-2.noarch
foreman-gce-1.7.2.19-1.el7sat.noarch


steps:
1.  Install a capsule and associate it with library
2.  Shut down the capsule goferd
# service goferd stop
Stopping goferd[  OK  ]
3.  Attempt to enable and sync a repo on sat6
Repo synced successfully

Comment 7 Bryan Kearney 2015-08-11 13:37:05 UTC

This bug is slated to be released with Satellite 6.1.

Comment 8 Bryan Kearney 2015-08-12 14:02:17 UTC

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