Failure to install Foreman 1.4

Support
#1

Background: I am in the process of automating theForeman installation. The
goal is to deploy the infrastructure for our product (which has no Internet
connectivity) to various locations. Each rack will be disconnected, and
fully stand-alone, so this automation will look just the same for each and
every location.
I was working so far with tehForeman 1.3.2 on RHEL 6.5 (after performing
the initial 'development' on Centos 6.5), and this procedure, except for a
little bug which annoys me greatly (the default template to an OS via CLI),
is working fine, automation and all.

In my development environment, which is running Centos 6.5, and is
connected to the Internet, I attempt to install theForeman 1.4 from RPMs,
based on the installation manual, and my predefined OS layout (which is not
supposed to matter), and fail. My installer command line is:
foreman-installer --foreman-db-type sqlite --foreman-proxy-bmc true
–foreman-proxy-dhcp true --foreman-proxy-dhcp-interface eth0
–foreman-proxy-dhcp-range "192.168.11.2 192.168.11.250"
The result is:
/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] at
/usr/share/foreman-installer/modules/foreman/manifests/rake.pp:9
/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] at
/usr/share/foreman-installer/modules/foreman/manifests/rake.pp:9
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[mdw.mgmt]: Could
not evaluate: 500 Internal Server Error
Installing Done
[100%] […]
Something went wrong! Check the log for ERROR-level output
The full log is at /var/log/foreman-installer/foreman-installer.log

I attached the log to this message.
Any assistance would be great. Thanks!
Etzion

foreman-installer.log (10.3 KB)

#2

Same setup succeeds with the default DB - postgresql, however, fails just
the same with sqlite. I will test with MySQL as well.

Etzion

··· On Saturday, 15 February 2014 01:44:58 UTC+2, Etzion Bar-Noy wrote: > > Background: I am in the process of automating theForeman installation. The > goal is to deploy the infrastructure for our product (which has no Internet > connectivity) to various locations. Each rack will be disconnected, and > fully stand-alone, so this automation will look just the same for each and > every location. > I was working so far with tehForeman 1.3.2 on RHEL 6.5 (after performing > the initial 'development' on Centos 6.5), and this procedure, except for a > little bug which annoys me greatly (the default template to an OS via CLI), > is working fine, automation and all. > > In my development environment, which is running Centos 6.5, and is > connected to the Internet, I attempt to install theForeman 1.4 from RPMs, > based on the installation manual, and my predefined OS layout (which is not > supposed to matter), and fail. My installer command line is: > foreman-installer --foreman-db-type sqlite --foreman-proxy-bmc true > --foreman-proxy-dhcp true --foreman-proxy-dhcp-interface eth0 > --foreman-proxy-dhcp-range "192.168.11.2 192.168.11.250" > The result is: > /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] at > /usr/share/foreman-installer/modules/foreman/manifests/rake.pp:9 > /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] at > /usr/share/foreman-installer/modules/foreman/manifests/rake.pp:9 > /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[mdw.mgmt]: Could > not evaluate: 500 Internal Server Error > Installing Done > [100%] [...................................................................] > Something went wrong! Check the log for ERROR-level output > The full log is at /var/log/foreman-installer/foreman-installer.log > > I attached the log to this message. > Any assistance would be great. Thanks! > Etzion >
#3

As mentioned in Bug #4353: relation "roles" does not exist during DB migration - Foreman, I suspect
this is because you have the discovery plugin loaded during installation.

I was trying to fix this a couple of days ago as part of some other
work, so may have a fix for 1.5. In the meantime, try temporarily
removing the discovery RPM.

··· -- Dominic Cleal Red Hat Engineering

On 15/02/14 14:01, Etzion Bar-Noy wrote:

Same setup succeeds with the default DB - postgresql, however, fails
just the same with sqlite. I will test with MySQL as well.

Etzion

On Saturday, 15 February 2014 01:44:58 UTC+2, Etzion Bar-Noy wrote:

