Bug 1125244
| Summary: | hosted engine upgrade in a NFS setup leaves the engine status as 'unknown stale-data' | ||
|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Antoni Segura Puimedon <asegurap> |
| Component: | ovirt-hosted-engine-ha | Assignee: | Jiri Moskovcak <jmoskovc> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | meital avital <mavital> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.5 | CC: | bazulay, bugs, dfediuck, ecohen, gklein, iheim, jmoskovc, rbalakri, yeylon |
| Target Milestone: | --- | ||
| Target Release: | 3.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | sla | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-17 12:24:32 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: | |||
oVirt 3.5 has been released and should include the fix for this issue. |
Description of problem: When upgrading from 3.4 to 3.5, following the steps in: http://www.ovirt.org/Hosted_Engine_Howto#Upgrade_Hosted_Engine After finishing all the steps, the engine status in --vm-status is reported as 'unknown stale-data'. Version-Release number of selected component (if applicable): ovirt-hosted-engine-ha-1.2.1-0.2.master.20140725101556.fc20.noarch How reproducible: I only did it once, but talking with jmoskovc seems like it is something that should reproduce. Steps to Reproduce: 1. Follow the guide for the upgrade on an NFS setup 2. On the host with the engine VM do: hosted-engine --vm-status Actual results: --== Host 2 status ==-- Status up-to-date : False Hostname : 10.34.63.180 Host ID : 2 Engine status : unknown stale-data Score : 2000 Local maintenance : False Host timestamp : 1406640293 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=1406640293 (Tue Jul 29 15:24:53 2014) host-id=2 score=2000 maintenance=False bridge=True cpu-load=0.0856 engine-health={"health": "good", "vm": "up", "detail": "up"} gateway=True mem-free=3192 Expected results: Engine status reports the status Additional info: