[ovirt-users] Re: cannot manually migrate vm's

2020-03-14 Thread Strahil Nikolov 
On March 14, 2020 11:41:42 PM GMT+02:00, eev...@digitaldatatechs.com wrote:
>I tried a migration on several different vm's. The migratiuon window
>flashes on the screen and immediately errors out saying it cannot get
>the vm ID. (See screen shot)
>Nothing in the logs corresponds to the time I try the migration and a
>destination server is never an option. 
>Also, load balancing is affected. At times it appears to work but at
>this moment, I have 10 servers on one host and none on the other 2. 
>All this since this upgrade which should have been seamless since is
>was not a version upgrade but a sub version.
>
>
>Eric Evans
>Digital Data Services LLC.
>304.660.9080
>
>
>-Original Message-
>From: Strahil Nikolov  
>Sent: Saturday, March 14, 2020 3:27 PM
>To: eev...@digitaldatatechs.com; 'Yedidyah Bar David' 
>Cc: 'users' 
>Subject: [ovirt-users] Re: cannot manually migrate vm's
>
>On March 14, 2020 4:01:48 PM GMT+02:00, eev...@digitaldatatechs.com
>wrote:
>>I am still having issue with migration and load balancing since the 
>>upgrade.
>>Any thoughts?
>>
>>Eric Evans
>>Digital Data Services LLC.
>>304.660.9080
>>
>>
>>-Original Message-
>>From: Yedidyah Bar David 
>>Sent: Tuesday, March 10, 2020 5:06 AM
>>To: eev...@digitaldatatechs.com
>>Cc: users 
>>Subject: [ovirt-users] Re: cannot manually migrate vm's
>>
>>On Tue, Mar 10, 2020 at 10:42 AM  wrote:
>>>
>>> Apologies. I had ask about the upgrade before I did it and thought
>>this would be a different subject.
>>> I have check the engine log. I can share it as well as any others.
>>There is a message in the engine log that appears right after I try to
>
>>migrate that says:
>>>
>>> 2020-03-10 04:40:09,375-04 INFO
>>> [org.ovirt.engine.core.utils.servlet.ServletUtils] (default task-29)
>
>>> [] Can't read file 
>>> '/usr/share/ovirt-engine/files/spice/SpiceVersion.txt' for request 
>>> '/ovirt-engine/services/files/spice/SpiceVersion.txt' -- 404
>>> 2020-03-10 04:40:19,985-04 WARN
>>[org.ovirt.engine.core.bll.SearchQuery] (default task-29) 
>>[33910d48-e9a3-4761-a7c4-ba93d9acfa2b]
>>ResourceManager::searchBusinessObjects - Invalid search text - ''VMs :
>>id=''
>>>
>>> These entries come right after I attempt manual migration.
>>
>>Are you sure this is the only relevant thing you get?
>>
>>Perhaps it's a UI issue. Some things you can try:
>>
>>1. Check also ui.log and also your browser's console.
>>
>>2. Try with a new browser profile, and/or clean its cache.
>>
>>3. Try using the API/SDK.
>>
>>We have many example scripts for the SDK, but this does not include 
>>migration, sadly:
>>
>>https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples
>>
>>But you can have a look at this, which is what is actually testing
>that 
>>this works in our CI:
>>
>>https://github.com/oVirt/ovirt-system-tests/blob/master/basic-suite-4.3
>>/test-scenarios/006_migrations.py
>>
>>Actually understanding how latter works and using it as-is will be 
>>hard. So you can start with one of the example scripts from first, and
>
>>copy/adapt relevant lines from second to your test script.
>>
>>Best regards,
>>
>>>
>>> Eric Evans
>>> Digital Data Services LLC.
>>> 304.660.9080
>>>
>>>
>>> -Original Message-
>>> From: Yedidyah Bar David 
>>> Sent: Tuesday, March 10, 2020 3:56 AM
>>> To: eev...@digitaldatatechs.com
>>> Cc: users 
>>> Subject: [ovirt-users] Re: cannot manually migrate vm's
>>>
>>> On Tue, Mar 10, 2020 at 12:49 AM 
>wrote:
>>> >
>>> > I upgraded from 4.3.8 to 4.3.9. Before the migration, I could
>>manually migrate vm's and also it would automatically load balance the
>
>>hosts. Now I cannot manually migrate and I have one server with no
>vm's 
>>and 2 with several.
>>> > If I put a host into maintenance mode, it will migrate the vm's
>off
>>to other hosts, but before I noticed it would move vm's around to load
>
>>balance and now it does not.
>>> > Not sure if this is a bug or not.
>>> > How it happens:
>>> > When I right click on a vm and click migrate, the migrate screen
>>flashes on screen then disappears. Same behavior if I highlight the vm
>
>>and click the migrate button at the top of the vm screen.
>>> > It's not critical, but something that needs corrected.
>>> > Any help or advice is very much appreciated.
>>>
>>> You already started a different thread about this, with subject:
>>>
>>> [ovirt-users] upgrade from 4.38 to 4.39
>>>
>>> Right? Did you see my reply there? In short: Please check/share logs
>>(more than what you shared there). Thanks.
>>>
>>> (No problem continuing in current thread, I think the subject is
>>> better...)
>>>
>>> Best regards,
>>> --
>>> Didi
>>> ___
>>> Users mailing list -- users@ovirt.org To unsubscribe send an email
>to 
>>> users-le...@ovirt.org Privacy
>>> Statement: https://www.ovirt.org/privacy-policy.html
>>> oVirt Code of Conduct: 
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives: 
>>>
>>https://lists.ovirt.org/archives/lis

[ovirt-users] Re: cannot manually migrate vm's

