Bug 1379074
| Summary: | [storage] Improve logging for ExportVM flow | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Marina Kalinin <mkalinin> |
| Component: | ovirt-engine | Assignee: | Shmuel Melamud <smelamud> |
| Status: | CLOSED ERRATA | QA Contact: | sefi litmanovich <slitmano> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.6.5 | CC: | acalleja, bgraveno, bmcclain, gklein, lsurette, mavital, mgoldboi, michal.skrivanek, mkalinin, rbalakri, Rhev-m-bugs, srevivo, tjelinek, tnisan, ykaul |
| Target Milestone: | ovirt-4.1.1 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
Previously, the ExportVmCommand appeared in the Engine log without the ID of the virtual machine being exported. This information has now been added to the log.
Note: After this change, users must have export permissions for the virtual machine and its disks to export a virtual machine. Previously, permissions to export virtual machine disks were sufficient.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-25 00:52:16 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1425219 | ||
|
Description
Marina Kalinin
2016-09-24 16:49:36 UTC
Michal as you are taking all export domain related bugs I'm putting this one on virt as well as a part of your consideration about the future of the export domain is it the correlation id across engine and vdsm you are looking for? there is a separate argument/bug about that i believe (also opened by you I think) (In reply to Michal Skrivanek from comment #6) > is it the correlation id across engine and vdsm you are looking for? there > is a separate argument/bug about that i believe (also opened by you I think) 1. and 2. - yes. 3. is different and still important, in my opinion. Can you please give a reference to the bug related to correlation ID fix (items 1 and 2)? (In reply to Shmuel Melamud from comment #9) > Can you please give a reference to the bug related to correlation ID fix > (items 1 and 2)? Tough one. Michal, I think you meant this one: https://bugzilla.redhat.com/show_bug.cgi?id=1339045 I do not think we have a specific one for correlation id in general. We may have a bug somewhere (or a gerrit commit?) requesting to stop using it, I think by smizrahi. Shmuel, I would start from little - fix those specific flows as requested. And this will contribute to the use of correlation id and related. #3 is addressed, the rest is out of scope of this bug. (In reply to Marina from comment #10) > (In reply to Shmuel Melamud from comment #9) > > Can you please give a reference to the bug related to correlation ID fix > > (items 1 and 2)? > > Tough one. > Michal, I think you meant this one: > https://bugzilla.redhat.com/show_bug.cgi?id=1339045 Indeed that is the one > Shmuel, I would start from little - fix those specific flows as requested. > And this will contribute to the use of correlation id and related. Ok, that's what is being tracked here Verified on rhevm-4.1.1.4-0.1.el7.noarch : [org.ovirt.engine.core.bll.ExportVmCommand] now show also the ID of the exported vm. |