[Katello 2.2] - how to setup a client for content

JC1 · April 1, 2015, 10:04am

Hi.

I've just completed a new install of Katello
(katello-2.3.0-1.201503310129git07a6e29.el6.noarch) on a CentOS6.6 minimal
install. What's the right* way to setup CentOS 5 and CentOS 6 clients (*I
fudged this with an earlier 2.1 install)? The documentation
<http://www.katello.org/docs/2.2/user_guide/content/content.html> says:

Subscribing a System to a Product for yum content
To read about registering systems and subscribing them to the Product click
TODO.

# yum install katello-agent

Loaded plugins: fastestmirror

Setting up Install Process

Loading mirror speeds from cached hostfile

Resolving Dependencies

–> Running transaction check

—> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed

–> Processing Dependency: python-pulp-agent-lib >= 2.6 for package:
katello-agent-2.3.0-1.el6.noarch

–> Processing Dependency: python-gofer-proton >= 2.5 for package:
katello-agent-2.3.0-1.el6.noarch

–> Processing Dependency: pulp-rpm-handlers >= 2.6 for package:
katello-agent-2.3.0-1.el6.noarch

–> Processing Dependency: gofer >= 2.5 for package:
katello-agent-2.3.0-1.el6.noarch

–> Processing Dependency: subscription-manager for package:
katello-agent-2.3.0-1.el6.noarch

–> Running transaction check

—> Package gofer.noarch 0:2.5.3-1.el6 will be installed

—> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed

–> Processing Dependency: subscription-manager for package:
katello-agent-2.3.0-1.el6.noarch

—> Package pulp-rpm-handlers.noarch 0:2.6.0-1.el6 will be installed

—> Package python-gofer-proton.noarch 0:2.5.3-1.el6 will be installed

–> Processing Dependency: python-qpid-proton >= 0.9-1.20150219 for
package: python-gofer-proton-2.5.3-1.el6.noarch

—> Package python-pulp-agent-lib.noarch 0:2.6.0-1.el6 will be installed

–> Running transaction check

—> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed

–> Processing Dependency: subscription-manager for package:
katello-agent-2.3.0-1.el6.noarch

—> Package python-qpid-proton.x86_64 0:0.9-1.20150219.el6 will be
installed

–> Finished Dependency Resolution

Error: Package: katello-agent-2.3.0-1.el6.noarch (katello)

Requires: subscription-manager*

# rpm -qa | grep "katello|pulp|candle|foreman"

foreman-proxy-1.9.0-0.develop.201503311321git95cd9c8.el6.noarch

foreman-debug-1.9.0-0.develop.201503261813git331ff16.el6.noarch

python-pulp-bindings-2.6.0-1.el6.noarch

katello-debug-2.3.0-1.201503310129git07a6e29.el6.noarch

python-pulp-docker-common-0.2.2-1.el6.noarch

foreman-1.9.0-0.develop.201503261813git331ff16.el6.noarch

foreman-vmware-1.9.0-0.develop.201503261813git331ff16.el6.noarch

rubygem-hammer_cli_foreman_tasks-0.0.5-1.el6.noarch

ruby193-rubygem-foreman_bootdisk-5.0.0-1.el6.noarch

rubygem-hammer_cli_katello-0.0.11-1.201503271931git8799b04.git.0.db4e3db.el6.noarch

candlepin-tomcat6-0.9.47-1.el6.noarch

katello-selinux-2.2.1-1.el6.noarch

pulp-nodes-common-2.6.0-1.el6.noarch

pulp-katello-0.3-4.el6.noarch

katello-2.3.0-1.201503310129git07a6e29.el6.noarch

pulp-puppet-tools-2.6.0-1.el6.noarch

katello-certs-tools-2.0.1-1.el6.noarch

katello-default-ca-1.0-1.noarch

katello-repos-2.3.0-2.el6.noarch

kmaster.lan-foreman-proxy-client-1.0-1.noarch

python-pulp-rpm-common-2.6.0-1.el6.noarch

foreman-libvirt-1.9.0-0.develop.201503261813git331ff16.el6.noarch

ruby193-rubygem-foreman_hooks-0.3.7-3.el6.noarch

candlepin-common-1.0.22-1.el6.noarch

candlepin-selinux-0.9.47-1.el6.noarch

rubygem-hammer_cli_foreman_docker-0.0.3-2.el6.noarch

pulp-selinux-2.6.0-1.el6.noarch

pulp-puppet-plugins-2.6.0-1.el6.noarch

pulp-docker-plugins-0.2.2-1.el6.noarch

katello-common-2.3.0-1.201503310129git07a6e29.el6.noarch

rubygem-smart_proxy_pulp-1.0.1-2.el6.noarch

kmaster.lan-foreman-proxy-1.0-1.noarch

m2crypto-0.21.1.pulp-8.el6.x86_64

python-isodate-0.5.0-4.pulp.el6.noarch

python-rhsm-1.8.0-2.pulp.el6.x86_64

foreman-gce-1.9.0-0.develop.201503261813git331ff16.el6.noarch

foreman-ovirt-1.9.0-0.develop.201503261813git331ff16.el6.noarch

mod_wsgi-3.4-2.pulp.el6.x86_64

candlepin-0.9.47-1.el6.noarch

pulp-server-2.6.0-1.el6.noarch

pulp-rpm-plugins-2.6.0-1.el6.noarch

ruby193-rubygem-foreman_gutterball-0.0.1-1.201503061946gite954cd1.git.0.6e21da0.el6.noarch

katello-installer-base-2.3.0-1.201503232042git7769450.el6.noarch

kmaster.lan-foreman-client-1.0-1.noarch

python-pulp-common-2.6.0-1.el6.noarch

python-pulp-puppet-common-2.6.0-1.el6.noarch

foreman-compute-1.9.0-0.develop.201503261813git331ff16.el6.noarch

ruby193-rubygem-foreman_docker-1.2.4-1.fm1_9.el6.noarch

ruby193-rubygem-foreman-tasks-0.6.13-2.el6.noarch

python-kombu-3.0.24-5.pulp.el6.noarch

rubygem-hammer_cli_foreman-0.1.4-1.201503240905git7377f48.el6.noarch

rubygem-hammer_cli_foreman_bootdisk-0.1.2-1.el6.noarch

foreman-selinux-1.9.0-0.develop.201503091423git639a8ed.el6.noarch

pulp-nodes-parent-2.6.0-1.el6.noarch

ruby193-rubygem-katello-2.3.0-1.201503310036git07a6e29.el6.noarch

katello-installer-2.3.0-1.201503232042git7769450.el6.noarch

katello-server-ca-1.0-1.noarch

foreman-release-1.9.0-0.develop.201503261813git331ff16.el6.noarch

foreman-postgresql-1.9.0-0.develop.201503261813git331ff16.el6.noarch

Repos provided by the CentOS and Katello installs:

# yum repolist

Loaded plugins: fastestmirror

Loading mirror speeds from cached hostfile

repo id repo name

status

SCL CentOS-6 - SCL

base CentOS-6 - Base

 6,518

epel Extra Packages for Enterprise Linux 6 - x86_64

11,362

extras CentOS-6 - Extras

foreman Foreman nightly

foreman-plugins Foreman plugins nightly

katello Katello Nightly

katello-candlepin Candlepin: an open source entitlement management
system.
6

katello-client Katello Client Nightly

katello-pulp Pulp Community Releases

puppetlabs-deps Puppet Labs Dependencies El 6 - x86_64

puppetlabs-products Puppet Labs Products El 6 - x86_64

updates CentOS-6 - Updates

Jorick_Astrego · April 1, 2015, 10:10am

I have enabled and use the subscription-manager repo @
"https://repos.fedorapeople.org/repos/candlepin/subscription-manager/epel-subscription-manager.repo"

Hope this helps.

Met vriendelijke groet, With kind regards,

Jorick Astrego

Netbulae Virtualization Experts

···

On 04/01/2015 12:04 PM, JC wrote: > Hi. > > I've just completed a new install of Katello > (katello-2.3.0-1.201503310129git07a6e29.el6.noarch) on a CentOS6.6 > minimal install. What's the right* way to setup CentOS 5 and CentOS 6 > clients (*I fudged this with an earlier 2.1 install)? The > documentation > says: > > *Subscribing a System to a Product for yum content* > To read about registering systems and subscribing them to the Product > click TODO. > > *# yum install katello-agent* > > Loaded plugins: fastestmirror > > Setting up Install Process > > Loading mirror speeds from cached hostfile > > * base: anorien.csc.warwick.ac.uk > > * epel: anorien.csc.warwick.ac.uk > > * extras: anorien.csc.warwick.ac.uk > > * updates: repo.bigstepcloud.com > > Resolving Dependencies > > --> Running transaction check > > ---> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed > > --> Processing Dependency: python-pulp-agent-lib >= 2.6 for package: > katello-agent-2.3.0-1.el6.noarch > > --> Processing Dependency: python-gofer-proton >= 2.5 for package: > katello-agent-2.3.0-1.el6.noarch > > --> Processing Dependency: pulp-rpm-handlers >= 2.6 for package: > katello-agent-2.3.0-1.el6.noarch > > --> Processing Dependency: gofer >= 2.5 for package: > katello-agent-2.3.0-1.el6.noarch > > --> Processing Dependency: subscription-manager for package: > katello-agent-2.3.0-1.el6.noarch > > --> Running transaction check > > ---> Package gofer.noarch 0:2.5.3-1.el6 will be installed > > ---> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed > > --> Processing Dependency: subscription-manager for package: > katello-agent-2.3.0-1.el6.noarch > > ---> Package pulp-rpm-handlers.noarch 0:2.6.0-1.el6 will be installed > > ---> Package python-gofer-proton.noarch 0:2.5.3-1.el6 will be installed > > --> Processing Dependency: python-qpid-proton >= 0.9-1.20150219 for > package: python-gofer-proton-2.5.3-1.el6.noarch > > ---> Package python-pulp-agent-lib.noarch 0:2.6.0-1.el6 will be installed > > --> Running transaction check > > ---> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed > > --> Processing Dependency: subscription-manager for package: > katello-agent-2.3.0-1.el6.noarch > > ---> Package python-qpid-proton.x86_64 0:0.9-1.20150219.el6 will be > installed > > --> Finished Dependency Resolution > > Error: Package: katello-agent-2.3.0-1.el6.noarch (katello) > > *Requires: subscription-manager* > >

Tel: 053 20 30 270 	info@netbulae.eu 	Staalsteden 4-3A 	KvK 08198180
Fax: 053 20 30 271 	www.netbulae.eu 	7547 TA Enschede 	BTW NL821234584B01

Mark_White · April 8, 2015, 5:43pm

Hi

I am still testing with Katello 2.1, and trying to get it to work with OEL
and having problems with subscription. Could you explain what the fudge was
you did for 2.1 and have you found 2.2 better ?

Also, in case I cannot get subscription to work so just using the repo with
yum, am I right thinking you just need a standard content view for each
repo, as a composite view fails as you still need the full path to each of
the repodata dirs in the compolsite i.e. composite is only useful if
subscription works ?

···

On Wednesday, April 1, 2015 at 11:04:17 AM UTC+1, JC wrote: > > Hi. > > I've just completed a new install of Katello > (katello-2.3.0-1.201503310129git07a6e29.el6.noarch) on a CentOS6.6 minimal > install. What's the right* way to setup CentOS 5 and CentOS 6 clients (*I > fudged this with an earlier 2.1 install)? The documentation > says: > > *Subscribing a System to a Product for yum content* > To read about registering systems and subscribing them to the Product > click TODO. > > *# yum install katello-agent* > > Loaded plugins: fastestmirror > > Setting up Install Process > > Loading mirror speeds from cached hostfile > > * base: anorien.csc.warwick.ac.uk > > * epel: anorien.csc.warwick.ac.uk > > * extras: anorien.csc.warwick.ac.uk > > * updates: repo.bigstepcloud.com > > Resolving Dependencies > > --> Running transaction check > > ---> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed > > --> Processing Dependency: python-pulp-agent-lib >= 2.6 for package: > katello-agent-2.3.0-1.el6.noarch > > --> Processing Dependency: python-gofer-proton >= 2.5 for package: > katello-agent-2.3.0-1.el6.noarch > > --> Processing Dependency: pulp-rpm-handlers >= 2.6 for package: > katello-agent-2.3.0-1.el6.noarch > > --> Processing Dependency: gofer >= 2.5 for package: > katello-agent-2.3.0-1.el6.noarch > > --> Processing Dependency: subscription-manager for package: > katello-agent-2.3.0-1.el6.noarch > > --> Running transaction check > > ---> Package gofer.noarch 0:2.5.3-1.el6 will be installed > > ---> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed > > --> Processing Dependency: subscription-manager for package: > katello-agent-2.3.0-1.el6.noarch > > ---> Package pulp-rpm-handlers.noarch 0:2.6.0-1.el6 will be installed > > ---> Package python-gofer-proton.noarch 0:2.5.3-1.el6 will be installed > > --> Processing Dependency: python-qpid-proton >= 0.9-1.20150219 for > package: python-gofer-proton-2.5.3-1.el6.noarch > > ---> Package python-pulp-agent-lib.noarch 0:2.6.0-1.el6 will be installed > > --> Running transaction check > > ---> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed > > --> Processing Dependency: subscription-manager for package: > katello-agent-2.3.0-1.el6.noarch > > ---> Package python-qpid-proton.x86_64 0:0.9-1.20150219.el6 will be > installed > > --> Finished Dependency Resolution > > Error: Package: katello-agent-2.3.0-1.el6.noarch (katello) > > * Requires: subscription-manager* > > > > *# rpm -qa | grep "katello\|pulp\|candle\|foreman"* > > foreman-proxy-1.9.0-0.develop.201503311321git95cd9c8.el6.noarch > > foreman-debug-1.9.0-0.develop.201503261813git331ff16.el6.noarch > > python-pulp-bindings-2.6.0-1.el6.noarch > > katello-debug-2.3.0-1.201503310129git07a6e29.el6.noarch > > python-pulp-docker-common-0.2.2-1.el6.noarch > > foreman-1.9.0-0.develop.201503261813git331ff16.el6.noarch > > foreman-vmware-1.9.0-0.develop.201503261813git331ff16.el6.noarch > > rubygem-hammer_cli_foreman_tasks-0.0.5-1.el6.noarch > > ruby193-rubygem-foreman_bootdisk-5.0.0-1.el6.noarch > > > rubygem-hammer_cli_katello-0.0.11-1.201503271931git8799b04.git.0.db4e3db.el6.noarch > > candlepin-tomcat6-0.9.47-1.el6.noarch > > katello-selinux-2.2.1-1.el6.noarch > > pulp-nodes-common-2.6.0-1.el6.noarch > > pulp-katello-0.3-4.el6.noarch > > katello-2.3.0-1.201503310129git07a6e29.el6.noarch > > pulp-puppet-tools-2.6.0-1.el6.noarch > > katello-certs-tools-2.0.1-1.el6.noarch > > katello-default-ca-1.0-1.noarch > > katello-repos-2.3.0-2.el6.noarch > > kmaster.lan-foreman-proxy-client-1.0-1.noarch > > python-pulp-rpm-common-2.6.0-1.el6.noarch > > foreman-libvirt-1.9.0-0.develop.201503261813git331ff16.el6.noarch > > ruby193-rubygem-foreman_hooks-0.3.7-3.el6.noarch > > candlepin-common-1.0.22-1.el6.noarch > > candlepin-selinux-0.9.47-1.el6.noarch > > rubygem-hammer_cli_foreman_docker-0.0.3-2.el6.noarch > > pulp-selinux-2.6.0-1.el6.noarch > > pulp-puppet-plugins-2.6.0-1.el6.noarch > > pulp-docker-plugins-0.2.2-1.el6.noarch > > katello-common-2.3.0-1.201503310129git07a6e29.el6.noarch > > rubygem-smart_proxy_pulp-1.0.1-2.el6.noarch > > kmaster.lan-foreman-proxy-1.0-1.noarch > > m2crypto-0.21.1.pulp-8.el6.x86_64 > > python-isodate-0.5.0-4.pulp.el6.noarch > > python-rhsm-1.8.0-2.pulp.el6.x86_64 > > foreman-gce-1.9.0-0.develop.201503261813git331ff16.el6.noarch > > foreman-ovirt-1.9.0-0.develop.201503261813git331ff16.el6.noarch > > mod_wsgi-3.4-2.pulp.el6.x86_64 > > candlepin-0.9.47-1.el6.noarch > > pulp-server-2.6.0-1.el6.noarch > > pulp-rpm-plugins-2.6.0-1.el6.noarch > > > ruby193-rubygem-foreman_gutterball-0.0.1-1.201503061946gite954cd1.git.0.6e21da0.el6.noarch > > katello-installer-base-2.3.0-1.201503232042git7769450.el6.noarch > > kmaster.lan-foreman-client-1.0-1.noarch > > python-pulp-common-2.6.0-1.el6.noarch > > python-pulp-puppet-common-2.6.0-1.el6.noarch > > foreman-compute-1.9.0-0.develop.201503261813git331ff16.el6.noarch > > ruby193-rubygem-foreman_docker-1.2.4-1.fm1_9.el6.noarch > > ruby193-rubygem-foreman-tasks-0.6.13-2.el6.noarch > > python-kombu-3.0.24-5.pulp.el6.noarch > > rubygem-hammer_cli_foreman-0.1.4-1.201503240905git7377f48.el6.noarch > > rubygem-hammer_cli_foreman_bootdisk-0.1.2-1.el6.noarch > > foreman-selinux-1.9.0-0.develop.201503091423git639a8ed.el6.noarch > > pulp-nodes-parent-2.6.0-1.el6.noarch > > ruby193-rubygem-katello-2.3.0-1.201503310036git07a6e29.el6.noarch > > katello-installer-2.3.0-1.201503232042git7769450.el6.noarch > > katello-server-ca-1.0-1.noarch > > foreman-release-1.9.0-0.develop.201503261813git331ff16.el6.noarch > > foreman-postgresql-1.9.0-0.develop.201503261813git331ff16.el6.noarch > > Repos provided by the CentOS and Katello installs: > > *# yum repolist* > > Loaded plugins: fastestmirror > > Loading mirror speeds from cached hostfile > > * base: anorien.csc.warwick.ac.uk > > * epel: anorien.csc.warwick.ac.uk > > * extras: anorien.csc.warwick.ac.uk > > * updates: repo.bigstepcloud.com > > repo id repo name > > status > > SCL CentOS-6 - SCL > > 504 > > base CentOS-6 - Base > > 6,518 > > epel Extra Packages for Enterprise Linux 6 - x86_64 > > 11,362 > > extras CentOS-6 - Extras > > 37 > > foreman Foreman nightly > > 243 > > foreman-plugins Foreman plugins nightly > > 559 > > katello Katello Nightly > > 142 > > katello-candlepin Candlepin: an open source entitlement management > system. > 6 > > katello-client Katello Client Nightly > > 16 > > katello-pulp Pulp Community Releases > > 67 > > puppetlabs-deps Puppet Labs Dependencies El 6 - x86_64 > > 77 > > puppetlabs-products Puppet Labs Products El 6 - x86_64 > > 494 > > updates CentOS-6 - Updates > > 926 >

JC1 · April 1, 2015, 10:48am

Jorick - thank you. It did.

# yum install katello-agent
Loaded plugins: fastestmirror
Setting up Install Process
Loading mirror speeds from cached hostfile

epel-subscription-manager
> 2.9 kB
00:00
epel-subscription-manager/primary_db
> 14 kB
00:00
Resolving Dependencies
–> Running transaction check
—> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed
–> Processing Dependency: python-pulp-agent-lib >= 2.6 for package:
katello-agent-2.3.0-1.el6.noarch
–> Processing Dependency: python-gofer-proton >= 2.5 for package:
katello-agent-2.3.0-1.el6.noarch
–> Processing Dependency: pulp-rpm-handlers >= 2.6 for package:
katello-agent-2.3.0-1.el6.noarch
–> Processing Dependency: gofer >= 2.5 for package:
katello-agent-2.3.0-1.el6.noarch
–> Processing Dependency: subscription-manager for package:
katello-agent-2.3.0-1.el6.noarch
–> Running transaction check
—> Package gofer.noarch 0:2.5.3-1.el6 will be installed
—> Package pulp-rpm-handlers.noarch 0:2.6.0-1.el6 will be installed
—> Package python-gofer-proton.noarch 0:2.5.3-1.el6 will be installed
–> Processing Dependency: python-qpid-proton >= 0.9-1.20150219 for
package: python-gofer-proton-2.5.3-1.el6.noarch
—> Package python-pulp-agent-lib.noarch 0:2.6.0-1.el6 will be installed
—> Package subscription-manager.x86_64 0:1.13.12-1.el6 will be installed
–> Processing Dependency: python-rhsm >= 1.13.5 for package:
subscription-manager-1.13.12-1.el6.x86_64
–> Processing Dependency: usermode for package:
subscription-manager-1.13.12-1.el6.x86_64
–> Processing Dependency: python-ethtool for package:
subscription-manager-1.13.12-1.el6.x86_64
–> Processing Dependency: python-dmidecode for package:
subscription-manager-1.13.12-1.el6.x86_64
–> Processing Dependency: pygobject2 for package:
subscription-manager-1.13.12-1.el6.x86_64
–> Processing Dependency: dbus-python for package:
subscription-manager-1.13.12-1.el6.x86_64
–> Running transaction check
—> Package dbus-python.x86_64 0:0.83.0-6.1.el6 will be installed
—> Package pygobject2.x86_64 0:2.20.0-5.el6 will be installed
—> Package python-dmidecode.x86_64 0:3.10.13-3.el6_4 will be installed
—> Package python-ethtool.x86_64 0:0.6-5.el6 will be installed
—> Package python-qpid-proton.x86_64 0:0.9-1.20150219.el6 will be
installed
—> Package python-rhsm.x86_64 0:1.8.0-2.pulp.el6 will be updated
—> Package python-rhsm.x86_64 0:1.13.8-1.el6 will be an update
—> Package usermode.x86_64 0:1.102-3.el6 will be installed
–> Finished Dependency Resolution

Dependencies Resolved

···

=============================================================================================================================================================== Package Arch Version Repository Size =============================================================================================================================================================== Installing: katello-agent noarch 2.3.0-1.el6 katello 23 k Installing for dependencies: dbus-python x86_64 0.83.0-6.1.el6 base 204 k gofer noarch 2.5.3-1.el6 katello-client 74 k pulp-rpm-handlers noarch 2.6.0-1.el6 katello-client 69 k pygobject2 x86_64 2.20.0-5.el6 base 172 k python-dmidecode x86_64 3.10.13-3.el6_4 base 80 k python-ethtool x86_64 0.6-5.el6 base 31 k python-gofer-proton noarch 2.5.3-1.el6 katello-client 51 k python-pulp-agent-lib noarch 2.6.0-1.el6 katello-client 89 k python-qpid-proton x86_64 0.9-1.20150219.el6 katello-client 188 k subscription-manager x86_64 1.13.12-1.el6 epel-subscription-manager 798 k usermode x86_64 1.102-3.el6 base 187 k Updating for dependencies: python-rhsm x86_64 1.13.8-1.el6 epel-subscription-manager 112 k

Transaction Summary

Install 12 Package(s)
Upgrade 1 Package(s)

Total download size: 2.0 M
Is this ok [y/N]: y
Downloading Packages:
(1/13): dbus-python-0.83.0-6.1.el6.x86_64.rpm
> 204 kB
00:00
(2/13): gofer-2.5.3-1.el6.noarch.rpm
> 74 kB
00:00
(3/13): katello-agent-2.3.0-1.el6.noarch.rpm
> 23 kB
00:00
(4/13): pulp-rpm-handlers-2.6.0-1.el6.noarch.rpm
> 69 kB
00:00
(5/13): pygobject2-2.20.0-5.el6.x86_64.rpm
> 172 kB
00:00
(6/13): python-dmidecode-3.10.13-3.el6_4.x86_64.rpm
> 80 kB
00:00
(7/13): python-ethtool-0.6-5.el6.x86_64.rpm
> 31 kB
00:00
(8/13): python-gofer-proton-2.5.3-1.el6.noarch.rpm
> 51 kB
00:00
(9/13): python-pulp-agent-lib-2.6.0-1.el6.noarch.rpm
> 89 kB
00:00
(10/13): python-qpid-proton-0.9-1.20150219.el6.x86_64.rpm
> 188 kB
00:01
(11/13): python-rhsm-1.13.8-1.el6.x86_64.rpm
> 112 kB
00:00
(12/13): subscription-manager-1.13.12-1.el6.x86_64.rpm
> 798 kB
00:01
(13/13): usermode-1.102-3.el6.x86_64.rpm
> 187 kB
00:00

Total
130 kB/s | 2.0 MB
00:15
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Updating : python-rhsm-1.13.8-1.el6.x86_64

1/14
Installing : python-pulp-agent-lib-2.6.0-1.el6.noarch

2/14
Installing : pulp-rpm-handlers-2.6.0-1.el6.noarch

3/14
Installing : usermode-1.102-3.el6.x86_64

4/14
Installing : python-dmidecode-3.10.13-3.el6_4.x86_64

5/14
Installing : python-ethtool-0.6-5.el6.x86_64

6/14
Installing : gofer-2.5.3-1.el6.noarch

7/14
Installing : dbus-python-0.83.0-6.1.el6.x86_64

8/14
Installing : pygobject2-2.20.0-5.el6.x86_64

9/14
Installing : subscription-manager-1.13.12-1.el6.x86_64

10/14
Installing : python-qpid-proton-0.9-1.20150219.el6.x86_64

11/14
Installing : python-gofer-proton-2.5.3-1.el6.noarch

12/14
Installing : katello-agent-2.3.0-1.el6.noarch

13/14
Stopping goferd[FAILED]

Starting goferd[ OK ]

Cleanup : python-rhsm-1.8.0-2.pulp.el6.x86_64

14/14
Verifying : katello-agent-2.3.0-1.el6.noarch

1/14
Verifying : python-qpid-proton-0.9-1.20150219.el6.x86_64

2/14
Verifying : pulp-rpm-handlers-2.6.0-1.el6.noarch

3/14
Verifying : python-gofer-proton-2.5.3-1.el6.noarch

4/14
Verifying : pygobject2-2.20.0-5.el6.x86_64

5/14
Verifying : dbus-python-0.83.0-6.1.el6.x86_64

6/14
Verifying : gofer-2.5.3-1.el6.noarch

7/14
Verifying : python-pulp-agent-lib-2.6.0-1.el6.noarch

8/14
Verifying : python-rhsm-1.13.8-1.el6.x86_64

9/14
Verifying : subscription-manager-1.13.12-1.el6.x86_64

10/14
Verifying : python-ethtool-0.6-5.el6.x86_64

11/14
Verifying : python-dmidecode-3.10.13-3.el6_4.x86_64

12/14
Verifying : usermode-1.102-3.el6.x86_64

13/14
Verifying : python-rhsm-1.8.0-2.pulp.el6.x86_64

14/14

Installed:
katello-agent.noarch 0:2.3.0-1.el6

Dependency Installed:
dbus-python.x86_64 0:0.83.0-6.1.el6 gofer.noarch
0:2.5.3-1.el6 pulp-rpm-handlers.noarch
0:2.6.0-1.el6
pygobject2.x86_64 0:2.20.0-5.el6
python-dmidecode.x86_64 0:3.10.13-3.el6_4 python-ethtool.x86_64
0:0.6-5.el6
python-gofer-proton.noarch 0:2.5.3-1.el6
python-pulp-agent-lib.noarch 0:2.6.0-1.el6
python-qpid-proton.x86_64 0:0.9-1.20150219.el6
subscription-manager.x86_64 0:1.13.12-1.el6 usermode.x86_64
0:1.102-3.el6

Dependency Updated:
python-rhsm.x86_64 0:1.13.8-1.el6

Complete!

On Wednesday, 1 April 2015 11:11:04 UTC+1, Jorick Astrego wrote:

On 04/01/2015 12:04 PM, JC wrote:

Hi.

I’ve just completed a new install of Katello
(katello-2.3.0-1.201503310129git07a6e29.el6.noarch) on a CentOS6.6 minimal
install. What’s the right* way to setup CentOS 5 and CentOS 6 clients (*I
fudged this with an earlier 2.1 install)? The documentation
http://www.katello.org/docs/2.2/user_guide/content/content.html says:

Subscribing a System to a Product for yum content
To read about registering systems and subscribing them to the Product
click TODO.

# yum install katello-agent

Loaded plugins: fastestmirror

Setting up Install Process

Loading mirror speeds from cached hostfile

base: anorien.csc.warwick.ac.uk

epel: anorien.csc.warwick.ac.uk

extras: anorien.csc.warwick.ac.uk

updates: repo.bigstepcloud.com

Resolving Dependencies

–> Running transaction check

—> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed

–> Processing Dependency: python-pulp-agent-lib >= 2.6 for package:
katello-agent-2.3.0-1.el6.noarch

–> Processing Dependency: python-gofer-proton >= 2.5 for package:
katello-agent-2.3.0-1.el6.noarch

–> Processing Dependency: pulp-rpm-handlers >= 2.6 for package:
katello-agent-2.3.0-1.el6.noarch

–> Processing Dependency: gofer >= 2.5 for package:
katello-agent-2.3.0-1.el6.noarch

–> Processing Dependency: subscription-manager for package:
katello-agent-2.3.0-1.el6.noarch

–> Running transaction check

—> Package gofer.noarch 0:2.5.3-1.el6 will be installed

—> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed

–> Processing Dependency: subscription-manager for package:
katello-agent-2.3.0-1.el6.noarch