2020-03-14 Thread eevans 
I tried a migration on several different vm's. The migratiuon window flashes on 
the screen and immediately errors out saying it cannot get the vm ID. (See 
screen shot)
Nothing in the logs corresponds to the time I try the migration and a 
destination server is never an option. 
Also, load balancing is affected. At times it appears to work but at this 
moment, I have 10 servers on one host and none on the other 2. 
All this since this upgrade which should have been seamless since is was not a 
version upgrade but a sub version.


Eric Evans
Digital Data Services LLC.
304.660.9080


-Original Message-
From: Strahil Nikolov  
Sent: Saturday, March 14, 2020 3:27 PM
To: eev...@digitaldatatechs.com; 'Yedidyah Bar David' 
Cc: 'users' 
Subject: [ovirt-users] Re: cannot manually migrate vm's

On March 14, 2020 4:01:48 PM GMT+02:00, eev...@digitaldatatechs.com wrote:
>I am still having issue with migration and load balancing since the 
>upgrade.
>Any thoughts?
>
>Eric Evans
>Digital Data Services LLC.
>304.660.9080
>
>
>-Original Message-
>From: Yedidyah Bar David 
>Sent: Tuesday, March 10, 2020 5:06 AM
>To: eev...@digitaldatatechs.com
>Cc: users 
>Subject: [ovirt-users] Re: cannot manually migrate vm's
>
>On Tue, Mar 10, 2020 at 10:42 AM  wrote:
>>
>> Apologies. I had ask about the upgrade before I did it and thought
>this would be a different subject.
>> I have check the engine log. I can share it as well as any others.
>There is a message in the engine log that appears right after I try to 
>migrate that says:
>>
>> 2020-03-10 04:40:09,375-04 INFO
>> [org.ovirt.engine.core.utils.servlet.ServletUtils] (default task-29) 
>> [] Can't read file 
>> '/usr/share/ovirt-engine/files/spice/SpiceVersion.txt' for request 
>> '/ovirt-engine/services/files/spice/SpiceVersion.txt' -- 404
>> 2020-03-10 04:40:19,985-04 WARN
>[org.ovirt.engine.core.bll.SearchQuery] (default task-29) 
>[33910d48-e9a3-4761-a7c4-ba93d9acfa2b]
>ResourceManager::searchBusinessObjects - Invalid search text - ''VMs :
>id=''
>>
>> These entries come right after I attempt manual migration.
>
>Are you sure this is the only relevant thing you get?
>
>Perhaps it's a UI issue. Some things you can try:
>
>1. Check also ui.log and also your browser's console.
>
>2. Try with a new browser profile, and/or clean its cache.
>
>3. Try using the API/SDK.
>
>We have many example scripts for the SDK, but this does not include 
>migration, sadly:
>
>https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples
>
>But you can have a look at this, which is what is actually testing that 
>this works in our CI:
>
>https://github.com/oVirt/ovirt-system-tests/blob/master/basic-suite-4.3
>/test-scenarios/006_migrations.py
>
>Actually understanding how latter works and using it as-is will be 
>hard. So you can start with one of the example scripts from first, and 
>copy/adapt relevant lines from second to your test script.
>
>Best regards,
>
>>
>> Eric Evans
>> Digital Data Services LLC.
>> 304.660.9080
>>
>>
>> -Original Message-
>> From: Yedidyah Bar David 
>> Sent: Tuesday, March 10, 2020 3:56 AM
>> To: eev...@digitaldatatechs.com
>> Cc: users 
>> Subject: [ovirt-users] Re: cannot manually migrate vm's
>>
>> On Tue, Mar 10, 2020 at 12:49 AM  wrote:
>> >
>> > I upgraded from 4.3.8 to 4.3.9. Before the migration, I could
>manually migrate vm's and also it would automatically load balance the 
>hosts. Now I cannot manually migrate and I have one server with no vm's 
>and 2 with several.
>> > If I put a host into maintenance mode, it will migrate the vm's off
>to other hosts, but before I noticed it would move vm's around to load 
>balance and now it does not.
>> > Not sure if this is a bug or not.
>> > How it happens:
>> > When I right click on a vm and click migrate, the migrate screen
>flashes on screen then disappears. Same behavior if I highlight the vm 
>and click the migrate button at the top of the vm screen.
>> > It's not critical, but something that needs corrected.
>> > Any help or advice is very much appreciated.
>>
>> You already started a different thread about this, with subject:
>>
>> [ovirt-users] upgrade from 4.38 to 4.39
>>
>> Right? Did you see my reply there? In short: Please check/share logs
>(more than what you shared there). Thanks.
>>
>> (No problem continuing in current thread, I think the subject is
>> better...)
>>
>> Best regards,
>> --
>> Didi
>> ___
>> Users mailing list -- users@ovirt.org To unsubscribe send an email to 
>> users-le...@ovirt.org Privacy
>> Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct: 
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives: 
>>
>https://lists.ovirt.org/archives/list/users@ovirt.org/message/UZ5YXYDO
>> 3I2ERDMXPFOE6TLS3SDF7ASR/
>>
>
>
>--
>Didi
>___
>Users mailing list -- users@ovirt.org
>To unsubscribe send an email to users-le...@ovirt.org

[ovirt-users] Re: cannot manually migrate vm's

