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

2016-11-07 Thread Austin Smith
I am having the same issue.  did you find a fix?

On Friday, October 28, 2016 at 7:11:46 AM UTC-4, Denis Müller wrote:
>
> I wanted to try the new version of katello-capsule:
>
> Installed Repos:
>
> yum -y localinstall 
> http://fedorapeople.org/groups/katello/releases/yum/3.2/katello/el7/x86_64/katello-repos-latest.rpm
> yum -y localinstall 
> http://yum.theforeman.org/releases/1.13/el7/x86_64/foreman-release.rpm
> rpm -Uvh https://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm 
> (to provide puppet 4 from during installation)
> yum -y localinstall 
> http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
> yum -y install foreman-release-scl
>
> yum install -y katello-capsule
>
> foreman-installer --scenario capsule --help
> /usr/share/gems/gems/kafo-0.9.8/lib/kafo/puppet_module.rb:69:in `parse': No 
> Puppet module parser is installed and no cache of the file 
> /usr/share/katello-installer-base/modules/certs/manifests/init.pp is 
> available. Please check debug logs and install optional dependencies for the 
> parser. (Kafo::ParserError)
>
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/configuration.rb:89:in 
> `block in modules'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/configuration.rb:89:in 
> `map'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/configuration.rb:89:in 
> `modules'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/configuration.rb:189:in 
> `params'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/configuration.rb:199:in 
> `preset_defaults_from_puppet'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/kafo_configure.rb:270:in 
> `set_parameters'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/kafo_configure.rb:99:in 
> `initialize'
> from /usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:133:in `new'
> from /usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:133:in `run'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/kafo_configure.rb:154:in 
> `run'
> from /usr/sbin/foreman-installer:8:in `'
>
>
> rpm -qa | grep -i parser
> rubygem-kafo_parsers-0.1.2-1.el7.noarch
> yum-metadata-parser-1.1.4-10.el7.x86_64
>
> Name   : rubygem-kafo_parsers
> Architektur : noarch
> Version: 0.1.2
> Ausgabe: 1.el7
>
>
> Greets,
> Denis
>
>
>

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


Re: [foreman-users] Upgrade Failure on db:migrate v1.7.5 to 1.13 - what now?

2016-10-21 Thread Austin Smith
Thanks for the clarification :)

On Oct 21, 2016 8:03 PM, "Greg Sutcliffe" <greg.sutcli...@gmail.com> wrote:

> On 21 October 2016 at 14:59, Austin Smith <smith.aus...@gmail.com> wrote:
>
>> Thank you for the guidance - I will probably deploy a new instance then
>> to "keep it clean"
>>
>> Curious as well - Is it a better practice to put katello on a separate
>> instance or install on same as foreman?  Very low node count - 100 MAX in
>> the next year.
>>
>
> Katello is a Foreman plugin, it can't be deployed as a standalone
> application. Thus, you'll want it all on one box :)
>
> Greg
>
> --
> 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/wX_3S7J_LXk/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.


Re: [foreman-users] Upgrade Failure on db:migrate v1.7.5 to 1.13 - what now?

2016-10-21 Thread Austin Smith
Thank you for the guidance - I will probably deploy a new instance then to 
"keep it clean"

Curious as well - Is it a better practice to put katello on a separate 
instance or install on same as foreman?  Very low node count - 100 MAX in 
the next year.

On Friday, October 21, 2016 at 3:05:12 AM UTC-4, Dominic Cleal wrote:
>
> On 21/10/16 04:24, Austin Smith wrote: 
> > Ahh.. I see :( 
> > 
> > I elected for reinstall - and received this error upon running 
> > foreman-installer: 
> > 
> > | 
> >  Executionof '/usr/bin/yum -d 0 -e 0 -y list 
> > ruby193-rubygem-passenger-native'returned 1:Error:Nomatching Packagesto 
> list 
> > | 
>
> We've not used this package name in quite a few versions. How exactly 
> are you reinstalling, and are you using an answers file from an old 
> version? 
>
> If so then you might have a few changes to make the answers file work. 
> For this error, add 
> --foreman-passenger-ruby-package=tfm-rubygem-passenger-native to update 
> the package name. If you didn't intend to use an old answers file, 
> delete it from /etc/foreman-installer before reinstalling the 
> foreman-installer package. 
>
> -- 
> Dominic Cleal 
> dom...@cleal.org  
>

-- 
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 Failure on db:migrate v1.7.5 to 1.13 - what now?

2016-10-19 Thread Austin Smith
ord-4.2.5.1/lib/active_record/migration.rb:654:in
> `method_missing'
> /usr/share/foreman/db/migrate/20151104100257_add_hosts_count_to_hostgroup.rb:3:in
> `up'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:611:in
> `exec_migration'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:592:in
> `block (2 levels) in migrate'
> /opt/rh/rh-ruby22/root/usr/share/ruby/benchmark.rb:288:in `measure'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:591:in
> `block in migrate'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:292:in
> `with_connection'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:590:in
> `migrate'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:768:in
> `migrate'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:998:in
> `block in execute_migration_in_transaction'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:1046:in
> `ddl_transaction'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:997:in
> `execute_migration_in_transaction'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:959:in
> `block in migrate'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:955:in
> `each'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:955:in
> `migrate'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:823:in
> `up'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:801:in
> `migrate'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/tasks/database_tasks.rb:137:in
> `migrate'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/railties/databases.rake:44:in
> `block (2 levels) in '
> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/task.rb:240:in
> `call'
> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/task.rb:240:in
> `block in execute'
> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/task.rb:235:in
> `each'
> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/task.rb:235:in
> `execute'
> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/task.rb:179:in
> `block in invoke_with_call_chain'
> /opt/rh/rh-ruby22/root/usr/share/ruby/monitor.rb:211:in `mon_synchronize'
> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/task.rb:172:in
> `invoke_with_call_chain'
> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/task.rb:165:in
> `invoke'
> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:150:in
> `invoke_task'
> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:106:in
> `block (2 levels) in top_level'
> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:106:in
> `each'
> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:106:in
> `block in top_level'
> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:115:in
> `run_with_threads'
> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:100:in
> `top_level'
> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:78:in
> `block in run'
> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:176:in
> `standard_exception_handling'
> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:75:in
> `run'
> /opt/rh/rh-ruby22/root/usr/bin/rake:33:in `'
> Tasks: TOP => db:migrate



Honestly, we have a minimal amount of hosts - and are trying to get katello
going.  Almost debating if it would be faster to just stand up a new
instance ;)  Using git for all the puppet code, so do not have many
concerns.

Do you know a quick fix or should I pursue the "fresh start" ?

Austin Smith A+, NET+, MCSA
www.digitalson.com
770.833.9188 Direct


On Wed, Oct 19, 2016 at 5:11 AM, Dominic Cleal <domi...@cleal.org> wrote:

> On 19/10/16 10:09, Austin Smith wrote:
> > Thank you for the reply - wonder why this did not show up in search
> > results.  If appears to have run successfully w/o a restoration of the
> DB.
> >
> > I would like

Re: [foreman-users] Upgrade Failure on db:migrate v1.7.5 to 1.13 - what now?

2016-10-19 Thread Austin Smith
Thank you for the reply - wonder why this did not show up in search 
results.  If appears to have run successfully w/o a restoration of the DB.

I would like to request the upgrade documetnation be updated on the foreman 
site to reflect the version step-up needing to take place.  Happy to submit 
the changes to contribute to the document if instructions can be provided ;)

Thanks again!  I appreciate your hard work and prompt reply!!

On Tuesday, October 18, 2016 at 4:27:03 AM UTC-4, Dominic Cleal wrote:
>
> On 18/10/16 04:26, Austin Smith wrote: 
> > Updating to the latest and greatest foreman - following the outstanding 
> > online documentation and received the following error (please note paste 
> > is with --trace option): 
> > 
> > | 
> > [root@%FOREMANSERVER-EDITED%~]# foreman-rake db:migrate --trace 
> > **Invokedb:migrate (first_time) 
> > **Invokeenvironment (first_time) 
> > **Executeenvironment 
> > **Invokedb:load_config (first_time) 
> > **Executedb:load_config 
> > **Executedb:migrate 
> > ==20150508124600CopyUnmanagedHostsToInterfaces:migrating 
> === 
> > --MigratingUnmanagedHostinterfaces to standalone Interfaces 
> > --  ...migrating %DBSERVER-EDITED% 
> > rake aborted! 
> > StandardError:Anerror has occurred,all later migrations canceled: 
> > 
> > 
> > undefinedlocalvariable ormethod `ip6' for 
> # 
> > | 
>
> This is issue http://projects.theforeman.org/issues/15920. It might be 
> possible to run `foreman-rake db:migrate:up VERSION=20160415134454` 
> first before the main db:migrate run. (After restoring the DB from 
> backup.) 
>
> Note that our upgrades are not supported over multiple versions, it's 
> strongly recommended to upgrade each version in turn and to follow each 
> set of upgrade notes. 
>
> -- 
> Dominic Cleal 
> dom...@cleal.org  
>

-- 
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: Migrate from Foreman to Foreman+Katello

2016-10-17 Thread Austin Smith
Same boat here.  Seems to be a lack of docs on that for some reason... 
Pretty excited to get that integration going!  Both projects have come so 
far!!

On Friday, October 14, 2016 at 5:36:35 PM UTC-4, steved0ca wrote:
>
> Hello,
>
> It looks like it is not possible to add Katello to an existing Foreman 
> installation. http://projects.theforeman.org/issues/7605
>
> Are there any recommended methods of migrating from an existing Foreman 
> only install, to a fresh Foreman+Katello installation? The puppet modules 
> and existing puppet certificates should be easy enough to copy over, but 
> what about my templates/hosts/host groups etc? Any way I can dump this data 
> and import it into the new host?
>
> Thanks,
> Steve
>
>
>

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


[foreman-users] Upgrade Failure on db:migrate v1.7.5 to 1.13 - what now?

2016-10-17 Thread Austin Smith

Greetings!

Updating to the latest and greatest foreman - following the outstanding 
online documentation and received the following error (please note paste is 
with --trace option):

[root@%FOREMANSERVER-EDITED% ~]# foreman-rake db:migrate --trace
** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
** Invoke db:load_config (first_time)
** Execute db:load_config
** Execute db:migrate
== 20150508124600 CopyUnmanagedHostsToInterfaces: migrating 
===
-- Migrating Unmanaged Host interfaces to standalone Interfaces
--   ... migrating %DBSERVER-EDITED%
rake aborted!
StandardError: An error has occurred, all later migrations canceled:


undefined local variable or method `ip6' for 
#/opt/rh/sclo-ror42/root/usr/share/gems/gems/activemodel-4.2.5.1/lib/active_model/attribute_methods.rb:433:in
 
`method_missing'
/usr/share/foreman/app/models/nic/interface.rb:92:in `normalize_ip'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/
active_support/callbacks.rb:432:in `block in make_lambda'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:164:in
 
`call'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:164:in
 
`block in halting'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/
active_support/callbacks.rb:504:in `call'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:504:in
 
`block in call'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:504:in
 
`each'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/
active_support/callbacks.rb:504:in `call'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:92:in
 
`__run_callbacks__'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/callbacks.rb:778:in
 
`_run_validation_callbacks'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activemodel-4.2.5.1/lib/
active_model/validations/callbacks.rb:113:in `run_validations!'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activemodel-4.2.5.1/lib/active_model/validations.rb:338:in
 
`valid?'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/validations.rb:58:in
 
`valid?'
/usr/share/foreman/app/models/concerns/orchestration.rb:77:in `valid?'
/usr/share/foreman/db/migrate/20150508124600_copy_unmanaged_hosts_to_interfaces.rb:27:in
 
`block in up'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/relation/delegation.rb:46:in
 
`each'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/
active_record/relation/delegation.rb:46:in `each'
/usr/share/foreman/db/migrate/20150508124600_copy_unmanaged_hosts_to_interfaces.rb:21:in
 
`up'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:611:in
 
`exec_migration'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/
active_record/migration.rb:592:in `block (2 levels) in migrate'
/opt/rh/rh-ruby22/root/usr/share/ruby/benchmark.rb:288:in `measure'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:591:in
 
`block in migrate'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/
active_record/connection_adapters/abstract/connection_pool.rb:292:in 
`with_connection'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:590:in
 
`migrate'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:768:in
 
`migrate'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/
active_record/migration.rb:998:in `block in 
execute_migration_in_transaction'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:1046:in
 
`ddl_transaction'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:997:in
 
`execute_migration_in_transaction'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/
active_record/migration.rb:959:in `block in migrate'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:955:in
 
`each'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:955:in
 
`migrate'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/
active_record/migration.rb:823:in `up'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/migration.rb:801:in
 
`migrate'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/tasks/database_tasks.rb:137:in
 
`migrate'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/
active_record/railties/databases.rake:44:in `block (2 levels) in '