Capablanca RC1 - RHEV - Not starting on boot


#1

Hello,

I just downloaded Capablanca RC1 for RHEV (manageiq-ovirt-capablanca-1-rc1.ova)
imported the appliance and deployed a new VM.

But when i started the VM, the services doesn’t start.
On the Centos VM there is no service listen on the http or https port.

[root@manageiq manageiq-appliance]# ss -tunalp |grep LIST
tcp LISTEN 0 128 :22 : users:((“sshd”,5396,3))
tcp LISTEN 0 100 127.0.0.1:25 : users:((“master”,2441,13))
tcp LISTEN 0 128 :::22 :::
users:((“sshd”,5396,4))
tcp LISTEN 0 100 ::1:25 :::* users:((“master”,2441,14))
[root@manageiq manageiq-appliance]#

If i run appliance_console i get the following error:

[root@manageiq ~]# appliance_console
/opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/source/git/git_proxy.rb:155:in allowed_in_path': The git source git://github.com/rails/rails.git is not yet checked out. Please runbundle installbefore trying to start your application (Bundler::GitError) from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/source/git/git_proxy.rb:47:inrevision’
from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/source/git.rb:215:in revision' from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/source/git.rb:85:ininstall_path’
from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/source/path.rb:110:in expanded_path' from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/source/path.rb:132:inload_spec_files’
from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/source/git.rb:188:in load_spec_files' from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/source/path.rb:92:inlocal_specs’
from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/source/git.rb:159:in specs' from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/definition.rb:550:inblock in converge_locked_specs’
from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/definition.rb:539:in each' from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/definition.rb:539:inconverge_locked_specs’
from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/definition.rb:195:in resolve' from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/definition.rb:140:inspecs’
from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/definition.rb:185:in specs_for' from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/definition.rb:174:inrequested_specs’
from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/environment.rb:18:in requested_specs' from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:13:insetup’
from /opt/rubies/ruby-2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.10.6/lib/bundler.rb:127:in setup' from /var/www/miq/vmdb/gems/pending/appliance_console.rb:16:in'
[root@manageiq ~]#

I don’t want to run “bundle install” as root because it says that will break the application for non-root users.

What steps should i follow to start the appliance ?

Regards


#2

@jrafanie @simaishi @carbonin Can one of you help out here?


#3

Looks like the fog gem released a new revision between the two image builds. We were (unknowingly) relying on it to provide a gem that we depended on (net-scp) and that gem was removed in the new version. So VMware has the gem and RHEV doesn’t. @kbrock has an open PR to fix it here https://github.com/ManageIQ/manageiq/pull/5452


#4

Update:

Looks like my last comment was not quite the root of the problem.

At build time bundle install was not run properly (Gemfile.lock is missing from the appliance on first-boot).
Applying the change here ( https://github.com/ManageIQ/manageiq/pull/5452/files ) then running bundle install from /var/www/miq/vmdb/ then rebooting the appliance will cause the appliance-initialize service to run which should create the database successfully. And enable/start the evmserverd service.

I’m still investigating the root of the build issue.


#5

Hi,

@carbonin should i wait for a new build of the RC1for oVirt/RHEV or can i try some workaround in my lab?

If you think i could help you with some test, let me know and i will try my best.

Regards.


#6

:sweat: Do’H

i just find , there is a RC2 build.

I will try that one and post the feedback.


Capablanca not starting
#7

@pablohalamaj I was able to get the RC2 build up and running. Looks like the issue with the first one was just an intermittent build failure.


#8

Confirmed! RC2 starts OK in RHEV.

Thank you!