[foreman-users] Re: katello update to version 3.5 failed

['Denis Müller' via Foreman users]

this post solves the problem:
https://groups.google.com/forum/#!searchin/foreman-users/db$20migrate|sort:date/foreman-users/bWfJJ-xyzGE/xz2M6VmHBQAJ

Maybe for anyone who has the same issue.

Am Montag, 18. Dezember 2017 16:40:25 UTC+1 schrieb Denis Müller:
>
> Maybe somebody can help:
>
> [root@theforeman ~]# foreman-installer --scenario katello --upgrade 
> --verbose 
> [ INFO 2017-12-18 16:37:05 verbose] Executing hooks in group 
> pre_migrations
> [ INFO 2017-12-18 16:37:05 verbose] All hooks in group pre_migrations 
> finished
> [ INFO 2017-12-18 16:37:05 verbose] Executing hooks in group boot
> [ INFO 2017-12-18 16:37:05 verbose] All hooks in group boot finished
> [ INFO 2017-12-18 16:37:05 verbose] Executing hooks in group init
> [ INFO 2017-12-18 16:37:05 verbose] All hooks in group init finished
> [ INFO 2017-12-18 16:37:05 verbose] Loading default values from puppet 
> modules...
> [ INFO 2017-12-18 16:37:05 verbose] ... finished
> [ INFO 2017-12-18 16:37:05 verbose] Executing hooks in group pre_values
> [ INFO 2017-12-18 16:37:05 verbose] All hooks in group pre_values finished
> [ INFO 2017-12-18 16:37:05 verbose] Running installer with args [[
> "--scenario", "katello", "--upgrade", "--verbose"]]
> [ INFO 2017-12-18 16:37:05 verbose] Executing hooks in group 
> pre_validations
> [ INFO 2017-12-18 16:37:05 verbose] All hooks in group pre_validations 
> finished
> [ INFO 2017-12-18 16:37:05 verbose] Running validation checks
> [ INFO 2017-12-18 16:37:05 verbose] Executing hooks in group pre_commit
> [ INFO 2017-12-18 16:37:05 verbose] All hooks in group pre_commit finished
> [ INFO 2017-12-18 16:37:05 verbose] Executing hooks in group pre
> Upgrading, to monitor the progress on all related services, please do:
> [ INFO 2017-12-18 16:37:05 verbose] Upgrading, to monitor the progress on 
> all related services, please do:
>   foreman-tail | tee upgrade-$(date +%Y-%m-%d-%H%M).log
> [ INFO 2017-12-18 16:37:05 verbose]   foreman-tail | tee upgrade-$(date +%
> Y-%m-%d-%H%M).log
> Upgrade Step: stop_services...
> [ INFO 2017-12-18 16:37:08 verbose] Upgrade Step: stop_services...
> /usr/sbin/service-wait goferd stop
>
> /usr/sbin/service-wait foreman-tasks stop
>
> /usr/sbin/service-wait puppetserver stop
>
> /usr/sbin/service-wait httpd stop
>
> /usr/sbin/service-wait pulp_celerybeat stop
>
> /usr/sbin/service-wait foreman-proxy stop
>
> /usr/sbin/service-wait pulp_streamer stop
>
> /usr/sbin/service-wait pulp_resource_manager stop
>
> /usr/sbin/service-wait smart_proxy_dynflow_core stop
>
> /usr/sbin/service-wait pulp_workers stop
>
> /usr/sbin/service-wait tomcat stop
>
> /usr/sbin/service-wait squid stop
>
> /usr/sbin/service-wait qdrouterd stop
>
> /usr/sbin/service-wait qpidd stop
>
> Success!
> katello-service stop --exclude mongod,postgresql finished successfully!
> Upgrade Step: start_databases...
> [ INFO 2017-12-18 16:37:48 verbose] Upgrade Step: start_databases...
> /usr/sbin/service-wait mongod start
>
> /usr/sbin/service-wait postgresql start
>
> Success!
> katello-service start --only mongod,postgresql finished successfully!
> Upgrade Step: update_http_conf...
> [ INFO 2017-12-18 16:37:59 verbose] Upgrade Step: update_http_conf...
> grep -F -q 'Include "/etc/httpd/conf.modules.d/*.conf"' /etc/httpd/conf/
> httpd.conf ||echo -e '= 2.4> 
> Include "/etc/httpd/conf.modules.d/*.conf"
> '>> /etc/httpd/conf/httpd.conf 
> finished successfully!
> Upgrade Step: migrate_pulp...
> [ INFO 2017-12-18 16:37:59 verbose] Upgrade Step: migrate_pulp...
> grep -qe '7.[[:digit:]]' /etc/redhat-release finished successfully!
> sed -i -e 's?/var/run/mongodb/mongodb.pid?/var/run/mongodb/mongod.pid?g' /
> etc/mongod.conf finished successfully!
> 22298
> pgrep mongod finished successfully!
> Attempting to connect to localhost:27017
> Attempting to connect to localhost:27017
> Write concern for Mongo connection: {}
> Loading content types.
> Loading type descriptors []
> Parsing type descriptors
> Validating type descriptor syntactic integrity
> Validating type descriptor semantic integrity
> Loading unit model: puppet_module = pulp_puppet.plugins.db.models:Module
> Loading unit model: ostree = pulp_ostree.plugins.db.model:Branch
> Loading unit model: docker_blob = pulp_docker.plugins.models:Blob
> Loading unit model: docker_manifest = pulp_docker.plugins.models:Manifest
> Loading unit model: docker_image = pulp_docker.plugins.models:Image
> Loading unit model: docker_tag = pulp_docker.plugins.models:Tag
> Loading unit model: erratum = pulp_rpm.plugins.db.models:Errata
> Loading unit model: distribution = pulp_rpm.plugins.db.models:Distribution
> Loading unit model: srpm = pulp_rpm.plugins.db.models:SRPM
> Loading unit model: package_group = pulp_rpm.plugins.db.models:
> PackageGroup
> Loading unit model: package_category = pulp_rpm.plugins.db.models:
> PackageCategory
> Loading unit model: iso = pulp_rpm.plugins.db.models:ISO
> Loading unit model: 

[foreman-users] Re: Foreman 1.16.0 released

['Denis Müller' via Foreman users]

we have upgrade issues while updating from katello 3.4.5 while yum update:

--> Abhängigkeit tfm-rubygem(rest-client) < 2.0.0 wird für Paket tfm-rubygem
-runcible-1.12.0-1.el7.noarch verarbeitet
---> Paket tfm-rubygem-rest-client.noarch 0:2.0.1-1.el7 markiert, um eine 
Aktualisierung zu werden
---> Paket tfm-runtime.x86_64 0:3.2-9.el7 markiert, um aktualisiert zu 
werden
---> Paket tfm-runtime.x86_64 0:3.2-10.el7 markiert, um eine Aktualisierung 
zu werden
--> Transaktionsprüfung wird ausgeführt
---> Paket rubygem-rsec.noarch 0:0.4.2-1.el7 markiert, um installiert zu 
werden
---> Paket tfm-rubygem-bastion.noarch 0:5.1.1-1.fm1_15.el7 markiert, um 
aktualisiert zu werden
--> Abhängigkeit tfm-rubygem(bastion) < 6.0.0 wird für Paket tfm-rubygem-
katello-3.4.5-1.el7.noarch verarbeitet
---> Paket tfm-rubygem-fog-digitalocean.noarch 0:0.3.0-1.el7 markiert, um 
installiert zu werden
---> Paket tfm-rubygem-rest-client.noarch 0:1.8.0-1.el7 markiert, um 
aktualisiert zu werden
--> Abhängigkeit tfm-rubygem(rest-client) < 2.0.0 wird für Paket tfm-rubygem
-runcible-1.12.0-1.el7.noarch verarbeitet
---> Paket tfm-rubygem-sprockets-rails.noarch 0:3.2.0-1.el7 markiert, um 
installiert zu werden
--> Abhängigkeitsauflösung beendet
Fehler: Paket: tfm-rubygem-katello-3.4.5-1.el7.noarch (@katello)
Benötigt: tfm-rubygem(bastion) < 6.0.0
Entfernen: tfm-rubygem-bastion-5.1.1-1.fm1_15.el7.noarch (
@foreman-plugins)
tfm-rubygem(bastion) = 5.1.1
Aktualisiert durch: tfm-rubygem-bastion-6.1.5-
1.fm1_16.el7.noarch (foreman-plugins)
tfm-rubygem(bastion) = 6.1.5
Verfügbar: tfm-rubygem-bastion-5.0.0-1.fm1_15.el7.noarch (
foreman-plugins)
tfm-rubygem(bastion) = 5.0.0
Verfügbar: tfm-rubygem-bastion-5.0.10-1.fm1_16.el7.noarch (
foreman-plugins)
tfm-rubygem(bastion) = 5.0.10
Verfügbar: tfm-rubygem-bastion-6.0.0-1.fm1_16.el7.noarch (
foreman-plugins)
tfm-rubygem(bastion) = 6.0.0
Fehler: Paket: tfm-rubygem-runcible-1.12.0-1.el7.noarch (@katello)
Benötigt: tfm-rubygem(rest-client) < 2.0.0
Entfernen: tfm-rubygem-rest-client-1.8.0-1.el7.noarch (@foreman)
tfm-rubygem(rest-client) = 1.8.0
Aktualisiert durch: tfm-rubygem-rest-client-2.0.1-1.el7.noarch (
foreman)
tfm-rubygem(rest-client) = 2.0.1
 Sie können versuchen, mit --skip-broken das Problem zu umgehen.
 Sie könnten Folgendes versuchen: rpm -Va --nofiles --nodigest
Uploading Enabled Repositories Report



Am Donnerstag, 30. November 2017 13:51:49 UTC+1 schrieb Daniel Lobato:
>
> Foreman 1.16.0 is now available, the latest major release containing 
> improvements on VMWare, Netgroups LDAP authentication, OpenStack v3 
> support, Puppet 5 support, among many other bugfixes and features. 
>
> Thanks to all contributors to this release, who helped write, fix and 
> translate it, and to the testers who've helped during the release 
> candidate phase. 
>
> Installation quick start: 
> https://theforeman.org/manuals/1.16/quickstart_guide.html 
>
> Upgrade instructions: 
> https://theforeman.org/manuals/1.16/index.html#3.6Upgrade 
>
> Release notes: 
> https://theforeman.org/manuals/1.16/index.html#Releasenotesfor1.16 
>
> Changes in this release 
> === 
> This release contains many varied changes, including: 
>
> - Thin host API 
> - OpenStack v3 
> - Puppet 5 support 
> - VMWare SCSI controllers with per-disk configuration 
> - Plugin role locking 
> - Netgroups LDAP authentication 
>
> Notice many users encountered a problem in 1.16.0 RC2 adding 
> ActiveDirectory 
> authentication sources. This is now fixed and they work fine as always. 
>
> Many other noticeable improvements can be found on the website release 
> notes, 
> https://theforeman.org/manuals/1.16/index.html#Releasenotesfor1.16 
> A full list of all issues fixed in the Foreman project is available in 
> our issue tracker 
> http://projects.theforeman.org/projects/foreman/issues?query_id=129 
>
> Two security issues have also been fixed in this release: 
>
> - CVE-2017-7535: Stored XSS in the manage organizations page 
> - CVE-2017-15100: Stored XSS in fact name or value 
>
> Lastly, do take note of the upgrade warnings and deprecations in this 
> release (right now empty, it will be updated with anything we find): 
> https://theforeman.org/manuals/1.16/index.html#Upgradewarnings 
>
> Downloads 
> = 
> Packages may be found in the 1.16 directories on both deb.foreman.org 
> and yum.theforeman.org, and tarballs are on downloads.theforeman.org. 
>
> The GPG key used for RPMs and tarballs has the following fingerprint: 
>   41EE 8815 A84C ACA4 A583 5055 9C21 BCB2 8977 40E9 
>   (https://theforeman.org/security.html#GPGkeys) 
>
> Bug reporting 
> = 
> If you come across a bug, please file it and note the 
> version of Foreman that you're using in the report. 
>
> Foreman: 

Re: [foreman-users] Re: Katello 3.4.5 Released

['Denis Müller' via Foreman users]

Thanks

Am Mittwoch, 30. August 2017 15:30:03 UTC+2 schrieb Eric Helms:
>
> Sorry I missed that package in my quick test that packages were all 
> signed. This should be fixed now.
>
> On Wed, Aug 30, 2017 at 2:25 AM, 'Denis Müller' via Foreman users <
> forema...@googlegroups.com > wrote:
>
>> I'm getting an error during "yum update":
>>
>> *Paket 
>> tfm-rubygem-foreman_virt_who_configure-0.1.5-1.fm1_15.el7.noarch.rpm ist 
>> nicht unterschrieben*
>>
>> Package is not signed.
>>
>> Am Mittwoch, 30. August 2017 03:17:54 UTC+2 schrieb Eric Helms:
>>>
>>> We are happy to announce the GA of Katello 3.4.5. This release contains 
>>> a large number of bug fixes for both small UI issues, user issues found 
>>> while using 3.4.4 and developer found issues that we felt would bring more 
>>> stability to users. There are some known Puppet 4 upgrade issues also 
>>> included as part of this release.
>>>
>>> The highlights are too numerous to outline here, so I would recommend to 
>>> please look at the changelog for a full list of changes:
>>>
>>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md  
>>>
>>> Installation:
>>> https://theforeman.org/plugins/katello/3.4/installation/index.html
>>>
>>> When upgrading from 3.4.4 or any prior version please follow these 
>>> instructions:
>>> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>>>
>>>
>>> Bug reporting
>>> =
>>> If you come across a bug in your testing, please file it and note the
>>> version of Katello or Foreman that you're using in the report.
>>>
>>> http://projects.theforeman.org/projects/katello/issues/new
>>>
>> -- 
>> 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 https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Eric D. Helms
> Red Hat Engineering
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Katello 3.4.5 Released

['Denis Müller' via Foreman users]

I'm getting an error during "yum update":

*Paket tfm-rubygem-foreman_virt_who_configure-0.1.5-1.fm1_15.el7.noarch.rpm 
ist nicht unterschrieben*

Package is not signed.

Am Mittwoch, 30. August 2017 03:17:54 UTC+2 schrieb Eric Helms:
>
> We are happy to announce the GA of Katello 3.4.5. This release contains a 
> large number of bug fixes for both small UI issues, user issues found while 
> using 3.4.4 and developer found issues that we felt would bring more 
> stability to users. There are some known Puppet 4 upgrade issues also 
> included as part of this release.
>
> The highlights are too numerous to outline here, so I would recommend to 
> please look at the changelog for a full list of changes:
>
> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md  
>
> Installation:
> https://theforeman.org/plugins/katello/3.4/installation/index.html
>
> When upgrading from 3.4.4 or any prior version please follow these 
> instructions:
> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>
>
> Bug reporting
> =
> If you come across a bug in your testing, please file it and note the
> version of Katello or Foreman that you're using in the report.
>
> http://projects.theforeman.org/projects/katello/issues/new
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Failing package is: gofer-2.7.6-1.el7.noarch (on katello agent install)

['Denis Müller' via Foreman users]

I'm having the same issue with no mathing gpg keys...

Am Donnerstag, 24. August 2017 16:44:05 UTC+2 schrieb Jorick Astrego:
>
> Hi,
>
> Trying to install with katello 3.4 client repository. But the katello 
> agent installation fails with "Failing package is: 
> gofer-2.7.6-1.el7.noarch" due to a gpg mismatch.
>
> The GPG keys listed for the "katello 3.4 client el7 x86_64" repository are 
> already installed but they are not correct for this package.
> Check that the correct key URLs are configured for this repository.
>
> The repo I have configured is 
> "https://fedorapeople.org/groups/katello/releases/yum/3.4/client/el7/x86_64/; 
>  
> with the Katello gpg key, internet repo's are disabled.
>
>
>
>
>
>
> Met vriendelijke groet, With kind regards,
>
> Jorick Astrego
>
> *Netbulae Virtualization Experts *
> --
> Tel: 053 20 30 270 in...@netbulae.eu  Staalsteden 4-3A KvK 
> 08198180
> Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01
> --
>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] subscription expected behaviour?

['Denis Müller' via Foreman users]

Hi,

do we always need to "reregister" the machine if we provide new content 
like a new repo in a content-view or new Product to activation key?

I thought the command "subscription-manager refresh" would tell the machine 
to get the new content, but fotunately noi have to reregister the 
machine all the time.

Or maybe i'm doing something wrong?

I would appreciate any advice.

Greets,
Denis

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Katello 3.4.4 Released

['Denis Müller' via Foreman users]

Hello and thank you for the release. But after i did the update to the 
latest version, i can't see and access any repos anymore. I can see the 
product but no repos.

Am Mittwoch, 2. August 2017 17:51:15 UTC+2 schrieb Eric Helms:
>
> We are happy to announce the GA of Katello 3.4.4. This release contains a 
> large number of bug fixes for both small UI issues, user issues found while 
> using 3.4.4 and developer found issues that we felt would bring more 
> stability to users.
>
> The highlights are too numerous to outline here, so I would recommend to 
> please look at the changelog for a full list of changes:
>
> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md  
>
> Installation:
> https://theforeman.org/plugins/katello/3.4/installation/index.html
>
> Upgrade:
> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>
>
> Bug reporting
> =
> If you come across a bug in your testing, please file it and note the
> version of Katello or Foreman that you're using in the report.
>
> http://projects.theforeman.org/projects/katello/issues/new
>
> -- 
> Eric D. Helms
> Red Hat Engineering
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] How to install puppet-agent in version 4

['Denis Müller' via Foreman users]

It worked, thank you

