<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 24, 2017 at 1:53 PM, Jason Keltz <span dir="ltr"><<a href="mailto:jas@cse.yorku.ca" target="_blank">jas@cse.yorku.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Quoting Yaniv Kaul <<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>>:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Sun, Dec 24, 2017 at 4:34 AM, Jason Keltz <<a href="mailto:jas@cse.yorku.ca" target="_blank">jas@cse.yorku.ca</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On 12/23/2017 5:38 PM, Jason Keltz wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi..<br>
<br>
I took the plunge to 4.2, but I think maybe I should have waited a bit...<br>
<br>
</blockquote>
<br>
</blockquote>
Can you specify what did you upgrade, and in which order? Engine, hosts?<br>
Cluster level, etc.?<br>
<br>
</blockquote>
<br></span>
I was running 4.1.8 everywhere. I upgraded engine (standalone) to 4.2, then the 4 hosts. I stopped ovirt-engine, added the new repo for 4.2, ran the yum update of ovirt setup, ran engine-setup and that process worked flawlessly. No errors. I had just upgraded to 4.1.8 a few days ago, so all my ovirt infrastructure was running latest ovirt and I also upgraded engine and hosts to latest CentOS and latest kernel with the last 4.1.8 update. I then upgraded cluster level. All the VMs were going to be upgraded as they were rebooted, and since it's the reboot that breaks console, and since a reinstall brings it back, I'm going to assume it's the switch from 4.1 to 4.2 cluster that breaks it. If I submit this as a bug then what log/logs would I submit?</blockquote><div><br></div><div>I think vdsm log is going to be very helpful, but also the console (and potentially engine). ovirt-log-collector should collect everything needed.</div><div>Thanks,</div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Initially, after upgrade to 4.2, the status of many of my hosts changed<br>
from "server" to "desktop". That's okay - I can change them back.<br>
<br>
</blockquote>
<br>
</blockquote>
You mean the VM type?<br>
<br>
<br>
</blockquote></span>
Yes. VM type. Most of the VMs switched from desktop to server after the update.<div><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
My first VM, "archive", I had the ability to access console after the<br>
upgrade. I rebooted archive, and I lost the ability (option is grayed<br>
out). The VM boots, but I need access to the console.<br>
<br>
My second VM is called "dist". That one, ovirt says is running, but I<br>
can't access it, can't ping it, and there's no console either, so I<br>
literally can't get to it. I can reboot it, and shut it down, but it would<br>
be helpful to be able to access it. What to do?<br>
<br>
I reinstalled "dist" because I needed the VM to be accessible on the<br>
</blockquote>
network. I was going to try detatching the disk from the existing dist<br>
server, and attaching it to a new dist VM, but I ended up inadvertently<br>
deleting the disk image. I can't believe that under "storage" you can't<br>
detatch a disk from a VM - you can only delete the disk.<br>
<br>
After reinstalling dist, I got back console, and network access! I tried<br>
rebooting it several times, and console remains... so the loss of console<br>
has something to do with switching from a 4.1 VM to 4.2.<br>
<br>
I've very afraid to reboot my engine because it seems like when I reboot<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
hosts, I lose access to console.<br>
<br>
I rebooted one more VM for which I had console access, and again, I've<br>
</blockquote>
lost it (at least network access remains). Now that this situation is<br>
repeatable, I'm going one of the ovirt gurus can send me the magical DB<br>
command to fix it. Probably not a solution to reinstall my 37 VMs from<br>
kickstart.. that would be a headache.<br>
<br>
In addition, when I try to check for "host updates", I get an error that<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
it can't check for host updates. I ran a yum update on the hosts (after<br>
upgrading repo to 4.2 and doing a yum update) and all I'm looking for it to<br>
do is clear status, but it doesn't seem to work.<br>
<br>
The error in engine.log when I try to update any of the hosts is:<br>
</blockquote>
<br>
2017-12-23 19:11:36,479-05 INFO [org.ovirt.engine.core.bll.hos<br>
tdeploy.HostUpgradeCheckComman<wbr>d] (default task-156)<br>
[ae11a704-3b40-45d3-9850-932f6<wbr>ed91ed9] Running command:<br>
HostUpgradeCheckCommand internal: false. Entities affected : ID:<br>
45f8b331-842e-48e7-9df8-56addd<wbr>b93836 Type: VDSAction group<br>
EDIT_HOST_CONFIGURATION with role type ADMIN<br>
2017-12-23 19:11:36,496-05 INFO [org.ovirt.engine.core.dal.dbb<br>
roker.auditloghandling.AuditLo<wbr>gDirector] (default task-156) [] EVENT_ID:<br>
HOST_AVAILABLE_UPDATES_STARTED<wbr>(884), Started to check for available<br>
updates on host virt1.<br>
2017-12-23 19:11:36,500-05 INFO [org.ovirt.engine.core.bll.hos<br>
tdeploy.HostUpgradeCheckIntern<wbr>alCommand] (EE-ManagedThreadFactory-comma<wbr>ndCoordinator-Thread-7)<br>
[ae11a704-3b40-45d3-9850-932f6<wbr>ed91ed9] Running command:<br>
HostUpgradeCheckInternalComman<wbr>d internal: true. Entities affected : ID:<br>
45f8b331-842e-48e7-9df8-56addd<wbr>b93836 Type: VDS<br>
2017-12-23 19:11:36,504-05 INFO [org.ovirt.engine.core.common.<wbr>utils.ansible.AnsibleExecutor]<br>
(EE-ManagedThreadFactory-comma<wbr>ndCoordinator-Thread-7)<br>
[ae11a704-3b40-45d3-9850-932f6<wbr>ed91ed9] Executing Ansible command:<br>
ANSIBLE_STDOUT_CALLBACK=hostup<wbr>gradeplugin [/usr/bin/ansible-playbook,<br>
--check, --private-key=/etc/pki/ovirt-e<wbr>ngine/keys/engine_id_rsa,<br>
--inventory=/tmp/ansible-inven<wbr>tory1039100972039373314,<br>
/usr/share/ovirt-engine/playbo<wbr>oks/ovirt-host-upgrade.yml] [Logfile: null]<br>
2017-12-23 19:11:37,897-05 INFO [org.ovirt.engine.core.common.<wbr>utils.ansible.AnsibleExecutor]<br>
(EE-ManagedThreadFactory-comma<wbr>ndCoordinator-Thread-7)<br>
[ae11a704-3b40-45d3-9850-932f6<wbr>ed91ed9] Ansible playbook command has<br>
exited with value: 4<br>
2017-12-23 19:11:37,897-05 ERROR [org.ovirt.engine.core.bll.hos<wbr>t.HostUpgradeManager]<br>
(EE-ManagedThreadFactory-comma<wbr>ndCoordinator-Thread-7)<br>
[ae11a704-3b40-45d3-9850-932f6<wbr>ed91ed9] Failed to run check-update of host<br>
'virt1-mgmt'.<br>
2017-12-23 19:11:37,897-05 ERROR [org.ovirt.engine.core.bll.hos<wbr>tdeploy.HostUpdatesChecker]<br>
(EE-ManagedThreadFactory-comma<wbr>ndCoordinator-Thread-7)<br>
[ae11a704-3b40-45d3-9850-932f6<wbr>ed91ed9] Failed to check if updates are<br>
available for host 'virt1' with error message 'Failed to run check-update<br>
of host 'virt1-mgmt'.'<br>
2017-12-23 19:11:37,904-05 ERROR [org.ovirt.engine.core.dal.dbb<br>
roker.auditloghandling.AuditLo<wbr>gDirector] (EE-ManagedThreadFactory-comma<wbr>ndCoordinator-Thread-7)<br>
[ae11a704-3b40-45d3-9850-932f6<wbr>ed91ed9] EVENT_ID:<br>
HOST_AVAILABLE_UPDATES_FAILED(<wbr>839), Failed to check for available updates<br>
on host virt1 with message 'Failed to run check-update of host<br>
'virt1-mgmt'.'.<br>
<br>
<br>
</blockquote>
Can you share the complete logs? Best if you could file a bug about it,<br>
with the logs attached.<br>
Y.<br>
<br>
</blockquote></div></div>
I will do that later today.<br>
<br>
Thanks!<span class="HOEnZb"><font color="#888888"><br>
<br>
Jason.<br>
<br>
<br>
-- <br>
dfjklgdfgkljdfgklfdklgj</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
<br>
<br>
</div></div></blockquote></div><br></div></div>