<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 24, 2017 at 4:34 AM, 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=""><br>
On 12/23/2017 5:38 PM, Jason Keltz wrote:<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></blockquote></span></blockquote><div><br></div><div>Can you specify what did you upgrade, and in which order? Engine, hosts? Cluster level, etc.?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Initially, after upgrade to 4.2, the status of many of my hosts changed from "server" to "desktop". That's okay - I can change them back.<br></blockquote></span></blockquote><div><br></div><div>You mean the VM type?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
My first VM, "archive", I had the ability to access console after the upgrade. I rebooted archive, and I lost the ability (option is grayed 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 can't access it, can't ping it, and there's no console either, so I literally can't get to it. I can reboot it, and shut it down, but it would be helpful to be able to access it. What to do?<br>
<br>
</blockquote></span>
I reinstalled "dist" because I needed the VM to be accessible on the network. I was going to try detatching the disk from the existing dist server, and attaching it to a new dist VM, but I ended up inadvertently deleting the disk image. I can't believe that under "storage" you can't 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 rebooting it several times, and console remains... so the loss of console has something to do with switching from a 4.1 VM to 4.2.<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I've very afraid to reboot my engine because it seems like when I reboot hosts, I lose access to console.<br>
<br>
</blockquote></span>
I rebooted one more VM for which I had console access, and again, I've lost it (at least network access remains). Now that this situation is repeatable, I'm going one of the ovirt gurus can send me the magical DB command to fix it. Probably not a solution to reinstall my 37 VMs from kickstart.. that would be a headache.<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In addition, when I try to check for "host updates", I get an error that it can't check for host updates. I ran a yum update on the hosts (after upgrading repo to 4.2 and doing a yum update) and all I'm looking for it to do is clear status, but it doesn't seem to work.<br>
<br>
</blockquote></span>
The error in engine.log when I try to update any of the hosts is:<br>
<br>
2017-12-23 19:11:36,479-05 INFO [org.ovirt.engine.core.bll.hos<wbr>tdeploy.HostUpgradeCheckComman<wbr>d] (default task-156) [ae11a704-3b40-45d3-9850-932f6<wbr>ed91ed9] Running command: HostUpgradeCheckCommand internal: false. Entities affected : ID: 45f8b331-842e-48e7-9df8-56addd<wbr>b93836 Type: VDSAction group EDIT_HOST_CONFIGURATION with role type ADMIN<br>
2017-12-23 19:11:36,496-05 INFO [org.ovirt.engine.core.dal.dbb<wbr>roker.auditloghandling.AuditLo<wbr>gDirector] (default task-156) [] EVENT_ID: HOST_AVAILABLE_UPDATES_STARTED<wbr>(884), Started to check for available updates on host virt1.<br>
2017-12-23 19:11:36,500-05 INFO [org.ovirt.engine.core.bll.hos<wbr>tdeploy.HostUpgradeCheckIntern<wbr>alCommand] (EE-ManagedThreadFactory-comma<wbr>ndCoordinator-Thread-7) [ae11a704-3b40-45d3-9850-932f6<wbr>ed91ed9] Running command: HostUpgradeCheckInternalComman<wbr>d internal: true. Entities affected : ID: 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] (EE-ManagedThreadFactory-comma<wbr>ndCoordinator-Thread-7) [ae11a704-3b40-45d3-9850-932f6<wbr>ed91ed9] Executing Ansible command: ANSIBLE_STDOUT_CALLBACK=hostup<wbr>gradeplugin [/usr/bin/ansible-playbook, --check, --private-key=/etc/pki/ovirt-e<wbr>ngine/keys/engine_id_rsa, --inventory=/tmp/ansible-inven<wbr>tory1039100972039373314, /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] (EE-ManagedThreadFactory-comma<wbr>ndCoordinator-Thread-7) [ae11a704-3b40-45d3-9850-932f6<wbr>ed91ed9] Ansible playbook command has exited with value: 4<br>
2017-12-23 19:11:37,897-05 ERROR [org.ovirt.engine.core.bll.hos<wbr>t.HostUpgradeManager] (EE-ManagedThreadFactory-comma<wbr>ndCoordinator-Thread-7) [ae11a704-3b40-45d3-9850-932f6<wbr>ed91ed9] Failed to run check-update of host 'virt1-mgmt'.<br>
2017-12-23 19:11:37,897-05 ERROR [org.ovirt.engine.core.bll.hos<wbr>tdeploy.HostUpdatesChecker] (EE-ManagedThreadFactory-comma<wbr>ndCoordinator-Thread-7) [ae11a704-3b40-45d3-9850-932f6<wbr>ed91ed9] Failed to check if updates are available for host 'virt1' with error message 'Failed to run check-update of host 'virt1-mgmt'.'<br>
2017-12-23 19:11:37,904-05 ERROR [org.ovirt.engine.core.dal.dbb<wbr>roker.auditloghandling.AuditLo<wbr>gDirector] (EE-ManagedThreadFactory-comma<wbr>ndCoordinator-Thread-7) [ae11a704-3b40-45d3-9850-932f6<wbr>ed91ed9] EVENT_ID: HOST_AVAILABLE_UPDATES_FAILED(<wbr>839), Failed to check for available updates on host virt1 with message 'Failed to run check-update of host 'virt1-mgmt'.'.<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>Can you share the complete logs? Best if you could file a bug about it, with the logs attached.</div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
<br>
Jason.<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>
</div></div></blockquote></div><br></div></div>