Bug 923116
| Summary: | engine: domain is not recovered after connection is reinstated in case hosts which have access to it are non-operational | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Liron Aravot <laravot> | ||||||||
| Component: | ovirt-engine | Assignee: | Liron Aravot <laravot> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Leonid Natapov <lnatapov> | ||||||||
| Severity: | urgent | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 3.2.0 | CC: | abaron, acathrow, amureini, bazulay, dpaikov, dron, dyasny, ebenahar, eedri, hateya, iheim, laravot, lnatapov, lpeer, mkublin, Rhev-m-bugs, scohen, yeylon, ykaul, yzaslavs | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | 3.2.0 | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | storage | ||||||||||
| Fixed In Version: | sf16 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | 917576 | 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: | 917576 | ||||||||||
| Bug Blocks: | 948448 | ||||||||||
| Attachments: |
|
||||||||||
|
Comment 1
Liron Aravot
2013-03-19 09:10:35 UTC
(In reply to comment #1) > This bug is about reconstruct failing after connect storage server (solved > in 917576) is being done, as InActive domain won't be selected as the new > master. Provide log for reproducing a problem, with out log this bug is speculation please change title, and provide all logs (since we already have 917576) Created attachment 712486 [details]
logs
haim/ mkublin, the original log from 917576 is fine of this scenario - you can see that the reconstruct isn't performing on domain. anyway, i've also attached the log from paikov run. (In reply to comment #5) > haim/ mkublin, the original log from 917576 is fine of this scenario - you > can see that the reconstruct isn't performing on domain. > anyway, i've also attached the log from paikov run. Liron, connect storage was not send, so reconstruct is not relevant. How you get to this situation, number of host, storages, scenario? Full log. Created attachment 712525 [details]
logs
adding needinfo? on paikov for fulls steps that he ran in that scenario. the reproduction steps can be the same as the scenario on bug 917576 - trying to activate a host when there's an inactive domain when master version changed (note that we encountered it during testing of another issue) - can be always reproduced. paikov - please add the vdsm logs. Liron, is the title correct? Created attachment 713652 [details]
vdsm.log
(In reply to comment #8) > adding needinfo? on paikov for fulls steps that he ran in that scenario. > > the reproduction steps can be the same as the scenario on bug 917576 - > trying to activate a host when there's an inactive domain when master > version changed (note that we encountered it during testing of another > issue) - can be always reproduced. > > paikov - please add the vdsm logs. 1. NFS DC with 2 data domains. 2. Block connectivity between host and storage. 3. After domains become Inactive, resume connectivity. This bug should be verified when AutoRecovery of storage is enabled and disabled sf16. fixed. 3.2 has been released 3.2 has been released 3.2 has been released 3.2 has been released |