Bug 1625283 - transfer_id should be included in image ticket
Summary: transfer_id should be included in image ticket
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.2.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.2.7
: ---
Assignee: Daniel Erez
QA Contact: Shir Fishbain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-04 14:44 UTC by Daniel Erez
Modified: 2018-11-02 14:32 UTC (History)
3 users (show)

Fixed In Version: ovirt-engine-4.2.7.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-02 14:32:45 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 94159 0 master MERGED core: transfer_id in add image ticket 2018-09-13 09:11:28 UTC
oVirt gerrit 94638 0 ovirt-engine-4.2 MERGED core: transfer_id in add image ticket 2018-10-03 11:33:22 UTC

Description Daniel Erez 2018-09-04 14:44:03 UTC
Upon creating an image ticket, the 'transfer_id' should be included in the ticket. I.e. when adding a ticket in the daemon, the transfer_id should be sent. So following a specific transfer in the daemon logs would be possible according to the transfer_id.

Comment 1 Shir Fishbain 2018-10-14 11:27:43 UTC
From image-proxy.log:

(Thread-5  ) INFO 2018-10-14 14:04:26,814 auth:197:auth2:(add_signed_ticket) Adding new ticket: <Ticket id=u'cc216cc3-e405-43e2-afd0-c637bad50c6c', transfer_id=None, url=u'https://storage-ge9-vdsm2.scl.lab.tlv.redhat.com:54322' timeout=35997.185286045074 at 0x7fb9cfc201d0>
(Thread-6  ) INFO 2018-10-14 14:04:26,980 images:104:root:(get) [10.35.7.57] READ ticket=cc216cc3-e405-43e2-afd0-c637bad50c6c
(Thread-6  ) INFO 2018-10-14 14:04:26,984 connectionpool:735:requests.packages.urllib3.connectionpool:(_new_conn) Starting new HTTPS connection (1): storage-ge9-vdsm2.scl.lab.tlv.redhat.com
(Thread-8  ) INFO 2018-10-14 14:13:06,946 auth:211:auth2:(delete_ticket) Deleting ticket u'cc216cc3-e405-43e2-afd0-c637bad50c6c'

Is transfer_id needs to be that way? (transfer_id=None)

Comment 2 Daniel Erez 2018-10-14 12:55:03 UTC
(In reply to Shir Fishbain from comment #1)
> From image-proxy.log:
> 
> (Thread-5  ) INFO 2018-10-14 14:04:26,814 auth:197:auth2:(add_signed_ticket)
> Adding new ticket: <Ticket id=u'cc216cc3-e405-43e2-afd0-c637bad50c6c',
> transfer_id=None,
> url=u'https://storage-ge9-vdsm2.scl.lab.tlv.redhat.com:54322'
> timeout=35997.185286045074 at 0x7fb9cfc201d0>
> (Thread-6  ) INFO 2018-10-14 14:04:26,980 images:104:root:(get) [10.35.7.57]
> READ ticket=cc216cc3-e405-43e2-afd0-c637bad50c6c
> (Thread-6  ) INFO 2018-10-14 14:04:26,984
> connectionpool:735:requests.packages.urllib3.connectionpool:(_new_conn)
> Starting new HTTPS connection (1): storage-ge9-vdsm2.scl.lab.tlv.redhat.com
> (Thread-8  ) INFO 2018-10-14 14:13:06,946 auth:211:auth2:(delete_ticket)
> Deleting ticket u'cc216cc3-e405-43e2-afd0-c637bad50c6c'
> 
> Is transfer_id needs to be that way? (transfer_id=None)

Seems that the fix wasn't included in 4.2.7.2, it should be in the next build.

Comment 3 Shir Fishbain 2018-10-14 14:57:12 UTC
(MainThread) INFO 2018-10-14 13:12:20,673 server:45:server:(start) Starting (pid=6761, version=1.4.5)
(MainThread) INFO 2018-10-14 13:12:20,728 image_proxy:26:root:(main) Server started, successfully notified systemd
(Thread-1  ) INFO 2018-10-14 17:22:33,976 auth:197:auth2:(add_signed_ticket) Adding new ticket: <Ticket id=u'73446d4b-5c2b-497b-8183-a0913ee80019', transfer_id=u'16ac1d4a-daa5-4b61-95f8-8f237e6337dc', url=u'https://storage-ge11-vdsm1.scl.lab.tlv.redhat.com:54322' timeout=35998.0228369236 at 0x7f97f1a1b550>

The transfer_id included in the ticket.

ovirt-engine-4.2.7.2-0.1.el7ev.noarch
vdsm-4.20.42-1.el7ev.x86_64

Comment 4 Sandro Bonazzola 2018-11-02 14:32:45 UTC
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.7 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.


Note You need to log in before you can comment on or make changes to this bug.