Bug 1314522
Summary: | hosted-engine --vm-status results into python exception | ||
---|---|---|---|
Product: | [oVirt] ovirt-hosted-engine-ha | Reporter: | olovopb |
Component: | General | Assignee: | Martin Sivák <msivak> |
Status: | CLOSED NOTABUG | QA Contact: | Ilanit Stein <istein> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.3.4.3 | CC: | bugs, dfediuck, olovopb, ylavi |
Target Milestone: | --- | Flags: | rule-engine:
planning_ack?
rule-engine: devel_ack? rule-engine: testing_ack? |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-27 08:00:30 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
olovopb
2016-03-03 20:12:21 UTC
*** Bug 1314523 has been marked as a duplicate of this bug. *** Hi, according to the message: " Metadata version 8 from host 10 too new for this agent (highest compatible version: 1) " The HE agent in one or more of your hosts is not updated. Did you make sure to update hosted engine RPMs on all relevant hypervisors? Hello, it was clear and new install of OS and new install of ovirt, so I assume, I have installed the newest versions of packages. This seems to be an issue with the metadata file that was not properly cleaned up during the setup. That usually happens when you use a physical disk that had some data before. It is exactly the same problem as in the bug you referenced. You should be able to fix this using the following procedure: 1) Stop all HA agents (they are probably down anyway) 2) Write all 0 (zeros) to the iSCSI LUN using dd if=/dev/zero of=/dev/the_proper_device bs=1M If you can attach the ovirt-hosted-engine-setup deploy log we will take a look at why setup did not clean the file during the install (it usually does that). Hello, well I used nfs instead of iscsi, so I do not have logs anymore. As I remember I used new iscsi LUN from NAS and I tried several times to reinstall hosted engine. I also cleaned isscsi disk between reinstalls. I used also --clean-metadata option in hosted-engine command. Nothing worked,so |decided to use NFS to store hosted engine VM. I cannot reconfigure it to scsi now, because it is in production. Clean metadata would work if you called it in a loop with high enough number of IDs. The dd would make it a single step operation. New iSCSI LUN does not mean there are all zeros unfortunately. Glad to hear NFS worked for you and too bad we can't check what went wrong as we are supposed to clear the volume. Since we cannot reproduce it closing this issue. If you are able to reproduce and provide logs please reopen with all relevant information. |