Bug 1523225
| Summary: | OVF update failure ignored | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Avihai <aefrat> | 
| Component: | BLL.Storage | Assignee: | Eyal Shenitzky <eshenitz> | 
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Yosi Ben Shimon <ybenshim> | 
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2.0 | CC: | aefrat, bugs, tnisan | 
| Target Milestone: | ovirt-4.2.1 | Flags: | rule-engine:
                ovirt-4.2+ | 
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-02-12 11:53:07 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: | 1321585, 1364947 | ||
| 
        
          Comment 6
        
        
          Avihai
        
        
        
        
        
          2017-12-10 09:16:17 UTC
        
       The following scenario has been tested: **************** New scenario: 1) UI: Create a new SD (NFS preferred) with a VM . 2) UI: To make sure OVF update will be triggered change the VM name . 3) VDSM host: change the relevant SD images on (rhev/data/...) user &group ownership from kvm:vdsm (or 36:36) to root:root via : "chwon root:root <image_path>" 4) Deactivate relevant SD . We saw the OVF update failed but still the SD was deactivated. ****************** The results are: 1. When checking the "Ignore OVF update failure" checkbox: the OVF is ignored and the SD is deactivated. 2. When NOT checking the "Ignore OVF update failure" checkbox: the OVF update fails and the SD stays active. Moving to VERIFIED This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |