On 05/09/2017 01:02 PM, Gianluca Cecchi wrote:
> On Fri, May 5, 2017 at 4:47 PM, Juan Hernández <jhern...@redhat.com
> <mailto:jhern...@redhat.com>> wrote:
>     Yes, capablanca is too old.
>     The instructions that you mention should still work, but remember to
>     make a backup before doing that in your production environment.
>     Anyhow, I'd suggest that you install a fresh euwe, if that is an option
>     for you.
>     There is no support for YUM/RPM upgrades, as far as I know.
> OK, after some attempts to upgrade in place my capablanca VM (just for
> learning), I abandoned it.
> It seems the euwe stable qemu/kvm has some problems too in general... I
> get this during the initialization after VM start
> appliance_console_cli --region 0 --internal --password smartvm
> /opt/rubies/ruby-2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.14.6/lib/bundler/source/git/git_proxy.rb:225:in
> |allowed_in_path': The git source
> https://github.com/ManageIQ/manageiq-providers-amazon is not yet checked
> out. Please run|bundle install` before trying to start your application
> (Bundler::GitError)
> Then I have tried the just released Fine qemu/kvm rc1 image and it works
> ok, so I'm using it for my tests...
> I was able to add oVirt engine 4.1.2 pre.
> But now I see almost all (VMs, datastores, ecc.) but the hosts...
> Furthermore in Compute --> Infrastructure --> Hosts I do find the engine
> but not the host...
> Do I have to add in any way also the hypervisors to the ManageIQ
> configuration? Or should it be automatic?

The hosts should be added automatically. Moti, I remember that you
mentioned some issue with hosts. Was that resolved?

> Also, do you know when I choose to see console in ManageIQ, both the
> "web console"  and the "WM console" options in "Access" menu, from where
> the connection is originated: my client where browser is running or from
> manageiq server and then passed in any way to client?
> Which protocol does the web console use?

I am not sure about that. Martin, can you answer that question?

Users mailing list

Reply via email to