[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

[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:

[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

[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: 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] 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

[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:

[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

[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 >

[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