[stable-only] Fix tempurl validity in OrchestrationDeployAction
Bug #1872446 reported by
Rabi Mishra
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Triaged
|
Medium
|
Rabi Mishra |
Bug Description
We delete the container and object created for tenpurl after 300s/5mins[1], whereas the tempurl expiry is set to 300mins[2][3].
[2]https:/
[3] https:/
Changed in tripleo: | |
status: | New → Triaged |
assignee: | nobody → Rabi Mishra (rabi) |
importance: | Undecided → Medium |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/719439 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=e319325ed43 60bf776e54cf153 51dcb3b8043676
Committed: https:/
Submitter: Zuul
Branch: stable/train
commit e319325ed4360bf 776e54cf15351dc b3b8043676
Author: Rabi Mishra <email address hidden>
Date: Mon Apr 13 17:15:27 2020 +0530
[stable-only] Pass timeout in mins to create_temp_url()
We seem to be deleting the container and object created for
tempurl before the tempurl expiry(300mins).
Also in certain deployments (possibly with high load), it has
been noticed that servers respond after the 5mins timeout.
Let's double the default timeout to 10mins.
Closes-Bug: #1872446 a16793a1509d509 3f8bf366270
Change-Id: I7d25f866461f5b