—> Package pulp-rpm-handlers.noarch 0:2.6.0-1.el6 will be installed

—> Package python-gofer-proton.noarch 0:2.5.3-1.el6 will be installed

–> Processing Dependency: python-qpid-proton >= 0.9-1.20150219 for
package: python-gofer-proton-2.5.3-1.el6.noarch

—> Package python-pulp-agent-lib.noarch 0:2.6.0-1.el6 will be installed

–> Running transaction check

—> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed

–> Processing Dependency: subscription-manager for package:
katello-agent-2.3.0-1.el6.noarch

—> Package python-qpid-proton.x86_64 0:0.9-1.20150219.el6 will be
installed

–> Finished Dependency Resolution

Error: Package: katello-agent-2.3.0-1.el6.noarch (katello)

Requires: subscription-manager*

I have enabled and use the subscription-manager repo @
"https://repos.fedorapeople.org/repos/candlepin/subscription-manager/epel-subscription-manager.repo"
https://repos.fedorapeople.org/repos/candlepin/subscription-manager/epel-subscription-manager.repo

Hope this helps.

Met vriendelijke groet, With kind regards,

Jorick Astrego

*Netbulae Virtualization Experts *

Tel: 053 20 30 270 in...@netbulae.eu <javascript:> Staalsteden 4-3A KvK
08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW
NL821234584B01

JC1 · April 1, 2015, 11:07am

Just to add, there are details (which I must have seen the first time
around, but not today) in the 'Content Host
<http://www.katello.org/docs/2.2/user_guide/content_hosts/index.html#How is
a Content Host registered?>' section of the docs, which point you (for
subscription-manager on CentOS5/6) to:

https://copr-be.cloud.fedoraproject.org/results/dgoodwin/subscription-manager/

But certainly for CentOS6, I'm not sure the content is preferable (to
https://repos.fedorapeople.org/repos/candlepin/subscription-manager/epel-6/x86_64/):

···

On Wednesday, 1 April 2015 11:48:10 UTC+1, JC wrote: > > Jorick - thank you. It did. > > *# yum install katello-agent* > Loaded plugins: fastestmirror > Setting up Install Process > Loading mirror speeds from cached hostfile > * base: anorien.csc.warwick.ac.uk > * epel: ftp.nluug.nl > > > * extras: anorien.csc.warwick.ac.uk > > > * updates: repo.bigstepcloud.com > > epel-subscription-manager > > 2.9 kB > 00:00 > epel-subscription-manager/primary_db > > 14 kB > 00:00 > Resolving Dependencies > --> Running transaction check > ---> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed > --> Processing Dependency: python-pulp-agent-lib >= 2.6 for package: > katello-agent-2.3.0-1.el6.noarch > --> Processing Dependency: python-gofer-proton >= 2.5 for package: > katello-agent-2.3.0-1.el6.noarch > --> Processing Dependency: pulp-rpm-handlers >= 2.6 for package: > katello-agent-2.3.0-1.el6.noarch > --> Processing Dependency: gofer >= 2.5 for package: > katello-agent-2.3.0-1.el6.noarch > --> Processing Dependency: subscription-manager for package: > katello-agent-2.3.0-1.el6.noarch > --> Running transaction check > ---> Package gofer.noarch 0:2.5.3-1.el6 will be installed > ---> Package pulp-rpm-handlers.noarch 0:2.6.0-1.el6 will be installed > ---> Package python-gofer-proton.noarch 0:2.5.3-1.el6 will be installed > --> Processing Dependency: python-qpid-proton >= 0.9-1.20150219 for > package: python-gofer-proton-2.5.3-1.el6.noarch > ---> Package python-pulp-agent-lib.noarch 0:2.6.0-1.el6 will be installed > ---> Package subscription-manager.x86_64 0:1.13.12-1.el6 will be installed > --> Processing Dependency: python-rhsm >= 1.13.5 for package: > subscription-manager-1.13.12-1.el6.x86_64 > --> Processing Dependency: usermode for package: > subscription-manager-1.13.12-1.el6.x86_64 > --> Processing Dependency: python-ethtool for package: > subscription-manager-1.13.12-1.el6.x86_64 > --> Processing Dependency: python-dmidecode for package: > subscription-manager-1.13.12-1.el6.x86_64 > --> Processing Dependency: pygobject2 for package: > subscription-manager-1.13.12-1.el6.x86_64 > --> Processing Dependency: dbus-python for package: > subscription-manager-1.13.12-1.el6.x86_64 > --> Running transaction check > ---> Package dbus-python.x86_64 0:0.83.0-6.1.el6 will be installed > ---> Package pygobject2.x86_64 0:2.20.0-5.el6 will be installed > ---> Package python-dmidecode.x86_64 0:3.10.13-3.el6_4 will be installed > ---> Package python-ethtool.x86_64 0:0.6-5.el6 will be installed > ---> Package python-qpid-proton.x86_64 0:0.9-1.20150219.el6 will be > installed > ---> Package python-rhsm.x86_64 0:1.8.0-2.pulp.el6 will be updated > ---> Package python-rhsm.x86_64 0:1.13.8-1.el6 will be an update > ---> Package usermode.x86_64 0:1.102-3.el6 will be installed > --> Finished Dependency Resolution > > Dependencies Resolved > > > =============================================================================================================================================================== > Package Arch > Version Repository > Size > > =============================================================================================================================================================== > Installing: > katello-agent noarch > 2.3.0-1.el6 katello > 23 k > Installing for dependencies: > dbus-python x86_64 > 0.83.0-6.1.el6 base > 204 k > gofer noarch > 2.5.3-1.el6 katello-client > 74 k > pulp-rpm-handlers noarch > 2.6.0-1.el6 katello-client > 69 k > pygobject2 x86_64 > 2.20.0-5.el6 base > 172 k > python-dmidecode x86_64 > 3.10.13-3.el6_4 base > 80 k > python-ethtool x86_64 > 0.6-5.el6 base > 31 k > python-gofer-proton noarch > 2.5.3-1.el6 katello-client > 51 k > python-pulp-agent-lib noarch > 2.6.0-1.el6 katello-client > 89 k > python-qpid-proton x86_64 > 0.9-1.20150219.el6 katello-client > 188 k > subscription-manager x86_64 > 1.13.12-1.el6 epel-subscription-manager > 798 k > usermode x86_64 > 1.102-3.el6 base > 187 k > Updating for dependencies: > python-rhsm x86_64 > 1.13.8-1.el6 epel-subscription-manager > 112 k > > Transaction Summary > > =============================================================================================================================================================== > Install 12 Package(s) > Upgrade 1 Package(s) > > Total download size: 2.0 M > Is this ok [y/N]: y > Downloading Packages: > (1/13): dbus-python-0.83.0-6.1.el6.x86_64.rpm > > 204 kB > 00:00 > (2/13): gofer-2.5.3-1.el6.noarch.rpm > > 74 kB > 00:00 > (3/13): katello-agent-2.3.0-1.el6.noarch.rpm > > 23 kB > 00:00 > (4/13): pulp-rpm-handlers-2.6.0-1.el6.noarch.rpm > > 69 kB > 00:00 > (5/13): pygobject2-2.20.0-5.el6.x86_64.rpm > > 172 kB > 00:00 > (6/13): python-dmidecode-3.10.13-3.el6_4.x86_64.rpm > > 80 kB > 00:00 > (7/13): python-ethtool-0.6-5.el6.x86_64.rpm > > 31 kB > 00:00 > (8/13): python-gofer-proton-2.5.3-1.el6.noarch.rpm > > 51 kB > 00:00 > (9/13): python-pulp-agent-lib-2.6.0-1.el6.noarch.rpm > > 89 kB > 00:00 > (10/13): python-qpid-proton-0.9-1.20150219.el6.x86_64.rpm > > 188 kB > 00:01 > (11/13): python-rhsm-1.13.8-1.el6.x86_64.rpm > > 112 kB > 00:00 > (12/13): subscription-manager-1.13.12-1.el6.x86_64.rpm > > 798 kB > 00:01 > (13/13): usermode-1.102-3.el6.x86_64.rpm > > 187 kB > 00:00 > > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > Total > 130 kB/s | 2.0 MB > 00:15 > Running rpm_check_debug > Running Transaction Test > Transaction Test Succeeded > Running Transaction > Updating : python-rhsm-1.13.8-1.el6.x86_64 > > 1/14 > Installing : python-pulp-agent-lib-2.6.0-1.el6.noarch > > 2/14 > Installing : pulp-rpm-handlers-2.6.0-1.el6.noarch > > 3/14 > Installing : usermode-1.102-3.el6.x86_64 > > 4/14 > Installing : python-dmidecode-3.10.13-3.el6_4.x86_64 > > 5/14 > Installing : python-ethtool-0.6-5.el6.x86_64 > > 6/14 > Installing : gofer-2.5.3-1.el6.noarch > > 7/14 > Installing : dbus-python-0.83.0-6.1.el6.x86_64 > > 8/14 > Installing : pygobject2-2.20.0-5.el6.x86_64 > > 9/14 > Installing : subscription-manager-1.13.12-1.el6.x86_64 > > 10/14 > Installing : python-qpid-proton-0.9-1.20150219.el6.x86_64 > > 11/14 > Installing : python-gofer-proton-2.5.3-1.el6.noarch > > 12/14 > Installing : katello-agent-2.3.0-1.el6.noarch > > 13/14 > Stopping goferd[FAILED] > > > Starting goferd[ OK ] > > > Cleanup : python-rhsm-1.8.0-2.pulp.el6.x86_64 > > 14/14 > Verifying : katello-agent-2.3.0-1.el6.noarch > > 1/14 > Verifying : python-qpid-proton-0.9-1.20150219.el6.x86_64 > > 2/14 > Verifying : pulp-rpm-handlers-2.6.0-1.el6.noarch > > 3/14 > Verifying : python-gofer-proton-2.5.3-1.el6.noarch > > 4/14 > Verifying : pygobject2-2.20.0-5.el6.x86_64 > > 5/14 > Verifying : dbus-python-0.83.0-6.1.el6.x86_64 > > 6/14 > Verifying : gofer-2.5.3-1.el6.noarch > > 7/14 > Verifying : python-pulp-agent-lib-2.6.0-1.el6.noarch > > 8/14 > Verifying : python-rhsm-1.13.8-1.el6.x86_64 > > 9/14 > Verifying : subscription-manager-1.13.12-1.el6.x86_64 > > 10/14 > Verifying : python-ethtool-0.6-5.el6.x86_64 > > 11/14 > Verifying : python-dmidecode-3.10.13-3.el6_4.x86_64 > > 12/14 > Verifying : usermode-1.102-3.el6.x86_64 > > 13/14 > Verifying : python-rhsm-1.8.0-2.pulp.el6.x86_64 > > 14/14 > > Installed: > katello-agent.noarch 0:2.3.0-1.el6 > > > > Dependency Installed: > dbus-python.x86_64 0:0.83.0-6.1.el6 gofer.noarch > 0:2.5.3-1.el6 pulp-rpm-handlers.noarch > 0:2.6.0-1.el6 > pygobject2.x86_64 0:2.20.0-5.el6 > python-dmidecode.x86_64 0:3.10.13-3.el6_4 python-ethtool.x86_64 > 0:0.6-5.el6 > python-gofer-proton.noarch 0:2.5.3-1.el6 > python-pulp-agent-lib.noarch 0:2.6.0-1.el6 > python-qpid-proton.x86_64 0:0.9-1.20150219.el6 > subscription-manager.x86_64 0:1.13.12-1.el6 usermode.x86_64 > 0:1.102-3.el6 > > Dependency Updated: > python-rhsm.x86_64 0:1.13.8-1.el6 > > ...

JC1 · April 8, 2015, 8:15pm

I'm not sure my approach will help you. As I couldn't get the rpms for the
subscription-manager (on CentOS) from elsewhere (at that time), at least
any that didn't leave my in dependency hell, I used the RHEL packages.

Yes, 2.2 and certainly RC2 has been much better (not tried RC3 yet).
Actually, I think the upgrade was only marginally better, it was when I did
a new install using 2.2 that things improved (but perhaps I was just
imagining it) - certainly more tasks now complete unassisted, but I still
have the candlepin tasks which never close off.

So you are configuring your published products in the client's .repo
file(s), right? That's the bit that doesn't work for you if you don't have
a content view created? If so, I can test that for you on Friday (sorry,
not around tomorrow). Unless someone else can earlier…

···

On 8 April 2015 at 18:43, Mark White wrote:

Hi

I am still testing with Katello 2.1, and trying to get it to work with OEL
and having problems with subscription. Could you explain what the fudge was
you did for 2.1 and have you found 2.2 better ?

Also, in case I cannot get subscription to work so just using the repo
with yum, am I right thinking you just need a standard content view for
each repo, as a composite view fails as you still need the full path to
each of the repodata dirs in the compolsite i.e. composite is only useful
if subscription works ?

On Wednesday, April 1, 2015 at 11:04:17 AM UTC+1, JC wrote:
Hi.

I’ve just completed a new install of Katello (katello-2.3.0-1.
201503310129git07a6e29.el6.noarch) on a CentOS6.6 minimal install.
What’s the right* way to setup CentOS 5 and CentOS 6 clients (*I fudged
this with an earlier 2.1 install)? The documentation
http://www.katello.org/docs/2.2/user_guide/content/content.html says:

Subscribing a System to a Product for yum content
To read about registering systems and subscribing them to the Product
click TODO.

# yum install katello-agent

Loaded plugins: fastestmirror

Setting up Install Process

Loading mirror speeds from cached hostfile

base: anorien.csc.warwick.ac.uk

epel: anorien.csc.warwick.ac.uk

extras: anorien.csc.warwick.ac.uk

updates: repo.bigstepcloud.com

Resolving Dependencies

–> Running transaction check

—> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed

–> Processing Dependency: python-pulp-agent-lib >= 2.6 for package:
katello-agent-2.3.0-1.el6.noarch

–> Processing Dependency: python-gofer-proton >= 2.5 for package:
katello-agent-2.3.0-1.el6.noarch

–> Processing Dependency: pulp-rpm-handlers >= 2.6 for package:
katello-agent-2.3.0-1.el6.noarch

–> Processing Dependency: gofer >= 2.5 for package:
katello-agent-2.3.0-1.el6.noarch

–> Processing Dependency: subscription-manager for package:
katello-agent-2.3.0-1.el6.noarch

–> Running transaction check

—> Package gofer.noarch 0:2.5.3-1.el6 will be installed

—> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed

–> Processing Dependency: subscription-manager for package:
katello-agent-2.3.0-1.el6.noarch

—> Package pulp-rpm-handlers.noarch 0:2.6.0-1.el6 will be installed

—> Package python-gofer-proton.noarch 0:2.5.3-1.el6 will be installed

–> Processing Dependency: python-qpid-proton >= 0.9-1.20150219 for
package: python-gofer-proton-2.5.3-1.el6.noarch

—> Package python-pulp-agent-lib.noarch 0:2.6.0-1.el6 will be installed

