Re: [ovirt-users] Moving a Hosted Engine from Fedora 20 to CentOS 7

2015-11-14 Thread John Florian 
I'm getting better results now but still no success.  My attempts at
rebuilding my host "ophelia" had a number of issues related to
networking which was no surprise given that ovirtmgmt wasn't present.  I
believe this all stemmed from the initial conditions of the host and
especially the ifcfg files for the two NICs.  I had started with a clean
install and did minimal changes but it was seeing too many weird issues
to try and sort out at once.  Plus once vdsm starts doing its thing
managing these it's hard to say from where exactly I was starting. 
So. time for a fresh slate.  Here are those results:

First off, the mail Subject is wholly wrong anymore since I ran into
really difficult sounding problems on that path.  There's no CentOS
involved right now, just Fedora.  I don't know which is worse, changing
the subject or leaving it wrong or prolonging a mail thread.  Anyway, my
current situation is:

GOOD: oVirt 3.5.4 hosted engine on enceladus-f20 atop F20
GOOD: oVirt 3.5.4 host on oberon (also F20)
PROBLEMS: attempting oVirt 3.6 on ophelia atop F22

The battle plan for oVirt 3.6 on ophelia:

  * installed F22 using minimal install option
  * initial networking setup immediately after installing F22:

[root@ophelia ~]# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp6s0:  mtu 1500 qdisc fq_codel
state UP group default qlen 1000
link/ether 00:1f:d0:dc:27:af brd ff:ff:ff:ff:ff:ff
3: enp4s0:  mtu 1500 qdisc fq_codel
state UP group default qlen 1000
link/ether 68:05:ca:2f:f4:7c brd ff:ff:ff:ff:ff:ff
inet 172.16.7.7/24 brd 172.16.7.255 scope global enp4s0
   valid_lft forever preferred_lft forever
inet6 fe80::6a05:caff:fe2f:f47c/64 scope link
   valid_lft forever preferred_lft forever
4: bond0:  mtu 1500 qdisc noop state DOWN
group default
link/ether 3a:67:d6:86:11:71 brd ff:ff:ff:ff:ff:ff

[root@ophelia ~]# cat /etc/resolv.conf
# Generated by NetworkManager
search doubledog.org
nameserver 172.16.7.6
nameserver 172.16.7.154

  * dnf update
  * edited /etc/ssh/sshd_config to add necessary KexAlgorithms
  * systemctl restart sshd
  * setenforce permissive so that vdsm can start
  o The Release Notes mention this is necessary for gluster.  I'm
only doing ISCSI but I must use permissive otherwise vdsm will
not start later.  This lesson already learned so applied here to
keep the logs void of any confusion from this aspect.
  * dnf install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm
  * dnf install ovirt-hosted-engine-setup
  * hosted-engine --deploy

I'm still seeing the SQL error (in the engine log) that I mentioned in
prior mails, though none of the networking issues I had on earlier
attempts.  Thus I believe I've made some progress but need advice on
what to dig into next for y'all.

Rather than pasting parts of the logs here, I've just dropped them in
their entirety where they should be easily retrievable here:
http://www.doubledog.org/john/ovirt-3.6-install-logs/attempt-10/

If additional logs are needed, please let me know.

Thanks for all the help with this!!!

-- 
John Florian

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Moving a Hosted Engine from Fedora 20 to CentOS 7

2015-11-12 Thread Yedidyah Bar David 
On Thu, Nov 12, 2015 at 2:37 AM, John Florian  wrote:
[snip]
>>> 2015-11-09 19:12:40,335 WARN
>>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>>> (DefaultQuartzScheduler_Worker-12) [5569d8a6] Correlation ID: 5569d8a6,
>>> Job ID: 98718a7b-4f64-4a3d-bb72-e6d46100edc5, Call Stack: null, Custom
>>> Event ID: -1, Message: Host hosted_engine_2 does not comply with the
>>> cluster Default networks, the following networks are missing on host:
>>> 'ovirtmgmt'
>> Didn't you see this one anywhere? There was some problem creating the
>> bridge, or something else making the engine think so.
>>
>> If it seems ok to you, perhaps check also vdsm logs.
> I might have missed that; I don't recall for certain as there is a lot
> of logging going on in various places, it's hard to know where to look
> sometimes.  Then there's all the errors that seem to happen that aren't
> really problems AFAICT.
>
> Anyway, I just ran through an attempted deploy again and I don't see
> ovirtmgmt mentioned anywhere in /var/log/vdsm/vdsm.log, nor anything
> else in that file looking majorly bad WRT networking.

But you still have problems?

Do you have on the host an interface 'ovirtmgmt'?

What do you see in the web admin? mark the host -> Network Interfaces ->
Setup host networks.

>  I do see a bunch
> of errors related to storage though.

If the storage relies on the network (likely), perhaps first fix network
issues, then storage.

>  Any hints what I should be search
> for?

If you do not find there 'ovirtmgmt', not sure.

You can check also /var/log/ovirt-hosted-engine-setup on the host,
as well as normal system log (/var/log/syslog or messages or whatever).

>  Would it be best just to post the file somewhere -- it's a rather
> portly 12MB ATM.

Perhaps. Some file sharing site or something.

>
> And just because I'm feeling stupid right now I don't need  to do
> anything special WRT configuring networking prior to running
> hosted-engine --deploy do I?  I mean its got working IP, DNS, etc. but
> IIRC, the installation handles all the setup of ovirtmgmt, right?

If you start from a clean machine, it should do all.

If you start from a machine which already has an interface 'ovirtmgmt'
but has problems, iiuc the script will not fix them.

Best,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Moving a Hosted Engine from Fedora 20 to CentOS 7

