Bug 1338503
| Summary: | Failed to remove watchdog device from template via REST | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Artyom <alukiano> | ||||
| Component: | RestAPI | Assignee: | Juan Hernández <juan.hernandez> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Shira Maximov <mshira> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 4.0.0 | CC: | alukiano, bugs, dfediuck, juan.hernandez, mavital, michal.skrivanek, mperina | ||||
| Target Milestone: | ovirt-4.0.0-rc | Flags: | rule-engine:
ovirt-4.0.0+
rule-engine: planning_ack+ juan.hernandez: devel_ack+ rule-engine: testing_ack+ |
||||
| Target Release: | 4.0.0 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-07-05 08:05:00 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
logs? 1. Please open an additional bug on the text 'VM is not found' (should be without 'is' at least). Another one on 'Cannot ${action} ${type}' ...
2. You added it to a template and tried to remove from a VM? Reproduction steps would have helped here.
3. Is it a regression? Did it work in the past (3.6.x) - you've marked it as such - in which version?
4. Lowered severity to medium. This is not a very common task.
I'm not aware of users who are actually using the watchdog device (it's off by default) and drivers are missing. Hence this should be in a low priority. Also, concurring Yaniv's regression question- are you sure this was working in previous versions? To Michael:
What log do you want, engine log does not really show much info about REST requests
To Yaniv:
1) Add watchdog to template
2) Try to remove watchdog from template
Failed with error
<fault>
<detail>[Cannot ${action} ${type}. VM is not found.]</detail>
<reason>Operation Failed</reason>
</fault>
3) Yes it worked under 3.6, rhevm-3.6.5.3-0.1.el6.noarch
at the very least your REST query, then engine.log. Ideally with debug level enabled Created attachment 1160479 [details]
engine log
Artyom, is this 3.6.z or 4.0 only? This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP. This regression was introduced as part of the changes to introduce the new API model in version 4 of the engine. It doesn't affect version 3 of the engine. I'm moving to the infra team. Bug relevant only for ovirt 4.0, under rhevm-3.6.7-0.1.el6.noarch delete template watchdog works fine. Bug relevant only for ovirt 4.0, under rhevm-3.6.7-0.1.el6.noarch delete template watchdog works fine. As this only affects version 4 of the API, which is seldom used at the moment, I'm removing the regression keyworkd and blocker flag. Merged long time ago and definitely part of 4.0.0.4 build verified on : oVirt Engine Version: 4.1.0-0.0.master.20160609051254.gita18ebb1.el7.centos verification steps: 1. Add watchdog to template 2. Try to remove watchdog device via REST(DELETE request on specific watchdog link) oVirt 4.0.0 has been released, closing current release. |
Description of problem: Failed to remove watchdog device from template via REST Version-Release number of selected component (if applicable): ovirt-engine-4.0.0-0.0.master.20160516171427.git0860aa2.el7.centos.noarch How reproducible: Always Steps to Reproduce: 1. Add watchdog to template 2. Try to remove watchdog device via REST(DELETE request on specific watchdog link) 3. Actual results: <fault> <detail>[Cannot ${action} ${type}. VM is not found.]</detail> <reason>Operation Failed</reason> </fault> Expected results: Delete action succeed and watchdog device removed from VM Additional info: bug relevant for both API versions