Am Donnerstag, 20. Juli 2017 17:57:10 UTC+2 schrieb Baptiste Agasse:
>
> Hi,
>
> - Le 20 Juil 17, à 14:09, foreman-users  > a écrit :
>
> In Katello, puppet.conf - Provisioning Template there is a variable 
> "enable-puppetlabs-pc1-repo". If it goes true, it will install puppet 4, 
> but where can i switch this variable to be true? 
> We are providing repos over Katello.
>
>
> You can set this variable to true at different level, in global variable 
> if all your hosts have this variable set to true, or at Org/location 
> hostgroup or directly in the host.
> If you provide the puppet 4 repo via katello, you have to use the 
> 'enable-puppet4' variable instead of 'enable-puppetlabs-pc1-repo'.
> There is a little bug in the puppet.conf template because it set the good 
> configuration path only if you enable 'enable-puppetlabs-pc1-repo' and not 
> when you set ' enable-puppet4' (which only setup puppet4 and not the repos)
> The fix is simple:
>
> @@ -5,9 +5,9 @@
>  <%
>os_family = @host.operatingsystem.family
>os_name   = @host.operatingsystem.name
>  
> -  if @host.param_true?('enable-puppetlabs-pc1-repo') && (os_family == 
> 'Debian' || os_family == 'Redhat' || os_name == 'SLES')
> +  if (@host.param_true?('enable-puppetlabs-pc1-repo') || 
> @host.param_true?('enable-puppet4')) && (os_family == 'Debian' || os_family 
> == 'Redhat' || os_name == 'SLES')
>  var_dir = '/opt/puppetlabs/puppet/cache'
>  log_dir = '/var/log/puppetlabs/puppet'
>  run_dir = '/var/run/puppetlabs'
>  ssl_dir = '/etc/puppetlabs/puppet/ssl'
>
> I will provide the fix on the comunity_template repo for this.
>
> Have a nice day.
>
> Cheers.
>
>
> -- 
> 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 https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
>
> -- 
> Baptiste AGASSE
> Lyra Network France, Senior GNU/Linux engineer
> 109 Rue de l'innovation, 31670 Labège - France
> Phone: (+33)5.67.22.31.87
> Fax: (+33)5.67.22.31.61
> Website: http://www.lyra-network.com
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] How to install puppet-agent in version 4

['Denis Müller' via Foreman users]

Hey,

thank you for the hint. I will try this out.


Am Donnerstag, 20. Juli 2017 17:57:10 UTC+2 schrieb Baptiste Agasse:
>
> Hi,
>
> - Le 20 Juil 17, à 14:09, foreman-users  > a écrit :
>
> In Katello, puppet.conf - Provisioning Template there is a variable 
> "enable-puppetlabs-pc1-repo". If it goes true, it will install puppet 4, 
> but where can i switch this variable to be true? 
> We are providing repos over Katello.
>
>
> You can set this variable to true at different level, in global variable 
> if all your hosts have this variable set to true, or at Org/location 
> hostgroup or directly in the host.
> If you provide the puppet 4 repo via katello, you have to use the 
> 'enable-puppet4' variable instead of 'enable-puppetlabs-pc1-repo'.
> There is a little bug in the puppet.conf template because it set the good 
> configuration path only if you enable 'enable-puppetlabs-pc1-repo' and not 
> when you set ' enable-puppet4' (which only setup puppet4 and not the repos)
> The fix is simple:
>
> @@ -5,9 +5,9 @@
>  <%
>os_family = @host.operatingsystem.family
>os_name   = @host.operatingsystem.name
>  
> -  if @host.param_true?('enable-puppetlabs-pc1-repo') && (os_family == 
> 'Debian' || os_family == 'Redhat' || os_name == 'SLES')
> +  if (@host.param_true?('enable-puppetlabs-pc1-repo') || 
> @host.param_true?('enable-puppet4')) && (os_family == 'Debian' || os_family 
> == 'Redhat' || os_name == 'SLES')
>  var_dir = '/opt/puppetlabs/puppet/cache'
>  log_dir = '/var/log/puppetlabs/puppet'
>  run_dir = '/var/run/puppetlabs'
>  ssl_dir = '/etc/puppetlabs/puppet/ssl'
>
> I will provide the fix on the comunity_template repo for this.
>
> Have a nice day.
>
> Cheers.
>
>
> -- 
> 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 https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
>
> -- 
> Baptiste AGASSE
> Lyra Network France, Senior GNU/Linux engineer
> 109 Rue de l'innovation, 31670 Labège - France
> Phone: (+33)5.67.22.31.87
> Fax: (+33)5.67.22.31.61
> Website: http://www.lyra-network.com
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] How to install puppet-agent in version 4

['Denis Müller' via Foreman users]

In Katello, puppet.conf - Provisioning Template there is a variable 
"enable-puppetlabs-pc1-repo". If it goes true, it will install puppet 4, 
but where can i switch this variable to be true? 
We are providing repos over Katello.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Install loop after upgrade to 3.4

['Denis Müller' via Foreman users]

as a stupid workaround, after host was built, i'm shutting it down, set 
first boot device to hdd and cancel build in foreman.

Am Donnerstag, 1. Juni 2017 12:04:39 UTC+2 schrieb Nuno Marques:
>
> What I'm doing right now is: a few minutes after the host starts 
> installing I cancel the build. The host finishes the installation and 
> doesn't start another.
>
> On 01-06-2017 09:47, Denis Müller wrote:
>
> I have the same issue, no solutions yet...
>
> Am Mittwoch, 31. Mai 2017 11:09:56 UTC+2 schrieb Nuno Marques: 
>>
>> Hi all, 
>>
>> I've just upgraded katello 3.2 to 3.4. 
>> Now when I create a new Host on VMWare using a bootdisk, it enters a 
>> loop, when the host reboots the installation starts all over again. 
>>
>> Should I roll back the update or there's something I could fix? 
>>
>> Thanks! 
>>
>> -- 
>> nuno 
>>
>>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: nsupdate on foreman-proxy doesn't work anymore

['Denis Müller' via Foreman users]

deleting foreman-proxy-files in /tmp folder did help.

Am Mittwoch, 26. April 2017 13:40:25 UTC+2 schrieb Denis Müller:
>
> Hello guys,
>
> since i justed updated and restart foreman-proxy on a centos 6 machine, i 
> can't assign new ip addresses anymore. Foreman-proxy debug shows me:
>
> *trying to find an ip address, we got {:to=>nil, :from=>nil}*
>
> Configuration didn't change. I restarted foreman-proxy and dhcpd couple of 
> times but no luck. What is wrong with that ?
>
>
> *foreman-proxy-1.12.4-1.el6.noarch*
>
> *and we have foreman-server in version 1.14.3*
>
> Can somebody help me?
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: nsupdate on foreman-proxy doesn't work anymore

['Denis Müller' via Foreman users]

