os-collect-config has no timeout on collector requests get
Bug #1600652 reported by
Steve Baker
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Fix Released
|
High
|
Steve Baker | ||
Bug Description
The ec2, cfn and request collectors do a python requests get without any timeout argument. This implies a timeout of None which will wait *forever* if necessary.
This could wedge os-collect-config if a collector source is unavailable for some reason (network brownout, service down) during a collection attempt.
This is affecting quite a few live deployments, the symptom is that os-collect-config stops polling, so deployment resources timeout during stack updates.
| Changed in tripleo: | |
| assignee: | nobody → Steve Baker (steve-stevebaker) |
| status: | New → In Progress |
| Changed in tripleo: | |
| milestone: | none → newton-3 |
| importance: | Undecided → High |
Revision history for this message
| Steven Hardy (shardy) wrote | #1 |
| Changed in tripleo: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/os-collect-config 5.0.0.0b3 | #2 |
To post a comment you must log in.
This was closed by https:/