2020-03-14 Thread Strahil Nikolov 
On March 14, 2020 4:01:48 PM GMT+02:00, eev...@digitaldatatechs.com wrote:
>I am still having issue with migration and load balancing since the
>upgrade.
>Any thoughts?
>
>Eric Evans
>Digital Data Services LLC.
>304.660.9080
>
>
>-Original Message-
>From: Yedidyah Bar David  
>Sent: Tuesday, March 10, 2020 5:06 AM
>To: eev...@digitaldatatechs.com
>Cc: users 
>Subject: [ovirt-users] Re: cannot manually migrate vm's
>
>On Tue, Mar 10, 2020 at 10:42 AM  wrote:
>>
>> Apologies. I had ask about the upgrade before I did it and thought
>this would be a different subject.
>> I have check the engine log. I can share it as well as any others.
>There is a message in the engine log that appears right after I try to
>migrate that says:
>>
>> 2020-03-10 04:40:09,375-04 INFO  
>> [org.ovirt.engine.core.utils.servlet.ServletUtils] (default task-29) 
>> [] Can't read file 
>> '/usr/share/ovirt-engine/files/spice/SpiceVersion.txt' for request 
>> '/ovirt-engine/services/files/spice/SpiceVersion.txt' -- 404
>> 2020-03-10 04:40:19,985-04 WARN 
>[org.ovirt.engine.core.bll.SearchQuery] (default task-29)
>[33910d48-e9a3-4761-a7c4-ba93d9acfa2b]
>ResourceManager::searchBusinessObjects - Invalid search text - ''VMs :
>id=''
>>
>> These entries come right after I attempt manual migration.
>
>Are you sure this is the only relevant thing you get?
>
>Perhaps it's a UI issue. Some things you can try:
>
>1. Check also ui.log and also your browser's console.
>
>2. Try with a new browser profile, and/or clean its cache.
>
>3. Try using the API/SDK.
>
>We have many example scripts for the SDK, but this does not include
>migration, sadly:
>
>https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples
>
>But you can have a look at this, which is what is actually testing that
>this works in our CI:
>
>https://github.com/oVirt/ovirt-system-tests/blob/master/basic-suite-4.3/test-scenarios/006_migrations.py
>
>Actually understanding how latter works and using it as-is will be
>hard. So you can start with one of the example scripts from first, and
>copy/adapt relevant lines from second to your test script.
>
>Best regards,
>
>>
>> Eric Evans
>> Digital Data Services LLC.
>> 304.660.9080
>>
>>
>> -Original Message-
>> From: Yedidyah Bar David 
>> Sent: Tuesday, March 10, 2020 3:56 AM
>> To: eev...@digitaldatatechs.com
>> Cc: users 
>> Subject: [ovirt-users] Re: cannot manually migrate vm's
>>
>> On Tue, Mar 10, 2020 at 12:49 AM  wrote:
>> >
>> > I upgraded from 4.3.8 to 4.3.9. Before the migration, I could
>manually migrate vm's and also it would automatically load balance the
>hosts. Now I cannot manually migrate and I have one server with no vm's
>and 2 with several.
>> > If I put a host into maintenance mode, it will migrate the vm's off
>to other hosts, but before I noticed it would move vm's around to load
>balance and now it does not.
>> > Not sure if this is a bug or not.
>> > How it happens:
>> > When I right click on a vm and click migrate, the migrate screen
>flashes on screen then disappears. Same behavior if I highlight the vm
>and click the migrate button at the top of the vm screen.
>> > It's not critical, but something that needs corrected.
>> > Any help or advice is very much appreciated.
>>
>> You already started a different thread about this, with subject:
>>
>> [ovirt-users] upgrade from 4.38 to 4.39
>>
>> Right? Did you see my reply there? In short: Please check/share logs
>(more than what you shared there). Thanks.
>>
>> (No problem continuing in current thread, I think the subject is 
>> better...)
>>
>> Best regards,
>> --
>> Didi
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org Privacy 
>> Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct: 
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives: 
>>
>https://lists.ovirt.org/archives/list/users@ovirt.org/message/UZ5YXYDO
>> 3I2ERDMXPFOE6TLS3SDF7ASR/
>>
>
>
>--
>Didi
>___
>Users mailing list -- users@ovirt.org
>To unsubscribe send an email to users-le...@ovirt.org Privacy
>Statement: https://www.ovirt.org/privacy-policy.html
>oVirt Code of Conduct:
>https://www.ovirt.org/community/about/community-guidelines/
>List Archives:
>https://lists.ovirt.org/archives/list/users@ovirt.org/message/EKNK3XLG7ZOKS7OWLS6SGNIGACLBFCAG/
>___
>Users mailing list -- users@ovirt.org
>To unsubscribe send an email to users-le...@ovirt.org
>Privacy Statement: https://www.ovirt.org/privacy-policy.html
>oVirt Code of Conduct:
>https://www.ovirt.org/community/about/community-guidelines/
>List Archives:
>https://lists.ovirt.org/archives/list/users@ovirt.org/message/3R2FHBFBEAIUZ263CNYV7LZF6YACVQ5Q/

Hi Eric,

I assume the reinstall was  OK.

You need to get deeper in the logs:
1. Check libvirt logs on source and destination host
2.  Check vdsm l

[ovirt-users] Re: upgrade from 4.38 to 4.39

