| Summary: | WARN org.ovirt.engine.core.bll.storage.disk.image.UploadDiskImageCommand Failed to stop image transfer session. Ticket does not exist for image ... | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Natalie Gavrielov <ngavrilo> | ||||||
| Component: | BLL.Storage | Assignee: | Daniel Erez <derez> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Natalie Gavrielov <ngavrilo> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 4.0.6 | CC: | amureini, bugs, ngavrilo, plarsen, tnisan | ||||||
| Target Milestone: | ovirt-4.2.0 | Flags: | rule-engine:
ovirt-4.2+
|
||||||
| Target Release: | 4.2.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||||
| Doc Text: |
undefined
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-12-20 11:19:11 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: | |||||||
| Attachments: |
|
||||||||
(In reply to Natalie Gavrielov from comment #0) > Steps to Reproduce: > Upload a disk image Was this done via the GUI or the API (or doesn't it matter?) > Additional info: > It seems it has no impact on image upload behaviour, but having this message > appear in engine.log ~15,000 times is just too much I'd say! Yikes! Created attachment 1229025 [details] engine.log for ui upload (In reply to Allon Mureinik from comment #1) > (In reply to Natalie Gavrielov from comment #0) > > Steps to Reproduce: > > Upload a disk image > Was this done via the GUI or the API (or doesn't it matter?) In this specific case I used the API.. now I made sure that it also happens with a normal GUI upload.. and it does (but strangely I've uploaded 2 disks using the ui, and see these warnings are issues only for one of them, meaning, these warnings are not consistent, the only difference I noticed is: raw upload - didn't issue warnings and the qcow one did..). (In reply to Natalie Gavrielov from comment #2) > Created attachment 1229025 [details] > engine.log for ui upload > > (In reply to Allon Mureinik from comment #1) > > (In reply to Natalie Gavrielov from comment #0) > > > Steps to Reproduce: > > > Upload a disk image > > Was this done via the GUI or the API (or doesn't it matter?) > > In this specific case I used the API.. now I made sure that it also happens > with a normal GUI upload.. and it does (but strangely I've uploaded 2 disks > using the ui, and see these warnings are issues only for one of them, > meaning, these warnings are not consistent, the only difference I noticed is: > raw upload - didn't issue warnings and the qcow one did..). ohh.. my bad.. the warnings that appear in this log, for image id: 82adb2b8-67c8-49e6-85a3-4df33d755ea6 are from a GUI upload that was paused by the system because of a certificate issue.. (so it still means the UI can cause these warnings as well as the API) Looks like I have a similar situation. The data volume the uploads were attempted to (they failed) was deleted. But there are still attempts to upload the images. How can you cancel these jobs? (In reply to Peter Larsen from comment #4) > Looks like I have a similar situation. The data volume the uploads were > attempted to (they failed) was deleted. But there are still attempts to > upload the images. How can you cancel these jobs? @Peter - you can cancel the uploads from the Disks main tab (Upload -> Cancel) (In reply to Daniel Erez from comment #5) > (In reply to Peter Larsen from comment #4) > > Looks like I have a similar situation. The data volume the uploads were > > attempted to (they failed) was deleted. But there are still attempts to > > upload the images. How can you cancel these jobs? > > @Peter - you can cancel the uploads from the Disks main tab (Upload -> > Cancel) It's been a while, so this is from memory. I think the problem was that the disk was a "data" and not an ISO. There are/was (?? not sure now) no option to cancel and I couldn't find one in the CLI either. Since I've redone the install since then, I no longer have a way to reproduce easily. Verified
Scenarios tested:
1. Uploaded disk using python sdk 4.1.3
a. regular upload.
b. kill ongoing upload.
2. Uploaded disk using UI
a. regular upload.
b. pause upload.
c. cancel upload.
Used builds:
ovirt-engine-4.2.0-0.0.master.20170721095131.git9f5e90c.el7.centos.noarch
ovirt-imageio-common-1.1.0-0.201706250653.git86d47ac.el7.centos.noarch
ovirt-imageio-proxy-1.1.0-0.201706250653.git86d47ac.el7.centos.noarch
ovirt-imageio-daemon-1.1.0-0.201706250653.git86d47ac.el7.centos.noarch
ovirt-engine-restapi-4.2.0-0.0.master.20170721095131.git9f5e90c.el7.centos.noarch
vdsm-4.20.1-218.git1b7671f.el7.centos.x86_64
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |
Created attachment 1228621 [details] engine.log Description of problem: The following message floods the engine.log: WARN org.ovirt.engine.core.bll.storage.disk.image.UploadDiskImageCommand Failed to stop image transfer session. Ticket does not exist for image ... Version-Release number of selected component (if applicable): ovirt-engine-4.0.6-0.1.el7ev.noarch vdsm-4.18.17-1.el7ev.x86_64 How reproducible: 100% Steps to Reproduce: Upload a disk image Actual results: Upload is successful - but this message in engine.log appears constantly.. WARN org.ovirt.engine.core.bll.storage.disk.image.UploadDiskImageCommand Failed to stop image transfer session. Ticket does not exist for image ... Expected results: No errors / warnings Additional info: It seems it has no impact on image upload behaviour, but having this message appear in engine.log ~15,000 times is just too much # cat /var/log/ovirt-engine/engine.log | grep "Failed to stop image transfer session" | wc -l 15332