unfortunately the actual underlying error is hidden here; re the original bug report - yes there are successful requests to the glance API, but they don't appear to correspond timestamp wise to the 180 second timeout detailed (the good requests are some seconds later).
unfortunately the actual underlying error is hidden here; re the original bug report - yes there are successful requests to the glance API, but they don't appear to correspond timestamp wise to the 180 second timeout detailed (the good requests are some seconds later).