–> Running transaction check

—> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed

–> Processing Dependency: subscription-manager for package:
katello-agent-2.3.0-1.el6.noarch

—> Package python-qpid-proton.x86_64 0:0.9-1.20150219.el6 will be
installed

–> Finished Dependency Resolution

Error: Package: katello-agent-2.3.0-1.el6.noarch (katello)

Requires: subscription-manager*

# rpm -qa | grep “katello|pulp|candle|foreman”

foreman-proxy-1.9.0-0.develop.201503311321git95cd9c8.el6.noarch

foreman-debug-1.9.0-0.develop.201503261813git331ff16.el6.noarch

python-pulp-bindings-2.6.0-1.el6.noarch

katello-debug-2.3.0-1.201503310129git07a6e29.el6.noarch

python-pulp-docker-common-0.2.2-1.el6.noarch

foreman-1.9.0-0.develop.201503261813git331ff16.el6.noarch

foreman-vmware-1.9.0-0.develop.201503261813git331ff16.el6.noarch

rubygem-hammer_cli_foreman_tasks-0.0.5-1.el6.noarch

ruby193-rubygem-foreman_bootdisk-5.0.0-1.el6.noarch

rubygem-hammer_cli_katello-0.0.11-1.201503271931git8799b04.
git.0.db4e3db.el6.noarch

candlepin-tomcat6-0.9.47-1.el6.noarch

katello-selinux-2.2.1-1.el6.noarch

pulp-nodes-common-2.6.0-1.el6.noarch

pulp-katello-0.3-4.el6.noarch

katello-2.3.0-1.201503310129git07a6e29.el6.noarch

pulp-puppet-tools-2.6.0-1.el6.noarch

katello-certs-tools-2.0.1-1.el6.noarch

katello-default-ca-1.0-1.noarch

katello-repos-2.3.0-2.el6.noarch

kmaster.lan-foreman-proxy-client-1.0-1.noarch

python-pulp-rpm-common-2.6.0-1.el6.noarch

foreman-libvirt-1.9.0-0.develop.201503261813git331ff16.el6.noarch

ruby193-rubygem-foreman_hooks-0.3.7-3.el6.noarch

candlepin-common-1.0.22-1.el6.noarch

candlepin-selinux-0.9.47-1.el6.noarch

rubygem-hammer_cli_foreman_docker-0.0.3-2.el6.noarch

pulp-selinux-2.6.0-1.el6.noarch

pulp-puppet-plugins-2.6.0-1.el6.noarch

pulp-docker-plugins-0.2.2-1.el6.noarch

katello-common-2.3.0-1.201503310129git07a6e29.el6.noarch

rubygem-smart_proxy_pulp-1.0.1-2.el6.noarch

kmaster.lan-foreman-proxy-1.0-1.noarch

m2crypto-0.21.1.pulp-8.el6.x86_64

python-isodate-0.5.0-4.pulp.el6.noarch

python-rhsm-1.8.0-2.pulp.el6.x86_64

foreman-gce-1.9.0-0.develop.201503261813git331ff16.el6.noarch

foreman-ovirt-1.9.0-0.develop.201503261813git331ff16.el6.noarch

mod_wsgi-3.4-2.pulp.el6.x86_64

candlepin-0.9.47-1.el6.noarch

pulp-server-2.6.0-1.el6.noarch

pulp-rpm-plugins-2.6.0-1.el6.noarch

ruby193-rubygem-foreman_gutterball-0.0.1-1.201503061946gite954cd1.git.0.
6e21da0.el6.noarch

katello-installer-base-2.3.0-1.201503232042git7769450.el6.noarch

kmaster.lan-foreman-client-1.0-1.noarch

python-pulp-common-2.6.0-1.el6.noarch

python-pulp-puppet-common-2.6.0-1.el6.noarch

foreman-compute-1.9.0-0.develop.201503261813git331ff16.el6.noarch

ruby193-rubygem-foreman_docker-1.2.4-1.fm1_9.el6.noarch

ruby193-rubygem-foreman-tasks-0.6.13-2.el6.noarch

python-kombu-3.0.24-5.pulp.el6.noarch

rubygem-hammer_cli_foreman-0.1.4-1.201503240905git7377f48.el6.noarch

rubygem-hammer_cli_foreman_bootdisk-0.1.2-1.el6.noarch

foreman-selinux-1.9.0-0.develop.201503091423git639a8ed.el6.noarch

pulp-nodes-parent-2.6.0-1.el6.noarch

ruby193-rubygem-katello-2.3.0-1.201503310036git07a6e29.el6.noarch

katello-installer-2.3.0-1.201503232042git7769450.el6.noarch

katello-server-ca-1.0-1.noarch

foreman-release-1.9.0-0.develop.201503261813git331ff16.el6.noarch

foreman-postgresql-1.9.0-0.develop.201503261813git331ff16.el6.noarch

Repos provided by the CentOS and Katello installs:

# yum repolist

Loaded plugins: fastestmirror

Loading mirror speeds from cached hostfile

base: anorien.csc.warwick.ac.uk

epel: anorien.csc.warwick.ac.uk

extras: anorien.csc.warwick.ac.uk

updates: repo.bigstepcloud.com

repo id repo name
  status
SCL CentOS-6 - SCL
    504
base CentOS-6 - Base
   6,518
epel Extra Packages for Enterprise Linux 6 - x86_64
 11,362
extras CentOS-6 - Extras
      37
foreman Foreman nightly
     243
foreman-plugins Foreman plugins nightly
     559
katello Katello Nightly
     142
katello-candlepin Candlepin: an open source entitlement management
system.
6

katello-client Katello Client Nightly
     16
katello-pulp Pulp Community Releases
      67
puppetlabs-deps Puppet Labs Dependencies El 6 - x86_64
     77
puppetlabs-products Puppet Labs Products El 6 - x86_64
    494
updates CentOS-6 - Updates
    926
–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/W0bK-Ystni4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Jamie.

Mark_White · April 9, 2015, 4:45pm

Jamie

Think I am making hard work of this …

I now have a client system that can access the yum repo if I configure the
yum.repos.d files with URL from the Library contentview repos (not
composite ones). I have also downloaded and run the subscription manager so
that it said it successfully registered the client and returned an ID.
However if I log onto the Katello server it gives no indication it has the
client registered - where should I look to confirm registration from the
server side ?

On the client if I run "subscription-manager config" I see it points to the
Katello server with a baseurl for [rhsm] ending ~pulp/repos" Did you update
the /etc/rhsm/rhsm.conf file to point to your Centos repos ?

Do you know if using the subscription-manager GUI is useful ?

Sorry if very basic Q's but just getting started.

Mark

···

On Wednesday, April 8, 2015 at 9:16:13 PM UTC+1, JC wrote: > > I'm not sure my approach will help you. As I couldn't get the rpms for > the subscription-manager (on CentOS) from elsewhere (at that time), at > least any that didn't leave my in dependency hell, I used the RHEL packages. > > Yes, 2.2 and certainly RC2 has been much better (not tried RC3 yet). > Actually, I think the upgrade was only marginally better, it was when I did > a new install using 2.2 that things improved (but perhaps I was just > imagining it) - certainly more tasks now complete unassisted, but I still > have the candlepin tasks which never close off. > > So you are configuring your published products in the client's .repo > file(s), right? That's the bit that doesn't work for you if you don't have > a content view created? If so, I can test that for you on Friday (sorry, > not around tomorrow). Unless someone else can earlier... > > > On 8 April 2015 at 18:43, Mark White <mark.f....@gmail.com > > wrote: > >> Hi >> >> I am still testing with Katello 2.1, and trying to get it to work with >> OEL and having problems with subscription. Could you explain what the fudge >> was you did for 2.1 and have you found 2.2 better ? >> >> Also, in case I cannot get subscription to work so just using the repo >> with yum, am I right thinking you just need a standard content view for >> each repo, as a composite view fails as you still need the full path to >> each of the repodata dirs in the compolsite i.e. composite is only useful >> if subscription works ? >> >> >> >> On Wednesday, April 1, 2015 at 11:04:17 AM UTC+1, JC wrote: >>> >>> Hi. >>> >>> I've just completed a new install of Katello (katello-2.3.0-1. >>> 201503310129git07a6e29.el6.noarch) on a CentOS6.6 minimal install. >>> What's the right* way to setup CentOS 5 and CentOS 6 clients (*I fudged >>> this with an earlier 2.1 install)? The documentation >>> says: >>> >>> *Subscribing a System to a Product for yum content* >>> To read about registering systems and subscribing them to the Product >>> click TODO. >>> >>> *# yum install katello-agent* >>> >>> Loaded plugins: fastestmirror >>> >>> Setting up Install Process >>> >>> Loading mirror speeds from cached hostfile >>> >>> * base: anorien.csc.warwick.ac.uk >>> >>> * epel: anorien.csc.warwick.ac.uk >>> >>> * extras: anorien.csc.warwick.ac.uk >>> >>> * updates: repo.bigstepcloud.com >>> >>> Resolving Dependencies >>> >>> --> Running transaction check >>> >>> ---> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed >>> >>> --> Processing Dependency: python-pulp-agent-lib >= 2.6 for package: >>> katello-agent-2.3.0-1.el6.noarch >>> >>> --> Processing Dependency: python-gofer-proton >= 2.5 for package: >>> katello-agent-2.3.0-1.el6.noarch >>> >>> --> Processing Dependency: pulp-rpm-handlers >= 2.6 for package: >>> katello-agent-2.3.0-1.el6.noarch >>> >>> --> Processing Dependency: gofer >= 2.5 for package: >>> katello-agent-2.3.0-1.el6.noarch >>> >>> --> Processing Dependency: subscription-manager for package: >>> katello-agent-2.3.0-1.el6.noarch >>> >>> --> Running transaction check >>> >>> ---> Package gofer.noarch 0:2.5.3-1.el6 will be installed >>> >>> ---> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed >>> >>> --> Processing Dependency: subscription-manager for package: >>> katello-agent-2.3.0-1.el6.noarch >>> >>> ---> Package pulp-rpm-handlers.noarch 0:2.6.0-1.el6 will be installed >>> >>> ---> Package python-gofer-proton.noarch 0:2.5.3-1.el6 will be installed >>> >>> --> Processing Dependency: python-qpid-proton >= 0.9-1.20150219 for >>> package: python-gofer-proton-2.5.3-1.el6.noarch >>> >>> ---> Package python-pulp-agent-lib.noarch 0:2.6.0-1.el6 will be installed >>> >>> --> Running transaction check >>> >>> ---> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed >>> >>> --> Processing Dependency: subscription-manager for package: >>> katello-agent-2.3.0-1.el6.noarch >>> >>> ---> Package python-qpid-proton.x86_64 0:0.9-1.20150219.el6 will be >>> installed >>> >>> --> Finished Dependency Resolution >>> >>> Error: Package: katello-agent-2.3.0-1.el6.noarch (katello) >>> >>> * Requires: subscription-manager* >>> >>> >>> >>> *# rpm -qa | grep "katello\|pulp\|candle\|foreman"* >>> >>> foreman-proxy-1.9.0-0.develop.201503311321git95cd9c8.el6.noarch >>> >>> foreman-debug-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>> >>> python-pulp-bindings-2.6.0-1.el6.noarch >>> >>> katello-debug-2.3.0-1.201503310129git07a6e29.el6.noarch >>> >>> python-pulp-docker-common-0.2.2-1.el6.noarch >>> >>> foreman-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>> >>> foreman-vmware-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>> >>> rubygem-hammer_cli_foreman_tasks-0.0.5-1.el6.noarch >>> >>> ruby193-rubygem-foreman_bootdisk-5.0.0-1.el6.noarch >>> >>> rubygem-hammer_cli_katello-0.0.11-1.201503271931git8799b04. >>> git.0.db4e3db.el6.noarch >>> >>> candlepin-tomcat6-0.9.47-1.el6.noarch >>> >>> katello-selinux-2.2.1-1.el6.noarch >>> >>> pulp-nodes-common-2.6.0-1.el6.noarch >>> >>> pulp-katello-0.3-4.el6.noarch >>> >>> katello-2.3.0-1.201503310129git07a6e29.el6.noarch >>> >>> pulp-puppet-tools-2.6.0-1.el6.noarch >>> >>> katello-certs-tools-2.0.1-1.el6.noarch >>> >>> katello-default-ca-1.0-1.noarch >>> >>> katello-repos-2.3.0-2.el6.noarch >>> >>> kmaster.lan-foreman-proxy-client-1.0-1.noarch >>> >>> python-pulp-rpm-common-2.6.0-1.el6.noarch >>> >>> foreman-libvirt-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>> >>> ruby193-rubygem-foreman_hooks-0.3.7-3.el6.noarch >>> >>> candlepin-common-1.0.22-1.el6.noarch >>> >>> candlepin-selinux-0.9.47-1.el6.noarch >>> >>> rubygem-hammer_cli_foreman_docker-0.0.3-2.el6.noarch >>> >>> pulp-selinux-2.6.0-1.el6.noarch >>> >>> pulp-puppet-plugins-2.6.0-1.el6.noarch >>> >>> pulp-docker-plugins-0.2.2-1.el6.noarch >>> >>> katello-common-2.3.0-1.201503310129git07a6e29.el6.noarch >>> >>> rubygem-smart_proxy_pulp-1.0.1-2.el6.noarch >>> >>> kmaster.lan-foreman-proxy-1.0-1.noarch >>> >>> m2crypto-0.21.1.pulp-8.el6.x86_64 >>> >>> python-isodate-0.5.0-4.pulp.el6.noarch >>> >>> python-rhsm-1.8.0-2.pulp.el6.x86_64 >>> >>> foreman-gce-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>> >>> foreman-ovirt-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>> >>> mod_wsgi-3.4-2.pulp.el6.x86_64 >>> >>> candlepin-0.9.47-1.el6.noarch >>> >>> pulp-server-2.6.0-1.el6.noarch >>> >>> pulp-rpm-plugins-2.6.0-1.el6.noarch >>> >>> ruby193-rubygem-foreman_gutterball-0.0.1-1.201503061946gite954cd1.git.0. >>> 6e21da0.el6.noarch >>> >>> katello-installer-base-2.3.0-1.201503232042git7769450.el6.noarch >>> >>> kmaster.lan-foreman-client-1.0-1.noarch >>> >>> python-pulp-common-2.6.0-1.el6.noarch >>> >>> python-pulp-puppet-common-2.6.0-1.el6.noarch >>> >>> foreman-compute-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>> >>> ruby193-rubygem-foreman_docker-1.2.4-1.fm1_9.el6.noarch >>> >>> ruby193-rubygem-foreman-tasks-0.6.13-2.el6.noarch >>> >>> python-kombu-3.0.24-5.pulp.el6.noarch >>> >>> rubygem-hammer_cli_foreman-0.1.4-1.201503240905git7377f48.el6.noarch >>> >>> rubygem-hammer_cli_foreman_bootdisk-0.1.2-1.el6.noarch >>> >>> foreman-selinux-1.9.0-0.develop.201503091423git639a8ed.el6.noarch >>> >>> pulp-nodes-parent-2.6.0-1.el6.noarch >>> >>> ruby193-rubygem-katello-2.3.0-1.201503310036git07a6e29.el6.noarch >>> >>> katello-installer-2.3.0-1.201503232042git7769450.el6.noarch >>> >>> katello-server-ca-1.0-1.noarch >>> >>> foreman-release-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>> >>> foreman-postgresql-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>> >>> Repos provided by the CentOS and Katello installs: >>> >>> *# yum repolist* >>> >>> Loaded plugins: fastestmirror >>> >>> Loading mirror speeds from cached hostfile >>> >>> * base: anorien.csc.warwick.ac.uk >>> >>> * epel: anorien.csc.warwick.ac.uk >>> >>> * extras: anorien.csc.warwick.ac.uk >>> >>> * updates: repo.bigstepcloud.com >>> >>> repo id repo name >>> >>> status >>> >>> SCL CentOS-6 - SCL >>> >>> 504 >>> >>> base CentOS-6 - Base >>> >>> 6,518 >>> >>> epel Extra Packages for Enterprise Linux 6 - x86_64 >>> >>> 11,362 >>> >>> extras CentOS-6 - Extras >>> >>> 37 >>> >>> foreman Foreman nightly >>> >>> 243 >>> >>> foreman-plugins Foreman plugins nightly >>> >>> 559 >>> >>> katello Katello Nightly >>> >>> 142 >>> >>> katello-candlepin Candlepin: an open source entitlement management >>> system. >>> 6 >>> >>> katello-client Katello Client Nightly >>> >>> 16 >>> >>> katello-pulp Pulp Community Releases >>> >>> 67 >>> >>> puppetlabs-deps Puppet Labs Dependencies El 6 - x86_64 >>> >>> 77 >>> >>> puppetlabs-products Puppet Labs Products El 6 - x86_64 >>> >>> 494 >>> >>> updates CentOS-6 - Updates >>> >>> 926 >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Foreman users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/foreman-users/W0bK-Ystni4/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Jamie. >