2020-03-14 Thread Strahil Nikolov 
On March 14, 2020 1:10:06 PM GMT+02:00, eev...@digitaldatatechs.com wrote:
>It worked with the password. 
>I recopied the authorized keys and ssh keys from engine host to it and
>copied it's keys back. 
>What do I need to look at to prevent this in the future?
>
>Eric Evans
>Digital Data Services LLC.
>304.660.9080
>
>
>-Original Message-
>From: Strahil Nikolov  
>Sent: Saturday, March 14, 2020 5:24 AM
>To: users@ovirt.org; eev...@digitaldatatechs.com
>Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39
>
>On March 14, 2020 1:34:46 AM GMT+02:00, eev...@digitaldatatechs.com
>wrote:
>>This is from the secure log, /var/log/secure
>>
>>Mar 13 19:23:17 kvm01 sshd[46045]: Accepted publickey for root from
>>192.168.254.240 port 39668 ssh2: RSA
>>SHA256:FobQnekaxOaUQ75xNh1OuZg5orcGbw+BgLDtr+el5VY
>>Mar 13 19:23:18 kvm01 sshd[46045]: pam_unix(sshd:session): session 
>>opened for user root by (uid=0) Mar 13 19:24:14 kvm01 sshd[46207]: 
>>Connection closed by 192.168.254.240 port 39760 [preauth] Mar 13 
>>19:24:23 kvm01 sudo: pam_unix(sudo:session): session opened for user 
>>root by root(uid=0) Mar 13 19:24:23 kvm01 sudo:
>pam_unix(sudo:session): 
>>session closed for user root Mar 13 19:24:24 kvm01 sudo: 
>>pam_unix(sudo:session): session opened for user root by root(uid=0)
>Mar 
>>13 19:24:24 kvm01 sudo: pam_unix(sudo:session): session closed for
>user 
>>root Mar 13 19:26:08 kvm01 sshd[46368]: Connection closed by 
>>192.168.254.240 port 39894 [preauth] Mar 13 19:26:15 kvm01 sudo: 
>>pam_unix(sudo:session): session opened for user root by root(uid=0)
>Mar 
>>13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session closed for
>user 
>>root Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session
>opened 
>>for user root by root(uid=0) Mar 13 19:26:15 kvm01 sudo: 
>>pam_unix(sudo:session): session closed for user root Mar 13 19:29:06 
>>kvm01 cockpit-session: pam_unix(cockpit:session):
>>session closed for user root
>>Mar 13 19:32:14 kvm01 sshd[46840]: Connection closed by
>192.168.254.240 
>>port 40368 [preauth] Mar 13 19:32:23 kvm01 sshd[46851]: Connection 
>>closed by 192.168.254.240 port 40382 [preauth] Mar 13 19:32:31 kvm01 
>>sudo: pam_unix(sudo:session): session opened for user root by (uid=0) 
>>Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session closed for
>
>>user root Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session 
>>opened for user root by (uid=0) Mar 13 19:32:31 kvm01 sudo: 
>>pam_unix(sudo:session): session closed for user root Mar 13 19:32:32 
>>kvm01 sudo: pam_unix(sudo:session): session opened for user root by 
>>(uid=0) Mar 13 19:32:32 kvm01 sudo: pam_unix(sudo:session): session 
>>closed for user root Mar 13 19:32:34 kvm01 sudo: 
>>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13
>
>>19:32:34 kvm01 sudo: pam_unix(sudo:session): session closed for user 
>>root Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session
>opened 
>>for user root by (uid=0) Mar 13 19:32:34 kvm01 sudo: 
>>pam_unix(sudo:session): session closed for user root Mar 13 19:32:34 
>>kvm01 sudo: pam_unix(sudo:session): session opened for user root by 
>>(uid=0) Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session 
>>closed for user root Mar 13 19:32:35 kvm01 sudo: 
>>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13
>
>>19:32:35 kvm01 sudo: pam_unix(sudo:session): session closed for user 
>>root Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session
>opened 
>>for user root by (uid=0) Mar 13 19:32:36 kvm01 sudo: 
>>pam_unix(sudo:session): session closed for user root Mar 13 19:32:36 
>>kvm01 sudo: pam_unix(sudo:session): session opened for user root by 
>>(uid=0) Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session 
>>closed for user root Mar 13 19:32:36 kvm01 sudo: 
>>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13
>
>>19:32:37 kvm01 sudo: pam_unix(sudo:session): session closed for user 
>>root Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session
>opened 
>>for user root by (uid=0) Mar 13 19:32:38 kvm01 sudo: 
>>pam_unix(sudo:session): session closed for user root Mar 13 19:32:38 
>>kvm01 sudo: pam_unix(sudo:session): session opened for user root by 
>>(uid=0) Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session 
>>closed for user root Mar 13 19:32:39 kvm01 sudo: 
>>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13
>
>>19:32:39 kvm01 sudo: pam_unix(sudo:session): session closed for user 
>>root Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session
>opened 
>>for user root by (uid=0) Mar 13 19:32:39 kvm01 sudo: 
>>pam_unix(sudo:session): session closed for user root Mar 13 19:32:39 
>>kvm01 sudo: pam_unix(sudo:session): session opened for user root by 
>>(uid=0) Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session 
>>closed for user root Mar 13 19:32:40 kvm01 sudo: 
>>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13
>
>>19:32:40 kvm01 sudo: p

[ovirt-users] Re: cannot manually migrate vm's

2020-03-14 Thread eevans 
I am still having issue with migration and load balancing since the upgrade.
Any thoughts?

Eric Evans
Digital Data Services LLC.
304.660.9080


-Original Message-
From: Yedidyah Bar David  
Sent: Tuesday, March 10, 2020 5:06 AM
To: eev...@digitaldatatechs.com
Cc: users 
Subject: [ovirt-users] Re: cannot manually migrate vm's

On Tue, Mar 10, 2020 at 10:42 AM  wrote:
>
> Apologies. I had ask about the upgrade before I did it and thought this would 
> be a different subject.
> I have check the engine log. I can share it as well as any others. There is a 
> message in the engine log that appears right after I try to migrate that says:
>
> 2020-03-10 04:40:09,375-04 INFO  
> [org.ovirt.engine.core.utils.servlet.ServletUtils] (default task-29) 
> [] Can't read file 
> '/usr/share/ovirt-engine/files/spice/SpiceVersion.txt' for request 
> '/ovirt-engine/services/files/spice/SpiceVersion.txt' -- 404
> 2020-03-10 04:40:19,985-04 WARN  [org.ovirt.engine.core.bll.SearchQuery] 
> (default task-29) [33910d48-e9a3-4761-a7c4-ba93d9acfa2b] 
> ResourceManager::searchBusinessObjects - Invalid search text - ''VMs : id=''
>
> These entries come right after I attempt manual migration.

Are you sure this is the only relevant thing you get?

Perhaps it's a UI issue. Some things you can try:

1. Check also ui.log and also your browser's console.

2. Try with a new browser profile, and/or clean its cache.

3. Try using the API/SDK.

We have many example scripts for the SDK, but this does not include migration, 
sadly:

https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples

But you can have a look at this, which is what is actually testing that this 
works in our CI:

https://github.com/oVirt/ovirt-system-tests/blob/master/basic-suite-4.3/test-scenarios/006_migrations.py

Actually understanding how latter works and using it as-is will be hard. So you 
can start with one of the example scripts from first, and copy/adapt relevant 
lines from second to your test script.

Best regards,

>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
>
>
> -Original Message-
> From: Yedidyah Bar David 
> Sent: Tuesday, March 10, 2020 3:56 AM
> To: eev...@digitaldatatechs.com
> Cc: users 
> Subject: [ovirt-users] Re: cannot manually migrate vm's
>
> On Tue, Mar 10, 2020 at 12:49 AM  wrote:
> >
> > I upgraded from 4.3.8 to 4.3.9. Before the migration, I could manually 
> > migrate vm's and also it would automatically load balance the hosts. Now I 
> > cannot manually migrate and I have one server with no vm's and 2 with 
> > several.
> > If I put a host into maintenance mode, it will migrate the vm's off to 
> > other hosts, but before I noticed it would move vm's around to load balance 
> > and now it does not.
> > Not sure if this is a bug or not.
> > How it happens:
> > When I right click on a vm and click migrate, the migrate screen flashes on 
> > screen then disappears. Same behavior if I highlight the vm and click the 
> > migrate button at the top of the vm screen.
> > It's not critical, but something that needs corrected.
> > Any help or advice is very much appreciated.
>
> You already started a different thread about this, with subject:
>
> [ovirt-users] upgrade from 4.38 to 4.39
>
> Right? Did you see my reply there? In short: Please check/share logs (more 
> than what you shared there). Thanks.
>
> (No problem continuing in current thread, I think the subject is 
> better...)
>
> Best regards,
> --
> Didi
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org Privacy 
> Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/UZ5YXYDO
> 3I2ERDMXPFOE6TLS3SDF7ASR/
>


--
Didi
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: 
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/EKNK3XLG7ZOKS7OWLS6SGNIGACLBFCAG/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3R2FHBFBEAIUZ263CNYV7LZF6YACVQ5Q/

[ovirt-users] Re: upgrade from 4.38 to 4.39

2020-03-14 Thread eevans 
I recopied the authorized keys from the engine host, did restorecon -RFv /root, 
and chmod 644 on .ssh. I’ll try it again.

 

Eric Evans

Digital Data Services LLC.

304.660.9080



 

From: Maton, Brett  
Sent: Saturday, March 14, 2020 7:44 AM
To: eev...@digitaldatatechs.com
Cc: Strahil Nikolov ; Ovirt Users 
Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39

 

I think all you need on the inaccessible host is

/root/.ssh/authorized_keys

copied from a working host (with the same ownership, permissions and SELinux 
context)

 

On Sat, 14 Mar 2020 at 11:15, mailto:eev...@digitaldatatechs.com> > wrote:

It worked with the password. 
I recopied the authorized keys and ssh keys from engine host to it and copied 
it's keys back. 
What do I need to look at to prevent this in the future?

Eric Evans
Digital Data Services LLC.
304.660.9080


-Original Message-
From: Strahil Nikolov mailto:hunter86...@yahoo.com> > 
Sent: Saturday, March 14, 2020 5:24 AM
To: users@ovirt.org  ; eev...@digitaldatatechs.com 
 
Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39

On March 14, 2020 1:34:46 AM GMT+02:00, eev...@digitaldatatechs.com 
  wrote:
>This is from the secure log, /var/log/secure
>
>Mar 13 19:23:17 kvm01 sshd[46045]: Accepted publickey for root from
>192.168.254.240 port 39668 ssh2: RSA
>SHA256:FobQnekaxOaUQ75xNh1OuZg5orcGbw+BgLDtr+el5VY
>Mar 13 19:23:18 kvm01 sshd[46045]: pam_unix(sshd:session): session 
>opened for user root by (uid=0) Mar 13 19:24:14 kvm01 sshd[46207]: 
>Connection closed by 192.168.254.240 port 39760 [preauth] Mar 13 
>19:24:23 kvm01 sudo: pam_unix(sudo:session): session opened for user 
>root by root(uid=0) Mar 13 19:24:23 kvm01 sudo: pam_unix(sudo:session): 
>session closed for user root Mar 13 19:24:24 kvm01 sudo: 
>pam_unix(sudo:session): session opened for user root by root(uid=0) Mar 
>13 19:24:24 kvm01 sudo: pam_unix(sudo:session): session closed for user 
>root Mar 13 19:26:08 kvm01 sshd[46368]: Connection closed by 
>192.168.254.240 port 39894 [preauth] Mar 13 19:26:15 kvm01 sudo: 
>pam_unix(sudo:session): session opened for user root by root(uid=0) Mar 
>13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session closed for user 
>root Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session opened 
>for user root by root(uid=0) Mar 13 19:26:15 kvm01 sudo: 
>pam_unix(sudo:session): session closed for user root Mar 13 19:29:06 
>kvm01 cockpit-session: pam_unix(cockpit:session):
>session closed for user root
>Mar 13 19:32:14 kvm01 sshd[46840]: Connection closed by 192.168.254.240 
>port 40368 [preauth] Mar 13 19:32:23 kvm01 sshd[46851]: Connection 
>closed by 192.168.254.240 port 40382 [preauth] Mar 13 19:32:31 kvm01 
>sudo: pam_unix(sudo:session): session opened for user root by (uid=0) 
>Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session closed for 
>user root Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session 
>opened for user root by (uid=0) Mar 13 19:32:31 kvm01 sudo: 
>pam_unix(sudo:session): session closed for user root Mar 13 19:32:32 
>kvm01 sudo: pam_unix(sudo:session): session opened for user root by 
>(uid=0) Mar 13 19:32:32 kvm01 sudo: pam_unix(sudo:session): session 
>closed for user root Mar 13 19:32:34 kvm01 sudo: 
>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 
>19:32:34 kvm01 sudo: pam_unix(sudo:session): session closed for user 
>root Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened 
>for user root by (uid=0) Mar 13 19:32:34 kvm01 sudo: 
>pam_unix(sudo:session): session closed for user root Mar 13 19:32:34 
>kvm01 sudo: pam_unix(sudo:session): session opened for user root by 
>(uid=0) Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session 
>closed for user root Mar 13 19:32:35 kvm01 sudo: 
>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 
>19:32:35 kvm01 sudo: pam_unix(sudo:session): session closed for user 
>root Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened 
>for user root by (uid=0) Mar 13 19:32:36 kvm01 sudo: 
>pam_unix(sudo:session): session closed for user root Mar 13 19:32:36 
>kvm01 sudo: pam_unix(sudo:session): session opened for user root by 
>(uid=0) Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session 
>closed for user root Mar 13 19:32:36 kvm01 sudo: 
>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 
>19:32:37 kvm01 sudo: pam_unix(sudo:session): session closed for user 
>root Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session opened 
>for user root by (uid=0) Mar 13 19:32:38 kvm01 sudo: 
>pam_unix(sudo:session): session closed for user root Mar 13 19:32:38 
>kvm01 sudo: pam_unix(sudo:session): session opened for user root by 
>(uid=0) Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session 
>closed for user root Mar 13 19:32:39 kvm01 sudo: 
>pam_unix(sudo:session): session opened for user root by

