Bug 1272075
Summary: | [vdsm] cannot add host with 3.6 vdsm into 3.5.4 engine / Storage domain does not exist | ||
---|---|---|---|
Product: | [oVirt] vdsm | Reporter: | Jiri Belka <jbelka> |
Component: | General | Assignee: | Ala Hino <ahino> |
Status: | CLOSED WORKSFORME | QA Contact: | Aharon Canan <acanan> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.17.9 | CC: | ahino, amureini, bugs, jbelka, oourfali, tnisan, ybronhei, ylavi |
Target Milestone: | ovirt-3.6.2 | Keywords: | Triaged |
Target Release: | 4.17.10 | Flags: | ybronhei:
ovirt-3.6.z?
ybronhei: blocker? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack? |
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | storage | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-20 14:45:08 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1264667 |
Description
Jiri Belka
2015-10-15 12:18:33 UTC
The errors seem storage related. Yaniv, can you take a look? Yes, in the log I see only the exception above repeating forever after the upgrade. please update target milestone to 3.6.0 if this is really 100% reproducible as a new upgrade regression Ala, please have a look asap Couldn't reproduce. In both logs there is no messages regarding unsupported cluster level. The only thing seen in vdsm log is StorageDomainDoesNotExist. This error indicates that there is an existing storage domain on this though this host is just being installed. Jiri, Can you make sure this host is clean? Maybe remove /rhev/ dir (assuming no data to lose). 3.5.4 was our long running RHEVM in hosted-engine setup. would you like to have access to this env or should i try to replicate the issue on clean env? I would recommend to reproduce on a clean env and if issue still exists, I will take a look at the env. Please make sure host is clean regarding old storage domains. Thanks! Pushing out until we have a reproducer. If this this just a dirty env issue, it's not 3.6.1 material. (In reply to Ala Hino from comment #7) > I would recommend to reproduce on a clean env and if issue still exists, I > will take a look at the env. > > Please make sure host is clean regarding old storage domains. > > Thanks! Hm, I can't reproduce on clean env: - rhevm 3.5.6 and rhel 7.1 with 3.5.6 vdsm > storage domain up - rhel 7.2 with vdsm-4.17.10.1-0.el7ev.noarch |