JC1 · April 9, 2015, 5:27pm

Hi.

Sounds like good progress. Keep going…

I'm probably saying the obvious, but how I see it is you can direct your
'unmanaged' hosts to the published repos (via /etc/yum.repos.d/your.repo)
and you can have managed clients by installing the agents (katello-agent
and subscription-manager) and then by registering/attaching them to the
products (you have created, with associated repos).

No, I didn't edit /etc/rhsm/rhsm.conf, but looking at my client's copy, it
already includes the katello server hostname and correct baseurl.

If you look under Hosts -> Content Hosts (from the Foreman UI) you should
see your host there (if it registered). You want to see a green dot for
the subscription status.

I registered from the command line as shown
<http://www.katello.org/docs/2.2/user_guide/content_hosts/index.html>, and
have used all suggestions - the base library, a content view, with an
activation key, with a password – all worked.

Once you can see your host in the UI, you can subscribe it to your products
and then see the repos from the client:

$ subscription-manager repos

Alternatively, once registered, you can attach from the client:

$ subscription-manager attach --pool {poolid}

From your the client what do you get for:
$ subscription-manager identity

I wrote a bash script for the install of our clients (note to self: you
still need to finish testing), just reading back through it, perhaps that
will shed more light on the topic (probably just repetition though)…I
check the FQDN resolution for the client and the katello server, I check
the ports are open / the script is running as root, create a temporary
.repo file to get the rpms for the software we will be installing*, install
the katello server cert, install the agents, register and then check which
repos are available.

*I have a product which contains the various external repos for the
clients, which I then publish. I can confirm the external URLs if that
would help.

···

On 9 April 2015 at 17:45, Mark White wrote:

Jamie

Think I am making hard work of this …

I now have a client system that can access the yum repo if I configure the
yum.repos.d files with URL from the Library contentview repos (not
composite ones). I have also downloaded and run the subscription manager so
that it said it successfully registered the client and returned an ID.
However if I log onto the Katello server it gives no indication it has the
client registered - where should I look to confirm registration from the
server side ?

On the client if I run “subscription-manager config” I see it points to
the Katello server with a baseurl for [rhsm] ending ~pulp/repos" Did you
update the /etc/rhsm/rhsm.conf file to point to your Centos repos ?

Do you know if using the subscription-manager GUI is useful ?

Sorry if very basic Q’s but just getting started.

Mark

On Wednesday, April 8, 2015 at 9:16:13 PM UTC+1, JC wrote:
I’m not sure my approach will help you. As I couldn’t get the rpms for
the subscription-manager (on CentOS) from elsewhere (at that time), at
least any that didn’t leave my in dependency hell, I used the RHEL packages.

Yes, 2.2 and certainly RC2 has been much better (not tried RC3 yet).
Actually, I think the upgrade was only marginally better, it was when I did
a new install using 2.2 that things improved (but perhaps I was just
imagining it) - certainly more tasks now complete unassisted, but I still
have the candlepin tasks which never close off.

So you are configuring your published products in the client’s .repo
file(s), right? That’s the bit that doesn’t work for you if you don’t have
a content view created? If so, I can test that for you on Friday (sorry,
not around tomorrow). Unless someone else can earlier…

On 8 April 2015 at 18:43, Mark White mark.f....@gmail.com wrote:
Hi

I am still testing with Katello 2.1, and trying to get it to work with
OEL and having problems with subscription. Could you explain what the fudge
was you did for 2.1 and have you found 2.2 better ?

Also, in case I cannot get subscription to work so just using the repo
with yum, am I right thinking you just need a standard content view for
each repo, as a composite view fails as you still need the full path to
each of the repodata dirs in the compolsite i.e. composite is only useful
if subscription works ?

On Wednesday, April 1, 2015 at 11:04:17 AM UTC+1, JC wrote:
Hi.

I’ve just completed a new install of Katello (katello-2.3.0-1.
201503310129git07a6e29.el6.noarch) on a CentOS6.6 minimal install.
What’s the right* way to setup CentOS 5 and CentOS 6 clients (*I fudged
this with an earlier 2.1 install)? The documentation
http://www.katello.org/docs/2.2/user_guide/content/content.html says:

Subscribing a System to a Product for yum content
To read about registering systems and subscribing them to the Product
click TODO.

# yum install katello-agent

Loaded plugins: fastestmirror

Setting up Install Process

Loading mirror speeds from cached hostfile

base: anorien.csc.warwick.ac.uk

epel: anorien.csc.warwick.ac.uk

extras: anorien.csc.warwick.ac.uk

updates: repo.bigstepcloud.com

Resolving Dependencies

–> Running transaction check

—> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed

–> Processing Dependency: python-pulp-agent-lib >= 2.6 for package:
katello-agent-2.3.0-1.el6.noarch

–> Processing Dependency: python-gofer-proton >= 2.5 for package:
katello-agent-2.3.0-1.el6.noarch

–> Processing Dependency: pulp-rpm-handlers >= 2.6 for package:
katello-agent-2.3.0-1.el6.noarch

–> Processing Dependency: gofer >= 2.5 for package:
katello-agent-2.3.0-1.el6.noarch

–> Processing Dependency: subscription-manager for package:
katello-agent-2.3.0-1.el6.noarch

–> Running transaction check

—> Package gofer.noarch 0:2.5.3-1.el6 will be installed

—> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed

–> Processing Dependency: subscription-manager for package:
katello-agent-2.3.0-1.el6.noarch

—> Package pulp-rpm-handlers.noarch 0:2.6.0-1.el6 will be installed

—> Package python-gofer-proton.noarch 0:2.5.3-1.el6 will be installed

–> Processing Dependency: python-qpid-proton >= 0.9-1.20150219 for
package: python-gofer-proton-2.5.3-1.el6.noarch

—> Package python-pulp-agent-lib.noarch 0:2.6.0-1.el6 will be
installed

–> Running transaction check

—> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed

–> Processing Dependency: subscription-manager for package:
katello-agent-2.3.0-1.el6.noarch

—> Package python-qpid-proton.x86_64 0:0.9-1.20150219.el6 will be
installed

–> Finished Dependency Resolution

Error: Package: katello-agent-2.3.0-1.el6.noarch (katello)

Requires: subscription-manager*

# rpm -qa | grep “katello|pulp|candle|foreman”

foreman-proxy-1.9.0-0.develop.201503311321git95cd9c8.el6.noarch

foreman-debug-1.9.0-0.develop.201503261813git331ff16.el6.noarch

python-pulp-bindings-2.6.0-1.el6.noarch

katello-debug-2.3.0-1.201503310129git07a6e29.el6.noarch

python-pulp-docker-common-0.2.2-1.el6.noarch

foreman-1.9.0-0.develop.201503261813git331ff16.el6.noarch

foreman-vmware-1.9.0-0.develop.201503261813git331ff16.el6.noarch

rubygem-hammer_cli_foreman_tasks-0.0.5-1.el6.noarch

ruby193-rubygem-foreman_bootdisk-5.0.0-1.el6.noarch

rubygem-hammer_cli_katello-0.0.11-1.201503271931git8799b04.g
it.0.db4e3db.el6.noarch

candlepin-tomcat6-0.9.47-1.el6.noarch

katello-selinux-2.2.1-1.el6.noarch

pulp-nodes-common-2.6.0-1.el6.noarch

pulp-katello-0.3-4.el6.noarch

katello-2.3.0-1.201503310129git07a6e29.el6.noarch

pulp-puppet-tools-2.6.0-1.el6.noarch

katello-certs-tools-2.0.1-1.el6.noarch

katello-default-ca-1.0-1.noarch

katello-repos-2.3.0-2.el6.noarch

kmaster.lan-foreman-proxy-client-1.0-1.noarch

python-pulp-rpm-common-2.6.0-1.el6.noarch

foreman-libvirt-1.9.0-0.develop.201503261813git331ff16.el6.noarch

ruby193-rubygem-foreman_hooks-0.3.7-3.el6.noarch

candlepin-common-1.0.22-1.el6.noarch

candlepin-selinux-0.9.47-1.el6.noarch

rubygem-hammer_cli_foreman_docker-0.0.3-2.el6.noarch

pulp-selinux-2.6.0-1.el6.noarch

pulp-puppet-plugins-2.6.0-1.el6.noarch

pulp-docker-plugins-0.2.2-1.el6.noarch

katello-common-2.3.0-1.201503310129git07a6e29.el6.noarch

rubygem-smart_proxy_pulp-1.0.1-2.el6.noarch

kmaster.lan-foreman-proxy-1.0-1.noarch

m2crypto-0.21.1.pulp-8.el6.x86_64

python-isodate-0.5.0-4.pulp.el6.noarch

python-rhsm-1.8.0-2.pulp.el6.x86_64

foreman-gce-1.9.0-0.develop.201503261813git331ff16.el6.noarch

foreman-ovirt-1.9.0-0.develop.201503261813git331ff16.el6.noarch

mod_wsgi-3.4-2.pulp.el6.x86_64

candlepin-0.9.47-1.el6.noarch

pulp-server-2.6.0-1.el6.noarch

pulp-rpm-plugins-2.6.0-1.el6.noarch

ruby193-rubygem-foreman_gutterball-0.0.1-1.201503061946gite9
54cd1.git.0.6e21da0.el6.noarch

katello-installer-base-2.3.0-1.201503232042git7769450.el6.noarch

kmaster.lan-foreman-client-1.0-1.noarch

python-pulp-common-2.6.0-1.el6.noarch

python-pulp-puppet-common-2.6.0-1.el6.noarch

foreman-compute-1.9.0-0.develop.201503261813git331ff16.el6.noarch

ruby193-rubygem-foreman_docker-1.2.4-1.fm1_9.el6.noarch

ruby193-rubygem-foreman-tasks-0.6.13-2.el6.noarch

python-kombu-3.0.24-5.pulp.el6.noarch

rubygem-hammer_cli_foreman-0.1.4-1.201503240905git7377f48.el6.noarch

rubygem-hammer_cli_foreman_bootdisk-0.1.2-1.el6.noarch

foreman-selinux-1.9.0-0.develop.201503091423git639a8ed.el6.noarch

pulp-nodes-parent-2.6.0-1.el6.noarch

ruby193-rubygem-katello-2.3.0-1.201503310036git07a6e29.el6.noarch

katello-installer-2.3.0-1.201503232042git7769450.el6.noarch

katello-server-ca-1.0-1.noarch

foreman-release-1.9.0-0.develop.201503261813git331ff16.el6.noarch

foreman-postgresql-1.9.0-0.develop.201503261813git331ff16.el6.noarch

Repos provided by the CentOS and Katello installs:

# yum repolist

Loaded plugins: fastestmirror

Loading mirror speeds from cached hostfile

base: anorien.csc.warwick.ac.uk

epel: anorien.csc.warwick.ac.uk

extras: anorien.csc.warwick.ac.uk

updates: repo.bigstepcloud.com

repo id repo name
    status
SCL CentOS-6 - SCL
      504
base CentOS-6 - Base
     6,518
epel Extra Packages for Enterprise Linux 6 - x86_64
   11,362
extras CentOS-6 - Extras
        37
foreman Foreman nightly
       243
foreman-plugins Foreman plugins nightly
       559
katello Katello Nightly
       142
katello-candlepin Candlepin: an open source entitlement management
system.
6

katello-client Katello Client Nightly
       16
katello-pulp Pulp Community Releases
        67
puppetlabs-deps Puppet Labs Dependencies El 6 - x86_64
       77
puppetlabs-products Puppet Labs Products El 6 - x86_64
      494
updates CentOS-6 - Updates
      926
–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/foreman-users/W0bK-Ystni4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Jamie.
–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/W0bK-Ystni4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Jamie.

Mark_White · April 14, 2015, 5:29pm

Moved on a bit. As per your summary I can access the repo directly from
unamanaged hosts and can also install katello-agent with subscription
manager and then see a valid subscription under "content hosts"

With some digging I eventually found the screen where you select the
content hosts and add a subscription under the subscription tag. The list
of things you can subscribe to appears to be the repos and not the content
views ( I have tried to name the products, repos and content views so I
know what is being referred to) which is not what I expected. I have
created a composite content view (for demo) which contains two standard
content views, one pointing to a base repo and the other pointing to a
release 6.6 repo. When I look at the content views the two "simple"
content views each show as having 1 reppo, but the composite view which
contains both of them does not show it having any repo's - tried publishing
etc but does not change …

Thats when I noticed that when trying to add a subscription to a content
host I can only see the repos. The composite content view is not available
at all. Am I missing the point - I thought you registered with the content
views not the repo's, and you say below you registered with a content view
from the CLI. Did you manage to register using the GUI, and did you try a
composite view ?

Are your content views named the same as the repos they contain ?

Just reread your post and saw "Once you can see your host in the UI, you
can subscribe it to your products and then see the repos from the client" -
so you don't subscribe to content views ? confusing …

