Re: [foreman-users] Update from Katello 3.4 to 3.5 RC1

[Eric D Helms]

roductcontent.xml:
> schema_reference.4: Failed to read schema document '
> http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.5.xsd', because
> 1) could not find the document; 2) the document could not be read; 3) the
> root element of the document is not .
>
> Configuring PostgreSQL with JDBC URL: jdbc:postgresql://localhost/
> candlepin
> Migrating candlepin database
> --driver=org.postgresql.Driver --classpath=/usr/share/java/
> postgresql-jdbc.jar:/var/lib/tomcat/webapps/candlepin/WEB-INF/classes/
> --changeLogFile=db/changelog/changelog-update.xml 
> --url=jdbc:postgresql://localhost/candlepin
> --username=candlepin  --password=
> Traceback (most recent call last):
>   File "/usr/share/candlepin/cpdb", line 273, in 
> dbsetup.update()
>   File "/usr/share/candlepin/cpdb", line 69, in update
> self._run_liquibase("db/changelog/changelog-update.xml")
>   File "/usr/share/candlepin/cpdb", line 94, in _run_liquibase
> self.community))
>   File "/usr/share/candlepin/cpdb", line 38, in run_command
> error_out(command, status, output)
>   File "/usr/share/candlepin/cpdb", line 46, in error_out
> raise Exception("Error running command")
> Exception: Error running command
> /usr/share/candlepin/cpdb --update --database '//localhost/candlepin'
> --user candlepin --password vh3MC4YwcHtZdPWwkU8RekeyPS6ByBAU failed!
> Check the output for error!
> Upgrade step migrate_candlepin failed. Check logs for more information.
>
> With ou without proxy, same error.
>
> Thx
>
>
> --
> 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.
>



-- 
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] TheForeman 1.16-RC1 with Puppet 5.3

[Eric D Helms]

The fix is planned for 1.16 RC2 I believe.

Eric

On Mon, Oct 23, 2017 at 7:56 AM, Roger Martensson <
roger.martens...@gmail.com> wrote:

> Hi!
>
> Trying to set up a very simple install of forman (Foreman-installer
> without anything else) and I'm getting an error while starting the Puppet
> Server.
>
> Oct 23 13:47:01 fmantest puppetserver[21806]: Exception in thread "main"
> java.lang.RuntimeException: Service ':FilesystemWatchService' not found.
>
> I did resolve the issue with:
> https://github.com/theforeman/puppet-puppet/issues/549
>
> Will the fix references in this Issue be added to 1.16?
>
>
> --
> 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.
>



-- 
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] Re: Katello 3.4.5 Released

[Eric D 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 <
foreman-users@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-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.
>



-- 
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] Foreman/Katello not displaying installable errata or packages in Content Hosts view

[Eric D Helms]

m-docker-api-1.28.0-2.el7.noarch
>- tfm-rubygem-domain_name-0.5.20160310-1.el7.noarch
>- tfm-rubygem-dynflow-0.8.24-1.fm1_15.el7.noarch
>- tfm-rubygem-excon-0.51.0-1.el7.noarch
>- tfm-rubygem-facter-2.4.0-3.el7.x86_64
>- tfm-rubygem-fast_gettext-1.1.0-1.el7.noarch
>- tfm-rubygem-fog-1.38.0-1.el7.noarch
>- tfm-rubygem-fog-aws-1.2.0-1.el7.noarch
>- tfm-rubygem-fog-core-1.42.0-1.el7.noarch
>- tfm-rubygem-fog-google-0.1.0-2.el7.noarch
>- tfm-rubygem-fog-json-1.0.2-4.el7.noarch
>- tfm-rubygem-fog-openstack-0.1.18-1.el7.noarch
>- tfm-rubygem-fog-rackspace-0.1.4-1.el7.noarch
>- tfm-rubygem-fog-vsphere-1.7.0-1.el7.noarch
>- tfm-rubygem-fog-xenserver-0.2.3-1.el7.noarch
>- tfm-rubygem-fog-xml-0.1.2-4.el7.noarch
>- tfm-rubygem-foreman-tasks-0.9.1-1.fm1_15.el7.noarch
>- tfm-rubygem-foreman-tasks-core-0.1.2-1.fm1_15.el7.noarch
>- tfm-rubygem-foreman_docker-3.0.0-1.fm1_13.el7.noarch
>- tfm-rubygem-formatador-0.2.1-9.el7.noarch
>- tfm-rubygem-friendly_id-5.1.0-3.el7.noarch
>- tfm-rubygem-gettext_i18n_rails-1.2.1-3.el7.noarch
>- tfm-rubygem-hammer_cli-0.10.0-1.el7.noarch
>- tfm-rubygem-hammer_cli_foreman-0.10.0-1.el7.noarch
>- tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-5.el7.noarch
>- tfm-rubygem-hammer_cli_foreman_docker-0.0.4-2.el7.noarch
>- tfm-rubygem-hammer_cli_foreman_tasks-0.0.10-2.fm1_12.el7.noarch
>- tfm-rubygem-hammer_cli_import-0.11.3-1.el7.noarch
>- tfm-rubygem-hammer_cli_katello-0.10.0-1.el7.noarch
>- tfm-rubygem-hashie-2.0.5-4.el7.noarch
>- tfm-rubygem-highline-1.7.8-2.el7.noarch
>- tfm-rubygem-http-cookie-1.0.2-1.el7.noarch
>- tfm-rubygem-ipaddress-0.8.0-9.el7.noarch
>- tfm-rubygem-jquery-ui-rails-4.1.2-5.el7.noarch
>- tfm-rubygem-katello-3.4.0.2-2.el7.noarch
>- tfm-rubygem-ldap_fluff-0.4.6-1.el7.noarch
>- tfm-rubygem-little-plugger-1.1.3-21.el7.noarch
>- tfm-rubygem-locale-2.0.9-11.el7.noarch
>- tfm-rubygem-logging-1.8.2-4.el7.noarch
>- tfm-rubygem-net-ldap-0.15.0-1.el7.noarch
>- tfm-rubygem-net-ping-2.0.1-1.el7.noarch
>- tfm-rubygem-net-scp-1.1.0-6.el7.noarch
>- tfm-rubygem-net-ssh-4.0.1-1.el7.noarch
>- tfm-rubygem-netrc-0.7.7-7.el7.noarch
>- tfm-rubygem-oauth-0.5.1-1.el7.noarch
>- tfm-rubygem-parse-cron-0.1.4-2.fm1_11.el7.noarch
>- tfm-rubygem-passenger-4.0.18-9.11.el7.x86_64
>- tfm-rubygem-passenger-native-4.0.18-9.11.el7.x86_64
>- tfm-rubygem-passenger-native-libs-4.0.18-9.11.el7.x86_64
>- tfm-rubygem-pg-0.15.1-3.el7.x86_64
>- tfm-rubygem-powerbar-1.0.17-1.el7.noarch
>- tfm-rubygem-protected_attributes-1.1.3-3.el7.noarch
>- tfm-rubygem-qpid_messaging-0.34.1-1.el7.x86_64
>- tfm-rubygem-rabl-0.12.0-2.el7.noarch
>- tfm-rubygem-rack-jsonp-1.3.1-5.el7.noarch
>- tfm-rubygem-rails-i18n-4.0.9-1.el7.noarch
>- tfm-rubygem-rails-observers-0.1.2-7.el7.noarch
>- tfm-rubygem-rainbow-2.2.1-1.el7.noarch
>- tfm-rubygem-rbvmomi-1.10.0-1.el7.noarch
>- tfm-rubygem-responders-2.3.0-1.el7.noarch
>- tfm-rubygem-rest-client-1.8.0-1.el7.noarch
>- tfm-rubygem-roadie-3.2.1-1.el7.noarch
>- tfm-rubygem-roadie-rails-1.1.1-1.el7.noarch
>- tfm-rubygem-robotex-1.0.0-19.el7.noarch
>- tfm-rubygem-ruby2ruby-2.1.3-4.el7.noarch
>- tfm-rubygem-ruby_parser-3.6.3-4.el7.noarch
>- tfm-rubygem-runcible-1.11.0-1.el7.noarch
>- tfm-rubygem-safemode-1.3.1-1.el7.noarch
>- tfm-rubygem-scoped_search-4.1.0-1.el7.noarch
>- tfm-rubygem-secure_headers-3.4.1-1.el7.noarch
>- tfm-rubygem-sequel-4.20.0-5.el7.noarch
>- tfm-rubygem-sexp_processor-4.4.4-3.el7.noarch
>- tfm-rubygem-sshkey-1.9.0-1.el7.noarch
>- tfm-rubygem-trollop-2.1.2-1.el7.noarch
>- tfm-rubygem-unf-0.1.3-5.el7.noarch
>- tfm-rubygem-unf_ext-0.0.6-6.el7.x86_64
>- tfm-rubygem-unicode-display_width-1.0.5-1.el7.noarch
>- tfm-rubygem-useragent-0.16.8-1.el7.noarch
>- tfm-rubygem-validates_lengths_from_database-0.5.0-3.el7.noarch
>- tfm-rubygem-webpack-rails-0.9.8-1.el7.noarch
>- tfm-rubygem-wicked-1.1.0-4.el7.noarch
>- tfm-rubygem-will_paginate-3.1.5-1.el7.noarch
>- tfm-rubygem-x-editable-rails-1.5.5-1.el7.noarch
>- tfm-runtime-3.2-9.el7.x86_64
>
> I am pretty new to all this but have been tasked with resolving the issue.
> If the only solution is to update to the latest release then we will have
> to eventually go with that, but if there is a solution that can used before
> getting to that stage, that would be greatly helpful.
>
> Katello-agent/goferd is running on all the hosts.
>
> Any other info needed please let me know.
>
> Cheers!
>
> Jasper
>
> --
> You received this

[foreman-users] Katello 3.4.5 Released

[Eric D 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.

Re: [foreman-users] Foreman Katello install 3.4 issue with db:migrate and bastion plugin

[Eric D Helms]

That should be fixed now, yum clean all to be safe and then yum upgrade to
ensure you have tfm-rubygem-bastion 5 .0.10.



On Aug 26, 2017 3:57 PM, "Jasper Connery"  wrote:

> On a CentOS 7 server I'm currently trying to install Katello using the 3.4
> guide found here: https://theforeman.org/plugins/katello/3.4/
> installation/index.html, but seem to be running into some errors. I had
> previously installed 3.2 (without realising I wasn't installing the latest
> version) but due to some non-katello issues had to uninstall, so now I have
> gone to 3.4.
>
> But when I get to the *foreman-installer --scenario katello
> --disable-system-checks* the install fails and a whole lot of error
> messages appear, and the lines that stand out the most are:
>
>  /Stage[main]/Foreman::Database/Foreman::Rake[db:
> migrate]/Exec[foreman-rake-db:migrate]: Failed to call refresh:
> /usr/sbin/foreman-rake db:migrate returned 1 instead of one of [0]
>  /Stage[main]/Foreman::Database/Foreman::Rake[db:
> migrate]/Exec[foreman-rake-db:migrate]: /usr/sbin/foreman-rake db:migrate
> returned 1 instead of one of [0]
>
> and
>
>  
> /Stage[main]/Katello::Config::Pulp_client/Foreman_config_entry[pulp_client_cert]/value:
> change from  to /etc/pki/katello/certs/pulp-client.crt failed: Execution
> of '/usr/sbin/foreman-rake -- config -k 'pulp_client_cert' -v
> '/etc/pki/katello/certs/pulp-client.crt'' returned 1: rake aborted!
> Foreman::PluginRequirementError: ERF72-1622 [Foreman::PluginRequirementError]:
> bastion plugin requires Foreman >= 1.16 but current is 1.15.3
> /usr/share/foreman/app/services/foreman/plugin.rb:143:in
> `requires_foreman'
> /opt/theforeman/tfm/root/usr/share/gems/gems/bastion-5.0.9/lib/bastion/engine.rb:48:in
> `block (2 levels) in '
>
> I'm new to Katello and foreman, and don't have much more experience with
> Linux but I've been given this task and trying to work my way through it
> all.
>
> I have not been able to locate too much info about the bastion dependency
> error so if anyone has any ideas, that would be greatly appreciated!
>
> --
> 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.
>

-- 
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] UPG 2.4.4 to 3.4.4: Upgrade step migrate_foreman failed

[Eric D Helms]

Thats a tough spot, as you are upgrading through a lot of versions. I would
recommend trying to upgrade sequentially to at least 3.2 before jumping up
to 3.4. We only test upgrading as far back as N-2.

Eric

On Thu, Aug 24, 2017 at 3:58 AM, <ehart...@gmail.com> wrote:

