Bug 960169
| Summary: | engine: support different status for disk copies on different domains | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Dafna Ron <dron> | ||||
| Component: | General | Assignee: | Tal Nisan <tnisan> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Elad <ebenahar> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | --- | CC: | acanan, bsettle, bugs, ebenahar, lpeer, mlipchuk, rbalakri, Rhev-m-bugs, scohen, srevivo, tnisan | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-07-02 08:08:14 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: | 1142762 | ||||||
| Bug Blocks: | 879222, 978975 | ||||||
| Attachments: |
|
||||||
This could be solved as part of BZ978975, if images will be mapped with new image id for each storage then it will be more simpler to set the image status per one image/storage. Currently the status of the image is part of the images table, which means that we'll have the same status for all the image copies on the different domains. I'm changing this bug description to reflect that we need to support different image status on different domain and postponing to 3.6. Allon, can you please mark this one as depends on the disks refactor bug (if we already have it opened?) (In reply to Liron Aravot from comment #7) > Allon, can you please mark this one as depends on the disks refactor bug (if > we already have it opened?) I cannot find one, but it definitely depends on it conceptually. Tal - please open one and make this depend on it. Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA. oVirt 4.0 beta has been released, moving to RC milestone. oVirt 4.0 beta has been released, moving to RC milestone. Closing old bugs, please reopen if still needed, in any case patches are welcome. |
Created attachment 744238 [details] logs Description of problem: I have a template copied to 3 domains. I removed the template lv from only one of the domains using lvremove. when I tried to remove the copy of this image in UI from that domain only and vdsm returned "Image does not exist" engine change the template's image to illegal (even though there are 2 other domains with that image and it can still be used by the two other domains). Version-Release number of selected component (if applicable): sf15 How reproducible: 100% Steps to Reproduce: 1. create 3 domains 2. create a template and copy it to all of the domains 3. run lvremove on the template image only on one of the domains 4. try to remove the image from the domain which you removed the lv from through the UI (template -> storage -> select the domain -> remove) Actual results: vdsm returns "Image does not exist" and the template's image becomes illegal even though the image exists on two other domains. Expected results: we should not move the entire image to illegal, only that copy of the image for that specific domain. Additional info: logs