[ovirt-users] Re: upgrade from 4.38 to 4.39

2020-03-14 Thread Maton, Brett 
I think all you need on the inaccessible host is
/root/.ssh/authorized_keys
copied from a working host (with the same ownership, permissions and
SELinux context)

On Sat, 14 Mar 2020 at 11:15,  wrote:

> It worked with the password.
> I recopied the authorized keys and ssh keys from engine host to it and
> copied it's keys back.
> What do I need to look at to prevent this in the future?
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
>
>
> -Original Message-
> From: Strahil Nikolov 
> Sent: Saturday, March 14, 2020 5:24 AM
> To: users@ovirt.org; eev...@digitaldatatechs.com
> Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39
>
> On March 14, 2020 1:34:46 AM GMT+02:00, eev...@digitaldatatechs.com wrote:
> >This is from the secure log, /var/log/secure
> >
> >Mar 13 19:23:17 kvm01 sshd[46045]: Accepted publickey for root from
> >192.168.254.240 port 39668 ssh2: RSA
> >SHA256:FobQnekaxOaUQ75xNh1OuZg5orcGbw+BgLDtr+el5VY
> >Mar 13 19:23:18 kvm01 sshd[46045]: pam_unix(sshd:session): session
> >opened for user root by (uid=0) Mar 13 19:24:14 kvm01 sshd[46207]:
> >Connection closed by 192.168.254.240 port 39760 [preauth] Mar 13
> >19:24:23 kvm01 sudo: pam_unix(sudo:session): session opened for user
> >root by root(uid=0) Mar 13 19:24:23 kvm01 sudo: pam_unix(sudo:session):
> >session closed for user root Mar 13 19:24:24 kvm01 sudo:
> >pam_unix(sudo:session): session opened for user root by root(uid=0) Mar
> >13 19:24:24 kvm01 sudo: pam_unix(sudo:session): session closed for user
> >root Mar 13 19:26:08 kvm01 sshd[46368]: Connection closed by
> >192.168.254.240 port 39894 [preauth] Mar 13 19:26:15 kvm01 sudo:
> >pam_unix(sudo:session): session opened for user root by root(uid=0) Mar
> >13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session closed for user
> >root Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session opened
> >for user root by root(uid=0) Mar 13 19:26:15 kvm01 sudo:
> >pam_unix(sudo:session): session closed for user root Mar 13 19:29:06
> >kvm01 cockpit-session: pam_unix(cockpit:session):
> >session closed for user root
> >Mar 13 19:32:14 kvm01 sshd[46840]: Connection closed by 192.168.254.240
> >port 40368 [preauth] Mar 13 19:32:23 kvm01 sshd[46851]: Connection
> >closed by 192.168.254.240 port 40382 [preauth] Mar 13 19:32:31 kvm01
> >sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
> >Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session closed for
> >user root Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session
> >opened for user root by (uid=0) Mar 13 19:32:31 kvm01 sudo:
> >pam_unix(sudo:session): session closed for user root Mar 13 19:32:32
> >kvm01 sudo: pam_unix(sudo:session): session opened for user root by
> >(uid=0) Mar 13 19:32:32 kvm01 sudo: pam_unix(sudo:session): session
> >closed for user root Mar 13 19:32:34 kvm01 sudo:
> >pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13
> >19:32:34 kvm01 sudo: pam_unix(sudo:session): session closed for user
> >root Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened
> >for user root by (uid=0) Mar 13 19:32:34 kvm01 sudo:
> >pam_unix(sudo:session): session closed for user root Mar 13 19:32:34
> >kvm01 sudo: pam_unix(sudo:session): session opened for user root by
> >(uid=0) Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session
> >closed for user root Mar 13 19:32:35 kvm01 sudo:
> >pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13
> >19:32:35 kvm01 sudo: pam_unix(sudo:session): session closed for user
> >root Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened
> >for user root by (uid=0) Mar 13 19:32:36 kvm01 sudo:
> >pam_unix(sudo:session): session closed for user root Mar 13 19:32:36
> >kvm01 sudo: pam_unix(sudo:session): session opened for user root by
> >(uid=0) Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session
> >closed for user root Mar 13 19:32:36 kvm01 sudo:
> >pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13
> >19:32:37 kvm01 sudo: pam_unix(sudo:session): session closed for user
> >root Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session opened
> >for user root by (uid=0) Mar 13 19:32:38 kvm01 sudo:
> >pam_unix(sudo:session): session closed for user root Mar 13 19:32:38
> >kvm01 sudo: pam_unix(sudo:session): session opened for user root by
> >(uid=0) Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session
> >closed for user root Mar 13 19:32:39 kvm01 sudo:
> >pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13
> >19:32:39 kvm01 sudo: pam_unix(sudo:session): session closed for user
> >root Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session opened
> >for user root by (uid=0) Mar 13 19:32:39 kvm01 sudo:
> >pam_unix(sudo:session): session closed for user root Mar 13 19:32:39
> >kvm01 sudo: pam_unix(sudo:session): session opened for user root by
> >(uid=0) Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session
> >closed for user root