Mark

···

On Thursday, April 9, 2015 at 6:27:47 PM UTC+1, JC wrote: > > Hi. > > Sounds like good progress. Keep going... > > I'm probably saying the obvious, but how I see it is you can direct your > 'unmanaged' hosts to the published repos (via /etc/yum.repos.d/your.repo) > and you can have managed clients by installing the agents (katello-agent > and subscription-manager) and then by registering/attaching them to the > products (you have created, with associated repos). > > No, I didn't edit /etc/rhsm/rhsm.conf, but looking at my client's copy, > it already includes the katello server hostname and correct baseurl. > > If you look under Hosts -> Content Hosts (from the Foreman UI) you should > see your host there (if it registered). You want to see a green dot for > the subscription status. > > I registered from the command line as shown > , > and have used all suggestions - the base library, a content view, with an > activation key, with a password -- all worked. > > Once you can see your host in the UI, you can subscribe it to your > products and then see the repos from the client: > > $ subscription-manager repos > > Alternatively, once registered, you can attach from the client: > > $ subscription-manager attach --pool {poolid} > > From your the client what do you get for: > $ subscription-manager identity > > I wrote a bash script for the install of our clients (note to self: you > still need to finish testing), just reading back through it, perhaps that > will shed more light on the topic (probably just repetition though)...I > check the FQDN resolution for the client and the katello server, I check > the ports are open / the script is running as root, create a temporary > .repo file to get the rpms for the software we will be installing*, install > the katello server cert, install the agents, register and then check which > repos are available. > > *I have a product which contains the various external repos for the > clients, which I then publish. I can confirm the external URLs if that > would help. > > > On 9 April 2015 at 17:45, Mark White <mark.f....@gmail.com > > wrote: > >> Jamie >> >> Think I am making hard work of this .. >> >> I now have a client system that can access the yum repo if I configure >> the yum.repos.d files with URL from the Library contentview repos (not >> composite ones). I have also downloaded and run the subscription manager so >> that it said it successfully registered the client and returned an ID. >> However if I log onto the Katello server it gives no indication it has the >> client registered - where should I look to confirm registration from the >> server side ? >> >> On the client if I run "subscription-manager config" I see it points to >> the Katello server with a baseurl for [rhsm] ending ~pulp/repos" Did you >> update the /etc/rhsm/rhsm.conf file to point to your Centos repos ? >> >> Do you know if using the subscription-manager GUI is useful ? >> >> Sorry if very basic Q's but just getting started. >> >> >> Mark >> >> On Wednesday, April 8, 2015 at 9:16:13 PM UTC+1, JC wrote: >>> >>> I'm not sure my approach will help you. As I couldn't get the rpms for >>> the subscription-manager (on CentOS) from elsewhere (at that time), at >>> least any that didn't leave my in dependency hell, I used the RHEL packages. >>> >>> Yes, 2.2 and certainly RC2 has been much better (not tried RC3 yet). >>> Actually, I think the upgrade was only marginally better, it was when I did >>> a new install using 2.2 that things improved (but perhaps I was just >>> imagining it) - certainly more tasks now complete unassisted, but I still >>> have the candlepin tasks which never close off. >>> >>> So you are configuring your published products in the client's .repo >>> file(s), right? That's the bit that doesn't work for you if you don't have >>> a content view created? If so, I can test that for you on Friday (sorry, >>> not around tomorrow). Unless someone else can earlier... >>> >>> >>> On 8 April 2015 at 18:43, Mark White wrote: >>> >>>> Hi >>>> >>>> I am still testing with Katello 2.1, and trying to get it to work with >>>> OEL and having problems with subscription. Could you explain what the fudge >>>> was you did for 2.1 and have you found 2.2 better ? >>>> >>>> Also, in case I cannot get subscription to work so just using the repo >>>> with yum, am I right thinking you just need a standard content view for >>>> each repo, as a composite view fails as you still need the full path to >>>> each of the repodata dirs in the compolsite i.e. composite is only useful >>>> if subscription works ? >>>> >>>> >>>> >>>> On Wednesday, April 1, 2015 at 11:04:17 AM UTC+1, JC wrote: >>>>> >>>>> Hi. >>>>> >>>>> I've just completed a new install of Katello (katello-2.3.0-1. >>>>> 201503310129git07a6e29.el6.noarch) on a CentOS6.6 minimal install. >>>>> What's the right* way to setup CentOS 5 and CentOS 6 clients (*I fudged >>>>> this with an earlier 2.1 install)? The documentation >>>>> >>>>> says: >>>>> >>>>> *Subscribing a System to a Product for yum content* >>>>> To read about registering systems and subscribing them to the Product >>>>> click TODO. >>>>> >>>>> *# yum install katello-agent* >>>>> >>>>> Loaded plugins: fastestmirror >>>>> >>>>> Setting up Install Process >>>>> >>>>> Loading mirror speeds from cached hostfile >>>>> >>>>> * base: anorien.csc.warwick.ac.uk >>>>> >>>>> * epel: anorien.csc.warwick.ac.uk >>>>> >>>>> * extras: anorien.csc.warwick.ac.uk >>>>> >>>>> * updates: repo.bigstepcloud.com >>>>> >>>>> Resolving Dependencies >>>>> >>>>> --> Running transaction check >>>>> >>>>> ---> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed >>>>> >>>>> --> Processing Dependency: python-pulp-agent-lib >= 2.6 for package: >>>>> katello-agent-2.3.0-1.el6.noarch >>>>> >>>>> --> Processing Dependency: python-gofer-proton >= 2.5 for package: >>>>> katello-agent-2.3.0-1.el6.noarch >>>>> >>>>> --> Processing Dependency: pulp-rpm-handlers >= 2.6 for package: >>>>> katello-agent-2.3.0-1.el6.noarch >>>>> >>>>> --> Processing Dependency: gofer >= 2.5 for package: >>>>> katello-agent-2.3.0-1.el6.noarch >>>>> >>>>> --> Processing Dependency: subscription-manager for package: >>>>> katello-agent-2.3.0-1.el6.noarch >>>>> >>>>> --> Running transaction check >>>>> >>>>> ---> Package gofer.noarch 0:2.5.3-1.el6 will be installed >>>>> >>>>> ---> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed >>>>> >>>>> --> Processing Dependency: subscription-manager for package: >>>>> katello-agent-2.3.0-1.el6.noarch >>>>> >>>>> ---> Package pulp-rpm-handlers.noarch 0:2.6.0-1.el6 will be installed >>>>> >>>>> ---> Package python-gofer-proton.noarch 0:2.5.3-1.el6 will be installed >>>>> >>>>> --> Processing Dependency: python-qpid-proton >= 0.9-1.20150219 for >>>>> package: python-gofer-proton-2.5.3-1.el6.noarch >>>>> >>>>> ---> Package python-pulp-agent-lib.noarch 0:2.6.0-1.el6 will be >>>>> installed >>>>> >>>>> --> Running transaction check >>>>> >>>>> ---> Package katello-agent.noarch 0:2.3.0-1.el6 will be installed >>>>> >>>>> --> Processing Dependency: subscription-manager for package: >>>>> katello-agent-2.3.0-1.el6.noarch >>>>> >>>>> ---> Package python-qpid-proton.x86_64 0:0.9-1.20150219.el6 will be >>>>> installed >>>>> >>>>> --> Finished Dependency Resolution >>>>> >>>>> Error: Package: katello-agent-2.3.0-1.el6.noarch (katello) >>>>> >>>>> * Requires: subscription-manager* >>>>> >>>>> >>>>> >>>>> *# rpm -qa | grep "katello\|pulp\|candle\|foreman"* >>>>> >>>>> foreman-proxy-1.9.0-0.develop.201503311321git95cd9c8.el6.noarch >>>>> >>>>> foreman-debug-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>>>> >>>>> python-pulp-bindings-2.6.0-1.el6.noarch >>>>> >>>>> katello-debug-2.3.0-1.201503310129git07a6e29.el6.noarch >>>>> >>>>> python-pulp-docker-common-0.2.2-1.el6.noarch >>>>> >>>>> foreman-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>>>> >>>>> foreman-vmware-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>>>> >>>>> rubygem-hammer_cli_foreman_tasks-0.0.5-1.el6.noarch >>>>> >>>>> ruby193-rubygem-foreman_bootdisk-5.0.0-1.el6.noarch >>>>> >>>>> rubygem-hammer_cli_katello-0.0.11-1.201503271931git8799b04.g >>>>> it.0.db4e3db.el6.noarch >>>>> >>>>> candlepin-tomcat6-0.9.47-1.el6.noarch >>>>> >>>>> katello-selinux-2.2.1-1.el6.noarch >>>>> >>>>> pulp-nodes-common-2.6.0-1.el6.noarch >>>>> >>>>> pulp-katello-0.3-4.el6.noarch >>>>> >>>>> katello-2.3.0-1.201503310129git07a6e29.el6.noarch >>>>> >>>>> pulp-puppet-tools-2.6.0-1.el6.noarch >>>>> >>>>> katello-certs-tools-2.0.1-1.el6.noarch >>>>> >>>>> katello-default-ca-1.0-1.noarch >>>>> >>>>> katello-repos-2.3.0-2.el6.noarch >>>>> >>>>> kmaster.lan-foreman-proxy-client-1.0-1.noarch >>>>> >>>>> python-pulp-rpm-common-2.6.0-1.el6.noarch >>>>> >>>>> foreman-libvirt-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>>>> >>>>> ruby193-rubygem-foreman_hooks-0.3.7-3.el6.noarch >>>>> >>>>> candlepin-common-1.0.22-1.el6.noarch >>>>> >>>>> candlepin-selinux-0.9.47-1.el6.noarch >>>>> >>>>> rubygem-hammer_cli_foreman_docker-0.0.3-2.el6.noarch >>>>> >>>>> pulp-selinux-2.6.0-1.el6.noarch >>>>> >>>>> pulp-puppet-plugins-2.6.0-1.el6.noarch >>>>> >>>>> pulp-docker-plugins-0.2.2-1.el6.noarch >>>>> >>>>> katello-common-2.3.0-1.201503310129git07a6e29.el6.noarch >>>>> >>>>> rubygem-smart_proxy_pulp-1.0.1-2.el6.noarch >>>>> >>>>> kmaster.lan-foreman-proxy-1.0-1.noarch >>>>> >>>>> m2crypto-0.21.1.pulp-8.el6.x86_64 >>>>> >>>>> python-isodate-0.5.0-4.pulp.el6.noarch >>>>> >>>>> python-rhsm-1.8.0-2.pulp.el6.x86_64 >>>>> >>>>> foreman-gce-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>>>> >>>>> foreman-ovirt-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>>>> >>>>> mod_wsgi-3.4-2.pulp.el6.x86_64 >>>>> >>>>> candlepin-0.9.47-1.el6.noarch >>>>> >>>>> pulp-server-2.6.0-1.el6.noarch >>>>> >>>>> pulp-rpm-plugins-2.6.0-1.el6.noarch >>>>> >>>>> ruby193-rubygem-foreman_gutterball-0.0.1-1.201503061946gite9 >>>>> 54cd1.git.0.6e21da0.el6.noarch >>>>> >>>>> katello-installer-base-2.3.0-1.201503232042git7769450.el6.noarch >>>>> >>>>> kmaster.lan-foreman-client-1.0-1.noarch >>>>> >>>>> python-pulp-common-2.6.0-1.el6.noarch >>>>> >>>>> python-pulp-puppet-common-2.6.0-1.el6.noarch >>>>> >>>>> foreman-compute-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>>>> >>>>> ruby193-rubygem-foreman_docker-1.2.4-1.fm1_9.el6.noarch >>>>> >>>>> ruby193-rubygem-foreman-tasks-0.6.13-2.el6.noarch >>>>> >>>>> python-kombu-3.0.24-5.pulp.el6.noarch >>>>> >>>>> rubygem-hammer_cli_foreman-0.1.4-1.201503240905git7377f48.el6.noarch >>>>> >>>>> rubygem-hammer_cli_foreman_bootdisk-0.1.2-1.el6.noarch >>>>> >>>>> foreman-selinux-1.9.0-0.develop.201503091423git639a8ed.el6.noarch >>>>> >>>>> pulp-nodes-parent-2.6.0-1.el6.noarch >>>>> >>>>> ruby193-rubygem-katello-2.3.0-1.201503310036git07a6e29.el6.noarch >>>>> >>>>> katello-installer-2.3.0-1.201503232042git7769450.el6.noarch >>>>> >>>>> katello-server-ca-1.0-1.noarch >>>>> >>>>> foreman-release-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>>>> >>>>> foreman-postgresql-1.9.0-0.develop.201503261813git331ff16.el6.noarch >>>>> >>>>> Repos provided by the CentOS and Katello installs: >>>>> >>>>> *# yum repolist* >>>>> >>>>> Loaded plugins: fastestmirror >>>>> >>>>> Loading mirror speeds from cached hostfile >>>>> >>>>> * base: anorien.csc.warwick.ac.uk >>>>> >>>>> * epel: anorien.csc.warwick.ac.uk >>>>> >>>>> * extras: anorien.csc.warwick.ac.uk >>>>> >>>>> * updates: repo.bigstepcloud.com >>>>> >>>>> repo id repo name >>>>> >>>>> status >>>>> >>>>> SCL CentOS-6 - SCL >>>>> >>>>> 504 >>>>> >>>>> base CentOS-6 - Base >>>>> >>>>> 6,518 >>>>> >>>>> epel Extra Packages for Enterprise Linux 6 - x86_64 >>>>> >>>>> 11,362 >>>>> >>>>> extras CentOS-6 - Extras >>>>> >>>>> 37 >>>>> >>>>> foreman Foreman nightly >>>>> >>>>> 243 >>>>> >>>>> foreman-plugins Foreman plugins nightly >>>>> >>>>> 559 >>>>> >>>>> katello Katello Nightly >>>>> >>>>> 142 >>>>> >>>>> katello-candlepin Candlepin: an open source entitlement management >>>>> system. >>>>> 6 >>>>> >>>>> katello-client Katello Client Nightly >>>>> >>>>> 16 >>>>> >>>>> katello-pulp Pulp Community Releases >>>>> >>>>> 67 >>>>> >>>>> puppetlabs-deps Puppet Labs Dependencies El 6 - x86_64 >>>>> >>>>> 77 >>>>> >>>>> puppetlabs-products Puppet Labs Products El 6 - x86_64 >>>>> >>>>> 494 >>>>> >>>>> updates CentOS-6 - Updates >>>>> >>>>> 926 >>>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Foreman users" group. >>>> To unsubscribe from this topic, visit https://groups.google.com/d/ >>>> topic/foreman-users/W0bK-Ystni4/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> foreman-user...@googlegroups.com. >>>> To post to this group, send email to forema...@googlegroups.com. >>>> Visit this group at http://groups.google.com/group/foreman-users. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> Jamie. >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Foreman users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/foreman-users/W0bK-Ystni4/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Jamie. >