*D, [2017-04-26T13:35:10.049838 #24049] DEBUG -- : Added a reservation: 
**D, [2017-04-26T13:35:10.051113 #24049] DEBUG -- : Added a reservation: 
***D, [2017-04-26T13:35:10.052186 #24049] DEBUG -- : Added a reservation: 


*D, [2017-04-26T13:35:10.055943 #24049] DEBUG -- : trying to find an ip 
address, we got {:to=>nil, :from=>nil}*
*D, [2017-04-26T13:35:10.169631 #24049] DEBUG -- : execution expired*
*E, [2017-04-26T13:35:10.170884 #24049] ERROR -- : undefined method 
`reopen' for nil:NilClass*
*D, [2017-04-26T13:35:10.171373 #24049] DEBUG -- : undefined method 
`reopen' for nil:NilClass (NoMethodError)*
*/usr/share/foreman-proxy/modules/dhcp_common/subnet.rb:81:in 
`write_index_and_unlock'*
*/usr/share/foreman-proxy/modules/dhcp_common/subnet.rb:115:in `unused_ip'*
*/usr/share/foreman-proxy/modules/dhcp_common/server.rb:75:in `unused_ip'*
*/usr/share/foreman-proxy/modules/dhcp/dhcp_api.rb:61:in `GET 
/:network/unused_ip'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:863:in `call'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:863:in `route'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:521:in 
`instance_eval'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:521:in 
`route_eval'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:500:in 
`route!'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:497:in `catch'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:497:in 
`route!'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:476:in `each'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:476:in 
`route!'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:601:in 
`dispatch!'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:411:in `call!'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in 
`instance_eval'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in 
`invoke'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in `catch'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in 
`invoke'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:411:in `call!'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:399:in `call'*
*/usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/methodoverride.rb:24:in 
`call'*
*/usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/commonlogger.rb:18:in 
`call'*
*/usr/share/foreman-proxy/lib/proxy/log.rb:63:in `call'*
*/usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/showexceptions.rb:24:in 
`call'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:979:in `call'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:1005:in 
`synchronize'*
*/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:979:in `call'*
*/usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/urlmap.rb:47:in `call'*
*/usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/urlmap.rb:41:in `each'*
*/usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/urlmap.rb:41:in `call'*
*/usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/builder.rb:77:in `call'*
*/usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/content_length.rb:13:in 
`call'*
*/usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/handler/webrick.rb:48:in 
`service'*
*/usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'*
*/usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'*
*/usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'*
*/usr/lib/ruby/1.8/webrick/server.rb:162:in `start'*
*/usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'*
*/usr/lib/ruby/1.8/webrick/server.rb:95:in `start'*
*/usr/lib/ruby/1.8/webrick/server.rb:92:in `each'*
*/usr/lib/ruby/1.8/webrick/server.rb:92:in `start'*
*/usr/lib/ruby/1.8/webrick/server.rb:23:in `start'*
*/usr/lib/ruby/1.8/webrick/server.rb:82:in `start'*
*/usr/share/foreman-proxy/lib/launcher.rb:134:in `launch'*
*/usr/share/foreman-proxy/lib/launcher.rb:134:in `initialize'*
*/usr/share/foreman-proxy/lib/launcher.rb:134:in `new'*
*/usr/share/foreman-proxy/lib/launcher.rb:134:in `launch'*
*/usr/share/foreman-proxy/bin/smart-proxy:6*
*I, [2017-04-26T13:35:10.173093 #24049]  INFO -- : 192.168.11.237 - - 
[26/Apr/2017 13:35:10] "GET /192.168.11.0/unused_ip HTTP/1.1" 400 42 
30.6926*

*D, [2017-04-26T13:35:10.176795 #24049] DEBUG -- : close: 
192.168.11.237:56678*
*D, [2017-04-26T13:35:40.100763 #24049] DEBUG -- : execution expired*
*E, [2017-04-26T13:35:40.101972 #24049] ERROR -- : undefined method 
`reopen' for nil:NilClass*
*D, [2017-04-26T13:35:40.102373 #24049] DEBUG -- : undefined method 
`reopen' for nil:NilClass (NoMethodError)*
*/usr/share/foreman-proxy/modules/dhcp_common/subnet.rb:81:in 
`write_index_and_unlock'*
*/usr/share/foreman-proxy/modules/dhcp_common/subnet.rb:115:in `unused_ip'*
*/usr/share/foreman-proxy/modules/dhcp_common/server.rb:75:in `unused_ip'*
*/usr/share/foreman-proxy/modules/dhcp/dhcp_api.rb:61:in `GET 
/:network/unused_ip'*

[foreman-users] nsupdate on foreman-proxy doesn't work anymore

['Denis Müller' via Foreman users]

Hello guys,

since i justed updated and restart foreman-proxy on a centos 6 machine, i 
can't assign new ip addresses anymore. Foreman-proxy debug shows me:

*trying to find an ip address, we got {:to=>nil, :from=>nil}*

Configuration didn't change. I restarted foreman-proxy and dhcpd couple of 
times but no luck. What is wrong with that ?


*foreman-proxy-1.12.4-1.el6.noarch*

*and we have foreman-server in version 1.14.3*

Can somebody help me?

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] katello 3.3 search doesn't work?

['Denis Müller' via Foreman users]

we have the same issue running out of memory while searching for specific 
hosts in foreman 1.14.2.

Am Donnerstag, 2. März 2017 09:34:57 UTC+1 schrieb Cristian Falcas:
>
> The machine has 32 GB.
>
> We run here tomcat (candlepin), puppetdb, foreman and postgresql db.
>
> On Thu, Mar 2, 2017 at 12:24 AM, John Mitsch  > wrote:
>
>> Cristian,
>>
>> how much memory do you have on the machine you are running 
>> katello/foreman on?
>>
>> -John
>>
>> John Mitsch
>> Red Hat Engineering
>> (860)-967-7285
>> irc: jomitsch
>>
>> On Wed, Mar 1, 2017 at 7:02 AM, Cristian Falcas > > wrote:
>>
>>> Hi,
>>>
>>> I'm trying to see the hosts in Error state from the Dashboard.
>>>
>>> When I click the Error from Host Configuration Chart, the new page never 
>>> loads (the same happens with Active hosts).
>>>
>>> This is the url that it's executed is:
>>>
>>>
>>> https://puppet.company.net/hosts?utf8=%E2%9C%93=last_report+%3E+%2214405+minutes+ago%22+and+%28status.failed+%3E+0+or+status.failed_restarts+%3E+0%29+and+status.enabled+%3D+true
>>>
>>> Eventually foreman is killed by the kernel oom:
>>>
>>> 2017-03-01T06:59:05.768945-05:00 puppet.company.net kernel: Out of 
>>> memory: Kill process 14812 (ruby) score 300 or sacrifice child
>>>
>>> There should be ~ 30 hosts in Error and ~ 200 in Active.
>>> "Out Of Sync" hosts is working, but we have only 2 hosts in this status.
>>>
>>> Are there any known issues about this?
>>>
>>> Thank you,
>>> Cristian
>>>
>>> -- 
>>> 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 https://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-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com 
>> .
>> Visit this group at https://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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Foreman Host Status

['Denis Müller' via Foreman users]

Hallo Folks,

Is it possible to change how "host status" is managed. I mean, if build 
goes wrong process, the status would be red. If there would be errata 
updates, the status word would be red. Is it possible to provide host 
status dependend on only pupept configuration, but ignore errata?

Greets,
Denis

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Custom Partition Table

['Denis Müller' via Foreman users]

We edited template one more time because there are no facts in foreman if 
you create new host, so we got it work this way, maybe it would help 
somebody else:

*<% if @host.model.to_s =~ /^ProLiant DL360 G(6|7|8|9)$/ -%>*

Am Dienstag, 20. Dezember 2016 08:38:53 UTC+1 schrieb Denis Müller:
>
> Worked for me:
>
> <% if @host.facts['productname'] =~ /^ProLiant DL360 G(6|7|8)$/ -%>
> part /  --size=1 --grow --fstype ext4 --ondisk=sda
> part swap   --size=8192 --ondisk=sda
> part /var/lib/mysql --size=1 --grow --asprimary --ondisk=sdb
> <% end -%>
>
> Thank you!!!
>
> Am Montag, 19. Dezember 2016 16:46:09 UTC+1 schrieb Jason B. Nance:
>>
>> Give one of these methods a try:
>>
>>
>> https://stackoverflow.com/questions/2113235/ruby-is-a-string-in-a-list-of-values
>>
>> --
>> *From: *"'Denis Müller' via Foreman users" <forema...@googlegroups.com>
>> *To: *"Foreman users" <forema...@googlegroups.com>
>> *Sent: *Monday, December 19, 2016 9:35:07 AM
>> *Subject: *[foreman-users] Custom Partition Table
>>
>> Hi guys,
>> we would woulk like to do this:
>>
>> <% if @host.facts['Productname'] == ''ProLiant DL360 G7" -%> < How can 
>> we provide multiply strings like G7,G8,G9?
>> part /  --size=1 --grow --fstype ext4 --ondisk=sda
>> part swap  --size=8192 --ondisk=sda
>> part /var/lib/mysql--size=1 --grow --asprimary --ondisk=sdb
>> <% end -%>
>>
>> -- 
>> 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 https://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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Custom Partition Table

['Denis Müller' via Foreman users]

Worked for me:

<% if @host.facts['productname'] =~ /^ProLiant DL360 G(6|7|8)$/ -%>
part /  --size=1 --grow --fstype ext4 --ondisk=sda
part swap   --size=8192 --ondisk=sda
part /var/lib/mysql --size=1 --grow --asprimary --ondisk=sdb
<% end -%>

Thank you!!!

Am Montag, 19. Dezember 2016 16:46:09 UTC+1 schrieb Jason B. Nance:
>
> Give one of these methods a try:
>
>
> https://stackoverflow.com/questions/2113235/ruby-is-a-string-in-a-list-of-values
>
> --------------
> *From: *"'Denis Müller' via Foreman users" <forema...@googlegroups.com 
> >
> *To: *"Foreman users" <forema...@googlegroups.com >
> *Sent: *Monday, December 19, 2016 9:35:07 AM
> *Subject: *[foreman-users] Custom Partition Table
>
> Hi guys,
> we would woulk like to do this:
>
> <% if @host.facts['Productname'] == ''ProLiant DL360 G7" -%> < How can we 
> provide multiply strings like G7,G8,G9?
> part /  --size=1 --grow --fstype ext4 --ondisk=sda
> part swap  --size=8192 --ondisk=sda
> part /var/lib/mysql--size=1 --grow --asprimary --ondisk=sdb
> <% end -%>
>
> -- 
> 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 https://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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Re: Installing and updating Katello, Foreman

['Denis Müller' via Foreman users]

Can you provide the output of "yum repolist" ?

Am Mittwoch, 7. Dezember 2016 03:03:31 UTC+1 schrieb Lachlan Musicman:
>
> Denis,
>
> I'm not fluent enough with rpm based linux to know what the difference is?
>
> I know that the custom repo is working - there's only one file in 
> /etc/yum.repos.d/ (redhat.repo)
> I did a yum info epel-release and it responded that version 7, release 8 
> was installed, so I uninstalled it but still got the same error?
>
> cheers
> L.
>
> --
> The most dangerous phrase in the language is, "We've always done it this 
> way."
>
> - Grace Hopper
>
> On 6 December 2016 at 23:53, 'Denis Müller' via Foreman users <
> forema...@googlegroups.com > wrote:
>
>> We had similar  Dependency Resolution problems if katello-server has 
>> epel-release and our custom epel-repo installed at the same time on the 
>> system. So after removing epel-releae, we got our problem solved.
>>
>>
>> Am Dienstag, 6. Dezember 2016 04:29:52 UTC+1 schrieb Lachlan Musicman:
>>>
>>> Hi,
>>>
>>> We spent 3 months wrestling with Spacewalk before giving it up and 
>>> moving to Katello/Foreman early this year.
>>>
>>> Centos 7.2 is our main OS. Everything is up to date (or at least as up 
>>> to date as possible). Currently we have Foreman 1.12.4 w Katello 3.1.0, 
>>> "self-registered".
>>>
>>> I think I would like to update to Katello 3.2. The Katello update docs 
>>> implore us to make sure our system is up to date.
>>>
>>> One issue we have consistently had since we installed the system (on the 
>>> Katello server only) is a package conflict - every yum update gives us this 
>>> or something like it:
>>>
>>> 1063 packages excluded due to repository priority protections
>>> Resolving Dependencies
>>> --> Running transaction check
>>> ---> Package python-qpid-proton.x86_64 0:0.13.1-1.el7 will be updated
>>> ---> Package python-qpid-proton.x86_64 0:0.14.0-1.el7 will be an update
>>> ---> Package python-qpid-qmf.x86_64 0:0.32-1.el7 will be updated
>>> ---> Package python-qpid-qmf.x86_64 0:1.35.0-1.el7 will be an update
>>> ---> Package qpid-cpp-client.x86_64 0:0.34-8.el7 will be updated
>>> ---> Package qpid-cpp-client.x86_64 0:1.35.0-1.el7 will be an update
>>> ---> Package qpid-cpp-client-devel.x86_64 0:0.34-8.el7 will be updated
>>> ---> Package qpid-cpp-client-devel.x86_64 0:1.35.0-1.el7 will be an 
>>> update
>>> ---> Package qpid-cpp-server.x86_64 0:0.34-8.el7 will be updated
>>> ---> Package qpid-cpp-server.x86_64 0:1.35.0-1.el7 will be an update
>>> ---> Package qpid-cpp-server-linearstore.x86_64 0:0.34-8.el7 will be 
>>> updated
>>> ---> Package qpid-cpp-server-linearstore.x86_64 0:1.35.0-1.el7 will be 
>>> an update
>>> ---> Package qpid-proton-c.x86_64 0:0.13.1-1.el7 will be updated
>>> --> Processing Dependency: libqpid-proton.so.7()(64bit) for package: 
>>> qpid-dispatch-router-0.6.0-2.katello.el7.x86_64
>>> ---> Package qpid-proton-c.x86_64 0:0.14.0-1.el7 will be an update
>>> ---> Package qpid-qmf.x86_64 0:0.32-1.el7 will be updated
>>> ---> Package qpid-qmf.x86_64 0:1.35.0-1.el7 will be an update
>>> ---> Package qpid-tools.noarch 0:0.32-9.el7 will be updated
>>> ---> Package qpid-tools.noarch 0:1.35.0-1.el7 will be an update
>>> --> Finished Dependency Resolution
>>> Error: Package: qpid-dispatch-router-0.6.0-2.katello.el7.x86_64 
>>> (@Peter_MacCallum_Cancer_Centre_Katello_client)
>>>Requires: libqpid-proton.so.7()(64bit)
>>>Removing: qpid-proton-c-0.13.1-1.el7.x86_64 
>>> (@Peter_MacCallum_Cancer_Centre_Extra_Packages_for_Enterprise_Linux_7_-_x86_64_epel)
>>>libqpid-proton.so.7()(64bit)
>>>Updated By: qpid-proton-c-0.14.0-1.el7.x86_64 
>>> (Peter_MacCallum_Cancer_Centre_Extra_Packages_for_Enterprise_Linux_7_-_x86_64_epel)
>>>   ~libqpid-proton.so.8()(64bit)
>>>  You could try using --skip-broken to work around the problem
>>>  You could try running: rpm -Va --nofiles --nodigest
>>>
>>>
>>> I have found this suggestion from many versions ago
>>>
>>> http://projects.theforeman.org/issues/10665
>>>
>>> But that hasn't worked for us (with EPEL on a lower priority)
>>>
>>> 1. What have we done wrong?
>>> 2. Is there a way to stop this conflict/error or res

[foreman-users] Re: Installing and updating Katello, Foreman

['Denis Müller' via Foreman users]

We had similar  Dependency Resolution problems if katello-server has 
epel-release and our custom epel-repo installed at the same time on the 
system. So after removing epel-releae, we got our problem solved.

Am Dienstag, 6. Dezember 2016 04:29:52 UTC+1 schrieb Lachlan Musicman:
>
> Hi,
>
> We spent 3 months wrestling with Spacewalk before giving it up and moving 
> to Katello/Foreman early this year.
>
> Centos 7.2 is our main OS. Everything is up to date (or at least as up to 
> date as possible). Currently we have Foreman 1.12.4 w Katello 3.1.0, 
> "self-registered".
>
> I think I would like to update to Katello 3.2. The Katello update docs 
> implore us to make sure our system is up to date.
>
> One issue we have consistently had since we installed the system (on the 
> Katello server only) is a package conflict - every yum update gives us this 
> or something like it:
>
> 1063 packages excluded due to repository priority protections
> Resolving Dependencies
> --> Running transaction check
> ---> Package python-qpid-proton.x86_64 0:0.13.1-1.el7 will be updated
> ---> Package python-qpid-proton.x86_64 0:0.14.0-1.el7 will be an update
> ---> Package python-qpid-qmf.x86_64 0:0.32-1.el7 will be updated
> ---> Package python-qpid-qmf.x86_64 0:1.35.0-1.el7 will be an update
> ---> Package qpid-cpp-client.x86_64 0:0.34-8.el7 will be updated
> ---> Package qpid-cpp-client.x86_64 0:1.35.0-1.el7 will be an update
> ---> Package qpid-cpp-client-devel.x86_64 0:0.34-8.el7 will be updated
> ---> Package qpid-cpp-client-devel.x86_64 0:1.35.0-1.el7 will be an update
> ---> Package qpid-cpp-server.x86_64 0:0.34-8.el7 will be updated
> ---> Package qpid-cpp-server.x86_64 0:1.35.0-1.el7 will be an update
> ---> Package qpid-cpp-server-linearstore.x86_64 0:0.34-8.el7 will be 
> updated
> ---> Package qpid-cpp-server-linearstore.x86_64 0:1.35.0-1.el7 will be an 
> update
> ---> Package qpid-proton-c.x86_64 0:0.13.1-1.el7 will be updated
> --> Processing Dependency: libqpid-proton.so.7()(64bit) for package: 
> qpid-dispatch-router-0.6.0-2.katello.el7.x86_64
> ---> Package qpid-proton-c.x86_64 0:0.14.0-1.el7 will be an update
> ---> Package qpid-qmf.x86_64 0:0.32-1.el7 will be updated
> ---> Package qpid-qmf.x86_64 0:1.35.0-1.el7 will be an update
> ---> Package qpid-tools.noarch 0:0.32-9.el7 will be updated
> ---> Package qpid-tools.noarch 0:1.35.0-1.el7 will be an update
> --> Finished Dependency Resolution
> Error: Package: qpid-dispatch-router-0.6.0-2.katello.el7.x86_64 
> (@Peter_MacCallum_Cancer_Centre_Katello_client)
>Requires: libqpid-proton.so.7()(64bit)
>Removing: qpid-proton-c-0.13.1-1.el7.x86_64 
> (@Peter_MacCallum_Cancer_Centre_Extra_Packages_for_Enterprise_Linux_7_-_x86_64_epel)
>libqpid-proton.so.7()(64bit)
>Updated By: qpid-proton-c-0.14.0-1.el7.x86_64 
> (Peter_MacCallum_Cancer_Centre_Extra_Packages_for_Enterprise_Linux_7_-_x86_64_epel)
>   ~libqpid-proton.so.8()(64bit)
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest
>
>
> I have found this suggestion from many versions ago
>
> http://projects.theforeman.org/issues/10665
>
> But that hasn't worked for us (with EPEL on a lower priority)
>
> 1. What have we done wrong?
> 2. Is there a way to stop this conflict/error or resolve this issue?
> 3. Can I just upgrade over the top of this issue?
> 4. Does the upgrade make this go away?
>
> Cheers
> L.
>
> --
> The most dangerous phrase in the language is, "We've always done it this 
> way."
>
> - Grace Hopper
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Foreman-GUI play Ansible-Role

['Denis Müller' via Foreman users]

Server and client both have ansible ver. 2.2 installed.

I selected a ntp-tole and provided it to the cleint-host.

If i click on "Play ansible-role" it does nothing.

here formeman production log:

2016-11-29 09:45:53 [app] [I] Started GET "/ansible/hosts/128/play_roles" 
for 192.168.0.6 at 2016-11-29 09:45:53 +0100
2016-11-29 09:45:53 [app] [I] Processing by HostsController#play_roles as 
HTML
2016-11-29 09:45:53 [app] [I]   Parameters: {"id"=>"128"}
2016-11-29 09:45:53 [app] [I] Performing ForemanAnsible::RunPlaybookJob 
from Inline(ansible) with arguments: 
"/tmp/foreman-ansible-client-roles20161129-7519-18oll3f", 
"/tmp/foreman-331b3e32-5486-485f-8216-4cf8de34c066-inventory20161129-7519-6i3owj"
2016-11-29 09:45:53 [foreman_ansible] [I] PID for playbook run for 
/tmp/foreman-ansible-client-roles20161129-7519-18oll3f 
/tmp/foreman-331b3e32-5486-485f-8216-4cf8de34c066-inventory20161129-7519-6i3owj:
 
4453
2016-11-29 09:45:53 [app] [I] Performed ForemanAnsible::RunPlaybookJob from 
Inline(ansible) in 1.08ms
2016-11-29 09:45:53 [app] [I] Enqueued ForemanAnsible::RunPlaybookJob (Job 
ID: d6ab0d86-2b90-4946-95f4-4ed7ab82369c) to Inline(ansible) with 
arguments: 
"/tmp/foreman-ansible-hhvm1.nodes.rto.de-roles20161129-7519-18oll3f", 
"/tmp/foreman-331b3e32-5486-485f-8216-4cf8de34c066-inventory20161129-7519-6i3owj"
2016-11-29 09:45:53 [app] [I] Redirected to 
https://theforeman.nodes.rto.de/hosts/hhvm1.nodes.rto.de
2016-11-29 09:45:53 [app] [I] Completed 302 Found in 44ms (ActiveRecord: 
6.9ms)
2016-11-29 09:45:53 [app] [I] Started GET "/hosts/hhvm1.nodes.rto.de" for 
192.168.0.6 at 2016-11-29 09:45:53 +0100
2016-11-29 09:45:53 [app] [I] Processing by HostsController#show as HTML
2016-11-29 09:45:53 [app] [I]   Parameters: {"id"=>"hhvm1.nodes.rto.de"}
2016-11-29 09:45:53 [app] [I]   Rendered hosts/_metrics.html.erb (1.0ms)
2016-11-29 09:45:53 [app] [I]   Rendered hosts/show.html.erb within 
layouts/application (121.5ms)
2016-11-29 09:45:53 [app] [I]   Rendered 
layouts/_application_content.html.erb (0.7ms)
2016-11-29 09:45:53 [app] [I]   Rendered home/_user_dropdown.html.erb 
(3.5ms)
2016-11-29 09:45:53 [app] [I] Read fragment views/tabs_and_title_records-6 
(0.6ms)
2016-11-29 09:45:53 [app] [I]   Rendered home/_topbar.html.erb (12.7ms)
2016-11-29 09:45:53 [app] [I]   Rendered layouts/base.html.erb (14.8ms)
2016-11-29 09:45:53 [app] [I] Completed 200 OK in 172ms (Views: 129.7ms | 
ActiveRecord: 14.9ms)
2016-11-29 09:45:54 [app] [I] Started GET 
"/images/avatars/4f0d9e11637861e817b0d619a3a236b2c404087e.jpg" for 
192.168.0.6 at 2016-11-29 09:45:54 +0100

There is no file 
"/tmp/foreman-331b3e32-5486-485f-8216-4cf8de34c066-inventory20161129-7519-6i3owj"
 
in tmp directory.

Should both client and server have in /etc/ansbiel/ansible.cfg option 
activated?

[defaults]

callback_whitelist = foreman <<--$FQDN?


Greets,
Denis

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] The server does not support such operation

['Denis Müller' via Foreman users]

Hi,

1.
i wanted to try to apply an errata to a host-collection, so i did:

hammer --username="admin" --password="***" host-collection erratum install 
--organization="***" --name "***" --errata "FEDORA-EPEL-2016-6019e05039"
As a result im getting: 

Could not schedule installation of errata:
Fehler: The server does not support such operation.

[root@theforeman ~]# hammer --username="admin" --password="***" 
host-collection erratum install
Could not schedule installation of errata:
  Fehler: Option '--errata' ist erforderlich
  
  Siehe: 'hammer host-collection erratum install --help'
[root@theforeman ~]# hammer --username="admin" --password="***" 
host-collection erratum install --errata
Could not schedule installation of errata:
  Fehler: The server does not support such operation.

2. Is it possible to apply all errata of one type like "bugfix" to a 
host-collection?

Greets,
Denis

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Katello+RedHat Repositories

['Denis Müller' via Foreman users]

Hello Guys,

i was wondering, is it possible to use RedHat repositories with CentOS 
Systems?

Now we are using this project 
https://github.com/brdude/pulp_centos_errata_import to provide new 
Errata-Updates to CentOS-Systems.

We have an RedHat-Subscripton "Red Hat Enterprise Linux Desktop, 
Self-support " 
but i have no idea if this subscription is enough to get Errata-Updates 
from RedHat.

On Katello site is only a quick how-to, but the is no explanation what 
subscription-type we need to be able to create a manifest file to import 
into Katello.



Greets,
Denis

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: No Puppet module parser is installed - Katello 3.2

['Denis Müller' via Foreman users]

After applying your solution:

foreman-installer --scenario capsule --help
/usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/markup/parser.rb:430:in `initialize': 
no implicit conversion of Hash into String (TypeError)
from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/markup/parser.rb:430:in `
new'
from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/markup/parser.rb:430:in 
`setup_scanner'
from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/markup/parser.rb:450:in 
`tokenize'
from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/markup/parser.rb:60:in `
parse'
from /usr/share/gems/gems/rdoc-4.0.0/lib/rdoc/markup.rb:751:in `parse'
from /usr/share/gems/gems/kafo_parsers-0.1.2/lib/kafo_parsers/doc_parser
.rb:19:in `initialize'
from 
/usr/share/gems/gems/kafo_parsers-0.1.2/lib/kafo_parsers/puppet_strings_module_parser.rb:100:in
 
`new'
from 
/usr/share/gems/gems/kafo_parsers-0.1.2/lib/kafo_parsers/puppet_strings_module_parser.rb:100:in
 
`docs'
from /usr/share/gems/gems/kafo_parsers-0.1.2/lib/kafo_parsers/
puppet_strings_module_parser.rb:13:in `parse'
from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/puppet_module.rb:71:in `
parse'
from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/configuration.rb:89:in 
`block in modules'
from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/configuration.rb:89:in 
`map'
from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/configuration.rb:89:in `
modules'
from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/configuration.rb:189:in 
`params'
from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/configuration.rb:199:in 
`preset_defaults_from_puppet'
from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/kafo_configure.rb:270:in `
set_parameters'
from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/kafo_configure.rb:99:in 
`initialize'
from /usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:133:in `new'
from /usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:133:in `run'
from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/kafo_configure.rb:154:in 
`run'
from /usr/sbin/foreman-installer:8:in `'



Am Dienstag, 8. November 2016 16:40:52 UTC+1 schrieb Rob Sanders:
>
> I meant to say:
>
> puppet resource package puppet-strings provider=puppet_gem
>
>
> https://github.com/puppetlabs/puppet-strings
>
>
> On Tuesday, 8 November 2016 15:37:13 UTC, Rob Sanders wrote:
>>
>> Have you tried:
>>
>> puppet resource package yard provider=puppet_gem
>>
>>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Katello 3.0 Errata import issues

['Denis Müller' via Foreman users]

Hi,

make sure "Administer" > "Settings" > "Katello" and set 
"force_post_sync_action" is set to true.

I do it personally one repo after another for an example CentOS Base repo:

./errata_import.pl --debug --errata=errata.latest.xml --user=admin 
--password=*** --include-repe="Repo name"

U can find repo name with:

pulp-admin -u admin -p *** repo list

Greets

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] confused about memcache

['Denis Müller' via Foreman users]

I installed a memcache on the same foreman server. Memcache is running on 
localhost port 11211, i configured foreman to use it. 

Production log:


2016-10-28 20:52:30 [app] [I] memcached cache backend enabled: [:dalli_store
, "192.168.11.237:11211", {:namespace=>"foreman", :expires_in=>86400, :
compress=>true}]
2016-10-28 20:52:33 [app] [I] memcached cache backend enabled: [:dalli_store
, "192.168.11.237:11211", {:namespace=>"foreman", :expires_in=>86400, :
compress=>true}]


But i can't notice any perfomance difference. I installed monitorix to 
check how much ram it using right now but it is only under 1MB, see picture.

Maybe somebody can share his experience with this plugin please?

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Upgrade Step: migrate_foreman...failed - Need Help!

['Denis Müller' via Foreman users]

thank you

Am Freitag, 21. Oktober 2016 14:00:15 UTC+2 schrieb Denis Müller:
>
> fix for the problem:
>
> http://projects.theforeman.org/issues/16441
>
> Am Freitag, 21. Oktober 2016 12:22:38 UTC+2 schrieb Denis Müller:
>>
>> Hello Guys, i tried to upgrade katello 3.0 to 3.1. 
>>
>> Can enybody help?
>>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Repository structure

['Denis Müller' via Foreman users]

Hi,

im trying to understand how katello/pulp manage directory structure.

I created 

Organization: Microcorp
Lifecycle Environemt: Library
Content View:default
Product:centosos-7-x86_64
repo: updates

If i publish it over http im getting on fs:


/var/lib/pulp/published/yum/http/repos/Microcorp/Library/default/*custom*
/centos-7-x86_64/updates/

What is custom and how i delete it?

Greets,
Denis

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Upgrade Step: migrate_foreman...failed - Need Help!

['Denis Müller' via Foreman users]

fix for the problem:

http://projects.theforeman.org/issues/16441

Am Freitag, 21. Oktober 2016 12:22:38 UTC+2 schrieb Denis Müller:
>
> Hello Guys, i tried to upgrade katello 3.0 to 3.1. 
>
> Can enybody help?
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Upgrade Step: migrate_foreman...failed - Need Help!

['Denis Müller' via Foreman users]

Hello Guys, i tried to upgrade katello 3.0 to 3.1. 

Can enybody help?

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_migrations/01-migrate_legacy_foreman_installer_config.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_migrations/10-migrate_legacy_capsule_config.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_migrations/11-migrate_legacy_katello_config.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/01-helpers.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/10-reset_hook.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/11-clear_pulp_data_hook.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/12-clear_puppet_environments.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/20-certs_update.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/30-upgrade.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/init/10-puppet-profile-on-el6.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/10-reset_feature.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/11-clear_pulp_data_feature.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/12-clear_puppet_environments_feature.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/15-check_java.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/16-set_umask.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/20-certs_update.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/29-remove_sslconf.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/30-upgrade.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/post/10-post_install.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/post/30-upgrade.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_validations/10-check_capsule_pulp.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_validations/11-check_proxy_url.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_migrations/01-migrate_legacy_foreman_installer_config.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_migrations/10-migrate_legacy_capsule_config.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_migrations/11-migrate_legacy_katello_config.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/01-helpers.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/10-reset_hook.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/11-clear_pulp_data_hook.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/12-clear_puppet_environments.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/20-certs_update.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/30-upgrade.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/init/10-puppet-profile-on-el6.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/10-reset_feature.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/11-clear_pulp_data_feature.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/12-clear_puppet_environments_feature.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/15-check_java.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/16-set_umask.rb
[DEBUG 2016-10-21 12:16:36 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/20-certs_update.rb

[foreman-users] Failed to sync iso

['Denis Müller' via Foreman users]

Hi guys,

im trying to sync http://oirase.annexia.org/virt-p2v/

but with no luck.

2016-10-18 18:19:08 [app] [I] Started POST 
"/katello/api/repositories/261/sync" for ::1 at 2016-10-18 18:19:08 +0200
2016-10-18 18:19:08 [app] [I] Processing by 
Katello::Api::V2::RepositoriesController#sync as JSON
2016-10-18 18:19:08 [app] [I]   Parameters: 
{"source_url"=>"http://oirase.annexia.org/virt-p2v;, "api_version"=>"v2", 
"id"=>"261", "repository"=>{}}
2016-10-18 18:19:08 [app] [I] Authorized user admin(Admin User)
2016-10-18 18:19:08 [app] [I]   Rendered 
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.2/app/views/katello/api/v2/repositories/sync.json.rabl
 
within katello/api/v2/layouts/resource (68.8ms)
2016-10-18 18:19:08 [app] [I] Completed 202 Accepted in 547ms (Views: 
60.2ms | ActiveRecord: 89.4ms)
2016-10-18 18:19:08 [app] [I] Started GET 
"/foreman_tasks/api/tasks/d1fded97-0233-4408-bae3-9fa06babd170" for ::1 at 
2016-10-18 18:19:08 +0200
2016-10-18 18:19:08 [app] [I] Processing by 
ForemanTasks::Api::TasksController#show as JSON
2016-10-18 18:19:08 [app] [I]   Parameters: 
{"id"=>"d1fded97-0233-4408-bae3-9fa06babd170", "task"=>{}}
2016-10-18 18:19:08 [app] [I] Authorized user admin(Admin User)
2016-10-18 18:19:08 [app] [I]   Rendered 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.7.18/app/views/foreman_tasks/api/tasks/show.json.rabl
 
(61.8ms)
2016-10-18 18:19:08 [app] [I] Completed 200 OK in 92ms (Views: 56.2ms | 
ActiveRecord: 15.4ms)
2016-10-18 18:19:09 [app] [I] Started POST 
"/katello/api/v2/repositories/sync_complete?token=ivf3HjarVjM7iZzHw2yfax3mqoM53nRQ"
 
for 192.168.11.237 at 2016-10-18 18:19:09 +0200
2016-10-18 18:19:09 [app] [I] Processing by 
Katello::Api::V2::RepositoriesController#sync_complete as */*
2016-10-18 18:19:09 [app] [I]   Parameters: {"call_report"=>"[FILTERED]", 
"event_type"=>"repo.sync.finish", 
"payload"=>{"importer_id"=>"iso_importer", "exception"=>nil, 
"repo_id"=>"RTO_GmbH-virt-p2v-libguestfs", "traceback"=>nil, 
"started"=>"2016-10-18T16:19:08Z", "_ns"=>"repo_sync_results", 
"completed"=>"2016-10-18T16:19:09Z", "importer_type_id"=>"iso_importer", 
"error_message"=>nil, "summary"=>{"traceback"=>nil, 
"error_message"=>{"response_code"=>404, "response_msg"=>"Not Found"}, 
"finished_bytes"=>0, "num_isos"=>nil, "state"=>"manifest_failed", 
"iso_error_messages"=>nil, "total_bytes"=>nil, "num_isos_finished"=>0, 
"state_times"=>{"not_started"=>"2016-10-18T16:19:08", 
"manifest_in_progress"=>"2016-10-18T16:19:08", 
"manifest_failed"=>"2016-10-18T16:19:08"}}, "added_count"=>0, 
"result"=>"failed", "updated_count"=>0, "details"=>nil, 
"id"=>"58064b7df57f2e61e336f075", "removed_count"=>0}, 
"token"=>"ivf3HjarVjM7iZzHw2yfax3mqoM53nRQ", "api_version"=>"v2", 
"repository"=>{}}
2016-10-18 18:19:09 [app] [I] Sync_complete called for libguestfs, running 
after_sync.
2016-10-18 18:19:09 [foreman-tasks/action] [E] PLP: Importer indicated 
a failed response (Katello::Errors::PulpError)
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.2/app/lib/actions/pulp/abstract_async_task.rb:121:in
 
`block in external_task='
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.2/app/lib/actions/pulp/abstract_async_task.rb:119:in
 
`each'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.2/app/lib/actions/pulp/abstract_async_task.rb:119:in
 
`external_task='
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.2/app/lib/actions/pulp/repository/sync.rb:46:in
 
`external_task='
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/action/polling.rb:98:in
 
`poll_external_task_with_rescue'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/action/polling.rb:21:in
 
`run'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/action/cancellable.rb:9:in
 
`run'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.2/app/lib/actions/pulp/abstract_async_task.rb:45:in
 
`run'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/action.rb:506:in
 
`block (3 levels) in execute_run'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware/stack.rb:26:in
 
`call'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware/stack.rb:26:in
 
`pass'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware.rb:17:in
 
`pass'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware.rb:30:in
 
`run'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware/stack.rb:22:in
 
`call'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware/stack.rb:26:in
 
`pass'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware.rb:17:in
 
`pass'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.2/app/lib/actions/middleware/remote_action.rb:16:in
 
`block in 

Re: [foreman-users] Katello 3.2 RC2 released

['Denis Müller' via Foreman users]

Just tried a fresh installation of capsule 3.2 but there are some packages 
missing:

[root@ffm01wopfp01 yum.repos.d]# yum search katello-debug
Geladene Plugins: fastestmirror, package_upload, product-id, 
search-disabled-repos, subscription-manager
Loading mirror speeds from cached hostfile
===
 
N/S matched: katello-debug 

katello-debug.noarch : Katello Debug utilities

  only-Übereinstimmungen in Name und Zusammenfassung, «Alles suchen» für 
vollständige Suche.
[root@ffm01wopfp01 yum.repos.d]# yum install katello-debug.noarch
Geladene Plugins: fastestmirror, package_upload, product-id, 
search-disabled-repos, 
subscription-manager

  
| 2.1 kB  00:00:00 
Loading mirror speeds from cached hostfile
Abhängigkeiten werden aufgelöst
--> Transaktionsprüfung wird ausgeführt
---> Paket* katello-debug.noarch 0:3.1.0-5.el7* markiert, um installiert zu 
werden
--> Abhängigkeitsauflösung beendet

Abhängigkeiten aufgelöst

===
 Package   
Arch   
Version
Paketquelle Größe
===
Installieren:
 katello-debug 
noarch 
3.1.0-5.el7
katello  13 k

Transaktionsübersicht
===
Installieren  1 Paket

Gesamte Downloadgröße: 13 k
Installationsgröße: 4.0 k
Is this ok [y/d/N]: y
Downloading packages:
Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
katello-debug-3.1.0-5.el7.noar 
FAILED  
https://fedorapeople.org/groups/katello/releases/yum/3.2/katello/el7/x86_64/katello-debug-3.1.0-5.el7.noarch.rpm:
 
[Errno 14] HTTPS Error 404 - Not Found ]  0.0 B/s 
|0 B  --:--:-- ETA 
Anderer Spiegelserver wird versucht.
To address this issue please refer to the below knowledge base article 

https://access.redhat.com/articles/1320623

If above article doesn't help to resolve this issue please create a bug on 
https://bugs.centos.org/



Error downloading packages:
  katello-debug-3.1.0-5.el7.noarch: [Errno 256] No more mirrors to try.

Am Donnerstag, 13. Oktober 2016 14:26:17 UTC+2 schrieb John Mitsch:
>
> We are happy to announce the second release candidate for Katello 3.2 (Malt 
> Liquor).
>
> One notable change in 3.2 is the support of Puppet 4. More info about 
> upgrading to Puppet 4 can be found here: 
>
> http://www.katello.org/docs/nightly/upgrade/puppet.html
>
> Your help is appreciated to ensure our GA release is solid, by either
> installing a new instance or upgrading a test server.
>
> A list of the changes in Katello 3.2 is in our release notes:
> http://www.katello.org/docs/3.2/release_notes/release_notes.html
>
>
> Installation or Upgrade
> ==
>
> For installation, please see the instructions at:
>
>   Server:  http://www.katello.org/docs/3.2/installation/index.html
>   Capsule:  http://www.katello.org/docs/3.2/installation/capsule.html 
>
> For those testing upgrades, please use the instructions below and file
> any issues you encounter. Please note that there are separate upgrade
> instructions for the Katello server and Capsules:
>
>   Server:  http://www.katello.org/docs/3.2/upgrade/index.html
>   Capsule:  http://www.katello.org/docs/3.2/upgrade/capsule.html
>
> Bug reporting
> ===
> If you come across a bug in your testing, please file it and note the
> version of Katello that you're using in the report and set the release
> to 3.2.0.
>
>   http://projects.theforeman.org/projects/katello/issues/new
>
> Justin
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at 

[foreman-users] "Host Errata Advisory" empty reports

['Denis Müller' via Foreman users]

Hi guys,

i configured foreman to send us daily reports about errata-updates, but 
there is only an empty template to read. Did i miss something?

See picture.


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Validation failed: Name has already been taken

['Denis Müller' via Foreman users]

Hello Foreman Users,

i'm trying to apply a filter to my content view, i have only one "Default 
View". After i created a filter i tried to publish new version of a content 
view but i'm getting the error:  Validation failed: Name has already been 
taken

Denis


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Katello sync plans custom interval

['Denis Müller' via Foreman users]

Hello Guys,

does anybody know if there a  way to customize the sync interval for 
products like every 15 mins?

Greets,
Denis

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Katello 2.4.3 missing

['Denis Müller' via Foreman users]

i found it by my self,  tfm-rubygem-katello.noarch is the right package to 
install/update.

Am Dienstag, 19. Juli 2016 10:37:19 UTC+2 schrieb Denis Müller:
>
> Hey guys,
>
> i used katello 2.4 now for a while and right now i would like to upgrade 
> to the newest version, to version 3. For the installation u used thsi 
> guide: http://www.katello.org/docs/2.4/installation/index.html
>
> I tied to follow the "Upgrade-Guide": 
> http://www.katello.org/docs/3.1/upgrade/index.html and the first step is 
> to try the "foreman-rake katello:upgrade_check" script that shoud be in 
> katello version 2.4.2 and 2.4.3, but there is only 
> katello-2.4.1-1.el7.noarch. 
>
> Yum update shows no new packages to install.
> Greets
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Katello 2.4.3 missing

['Denis Müller' via Foreman users]

Hey guys,

i used katello 2.4 now for a while and right now i would like to upgrade to 
the newest version, to version 3. For the installation u used thsi guide: 
http://www.katello.org/docs/2.4/installation/index.html

I tied to follow the "Upgrade-Guide": 
http://www.katello.org/docs/3.1/upgrade/index.html and the first step is to 
try the "foreman-rake katello:upgrade_check" script that shoud be in 
katello version 2.4.2 and 2.4.3, but there is only katello-2.4.1-1.el7.noarch. 

Yum update shows no new packages to install.
Greets

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Foreman Ansible 1.0 released - now with roles support

['Denis Müller' via Foreman users]

This is the greate feature, thank you very much!

Am Montag, 11. Juli 2016 12:07:39 UTC+2 schrieb Daniel Lobato:
>
> Hi all! 
>
> 1.12 just came out, and with it, foreman_ansible 1.0! 
>
> The main changes are bugfixes to the callback script, and now you can 
> select roles (from /etc/ansible/roles) - 
> http://docs.ansible.com/ansible/playbooks_roles.html 
> and apply them to one or multiple hosts. Some of the improvements I can 
> think of are adding support to inherit roles from Host groups, read 
> playbook parameters and import them to Foreman so we can use 
> smart-variables (like with Puppet), and add support to enforce roles 
> through the API (unoficially you can do this at /hosts/:id/play_roles). 
>
> I want to wait until the community starts using this plugin & hear 
> feedback before continuing working on it, so please reply to the thread 
> if you want X or Y feature, have anything to say, etc :) 
>
> You can find the new documentation here: 
> https://www.theforeman.org/plugins/foreman_ansible/1.x/index.html 
>
> This release is available from Foreman 1.12-rc1 onwards. 
>
> Thank you! 
>
> -- 
> Daniel Lobato Garcia 
>
> @dLobatog 
> blog.daniellobato.me 
> daniellobato.me 
>
> GPG: http://keys.gnupg.net/pks/lookup?op=get=0x7A92D6DD38D6DE30 
> Keybase: https://keybase.io/elobato 
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Katello 3 Installation failed cause of dependencies

['Denis Müller' via Foreman users]

Hi,

i was trying to install "katello.noarch 0:3.0.0-9.el7" but no luck here. 
Installation can not resolve all dependencies, is it a bug? See install.log.
I would appreciate any help.

Best regards,

Denis

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
Geladene Plugins: fastestmirror, package_upload, priorities, product-id, search-
: disabled-repos, subscription-manager
Loading mirror speeds from cached hostfile
 * epel: mirrors.n-ix.net
72 packages excluded due to repository priority protections
Abhängigkeiten werden aufgelöst
--> Transaktionsprüfung wird ausgeführt
---> Paket katello.noarch 0:3.0.0-9.el7 markiert, um installiert zu werden
--> Abhängigkeit katello-common = 3.0.0-9.el7 wird für Paket 
katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit java-openjdk < 1:1.8.0.45 wird für Paket 
katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit mongodb-server >= 2.4 wird für Paket 
katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit mongodb >= 2.4 wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit java-openjdk >= 1:1.7.0 wird für Paket 
katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit createrepo >= 0.9.9-18.el7 wird für Paket 
katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit squid wird für Paket katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit qpid-dispatch-router wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit qpid-cpp-server-linearstore wird für Paket 
katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit qpid-cpp-client-devel wird für Paket 
katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit python-pulp-streamer wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit python-gofer-qpid wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit python-crane wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit pulp-server wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit pulp-selinux wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit pulp-rpm-plugins wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit pulp-puppet-tools wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit pulp-puppet-plugins wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit pulp-katello wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit pulp-docker-plugins wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit postgresql-server wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit postgresql wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit mod_xsendfile wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit lsof wird für Paket katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit foreman-installer-katello wird für Paket 
katello-3.0.0-9.el7.noarch verarbeitet
--> Abhängigkeit cyrus-sasl-plain wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit candlepin-selinux wird für Paket katello-3.0.0-9.el7.noarch 
verarbeitet
--> Abhängigkeit candlepin wird für Paket katello-3.0.0-9.el7.noarch verarbeitet
--> Transaktionsprüfung wird ausgeführt
---> Paket candlepin.noarch 0:0.9.54.6-1.el7 markiert, um installiert zu werden
--> Abhängigkeit liquibase >= 2.0.5 wird für Paket 
candlepin-0.9.54.6-1.el7.noarch verarbeitet
--> Abhängigkeit tomcat wird für Paket candlepin-0.9.54.6-1.el7.noarch 
verarbeitet
--> Abhängigkeit postgresql-jdbc wird für Paket candlepin-0.9.54.6-1.el7.noarch 
verarbeitet
---> Paket candlepin-selinux.noarch 0:0.9.54.6-1.el7 markiert, um installiert 
zu werden
---> Paket createrepo.noarch 0:0.9.9-25.el7_2 markiert, um installiert zu werden
--> Abhängigkeit python-deltarpm wird für Paket 
createrepo-0.9.9-25.el7_2.noarch verarbeitet
--> Abhängigkeit deltarpm wird für Paket createrepo-0.9.9-25.el7_2.noarch 
verarbeitet
---> Paket cyrus-sasl-plain.x86_64 0:2.1.26-20.el7_2 markiert, um installiert 
zu werden
---> Paket foreman-installer-katello.noarch 0:3.0.2-1.el7 markiert, um 
installiert zu werden
--> Abhängigkeit katello-installer-base = 3.0.2-1.el7 wird für Paket 
foreman-installer-katello-3.0.2-1.el7.noarch verarbeitet
--> Abhängigkeit katello-service >= 3.0.0 wird für Paket 
foreman-installer-katello-3.0.2-1.el7.noarch verarbeitet
---> Paket java-1.7.0-openjdk.x86_64 1:1.7.0.101-2.6.6.1.el7_2 markiert, um 
installiert zu werden
--> Abhängigkeit java-1.7.0-openjdk-headless = 1:1.7.0.101-2.6.6.1.el7_2 wird 
für Paket 1:java-1.7.0-openjdk-1.7.0.101-2.6.6.1.el7_2.x86_64 verarbeitet
-->