[ovirt-users] Re: upgrade from 4.38 to 4.39

2020-03-14 Thread eevans 
It worked with the password. 
I recopied the authorized keys and ssh keys from engine host to it and copied 
it's keys back. 
What do I need to look at to prevent this in the future?

Eric Evans
Digital Data Services LLC.
304.660.9080


-Original Message-
From: Strahil Nikolov  
Sent: Saturday, March 14, 2020 5:24 AM
To: users@ovirt.org; eev...@digitaldatatechs.com
Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39

On March 14, 2020 1:34:46 AM GMT+02:00, eev...@digitaldatatechs.com wrote:
>This is from the secure log, /var/log/secure
>
>Mar 13 19:23:17 kvm01 sshd[46045]: Accepted publickey for root from
>192.168.254.240 port 39668 ssh2: RSA
>SHA256:FobQnekaxOaUQ75xNh1OuZg5orcGbw+BgLDtr+el5VY
>Mar 13 19:23:18 kvm01 sshd[46045]: pam_unix(sshd:session): session 
>opened for user root by (uid=0) Mar 13 19:24:14 kvm01 sshd[46207]: 
>Connection closed by 192.168.254.240 port 39760 [preauth] Mar 13 
>19:24:23 kvm01 sudo: pam_unix(sudo:session): session opened for user 
>root by root(uid=0) Mar 13 19:24:23 kvm01 sudo: pam_unix(sudo:session): 
>session closed for user root Mar 13 19:24:24 kvm01 sudo: 
>pam_unix(sudo:session): session opened for user root by root(uid=0) Mar 
>13 19:24:24 kvm01 sudo: pam_unix(sudo:session): session closed for user 
>root Mar 13 19:26:08 kvm01 sshd[46368]: Connection closed by 
>192.168.254.240 port 39894 [preauth] Mar 13 19:26:15 kvm01 sudo: 
>pam_unix(sudo:session): session opened for user root by root(uid=0) Mar 
>13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session closed for user 
>root Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session opened 
>for user root by root(uid=0) Mar 13 19:26:15 kvm01 sudo: 
>pam_unix(sudo:session): session closed for user root Mar 13 19:29:06 
>kvm01 cockpit-session: pam_unix(cockpit:session):
>session closed for user root
>Mar 13 19:32:14 kvm01 sshd[46840]: Connection closed by 192.168.254.240 
>port 40368 [preauth] Mar 13 19:32:23 kvm01 sshd[46851]: Connection 
>closed by 192.168.254.240 port 40382 [preauth] Mar 13 19:32:31 kvm01 
>sudo: pam_unix(sudo:session): session opened for user root by (uid=0) 
>Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session closed for 
>user root Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session 
>opened for user root by (uid=0) Mar 13 19:32:31 kvm01 sudo: 
>pam_unix(sudo:session): session closed for user root Mar 13 19:32:32 
>kvm01 sudo: pam_unix(sudo:session): session opened for user root by 
>(uid=0) Mar 13 19:32:32 kvm01 sudo: pam_unix(sudo:session): session 
>closed for user root Mar 13 19:32:34 kvm01 sudo: 
>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 
>19:32:34 kvm01 sudo: pam_unix(sudo:session): session closed for user 
>root Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened 
>for user root by (uid=0) Mar 13 19:32:34 kvm01 sudo: 
>pam_unix(sudo:session): session closed for user root Mar 13 19:32:34 
>kvm01 sudo: pam_unix(sudo:session): session opened for user root by 
>(uid=0) Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session 
>closed for user root Mar 13 19:32:35 kvm01 sudo: 
>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 
>19:32:35 kvm01 sudo: pam_unix(sudo:session): session closed for user 
>root Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened 
>for user root by (uid=0) Mar 13 19:32:36 kvm01 sudo: 
>pam_unix(sudo:session): session closed for user root Mar 13 19:32:36 
>kvm01 sudo: pam_unix(sudo:session): session opened for user root by 
>(uid=0) Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session 
>closed for user root Mar 13 19:32:36 kvm01 sudo: 
>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 
>19:32:37 kvm01 sudo: pam_unix(sudo:session): session closed for user 
>root Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session opened 
>for user root by (uid=0) Mar 13 19:32:38 kvm01 sudo: 
>pam_unix(sudo:session): session closed for user root Mar 13 19:32:38 
>kvm01 sudo: pam_unix(sudo:session): session opened for user root by 
>(uid=0) Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session 
>closed for user root Mar 13 19:32:39 kvm01 sudo: 
>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 
>19:32:39 kvm01 sudo: pam_unix(sudo:session): session closed for user 
>root Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session opened 
>for user root by (uid=0) Mar 13 19:32:39 kvm01 sudo: 
>pam_unix(sudo:session): session closed for user root Mar 13 19:32:39 
>kvm01 sudo: pam_unix(sudo:session): session opened for user root by 
>(uid=0) Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session 
>closed for user root Mar 13 19:32:40 kvm01 sudo: 
>pam_unix(sudo:session): session opened for user root by (uid=0) Mar 13 
>19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for user 
>root Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened 
>for user root by (uid=0) Mar 13 19:32:40 kvm01 sudo:

[ovirt-users] Re: upgrade from 4.38 to 4.39

2020-03-14 Thread eevans 
I dd a autorelabel and checked to make sure they were 644.

 

Eric Evans

Digital Data Services LLC.

304.660.9080



 

From: Maton, Brett  
Sent: Saturday, March 14, 2020 5:35 AM
To: eev...@digitaldatatechs.com
Cc: Strahil Nikolov ; Ovirt Users 
Subject: [ovirt-users] Re: upgrade from 4.38 to 4.39

 

Have you checked the file permissions and SELinux context of the SSH keys you 
copied to kvm01 ?

 

On Fri, 13 Mar 2020 at 23:39, mailto:eev...@digitaldatatechs.com> > wrote:

This is from the secure log, /var/log/secure

Mar 13 19:23:17 kvm01 sshd[46045]: Accepted publickey for root from 
192.168.254.240 port 39668 ssh2: RSA 
SHA256:FobQnekaxOaUQ75xNh1OuZg5orcGbw+BgLDtr+el5VY
Mar 13 19:23:18 kvm01 sshd[46045]: pam_unix(sshd:session): session opened for 
user root by (uid=0)
Mar 13 19:24:14 kvm01 sshd[46207]: Connection closed by 192.168.254.240 port 
39760 [preauth]
Mar 13 19:24:23 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by root(uid=0)
Mar 13 19:24:23 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:24:24 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by root(uid=0)
Mar 13 19:24:24 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:26:08 kvm01 sshd[46368]: Connection closed by 192.168.254.240 port 
39894 [preauth]
Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by root(uid=0)
Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by root(uid=0)
Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:29:06 kvm01 cockpit-session: pam_unix(cockpit:session): session 
closed for user root
Mar 13 19:32:14 kvm01 sshd[46840]: Connection closed by 192.168.254.240 port 
40368 [preauth]
Mar 13 19:32:23 kvm01 sshd[46851]: Connection closed by 192.168.254.240 port 
40382 [preauth]
Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:32 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:32 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:37 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for user root
Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for

[ovirt-users] Re: upgrade from 4.38 to 4.39

2020-03-14 Thread Maton, Brett 
Have you checked the file permissions and SELinux context of the SSH keys
you copied to kvm01 ?


On Fri, 13 Mar 2020 at 23:39,  wrote:

> This is from the secure log, /var/log/secure
>
> Mar 13 19:23:17 kvm01 sshd[46045]: Accepted publickey for root from
> 192.168.254.240 port 39668 ssh2: RSA
> SHA256:FobQnekaxOaUQ75xNh1OuZg5orcGbw+BgLDtr+el5VY
> Mar 13 19:23:18 kvm01 sshd[46045]: pam_unix(sshd:session): session opened
> for user root by (uid=0)
> Mar 13 19:24:14 kvm01 sshd[46207]: Connection closed by 192.168.254.240
> port 39760 [preauth]
> Mar 13 19:24:23 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by root(uid=0)
> Mar 13 19:24:23 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:24:24 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by root(uid=0)
> Mar 13 19:24:24 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:26:08 kvm01 sshd[46368]: Connection closed by 192.168.254.240
> port 39894 [preauth]
> Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by root(uid=0)
> Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by root(uid=0)
> Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:29:06 kvm01 cockpit-session: pam_unix(cockpit:session): session
> closed for user root
> Mar 13 19:32:14 kvm01 sshd[46840]: Connection closed by 192.168.254.240
> port 40368 [preauth]
> Mar 13 19:32:23 kvm01 sshd[46851]: Connection closed by 192.168.254.240
> port 40382 [preauth]
> Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:32 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:32 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:37 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for
> user root
> Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for
> user root by (uid=0)
> Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session)

[ovirt-users] Re: upgrade from 4.38 to 4.39

2020-03-14 Thread Strahil Nikolov 
On March 14, 2020 1:34:46 AM GMT+02:00, eev...@digitaldatatechs.com wrote:
>This is from the secure log, /var/log/secure
>
>Mar 13 19:23:17 kvm01 sshd[46045]: Accepted publickey for root from
>192.168.254.240 port 39668 ssh2: RSA
>SHA256:FobQnekaxOaUQ75xNh1OuZg5orcGbw+BgLDtr+el5VY
>Mar 13 19:23:18 kvm01 sshd[46045]: pam_unix(sshd:session): session
>opened for user root by (uid=0)
>Mar 13 19:24:14 kvm01 sshd[46207]: Connection closed by 192.168.254.240
>port 39760 [preauth]
>Mar 13 19:24:23 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by root(uid=0)
>Mar 13 19:24:23 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:24:24 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by root(uid=0)
>Mar 13 19:24:24 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:26:08 kvm01 sshd[46368]: Connection closed by 192.168.254.240
>port 39894 [preauth]
>Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by root(uid=0)
>Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by root(uid=0)
>Mar 13 19:26:15 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:29:06 kvm01 cockpit-session: pam_unix(cockpit:session):
>session closed for user root
>Mar 13 19:32:14 kvm01 sshd[46840]: Connection closed by 192.168.254.240
>port 40368 [preauth]
>Mar 13 19:32:23 kvm01 sshd[46851]: Connection closed by 192.168.254.240
>port 40382 [preauth]
>Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:31 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:32 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:32 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:34 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:35 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:36 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:37 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:38 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:39 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session opened for
>user root by (uid=0)
>Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session): session closed for
>user root
>Mar 13 19:32:40 kvm01 sudo: pam_unix(sudo:session):