2015-11-11 Thread John Florian 
On 11/10/2015 03:39 AM, Yedidyah Bar David wrote:
> On Tue, Nov 10, 2015 at 2:16 AM, John Florian  wrote:
>> On 11/09/2015 06:25 PM, John Florian wrote:
>>> I don't think it has anything to do with name resolution either. I
>>> believe the telltale clue is this bit... 2015-11-09 18:22:31,738 WARN
>>> [org.apache.sshd.client.session.ClientSessionImpl] (pool-20-thread-3)
>>> Exception caught: java.lang.IllegalStateException: Unable to negotiate
>>> key exchange for kex algorithms (client: diffie-hellman-group1-sha1 /
>>> server:
>>> curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1)
>>> As mentioned, I can ssh from my engine to the host just fine. It
>>> appears that the Java-based ssh client however cannot.
>> I got past the above problem by adding the following line to the
>> /etc/ssh/sshd_config of the new F22 host:
>>
>> KexAlgorithms
>> curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
>>
>> This represents the defaults for F22 -- at least according to
>> sshd_config(5) -- but with the addition of diffie-hellman-group1-sha1
>> that the Java-based ssh client seems insistent on using.
>>
> Adding Alon for this. Not sure if we can configure the java ssh client
> and how.
>
>> However, all is not rosy.  The deploy script ground to a halt with:
>> [ INFO  ] Waiting for the host to become operational in the engine. This
>> may take several minutes...
>>   The host hosted_engine_2 is in non-operational state.
>>   Please try to activate it via the engine webadmin UI.
>>   Retry checking host status or ignore this and continue (Retry,
>> Ignore)[Retry]?
>>
>> So I did as suggested and tried to activate the host from the webadmin
>> UI.  That didn't work either.  The status message at the bottom of the
>> browser page shows:
>>
>> Host hosted_engine_2 is installed with VDSM version () and
>> cannot join cluster Default which is compatible with VDSM versions
>> [4.13, 4.14, 4.9, 4.16, 4.11, 4.15, 4.12, 4.10].
>>
>> The attempt to activate the host via the web UI also caused the
>> following to be logged on the engine:
>>
>> 2015-11-09 19:12:39,828 INFO
>> [org.ovirt.engine.core.bll.ActivateVdsCommand] (ajp--127.0.0.1-8702-7)
>> [4bf460e8] Lock Acquired to object EngineLock [exclusiveLocks= key:
>> fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df value: VDS
>> , sharedLocks= ]
>> 2015-11-09 19:12:39,838 INFO
>> [org.ovirt.engine.core.bll.ActivateVdsCommand]
>> (org.ovirt.thread.pool-8-thread-49) [4bf460e8] Running command:
>> ActivateVdsCommand internal: false. Entities affected :  ID:
>> fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df Type: VDSAction group
>> MANIPULATE_HOST with role type ADMIN
>> 2015-11-09 19:12:39,851 INFO
>> [org.ovirt.engine.core.bll.ActivateVdsCommand]
>> (org.ovirt.thread.pool-8-thread-49) [4bf460e8] Before acquiring lock in
>> order to prevent monitoring for host hosted_engine_2 from data-center
>> Default
>> 2015-11-09 19:12:39,856 INFO
>> [org.ovirt.engine.core.bll.ActivateVdsCommand]
>> (org.ovirt.thread.pool-8-thread-49) [4bf460e8] Lock acquired, from now a
>> monitoring of host will be skipped for host hosted_engine_2 from
>> data-center Default
>> 2015-11-09 19:12:39,861 INFO
>> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
>> (org.ovirt.thread.pool-8-thread-49) [4bf460e8] START,
>> SetVdsStatusVDSCommand(HostName = hosted_engine_2, HostId =
>> fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df, status=Unassigned,
>> nonOperationalReason=NONE, stopSpmFailureLogged=false), log id: 1d206899
>> 2015-11-09 19:12:39,870 INFO
>> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
>> (org.ovirt.thread.pool-8-thread-49) [4bf460e8] FINISH,
>> SetVdsStatusVDSCommand, log id: 1d206899
>> 2015-11-09 19:12:39,888 INFO
>> [org.ovirt.engine.core.bll.ActivateVdsCommand]
>> (org.ovirt.thread.pool-8-thread-49) Activate finished. Lock released.
>> Monitoring can run now for host hosted_engine_2 from data-center Default
>> 2015-11-09 19:12:39,892 INFO
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (org.ovirt.thread.pool-8-thread-49) Correlation ID: 4bf460e8, Job ID:
>> 08a2b1ad-1c1c-425c-b657-7739df72b764, Call Stack: null, Custom Event ID:
>> -1, Message: Host hosted_engine_2 was activated by admin@internal.
>> 2015-11-09 19:12:39,895 INFO
>> [org.ovirt.engine.core.bll.ActivateVdsCommand]
>> (org.ovirt.thread.pool-8-thread-49) Lock freed to object EngineLock
>> [exclusiveLocks= key: fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df value: VDS
>> , sharedLocks= ]
>> 2015-11-09 19:12:40,263 INFO
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
>> (DefaultQuartzScheduler_Worker-12) [79b24fed] START,
>> GetHardwareInfoVDSCommand(HostName = hosted_engine_2, HostId =
>> fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df,
>> vds=Host[hosted_engine_2,fab

Re: [ovirt-users] Moving a Hosted Engine from Fedora 20 to CentOS 7

2015-11-11 Thread John Florian 
On 11/10/2015 03:45 AM, Alon Bar-Lev wrote:
>
> - Original Message -
>> From: "Yedidyah Bar David" 
>> To: "John Florian" , "Alon Bar-Lev" 
>> , "Roy Golan" ,
>> "Eli Mesika" 
>> Cc: "users" 
>> Sent: Tuesday, November 10, 2015 10:39:27 AM
>> Subject: Re: [ovirt-users] Moving a Hosted Engine from Fedora 20 to CentOS 7
>>
>> On Tue, Nov 10, 2015 at 2:16 AM, John Florian  wrote:
>>> On 11/09/2015 06:25 PM, John Florian wrote:
>>>> I don't think it has anything to do with name resolution either. I
>>>> believe the telltale clue is this bit... 2015-11-09 18:22:31,738 WARN
>>>> [org.apache.sshd.client.session.ClientSessionImpl] (pool-20-thread-3)
>>>> Exception caught: java.lang.IllegalStateException: Unable to negotiate
>>>> key exchange for kex algorithms (client: diffie-hellman-group1-sha1 /
>>>> server:
>>>> curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1)
>>>> As mentioned, I can ssh from my engine to the host just fine. It
>>>> appears that the Java-based ssh client however cannot.
>>> I got past the above problem by adding the following line to the
>>> /etc/ssh/sshd_config of the new F22 host:
>>>
>>> KexAlgorithms
>>> curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
>>>
>>> This represents the defaults for F22 -- at least according to
>>> sshd_config(5) -- but with the addition of diffie-hellman-group1-sha1
>>> that the Java-based ssh client seems insistent on using.
>>>
>> Adding Alon for this. Not sure if we can configure the java ssh client
>> and how.
>>
> I think that newer than apache-sshd-0.14 altered its behavior, can you please 
> try to downgrade to apache-sshd-0.13 and see if it helps, if it does we will 
> enforce it. Only in apache-sshd-1.1.0 (unreleased) we will be able to migrate 
> properly (I hope).

This is my fault.  I see now that this was mentioned in the 3.6.0
release notes as a Fedora 22 specific issue (see also
https://bugzilla.redhat.com/show_bug.cgi?id=1225531).  The work around
is just exactly as I mentioned above, though I figured it out, then read
the release notes; doh!

I don't even see an apache-sshd package installed on my engine (or hosts).
>>> However, all is not rosy.  The deploy script ground to a halt with:
>>> [ INFO  ] Waiting for the host to become operational in the engine. This
>>> may take several minutes...
>>>   The host hosted_engine_2 is in non-operational state.
>>>   Please try to activate it via the engine webadmin UI.
>>>   Retry checking host status or ignore this and continue (Retry,
>>> Ignore)[Retry]?
>>>
>>> So I did as suggested and tried to activate the host from the webadmin
>>> UI.  That didn't work either.  The status message at the bottom of the
>>> browser page shows:
>>>
>>> Host hosted_engine_2 is installed with VDSM version () and
>>> cannot join cluster Default which is compatible with VDSM versions
>>> [4.13, 4.14, 4.9, 4.16, 4.11, 4.15, 4.12, 4.10].
>>>
>>> The attempt to activate the host via the web UI also caused the
>>> following to be logged on the engine:
>>>
>>> 2015-11-09 19:12:39,828 INFO
>>> [org.ovirt.engine.core.bll.ActivateVdsCommand] (ajp--127.0.0.1-8702-7)
>>> [4bf460e8] Lock Acquired to object EngineLock [exclusiveLocks= key:
>>> fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df value: VDS
>>> , sharedLocks= ]
>>> 2015-11-09 19:12:39,838 INFO
>>> [org.ovirt.engine.core.bll.ActivateVdsCommand]
>>> (org.ovirt.thread.pool-8-thread-49) [4bf460e8] Running command:
>>> ActivateVdsCommand internal: false. Entities affected :  ID:
>>> fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df Type: VDSAction group
>>> MANIPULATE_HOST with role type ADMIN
>>> 2015-11-09 19:12:39,851 INFO
>>> [org.ovirt.engine.core.bll.ActivateVdsCommand]
>>> (org.ovirt.thread.pool-8-thread-49) [4bf460e8] Before acquiring lock in
>>> order to prevent monitoring for host hosted_engine_2 from data-center
>>> Default
>>> 2015-11-09 19:12:39,856 INFO
>>> [org.ovirt.engine.core.bll.ActivateVdsCommand]
>>> (org.ovirt.thread.pool-8-thread-49) [4bf460e8] Lock acquired, from now a
>>> monitoring of host will be ski

Re: [ovirt-users] Moving a Hosted Engine from Fedora 20 to CentOS 7

2015-11-10 Thread Alon Bar-Lev 


- Original Message -
> From: "Yedidyah Bar David" 
> To: "John Florian" , "Alon Bar-Lev" 
> , "Roy Golan" ,
> "Eli Mesika" 
> Cc: "users" 
> Sent: Tuesday, November 10, 2015 10:39:27 AM
> Subject: Re: [ovirt-users] Moving a Hosted Engine from Fedora 20 to CentOS 7
> 
> On Tue, Nov 10, 2015 at 2:16 AM, John Florian  wrote:
> > On 11/09/2015 06:25 PM, John Florian wrote:
> >> I don't think it has anything to do with name resolution either. I
> >> believe the telltale clue is this bit... 2015-11-09 18:22:31,738 WARN
> >> [org.apache.sshd.client.session.ClientSessionImpl] (pool-20-thread-3)
> >> Exception caught: java.lang.IllegalStateException: Unable to negotiate
> >> key exchange for kex algorithms (client: diffie-hellman-group1-sha1 /
> >> server:
> >> curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1)
> >> As mentioned, I can ssh from my engine to the host just fine. It
> >> appears that the Java-based ssh client however cannot.
> >
> > I got past the above problem by adding the following line to the
> > /etc/ssh/sshd_config of the new F22 host:
> >
> > KexAlgorithms
> > curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
> >
> > This represents the defaults for F22 -- at least according to
> > sshd_config(5) -- but with the addition of diffie-hellman-group1-sha1
> > that the Java-based ssh client seems insistent on using.
> >
> 
> Adding Alon for this. Not sure if we can configure the java ssh client
> and how.
> 

I think that newer than apache-sshd-0.14 altered its behavior, can you please 
try to downgrade to apache-sshd-0.13 and see if it helps, if it does we will 
enforce it. Only in apache-sshd-1.1.0 (unreleased) we will be able to migrate 
properly (I hope).

> > However, all is not rosy.  The deploy script ground to a halt with:
> > [ INFO  ] Waiting for the host to become operational in the engine. This
> > may take several minutes...
> >   The host hosted_engine_2 is in non-operational state.
> >   Please try to activate it via the engine webadmin UI.
> >   Retry checking host status or ignore this and continue (Retry,
> > Ignore)[Retry]?
> >
> > So I did as suggested and tried to activate the host from the webadmin
> > UI.  That didn't work either.  The status message at the bottom of the
> > browser page shows:
> >
> > Host hosted_engine_2 is installed with VDSM version () and
> > cannot join cluster Default which is compatible with VDSM versions
> > [4.13, 4.14, 4.9, 4.16, 4.11, 4.15, 4.12, 4.10].
> >
> > The attempt to activate the host via the web UI also caused the
> > following to be logged on the engine:
> >
> > 2015-11-09 19:12:39,828 INFO
> > [org.ovirt.engine.core.bll.ActivateVdsCommand] (ajp--127.0.0.1-8702-7)
> > [4bf460e8] Lock Acquired to object EngineLock [exclusiveLocks= key:
> > fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df value: VDS
> > , sharedLocks= ]
> > 2015-11-09 19:12:39,838 INFO
> > [org.ovirt.engine.core.bll.ActivateVdsCommand]
> > (org.ovirt.thread.pool-8-thread-49) [4bf460e8] Running command:
> > ActivateVdsCommand internal: false. Entities affected :  ID:
> > fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df Type: VDSAction group
> > MANIPULATE_HOST with role type ADMIN
> > 2015-11-09 19:12:39,851 INFO
> > [org.ovirt.engine.core.bll.ActivateVdsCommand]
> > (org.ovirt.thread.pool-8-thread-49) [4bf460e8] Before acquiring lock in
> > order to prevent monitoring for host hosted_engine_2 from data-center
> > Default
> > 2015-11-09 19:12:39,856 INFO
> > [org.ovirt.engine.core.bll.ActivateVdsCommand]
> > (org.ovirt.thread.pool-8-thread-49) [4bf460e8] Lock acquired, from now a
> > monitoring of host will be skipped for host hosted_engine_2 from
> > data-center Default
> > 2015-11-09 19:12:39,861 INFO
> > [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> > (org.ovirt.thread.pool-8-thread-49) [4bf460e8] START,
> > SetVdsStatusVDSCommand(HostName = hosted_engine_2, HostId =
> > fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df, status=Unassigned,
> > nonOperationalReason=NONE, stopSpmFailureLogged=false), log id: 1d206899
> > 2015-11-09 19:12:39,870 INFO
> > [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> > (org.ovirt.thread.pool-8-thread-49) [4bf460e8] FINISH,
> > SetVdsStatusVD

Re: [ovirt-users] Moving a Hosted Engine from Fedora 20 to CentOS 7

2015-11-10 Thread Yedidyah Bar David 
On Tue, Nov 10, 2015 at 2:16 AM, John Florian  wrote:
> On 11/09/2015 06:25 PM, John Florian wrote:
>> I don't think it has anything to do with name resolution either. I
>> believe the telltale clue is this bit... 2015-11-09 18:22:31,738 WARN
>> [org.apache.sshd.client.session.ClientSessionImpl] (pool-20-thread-3)
>> Exception caught: java.lang.IllegalStateException: Unable to negotiate
>> key exchange for kex algorithms (client: diffie-hellman-group1-sha1 /
>> server:
>> curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1)
>> As mentioned, I can ssh from my engine to the host just fine. It
>> appears that the Java-based ssh client however cannot.
>
> I got past the above problem by adding the following line to the
> /etc/ssh/sshd_config of the new F22 host:
>
> KexAlgorithms
> curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
>
> This represents the defaults for F22 -- at least according to
> sshd_config(5) -- but with the addition of diffie-hellman-group1-sha1
> that the Java-based ssh client seems insistent on using.
>

Adding Alon for this. Not sure if we can configure the java ssh client
and how.

> However, all is not rosy.  The deploy script ground to a halt with:
> [ INFO  ] Waiting for the host to become operational in the engine. This
> may take several minutes...
>   The host hosted_engine_2 is in non-operational state.
>   Please try to activate it via the engine webadmin UI.
>   Retry checking host status or ignore this and continue (Retry,
> Ignore)[Retry]?
>
> So I did as suggested and tried to activate the host from the webadmin
> UI.  That didn't work either.  The status message at the bottom of the
> browser page shows:
>
> Host hosted_engine_2 is installed with VDSM version () and
> cannot join cluster Default which is compatible with VDSM versions
> [4.13, 4.14, 4.9, 4.16, 4.11, 4.15, 4.12, 4.10].
>
> The attempt to activate the host via the web UI also caused the
> following to be logged on the engine:
>
> 2015-11-09 19:12:39,828 INFO
> [org.ovirt.engine.core.bll.ActivateVdsCommand] (ajp--127.0.0.1-8702-7)
> [4bf460e8] Lock Acquired to object EngineLock [exclusiveLocks= key:
> fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df value: VDS
> , sharedLocks= ]
> 2015-11-09 19:12:39,838 INFO
> [org.ovirt.engine.core.bll.ActivateVdsCommand]
> (org.ovirt.thread.pool-8-thread-49) [4bf460e8] Running command:
> ActivateVdsCommand internal: false. Entities affected :  ID:
> fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df Type: VDSAction group
> MANIPULATE_HOST with role type ADMIN
> 2015-11-09 19:12:39,851 INFO
> [org.ovirt.engine.core.bll.ActivateVdsCommand]
> (org.ovirt.thread.pool-8-thread-49) [4bf460e8] Before acquiring lock in
> order to prevent monitoring for host hosted_engine_2 from data-center
> Default
> 2015-11-09 19:12:39,856 INFO
> [org.ovirt.engine.core.bll.ActivateVdsCommand]
> (org.ovirt.thread.pool-8-thread-49) [4bf460e8] Lock acquired, from now a
> monitoring of host will be skipped for host hosted_engine_2 from
> data-center Default
> 2015-11-09 19:12:39,861 INFO
> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> (org.ovirt.thread.pool-8-thread-49) [4bf460e8] START,
> SetVdsStatusVDSCommand(HostName = hosted_engine_2, HostId =
> fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df, status=Unassigned,
> nonOperationalReason=NONE, stopSpmFailureLogged=false), log id: 1d206899
> 2015-11-09 19:12:39,870 INFO
> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> (org.ovirt.thread.pool-8-thread-49) [4bf460e8] FINISH,
> SetVdsStatusVDSCommand, log id: 1d206899
> 2015-11-09 19:12:39,888 INFO
> [org.ovirt.engine.core.bll.ActivateVdsCommand]
> (org.ovirt.thread.pool-8-thread-49) Activate finished. Lock released.
> Monitoring can run now for host hosted_engine_2 from data-center Default
> 2015-11-09 19:12:39,892 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (org.ovirt.thread.pool-8-thread-49) Correlation ID: 4bf460e8, Job ID:
> 08a2b1ad-1c1c-425c-b657-7739df72b764, Call Stack: null, Custom Event ID:
> -1, Message: Host hosted_engine_2 was activated by admin@internal.
> 2015-11-09 19:12:39,895 INFO
> [org.ovirt.engine.core.bll.ActivateVdsCommand]
> (org.ovirt.thread.pool-8-thread-49) Lock freed to object EngineLock
> [exclusiveLocks= key: fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df value: VDS
> , sharedLocks= ]
> 2015-11-09 19:12:40,263 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
> (DefaultQuartzScheduler_Worker-12) [79b24fed] START,
> GetHardwareInfoVDSCommand(HostName = hosted_engine_2, HostId =
> fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df,
> vds=Host[hosted_engine_2,fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df]), log id:
> 7be846bb
> 2015-11-09 19:12:40,298 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareI

Re: [ovirt-users] Moving a Hosted Engine from Fedora 20 to CentOS 7

2015-11-09 Thread John Florian 
On 11/09/2015 06:25 PM, John Florian wrote:
> I don't think it has anything to do with name resolution either. I
> believe the telltale clue is this bit... 2015-11-09 18:22:31,738 WARN
> [org.apache.sshd.client.session.ClientSessionImpl] (pool-20-thread-3)
> Exception caught: java.lang.IllegalStateException: Unable to negotiate
> key exchange for kex algorithms (client: diffie-hellman-group1-sha1 /
> server:
> curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1)
> As mentioned, I can ssh from my engine to the host just fine. It
> appears that the Java-based ssh client however cannot. 

I got past the above problem by adding the following line to the
/etc/ssh/sshd_config of the new F22 host:

KexAlgorithms
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1

This represents the defaults for F22 -- at least according to
sshd_config(5) -- but with the addition of diffie-hellman-group1-sha1
that the Java-based ssh client seems insistent on using.

However, all is not rosy.  The deploy script ground to a halt with:
[ INFO  ] Waiting for the host to become operational in the engine. This
may take several minutes...
  The host hosted_engine_2 is in non-operational state.
  Please try to activate it via the engine webadmin UI.
  Retry checking host status or ignore this and continue (Retry,
Ignore)[Retry]?

So I did as suggested and tried to activate the host from the webadmin
UI.  That didn't work either.  The status message at the bottom of the
browser page shows:

Host hosted_engine_2 is installed with VDSM version () and
cannot join cluster Default which is compatible with VDSM versions
[4.13, 4.14, 4.9, 4.16, 4.11, 4.15, 4.12, 4.10].

The attempt to activate the host via the web UI also caused the
following to be logged on the engine:

2015-11-09 19:12:39,828 INFO 
[org.ovirt.engine.core.bll.ActivateVdsCommand] (ajp--127.0.0.1-8702-7)
[4bf460e8] Lock Acquired to object EngineLock [exclusiveLocks= key:
fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df value: VDS
, sharedLocks= ]
2015-11-09 19:12:39,838 INFO 
[org.ovirt.engine.core.bll.ActivateVdsCommand]
(org.ovirt.thread.pool-8-thread-49) [4bf460e8] Running command:
ActivateVdsCommand internal: false. Entities affected :  ID:
fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df Type: VDSAction group
MANIPULATE_HOST with role type ADMIN
2015-11-09 19:12:39,851 INFO 
[org.ovirt.engine.core.bll.ActivateVdsCommand]
(org.ovirt.thread.pool-8-thread-49) [4bf460e8] Before acquiring lock in
order to prevent monitoring for host hosted_engine_2 from data-center
Default
2015-11-09 19:12:39,856 INFO 
[org.ovirt.engine.core.bll.ActivateVdsCommand]
(org.ovirt.thread.pool-8-thread-49) [4bf460e8] Lock acquired, from now a
monitoring of host will be skipped for host hosted_engine_2 from
data-center Default
2015-11-09 19:12:39,861 INFO 
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(org.ovirt.thread.pool-8-thread-49) [4bf460e8] START,
SetVdsStatusVDSCommand(HostName = hosted_engine_2, HostId =
fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df, status=Unassigned,
nonOperationalReason=NONE, stopSpmFailureLogged=false), log id: 1d206899
2015-11-09 19:12:39,870 INFO 
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(org.ovirt.thread.pool-8-thread-49) [4bf460e8] FINISH,
SetVdsStatusVDSCommand, log id: 1d206899
2015-11-09 19:12:39,888 INFO 
[org.ovirt.engine.core.bll.ActivateVdsCommand]
(org.ovirt.thread.pool-8-thread-49) Activate finished. Lock released.
Monitoring can run now for host hosted_engine_2 from data-center Default
2015-11-09 19:12:39,892 INFO 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(org.ovirt.thread.pool-8-thread-49) Correlation ID: 4bf460e8, Job ID:
08a2b1ad-1c1c-425c-b657-7739df72b764, Call Stack: null, Custom Event ID:
-1, Message: Host hosted_engine_2 was activated by admin@internal.
2015-11-09 19:12:39,895 INFO 
[org.ovirt.engine.core.bll.ActivateVdsCommand]
(org.ovirt.thread.pool-8-thread-49) Lock freed to object EngineLock
[exclusiveLocks= key: fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df value: VDS
, sharedLocks= ]
2015-11-09 19:12:40,263 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
(DefaultQuartzScheduler_Worker-12) [79b24fed] START,
GetHardwareInfoVDSCommand(HostName = hosted_engine_2, HostId =
fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df,
vds=Host[hosted_engine_2,fab55ebe-cc0f-4f95-87aa-fc3a5e08a5df]), log id:
7be846bb
2015-11-09 19:12:40,298 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
(DefaultQuartzScheduler_Worker-12) [79b24fed] FINISH,
GetHardwareInfoVDSCommand, log id: 7be846bb
2015-11-09 19:12:40,326 INFO 
[org.ovirt.engine.core.bll.SetNonOperationalVdsCommand]
(DefaultQuartzScheduler_Worker-12) [5569d8a6] Running command:
SetNonOperationalVdsCommand inter

Re: [ovirt-users] Moving a Hosted Engine from Fedora 20 to CentOS 7

2015-11-09 Thread John Florian 
On 11/08/2015 04:16 AM, Yedidyah Bar David wrote:
> On Sat, Nov 7, 2015 at 2:38 AM, John Florian  wrote:
>> On 10/29/2015 05:49 AM, Roy Golan wrote:
>>
>>
>>
>> On Thu, Oct 29, 2015 at 11:39 AM, Roy Golan  wrote:
>>>
>>>
>>> On Wed, Oct 28, 2015 at 10:23 PM, John Florian 
>>> wrote:
 Can somebody please point me to documentation or describe how I should
 proceed with this task?  I see lots of pages for moving from a physical
 engine to a VM and vice-versa but am having no luck finding how to go
 about building a new HE to obsolete my original.

>>> using ovirt-hosted-engine-setup you can choose a setup without using the
>>> appliance. So you can scratch install your VM
>>
>>
>> BTW the ovirt-engine-appliacnce we build [1] is Centos based. Seems like
>> perfect candidate.
>>
>> #install the appliance
>> yum install ovirt-engine-appliance
>>
>> #and then run the setup
>> ovirt-hosted-engine-setup
>>
>> choose "disk" in this stage
>>
>> Please specify the device to boot the VM from (cdrom, disk, pxe) [cdrom]:
>> disk
>>
>> it will suggest the downloaded appliance automatically
>>
>> See this wiki for reference
>> http://www.ovirt.org/Features/HEApplianceFlow#Testing
>>
>>
>>
>> I'm afraid I'm lost here.  Here's a map of my setup:
>>
>> oVirt 3.5.5 hosted engine is named enceladus-f20 (on Fedora 20)
>> I have one oVirt 3.5.5 Host named oberon-f20 (also on Fedora 20)
>> I previously had one other oVirt 3.5.5 Host named ophelia-f20
>>
>> I took opehlia down, installed CentOS 7 on it and attempted a "hosted-engine
>> --deploy".  I can't remember if that was 3.5.5 or 3.6, but I could not add
>> it to my cluster.  From what I could gather enceladus-f20 provided an
>> emulation type of pc1.0 while ophelia-c7 didn't seem to have anything that
>> matched, the closest being just "pc".  That looked hopelessly complicated to
>> resolve so I thought I'd try again, but this time putting F22 on the ophelia
>> and doing a 3.6 HE deploy saying yes to the redeploy prompt.  This time I
>> was met with:
>>
>>   Checking for oVirt-Engine status at enceladus-f20.doubledog.org...
>>
>> [ INFO  ] Engine replied: DB Up!Welcome to Health Status!
>>
>> [ ERROR ] Cannot automatically add the host to cluster Default: Cannot add
>> Host. Connecting to host via SSH has failed, verify that the host is
>> reachable (IP address, routable address etc.) You may refer to the
>> engine.log file for further details.
>>
>>
>>
>>   Please check Engine VM configuration.
>>
>> On enceladus-f20, I see:
>>
>> ==> /var/log/ovirt-engine/engine.log <==
>>
>> 2015-11-06 19:17:12,085 INFO
>> [org.ovirt.engine.core.bll.aaa.LoginUserCommand] (ajp--127.0.0.1-8702-9)
>> Running command: LoginUserCommand internal: false.
>>
>> 2015-11-06 19:17:12,128 INFO
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (ajp--127.0.0.1-8702-9) Correlation ID: null, Call Stack: null, Custom Event
>> ID: -1, Message: User admin@internal logged in.
>>
>> ==> /var/log/ovirt-engine/server.log <==
>>
>> 2015-11-06 19:17:13,654 INFO
>> [org.apache.sshd.client.session.ClientSessionImpl] (pool-18-thread-1) Client
>> session created
>>
>> 2015-11-06 19:17:13,663 INFO
>> [org.apache.sshd.client.session.ClientSessionImpl] (pool-18-thread-2) Server
>> version string: SSH-2.0-OpenSSH_6.9
>>
>> 2015-11-06 19:17:13,667 WARN
>> [org.apache.sshd.client.session.ClientSessionImpl] (pool-18-thread-3)
>> Exception caught: java.lang.IllegalStateException: Unable to negotiate key
>> exchange for kex algorithms (client: diffie-hellman-group1-sha1 / server:
>> curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1)
>>
>> at
>> org.apache.sshd.common.session.AbstractSession.negotiate(AbstractSession.java:1098)
>>
>> at
>> org.apache.sshd.common.session.AbstractSession.doHandleMessage(AbstractSession.java:357)
>>
>> at
>> org.apache.sshd.common.session.AbstractSession.handleMessage(AbstractSession.java:295)
>>
>> at
>> org.apache.sshd.client.session.ClientSessionImpl.handleMessage(ClientSessionImpl.java:266)
>>
>> at
>> org.apache.sshd.common.session.AbstractSession.decode(AbstractSession.java:720)
>>
>> at
>> org.apache.sshd.common.session.AbstractSession.messageReceived(AbstractSession.java:277)
>>
>> at
>> org.apache.sshd.common.AbstractSessionIoHandler.messageReceived(AbstractSessionIoHandler.java:54)
>>
>> at
>> org.apache.sshd.common.io.nio2.Nio2Session$1.completed(Nio2Session.java:188)
>>
>> at
>> org.apache.sshd.common.io.nio2.Nio2Session$1.completed(Nio2Session.java:174)
>>
>> at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
>> [rt.jar:1.7.0_79]
>>
>> at sun.nio.ch.Invoker$2.run(Invoker.java:218) [rt.jar:1.7.0_79]
>>
>> at
>> sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
>> [rt.jar:1.7.0_79]
>>
>>

Re: [ovirt-users] Moving a Hosted Engine from Fedora 20 to CentOS 7

2015-11-08 Thread Yedidyah Bar David 
On Sat, Nov 7, 2015 at 2:38 AM, John Florian  wrote:
> On 10/29/2015 05:49 AM, Roy Golan wrote:
>
>
>
> On Thu, Oct 29, 2015 at 11:39 AM, Roy Golan  wrote:
>>
>>
>>
>> On Wed, Oct 28, 2015 at 10:23 PM, John Florian 
>> wrote:
>>>
>>> Can somebody please point me to documentation or describe how I should
>>> proceed with this task?  I see lots of pages for moving from a physical
>>> engine to a VM and vice-versa but am having no luck finding how to go
>>> about building a new HE to obsolete my original.
>>>
>>
>> using ovirt-hosted-engine-setup you can choose a setup without using the
>> appliance. So you can scratch install your VM
>
>
>
> BTW the ovirt-engine-appliacnce we build [1] is Centos based. Seems like
> perfect candidate.
>
> #install the appliance
> yum install ovirt-engine-appliance
>
> #and then run the setup
> ovirt-hosted-engine-setup
>
> choose "disk" in this stage
>
> Please specify the device to boot the VM from (cdrom, disk, pxe) [cdrom]:
> disk
>
> it will suggest the downloaded appliance automatically
>
> See this wiki for reference
> http://www.ovirt.org/Features/HEApplianceFlow#Testing
>
>
>
> I'm afraid I'm lost here.  Here's a map of my setup:
>
> oVirt 3.5.5 hosted engine is named enceladus-f20 (on Fedora 20)
> I have one oVirt 3.5.5 Host named oberon-f20 (also on Fedora 20)
> I previously had one other oVirt 3.5.5 Host named ophelia-f20
>
> I took opehlia down, installed CentOS 7 on it and attempted a "hosted-engine
> --deploy".  I can't remember if that was 3.5.5 or 3.6, but I could not add
> it to my cluster.  From what I could gather enceladus-f20 provided an
> emulation type of pc1.0 while ophelia-c7 didn't seem to have anything that
> matched, the closest being just "pc".  That looked hopelessly complicated to
> resolve so I thought I'd try again, but this time putting F22 on the ophelia
> and doing a 3.6 HE deploy saying yes to the redeploy prompt.  This time I
> was met with:
>
>   Checking for oVirt-Engine status at enceladus-f20.doubledog.org...
>
> [ INFO  ] Engine replied: DB Up!Welcome to Health Status!
>
> [ ERROR ] Cannot automatically add the host to cluster Default: Cannot add
> Host. Connecting to host via SSH has failed, verify that the host is
> reachable (IP address, routable address etc.) You may refer to the
> engine.log file for further details.
>
>
>
>   Please check Engine VM configuration.
>
> On enceladus-f20, I see:
>
> ==> /var/log/ovirt-engine/engine.log <==
>
> 2015-11-06 19:17:12,085 INFO
> [org.ovirt.engine.core.bll.aaa.LoginUserCommand] (ajp--127.0.0.1-8702-9)
> Running command: LoginUserCommand internal: false.
>
> 2015-11-06 19:17:12,128 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (ajp--127.0.0.1-8702-9) Correlation ID: null, Call Stack: null, Custom Event
> ID: -1, Message: User admin@internal logged in.
>
> ==> /var/log/ovirt-engine/server.log <==
>
> 2015-11-06 19:17:13,654 INFO
> [org.apache.sshd.client.session.ClientSessionImpl] (pool-18-thread-1) Client
> session created
>
> 2015-11-06 19:17:13,663 INFO
> [org.apache.sshd.client.session.ClientSessionImpl] (pool-18-thread-2) Server
> version string: SSH-2.0-OpenSSH_6.9
>
> 2015-11-06 19:17:13,667 WARN
> [org.apache.sshd.client.session.ClientSessionImpl] (pool-18-thread-3)
> Exception caught: java.lang.IllegalStateException: Unable to negotiate key
> exchange for kex algorithms (client: diffie-hellman-group1-sha1 / server:
> curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1)
>
> at
> org.apache.sshd.common.session.AbstractSession.negotiate(AbstractSession.java:1098)
>
> at
> org.apache.sshd.common.session.AbstractSession.doHandleMessage(AbstractSession.java:357)
>
> at
> org.apache.sshd.common.session.AbstractSession.handleMessage(AbstractSession.java:295)
>
> at
> org.apache.sshd.client.session.ClientSessionImpl.handleMessage(ClientSessionImpl.java:266)
>
> at
> org.apache.sshd.common.session.AbstractSession.decode(AbstractSession.java:720)
>
> at
> org.apache.sshd.common.session.AbstractSession.messageReceived(AbstractSession.java:277)
>
> at
> org.apache.sshd.common.AbstractSessionIoHandler.messageReceived(AbstractSessionIoHandler.java:54)
>
> at
> org.apache.sshd.common.io.nio2.Nio2Session$1.completed(Nio2Session.java:188)
>
> at
> org.apache.sshd.common.io.nio2.Nio2Session$1.completed(Nio2Session.java:174)
>
> at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
> [rt.jar:1.7.0_79]
>
> at sun.nio.ch.Invoker$2.run(Invoker.java:218) [rt.jar:1.7.0_79]
>
> at
> sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
> [rt.jar:1.7.0_79]
>
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [rt.jar:1.7.0_79]
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.

Re: [ovirt-users] Moving a Hosted Engine from Fedora 20 to CentOS 7

2015-11-06 Thread John Florian 
On 10/29/2015 05:49 AM, Roy Golan wrote:
>
>
> On Thu, Oct 29, 2015 at 11:39 AM, Roy Golan  > wrote:
>
>
>
> On Wed, Oct 28, 2015 at 10:23 PM, John Florian
> mailto:jflor...@doubledog.org>> wrote:
>
> Can somebody please point me to documentation or describe how
> I should
> proceed with this task?  I see lots of pages for moving from a
> physical
> engine to a VM and vice-versa but am having no luck finding
> how to go
> about building a new HE to obsolete my original.
>
>
> using ovirt-hosted-engine-setup you can choose a setup without
> using the appliance. So you can scratch install your VM
>
>
>
> BTW the ovirt-engine-appliacnce we build [1] is Centos based. Seems
> like perfect candidate.
>
> #install the appliance
> yum install ovirt-engine-appliance
>
> #and then run the setup
> ovirt-hosted-engine-setup
>
> choose "disk" in this stage
> Please specify the device to boot the VM from (cdrom, disk, pxe) [cdrom]: disk
>
> it will suggest the downloaded appliance automatically
> See this wiki for reference
> http://www.ovirt.org/Features/HEApplianceFlow#Testing
>

I'm afraid I'm lost here.  Here's a map of my setup:

oVirt 3.5.5 hosted engine is named enceladus-f20 (on Fedora 20)
I have one oVirt 3.5.5 Host named oberon-f20 (also on Fedora 20)
I previously had one other oVirt 3.5.5 Host named ophelia-f20

I took opehlia down, installed CentOS 7 on it and attempted a
"hosted-engine --deploy".  I can't remember if that was 3.5.5 or 3.6,
but I could not add it to my cluster.  From what I could gather
enceladus-f20 provided an emulation type of pc1.0 while ophelia-c7
didn't seem to have anything that matched, the closest being just "pc". 
That looked hopelessly complicated to resolve so I thought I'd try
again, but this time putting F22 on the ophelia and doing a 3.6 HE
deploy saying yes to the redeploy prompt.  This time I was met with:

  Checking for oVirt-Engine status at enceladus-f20.doubledog.org...

[ INFO  ] Engine replied: DB Up!Welcome to Health Status!

[ ERROR ] Cannot automatically add the host to cluster Default: Cannot add 
Host. Connecting to host via SSH has failed, verify that the host is reachable 
(IP address, routable address etc.) You may refer to the engine.log file for 
further details. 

  

  Please check Engine VM configuration.

On enceladus-f20, I see:

==> /var/log/ovirt-engine/engine.log <==

2015-11-06 19:17:12,085 INFO  [org.ovirt.engine.core.bll.aaa.LoginUserCommand] 
(ajp--127.0.0.1-8702-9) Running command: LoginUserCommand internal: false.

2015-11-06 19:17:12,128 INFO  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(ajp--127.0.0.1-8702-9) Correlation ID: null, Call Stack: null, Custom Event 
ID: -1, Message: User admin@internal logged in.

==> /var/log/ovirt-engine/server.log <==

2015-11-06 19:17:13,654 INFO  
[org.apache.sshd.client.session.ClientSessionImpl] (pool-18-thread-1) Client 
session created

2015-11-06 19:17:13,663 INFO  
[org.apache.sshd.client.session.ClientSessionImpl] (pool-18-thread-2) Server 
version string: SSH-2.0-OpenSSH_6.9

2015-11-06 19:17:13,667 WARN  
[org.apache.sshd.client.session.ClientSessionImpl] (pool-18-thread-3) Exception 
caught: java.lang.IllegalStateException: Unable to negotiate key exchange for 
kex algorithms (client: diffie-hellman-group1-sha1 / server: 
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1)

at 
org.apache.sshd.common.session.AbstractSession.negotiate(AbstractSession.java:1098)

at 
org.apache.sshd.common.session.AbstractSession.doHandleMessage(AbstractSession.java:357)

at 
org.apache.sshd.common.session.AbstractSession.handleMessage(AbstractSession.java:295)

at 
org.apache.sshd.client.session.ClientSessionImpl.handleMessage(ClientSessionImpl.java:266)

at 
org.apache.sshd.common.session.AbstractSession.decode(AbstractSession.java:720)

at 
org.apache.sshd.common.session.AbstractSession.messageReceived(AbstractSession.java:277)

at 
org.apache.sshd.common.AbstractSessionIoHandler.messageReceived(AbstractSessionIoHandler.java:54)

at 
org.apache.sshd.common.io.nio2.Nio2Session$1.completed(Nio2Session.java:188)

at 
org.apache.sshd.common.io.nio2.Nio2Session$1.completed(Nio2Session.java:174)

at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126) 
[rt.jar:1.7.0_79]

at sun.nio.ch.Invoker$2.run(Invoker.java:218) [rt.jar:1.7.0_79]

at 
sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
 [rt.jar:1.7.0_79]

at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
[rt.jar:1.7.0_79]

at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
[rt.jar:1.7.0_79]

at

Re: [ovirt-users] Moving a Hosted Engine from Fedora 20 to CentOS 7

2015-10-29 Thread John Florian 
On 10/29/2015 05:49 AM, Roy Golan wrote:
>
>
> On Thu, Oct 29, 2015 at 11:39 AM, Roy Golan  > wrote:
>
>
>
> On Wed, Oct 28, 2015 at 10:23 PM, John Florian
> mailto:jflor...@doubledog.org>> wrote:
>
> Can somebody please point me to documentation or describe how
> I should
> proceed with this task?  I see lots of pages for moving from a
> physical
> engine to a VM and vice-versa but am having no luck finding
> how to go
> about building a new HE to obsolete my original.
>
>
> using ovirt-hosted-engine-setup you can choose a setup without
> using the appliance. So you can scratch install your VM
>
>
>
> BTW the ovirt-engine-appliacnce we build [1] is Centos based. Seems
> like perfect candidate.
>
> #install the appliance
> yum install ovirt-engine-appliance
>
> #and then run the setup
> ovirt-hosted-engine-setup
>
> choose "disk" in this stage
> Please specify the device to boot the VM from (cdrom, disk, pxe) [cdrom]: disk
>
> it will suggest the downloaded appliance automatically
> See this wiki for reference
> http://www.ovirt.org/Features/HEApplianceFlow#Testing
>

Neat!  I was unaware of the HEA so I'm happy to learn of this offering. 
However, my concern is focused more on a procedure that I presently can
only imagine looking something akin to:

1. hosted-engine --set-maintenance --mode=global
2. hosted-engine --vm-poweroff
3. ovirt-hosted-engine-setup ...
4. use the exact same host name and IP address
5. hosted-engine --vm-start
6. hosted-engine --set-maintenance --mode=none

Or perhaps:

1. create a new guest
2. inside run foo to deploy the HE packages
3. configure it be aware of existing HE
4. run bar manually or wait for the two HE's to sync their state, sort
of like a RAID mirror
5. power off the original HE guest and allow the new one to be the sole
provider going forward

My confusion may simply stem from having forgot much of the process when
I deployed my HE back in January this year.  But I thought it best to
get started on the right foot for the simplest and/or best practice.

-- 
John Florian

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Moving a Hosted Engine from Fedora 20 to CentOS 7

2015-10-29 Thread Roy Golan 
On Thu, Oct 29, 2015 at 11:39 AM, Roy Golan  wrote:

>
>
> On Wed, Oct 28, 2015 at 10:23 PM, John Florian 
> wrote:
>
>> Can somebody please point me to documentation or describe how I should
>> proceed with this task?  I see lots of pages for moving from a physical
>> engine to a VM and vice-versa but am having no luck finding how to go
>> about building a new HE to obsolete my original.
>>
>>
> using ovirt-hosted-engine-setup you can choose a setup without using the
> appliance. So you can scratch install your VM
>


BTW the ovirt-engine-appliacnce we build [1] is Centos based. Seems like
perfect candidate.

#install the appliance
yum install ovirt-engine-appliance

#and then run the setup
ovirt-hosted-engine-setup

choose "disk" in this stage

Please specify the device to boot the VM from (cdrom, disk, pxe) [cdrom]: disk

it will suggest the downloaded appliance automatically

See this wiki for reference
http://www.ovirt.org/Features/HEApplianceFlow#Testing


--
>> John Florian
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Moving a Hosted Engine from Fedora 20 to CentOS 7

2015-10-29 Thread Roy Golan 
On Wed, Oct 28, 2015 at 10:23 PM, John Florian 
wrote:

> Can somebody please point me to documentation or describe how I should
> proceed with this task?  I see lots of pages for moving from a physical
> engine to a VM and vice-versa but am having no luck finding how to go
> about building a new HE to obsolete my original.
>
>
using ovirt-hosted-engine-setup you can choose a setup without using the
appliance. So you can scratch install your VM

> --
> John Florian
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Moving a Hosted Engine from Fedora 20 to CentOS 7

2015-10-28 Thread John Florian 
Can somebody please point me to documentation or describe how I should
proceed with this task?  I see lots of pages for moving from a physical
engine to a VM and vice-versa but am having no luck finding how to go
about building a new HE to obsolete my original.

-- 
John Florian

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users