ehelms · April 14, 2015, 10:04pm

I'll try to shed some light on the process and idea. And of course, your
input, common workflows and ideas are welcome to help us evolve the project.

To get content into your Foreman/Katello, you first create a product to
house any number of related repositories. When this product is created, a
subscription for that product is also created that controls access to the
contents of the product. After you add some repositories to the product,
sync them down or upload content to them, all of the content is available
in the Library. If you stopped at this point your workflow would be to
register your hosts to Library that contains all of the products (and their
repositories) you have created. Now, if your content host had initial
access to all of these products, then your host would also see (via yum
repolist) all of the repositories. If you are managing a wide range of
products and repositories you could see how this might get out of hand.
instead, you pick and choose what products you want to attach your content
host to . The action of attaching the products makes the repositories
available to the content host.

Now, at this point you are just syncing and dumping content into Library
without any control over the content other than what products and
repositories the content host has access to - enter content views. They
allow you to take that un-managed content and derive meaningful
representations of it through repositories combinations, puppet modules,
and docker content. The filtering allows you to lock down and control what
exactly goes into the view and then produce an immutable 'view' of the
content in the Library. At this point, you can register your content host
to this content view and the process from there on looks the same. You
attach your content host to any number of the products via a subscription
that grants access to the products within the content view to grant your
content host access to the repositories therein.

For custom content this might seem a bit heavy handed when there aren't
multiple subscriptions that govern the same product, or subscriptions that
vary based upon the type of host being attached to. As I mentioned before,
your input and expectations are welcome to help us improve this for users.

Hope that helped some,
Eric

JC1 · April 15, 2015, 12:04pm

Thanks Eric, that's very useful.

On this topic, I'd like to register a content host using an activation key
and automatically pick-up the (centos) subscriptions (the key has been
given) in the process. To date I have either done the 'attach' from the
client or assigned subscriptions/products from the UI once a host has
registered.

I've
followed http://www.katello.org/docs/2.2/user_guide/activation_keys/index.html.
My key, under subscriptions -> list, shows my 'centos6' product and
'auto-attach' is set to 'yes'. Under Product Content, I see my two repos
marked as 'Enabled? Yes(default)' But my newly registering client tells me:

This system has no repositories available through subscriptions.

Back in the UI, an information message says 'When Auto Attach is enabled,
registering systems will be attached to all associated custom products and
only associated Red Hat subscriptions required to satisfy the system's
installed products.'

The client will still let me manually attach or update the subscriptions
from the UI, but auto-attachment feature would be preferable.

Anyone got any suggestions? Cheers.

···

On Tuesday, 14 April 2015 23:04:16 UTC+1, Eric Helms wrote: > > I'll try to shed some light on the process and idea. And of course, your > input, common workflows and ideas are welcome to help us evolve the project. > > To get content into your Foreman/Katello, you first create a product to > house any number of related repositories. When this product is created, a > subscription for that product is also created that controls access to the > contents of the product. After you add some repositories to the product, > sync them down or upload content to them, all of the content is available > in the Library. If you stopped at this point your workflow would be to > register your hosts to Library that contains all of the products (and their > repositories) you have created. Now, if your content host had initial > access to all of these products, then your host would also see (via yum > repolist) all of the repositories. If you are managing a wide range of > products and repositories you could see how this might get out of hand. > instead, you pick and choose what products you want to attach your content > host to . The action of attaching the products makes the repositories > available to the content host. > > Now, at this point you are just syncing and dumping content into Library > without any control over the content other than what products and > repositories the content host has access to - enter content views. They > allow you to take that un-managed content and derive meaningful > representations of it through repositories combinations, puppet modules, > and docker content. The filtering allows you to lock down and control what > exactly goes into the view and then produce an immutable 'view' of the > content in the Library. At this point, you can register your content host > to this content view and the process from there on looks the same. You > attach your content host to any number of the products via a subscription > that grants access to the products within the content view to grant your > content host access to the repositories therein. > > For custom content this might seem a bit heavy handed when there aren't > multiple subscriptions that govern the same product, or subscriptions that > vary based upon the type of host being attached to. As I mentioned before, > your input and expectations are welcome to help us improve this for users. > > > Hope that helped some, > Eric >

Danilo_Sousa · May 18, 2015, 7:04pm

I'm in the same situation that JC reported. Only way for a host to get any
repositories is to manually assign them on the 'Content Host' page.

The subscription-manager register ... shouldn't already create the
repositories from Activation Key? Or am I missing something in the workfow?

Cheers, guys!

···

On Wednesday, 15 April 2015 09:04:19 UTC-3, JC wrote: > > Thanks Eric, that's very useful. > > On this topic, I'd like to register a content host using an activation key > *and* automatically pick-up the (centos) subscriptions (the key has been > given) in the process. To date I have either done the 'attach' from the > client or assigned subscriptions/products from the UI once a host has > registered. > > I've followed > http://www.katello.org/docs/2.2/user_guide/activation_keys/index.html. > My key, under subscriptions -> list, shows my 'centos6' product and > 'auto-attach' is set to 'yes'. Under Product Content, I see my two repos > marked as 'Enabled? Yes(default)' But my newly registering client tells me: > > This system has no repositories available through subscriptions. > > Back in the UI, an information message says 'When Auto Attach is enabled, > registering systems will be attached to all associated custom products and > only associated Red Hat subscriptions required to satisfy the system's > installed products.' > > The client will still let me manually attach or update the subscriptions > from the UI, but auto-attachment feature would be preferable. > > Anyone got any suggestions? Cheers. > > On Tuesday, 14 April 2015 23:04:16 UTC+1, Eric Helms wrote: >> >> I'll try to shed some light on the process and idea. And of course, your >> input, common workflows and ideas are welcome to help us evolve the project. >> >> To get content into your Foreman/Katello, you first create a product to >> house any number of related repositories. When this product is created, a >> subscription for that product is also created that controls access to the >> contents of the product. After you add some repositories to the product, >> sync them down or upload content to them, all of the content is available >> in the Library. If you stopped at this point your workflow would be to >> register your hosts to Library that contains all of the products (and their >> repositories) you have created. Now, if your content host had initial >> access to all of these products, then your host would also see (via yum >> repolist) all of the repositories. If you are managing a wide range of >> products and repositories you could see how this might get out of hand. >> instead, you pick and choose what products you want to attach your content >> host to . The action of attaching the products makes the repositories >> available to the content host. >> >> Now, at this point you are just syncing and dumping content into Library >> without any control over the content other than what products and >> repositories the content host has access to - enter content views. They >> allow you to take that un-managed content and derive meaningful >> representations of it through repositories combinations, puppet modules, >> and docker content. The filtering allows you to lock down and control what >> exactly goes into the view and then produce an immutable 'view' of the >> content in the Library. At this point, you can register your content host >> to this content view and the process from there on looks the same. You >> attach your content host to any number of the products via a subscription >> that grants access to the products within the content view to grant your >> content host access to the repositories therein. >> >> For custom content this might seem a bit heavy handed when there aren't >> multiple subscriptions that govern the same product, or subscriptions that >> vary based upon the type of host being attached to. As I mentioned before, >> your input and expectations are welcome to help us improve this for users. >> >> >> Hope that helped some, >> Eric >> >

ehelms · May 18, 2015, 7:09pm

This sounds like you might be experiencing this issue
Bug #10208: Auto-attach subscriptions not working for content hosts with custom products only - Katello - Foreman . Does what the users describe
in the issue sound like the situations you are experiencing?

Eric

···

On Mon, May 18, 2015 at 3:04 PM, Danilo Sousa wrote:

I’m in the same situation that JC reported. Only way for a host to get any
repositories is to manually assign them on the ‘Content Host’ page.

The subscription-manager register ... shouldn’t already create the
repositories from Activation Key? Or am I missing something in the workfow?

Cheers, guys!

On Wednesday, 15 April 2015 09:04:19 UTC-3, JC wrote:

Thanks Eric, that’s very useful.

On this topic, I’d like to register a content host using an activation
key and automatically pick-up the (centos) subscriptions (the key has
been given) in the process. To date I have either done the ‘attach’ from
the client or assigned subscriptions/products from the UI once a host has
registered.

I’ve followed
http://www.katello.org/docs/2.2/user_guide/activation_keys/index.html.
My key, under subscriptions -> list, shows my ‘centos6’ product and
’auto-attach’ is set to ‘yes’. Under Product Content, I see my two repos
marked as ‘Enabled? Yes(default)’ But my newly registering client tells me:

This system has no repositories available through subscriptions.

Back in the UI, an information message says ‘When Auto Attach is
enabled, registering systems will be attached to all associated custom
products and only associated Red Hat subscriptions required to satisfy the
system’s installed products.’

The client will still let me manually attach or update the subscriptions
from the UI, but auto-attachment feature would be preferable.

Anyone got any suggestions? Cheers.

On Tuesday, 14 April 2015 23:04:16 UTC+1, Eric Helms wrote:

I’ll try to shed some light on the process and idea. And of course, your
input, common workflows and ideas are welcome to help us evolve the project.

To get content into your Foreman/Katello, you first create a product to
house any number of related repositories. When this product is created, a
subscription for that product is also created that controls access to the
contents of the product. After you add some repositories to the product,
sync them down or upload content to them, all of the content is available
in the Library. If you stopped at this point your workflow would be to
register your hosts to Library that contains all of the products (and their
repositories) you have created. Now, if your content host had initial
access to all of these products, then your host would also see (via yum
repolist) all of the repositories. If you are managing a wide range of
products and repositories you could see how this might get out of hand.
instead, you pick and choose what products you want to attach your content
host to . The action of attaching the products makes the repositories
available to the content host.

Now, at this point you are just syncing and dumping content into Library
without any control over the content other than what products and
repositories the content host has access to - enter content views. They
allow you to take that un-managed content and derive meaningful
representations of it through repositories combinations, puppet modules,
and docker content. The filtering allows you to lock down and control what
exactly goes into the view and then produce an immutable ‘view’ of the
content in the Library. At this point, you can register your content host
to this content view and the process from there on looks the same. You
attach your content host to any number of the products via a subscription
that grants access to the products within the content view to grant your
content host access to the repositories therein.

For custom content this might seem a bit heavy handed when there aren’t
multiple subscriptions that govern the same product, or subscriptions that
vary based upon the type of host being attached to. As I mentioned before,
your input and expectations are welcome to help us improve this for users.

Hope that helped some,
Eric

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Danilo_Sousa · May 18, 2015, 7:16pm

Eric,

this seems exactly the problem I'm facing.

Disabling auto-attach should allow all subscriptions to attach if you
need a workaround in the meantime.

Will try this suggestion later today.

Thank you, Eric.

Cheers

···

On Monday, 18 May 2015 16:09:25 UTC-3, Eric Helms wrote: > > This sounds like you might be experiencing this issue > http://projects.theforeman.org/issues/10208 . Does what the users > describe in the issue sound like the situations you are experiencing? > > > Eric > > On Mon, May 18, 2015 at 3:04 PM, Danilo Sousa > wrote: > >> I'm in the same situation that JC reported. Only way for a host to get >> any repositories is to manually assign them on the 'Content Host' page. >> >> The `subscription-manager register ...` shouldn't already create the >> repositories from Activation Key? Or am I missing something in the workfow? >> >> Cheers, guys! >> >> >> On Wednesday, 15 April 2015 09:04:19 UTC-3, JC wrote: >>> >>> Thanks Eric, that's very useful. >>> >>> On this topic, I'd like to register a content host using an activation >>> key *and* automatically pick-up the (centos) subscriptions (the key has >>> been given) in the process. To date I have either done the 'attach' from >>> the client or assigned subscriptions/products from the UI once a host has >>> registered. >>> >>> I've followed >>> http://www.katello.org/docs/2.2/user_guide/activation_keys/index.html. >>> My key, under subscriptions -> list, shows my 'centos6' product and >>> 'auto-attach' is set to 'yes'. Under Product Content, I see my two repos >>> marked as 'Enabled? Yes(default)' But my newly registering client tells me: >>> >>> This system has no repositories available through subscriptions. >>> >>> Back in the UI, an information message says 'When Auto Attach is >>> enabled, registering systems will be attached to all associated custom >>> products and only associated Red Hat subscriptions required to satisfy the >>> system's installed products.' >>> >>> The client will still let me manually attach or update the subscriptions >>> from the UI, but auto-attachment feature would be preferable. >>> >>> Anyone got any suggestions? Cheers. >>> >>> On Tuesday, 14 April 2015 23:04:16 UTC+1, Eric Helms wrote: >>>> >>>> I'll try to shed some light on the process and idea. And of course, >>>> your input, common workflows and ideas are welcome to help us evolve the >>>> project. >>>> >>>> To get content into your Foreman/Katello, you first create a product to >>>> house any number of related repositories. When this product is created, a >>>> subscription for that product is also created that controls access to the >>>> contents of the product. After you add some repositories to the product, >>>> sync them down or upload content to them, all of the content is available >>>> in the Library. If you stopped at this point your workflow would be to >>>> register your hosts to Library that contains all of the products (and their >>>> repositories) you have created. Now, if your content host had initial >>>> access to all of these products, then your host would also see (via yum >>>> repolist) all of the repositories. If you are managing a wide range of >>>> products and repositories you could see how this might get out of hand. >>>> instead, you pick and choose what products you want to attach your content >>>> host to . The action of attaching the products makes the repositories >>>> available to the content host. >>>> >>>> Now, at this point you are just syncing and dumping content into >>>> Library without any control over the content other than what products and >>>> repositories the content host has access to - enter content views. They >>>> allow you to take that un-managed content and derive meaningful >>>> representations of it through repositories combinations, puppet modules, >>>> and docker content. The filtering allows you to lock down and control what >>>> exactly goes into the view and then produce an immutable 'view' of the >>>> content in the Library. At this point, you can register your content host >>>> to this content view and the process from there on looks the same. You >>>> attach your content host to any number of the products via a subscription >>>> that grants access to the products within the content view to grant your >>>> content host access to the repositories therein. >>>> >>>> For custom content this might seem a bit heavy handed when there aren't >>>> multiple subscriptions that govern the same product, or subscriptions that >>>> vary based upon the type of host being attached to. As I mentioned before, >>>> your input and expectations are welcome to help us improve this for users. >>>> >>>> >>>> Hope that helped some, >>>> Eric >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > >

Nathan_Peters · June 1, 2015, 7:23pm

I am having a similar issue. My subscriptions are set to auto-attach.

I do not have any redhat products or subscriptions in my system, only
custom ones. Therefore I have no ability to define or use service levels.

I am using Fedora 20 as the client, CentOS7 as the Katello host.

I can attach a subscription manually through the web ui once a content host
is subscribed, but they will not auto-attach at subscription time even
though they are set to do that in their activation key settings.

This means that I have to run the entire installation and then manually
attach the subscription and then run yum updates on the system instead of
being able to have this all done by the end of the kickstart file.

···

