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 968378

Summary: Distributions not synced into Foreman
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: InfrastructureAssignee: Ivan Necas <inecas>
Status: CLOSED CURRENTRELEASE QA Contact: Sachin Ghai <sghai>
Severity: high Docs Contact:
Priority: unspecified    
Version: NightlyCC: bbuckingham, omaciel, sghai
Target Milestone: UnspecifiedKeywords: 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: 2013-07-18 21:19:09 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:
Attachments:
Description Flags
Foreman is showing the promoted repo under foreman->Installation media none

Description Mike McCune 2013-05-29 15:03:17 UTC
If you sync a product and promote a Content View into an environment the distributions and other data are not showing up in Foreman.

This is caused by some missing cherry-picks that we need to get in.

Comment 1 Mike McCune 2013-05-29 15:31:07 UTC
WORKAROUND

# cd /usr/share/katello
# patch -p1 < 2322.patch 
patching file app/models/deletion_changeset.rb
patching file app/models/promotion_changeset.rb
patching file app/models/repository.rb
patching file lib/katello/actions/changeset_promote.rb
patching file lib/katello/actions/repository_destroy.rb

# rpm -Uvh http://fedorapeople.org/groups/katello/releases/yum/nightly/RHEL/6Server/x86_64/ruby193-rubygem-katello-foreman-engine-0.0.2-1.el6.noarch.rpm
Retrieving http://fedorapeople.org/groups/katello/releases/yum/nightly/RHEL/6Server/x86_64/ruby193-rubygem-katello-foreman-engine-0.0.2-1.el6.noarch.rpm
Preparing...                ########################################### [100%]
   1:ruby193-rubygem-katello########################################### [100%]

# katello-service restart

Comment 2 Mike McCune 2013-05-29 15:42:16 UTC
Crud, that workaround was missing a critical step:

WORKAROUND

# cd /usr/share/katello
# wget https://github.com/Katello/katello/pull/2322.patch
# patch -p1 < 2322.patch 
patching file app/models/deletion_changeset.rb
patching file app/models/promotion_changeset.rb
patching file app/models/repository.rb
patching file lib/katello/actions/changeset_promote.rb
patching file lib/katello/actions/repository_destroy.rb

# rpm -Uvh http://fedorapeople.org/groups/katello/releases/yum/nightly/RHEL/6Server/x86_64/ruby193-rubygem-katello-foreman-engine-0.0.2-1.el6.noarch.rpm
Retrieving http://fedorapeople.org/groups/katello/releases/yum/nightly/RHEL/6Server/x86_64/ruby193-rubygem-katello-foreman-engine-0.0.2-1.el6.noarch.rpm
Preparing...                ########################################### [100%]
   1:ruby193-rubygem-katello########################################### [100%]

# katello-service restart

Comment 3 Mike McCune 2013-05-29 16:19:56 UTC
https://github.com/Katello/katello/pull/2322

Comment 5 Sachin Ghai 2013-06-05 11:36:23 UTC
Verified with following Satellite6 MDP1 build:

--
* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.8.9-1.el6_4.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.8.9-1.el6_4.noarch
* candlepin-tomcat6-0.8.9-1.el6_4.noarch
* elasticsearch-0.19.9-8.el6sat.noarch
* foreman-1.1.10002-44.noarch
* foreman-installer-puppet-concat-0-2.d776701.git.0.21ef926.el6sat.noarch
* foreman-installer-puppet-dhcp-0-5.3a4a13c.el6sat.noarch
* foreman-installer-puppet-dns-0-7.fcae203.el6sat.noarch
* foreman-installer-puppet-foreman-0-6.568c5c4.el6sat.noarch
* foreman-installer-puppet-foreman_proxy-0-8.bd1e35d.el6sat.noarch
* foreman-installer-puppet-puppet-0-3.ab46748.el6sat.noarch
* foreman-installer-puppet-tftp-0-5.ea6c5e5.el6sat.noarch
* foreman-installer-puppet-xinetd-0-50a267b8.git.0.44aca6a.el6sat.noarch
* foreman-postgresql-1.1.10002-44.noarch
* foreman-proxy-1.1.10002-1.el6sat.noarch
* foreman-proxy-installer-1.0.1-8.f5ae2cd.el6sat.noarch
* katello-1.4.2-8.el6sat.noarch
* katello-all-1.4.2-8.el6sat.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.4.2-2.el6sat.noarch
* katello-cli-1.4.2-6.el6sat.noarch
* katello-cli-common-1.4.2-6.el6sat.noarch
* katello-common-1.4.2-8.el6sat.noarch
* katello-configure-1.4.3-12.el6sat.noarch
* katello-configure-foreman-1.4.3-12.el6sat.noarch
* katello-foreman-all-1.4.2-8.el6sat.noarch
* katello-glue-candlepin-1.4.2-8.el6sat.noarch
* katello-glue-elasticsearch-1.4.2-8.el6sat.noarch
* katello-glue-pulp-1.4.2-8.el6sat.noarch
* katello-qpid-broker-key-pair-1.0-1.noarch
* katello-qpid-client-key-pair-1.0-1.noarch
* katello-selinux-1.4.3-3.el6sat.noarch
* openldap-2.4.23-31.el6.x86_64
* pulp-rpm-plugins-2.1.1-1.el6sat.noarch
* pulp-selinux-2.1.1-1.el6sat.noarch
* pulp-server-2.1.1-1.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-ldap_fluff-0.1.7-3.el6sat.noarch
* ruby193-rubygem-net-ldap-0.2.2-7.el6_4.noarch
* signo-0.0.15-1.el6sat.noarch
* signo-katello-0.0.15-1.el6sat.noarch
--

I synced a repo and promoted the CV to an env. And now I can see the distribution in Foreman.

Please note the while creating repo we need to check 'publish via http' too, Thanks to inecas for pointing this.

Comment 6 Sachin Ghai 2013-06-05 11:37:54 UTC
Created attachment 757139 [details]
Foreman is showing the promoted repo under foreman->Installation media

Comment 7 Mike McCune 2013-07-18 21:19:09 UTC
mass move to CLOSED:CURRENTRELEASE since MDP1 has been released.