Background: I am in the process of automating theForeman
installation. The goal is to deploy the infrastructure for our
product (which has no Internet connectivity) to various locations.
Each rack will be disconnected, and fully stand-alone, so this
automation will look just the same for each and every location.
I was working so far with tehForeman 1.3.2 on RHEL 6.5 (after
performing the initial 'development' on Centos 6.5), and this
procedure, except for a little bug which annoys me greatly (the
default template to an OS via CLI), is working fine, automation and all.

In my development environment, which is running Centos 6.5, and is
connected to the Internet, I attempt to install theForeman 1.4 from
RPMs, based on the installation manual, and my predefined OS layout
(which is not supposed to matter), and fail. My installer command
line is:
foreman-installer --foreman-db-type sqlite --foreman-proxy-bmc true
--foreman-proxy-dhcp true --foreman-proxy-dhcp-interface eth0
--foreman-proxy-dhcp-range "192.168.11.2 192.168.11.250"
The result is:
/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] at
/usr/share/foreman-installer/modules/foreman/manifests/rake.pp:9
 /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] at
/usr/share/foreman-installer/modules/foreman/manifests/rake.pp:9
 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[mdw.mgmt]:
Could not evaluate: 500 Internal Server Error
Installing            
Done                                               [100%]
[...................................................................]
  Something went wrong! Check the log for ERROR-level output
  The full log is at /var/log/foreman-installer/foreman-installer.log

I attached the log to this message.
Any assistance would be great. Thanks!
Etzion

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

#4

Hi Dominic.
Thank you for the answer and for directing me in the right path. It is the
discovery plugin. Removing it before the initial installation process
resulting in a successful installation.

Thanks!
Etzion

··· On Monday, 17 February 2014 10:51:37 UTC+2, Dominic Cleal wrote: > > > As mentioned in http://projects.theforeman.org/issues/4353, I suspect > this is because you have the discovery plugin loaded during installation. > > I was trying to fix this a couple of days ago as part of some other > work, so may have a fix for 1.5. In the meantime, try temporarily > removing the discovery RPM. > > -- > Dominic Cleal > Red Hat Engineering > > On 15/02/14 14:01, Etzion Bar-Noy wrote: > > Same setup succeeds with the default DB - postgresql, however, fails > > just the same with sqlite. I will test with MySQL as well. > > > > Etzion > > > > On Saturday, 15 February 2014 01:44:58 UTC+2, Etzion Bar-Noy wrote: > > > > Background: I am in the process of automating theForeman > > installation. The goal is to deploy the infrastructure for our > > product (which has no Internet connectivity) to various locations. > > Each rack will be disconnected, and fully stand-alone, so this > > automation will look just the same for each and every location. > > I was working so far with tehForeman 1.3.2 on RHEL 6.5 (after > > performing the initial 'development' on Centos 6.5), and this > > procedure, except for a little bug which annoys me greatly (the > > default template to an OS via CLI), is working fine, automation and > all. > > > > In my development environment, which is running Centos 6.5, and is > > connected to the Internet, I attempt to install theForeman 1.4 from > > RPMs, based on the installation manual, and my predefined OS layout > > (which is not supposed to matter), and fail. My installer command > > line is: > > foreman-installer --foreman-db-type sqlite --foreman-proxy-bmc true > > --foreman-proxy-dhcp true --foreman-proxy-dhcp-interface eth0 > > --foreman-proxy-dhcp-range "192.168.11.2 192.168.11.250" > > The result is: > > > /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] at > > /usr/share/foreman-installer/modules/foreman/manifests/rake.pp:9 > > > /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] at > > /usr/share/foreman-installer/modules/foreman/manifests/rake.pp:9 > > /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[mdw.mgmt]: > > Could not evaluate: 500 Internal Server Error > > Installing > > Done [100%] > > > [...................................................................] > > Something went wrong! Check the log for ERROR-level output > > The full log is at > /var/log/foreman-installer/foreman-installer.log > > > > I attached the log to this message. > > Any assistance would be great. Thanks! > > Etzion > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Foreman users" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to foreman-user...@googlegroups.com . > > To post to this group, send email to forema...@googlegroups.com. > > > Visit this group at http://groups.google.com/group/foreman-users. > > For more options, visit https://groups.google.com/groups/opt_out. > >