On Monday, May 18, 2015 at 12:16:19 PM UTC-7, Danilo Sousa wrote: > > Eric, > > this seems exactly the problem I'm facing. > > Disabling auto-attach *should* allow all subscriptions to attach if you > need a workaround in the meantime. > > > Will try this suggestion later today. > > Thank you, Eric. > > Cheers > > On Monday, 18 May 2015 16:09:25 UTC-3, Eric Helms wrote: >> >> This sounds like you might be experiencing this issue >> http://projects.theforeman.org/issues/10208 . Does what the users >> describe in the issue sound like the situations you are experiencing? >> >> >> Eric >> >> On Mon, May 18, 2015 at 3:04 PM, Danilo Sousa >> wrote: >> >>> I'm in the same situation that JC reported. Only way for a host to get >>> any repositories is to manually assign them on the 'Content Host' page. >>> >>> The `subscription-manager register ...` shouldn't already create the >>> repositories from Activation Key? Or am I missing something in the workfow? >>> >>> Cheers, guys! >>> >>> >>> On Wednesday, 15 April 2015 09:04:19 UTC-3, JC wrote: >>>> >>>> Thanks Eric, that's very useful. >>>> >>>> On this topic, I'd like to register a content host using an activation >>>> key *and* automatically pick-up the (centos) subscriptions (the key >>>> has been given) in the process. To date I have either done the 'attach' >>>> from the client or assigned subscriptions/products from the UI once a host >>>> has registered. >>>> >>>> I've followed >>>> http://www.katello.org/docs/2.2/user_guide/activation_keys/index.html. >>>> My key, under subscriptions -> list, shows my 'centos6' product and >>>> 'auto-attach' is set to 'yes'. Under Product Content, I see my two repos >>>> marked as 'Enabled? Yes(default)' But my newly registering client tells me: >>>> >>>> This system has no repositories available through subscriptions. >>>> >>>> Back in the UI, an information message says 'When Auto Attach is >>>> enabled, registering systems will be attached to all associated custom >>>> products and only associated Red Hat subscriptions required to satisfy the >>>> system's installed products.' >>>> >>>> The client will still let me manually attach or update the >>>> subscriptions from the UI, but auto-attachment feature would be preferable. >>>> >>>> Anyone got any suggestions? Cheers. >>>> >>>> On Tuesday, 14 April 2015 23:04:16 UTC+1, Eric Helms wrote: >>>>> >>>>> I'll try to shed some light on the process and idea. And of course, >>>>> your input, common workflows and ideas are welcome to help us evolve the >>>>> project. >>>>> >>>>> To get content into your Foreman/Katello, you first create a product >>>>> to house any number of related repositories. When this product is created, >>>>> a subscription for that product is also created that controls access to the >>>>> contents of the product. After you add some repositories to the product, >>>>> sync them down or upload content to them, all of the content is available >>>>> in the Library. If you stopped at this point your workflow would be to >>>>> register your hosts to Library that contains all of the products (and their >>>>> repositories) you have created. Now, if your content host had initial >>>>> access to all of these products, then your host would also see (via yum >>>>> repolist) all of the repositories. If you are managing a wide range of >>>>> products and repositories you could see how this might get out of hand. >>>>> instead, you pick and choose what products you want to attach your content >>>>> host to . The action of attaching the products makes the repositories >>>>> available to the content host. >>>>> >>>>> Now, at this point you are just syncing and dumping content into >>>>> Library without any control over the content other than what products and >>>>> repositories the content host has access to - enter content views. They >>>>> allow you to take that un-managed content and derive meaningful >>>>> representations of it through repositories combinations, puppet modules, >>>>> and docker content. The filtering allows you to lock down and control what >>>>> exactly goes into the view and then produce an immutable 'view' of the >>>>> content in the Library. At this point, you can register your content host >>>>> to this content view and the process from there on looks the same. You >>>>> attach your content host to any number of the products via a subscription >>>>> that grants access to the products within the content view to grant your >>>>> content host access to the repositories therein. >>>>> >>>>> For custom content this might seem a bit heavy handed when there >>>>> aren't multiple subscriptions that govern the same product, or >>>>> subscriptions that vary based upon the type of host being attached to. As I >>>>> mentioned before, your input and expectations are welcome to help us >>>>> improve this for users. >>>>> >>>>> >>>>> Hope that helped some, >>>>> Eric >>>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Foreman users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to foreman-user...@googlegroups.com. >>> To post to this group, send email to forema...@googlegroups.com. >>> Visit this group at http://groups.google.com/group/foreman-users. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >>

Nathan_Peters · June 24, 2015, 5:55pm

I'm still looking for an answer on this question. I would like to not have
to go back after the installation and manually attach the subscription.

Is this a confirmed bug and if so, is there a target release for the fix?

···

On Monday, June 1, 2015 at 12:23:25 PM UTC-7, Nathan Peters wrote: > > I am having a similar issue. My subscriptions are set to auto-attach. > > I do not have any redhat products or subscriptions in my system, only > custom ones. Therefore I have no ability to define or use service levels. > > I am using Fedora 20 as the client, CentOS7 as the Katello host. > > I can attach a subscription manually through the web ui once a content > host is subscribed, but they will not auto-attach at subscription time even > though they are set to do that in their activation key settings. > > This means that I have to run the entire installation and then manually > attach the subscription and then run yum updates on the system instead of > being able to have this all done by the end of the kickstart file. > > On Monday, May 18, 2015 at 12:16:19 PM UTC-7, Danilo Sousa wrote: >> >> Eric, >> >> this seems exactly the problem I'm facing. >> >> Disabling auto-attach *should* allow all subscriptions to attach if you >> need a workaround in the meantime. >> >> >> Will try this suggestion later today. >> >> Thank you, Eric. >> >> Cheers >> >> On Monday, 18 May 2015 16:09:25 UTC-3, Eric Helms wrote: >>> >>> This sounds like you might be experiencing this issue >>> http://projects.theforeman.org/issues/10208 . Does what the users >>> describe in the issue sound like the situations you are experiencing? >>> >>> >>> Eric >>> >>> On Mon, May 18, 2015 at 3:04 PM, Danilo Sousa >>> wrote: >>> >>>> I'm in the same situation that JC reported. Only way for a host to get >>>> any repositories is to manually assign them on the 'Content Host' page. >>>> >>>> The `subscription-manager register ...` shouldn't already create the >>>> repositories from Activation Key? Or am I missing something in the workfow? >>>> >>>> Cheers, guys! >>>> >>>> >>>> On Wednesday, 15 April 2015 09:04:19 UTC-3, JC wrote: >>>>> >>>>> Thanks Eric, that's very useful. >>>>> >>>>> On this topic, I'd like to register a content host using an activation >>>>> key *and* automatically pick-up the (centos) subscriptions (the key >>>>> has been given) in the process. To date I have either done the 'attach' >>>>> from the client or assigned subscriptions/products from the UI once a host >>>>> has registered. >>>>> >>>>> I've followed >>>>> http://www.katello.org/docs/2.2/user_guide/activation_keys/index.html. >>>>> My key, under subscriptions -> list, shows my 'centos6' product and >>>>> 'auto-attach' is set to 'yes'. Under Product Content, I see my two repos >>>>> marked as 'Enabled? Yes(default)' But my newly registering client tells me: >>>>> >>>>> This system has no repositories available through subscriptions. >>>>> >>>>> Back in the UI, an information message says 'When Auto Attach is >>>>> enabled, registering systems will be attached to all associated custom >>>>> products and only associated Red Hat subscriptions required to satisfy the >>>>> system's installed products.' >>>>> >>>>> The client will still let me manually attach or update the >>>>> subscriptions from the UI, but auto-attachment feature would be preferable. >>>>> >>>>> Anyone got any suggestions? Cheers. >>>>> >>>>> On Tuesday, 14 April 2015 23:04:16 UTC+1, Eric Helms wrote: >>>>>> >>>>>> I'll try to shed some light on the process and idea. And of course, >>>>>> your input, common workflows and ideas are welcome to help us evolve the >>>>>> project. >>>>>> >>>>>> To get content into your Foreman/Katello, you first create a product >>>>>> to house any number of related repositories. When this product is created, >>>>>> a subscription for that product is also created that controls access to the >>>>>> contents of the product. After you add some repositories to the product, >>>>>> sync them down or upload content to them, all of the content is available >>>>>> in the Library. If you stopped at this point your workflow would be to >>>>>> register your hosts to Library that contains all of the products (and their >>>>>> repositories) you have created. Now, if your content host had initial >>>>>> access to all of these products, then your host would also see (via yum >>>>>> repolist) all of the repositories. If you are managing a wide range of >>>>>> products and repositories you could see how this might get out of hand. >>>>>> instead, you pick and choose what products you want to attach your content >>>>>> host to . The action of attaching the products makes the repositories >>>>>> available to the content host. >>>>>> >>>>>> Now, at this point you are just syncing and dumping content into >>>>>> Library without any control over the content other than what products and >>>>>> repositories the content host has access to - enter content views. They >>>>>> allow you to take that un-managed content and derive meaningful >>>>>> representations of it through repositories combinations, puppet modules, >>>>>> and docker content. The filtering allows you to lock down and control what >>>>>> exactly goes into the view and then produce an immutable 'view' of the >>>>>> content in the Library. At this point, you can register your content host >>>>>> to this content view and the process from there on looks the same. You >>>>>> attach your content host to any number of the products via a subscription >>>>>> that grants access to the products within the content view to grant your >>>>>> content host access to the repositories therein. >>>>>> >>>>>> For custom content this might seem a bit heavy handed when there >>>>>> aren't multiple subscriptions that govern the same product, or >>>>>> subscriptions that vary based upon the type of host being attached to. As I >>>>>> mentioned before, your input and expectations are welcome to help us >>>>>> improve this for users. >>>>>> >>>>>> >>>>>> Hope that helped some, >>>>>> Eric >>>>>> >>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Foreman users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to foreman-user...@googlegroups.com. >>>> To post to this group, send email to forema...@googlegroups.com. >>>> Visit this group at http://groups.google.com/group/foreman-users. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>>

ehelms · June 29, 2015, 4:01pm

We've had trouble reproducing this given the issue I posted previously. I
will prioritize revisiting the issue for a potential 2.2.3 release.

···

On Wed, Jun 24, 2015 at 1:55 PM, Nathan Peters wrote:

I’m still looking for an answer on this question. I would like to not
have to go back after the installation and manually attach the subscription.

Is this a confirmed bug and if so, is there a target release for the fix?

On Monday, June 1, 2015 at 12:23:25 PM UTC-7, Nathan Peters wrote:

I am having a similar issue. My subscriptions are set to auto-attach.

I do not have any redhat products or subscriptions in my system, only
custom ones. Therefore I have no ability to define or use service levels.

I am using Fedora 20 as the client, CentOS7 as the Katello host.

I can attach a subscription manually through the web ui once a content
host is subscribed, but they will not auto-attach at subscription time even
though they are set to do that in their activation key settings.

This means that I have to run the entire installation and then manually
attach the subscription and then run yum updates on the system instead of
being able to have this all done by the end of the kickstart file.

On Monday, May 18, 2015 at 12:16:19 PM UTC-7, Danilo Sousa wrote:

Eric,

this seems exactly the problem I’m facing.

Disabling auto-attach should allow all subscriptions to attach if you
need a workaround in the meantime.

Will try this suggestion later today.

Thank you, Eric.

Cheers

On Monday, 18 May 2015 16:09:25 UTC-3, Eric Helms wrote:

This sounds like you might be experiencing this issue
Bug #10208: Auto-attach subscriptions not working for content hosts with custom products only - Katello - Foreman . Does what the users
describe in the issue sound like the situations you are experiencing?

Eric

On Mon, May 18, 2015 at 3:04 PM, Danilo Sousa danilo...@gmail.com >>>> wrote:

I’m in the same situation that JC reported. Only way for a host to get
any repositories is to manually assign them on the ‘Content Host’ page.

The subscription-manager register ... shouldn’t already create the
repositories from Activation Key? Or am I missing something in the workfow?

Cheers, guys!

On Wednesday, 15 April 2015 09:04:19 UTC-3, JC wrote:

Thanks Eric, that’s very useful.

On this topic, I’d like to register a content host using an
activation key and automatically pick-up the (centos)
subscriptions (the key has been given) in the process. To date I have
either done the ‘attach’ from the client or assigned subscriptions/products
from the UI once a host has registered.

I’ve followed
http://www.katello.org/docs/2.2/user_guide/activation_keys/index.html.
My key, under subscriptions -> list, shows my ‘centos6’ product and
’auto-attach’ is set to ‘yes’. Under Product Content, I see my two repos
marked as ‘Enabled? Yes(default)’ But my newly registering client tells me:

This system has no repositories available through subscriptions.

Back in the UI, an information message says ‘When Auto Attach is
enabled, registering systems will be attached to all associated custom
products and only associated Red Hat subscriptions required to satisfy the
system’s installed products.’

The client will still let me manually attach or update the
subscriptions from the UI, but auto-attachment feature would be preferable.

Anyone got any suggestions? Cheers.

On Tuesday, 14 April 2015 23:04:16 UTC+1, Eric Helms wrote:

I’ll try to shed some light on the process and idea. And of course,
your input, common workflows and ideas are welcome to help us evolve the
project.

To get content into your Foreman/Katello, you first create a product
to house any number of related repositories. When this product is created,
a subscription for that product is also created that controls access to the
contents of the product. After you add some repositories to the product,
sync them down or upload content to them, all of the content is available
in the Library. If you stopped at this point your workflow would be to
register your hosts to Library that contains all of the products (and their
repositories) you have created. Now, if your content host had initial
access to all of these products, then your host would also see (via yum
repolist) all of the repositories. If you are managing a wide range of
products and repositories you could see how this might get out of hand.
instead, you pick and choose what products you want to attach your content
host to . The action of attaching the products makes the repositories
available to the content host.

Now, at this point you are just syncing and dumping content into
Library without any control over the content other than what products and
repositories the content host has access to - enter content views. They
allow you to take that un-managed content and derive meaningful
representations of it through repositories combinations, puppet modules,
and docker content. The filtering allows you to lock down and control what
exactly goes into the view and then produce an immutable ‘view’ of the
content in the Library. At this point, you can register your content host
to this content view and the process from there on looks the same. You
attach your content host to any number of the products via a subscription
that grants access to the products within the content view to grant your
content host access to the repositories therein.

For custom content this might seem a bit heavy handed when there
aren’t multiple subscriptions that govern the same product, or
subscriptions that vary based upon the type of host being attached to. As I
mentioned before, your input and expectations are welcome to help us
improve this for users.

Hope that helped some,
Eric

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

[Katello 2.2] - how to setup a client for content

Transaction Summary

*Netbulae Virtualization Experts *

Tel: 053 20 30 270 in...@netbulae.eu <javascript:> Staalsteden 4-3A KvK 08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01

Netbulae Virtualization Experts

Tel: 053 20 30 270 in...@netbulae.eu <javascript:> Staalsteden 4-3A KvK
08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW
NL821234584B01