Your message dated Fri, 29 Jun 2018 22:06:55 +0200
with message-id <[email protected]>
and subject line Re: python-openstackclient: autopkgtest timed out after 5h: 
Gateway Timeout (HTTP 504)
has caused the Debian Bug report #902152,
regarding python-openstackclient: autopkgtest timed out after 5h: Gateway 
Timeout (HTTP 504)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
902152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902152
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: python-openstackclient
Version: 3.14.2-1
User: [email protected]
Usertags: timeout

Dear maintainer, zigo,

python-openstackclient has an autopkgtest, great. On ci.d.n we are
monitoring tests that take extremely long to run, and today I noticed
python-openstackclient. The last run hit a time out on what seems to be
a non-handled error mode. The was one other time out that I spotted in
the past which seems to be slightly different. Both of them had "Gateway
Timeout (HTTP 504)".

Could you please check and if possible make the autopkgtest robust
against these failure mode to not waste precious time on the
infrastructure? I have no clue, but maybe these are even real failure
modes you want to improve.

Thanks for considering.

Paul

https://ci.debian.net/data/autopkgtest/unstable/amd64/p/python-openstackclient/488862/log.gz

Registering service and endpoints for heat-cfn with type cloudformation
at http://192.168.122.144:8000/v1
Gateway Timeout (HTTP 504)
dpkg: error processing package heat-api-cfn (--configure):
 installed heat-api-cfn package post-installation script subprocess
returned error exit status 1
Setting up neutron-dhcp-agent (2:12.0.2-9) ...
Created symlink
/etc/systemd/system/multi-user.target.wants/neutron-dhcp-agent.service →
/lib/systemd/system/neutron-dhcp-agent.service.
Setting up heat-api (1:10.0.0-3) ...
Registering service and endpoints for heat with type orchestration at
http://192.168.122.144:8004/v1/%(tenant_id)s



https://ci.debian.net/data/autopkgtest/unstable/amd64/p/python-openstackclient/228203/log.gz

Registering service and endpoints for placement with type placement at
http://192.168.122.215:8778
+-------------+----------------------------------+
| Field       | Value                            |
+-------------+----------------------------------+
| description | Placement API                    |
| enabled     | True                             |
| id          | 51b8fe114e1a46a28b7f4ddd402de536 |
| name        | placement                        |
| type        | placement                        |
+-------------+----------------------------------+
+--------------+----------------------------------+
| Field        | Value                            |
+--------------+----------------------------------+
| enabled      | True                             |
| id           | 55fd61553b2c4cec92b688aef53ce5c1 |
| interface    | public                           |
| region       | regionOne                        |
| region_id    | regionOne                        |
| service_id   | 51b8fe114e1a46a28b7f4ddd402de536 |
| service_name | placement                        |
| service_type | placement                        |
| url          | http://192.168.122.215:8778      |
+--------------+----------------------------------+
+--------------+----------------------------------+
| Field        | Value                            |
+--------------+----------------------------------+
| enabled      | True                             |
| id           | 437c4d8d60364b2a9c005a61c596d52a |
| interface    | internal                         |
| region       | regionOne                        |
| region_id    | regionOne                        |
| service_id   | 51b8fe114e1a46a28b7f4ddd402de536 |
| service_name | placement                        |
| service_type | placement                        |
| url          | http://192.168.122.215:8778      |
+--------------+----------------------------------+
+--------------+----------------------------------+
| Field        | Value                            |
+--------------+----------------------------------+
| enabled      | True                             |
| id           | 8a8fbf75275f448e852b304d5aa3a282 |
| interface    | admin                            |
| region       | regionOne                        |
| region_id    | regionOne                        |
| service_id   | 51b8fe114e1a46a28b7f4ddd402de536 |
| service_name | placement                        |
| service_type | placement                        |
| url          | http://192.168.122.215:8778      |
+--------------+----------------------------------+
Created symlink
/etc/systemd/system/multi-user.target.wants/nova-placement-api.service →
/lib/systemd/system/nova-placement-api.service.
Setting up nova-scheduler (2:17.0.0-4) ...
Created symlink
/etc/systemd/system/multi-user.target.wants/nova-scheduler.service →
/lib/systemd/system/nova-scheduler.service.
Setting up nova-consoleauth (2:17.0.0-4) ...
Created symlink
/etc/systemd/system/multi-user.target.wants/nova-consoleauth.service →
/lib/systemd/system/nova-consoleauth.service.
Setting up openstack-proxy-node (0.21) ...
Processing triggers for libc-bin (2.27-3) ...
Processing triggers for systemd (238-4) ...
Processing triggers for dbus (1.12.6-2) ...
+----------------------------------+---------+
| ID                               | Name    |
+----------------------------------+---------+
| 635ff11eb3964a9aa850cc91364a217d | admin   |
| 65832de75b7649ba842f095a966dd4f0 | nova    |
| 6cb95ca20d434e9f85d72b32c804d4d7 | neutron |
| aae4de15d8304ef99ce96dba8aa04b73 | glance  |
| c1fa28998b834d3a9fd7b5a11d7f017a | aodh    |
| f8bff13329694d0e90bc508821e98388 | heat    |
+----------------------------------+---------+
Gateway Timeout (HTTP 504)

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Hi

On 23-06-18 13:01, Paul Gevers wrote:
> Dear all,
> 
> On Fri, 22 Jun 2018 21:04:58 +0200 Paul Gevers <[email protected]> wrote:
>> Could you please check and if possible make the autopkgtest robust
>> against these failure mode to not waste precious time on the
>> infrastructure? I have no clue, but maybe these are even real failure
>> modes you want to improve.
> 
> Before wasting time on this report, this may be an infrastructure issue.
> After this test, multiple tests on the same worker are timing out. So
> fear the worker broke while running this test.

I had to reset the worker. Let's assume this was an infrastructure issue.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to