> Dear all,
>
> can someone help me to upgrade my Katello from 2.4.4 to 3.4.4, I´m getting
> now the following:
>
> [ERROR 2017-08-23 22:20:58 main] foreman-rake -- config -k use_pulp_oauth
> -v true >/dev/null failed! Check the output for error!
> [DEBUG 2017-08-23 22:21:12 main] API controllers newer than Apipie cache!
> Run apipie:cache rake task to regenerate cache.
> [DEBUG 2017-08-23 22:21:44 main] rake aborted!
> [DEBUG 2017-08-23 22:21:44 main] StandardError: An error has occurred,
> this and all later migrations canceled:
> [DEBUG 2017-08-23 22:21:44 main]
> [DEBUG 2017-08-23 22:21:44 main] The single-table inheritance mechanism
> failed to locate the subclass: 'Katello::System'. This error is raised
> because the column 'type' is reserved for storing the class in case of
> inheritance. Please rename this column if you didn't intend it to be used
> for storing the inheritance class or overwrite
> HostCollectionToHosts::System.inheritance_column to use another column
> for that information./opt/rh/sclo-ror42/root/usr/share/gems/
> gems/activerecord-4.2.5.1/lib/active_record/inheritance.rb:186:in `rescue
> in find_sti_class'
> [DEBUG 2017-08-23 22:21:44 main] ActiveRecord::SubclassNotFound: The
> single-table inheritance mechanism failed to locate the subclass:
> 'Katello::System'. This error is raised because the column 'type' is
> reserved for storing the class in case of inheritance. Please rename this
> column if you didn't intend it to be used for storing the inheritance class
> or overwrite HostCollectionToHosts::System.inheritance_column to use
> another column for that information.
> [DEBUG 2017-08-23 22:21:44 main] NameError: uninitialized constant
> Katello::System
> [ERROR 2017-08-23 22:21:44 main] foreman-rake db:migrate failed! Check the
> output for error!
> [ERROR 2017-08-23 22:22:02 main] foreman-rake -- config -k use_pulp_oauth
> -v false >/dev/null failed! Check the output for error!
> [ERROR 2017-08-23 22:22:02 main] Upgrade step migrate_foreman failed.
> Check logs for more information.
> [DEBUG 2017-08-23 22:22:02 main] Exit with status code: 1 (signal was 1)
> [ERROR 2017-08-23 22:22:02 main] Errors encountered during run:
> [ERROR 2017-08-23 22:22:02 main] foreman-rake -- config -k use_pulp_oauth
> -v true >/dev/null failed! Check the output for error!
> [ERROR 2017-08-23 22:22:02 main] foreman-rake db:migrate failed! Check the
> output for error!
> [ERROR 2017-08-23 22:22:02 main] foreman-rake -- config -k use_pulp_oauth
> -v false >/dev/null failed! Check the output for error!
> [ERROR 2017-08-23 22:22:02 main] Upgrade step migrate_foreman failed.
> Check logs for more information.
>
> Thanks,
> Christian
>
> --
> 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.
>



-- 
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] Katello 3.4 fixed with new Bastion release

[Eric D Helms]

All,

Some have reported a broken issue with a new version of tfm-rubygem-bastion
breaking Katello installs and upgrades. I have pushed out an updated
version of the plugin (5.0.10) that is now available in the plugins. Please
upgrade to it and re-run your workflows.

My sincerest apologies for breaking everyone.


-- 
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] [katello 2.4] passenger status broken

[Eric D Helms]

> [root@katello-test emanners]# cat /etc/redhat-release
>>>>> CentOS Linux release 7.2.1511 (Core)
>>>>> [root@katello-test emanners]# which passenger-status
>>>>> /sbin/passenger-status
>>>>> [root@katello-test emanners]# rpm -q --whatprovides
>>>>> /usr/sbin/passenger-status
>>>>> passenger-4.0.53-4.el7.x86_64
>>>>> [root@katello-test emanners]# /usr/sbin/passenger-status
>>>>> ERROR: Phusion Passenger doesn't seem to be running.
>>>>>
>>>>> I've managed to find a few posts on Google (not Katello related) that
>>>>> suggest the reason is multiple copies of passenger on the host.
>>>>> [root@katello-test ~]# locate passenger-status
>>>>> /opt/theforeman/tfm/root/usr/bin/passenger-status
>>>>> /opt/theforeman/tfm/root/usr/share/gems/gems/passenger-4.0.1
>>>>> 8/bin/passenger-status
>>>>> /opt/theforeman/tfm/root/usr/share/man/man8/passenger-status.8.gz
>>>>>
>>>>
>>>> This set of passenger libraries are used for running the Foreman web
>>>> application under Apache within the SCL. To run the passenger-status
>>>> command for the SCL, you'd need to enable the SCL and run it:
>>>>
>>>> scl enable tfm '/opt/theforeman/tfm/root/usr/bin/passenger-status'
>>>>
>>>>
>>>>> /usr/sbin/passenger-status
>>>>> /usr/share/man/man8/passenger-status.8.gz
>>>>>
>>>>
>>>> This set of passenger libraries are used for running the puppetmaster
>>>> that is installed on the server by default which is running outside the SC
>>>> and should work like normal (barring a bug in newer passenger).
>>>>
>>>>
>>>>> [root@katello-test ~]# /opt/theforeman/tfm/root/usr/b
>>>>> in/passenger-status
>>>>> /opt/rh/ruby193/root/usr/bin/ruby: error while loading shared
>>>>> libraries: libruby.so.1.9: cannot open shared object file: No such file or
>>>>> directory
>>>>> [root@katello-test ~]# /opt/theforeman/tfm/root/usr/s
>>>>> hare/gems/gems/passenger-4.0.18/bin/passenger-status
>>>>> *** Phusion Passenger: no passenger_native_support.so found for the
>>>>> current Ruby interpreter. Compiling one (set 
>>>>> PASSENGER_COMPILE_NATIVE_SUPPORT_BINARY=0
>>>>> to disable)...
>>>>> # mkdir -p /root/.passenger/native_support/4.0.18/ruby-2.0.0-x86_64-
>>>>> linux
>>>>> # cd /root/.passenger/native_support/4.0.18/ruby-2.0.0-x86_64-linux
>>>>> # /usr/bin/ruby '/opt/theforeman/tfm/root/usr/
>>>>> share/gems/gems/passenger-4.0.18/ruby_extension_source/extconf.rb'
>>>>> /usr/bin/ruby: No such file or directory --
>>>>> /opt/theforeman/tfm/root/usr/share/gems/gems/passenger-4.0.1
>>>>> 8/ruby_extension_source/extconf.rb (LoadError)
>>>>> Compilation failed.
>>>>> ---
>>>>> Ruby native_support extension not loaded. Continuing without
>>>>> native_support.
>>>>> ERROR: Phusion Passenger doesn't seem to be running.
>>>>>
>>>>>
>>>>> So the question is which ones does Katello really need since they were
>>>>> both installed during the installer and how do I get this command working
>>>>> again without breaking the underlying app?
>>>>> --
>>>>> 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
>>>> Ph.D. Student - North Carolina State University
>>>>
>>> --
>> 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/to
>> pic/foreman-users/rWnFdRzy3Zg/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 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.
>



-- 
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] Re: Katello 2.4.2 -> 3.0.0 upgrade broke katello-agent everywhere

[Eric D Helms]

gt; Jun 28 21:48:13 ipatest.internal goferd[13681]: [ERROR][worker-0]
>>> gofer.messaging.adapter.connect:33 - connect:
>>> proton+amqps://katello.internal:5647, failed: Connection
>>> amqps://katello.internal.resi
>>> Jun 28 21:48:13 ipatest.internal goferd[13681]: [INFO][worker-0]
>>> gofer.messaging.adapter.connect:35 - retry in 12 seconds
>>
>>
>> There's no firewall involved here and I am able to see a connection
>> establish and then go away on 5647 on both machines. They are able to
>> telnet to each other on 5647 as well, and I was able to repro with selinux
>> off on both and firewalld off.
>>
>> Curious, I hopped over to katello.internal and enabled / looked at the
>> qdrouterd log:
>>
>>> Tue Jun 28 21:47:42 2016 SERVER (debug) Accepting incoming connection
>>> from ipatest.internal:55332 to 0.0.0.0:5647
>>> Tue Jun 28 21:47:42 2016 SERVER (trace) Configuring SSL on incoming
>>> connection from  ipatest.internal:55332 to 0.0.0.0:5647
>>> Tue Jun 28 21:47:42 2016 ROUTER_HELLO (trace) SENT:
>>> HELLO(id=katello.internal area=0 inst=1467138250 seen=[])
>>> Tue Jun 28 21:47:43 2016 ROUTER_HELLO (trace) SENT:
>>> HELLO(id=katello.internal area=0 inst=1467138250 seen=[])
>>> Tue Jun 28 21:47:45 2016 ROUTER_HELLO (trace) SENT:
>>> HELLO(id=katello.internal area=0 inst=1467138250 seen=[])
>>> Tue Jun 28 21:47:46 2016 ROUTER_HELLO (trace) SENT:
>>> HELLO(id=katello.internal area=0 inst=1467138250 seen=[])
>>> Tue Jun 28 21:47:47 2016 ROUTER_HELLO (trace) SENT:
>>> HELLO(id=katello.internal area=0 inst=1467138250 seen=[])
>>
>>
>> So I thought I'd check ssl, from the ipatest box I did a:
>> openssl s_client -connect katello.internal:5647 -cert
>> /etc/pki/consumer/bundle.pem -key /etc/pki/consumer/bundle.pem -CAfile
>> /etc/rhsm/ca/katello-default-ca.pem -state -debug
>> and everything seemed to come back OK.
>>
>> Thought maybe it was something underlying in qpidd, and I did find errors
>> in that log, but not sure if they're related:
>>
>>> Jun 28 15:25:35 katello.internal qpidd[18457]: 2016-06-28 15:25:35
>>> [System] error Connection qpid No protocol received closing
>>> Jun 28 15:25:35 katello.internal qpidd[18457]: 2016-06-28 15:25:35
>>> [System] error Connection qpid No protocol received closing
>>> Jun 28 15:26:20 katello.internal qpidd[18457]: 2016-06-28 15:26:20
>>> [System] error Connection qpid No protocol received closing
>>> Jun 28 15:26:20 katello.internal qpidd[18457]: 2016-06-28 15:26:20
>>> [System] error Connection qpid No protocol received closing
>>>
>>
>> The agents show as up as active, but any commands fail.
>>
>> Anyone have any ideas?
>>
>> Best,
>> --Nick Cammorato
>>
> --
> 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.
>



-- 
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] Katello 3.4.4 Released

[Eric D Helms]

What happens if you rerun the installer? Does it succeed?

On Aug 16, 2017 7:16 AM, "Louis Bohm" <louisb...@gmail.com> wrote:

Any suggestions since my last post?  Should I revert the VM and start over?

Louis

On Aug 15, 2017, at 12:33 PM, Louis Bohm <louisb...@gmail.com> wrote:

I commented out the Listen 443 line from /etc/httpd/conf.d/ports.conf.

Louis

On Aug 15, 2017, at 12:23 PM, Eric D Helms <eric.d.he...@gmail.com> wrote:

Which one did you remove? The one from sleeping.conf?


On Aug 15, 2017 12:12 PM, "Louis Bohm" <louisb...@gmail.com> wrote:

> OK.  I see what you are saying and that is what I ran:  foreman-installer
> --scenario katello —upgrade
>
> When I run foreman-installer --scenario katello —upgrade apache fails to
> start up.  When I fist look at the logs I see this:
>
> Aug 15 09:22:45 fm httpd: (98)Address already in use: AH00072: make_sock:
> could not bind to address 0.0.0.0:443
>
>
> If I remove one of the Listen 443 in the configurations and manually start
> apache with katello-services —only httpd I then get these errors:
>
> [Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No such
> file or directory: AH01515: mod_mime_magic: can't read magic file
> /etc/httpd/NEVER_EVER_USE
> [Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init:
> Name-based SSL virtual hosts only work for clients with TLS server name
> indication support (RFC 4366)
> [Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232:
> suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
> [ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:538
> ]: Options: { 'analytics_log_user' => 'nobody', 'default_group' =>
> 'nobody', 'default_python' => 'python', 'default_ruby' => 'ruby',
> 'default_user' => 'nobody', 'log_level' => '0', 'max_pool_size' => '12',
> 'passenger_root' => '/usr/share/passenger//phusion_passenger/locations.ini',
> 'passenger_version' => '4.0.53', 'pool_idle_time' => '300', 'prestart_urls'
> => 'aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29
> tOjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=', 'temp_dir' => '/tmp',
> 'union_station_gateway_address' => 'gateway.unionstationapp.com',
> 'union_station_gateway_port' => '443', 'user_switching' => 'true',
> 'web_server_passenger_version' => '4.0.53', 'web_server_pid' => '2600',
> 'web_server_type' => 'apache', 'web_server_worker_gid' => '48',
> 'web_server_worker_uid' => '48' }
> [ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780 agents/HelperAgent/Main.cpp:650
> ]: PassengerHelperAgent online, listening at unix:/tmp/passenger.1.0.2600/g
> eneration-0/request
> [ 2017-08-15 09:25:32.6930 2609/7fd0539ea880 agents/LoggingAgent/Main.cpp:321
> ]: PassengerLoggingAgent online, listening at unix:/tmp/passenger.1.0.2600/g
> eneration-0/logging
> [ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:728
> ]: All Phusion Passenger agents started!
> [Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module
> access_compat_module is already loaded, skipping
> [Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module
> actions_module is already loaded, skipping
> [Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module
> alias_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module
> auth_basic_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module
> auth_digest_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module
> authn_anon_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module
> authn_core_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module
> authn_dbm_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module
> authn_file_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module
> authz_core_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module
> authz_dbm_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749125 2017] [so:warn] [pid 2600] AH01574: module
> authz_groupfile_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749143 2017] [so:warn] [pid 2600] AH01574: module
> authz_host_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749164 2017] [so:warn] [pid 2600] AH01574: module
> authz_owner_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749263 2017] [so:warn] [pid 2600] AH

Re: [foreman-users] Katello 3.4.4 Released

[Eric D Helms]

t; from /usr/share/passenger/helper-scripts/prespawn:153:in `'
> /usr/share/passenger/helper-scripts/prespawn:113:in `initialize': No
> route to host - connect(2) (Errno::EHOSTUNREACH)
> from /usr/share/passenger/helper-scripts/prespawn:113:in `new'
> from /usr/share/passenger/helper-scripts/prespawn:113:in `rescue in
> connect'
> from /usr/share/passenger/helper-scripts/prespawn:111:in `connect'
> from /usr/share/passenger/helper-scripts/prespawn:120:in `connect'
> from /usr/share/passenger/helper-scripts/prespawn:87:in `socket'
> from /usr/share/passenger/helper-scripts/prespawn:91:in `head_request'
> from /usr/share/passenger/helper-scripts/prespawn:153:in `'
> /usr/share/passenger/helper-scripts/prespawn:113:in `initialize': No
> route to host - connect(2) (Errno::EHOSTUNREACH)
> from /usr/share/passenger/helper-scripts/prespawn:113:in `new'
> from /usr/share/passenger/helper-scripts/prespawn:113:in `rescue in
> connect'
> from /usr/share/passenger/helper-scripts/prespawn:111:in `connect'
> from /usr/share/passenger/helper-scripts/prespawn:120:in `connect'
> from /usr/share/passenger/helper-scripts/prespawn:87:in `socket'
> from /usr/share/passenger/helper-scripts/prespawn:91:in `head_request'
> from /usr/share/passenger/helper-scripts/prespawn:153:in `’
>
>
> Louis
>
> On Aug 15, 2017, at 12:06 PM, Eric D Helms <eric.d.he...@gmail.com> wrote:
>
> I did not see anything included. But every upgrade both minor and patch,
> since before 2.4 has required using the installer with --upgrade.
>
> Per -- https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>
> Check Step 5
>
> On Aug 15, 2017 12:03 PM, "Louis Bohm" <louisb...@gmail.com> wrote:
>
>> Here is the documentation and it does not show it.  I also do not
>> remember it when I went from 3.2 to 3.3.  But I will run it.
>>
>> Louis
>>
>> On Aug 15, 2017, at 11:59 AM, Eric D Helms <eric.d.he...@gmail.com>
>> wrote:
>>
>> Absolutely, every time. Can you double check? Or show a screenshot of
>> what you looked at that didn't have it?
>>
>>
>> On Aug 15, 2017 11:48 AM, "Louis Bohm" <louisb...@gmail.com> wrote:
>>
>>> No.  Its not on the Katello upgrade page.  Am I supposed to?
>>>
>>> Louis
>>>
>>> On Aug 15, 2017, at 10:59 AM, Eric D Helms <ericdhe...@gmail.com> wrote:
>>>
>>> You ran 'foreman-installer --upgrade' once you updated the RPMs?
>>>
>>> On Tue, Aug 15, 2017 at 9:31 AM, Louis Bohm <louisb...@gmail.com> wrote:
>>>
>>>> I re-ran the foreman-installer —scenario katello —upgrade and it got as
>>>> far as apache.  The apache upgrade failed.  The foreman log says this:
>>>>
>>>> Aug 15 09:22:45 fm httpd: (98)Address already in use: AH00072:
>>>> make_sock: could not bind to address 0.0.0.0:443
>>>> Aug 15 09:22:45 fm httpd: no listening sockets available, shutting down
>>>>
>>>>
>>>> So I took a look and noticed that Listen 443 was listed twice.  Once in
>>>> /etc/httpd/conf/ports.conf and /etc/httpd/conf.d/ssl.conf.  Thats not
>>>> good.  So I commented out the one in ports.conf and restarted it.
>>>>
>>>> Now when it fails I get a log more information.  From
>>>> /var/log/httpd/error_log I see:
>>>>
>>>> [Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No
>>>> such file or directory: AH01515: mod_mime_magic: can't read magic file
>>>> /etc/httpd/NEVER_EVER_USE
>>>> [Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init:
>>>> Name-based SSL virtual hosts only work for clients with TLS server name
>>>> indication support (RFC 4366)
>>>> [Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232:
>>>> suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
>>>> [ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780
>>>> agents/Watchdog/Main.cpp:538 ]: Options: { 'analytics_log_user' =>
>>>> 'nobody', 'default_group' => 'nobody', 'default_python' => 'python',
>>>> 'default_ruby' => 'ruby', 'default_user' => 'nobody', 'log_level' => '0',
>>>> 'max_pool_size' => '12', 'passenger_root' => 
>>>> '/usr/share/passenger//phusion_passenger/locations.ini',
>>>> 'passenger_version' => '4.0.53', 'pool_idle_time' => '300', 'prestart_urls'
>>>> => 'aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29
>>>> tOjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=', 'temp_dir' => '/tmp',
>>>&

Re: [foreman-users] Katello 3.4.4 Released

[Eric D Helms]

I did not see anything included. But every upgrade both minor and patch,
since before 2.4 has required using the installer with --upgrade.

Per -- https://theforeman.org/plugins/katello/3.4/upgrade/index.html

Check Step 5

On Aug 15, 2017 12:03 PM, "Louis Bohm" <louisb...@gmail.com> wrote:

> Here is the documentation and it does not show it.  I also do not remember
> it when I went from 3.2 to 3.3.  But I will run it.
>
> Louis
>
> On Aug 15, 2017, at 11:59 AM, Eric D Helms <eric.d.he...@gmail.com> wrote:
>
> Absolutely, every time. Can you double check? Or show a screenshot of what
> you looked at that didn't have it?
>
>
> On Aug 15, 2017 11:48 AM, "Louis Bohm" <louisb...@gmail.com> wrote:
>
>> No.  Its not on the Katello upgrade page.  Am I supposed to?
>>
>> Louis
>>
>> On Aug 15, 2017, at 10:59 AM, Eric D Helms <ericdhe...@gmail.com> wrote:
>>
>> You ran 'foreman-installer --upgrade' once you updated the RPMs?
>>
>> On Tue, Aug 15, 2017 at 9:31 AM, Louis Bohm <louisb...@gmail.com> wrote:
>>
>>> I re-ran the foreman-installer —scenario katello —upgrade and it got as
>>> far as apache.  The apache upgrade failed.  The foreman log says this:
>>>
>>> Aug 15 09:22:45 fm httpd: (98)Address already in use: AH00072:
>>> make_sock: could not bind to address 0.0.0.0:443
>>> Aug 15 09:22:45 fm httpd: no listening sockets available, shutting down
>>>
>>>
>>> So I took a look and noticed that Listen 443 was listed twice.  Once in
>>> /etc/httpd/conf/ports.conf and /etc/httpd/conf.d/ssl.conf.  Thats not
>>> good.  So I commented out the one in ports.conf and restarted it.
>>>
>>> Now when it fails I get a log more information.  From
>>> /var/log/httpd/error_log I see:
>>>
>>> [Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No
>>> such file or directory: AH01515: mod_mime_magic: can't read magic file
>>> /etc/httpd/NEVER_EVER_USE
>>> [Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init:
>>> Name-based SSL virtual hosts only work for clients with TLS server name
>>> indication support (RFC 4366)
>>> [Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232:
>>> suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
>>> [ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780
>>> agents/Watchdog/Main.cpp:538 ]: Options: { 'analytics_log_user' =>
>>> 'nobody', 'default_group' => 'nobody', 'default_python' => 'python',
>>> 'default_ruby' => 'ruby', 'default_user' => 'nobody', 'log_level' => '0',
>>> 'max_pool_size' => '12', 'passenger_root' => 
>>> '/usr/share/passenger//phusion_passenger/locations.ini',
>>> 'passenger_version' => '4.0.53', 'pool_idle_time' => '300', 'prestart_urls'
>>> => 'aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29
>>> tOjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=', 'temp_dir' => '/tmp',
>>> 'union_station_gateway_address' => 'gateway.unionstationapp.com',
>>> 'union_station_gateway_port' => '443', 'user_switching' => 'true',
>>> 'web_server_passenger_version' => '4.0.53', 'web_server_pid' => '2600',
>>> 'web_server_type' => 'apache', 'web_server_worker_gid' => '48',
>>> 'web_server_worker_uid' => '48' }
>>> [ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780
>>> agents/HelperAgent/Main.cpp:650 ]: PassengerHelperAgent online,
>>> listening at unix:/tmp/passenger.1.0.2600/generation-0/request
>>> [ 2017-08-15 09:25:32.6930 2609/7fd0539ea880
>>> agents/LoggingAgent/Main.cpp:321 ]: PassengerLoggingAgent online,
>>> listening at unix:/tmp/passenger.1.0.2600/generation-0/logging
>>> [ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780
>>> agents/Watchdog/Main.cpp:728 ]: All Phusion Passenger agents started!
>>> [Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module
>>> access_compat_module is already loaded, skipping
>>> [Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module
>>> actions_module is already loaded, skipping
>>> [Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module
>>> alias_module is already loaded, skipping
>>> [Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module
>>> auth_basic_module is already loaded, skipping
>>> [Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module
>>> auth_digest_module is already loaded, skipping
>>> [Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 

Re: [foreman-users] Katello 3.4.4 Released

[Eric D Helms]

Absolutely, every time. Can you double check? Or show a screenshot of what
you looked at that didn't have it?


On Aug 15, 2017 11:48 AM, "Louis Bohm" <louisb...@gmail.com> wrote:

> No.  Its not on the Katello upgrade page.  Am I supposed to?
>
> Louis
>
> On Aug 15, 2017, at 10:59 AM, Eric D Helms <ericdhe...@gmail.com> wrote:
>
> You ran 'foreman-installer --upgrade' once you updated the RPMs?
>
> On Tue, Aug 15, 2017 at 9:31 AM, Louis Bohm <louisb...@gmail.com> wrote:
>
>> I re-ran the foreman-installer —scenario katello —upgrade and it got as
>> far as apache.  The apache upgrade failed.  The foreman log says this:
>>
>> Aug 15 09:22:45 fm httpd: (98)Address already in use: AH00072: make_sock:
>> could not bind to address 0.0.0.0:443
>> Aug 15 09:22:45 fm httpd: no listening sockets available, shutting down
>>
>>
>> So I took a look and noticed that Listen 443 was listed twice.  Once in
>> /etc/httpd/conf/ports.conf and /etc/httpd/conf.d/ssl.conf.  Thats not
>> good.  So I commented out the one in ports.conf and restarted it.
>>
>> Now when it fails I get a log more information.  From
>> /var/log/httpd/error_log I see:
>>
>> [Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No
>> such file or directory: AH01515: mod_mime_magic: can't read magic file
>> /etc/httpd/NEVER_EVER_USE
>> [Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init:
>> Name-based SSL virtual hosts only work for clients with TLS server name
>> indication support (RFC 4366)
>> [Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232:
>> suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
>> [ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:538
>> ]: Options: { 'analytics_log_user' => 'nobody', 'default_group' =>
>> 'nobody', 'default_python' => 'python', 'default_ruby' => 'ruby',
>> 'default_user' => 'nobody', 'log_level' => '0', 'max_pool_size' => '12',
>> 'passenger_root' => '/usr/share/passenger//phusion_passenger/locations.ini',
>> 'passenger_version' => '4.0.53', 'pool_idle_time' => '300', 'prestart_urls'
>> => 'aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29
>> tOjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=', 'temp_dir' => '/tmp',
>> 'union_station_gateway_address' => 'gateway.unionstationapp.com',
>> 'union_station_gateway_port' => '443', 'user_switching' => 'true',
>> 'web_server_passenger_version' => '4.0.53', 'web_server_pid' => '2600',
>> 'web_server_type' => 'apache', 'web_server_worker_gid' => '48',
>> 'web_server_worker_uid' => '48' }
>> [ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780
>> agents/HelperAgent/Main.cpp:650 ]: PassengerHelperAgent online,
>> listening at unix:/tmp/passenger.1.0.2600/generation-0/request
>> [ 2017-08-15 09:25:32.6930 2609/7fd0539ea880
>> agents/LoggingAgent/Main.cpp:321 ]: PassengerLoggingAgent online,
>> listening at unix:/tmp/passenger.1.0.2600/generation-0/logging
>> [ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:728
>> ]: All Phusion Passenger agents started!
>> [Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module
>> access_compat_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module
>> actions_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module
>> alias_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module
>> auth_basic_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module
>> auth_digest_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module
>> authn_anon_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module
>> authn_core_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module
>> authn_dbm_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module
>> authn_file_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module
>> authz_core_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module
>> authz_dbm_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.749125 2017] [so:warn] [pid 2600] AH01574: module
>> authz_groupfile_

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

[Eric D Helms]

t'
> from /usr/share/passenger/helper-scripts/prespawn:87:in `socket'
> from /usr/share/passenger/helper-scripts/prespawn:91:in `head_request'
> from /usr/share/passenger/helper-scripts/prespawn:153:in `'
> /usr/share/passenger/helper-scripts/prespawn:113:in `initialize': No
> route to host - connect(2) (Errno::EHOSTUNREACH)
> from /usr/share/passenger/helper-scripts/prespawn:113:in `new'
> from /usr/share/passenger/helper-scripts/prespawn:113:in `rescue in
> connect'
> from /usr/share/passenger/helper-scripts/prespawn:111:in `connect'
> from /usr/share/passenger/helper-scripts/prespawn:120:in `connect'
> from /usr/share/passenger/helper-scripts/prespawn:87:in `socket'
> from /usr/share/passenger/helper-scripts/prespawn:91:in `head_request'
> from /usr/share/passenger/helper-scripts/prespawn:153:in `'
> /usr/share/passenger/helper-scripts/prespawn:113:in `initialize': No
> route to host - connect(2) (Errno::EHOSTUNREACH)
> from /usr/share/passenger/helper-scripts/prespawn:113:in `new'
> from /usr/share/passenger/helper-scripts/prespawn:113:in `rescue in
> connect'
> from /usr/share/passenger/helper-scripts/prespawn:111:in `connect'
> from /usr/share/passenger/helper-scripts/prespawn:120:in `connect'
> from /usr/share/passenger/helper-scripts/prespawn:87:in `socket'
> from /usr/share/passenger/helper-scripts/prespawn:91:in `head_request'
> from /usr/share/passenger/helper-scripts/prespawn:153:in `'
>
> Starting at the top I do not see the module mod_mime_magic being loaded
> from any of the conf files.
>
> Any ideas on what I do now?
>
> Louis
>
> On Aug 15, 2017, at 9:06 AM, Louis Bohm <louisb...@gmail.com> wrote:
>
> As with mongodb postgresql was also complaining about its pid directory:
>
> Aug 15 09:02:35 fm systemd: Starting PostgreSQL database server...
> Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT LOG:  could not bind
> IPv6 socket: Cannot assign requested address
> Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT HINT:  Is another
> postmaster already running on port 5432? If not, wait a few seconds and
> retry.
> Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT FATAL:  could not
> create lock file "/var/run/postgresql/.s.PGSQL.5432.lock": No such file
> or directory
> Aug 15 09:02:36 fm pg_ctl: pg_ctl: could not start server
> Aug 15 09:02:36 fm pg_ctl: Examine the log output.
>
> And again once i created the dir /var/run/postgresql and set its
> perms/owner/group postgresql starts up fine.
>
> Louis
>
> On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote:
>>
>> 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 a topic in the
> Google Groups "Foreman users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/foreman-users/Gmo72QQW86A/unsubscribe.
> To unsubscribe from this group and all its topics, 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.
>
>
> --
> 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.
>



-- 
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] Re: Katello 3.4.4 Released

[Eric D Helms]

:
>> 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.
>



-- 
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] Re: Katello 3.4.4 Released

[Eric D Helms]

On Mon, Aug 14, 2017 at 12:14 PM, Louis Bohm <louisb...@gmail.com> wrote:

>
> Having major issues upgrading from Katello 3.3 to 3.4 on CentOS 7.3.1611.
>
> For starters running: yum update -y http://fedorapeople.org/
> groups/katello/releases/yum/3.4/katello/el7/x86_64/katello-
> repos-latest.rpm fails because http-parser and http-parser-devel are not
> found.  I found them and had to manually install them.
>

This one is strange, as it appears they pulled these packages from EPEL :/
We'll have to investigate this further.


>
> Then yum update -y http://yum.theforeman.org/releases/1.15/el7/x86_64/
> foreman-release.rpm fails because I have foreman-plugin-1.14.3-1.el7.noarch.
> Cannot update the plugins because foreman-release has not been upgraded.  I
> am running this on a VM so I tried to remove foreman-plugin and go that
> way.  But that failed miserably.  I have tried just manually changing the
> version numbers in the foreman repos from 1.14 to 1.15 but still same
> errors.
>
>
Can you give more information regarding your first statement? Why does that
first statement fail? Got yum output?


> Whats the fix for this???  I have to say going from Katello 3.2 to 3.3 was
> no where nearly as difficult as this.
>
> Louis
> On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote:
>>
>> 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.
>



-- 
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] Re: Katello 3.4.4 Released

[Eric D Helms]

Few questions to help us debug:

 1) Are all repos missing from the UI? Just custom? Just red hat repos?
 2) Do clients have repo access still?

On Aug 9, 2017 3:31 AM, "'Denis Müller' via Foreman users" <
foreman-users@googlegroups.com> wrote:

> 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.
>

-- 
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: [Katello] Pulp repos sync on schedule but not showing in katello

[Eric D Helms]

Couple of follow up questions to help us:

 1) Are you using custom certificates?
 2) What version of python-requests is on the box? Both from yum and pip's
perspective?

On Fri, Aug 4, 2017 at 9:11 AM, Anthony Chevalet <anthony.cheva...@gmail.com
> wrote:

> ps: Initially it was working fine, I suspect it stopped working since I've
> created a proxy content.
>
> 2017-08-04 12:58 GMT+02:00 Anthony Chevalet <anthony.cheva...@gmail.com>:
>
>> Hi Eric,
>>
>> When syncing on schedule, there is no task in Foreman. I can see the
>> tasks only for manual sync.
>>
>> In both cases (on schedule or manual) the post sync occurs but seems to
>> fail:
>>
>> Aug  4 10:45:16 p-infra-katello pulp[1045]: celery.worker.strategy:INFO:
>> Received task: pulp.server.async.tasks._queue
>> _reserved_task[86c84b8d-f592-49e0-901e-855267ffb428]
>> Aug  4 10:45:16 p-infra-katello pulp[1198]: celery.worker.job:INFO: Task
>> pulp.server.managers.repo.sync.sync[244bbfe1-b12a-4a5a-b757-3693d1b1d953]
>> succeeded in 15.983295023s: > at 0xd71dd10>
>> Aug  4 10:45:16 p-infra-katello pulp[1198]: celery.worker.strategy:INFO:
>> Received task: pulp.server.managers.repo.publ
>> ish.publish[1a6279a3-925e-4c45-9fc8-5117e9aa0bf7]
>> Aug  4 10:45:16 p-infra-katello pulp[1198]: celery.worker.strategy:INFO:
>> Received task: pulp.server.async.tasks._release_resource[9df9a54e-b18c-
>> 4b31-9696-d9990481cc1f]
>> Aug  4 10:45:16 p-infra-katello celery[1198]: Exception in thread
>> Thread-184:
>> Aug  4 10:45:16 p-infra-katello celery[1198]: Traceback (most recent call
>> last):
>> Aug  4 10:45:16 p-infra-katello celery[1198]: File
>> "/usr/lib64/python2.7/threading.py", line 811, in __bootstrap_inner
>> Aug  4 10:45:16 p-infra-katello celery[1198]: self.run()
>> Aug  4 10:45:16 p-infra-katello celery[1198]: File
>> "/usr/lib64/python2.7/threading.py", line 764, in run
>> Aug  4 10:45:16 p-infra-katello celery[1198]: self.__target(*self.__args,
>> **self.__kwargs)
>> Aug  4 10:45:16 p-infra-katello celery[1198]: File
>> "/usr/lib/python2.7/site-packages/pulp/server/event/http.py", line 58,
>> in _send_post
>> Aug  4 10:45:16 p-infra-katello celery[1198]: response = post(url,
>> data=json_body, auth=auth, headers={'Content-Type': 'application/json'})
>> Aug  4 10:45:16 p-infra-katello celery[1198]: File
>> "/usr/lib/python2.7/site-packages/requests/api.py", line 112, in post
>> Aug  4 10:45:16 p-infra-katello celery[1198]: return request('post', url,
>> data=data, json=json, **kwargs)
>> Aug  4 10:45:16 p-infra-katello celery[1198]: File
>> "/usr/lib/python2.7/site-packages/requests/api.py", line 58, in request
>> Aug  4 10:45:16 p-infra-katello celery[1198]: return
>> session.request(method=method, url=url, **kwargs)
>> Aug  4 10:45:16 p-infra-katello celery[1198]: File
>> "/usr/lib/python2.7/site-packages/requests/sessions.py", line 502, in
>> request
>> Aug  4 10:45:16 p-infra-katello celery[1198]: resp = self.send(prep,
>> **send_kwargs)
>> Aug  4 10:45:16 p-infra-katello celery[1198]: File
>> "/usr/lib/python2.7/site-packages/requests/sessions.py", line 612, in
>> send
>> Aug  4 10:45:16 p-infra-katello celery[1198]: r = adapter.send(request,
>> **kwargs)
>> Aug  4 10:45:16 p-infra-katello celery[1198]: File
>> "/usr/lib/python2.7/site-packages/requests/adapters.py", line 504, in
>> send
>> Aug  4 10:45:16 p-infra-katello celery[1198]: raise ConnectionError(e,
>> request=request)
>> Aug  4 10:45:16 p-infra-katello celery[1198]: ConnectionError:
>> HTTPSConnectionPool(host='p-infra-katello.ks.net', port=443): Max
>> retries exceeded with url: /katello/api/v2/repositories/s
>> ync_complete?token=Byitjkvw92TpyWBHS2cdmHvbwMneMktQ (Caused by
>> SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify
>> failed (_ssl.c:579)'),))
>>
>> Even with this error, manual sync correctly updates the status.
>>
>> If I run it manually:
>> $ curl -X POST -u admin -H Content-Type:application/json
>> https://p-infra-katello.ks.net/katello/api/v2/repositories/
>> sync_complete?token=Byitjkvw92TpyWBHS2cdmHvbwMneMktQ
>> Enter host password for user 'admin':
>> {"displayMessage":"undefined method `[]' for
>> nil:NilClass","errors":["undefined method `[]' for nil:NilClass"]}
>>
>>
>>
>>
>>
>> 2017-08-03 20:01 GMT+02:00 Eric D Helms <eric.d.he...@gmail.com>:
>>
>>> I'll shed a little light on what should

Re: [foreman-users] Re: LCE or CV/CCV package differentials

[Eric D Helms]

There are existing issues around this large feature and an RFC if you'd
like to contribute via review:

https://github.com/theforeman/rfcs/pull/17

I've written a script using both hammer and apipie to do comparisons I
could share.

On Aug 3, 2017 7:35 PM, "Lachlan Musicman"  wrote:

>
> On 3 August 2017 at 22:42, Greg Sutcliffe 
> wrote:
>
>> On Wed, 2017-08-02 at 13:02 +1000, Lachlan Musicman wrote:
>> > On the "I wish" pile.
>>
>> Maybe also add it to our "I wish" pile too? :)
>>
>> http://projects.theforeman.org/projects/katello/issues/new
>>
>
> http://projects.theforeman.org/issues/20501
>
>
>
>
> --
> "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic
> civics is the insistence that we cannot ignore the truth, nor should we
> panic about it. It is a shared consciousness that our institutions have
> failed and our ecosystem is collapsing, yet we are still here — and we are
> creative agents who can shape our destinies. Apocalyptic civics is the
> conviction that the only way out is through, and the only way through is
> together. "
>
> *Greg Bloom* @greggish https://twitter.com/greggish/
> status/873177525903609857
>
> --
> 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.
>

-- 
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: [Katello] Pulp repos sync on schedule but not showing in katello

[Eric D Helms]

I'll shed a little light on what should be happening. When the sync plan
kicks off, it kicks off async by Pulp. The system configures Pulp to have
an http notifier so that when Pulp finished it notifies Katello which
triggers a sync task to index and update new content t for the repositories.

The most obvious thing to check is if you see tasks that result from this
and if you see API hits to Katello for the sync notification URL. You can
find this in /etc/foreman/plugins/katello.yaml.

We need to figure out if Pulp is hitting Katello and the errors like there
or if Pulp is not configured to http notify.

On Aug 3, 2017 9:13 AM, "Anthony Chevalet" 
wrote:

> Hello,
>
> Any news on this? Bug report?
> I have the same behavior for ages (katello 3.0?), and it's still there
> with foreman 1.15.2/Katello 3.4.3.
>
> Thanks,
> Anthony
>
> Le vendredi 31 mars 2017 22:41:46 UTC+2, Alan Evans a écrit :
>>
>> Hello,
>>
>> I am using Katello 3.3/Foreman 1.14.2.  I have a fresh install and I
>> created new Sync plan, product and repos with hammer.  At first I didn't
>> think the jobs were running at all, but I read a thread here that got me
>> looking at things and I found that pulp is in fact syncing on schedule but
>> the results aren't appearing in the katello UI/Hammer CLI.  I suspect there
>> is some kind of post sync job that has to happen that isn't.  If I manually
>> sync them from the UI then the UI is updated.
>>
>> Thoughts?
>>
>> -Alan
>>
>>
>>
>>
>> --
> 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.
>

-- 
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.4.4 Released

[Eric D 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] Help with plugin - Gem loading error: cannot load such file

[Eric D Helms]

Hey Josh,

Is that error line the only stack trace there is?

On Jul 19, 2017 2:29 PM, "jpavel"  wrote:

What's really strange is that I have thus plugin working on a test
installation, but I can't get it to work on production.

*NOT MY CODE* https://github.com/011000100110010101100101011100
00/foreman_azure_rm - this is something I'm really, really interested in
getting working.

The gem builds fine (gem build foreman_azure_rm.gemspec) - and I can
install the same exact gem on my test server.

I install it via: scl enable tfm "gem install /root/foreman_azure_rm/
foreman_azure_rm-1.3.0.gem"

I can see the gem in /opt/rh/rh-ruby22/root/usr/
local/share/gems/gems/foreman_azure_rm-1.3.0

I create /usr/share/foreman/bundler.d/Gemfile.local.rb, with a single line:
gem 'foreman_azure_rm'

I restart httpd, and I get: *Gem loading error: cannot load such file --
foreman_azure_rm (RuntimeError)*

If I run: scl enable tfm "gem list", I see the gem listed. And when I list:
scl enable tfm "gem contents foreman_azure_rm", everything is listed in the
/opt/rh/rh-ruby22/root/usr/local/share/gems/gems path.

Any help on how I can troubleshoot this? Have I done something wrong?


-- 
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.

-- 
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: [event] Deep Dive: Running the Foreman Stack in Containers - Mon 10th July, 2pm (UK)

[Eric D Helms]

On Mon, Jul 10, 2017 at 10:43 PM, Alejandro Cortina <
alejandro.corti...@gmail.com> wrote:

> Ey,
>
> thank you for the video! really good stuff.
>
> Since one of the strong points of k8s is to make rapid development I think
> it would be good to make a P2 video showing that. Ex.: how can you
> code/update/ mix and mach new services and deploy and/or rollback if broken.
>

I'll put this on the list for when we get to this in general. I've mostly
spent time just trying to get the stack to come up and not on advanced
workflows yet. This is definitely in the pipeline of things to look at
though. And I think it would be helpful to get info from users as to how
they see themselves wanting to use and deploy the stack on a platform like
this given what it can provide.

For example, in my current way of tackling it I am imaging users pulling
pre-built images and running them. That is, not pushing the requirement to
build the images on to the users. This comes with its own benefits and
potential downsides for flexibility.


>
> I think also it would be good to add Kubernetes to the title to make it
> more reachable in youtube.
>

Greg - is that possible to add keywords or adjust the title for Kubernetes
/ Openshift?


>
> Cheers,
>
> Alex
>
> On Thursday, June 29, 2017 at 11:15:45 PM UTC+9, Greg Sutcliffe wrote:
>>
>> Hi all,
>>
>> Running Foreman in a container is a question that comes up from time to
>> time in the Foreman community. Eric Helms has been experimenting with
>> running the whole Foreman stack (core, proxies, plugins) inside
>> Kubernetes, and wants to show you how it looks. We'll be holding a deep
>> dive into this on Monday 10th July, at 2pm (GMT +1). You can tune in
>> here:
>>
>> https://www.youtube.com/watch?v=mPjUvNAYp1c
>>
>> As always, we welcome your contributions to the video - do join us live
>> on YouTube Live chat or in our IRC channel to put your questions to
>> Eric!
>>
>> Cheers,
>> Greg
>> --
>> IRC / Twitter: @gwmngilfen
>> Diaspora: gwmng...@joindiaspora.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.
>



-- 
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] Re: [foreman-dev] [event] Deep Dive: Running the Foreman Stack in Containers - Mon 10th July, 2pm (UK)

[Eric D Helms]

I did not get a chance to answer all the questions during the deep dive so
here is my follow up.

On Mon, Jul 3, 2017 at 8:20 AM, Ohad Levy <ohadl...@gmail.com> wrote:
>
>  * Current state and future Roadmap
>>
>
> I would be happy if you could also cover:
> - Smart proxy features (and how it works - e.g. a container per feature
> with base container etc).
>

I have not touched more of the core smart proxy feature management such as
DHCP and DNS yet.


> - Dev vs Production (whats in scope vs not)
>

I mentioned this in the video, but I'll recap. I have mostly targeted
production setups but there are known strategies for development. There are
a few ways we could consider and try to do development with this:

 1) ansible-container run is local docker and has a section for
dev_overrides [1]. With this you should point and mount source code
directly in when using 'run' (however, run does not entirely work currently
due to size of the setup)
 2) Openshift could have a host path mounted for development and allow
source code to be edited directly to use it as a dev environment
 3) Openshift has an rsync strategy to rsync a directory to a container for
development work

[1]
https://docs.ansible.com/ansible-container/container_yml/reference.html#dev-overrides


> - Installer - do we still need it in a context of a Kubernetes
> application?
>

I would say no given the current state of the installer. The installer is
designed around a single machine deployment currently. The puppet modules
themselves are not currently usable as they would each need to be tweaked
to allow for deploying no runtime configuration. We could then explore
trying to puppet apply them to build the containers. You could argue it is
bad on me to try to not re-use them due to all the work that has gone into
them. I just found starting from scratch and working with Ansible to be
easier and quicker than attempting to dissect them so far.

I do believe we still need an "installer" or "deployer" to orchestrate
everything being configured and setup for users. Our stack can get complex,
and between all the customization pieces, passwords, certificates, having a
tool to manage that would be useful for user interaction and ease.


> - SCL ? can we move away from it?
>

I think that's a big question. You are essentially asking can we move away
from RPM packaging (since Deb uses gems directly if I recall). There is a
valid argument for using gems directly. That would reduce build overhead,
allow for development and production to be closer to together and reduce
build time. We'd still want the SCL for runtime on enterprise Linux to
allow for upgrading the version of Ruby as I think that is better than
relying on RVM.


> - reuse? for example, https://github.com/manageiq?q=container have some
> basic ruby / rails containers etc
>

Sure, any container could be used as a base and built on top of. This would
come down to how much customization do we need or is there in an existing
container. Right now I build the entire stack, so every application gets a
container built except for using thirdparty Postgres and Mongodb.


> - application scaling ? (e.g. more dynflow workers etc).
>

I touched on this briefly, by default I am attempting to set services as
scaled by default to enforce getting used to and dealing with those
behaviors for scaling. For example, having 2 Foreman applications, 4 Pulp
workers by default. I have not yet tried a 2 or more foreman-tasks replica
yet. But I'll put it on my list to bump next spin up.

Eric


>
> sorry for the long list :)
>
> thanks,
> Ohad
>
>>
>>
>> Thanks,
>> Eric
>>
>>
>> [1] https://github.com/theforeman/forklift/pull/424
>>
>> On Thu, Jun 29, 2017 at 10:15 AM, Greg Sutcliffe <
>> greg.sutcli...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> Running Foreman in a container is a question that comes up from time to
>>> time in the Foreman community. Eric Helms has been experimenting with
>>> running the whole Foreman stack (core, proxies, plugins) inside
>>> Kubernetes, and wants to show you how it looks. We'll be holding a deep
>>> dive into this on Monday 10th July, at 2pm (GMT +1). You can tune in
>>> here:
>>>
>>> https://www.youtube.com/watch?v=mPjUvNAYp1c
>>>
>>> As always, we welcome your contributions to the video - do join us live
>>> on YouTube Live chat or in our IRC channel to put your questions to
>>> Eric!
>>>
>>> Cheers,
>>> Greg
>>> --
>>> IRC / Twitter: @gwmngilfen
>>> Diaspora: gwmngil...@joindiaspora.com
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "foreman-de

Re: [foreman-users] katello-agent 3.4 repos missing deps

[Eric D Helms]

This took a bit longer than I intended to rectify. Please see the link to
the release below that fixes this an introduces a new package.

https://groups.google.com/forum/#!topic/foreman-users/y18Ialuam4A


Eric

On Wed, Jun 28, 2017 at 3:46 PM, Tony Coffman <t...@emitony.com> wrote:

> FYI - I opened an issue last week about this.
>
> http://projects.theforeman.org/issues/20088
>
>
>
>
>
>
> On Tuesday, June 27, 2017 at 5:40:00 PM UTC-4, Eric Helms wrote:
>>
>> I'll look into this discrepancy. This is likely due to the migration we
>> had to make and rebuild our RPM build server. Stay tuned.
>>
>> On Tue, Jun 27, 2017 at 4:53 PM, 'Jason B. Nance' via Foreman users <
>> forema...@googlegroups.com> wrote:
>>
>>> Errr... wait, sorry, I totally misread your email.  I thought you were
>>> referring to Katello server, not client.
>>>
>>> Sorry sorry... Ignore me.
>>>
>>> j
>>>
>>>
>>>
>>> --
>>> *From: *"Jason Nance" <ja...@tresgeek.net>
>>> *To: *"Foreman Users" <forema...@googlegroups.com>
>>> *Sent: *Tuesday, June 27, 2017 3:52:19 PM
>>> *Subject: *Re: [foreman-users] katello-agent 3.4 repos missing deps
>>>
>>> Hi Matthew,
>>>
>>> EL 6 support was dropped earlier in the 3.x series.  EL 7 is currently
>>> the only supported version for RHEL/RHEL-like distros.
>>>
>>> Regards,
>>>
>>> j
>>>
>>>
>>>
>>> --
>>> *From: *matthew...@gmail.com
>>> *To: *"Foreman Users" <forema...@googlegroups.com>
>>> *Sent: *Tuesday, June 27, 2017 3:03:29 PM
>>> *Subject: *[foreman-users] katello-agent 3.4 repos missing deps
>>>
>>> I'm attempting to install the katello-agent on a CentOS 6 system per the
>>> instructions listed here:  https://theforeman.org/plugin
>>> s/katello/3.4/installation/clients.html
>>>
>>> But I get the following error:
>>>
>>> Cannot open: http://fedorapeople.org/groups/katello/releases/yum/3.4/
>>> client/el6/x86_64/katello-client-repos-latest.rpm. Skipping.
>>> Error: Nothing to do
>>>
>>> Looking at the repo the katello-client-repos-latest.rpm does not exist
>>> there.  Nor do any of the dependencies for katello-agent (except for
>>> katello-agent-fact-plugin).  The only OS that seems to have a fully
>>> populated repo for 3.4 is EL7.
>>>
>>> --
>>> 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.
>>>
>>
>>
>>
>> --
>> 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.
>



-- 
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] Katello 3.4 Client Release: introducing agent(gofer)-less host tools

[Eric D Helms]

We've decided to make a stand alone release to the Katello client
repositories to address address an issue and release a new feature.

Gofer-less Client Support

For some time, users have been asking for a way to have errata and package
applicability without having to run the full agent on their client
machines. Further, while running the agent does provide for remote action
such as package or errata installation, the remote execution plugin can
also provide this functionality in an agent-less manner. To bring this full
circle, we've decided to release goferless client packages into the 3.4
stream. Also, this should reduce memory consumption on individual clients.

This new package is: katello-host-tools. Installing this package will not
install the katello-agent package nor will it start goferd. However, any
yum action will result in package profile and enabled repository updates
back to the server ensuring up to date errata listing.

For those wanting the previous behavior, simply install katello-agent as
this will continue to function as it did before.

For those upgrading, if you wish to continue to use katello-agent as is,
simply upgrade like normal. If you wish to switch to agent-less mode,
update the katello-agent and either stop goferd or remove the katello-agent
package. Ensure that the katello-host-tools package remains installed.

Broken Client Repositories

During the time frame of the Katello 3.4 release, our RPM build server went
down and had to be migrated. Part of that recovery required rebuilding and
populating our build structure for RPMs. This resulted in broken client
repositories for all but EL7 being released. Today's release fixes the EL6,
EL5, Fedora 24 and Fedora 25 client repositories to put back the missing
packages.

Please let us know if you find any further irregularities with these
repositories.

-- 
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: [foreman-dev] [event] Deep Dive: Running the Foreman Stack in Containers - Mon 10th July, 2pm (UK)

[Eric D Helms]

Thanks for setting this up Greg.

I wanted to send out a few notes ahead of time so that folks can do any
background reading, using the work I'll be presenting or think about
questions they might have. If you want to send along questions ahead of
time you'd like addressed (or to ensure I cover) please feel free to reply
here and I'll do my best to work them into the presentation.

Rough Topics I'll be covering:

 * Brief presentation on why containers, the technologies involved in build
and deploy
 * Architecture presentation of service breakdown
 * How the PR[1] works
 * Current state and future Roadmap


Thanks,
Eric


[1] https://github.com/theforeman/forklift/pull/424

On Thu, Jun 29, 2017 at 10:15 AM, Greg Sutcliffe <greg.sutcli...@gmail.com>
wrote:

> Hi all,
>
> Running Foreman in a container is a question that comes up from time to
> time in the Foreman community. Eric Helms has been experimenting with
> running the whole Foreman stack (core, proxies, plugins) inside
> Kubernetes, and wants to show you how it looks. We'll be holding a deep
> dive into this on Monday 10th July, at 2pm (GMT +1). You can tune in
> here:
>
> https://www.youtube.com/watch?v=mPjUvNAYp1c
>
> As always, we welcome your contributions to the video - do join us live
> on YouTube Live chat or in our IRC channel to put your questions to
> Eric!
>
> Cheers,
> Greg
> --
> IRC / Twitter: @gwmngilfen
> Diaspora: gwmngil...@joindiaspora.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-dev+unsubscr...@googlegroups.com.
> 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.

Re: [foreman-users] katello-agent 3.4 repos missing deps

[Eric D Helms]

I'll look into this discrepancy. This is likely due to the migration we had
to make and rebuild our RPM build server. Stay tuned.

On Tue, Jun 27, 2017 at 4:53 PM, 'Jason B. Nance' via Foreman users <
foreman-users@googlegroups.com> wrote:

> Errr... wait, sorry, I totally misread your email.  I thought you were
> referring to Katello server, not client.
>
> Sorry sorry... Ignore me.
>
> j
>
>
>
> --
> *From: *"Jason Nance" <ja...@tresgeek.net>
> *To: *"Foreman Users" <foreman-users@googlegroups.com>
> *Sent: *Tuesday, June 27, 2017 3:52:19 PM
> *Subject: *Re: [foreman-users] katello-agent 3.4 repos missing deps
>
> Hi Matthew,
>
> EL 6 support was dropped earlier in the 3.x series.  EL 7 is currently the
> only supported version for RHEL/RHEL-like distros.
>
> Regards,
>
> j
>
>
>
> --
> *From: *matthewhmil...@gmail.com
> *To: *"Foreman Users" <foreman-users@googlegroups.com>
> *Sent: *Tuesday, June 27, 2017 3:03:29 PM
> *Subject: *[foreman-users] katello-agent 3.4 repos missing deps
>
> I'm attempting to install the katello-agent on a CentOS 6 system per the
> instructions listed here:  https://theforeman.org/plugins/katello/3.4/
> installation/clients.html
>
> But I get the following error:
>
> Cannot open: http://fedorapeople.org/groups/katello/releases/yum/3.
> 4/client/el6/x86_64/katello-client-repos-latest.rpm. Skipping.
> Error: Nothing to do
>
> Looking at the repo the katello-client-repos-latest.rpm does not exist
> there.  Nor do any of the dependencies for katello-agent (except for
> katello-agent-fact-plugin).  The only OS that seems to have a fully
> populated repo for 3.4 is EL7.
>
> --
> 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.
>
> --
> 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.
>



-- 
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] Katello 3.4.2 Released

[Eric D Helms]

We are happy to announce the GA of Katello 3.4.2. This release was
accelerated due to the breakage in attempting to register via an activation
key.

This release includes 17 bug fixes, a few highlighted:

  * Registration via an activation key will not error
  * The katello-backup tool now has support for LVM based snapshots
  * Performance improvements including faster fact importing during
registration and fact upload
  * Package update buttons in the UI are more obvious and work again

See the changelog for detailed feature issues and bug fixes:
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.

[foreman-users] Katello 3.4.1 Released

[Eric D Helms]

Happy Friday,

We are happy to announce the GA of Katello 3.4.1

This release includes 48 bug fixes, a few highlighted:

  * Foreman remote execution inclusion should no longer fail installation
  * Entitlement events were not being picked up by server, this is fixed now
  * Package uploads should no longer result in incorrect names
  * virt_who reporting works again


Release Notes:
https://theforeman.org/plugins/katello/3.4/release_notes/release_notes.html

Installation:
https://theforeman.org/plugins/katello/3.4/installation/index.html

Upgrade:
https://theforeman.org/plugins/katello/3.4/upgrade/index.html

See the changelog for detailed feature issues and bug fixes:
https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md

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] Katello not showing available Updates

[Eric D Helms]

This has been investigated and found to be a legitimate bug that can arise
in certain scenarios. We'll reply back here once we have the full issue and
solution worked out.

On Jun 6, 2017 6:29 AM, "Tim Hofmann"  wrote:

> Hi Duncan,
>
> the client is definitely registered to the correct ContentView.
>
> 'yum update' shows me the newer version of the nginx package (cause the
> installed is older).
>
> Yes the client is showing me the correct Repos.
>
>
> Am Dienstag, 6. Juni 2017 11:26:11 UTC+2 schrieb Duncan Innes:
>>
>> I've done this a few times and not noticed that the client was subscribed
>> to the wrong view (i.e. a view that didn't have the new RPMs).
>>
>> What does yum update on the client say?  Does it show the new nginx as
>> available for upgrade?  Is it showing you the repositories that you expect
>> from your Katello?
>>
>> On Tuesday, 6 June 2017 07:18:56 UTC+1, Tim Hofmann wrote:
>>>
>>> Hi Eric,
>>>
>>> thanks for your answer.
>>>
>>> - Check. Katello Agent is installed and Running. UI also indicates that.
>>> - Yes, the outdatet nginx is listed under installed packages.
>>> - Yes, the content Host is registered to a Content View (via Activation
>>> Key). Auto-Attach is disabled and all needed Subsrciptions are added.
>>>
>>> I already tried to restart the goferd agent and checked the logs. No
>>> Error or hint is logged :-(
>>>
>>> Tim
>>>
>>> Am Samstag, 3. Juni 2017 17:29:09 UTC+2 schrieb Eric Helms:

 Howdy Tim,

 Let's check a few items to narrow down what the issue might be:

  * you've got katello-agent installed on the host and goferd is
 running; does the UI indicate that it knows katello-agent is installed?
  * if you look at the package list for the content host do you see the
 outdated nginx listed?
  * The content host is currently registered to a content view that
 contains the EPEL repository? (I assume yes since yum update picks up the
 update but just checking)

 You could try restarting goferd on the host.

 Eric

 On Jun 3, 2017 10:07 AM, "Tim Hofmann"  wrote:

 Hey guys,

 i got a strange issue. I did a fresh install of katello 3.4 on CentOS 7.
 On a second CentOs 7 VM i installed an outdated nginx version.
 On the next step i added the EPEL Repo's to Katello synced them and
 added my Outdated nginx VM. I also installed the katello agent on this vm.

 The Problem is now that katello isnt't showing up any availible updates
 for my outdated nginx VM (on yum update the newer version on nginx is
 showing up).

 Is this by design or i am doing something wrong?

 thanks in advance and sorry for my bad english :-/

 --
 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.
>

-- 
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: foreman/katello smart-proxy setup

[Eric D Helms]

Katello does not use the puppet certificates for a majority of
configuration which means that if you follow the Smart Proxy instructions
you pointed to you'll likely end up with a smart proxy that cannot
communicate back to the server.

Was your DHCP smart proxy an existing smart proxy or a fresh install? I
would recommend looking at how to install a smart proxy when you have a
Katello install:

https://theforeman.org/plugins/katello/3.4/installation/smart_proxy.html

This by default configures the smart proxy with content for syncing content
to an external location or datacenter. If you are not wanting to use this
and thus want a lighter weight smart proxy with your Katello install you
can disable Pulp setup and configuration.

Eric

On May 29, 2017 5:35 AM, "Vincenzo Z"  wrote:

> update when I use the foreman-installer without Katello I can add my DHCP
> proxy without problems:
>
> foreman-installer --scenario foreman --foreman-admin-password test
>
>
>
> Le mercredi 24 mai 2017 15:12:11 UTC+2, Vincenzo Z a écrit :
>>
>> Hello,
>>
>>
>> I'm trying to install katello/foreman with a DHCP smart-proxy located on
>> another server.
>>
>> My first attempt was to use a certificate signed by our internal CA with
>> this command:
>> foreman-installer --scenario katello --foreman-admin-password test
>> --certs-server-cert "/root/katello_certs/katello2.example.com.crt"
>> --certs-server-cert-req "/root/katello_certs/katello2.example.com.csr"
>> --certs-server-key "/root/katello_certs/katello2.example.com.key"
>> --certs-server-ca-cert "/root/katello_certs/cacert.pem"
>>
>> Installation was successful and I was able to connect to my foreman web
>> interface without SSL warnings.
>>
>>
>> Next step was to setup the connection between my foreman and my DHCP
>> smart-proxy:
>>
>> So I followed the steps documented here https://theforeman.org/manuals
>> /1.15/index.html#4.3SmartProxies
>>
>> generate my cert on my foreman server:
>>
>> puppet cert generate dhcp.example.com
>>
>> copy cert, ca and key to the /etc/foreman-proxy/ssl directory on my DHCP 
>> smart-proxy
>>
>> edit my setting.yml config file like this:
>>
>> ---
>> :settings_directory: "/etc/foreman-proxy/settings.d"
>> :daemon: true
>> :daemon_pid: /var/run/foreman-proxy/foreman-proxy.pid
>> :bind_host: '*'
>> :https_port: 8443
>> :ssl_certificate: /etc/foreman-proxy/ssl/dhcp.example.com.pem
>> :ssl_ca_file: /etc/foreman-proxy/ssl/ca.pem
>> :ssl_private_key: /etc/foreman-proxy/ssl/dhcp.example.com.key
>> :trusted_hosts:
>> - katello2.example.com
>> :log_file: /var/log/foreman-proxy/proxy.log
>> :log_level: DEBUG
>>
>> open firewall ports
>>
>> When I try to connect from my foreman web interface with this URL 
>> https://dhcp.example.com:8443
>>
>> I get this error message in the log file of my DHCP smart-proxy:
>>
>> "OpenSSL::SSL::SSLError: SSL_accept returned=1 errno=0 state=unknown
>> state: tlsv1 alert unknown ca"
>>
>>
>> It's a CA issue maybe because I'm playing with internal CA so I tried
>> with the self-signed certificates generated with the foreman/katello
>> installation:
>>
>> foreman-installer --scenario katello --foreman-admin-password "test"
>>
>> Same error.
>>
>>
>> I think I miss something in the smart-proxy setup  and I don't play with
>> the right certificates.
>>
>> I probably don't use the same CA to sign my foreman certificate and my
>> DHCP smart-proxy certificate.
>>
>> Can somebody put me in the good direction to solve this problem?
>>
>>
>> Best regards,
>>
>>
>>
>> --
> 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.
>

-- 
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] Applicable packages not updated since upgrade since upgrade from Katello3.3 to 3.4

[Eric D Helms]

Howdy,

You are the second user to report an issue around applicable packages in
3.4. Would you mind filing a redmine issue with details for us to
investigate?

Eric

On Jun 3, 2017 5:46 AM, "pascalp"  wrote:

> Hello,
>
> ever since I updated Katello from 3.3 to 3.4 I do not get any available
> package updates listed at "content hosts". Manually doing a "yum update" on
> a machine shows available updates.
> I also noticed there is no execution of task "Generate applicability" ever
> since the upgrade in the task history.
>
> 
>
> foreman-1.15.0-1.el7.noarch
> katello-3.4.0-3.el7.noarch
> pulp-server-2.12.2-1.el7.noarch
>
> I would be glad for any advice on how to troubleshoot/solve this.
>
> Thanks
>
> Pascal
>
> --
> 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.
>

-- 
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 not showing available Updates

[Eric D Helms]

Howdy Tim,

Let's check a few items to narrow down what the issue might be:

 * you've got katello-agent installed on the host and goferd is running;
does the UI indicate that it knows katello-agent is installed?
 * if you look at the package list for the content host do you see the
outdated nginx listed?
 * The content host is currently registered to a content view that contains
the EPEL repository? (I assume yes since yum update picks up the update but
just checking)

You could try restarting goferd on the host.

Eric

On Jun 3, 2017 10:07 AM, "Tim Hofmann"  wrote:

Hey guys,

i got a strange issue. I did a fresh install of katello 3.4 on CentOS 7.
On a second CentOs 7 VM i installed an outdated nginx version.
On the next step i added the EPEL Repo's to Katello synced them and added
my Outdated nginx VM. I also installed the katello agent on this vm.

The Problem is now that katello isnt't showing up any availible updates for
my outdated nginx VM (on yum update the newer version on nginx is showing
up).

Is this by design or i am doing something wrong?

thanks in advance and sorry for my bad english :-/

-- 
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.

-- 
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/foreman 1.14

[Eric D Helms]

Edward,

The katello-agent is actually running as 'goferd' on the system. When you
install this service gets started which triggers initial uploads for
package profiles and enabled repositories. Subsequent actions on the host
will re-trigger these events (e.g. yum update will re-trigger package
upload) to keep the data up to date in Katello and applicability current.

Eric

On Wed, May 31, 2017 at 10:59 AM, Edward Clay <edward.c...@uk2group.com>
wrote:

> Thanks Eric for the quick response. is there some service that runs on the
> system or is it called by something? Just trying to figure out how this
> works without enabling the puppet service, which doesn't seem to be related.
>
> On Tue, 2017-05-30 at 20:08 -0400, Eric D Helms wrote:
>
> The service you are looking for is when you installed katello-agent. This
> package includes utilities that upload the hosts package profile and
> enabled repositories to Katello which allow errata to be calculated.
>
> Eric
>
> On Tue, May 30, 2017 at 6:46 PM, Edward Clay <edward.c...@uk2group.com>
> wrote:
>
> Can anyone tell me what software/agent/code is used to to inform
> katello/foreman that a system is either up to date or needs patches (aka
> erratas that apply to host) and what executes it?  From what I've come up
> with thus far, I perform the following task on a host and then everything
> is good.  But this is because puppet agent does a puppet run every 35'is
> minutes.  At least that's what my understanding is.
>
> 1. So first I create a host in foreman with the specifics/details needed
> to define a specific host.
>
> 2. On a existing system I run these task.  Rough draft of the steps I
> follow to set up an existing host.
>
> -- install subscription manager
> wget https://copr.fedoraproject.org/coprs/dgoodwin/subscription-
> manager/repo/epel-6/dgoodwin-subscription-manager-epel-6.repo -O
> /etc/yum.repos.d/dgoodwin-subscription-manager-epel-6.repo
> -- install katello client
> yum install -y http://fedorapeople.org/groups/katello/releases/yum/3.2/
> client/el6/x86_64/katello-client-repos-latest.rpm
> yum -y install katello-agent
> wget --no-check-certificate https://foreman.domain.com/pub
> /katello-ca-consumer-latest.noarch.rpm
> rpm -ihv ./katello-ca-consumer-latest.noarch.rpm
> subscription-manager register --org="myOrg" --activationkey="COS6"
>
> -- Install puppet
> rpm -ihv https://yum.puppetlabs.com/puppetlabs-release-el-6.noarch.rpm
> yum -y install puppet
> add the following two lines just under [main]
> server = foreman.domain.com
> environment = production
> --   puppet agent -t
> --   service puppet start
> --   chkconfig puppet on
>
> So after doing these steps i'm able to login to foreman and see weather or
> not a system has outstanding erratas that need to be applied and I can
> apply them.
>
> --
> 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.
>
>
>
>
> --
>
> Edward Clay
> Systems Adminstrator
> UK2 Group -- US Operations
> Phone: 1-800-222-2165 <(800)%20222-2165>
> E-Mail: edward.c...@uk2group.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.
>



-- 
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] katello 3.3/foreman 1.14

[Eric D Helms]

The service you are looking for is when you installed katello-agent. This
package includes utilities that upload the hosts package profile and
enabled repositories to Katello which allow errata to be calculated.

Eric

On Tue, May 30, 2017 at 6:46 PM, Edward Clay <edward.c...@uk2group.com>
wrote:

> Can anyone tell me what software/agent/code is used to to inform
> katello/foreman that a system is either up to date or needs patches (aka
> erratas that apply to host) and what executes it?  From what I've come up
> with thus far, I perform the following task on a host and then everything
> is good.  But this is because puppet agent does a puppet run every 35'is
> minutes.  At least that's what my understanding is.
>
> 1. So first I create a host in foreman with the specifics/details needed
> to define a specific host.
>
> 2. On a existing system I run these task.  Rough draft of the steps I
> follow to set up an existing host.
>
> -- install subscription manager
> wget https://copr.fedoraproject.org/coprs/dgoodwin/
> subscription-manager/repo/epel-6/dgoodwin-subscription-manager-epel-6.repo
> -O /etc/yum.repos.d/dgoodwin-subscription-manager-epel-6.repo
> -- install katello client
> yum install -y http://fedorapeople.org/groups/katello/releases/yum/3.
> 2/client/el6/x86_64/katello-client-repos-latest.rpm
> yum -y install katello-agent
> wget --no-check-certificate https://foreman.domain.com/
> pub/katello-ca-consumer-latest.noarch.rpm
> rpm -ihv ./katello-ca-consumer-latest.noarch.rpm
> subscription-manager register --org="myOrg" --activationkey="COS6"
>
> -- Install puppet
> rpm -ihv https://yum.puppetlabs.com/puppetlabs-release-el-6.noarch.rpm
> yum -y install puppet
> add the following two lines just under [main]
> server = foreman.domain.com
> environment = production
> --   puppet agent -t
> --   service puppet start
> --   chkconfig puppet on
>
> So after doing these steps i'm able to login to foreman and see weather or
> not a system has outstanding erratas that need to be applied and I can
> apply them.
>
> --
> 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.
>



-- 
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] Re: Katello 3.4 (Oud Bruin) Released!

[Eric D Helms]

Nah, someone put in a quick PR fix thanks to your report!

On May 30, 2017 10:05 AM, "Duncan Innes" <dun...@innes.net> wrote:

> They've changed now.  Might I have been hitting a cache?
>
> On Tuesday, 30 May 2017 13:30:53 UTC+1, Eric Helms wrote:
>>
>> Duncan,
>>
>> Can you point me to which website page/link you are meaning?
>>
>> On Tue, May 30, 2017 at 8:20 AM, Duncan Innes <dun...@innes.net> wrote:
>>
>>> The install docs are still referencing 3.3 as the latest stable versions
>>> and referring to 3.4 as 3.4-RC.
>>>
>>>
>>> On Monday, 29 May 2017 05:32:56 UTC+1, Eric Helms wrote:
>>>>
>>>> All,
>>>>
>>>> We are happy to announce the GA of Katello 3.4. Highlights of the
>>>> release:
>>>>
>>>>  * Better file repository content management
>>>>  * Advanced repository syncing options for recovery and repair
>>>>  * UI overhaul
>>>>  * Content view force republishing
>>>>  * Candlepin 2.0 support
>>>>  * Pulp 2.12.2
>>>>
>>>> Release Notes:
>>>> https://theforeman.org/plugins/katello/3.4/release_notes/
>>>> release_notes.html
>>>>
>>>> Installation:
>>>> https://theforeman.org/plugins/katello/3.4/installation/index.html
>>>>
>>>> Upgrade:
>>>> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>>>>
>>>> See the changelog for detailed feature issues and bug fixes:
>>>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md
>>>>
>>>> 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-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.
>

-- 
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.4 (Oud Bruin) Released!

[Eric D Helms]

The foreman-release-scl ensures that the necessary SCL epositories are
setup and configured for a typical installation. If you are importing all
the necessary repositories into Katello and using that yourself then I
wouldn't worry about it.

Eric

On Mon, May 29, 2017 at 8:51 PM, Lachlan Musicman <data...@gmail.com> wrote:

> Thanks for all the hard work.
>
> I'd like to ask a question about the upgrade instructions.
>
> In step 3, what does the line
>
>   yum update -y foreman-release-scl
>
> do?
>
> The other two lines make sense. This one, I don't quite understand.
>
> We host Katello on katello, so there is some jiggery-pokery with moving 
> products and content views around,
> and deploying them.
>
> Adding a new product (pulp-3.4, client-3.4, candlepin-3.4, katello-3.4, 
> plugins-1.15, foreman-1.15 etc) is easy
> enough as a sub for the other two lines in that instruction.
>
> I'm not 100% sure what the foreman-release-scl does? We are tracking the 
> various extra repos as necessary,
> I presume they are kept up to date, since they aren't as explicitly 
> versioned. (rhsc, sig, passenger, puppet).
>
> I usually just ignore this step, but that is bad practice - what does it do?
>
> cheers
>
> L.
>
>
>
>
>
> --
> "Mission Statement: To provide hope and inspiration for collective action,
> to build collective power, to achieve collective transformation, rooted in
> grief and rage but pointed towards vision and dreams."
>
>  - Patrisse Cullors, *Black Lives Matter founder*
>
> On 29 May 2017 at 14:32, Eric D Helms <ericdhe...@gmail.com> wrote:
>
>> All,
>>
>> We are happy to announce the GA of Katello 3.4. Highlights of the release:
>>
>>  * Better file repository content management
>>  * Advanced repository syncing options for recovery and repair
>>  * UI overhaul
>>  * Content view force republishing
>>  * Candlepin 2.0 support
>>  * Pulp 2.12.2
>>
>> Release Notes:
>> https://theforeman.org/plugins/katello/3.4/release_notes/
>> release_notes.html
>>
>> Installation:
>> https://theforeman.org/plugins/katello/3.4/installation/index.html
>>
>> Upgrade:
>> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>>
>> See the changelog for detailed feature issues and bug fixes:
>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md
>>
>> 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.
>>
>
> --
> 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.
>



-- 
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] Katello 3.4 (Oud Bruin) Released!

[Eric D Helms]

All,

We are happy to announce the GA of Katello 3.4. Highlights of the release:

 * Better file repository content management
 * Advanced repository syncing options for recovery and repair
 * UI overhaul
 * Content view force republishing
 * Candlepin 2.0 support
 * Pulp 2.12.2

Release Notes:
https://theforeman.org/plugins/katello/3.4/release_notes/release_notes.html

Installation:
https://theforeman.org/plugins/katello/3.4/installation/index.html

Upgrade:
https://theforeman.org/plugins/katello/3.4/upgrade/index.html

See the changelog for detailed feature issues and bug fixes:
https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md

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] Katello 3.4 RC2 Available for Testing

[Eric D Helms]

Howdy,

Please check out this thread for information regarding why we are holding
the GA release:

https://groups.google.com/forum/#!topic/foreman-users/z4nlpi96GrM


Eric

On Sun, May 21, 2017 at 11:05 PM, Lachlan Musicman <data...@gmail.com>
wrote:

> Did Katello 3.4 get released yet - did I miss an announcement?
>
> I feel like there has been movement on the github (3.4.0 released 11 days
> ago, 3.4.0.1 released over the weekend?)
>
> Cheers
> L.
>
> --
> "Mission Statement: To provide hope and inspiration for collective action,
> to build collective power, to achieve collective transformation, rooted in
> grief and rage but pointed towards vision and dreams."
>
>  - Patrice Cullors, *Black Lives Matter founder*
>
> On 28 April 2017 at 06:04, Eric D Helms <ericdhe...@gmail.com> wrote:
>
>> In conjunction with the release for Foreman 1.15 RC2, Katello 3.4 RC2 is
>> now available for testing.
>>
>> Please help by testing and filing any issues that you find so that we may
>> address them before the final release.
>>
>> Installation:
>> https://theforeman.org/plugins/katello/3.4/installation/index.html
>>
>> Upgrade:
>> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>>
>> See the preliminary changelog for detailed information:
>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md
>>
>> 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.
>>
>
> --
> 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.
>



-- 
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] Katello 3.4 Release Update

[Eric D Helms]

All,

The Katello 3.4 GA release is currently being blocked by a severe issue for
those using RH manifests [1]. For those currently testing the RC, If you
have custom products and import or refresh a manifest those custom product
subscriptions will be lost. This is an issue identified in Candlepin and
they are working to resolve it. Again:

DO NOT REFRESH OR IMPORT YOUR MANIFEST until the GA release.

Once this issue has been resolved you can expect the GA to follow.

[1] http://projects.theforeman.org/issues/18971

-- 
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] Katello 3.4 RC2 Available for Testing

[Eric D Helms]

In conjunction with the release for Foreman 1.15 RC2, Katello 3.4 RC2 is
now available for testing.

Please help by testing and filing any issues that you find so that we may
address them before the final release.

Installation:
https://theforeman.org/plugins/katello/3.4/installation/index.html

Upgrade:
https://theforeman.org/plugins/katello/3.4/upgrade/index.html

See the preliminary changelog for detailed information:
https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md

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] Re: Katello 3.3.1 released!

[Eric D Helms]

I believe this is the key error "ArgumentError: Unknown key:
:host_action_button. Valid keys are: :provided_inputs, :description" which
comes from foreman_remote_execution having an older release. This is fixed
in master of the plugin but releasing a newer version is blocked by other
issues that are being worked on.

On Thu, Mar 23, 2017 at 9:14 AM, Duncan Innes <dun...@innes.net> wrote:

> I'm not skilled in diagnosing log files, but I see the following in
> katello.1.log and katello.log:
>
>
>1. [ INFO 2017-03-22 10:58:20 main] Upgrade Step: migrate_foreman...
>2. [ERROR 2017-03-22 10:58:25 main]
>3. [ERROR 2017-03-22 10:58:31 main] API controllers newer than Apipie
>cache! Run apipie:cache rake task to regenerate cache.
>4. rake aborted!
>
> Is this the source of the problem, or just a symptom of an underlying
> issue?
>
> Duncan
>
> On Wednesday, 22 March 2017 12:21:15 UTC, Duncan Innes wrote:
>>
>>
>> Apologies, forgot about my pastebin account until midway through
>> splitting initial log file:
>>
>> [root@katello ~]# cd /var/log/foreman-installer/
>> [root@katello foreman-installer]# ls -lrt
>> total 3572
>> -rw-r--r--. 1 root root   0 Feb 28 21:47 foreman.2.log
>> -rw-r--r--. 1 root root   0 Feb 28 21:48 katello.6.log
>> -rw-r--r--. 1 root root   15751 Feb 28 21:50 katello.5.log
>> -rw-r--r--. 1 root root 2172590 Feb 28 23:27 katello.4.log
>> -rw-r--r--. 1 root root8553 Mar 22 10:47 foreman.1.log   <-
>> http://pastebin.com/ep4HajV5
>> -rw-r--r--. 1 root root1212 Mar 22 10:47 foreman.log <-
>> http://pastebin.com/TVixt0eK
>> -rw-r--r--. 1 root root 1338785 Mar 22 10:48 katello.3.log   <-
>> http://pastebin.com/530ih26P
>> -rw-r--r--. 1 root root8624 Mar 22 10:49 katello.2.log   <-
>> http://pastebin.com/d7RLn3Hw
>> -rw-r--r--. 1 root root   49047 Mar 22 10:55 katello.1.log   <-
>> http://pastebin.com/G0EFGwCa
>> -rw-r--r--. 1 root root   48628 Mar 22 10:58 katello.log <-
>> http://pastebin.com/UDTTjrwU
>> [root@katello foreman-installer]#
>>
>>
>> On Wednesday, 22 March 2017 11:47:39 UTC, Eric Helms wrote:
>>>
>>> What errors?
>>>
>>
>>
> --
> 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.
>



-- 
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] Re: Katello 3.3.1 released!

[Eric D Helms]

What errors?

On Mar 22, 2017 6:59 AM, "Duncan Innes"  wrote:

> Should I be running
>
> foreman-installer --scenario katello --upgrade
>
> after my yum update when upgrading from 3.3 to 3.3.1?
>
> I'm getting errors during Upgrade Step: migrate_foreman
>
> D
>
> --
> 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.
>

-- 
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 sync failing

[Eric D Helms]

You'll need to regenerate a certificate tarball for each proxy and deploy
it with the installer. This is due to the hostname change on the main
server and how the certificates are used to sync from the server to the
proxy.

On Mar 14, 2017 10:12 PM, "jpavel"  wrote:

> I'm running foreman 1.14.2, and Katello 3.3.0.
>
> On the foreman server, I'm seeing these messages:
> [Wed Mar 15 01:57:02.739257 2017] [ssl:error] [pid 18720] [client
> 10.9.0.1:42382] AH02039: Certificate Verification: Error (20): unable to
> get local issuer certificate
> ...
> eventually followed by a burst of something like this:
> 2017-03-15 01:57:02  [foreman-tasks/action] [E] RPM1004: Error retrieving
> metadata: Not found (Katello::Errors::PulpError)
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.3.0.
> 1/app/lib/actions/pulp/abstract_async_task.rb:121:in `block in
> external_task='
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.3.0.
> 1/app/lib/actions/pulp/abstract_async_task.rb:119:in `each'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.3.0.
> 1/app/lib/actions/pulp/abstract_async_task.rb:119:in `external_task='
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/action/polling.rb:98:in `poll_external_task_with_rescue'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/action/polling.rb:21:in `run'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/action/cancellable.rb:9:in `run'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.3.0.
> 1/app/lib/actions/pulp/abstract_async_task.rb:45:in `run'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/action.rb:506:in `block (3 levels) in execute_run'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/middleware/stack.rb:26:in `call'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/middleware/stack.rb:26:in `pass'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/middleware.rb:17:in `pass'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/middleware.rb:30:in `run'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/middleware/stack.rb:22:in `call'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/middleware/stack.rb:26:in `pass'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/middleware.rb:17:in `pass'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.3.0.
> 1/app/lib/actions/middleware/remote_action.rb:16:in `block in run'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.3.0.
> 1/app/lib/actions/middleware/remote_action.rb:40:in `block in
> as_remote_user'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.3.0.
> 1/app/models/katello/concerns/user_extensions.rb:21:in `cp_config'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.3.0.
> 1/app/lib/actions/middleware/remote_action.rb:27:in `as_cp_user'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.3.0.
> 1/app/lib/actions/middleware/remote_action.rb:39:in `as_remote_user'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.3.0.
> 1/app/lib/actions/middleware/remote_action.rb:16:in `run'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/middleware/stack.rb:22:in `call'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/middleware/stack.rb:26:in `pass'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/middleware.rb:17:in `pass'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/action/progress.rb:30:in `with_progress_calculation'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/action/progress.rb:16:in `run'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/middleware/stack.rb:22:in `call'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/middleware/stack.rb:26:in `pass'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/middleware.rb:17:in `pass'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.3.0.
> 1/app/lib/actions/middleware/keep_locale.rb:11:in `block in run'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.3.0.
> 1/app/lib/actions/middleware/keep_locale.rb:22:in `with_locale'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.3.0.
> 1/app/lib/actions/middleware/keep_locale.rb:11:in `run'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/middleware/stack.rb:22:in `call'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/middleware/stack.rb:26:in `pass'
>  | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.
> 17/lib/dynflow/middleware.rb:17:in `pass'
>  | 

Re: [foreman-users] katello centos-base repo not syncing

[Eric D Helms]

Does the sync task itself fail? If so, what do you see on the errors tab of
the task? Is Pulp throwing an error?

Thanks
Eric

On Feb 16, 2017 10:07 PM, "Edson Manners"  wrote:

Hate to bump the thread but I have the same issue. Katello 3.1.

The sync worked in this repo: http://vault.centos.org/7.1.1503/os/x86_64/
and did 8652 packages 3 months ago. A few yum updates later and now it wont
do it again or this repo:
http://vault.centos.org/7.2.1511/os/x86_64/

On Tuesday, October 25, 2016 at 4:42:55 PM UTC-4, steved0ca wrote:
>
> It seems the pulp-streaming service stopped running. After restarting it I
> was able to kill the sync tasks and restart them, but they still don't
> actually download any packages for Centos-base or -updates repos.
>
> On Mon, Oct 24, 2016 at 1:35 PM, steved0ca  wrote:
>
>> I tried all three options without any luck.
>>
>> After restarting the host, I tried to sync again with the 'background'
>> option and a manual sync and now I have an endless 'Result: Pending'
>> spinning circle for both the centos-base repo, and another repo that was
>> previously working.
>>
>> Here is the foreman production.log but I don't see anything helpful.
>> https://drive.google.com/file/d/0B7s4TFC-GYcAdVM1MH
>> NaOWZfR3c/view?usp=sharing
>>
>> On Monday, 24 October 2016 01:12:12 UTC-7, Klaas Demter wrote:
>>>
>>> Hi,
>>> try to change the download policy to "Immediate", I have had problems
>>> with "On demand" for some repositories.
>>>
>>> Greetings
>>> Klaas
>>>
>>>
>>>
>>> - Ursprüngliche Mail -
>>> Von: "steved0ca" 
>>> An: "Foreman users" 
>>> Gesendet: Sonntag, 23. Oktober 2016 21:03:59
>>> Betreff: [foreman-users] katello centos-base repo not syncing
>>>
>>> I have successfully synced other repos ie 'epel' without any difficulty.
>>>
>>> I've created a product 'centos-base' with a repo called 'centos-base'
>>> and
>>> attempted to sync the repo but no packages will sync. Same problem with
>>> centos-updates. Not sure where to start troubleshooting this, the
>>> foreman
>>> production.log doesn't have any obvious errors.
>>>
>>> The content host does display the repo including package count:
>>> # yum repolist
>>> ...
>>> repo id
>>>
>>> repo name status
>>> *!Default_Organization_CentOS-Base_CentOS-Base
>>>
>>>   CentOS-Base9,007*
>>> !Default_Organization_CentOS-Gluster-3_7_CentOS-Gluster-3_7
>>>
>>> CentOS-Gluster-3.714
>>> !Default_Organization_CentOS-Updates_CentOS-Updates
>>>
>>> CentOS-Updates 2,548
>>> !Default_Organization_epel_epel
>>>
>>> epel  11,215
>>> !Default_Organization_filebeat_filebeat
>>>
>>> filebeat  44
>>> !Default_Organization_glusterfs-nagios-epel_glusterfs-nagios-epel
>>>
>>> glusterfs-nagios-epel 10
>>> !Default_Organization_katello-agent_katello-agent
>>>
>>> katello-agent 15
>>> !Default_Organization_pcic_internal_pcic_internal
>>>
>>> pcic_internal 13
>>> base/7/x86_64
>>>
>>> CentOS-7 - Base*9,007*
>>> epel/x86_64
>>>
>>> Extra Packages for Enterprise Linux 7 - x86_6410,751
>>> extras/7/x86_64
>>>
>>> CentOS-7 - Extras393
>>> updates/7/x86_64
>>>
>>>  CentOS-7 - Updates 2,548
>>> repolist: 45,565
>>>
>>>
>>> Katello version 3.1
>>> Foreman 1.12.3
>>> Foreman OS CentOS 7.2
>>>
>>> pulp journal:
>>> Oct 23 11:45:03 foreman.my.domain.name pulp[12865]:
>>> kombu.transport.qpid:INFO: Connected to qpid with SASL mechanism
>>> ANONYMOUS
>>> Oct 23 11:45:04 foreman.my.domain.name pulp[299]:
>>> celery.worker.strategy:INFO: Received task:
>>> pulp.server.async.tasks._queue_reserved_task[060c2ae6-44a4-483f-ad90-be54e872ffec]
>>>
>>> Oct 23 11:45:04 foreman.my.domain.name pulp[322]:
>>> celery.worker.strategy:INFO: Received task:
>>> pulp.server.managers.repo.sync.sync[a3070bfa-6723-40c4-971e-2781746212c5]
>>>
>>> Oct 23 11:45:04 foreman.my.domain.name pulp[322]:
>>> celery.worker.strategy:INFO: Received task:
>>> pulp.server.async.tasks._release_resource[1f2bfee7-af00-4b0c-adb5-6dae94460415]
>>>
>>> Oct 23 11:45:04 foreman.my.domain.name pulp[648]:
>>> pulp_rpm.plugins.importers.yum.sync:INFO: Downloading metadata from
>>> http://mirror.it.ubc.ca/centos/7.2.1511/os/x86_64/.
>>> Oct 23 11:45:04 foreman.my.domain.name pulp[299]:
>>> celery.worker.job:INFO:
>>> Task
>>> pulp.server.async.tasks._queue_reserved_task[060c2ae6-44a4-483f-ad90-be54e872ffec]
>>>
>>> succeeded in 0.0428758189082s: None
>>> Oct 23 11:45:04 

Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

[Eric D Helms]

Could you please file a bug report with this information including your fix
or add it to an existing report so that we can look at getting this fixed
in the upcoming 3.3 release?

Thanks
Eric

On Feb 16, 2017 11:58 PM, "Lachlan Musicman"  wrote:

GOT IT.

GADDAM.

Edited

/usr/share/katello-installer-base/hooks/pre/31-upgrade-puppet.rb

commented out lines 21 and 22:

  success << Kafo::Helpers.execute('mv /var/lib/puppet/ssl
/etc/puppetlabs/puppet') if File.directory?('/var/lib/puppet/ssl')
  success << Kafo::Helpers.execute('mv /var/lib/puppet/foreman_cache_data
/opt/puppetlabs/puppet/cache/') if File.directory?('/var/lib/
puppet/foreman_cache_data')

did a diff on the two folders in both, made sure they were matching.

Ran foreman-installer --upgrade-puppet and it worked.

Un commented to two lines,  ran Klass's 18131 bug solution after it, and
all worked fine.

cheers
L.


--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 17 February 2017 at 14:54, Lachlan Musicman  wrote:

> Daniel,
>
> running the instructions as per the puppet upgrade page failed again.
>
> On issue we kept running into was this, from /var/log/foreman-installer/kat
> ello.log
>
> [ERROR 2017-02-17 13:44:48 main] mv: cannot move ‘/var/lib/puppet/ssl’ to
> ‘/etc/puppetlabs/puppet/ssl’: File exists
> [ERROR 2017-02-17 13:44:48 main] mv: cannot move
> ‘/var/lib/puppet/foreman_cache_data’ to 
> ‘/opt/puppetlabs/puppet/cache/foreman_cache_data’:
> File exists
> [ERROR 2017-02-17 13:44:48 main] Upgrade step copy_data failed. Check logs
> for more information.
>
> If you could point me to the log file that this message is talking about,
> I'd appreciate that. Note that physically removing the offending files
> doesn't seem to work - obviously there is some part of the
> --foreman-installer --update-puppet execution that  recreates them
>
> Moving onto the next page, we start to do the whole thing by hand, as per
> http://projects.theforeman.org/projects/foreman/wiki/Upgradi
> ng_from_Puppet_3_to_4
>
> Again, Step 1a and 1b completes fine, except for 1b.5 again - this time we
> did a grep on the whole of /etc/httpd/conf.d - there is no mention of
> /var/lib/puppet/ssl in there at all
>
>
> Moving onto Step 2, I ran the instructions with the changes you suggested
> - adding --forman to some of the command line options.
>
> ERROR: Unrecognised option '--foreman-puppet-server-implementation'
>
> See: 'foreman-installer --help'
>
> So I look at the help:
>
> # foreman-installer --help | grep implementation
> --capsule-puppet-server-implementation  Puppet master implementation,
> either "master" (traditional
>
> And then if I do a grep on reset, none of these commands exist?
>
> I tried noop with capsule-puppet-server-implementation=puppetserver with
> both --foreman-reset-puppet-X (as per your recommendation) and
> --reset-foreman-puppet-X (format in line with other options) and neither
> worked - all died with "ERROR: Unrecognised option '--X-puppet-autosign'"
>
>
> Any other pointers would be appreciated.
>
> cheers
> L.
>
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 17 February 2017 at 11:18, Lachlan Musicman  wrote:
>
>> Great - thanks all. VM snapshot from last week has been restored. We will
>> try again now.
>>
>> cheers
>> L.
>>
>> --
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>> On 16 February 2017 at 22:06, Daniel Lobato Garcia 
>> wrote:
>>
>>> On 02/13, Lachlan Musicman wrote:
>>> > Ok, I've found the itemized puppet upgrade instructions that are here:
>>> >
>>> > http://projects.theforeman.org/projects/foreman/wiki/
>>> > Upgrading_from_Puppet_3_to_4
>>> >
>>> > and the place where the doc'd process fails. I start there.
>>> >
>>> > When I get to Step 1b. Environments, SSL and Apache; part 5 states
>>> "Update
>>> > SSL paths in /etc/httpd/conf.d/05-foreman-ssl.conf or
>>> > /etc/apache2/sites-available/05-foreman-ssl.conf, changing
>>> > /var/lib/puppet/ssl to /etc/puppetlabs/puppet/ssl"
>>> >
>>> > but our /etc/httpd/conf.d/05-foreman-ssl.conf contains no reference to
>>> > *either* reference?
>>> >
>>> > Skip it.
>>> >
>>> > Go to next step, figuring we have little if any manual customisations,
>>> I do
>>> > step 2 and the first run give teh error
>>>
>>> I think all of these flags would be required and by removing them is why
>>> you see all of the errors. In order to use them, I think you can by
>>> appending --foreman to them, like:
>>>
>>>--foreman-puppet-server-implementation
>>>--foreman-reset-puppet-autosign
>>>etc...
>>>
>>> >
>>> > ERROR: Unrecognised option '--puppet-server-implementation'
>>> >
>>> > remove it, get
>>> >
>>> > ERROR: Unrecognised option '--reset-puppet-autosign'
>>> >
>>> > remove it, get
>>> >
>>> > ERROR: 

Re: [foreman-users] Re: Installable errata is not updated

[Eric D Helms]

What version of Katello are you running?

On Dec 8, 2016 5:47 AM, "yannig rousseau"  wrote:

> Hi all,
>
> In case anyone is interested.
> The task which recalculate "installable errata" depending on installed
> package is :
> *Generate applicability {"services_checked"=>...
> *
> This task seems to be automatically launched at the end of an successfull
> "Install erratum" task or when installing / removing package on
> content-host manually, but it will update only for the installed / removed
> package.
>
> On my instance those task were correctly generated but failed with error
>
> Trying to use logger katello/pulp_rest which has not been configured.
>
>
> With an update of my server + a reboot, pulp seems to function better now
> but I don't know what was originally the issue. If I resume one of the
> failed task, it does finish correctly & update the installable errata list.
>
> My issue now is : How to update massively for all package / content-host
> (other than manually restarting "Generate applicability" tasks) ??
>
> Regards
>
> On Wednesday, 7 December 2016 11:36:03 UTC+1, yannig rousseau wrote:
>>
>> Hi all,
>>
>> I just migrate to a katello instance to install errata (previously we
>> just used it as a repository.
>> Within content host view, I can install errata correctly. Tasks tab
>> indicate task as finished with success, package tab is correctly updated,
>> but within errata tab it is still indicated as installable ...
>>
>> Is that a normal behavior ? If not, how should I investigate this issue ?
>>
>> Regards
>> Yannig Rousseau
>>
>> OS= Oracle Linux 6.7
>> package version : katello-2.4.0-7 / pulp-server-2.6.4-1 / foreman-1.10.2-1
>>
>>
>>
>> --
> 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.
>

-- 
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 repositories

[Eric D Helms]

That is correct. The client repo is all you should need on clients.

On Dec 6, 2016 12:27 AM, "Lachlan Musicman"  wrote:

> Hola,
>
> Investigating the Katello repos, I see there are 4 - pulp, client,
> candlepin and katello
>
> At the moment my understanding of what these are:
>
> katello - the foreman plugin, goes on the "foreman/katello server"
> (satellite server in RHEL speak)
> candlepin - used on the foreman/katello server, not needed on the clients
> pulp - used on the foreman/katello server, not needed on the clients
>
> client - the end point that goes on each "enrolled" system. Put onto
> systems that have their software managed by Foreman/Katello.
>
> Is that a roughly correct breakdown?
>
> (I'm trying to improve our current Content Views and I want to put some
> repos in 'client' and some in 'not client' for various services)
>
> 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.
>

-- 
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 1.13.2 EL6 Released

[Eric D Helms]

The unofficial 1.13 EL6 repository has been updated to include the Foreman
1.13.2 release. This also includes rubygem-sinatra and dependencies to fix
the broken foreman-proxy installs on EL6.

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

-- 
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 and Katello EL6 Deprecations

[Eric D Helms]

All,

There have been comments and release notes around EL6 support but I wanted
to take the time to make sure users see the information and are aware of
the deprecations.

As of Foreman 1.13, EL6 was officially dropped as a supported operating
system. An official repository of EL6 builds exists for 1.13 extending the
life of Foreman on EL6 for that release and that release alone.

The Katello 3.2 release is the last release stream that will have support
for EL6. For Katello 3.3 and beyond, only EL7 releases will be made
available. We will be working on a strategy to help users migrate their EL6
installations to EL7 and please reach out to us if you have questions
regrading this.

Further, we recommend ALL new installs of 1.13 or 3.2 be done on an EL7 box.

To reiterate, Foreman 1.14 and Katello 3.2 will NOT be provided on EL6. The
1.13 and 3.2 streams will continue to receive updates per our normal
support policy.

-- 
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] Upgrade 2.3 -> 3.2

[Eric D Helms]

In theory yes, but I don't know anyone who has tested that path. If you can
clone your system or do a full backup before you try that would be
recommended. Otherwise you can try going through the version upgrades
incrementally.

On Tue, Nov 29, 2016 at 11:07 AM, Kastytis T <kastyti...@gmail.com> wrote:

> Hi everyone,
>
> is it safe to perform katello upgrade from version 2.3 to 3.2 ?
>
> --
> 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.
>



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

-- 
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 documentation moved to theforeman.org

[Eric D Helms]

All,

The katello.org site has moved all pages and documentation to live under
theforeman.org website. You can now find Katello documentation in the
plugin section [1]. The katello.org website has been updated to indicate
this to users. As well, any old links or bookmarks you may have should
redirect you to the new location on theforeman.org for a time. So please
update your bookmarks as you are redirected.

[1] https://theforeman.org/plugins/katello/


Eric

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

-- 
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 and Katello Ansible Module

[Eric D Helms]

Howdy,

The ansible-modules-extras [1] repository now contains the beginnings of
Foreman and Katello modules for managing resources with Ansible. This will
be officially included with Ansible 2.3.

The functionality contained within is a subset of functionality that I
required to manage some entities and serves as a basis for additional
changes and entities to be added. Now that it's contained within the
repository, I can open it up to any contributors that would like to add
functionality as well.

I'd love to hear any feedback you have, or review any contributions. Feel
free to drop me an email or ping if you open a PR that needs review or have
questions while using it. If you have requests for functionality before the
2.3 release, share that as well and I'll see what I can do to get it in.


[1]
https://github.com/ansible/ansible-modules-extras/tree/devel/infrastructure/foreman

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

-- 
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] Officially Unofficial Foreman 1.13 on EL6 Now Available

[Eric D Helms]

Foreman 1.13.1 and associated plugins have now been released into this
repository for EL6.


Eric

On Tue, Oct 18, 2016 at 2:27 AM, Ivan Necas <ine...@redhat.com> wrote:

> Eric D Helms <ericdhe...@gmail.com> writes:
>
> > All,
> >
> > Given that Foreman has officially dropped EL6 support for 1.13, we are
> > providing a set of EL6 builds for existing Foreman users as well as
> Katello
> > users who may not have been aware of the impending support drop. The
> builds
> > are being hosted with Katello's repositories and are signed by the
> Katello
> > GPG key. This includes an EL6 plugins repository as well (although, like
> > usual, they are not signed).
> >
> > We will be working to ensure that for each Foreman z-stream release, we
> > will rebuild the EL6 repositories with the updates and provide them
> within
> > a few days of the official Foreman release.
> >
> > Known Issues:
> >
> > Base Foreman installation will fail with a TFTP error that will ideally
> be
> > fixed by having [1] included in Foreman 1.13.1.
> >
> > We do not plan to build and support Foreman 1.14 and beyond on EL6 which
> > also means Katello will be moving off EL6 then as well. So please
> consider
> > planning a migration strategy to continue getting updates if you are on
> > EL6. The Katello team will be working to build out a migration path and
> > strategy to ensure there is a supported path to go from EL6 to El7. If
> you
> > have questions or concerns please reach out to us so we can help with
> this
> > effort.
> >
> > For Katello 3.2 RC users, expect an EL6 Katello build to follow in the
> next
> > few days.
>
> Thanks Eric, Daniel and anyone else involved! I think this was an
> important step to do before the actual move from rhel6
>
> -- Ivan
>
> >
> >
> > Thanks,
> > Eric
> >
> >
> > [1] https://github.com/theforeman/puppet-foreman_proxy/pull/293
> >
> >
> > --
> > 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.
>
> --
> 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.
>



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

-- 
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] Officially Unofficial Foreman 1.13 on EL6 Now Available

[Eric D Helms]

All,

Given that Foreman has officially dropped EL6 support for 1.13, we are
providing a set of EL6 builds for existing Foreman users as well as Katello
users who may not have been aware of the impending support drop. The builds
are being hosted with Katello's repositories and are signed by the Katello
GPG key. This includes an EL6 plugins repository as well (although, like
usual, they are not signed).

We will be working to ensure that for each Foreman z-stream release, we
will rebuild the EL6 repositories with the updates and provide them within
a few days of the official Foreman release.

Known Issues:

Base Foreman installation will fail with a TFTP error that will ideally be
fixed by having [1] included in Foreman 1.13.1.

We do not plan to build and support Foreman 1.14 and beyond on EL6 which
also means Katello will be moving off EL6 then as well. So please consider
planning a migration strategy to continue getting updates if you are on
EL6. The Katello team will be working to build out a migration path and
strategy to ensure there is a supported path to go from EL6 to El7. If you
have questions or concerns please reach out to us so we can help with this
effort.

For Katello 3.2 RC users, expect an EL6 Katello build to follow in the next
few days.


Thanks,
Eric


[1] https://github.com/theforeman/puppet-foreman_proxy/pull/293


-- 
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] Re: Katello 3.0.2 API content upload not updating info

[Eric D Helms]

Can you try an upload with hammer? Do you see the same behavior?

On Aug 10, 2016 5:15 AM, "Edgars M."  wrote:

> Hi
>
> I have the same issue. To workaround this I had to create local repo on
> Katello server with createrepo and then sync it in Katello with
> file:///path/to/repo URL. Then it worked.
>
> Edgars
>
> trešdiena, 2016. gada 10. augusts 07:39:05 UTC+2, Dylan Baars rakstīja:
>>
>> I am attempting to use the Katello API to upload content into a
>> repository - we are using Jenkins to package an RPM and upload it into
>> Katello for deployment. This worked fine with the 3.0 RCs, however in 3.0.2
>> although everything seems to complete successfully, I am not seeing the
>> package in the GUI -
>>
>> I followed the "Uploading content to the satellite server" example from
>> https://access.redhat.com/documentation/en-US/Red_Hat_
>> Satellite/6.1/html/API_Guide/curl-examples.html
>>
>> The steps and output I do are below (the output is from Jenkins)
>>
>> + byte=500
>> + offset=0
>> + /usr/bin/rm uploadlist.000 uploadlist.001
>> + split --bytes 500 --numeric-suffixes --suffix-length=3
>> tomcat8-8.5.4-1.noarch.rpm uploadlist.
>> + shopt -s nullglob
>> + array=(uploadlist.*)
>> ++ curl -s -H Accept:application/json,version=2 -H
>> Content-Type:application/json -X POST -u jenkins:removed -k -d '{}'
>> https://wellkatello.niwa.local/katello/api/repositories/
>> 1406/content_uploads
>> + RESPONSE='{"upload_id":"4376d1f2-a9f0-451d-b888-3b53e496581c
>> ","_href":"/pulp/api/v2/content/uploads/4376d1f2-a9f0-
>> 451d-b888-3b53e496581c/"}'
>> ++ echo '{"upload_id":"4376d1f2-a9f0-451d-b888-3b53e496581c","_href"
>> :"/pulp/api/v2/content/uploads/4376d1f2-a9f0-451d-b888-3b53e496581c/"}'
>> ++ sed 's/"//g'
>> ++ grep -e '.*"upload_id":\s*"\([a-zA-Z0-9-]\)*"' -o
>> ++ sed 's/{"upload_id"://'
>> + REQUEST_ID=4376d1f2-a9f0-451d-b888-3b53e496581c
>> + echo 'Request ID [4376d1f2-a9f0-451d-b888-3b53e496581c] created'
>> Request ID [4376d1f2-a9f0-451d-b888-3b53e496581c] created
>> + for file in '"${array[@]}"'
>> + echo 'Offset is 0'
>> Offset is 0
>> + echo 'Uploading chunk uploadlist.000'
>> Uploading chunk uploadlist.000
>> + curl -H Accept:application/json,version=2 -H
>> Content-Type:multipart/form-data -X PUT -u jenkins:removed -k
>> --data-urlencode content@uploadlist.000 --data-urlencode offset=0
>> https://wellkatello.niwa.local/katello/api/repositories/
>> 1406/content_uploads/4376d1f2-a9f0-451d-b888-3b53e496581c
>>   % Total% Received % Xferd  Average Speed   TimeTime Time
>>  Current
>>  Dload  Upload   Total   SpentLeft
>>  Speed
>>
>>   0 00 00 0  0  0 --:--:-- --:--:-- --:--:--
>> 0
>> 100 11.8M0 0  100 11.8M  0  10.1M  0:00:01  0:00:01 --:--:--
>> 10.1M
>> 100 11.8M0 0  100 11.8M  0  5597k  0:00:02  0:00:02 --:--:--
>> 5598k
>> 100 11.8M0 0  100 11.8M  0  3827k  0:00:03  0:00:03 --:--:--
>> 3828k
>> 100 11.8M0 0  100 11.8M  0  2907k  0:00:04  0:00:04 --:--:--
>> 2908k
>> 100 11.8M0 1  100 11.8M  0  2745k  0:00:04  0:00:04 --:--:--
>> 2745k
>>  + offset=500
>> + for file in '"${array[@]}"'
>> + echo 'Offset is 500'
>> Offset is 500
>> + echo 'Uploading chunk uploadlist.001'
>> Uploading chunk uploadlist.001
>> + curl -H Accept:application/json,version=2 -H
>> Content-Type:multipart/form-data -X PUT -u jenkins:removed -k
>> --data-urlencode content@uploadlist.001 --data-urlencode offset=500
>> https://wellkatello.niwa.local/katello/api/repositories/
>> 1406/content_uploads/4376d1f2-a9f0-451d-b888-3b53e496581c
>>   % Total% Received % Xferd  Average Speed   TimeTime Time
>>  Current
>>  Dload  Upload   Total   SpentLeft
>>  Speed
>>
>>   0 00 00 0  0  0 --:--:-- --:--:-- --:--:--
>> 0
>> 100 6590k0 0  100 6590k  0  5647k  0:00:01  0:00:01 --:--:--
>> 5652k
>> 100 6590k0 0  100 6590k  0  3039k  0:00:02  0:00:02 --:--:--
>> 3041k
>> 100 6590k0 1  100 6590k  0  2643k  0:00:02  0:00:02 --:--:--
>> 2643k
>>  + offset=1000
>> + echo 'Importing upload into repository'
>> Importing upload into repository
>> + curl -H Accept:application/json,version=2 -H
>> Content-Type:application/json -X PUT -u jenkins:removed -k -d
>> '{"upload_ids":["4376d1f2-a9f0-451d-b888-3b53e496581c"]}'
>> https://wellkatello.niwa.local/katello/api/repositories/
>> 1406/import_uploads
>>   % Total% Received % Xferd  Average Speed   TimeTime Time
>>  Current
>>  Dload  Upload   Total   SpentLeft
>>  Speed
>>
>>   0 00 00 0  0  0 --:--:-- --:--:-- --:--:--
>> 0
>> 100550 0  10055  0 44  0:00:01  0:00:01 --:--:--
>>44
>> 100550 0  10055  0 24  0:00:02  0:00:02 --:--:--
>>24
>>  98560 0  10055 

Re: [foreman-users] yum update, package fails "requested range not satisfiable"

[Eric D Helms]

Dylan,

Can you wget the package from the HTTP repository published by Katello that
should have the RPM? Can you yum localinstall from the published HTTP
repository on Katello?


Eric

On Wed, Jul 27, 2016 at 8:20 PM, Dylan Baars <baa...@gmail.com> wrote:

> Hi,
>
> we have synced (and been syncing) the Jenkins LTS release for RH for
> months now, which is this repo http://pkg.jenkins-ci.org/redhat-stable/
> They have added a new RPM, jenkins-2.7.1-1.1.noarch.rpm
> <http://pkg.jenkins-ci.org/redhat-stable/jenkins-2.7.1-1.1.noarch.rpm> and
> our local katello has synced that, however now when trying to run a "yum
> update" I get
>
> jenkins-2.7.1-1.1.noarch.rpm   FAILED
>
> https://wellkatello.niwa.local/pulp/repos/NIWA/Dev-Server/CentOS7_Server/custom/Jenkins/Jenkins_LTS/jenkins-2.7.1-1.1.noarch.rpm:
> [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable ]
>  0.0 B/s |0 B  --:--:-- ETA
> Trying other mirror.
>
>
> Error downloading packages:
>   jenkins-2.7.1-1.1.noarch: [Errno 256] No more mirrors to try.
>
> I can manually download the file from the pkg.jenkins-ci.org repo and do
> a "yum localinstall" - works fine. What's happening with the above?
>
> Dylan
>
> --
> 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.
>



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

-- 
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 capsule content sync super slow?

[Eric D Helms]

Dylan,

Are you able to determine the network traffic between the server and
capsule? In general I think there are two possibilities, slow transfer of
data to the Capsule or slowness on the Capsule itself. I would recommend
checking the network speeds and the Capsule resources to see if its
constrained I/O wise or processes are eating the CPU.


Eric

On Tue, Jul 26, 2016 at 10:52 PM, Dylan Baars <baa...@gmail.com> wrote:

> Hi all,
>
> we have a katello 3.0.1 install with a katello capsule in our DMZ.
>
> we've noticed if we publish/promote content, the main katello server does
> this reasonably quickly, but tasks (to sync content) on the capsule are
> taking hours to complete to match the change on the main server. Does
> anyone know why this is? Can it be improved?
>
> Thanks!
> Dylan
>
> --
> 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.
>



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

-- 
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: Katello 3.0.2 (Saison) Released

[Eric D Helms]

No worries! Certs don't always make it easy -- glad to hear its working!

Eric

On Tue, Jul 26, 2016 at 9:49 AM, Edgars M. <edgars.maz...@gmail.com> wrote:

> Hi Eric
>
> I re-generated all certs and re-downloaded CA cert again and now it works!
> I have no idea what was wrong with them. Sorry about all the noise :)
>
> Edgars
>
> trešdiena, 2016. gada 6. jūlijs 22:51:48 UTC+2, Eric Helms rakstīja:
>>
>> Katello 3.0.2 has been released to supply bug fixes and major upgrade
>> issues found by some awesome users. Please see the changelog for more
>> information (
>> https://github.com/Katello/katello/blob/KATELLO-3.0/CHANGELOG.md).
>>
>> Installation
>> 
>>
>> For installation, please see the instructions at:
>>
>>Server: http://www.katello.org/docs/3.0/installation/index.html
>> <http://www.katello.org/docs/2.4/installation/index.html>
>>Capsule: http://www.katello.org/docs/3.0/installation/capsule.html
>> <http://www.katello.org/docs/2.4/installation/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.0.2.
>>
>>http://projects.theforeman.org/projects/katello/issues/new
>>
>>
>> --
>> Eric D. Helms
>> Red Hat Engineering
>> Ph.D. Student - North Carolina State University
>>
> --
> 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.
>



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

-- 
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] Cannot upgrade packages on client / not able to use pulp-admin

[Eric D Helms]

I didn't see it mentioned that you had the katello-agent installed on the
client. Can you double check that and that goferd is running?

On Tue, Jul 19, 2016 at 10:51 AM, <psch...@puzzle.ch> wrote:

>  Hi There
>
> I have the following problem while installing Katello. I did follow the
> install guide on http://www.katello.org/docs/3.0/installation/index.html
>
> We did a "standard" install without any options:
>
> foreman-installer --scenario katello
>
>
> Install went fine. I was able to connect a client using subscription
> manager, was abel to include repositories and sync then. The I wanted to
> upgrade a package on the testserver by clicking in the webgui:
>
> hosts > content hosts > click on name of testserver the > packages, select
> a package and choose "update all"
>
>
> But the the process takes forever without completing (progress bar jumps
> to 50%):
>
> The I have a look at the details:
>
> Id: c3ba7122-9af3-4828-a98f-b1be6cf9249e
> Label: Actions::Katello::Host::Package::Update
> Name: Update package
> Owner: admin
> Execution type: Delayed
> Start at: 2016-07-19 16:33:22 +0200
> Start before: -
> Started at: 2016-07-19 16:33:23 +0200
> Ended at:
> State: running
> Result: -
> Params:
>
> I the wanted to use pulp-admin to debug why pulp is waiting, but wasn't
> able to use pulp-admin:
> [root@hssvr115 certs]#  pulp-admin login -uadmin -pX
> Successfully logged in. Session certificate will expire at Jul 26 14:38:39
> 2016
> GMT.
>
> [root@hssvr115 certs]# pulp-admin -vvv tasks list
> +--+
>  Tasks
> +--+
>
> 2016-07-19 16:39:06,790 - DEBUG - sending POST request to
> /pulp/api/v2/tasks/search/
> 2016-07-19 16:39:06,802 - ERROR - Client-side exception occurred
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/pulp/client/extensions/core.py",
> line 474, in run
> exit_code = Cli.run(self, args)
>   File "/usr/lib/python2.7/site-packages/okaara/cli.py", line 974, in run
> exit_code = command_or_section.execute(self.prompt, remaining_args)
>   File
> "/usr/lib/python2.7/site-packages/pulp/client/extensions/extensions.py",
> line 210, in execute
> return self.method(*arg_list, **clean_kwargs)
>   File "/usr/lib/python2.7/site-packages/pulp/client/admin/tasks.py", line
> 82, in list
> task_objects = self.retrieve_tasks(**kwargs)
>   File "/usr/lib/python2.7/site-packages/pulp/client/admin/tasks.py", line
> 294, in retrieve_tasks
> fields=self.FIELDS)
>   File "/usr/lib/python2.7/site-packages/pulp/bindings/tasks.py", line
> 147, in search
> tasks = super(TaskSearchAPI, self).search(**kwargs)
>   File "/usr/lib/python2.7/site-packages/pulp/bindings/search.py", line
> 95, in search
> response = self.server.POST(self.PATH, {'criteria': kwargs})
>   File "/usr/lib/python2.7/site-packages/pulp/bindings/server.py", line
> 100, in POST
> log_request_body=log_request_body, ignore_prefix=ignore_prefix)
>   File "/usr/lib/python2.7/site-packages/pulp/bindings/server.py", line
> 152, in _request
> response_code, response_body = self.server_wrapper.request(method,
> url, body)
>   File "/usr/lib/python2.7/site-packages/pulp/bindings/server.py", line
> 349, in request
> raise exceptions.ConnectionException(None, str(err), None)
> ConnectionException: (None, 'tlsv1 alert unknown ca', None)
> An error occurred attempting to contact the server. More information may be
> found using the -v flag.
>
> [root@hssvr115 certs]#
>
> So why am I having the "'tlsv1 alert unknown ca', None" error? I didn't
> specify anything special while using katello-installer.
>
> Any ideas?
>
> thanks philippe
>
> --
> 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.
>



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

-- 
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] Attaching subscriptions/products no longer adds yum repo

[Eric D Helms]

Does the host show as having that subscription in the UI?

On Jul 18, 2016 11:23 AM, "Peter Kirby" 
wrote:

> I'm facing an issue where when I attach a subscription via
> "subscription-manger attach --pool xxx" is successfully
> attaches the subscription, but redhat.repo is not longer updated to include
> the new repo data.
>
> This has happened before and I ended up just wiping the entire foreman
> server and rebuilding it fresh.  Everything worked fine after that, but now
> the problem has returned.  I can't just rebuild everything every few weeks.
>
> I've checked all the log files I could find including
> /var/log/rhsm/rhsm.log and I cannot find any errors.
>
> I've tried deleting the rhsm cache and running subscription-manager
> refresh, but nothing changes redhat.repo anymore.
>
> Has anyone run into this before or have any suggestions for things to try?
>
> Thank you,
> Peter
>
> 
>
> --
> 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.
>

-- 
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: Katello 3.1 RC1 Released

[Eric D Helms]

Today, Katello only supports el6 and el7 installations but with a variety
of clients.

On Jul 18, 2016 9:19 AM, "Duncan Innes"  wrote:

> Sorry - for installation.
>
> Was just taking the Foreman installation OS options as examples here.
>
> Ideally I'd run Katello on a CentOS7 guest, but the host OS will be Fedora
> 24 for which I'll be trying to get libvirt smart-proxy working.
>
> D
>
> On Monday, 18 July 2016 14:09:13 UTC+1, Eric Helms wrote:
>>
>> For installation purposes or client support?
>>
>> On Jul 18, 2016 8:10 AM, "Duncan Innes"  wrote:
>>
>>> Hi,
>>>
>>> Is Katello 3.1 not going to support the same OS platforms as Foreman
>>> 1.12 is doing?
>>>
>>> i.e. Fedora 24 for my purpose, but others may look to Debian & Ubuntu
>>>
>>> Cheers
>>>
>>> Duncan
>>>
>>> On Monday, 11 July 2016 13:52:50 UTC+1, jsherril wrote:


 We are happy to announce the first release candidate for Katello 3.1
 (California Common).

 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.1 is in our release notes:
 http://www.katello.org/docs/3.1/release_notes/release_notes.html


 Installation or Upgrade
 ===

 For installation, please see the instructions at:

   Server:  http://www.katello.org/docs/3.1/installation/index.html
   Capsule:  http://www.katello.org/docs/3.1/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.1/upgrade/index.html
   Capsule:  http://www.katello.org/docs/3.1/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.1.0.

   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.
>>>
>> --
> 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.
>

-- 
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: Katello 3.1 RC1 Released

[Eric D Helms]

For installation purposes or client support?

On Jul 18, 2016 8:10 AM, "Duncan Innes"  wrote:

> Hi,
>
> Is Katello 3.1 not going to support the same OS platforms as Foreman 1.12
> is doing?
>
> i.e. Fedora 24 for my purpose, but others may look to Debian & Ubuntu
>
> Cheers
>
> Duncan
>
> On Monday, 11 July 2016 13:52:50 UTC+1, jsherril wrote:
>>
>>
>> We are happy to announce the first release candidate for Katello 3.1
>> (California Common).
>>
>> 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.1 is in our release notes:
>> http://www.katello.org/docs/3.1/release_notes/release_notes.html
>>
>>
>> Installation or Upgrade
>> ===
>>
>> For installation, please see the instructions at:
>>
>>   Server:  http://www.katello.org/docs/3.1/installation/index.html
>>   Capsule:  http://www.katello.org/docs/3.1/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.1/upgrade/index.html
>>   Capsule:  http://www.katello.org/docs/3.1/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.1.0.
>>
>>   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.
>

-- 
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: Katello 3.0.2 (Saison) Released

[Eric D Helms]

disable it? Can I disable everything related
>>> to Puppet as we don't need that functionality?
>>>
>>> I just tested it and it failed again, here is my full install command:
>>>
>>> sudo foreman-installer --scenario katello \
>>> --certs-server-cert="/etc/pki/tls/certs/katello.tld.crt" \
>>> --certs-server-cert-req="/etc/pki/tls/csr/katello.tld.csr" \
>>> --certs-server-key="/etc/pki/tls/private/katello.tld.key" \
>>> --certs-server-ca-cert="/etc/pki/tls/certs/CompanyInternalCA.crt" \
>>> --foreman-admin-email="n...@company.tld" \
>>> --foreman-admin-first-name="Name" \
>>> --foreman-admin-last-name="LastName" \
>>> --foreman-admin-password="SomeCustomPassword" \
>>> --foreman-initial-organization="Company" \
>>> --katello-num-pulp-workers="24" \
>>> --katello-proxy-url="http://corporate.proxy.tld; \
>>> --katello-proxy-port="8080" \
>>> --verbose
>>>
>>>
>>> Errors:
>>> [ERROR 2016-07-08 10:48:00 verbose]  Could not start Service[httpd]:
>>> Execution of 
>>> '/usr/share/katello-installer-base/modules/service_wait/bin/service-wait
>>> start httpd' returned 1: Redirecting to /bin/systemctl start  httpd.
>>> service
>>> [ INFO 2016-07-08 10:48:00 verbose] Job for httpd.service failed
>>> because the control process exited with error code. See "systemctl
>>> status httpd.service" and "journalctl -xe" for details.
>>> [ERROR 2016-07-08 10:48:00 verbose]  /Stage[main]/Apache::Service/
>>> Service[httpd]/ensure: change from stopped to running failed: Could not
>>> start Service[httpd]: Execution of 
>>> '/usr/share/katello-installer-base/modules/service_wait/bin/service-wait
>>> start httpd' returned 1: Redirecting to /bin/systemctl start  httpd.
>>> service
>>> [ERROR 2016-07-08 10:48:18 verbose]  /Stage[main]/Foreman::Database/
>>> Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: Failed to call
>>> refresh: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]
>>> [ERROR 2016-07-08 10:48:18 verbose]  /Stage[main]/Foreman::Database/
>>> Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: /usr/sbin/foreman-rake
>>> db:seed returned 1 instead of one of [0]
>>> [ERROR 2016-07-08 10:49:15 verbose]  /Stage[main]/Foreman_proxy::
>>> Register/Foreman_smartproxy[katello.tld]: Failed to call refresh: Proxy
>>> katello.tld cannot be registered (Could not load data from https:
>>> //katello.tld
>>> [ INFO 2016-07-08 10:49:15 verbose]  - is your server down?
>>> [ INFO 2016-07-08 10:49:15 verbose]  - was rake apipie:cache run when
>>> using apipie cache? (typical production settings)): N/A
>>> [ERROR 2016-07-08 10:49:15 verbose]  /Stage[main]/Foreman_proxy::
>>> Register/Foreman_smartproxy[katello.tld]: Proxy katello.tld cannot be
>>> registered (Could not load data from https://katello.tld
>>> [ INFO 2016-07-08 10:49:15 verbose]  - is your server down?
>>> [ INFO 2016-07-08 10:49:15 verbose]  - was rake apipie:cache run when
>>> using apipie cache? (typical production settings)): N/A
>>> [ INFO 2016-07-08 10:49:15 verbose] /usr/share/ruby/vendor_ruby/puppet/
>>> util/errors.rb:106:in `fail'
>>> [ INFO 2016-07-08 10:49:19 verbose] Executing hooks in group post
>>>   Something went wrong! Check the log for ERROR-level output
>>>
>>> sudo cat /var/log/httpd/crane_error_ssl.log
>>> [Fri Jul 08 10:48:00.480289 2016] [ssl:emerg] [pid 13049] AH01903:
>>> Failed to configure CA certificate chain!
>>> [Fri Jul 08 10:57:44.197492 2016] [ssl:emerg] [pid 13508] AH01903:
>>> Failed to configure CA certificate chain!
>>>
>>> Edgars
>>>
>>> ceturtdiena, 2016. gada 7. jūlijs 20:26:43 UTC+2, Eric Helms rakstīja:
>>>>
>>>> Edgars,
>>>>
>>>> I tested this scenario today and could not duplicate your results. Is
>>>> there anything special about your custom certificates? Wildcard? Attributes
>>>> special to them? This is my test scenario:
>>>>
>>>> https://github.com/Katello/forklift/pull/247/files
>>>>
>>>> On Thu, Jul 7, 2016 at 8:07 AM, Eric D Helms <ericd...@gmail.com>
>>>> wrote:
>>>>
>>>>> Edgars,
>>>>>
>>>>> I will test this today and report back to you.
>>>>>
>>>>>
>>

Re: [foreman-users] puppet modules and default organization view

[Eric D Helms]

Today this is not possible because we are not creating puppet environments
for the default content view in part due to how modules can have multiple
versions upload to a puppet repository. There is an open issue around this
[1] that would be great to get an upvote(s) on and information describing
your workflow to help us prioritize it.

[1] http://projects.theforeman.org/issues/8773

On Wed, Jun 22, 2016 at 11:05 AM, Nathanaël Blanchet <
digitall.fin...@gmail.com> wrote:

>  hello, is it possible to add puppet module to the default organization
> view?
>  I don't want to publish a new view each time I add a new puppet module
> from repo
> I thought it was possible the same way we usually do for getiing
> continuous rpm update with default organization view.
>  I thought it was default, but when looking at
> environment->library->default-organization->puppet modules, it says There
> are no Puppet Modules that match the criteria.
>
> katello 3.0/foreman 1.11.3
>
> --
> 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.
>



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

-- 
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 2.4] passenger status broken

[Eric D Helms]

On Tue, Jul 5, 2016 at 10:55 AM, Edson Manners <edson.mann...@gmail.com>
wrote:

> I've been struggling with this issue for a while and finally feel the need
> to seek external help.
>
> We used to run Foreman 1.9.3 on RHEL 7.2. the passenger-status command was
> used to tune the puppetmaster when the server got overwhelmed.
>
> [root@foreman ~]# cat /etc/redhat-release
> Red Hat Enterprise Linux Server release 7.2 (Maipo)
> [root@foreman ~]# which passenger-status
> /usr/bin/passenger-status
> [root@foreman ~]# rpm -q --whatprovides /usr/bin/passenger-status
> rubygem-passenger-4.0.18-9.8.el7.x86_64
> [root@foreman ~]# /usr/bin/passenger-status
> Version : 4.0.18
> Date: 2016-07-05 10:44:15 -0400
> Instance: 3376
> --- General information ---
> Max pool size : 48
> Processes : 3
> Requests in top-level queue : 0
>
> --- Application groups ---
> /usr/share/foreman#default:
>   App root: /usr/share/foreman
>   Requests in queue: 0
>   * PID: 18170   Sessions: 0   Processed: 622 Uptime: 4h 24m 28s
> CPU: 0%  Memory  : 232MLast used: 6s ago
> 
> ...
>
>
> We've moved to katello 2.4 on CentOS 7.2 and now passenger-status no
> longer works out of the box.
>
> [root@katello-test emanners]# cat /etc/redhat-release
> CentOS Linux release 7.2.1511 (Core)
> [root@katello-test emanners]# which passenger-status
> /sbin/passenger-status
> [root@katello-test emanners]# rpm -q --whatprovides
> /usr/sbin/passenger-status
> passenger-4.0.53-4.el7.x86_64
> [root@katello-test emanners]# /usr/sbin/passenger-status
> ERROR: Phusion Passenger doesn't seem to be running.
>
> I've managed to find a few posts on Google (not Katello related) that
> suggest the reason is multiple copies of passenger on the host.
> [root@katello-test ~]# locate passenger-status
> /opt/theforeman/tfm/root/usr/bin/passenger-status
>
> /opt/theforeman/tfm/root/usr/share/gems/gems/passenger-4.0.18/bin/passenger-status
> /opt/theforeman/tfm/root/usr/share/man/man8/passenger-status.8.gz
>

This set of passenger libraries are used for running the Foreman web
application under Apache within the SCL. To run the passenger-status
command for the SCL, you'd need to enable the SCL and run it:

scl enable tfm '/opt/theforeman/tfm/root/usr/bin/passenger-status'


> /usr/sbin/passenger-status
> /usr/share/man/man8/passenger-status.8.gz
>

This set of passenger libraries are used for running the puppetmaster that
is installed on the server by default which is running outside the SC and
should work like normal (barring a bug in newer passenger).


> [root@katello-test ~]# /opt/theforeman/tfm/root/usr/bin/passenger-status
> /opt/rh/ruby193/root/usr/bin/ruby: error while loading shared libraries:
> libruby.so.1.9: cannot open shared object file: No such file or directory
> [root@katello-test ~]#
> /opt/theforeman/tfm/root/usr/share/gems/gems/passenger-4.0.18/bin/passenger-status
> *** Phusion Passenger: no passenger_native_support.so found for the
> current Ruby interpreter. Compiling one (set
> PASSENGER_COMPILE_NATIVE_SUPPORT_BINARY=0 to disable)...
> # mkdir -p /root/.passenger/native_support/4.0.18/ruby-2.0.0-x86_64-linux
> # cd /root/.passenger/native_support/4.0.18/ruby-2.0.0-x86_64-linux
> # /usr/bin/ruby
> '/opt/theforeman/tfm/root/usr/share/gems/gems/passenger-4.0.18/ruby_extension_source/extconf.rb'
> /usr/bin/ruby: No such file or directory --
> /opt/theforeman/tfm/root/usr/share/gems/gems/passenger-4.0.18/ruby_extension_source/extconf.rb
> (LoadError)
> Compilation failed.
> ---
> Ruby native_support extension not loaded. Continuing without
> native_support.
> ERROR: Phusion Passenger doesn't seem to be running.
>
>
> So the question is which ones does Katello really need since they were
> both installed during the installer and how do I get this command working
> again without breaking the underlying app?
>
> --
> 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.
>



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

-- 
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.0] foreman-installer --help fails ("no documentation found for manifest")

[Eric D Helms]

   from
> /usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:88:in `map'
> from
> /usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:88:in `modules'
> from /usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:184
> :in `params'
> from
> /usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:193:in `
> preset_defaults_from_puppet'
> from
> /usr/share/gems/gems/kafo-0.7.4/lib/kafo/kafo_configure.rb:253:in
> `set_parameters'
> from /usr/share/gems/gems/kafo-0.7.4/lib/kafo/kafo_configure.rb:96
> :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.7.4/lib/kafo/kafo_configure.rb:
> 150:in `run'
> from /usr/sbin/foreman-installer:12:in `'
>
> Is this a bug I should report on the issue tracker or did I screw up my
> setup? Any helpful advice is appreciated, thanks for taking the time to
> read this!
>
> Marvin
>
> --
> 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.
>



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

-- 
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: Katello upgrade 2.4.4 -> 3.0, foreman-rake db:migrate returned 1 instead of [0]

[Eric D Helms]

Dylan,

You've hit an error that I spent the past two days debugging for another
user but have not been able to replicate locally. Couple of questions for
you:

1) do you have a backup of your 2.4 before upgrading?
2) If yes, would you be able to privately share backups of your database
with me from 2.4? If you are unable to share it out, would you be willing
to help by doing some live debugging on IRC or some other means?
On Jul 1, 2016 1:15 AM, "Dylan Baars"  wrote:

> I had a further error, final output below
>
> Upgrade Step: restart_services...
> Upgrade Step: db_seed...
> Upgrade Step: import_package_groups (this may take a while) ...
> Upgrade Step: import_rpms (this may take a while) ...
> Upgrade Step: import_distributions (this may take a while) ...
> Upgrade Step: import_puppet_modules (this may take a while) ...
> Upgrade Step: import_subscriptions (this may take a while) ...
> Upgrade Step: elasticsearch_message...
> Elasticsearch has been removed as a dependency. The database files can be
> removed manually with #rm -rf /var/lib/elasticsearch. Some packages are no
> longer needed and can be removed: #rpm -e ruby193-rubygem-tire
> tfm-rubygem-tire elasticsearch sigar-java sigar snappy-java lucene4-contrib
> lucene4
> Upgrade Step: add_export_distributor (this may take a while) ...
> Upgrade Step: remove_docker_v1_content (this may take a while) ...
> Upgrade Step: update_puppet_repository_distributors (this may take a
> while) ...
> Upgrade Step: update_subscription_facet_backend_data (this may take a
> while) ...
> Upgrade step update_subscription_facet_backend_data failed. Check logs for
> more information.
> [root@wellkatello ~]#
>
>
> I've created a ticket for it...
> http://projects.theforeman.org/issues/15558
>
> --
> 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.
>

-- 
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.0 upgrade from 3.0 RC8 no answer file exists?

[Eric D Helms]

For the record, we don't test or guarantee inter-RC upgrades. If you are
upgrading from 2.4, prior to the last round of commits after RC8 your
upgrade could end up in a position where the installer data is wrong or
missing values. If you are able to upgrade from your 2.4 to 3.0 we highly
recommend that. If not, we can try to fix your install.
On Jun 16, 2016 11:40 PM, "Dylan Baars"  wrote:

> Hi,
>
> I've run into a problem attempting to upgrade from RC8 to the production
> release, I get this message:
>
> foreman-installer --scenario katello --upgrade
> No answer file at /etc/katello-installer/answers.katello-installer.yaml
> found, can not continue
>
> I've done the following:
> 1. Updated kafo:
> rpm -ivh
> http://koji.katello.org/packages/rubygem-kafo/0.7.4/1.el7/noarch/rubygem-kafo-0.7.4-1.el7.noarch.rpm
>
> 2. Updated repos
> yum update -y
> http://fedorapeople.org/groups/katello/releases/yum/3.0/katello/el7/x86_64/katello-repos-latest.rpm
> yum update -y
> http://yum.theforeman.org/releases/1.11/el7/x86_64/foreman-release.rpm
>
> 3. Clean and update foreman-release-scl
> yum clean all
> yum update -y foreman-release-scl
>
> 4. Update the system
> yum -y update
>
> During this I spotted two warning/errors
>
> Warning: RPMDB altered outside of yum.
> ** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
> rubygem-kafo-0.7.4-1.el7.noarch is a duplicate with
> rubygem-kafo-0.7.2-1.el7.noarch
> (OK fine, I updated this above ;-) )
>
> warning: %posttrans(foreman-installer-katello-3.0.1-2.el7.noarch)
> scriptlet failed, exit status 23
> Non-fatal POSTTRANS scriptlet failure in rpm package
> foreman-installer-katello-3.0.1-2.el7.noarch
>
> /etc/katello-installer has these files in it
>
> -rw---. 1 root root 6950 Mar  7 12:32
> answers.katello-installer.yaml.backup
> -rw---. 1 root root 1583 Dec 24 04:34
> answers.katello-installer.yaml.rpmnew
> -rw---. 1 root root  702 Mar 26 07:32
> capsule-certs-generate.yaml.rpmsave
> drwx--. 2 root root   32 Mar  4 13:11 d20160304-16237-1y53b5q
> -rw---. 1 root root 2385 Jun 17 15:33 katello-installer.yaml
> -rw---. 1 root root 2565 Apr 22 17:19 katello-installer.yaml.backup
>
>
> If I copy the latest katello-installer.yaml to
> answers.katello-installer.yaml and try the upgrade it doesn't like that at
> all
>
> foreman-installer --scenario katello --upgrade
> /usr/share/gems/gems/kafo-0.7.4/lib/kafo/puppet_module.rb:155:in
> `get_name': undefined method `gsub' for :name:Symbol (NoMethodError)
> from
> /usr/share/gems/gems/kafo-0.7.4/lib/kafo/puppet_module.rb:18:in `initialize'
> from
> /usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:88:in `new'
> from
> /usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:88:in `block in
> modules'
> from
> /usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:88:in `map'
> from
> /usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:88:in `modules'
> from
> /usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:184:in `params'
> from
> /usr/share/gems/gems/kafo-0.7.4/lib/kafo/configuration.rb:193:in
> `preset_defaults_from_puppet'
> from
> /usr/share/gems/gems/kafo-0.7.4/lib/kafo/kafo_configure.rb:253:in
> `set_parameters'
> from
> /usr/share/gems/gems/kafo-0.7.4/lib/kafo/kafo_configure.rb:96: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.7.4/lib/kafo/kafo_configure.rb:150:in `run'
> from /sbin/foreman-installer:12:in `'
>
>
> Have I made a mistake in my upgrade process?
>
> --
> 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.
>

-- 
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: Katello 3.0 (Saison) Released

[Eric D Helms]

I see it:

https://fedorapeople.org/groups/katello/releases/yum/2.4/katello/RHEL/7Server/x86_64/tfm-rubygem-katello-2.4.4-1.el7.noarch.rpm
On Jun 17, 2016 6:25 AM, "Edgars M." <edgars.maz...@gmail.com> wrote:

> Hi
>
> I cannot find Katello 2.4.4 packages for CentOS 7.
> https://fedorapeople.org/groups/katello/releases/yum/2.4/katello/RHEL/7Server/x86_64/
> contains only Katello 2.4.1. Is there another repo?
>
> Edgars
>
> ceturtdiena, 2016. gada 16. jūnijs 17:21:14 UTC+2, Eric Helms rakstīja:
>>
>> Katello 3.0 (Saison) has been released! This has been a long release
>> process due to the large amount of features and bug fixes introduced with
>> over 650+ Redmine issues set to closed or resolved. This release is a
>> major version bump because it introduces some backwards incompatible
>> changes and the removal of all deprecations that existed through the 2.X
>> lifespan.
>>
>> UPGRADES - PLEASE READ
>> ==
>>
>> The features introduced in 3.0 bring changes that require some action and
>> thought before upgrading. We highly encourage reading over the pre-upgrade
>> considerations and the upgrade caveat before attempting any upgrades (
>> http://www.katello.org/docs/3.0/upgrade/index.html).
>>
>> Katello 2.4.4 has been released with special updates for upgrades. Please
>> ensure that you update to 2.4.4 and read through the upgrade steps on our
>> site before proceeding.
>>
>> Please feel free to contact us with questions before doing your upgrade
>> to ensure all your bases are covered. A big thanks to all the RC testers
>> that found a lot of upgrade issues prior to the release!
>>
>> Highlights
>> ===
>>
>>  * Foreman Remote Execution Integration
>>  * OSTree Content Support
>>  * Capsule Status Views
>>  * Lazy Sync
>>  * Mirror on Sync
>>  * Docker V2 Support
>>  * Inter-Server Sync
>>  * Host Unification
>>  * Installer Scenarios
>>
>> For a detailed list and information of the changes in Katello 3.0 is in
>> our release notes:
>> http://www.katello.org/docs/3.0/release_notes/release_notes.html
>>
>>
>> Installation
>> 
>>
>> For installation, please see the instructions at:
>>
>>Server: http://www.katello.org/docs/3.0/installation/index.html
>> <http://www.katello.org/docs/2.4/installation/index.html>
>>Capsule: http://www.katello.org/docs/3.0/installation/capsule.html
>> <http://www.katello.org/docs/2.4/installation/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.0.0.
>>
>>http://projects.theforeman.org/projects/katello/issues/new
>>
>> --
>> Eric D. Helms
>> Red Hat Engineering
>> Ph.D. Student - North Carolina State University
>>
> --
> 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.
>

-- 
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: Katello 3.0 (Saison) Released

[Eric D Helms]

They are -- can you point us to which ones you still see with rc8 in the
name?

On Thu, Jun 16, 2016 at 2:02 PM, Prasun Gera <prasun.g...@gmail.com> wrote:

> Are the repos the same as they were for the RC releases ? I see that some
> of the packages from that repo still have rc8 in the name.
>
> On Thu, Jun 16, 2016 at 11:30 AM, Duncan Innes <dun...@innes.net> wrote:
>
>> Yay \o/ great news.
>>
>> Congratulations for getting this over the finish line.  And thanks to all
>> the devs for their hard work.
>>
>> D
>>
>> --
>> 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.
>>
>
> --
> 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.
>



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

-- 
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.0 (Saison) Released

[Eric D Helms]

Katello 3.0 (Saison) has been released! This has been a long release
process due to the large amount of features and bug fixes introduced with
over 650+ Redmine issues set to closed or resolved. This release is a major
version bump because it introduces some backwards incompatible changes and
the removal of all deprecations that existed through the 2.X lifespan.

UPGRADES - PLEASE READ
==

The features introduced in 3.0 bring changes that require some action and
thought before upgrading. We highly encourage reading over the pre-upgrade
considerations and the upgrade caveat before attempting any upgrades (
http://www.katello.org/docs/3.0/upgrade/index.html).

Katello 2.4.4 has been released with special updates for upgrades. Please
ensure that you update to 2.4.4 and read through the upgrade steps on our
site before proceeding.

Please feel free to contact us with questions before doing your upgrade to
ensure all your bases are covered. A big thanks to all the RC testers that
found a lot of upgrade issues prior to the release!

Highlights
===

 * Foreman Remote Execution Integration
 * OSTree Content Support
 * Capsule Status Views
 * Lazy Sync
 * Mirror on Sync
 * Docker V2 Support
 * Inter-Server Sync
 * Host Unification
 * Installer Scenarios

For a detailed list and information of the changes in Katello 3.0 is in our
release notes:
http://www.katello.org/docs/3.0/release_notes/release_notes.html


Installation


For installation, please see the instructions at:

   Server: http://www.katello.org/docs/3.0/installation/index.html
<http://www.katello.org/docs/2.4/installation/index.html>
   Capsule: http://www.katello.org/docs/3.0/installation/capsule.html
<http://www.katello.org/docs/2.4/installation/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.0.0.

   http://projects.theforeman.org/projects/katello/issues/new

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

-- 
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.