Bug 955569
| Summary: | [Storage] A new Storage Domain not becoming Master after Re-initializing DataCenter. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Leonid Natapov <lnatapov> | ||||
| Component: | ovirt-engine | Assignee: | Liron Aravot <laravot> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Leonid Natapov <lnatapov> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | unspecified | CC: | acathrow, amureini, dyasny, hateya, iheim, lpeer, Rhev-m-bugs, scohen, yeylon, ykaul | ||||
| Target Milestone: | --- | Keywords: | Regression | ||||
| Target Release: | 3.2.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | storage | ||||||
| Fixed In Version: | sf16 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 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: | 948448 | ||||||
| Attachments: |
|
||||||
It's a regression. fixed. sf 16 3.2 has been released 3.2 has been released 3.2 has been released 3.2 has been released |
Created attachment 738921 [details] engine log Description of problem: I have two hosts and 3 SDs that resied on one host. Blocking connection from both hosts to StorageDomain. Storage Domains become Uknown and Imactive. 2 of them Uknown and 1 is Inactive. No host is SPM because the connection to SD is blocked. Re-initializng DC with the new Storage domain that both hosts can connect to it. After attaching new storage domain it should become Master but it doesn't. Version-Release number of selected component (if applicable): How reproducible: Actual results: After reinitializeing a new SD not becoming Master SD. Expected results: After reinitializeing a new SD should become Master SD. Additional info: logs attached.