#2066 xmlrpc errors on backend when working with the resalloc tickets
Closed: MIGRATED a year ago by nikromen. Opened 2 years ago by praiskup.

[2022-02-01 09:30:13,881][  INFO][PID:2652840] Trying to allocate VM
[2022-02-01 09:30:18,984][ ERROR][PID:2652840] Unexpected exception (in /usr/lib64/python3.10/xmlrpc/client.py:662)
[2022-02-01 09:30:18,986][WARNING][PID:2652840] Switching not-finished job state to 'failed'

This makes the build fail, without an obvious user error. We should catch some
exeception there and try again, I'm sure.


This is actually failing the builds, too:

[2022-03-30 08:38:33,935][  INFO][PID:1494886] Releasing VM back to pool
[2022-03-30 08:38:39,191][ ERROR][PID:1494886] Unexpected exception (in /usr/lib64/python3.10/xmlrpc/client.py:662)
[2022-03-30 08:38:39,200][  INFO][PID:1494886] Releasing VM back to pool
[2022-03-30 08:38:44,176][WARNING][PID:1494886] Switching not-finished job state to 'failed'
[2022-03-30 08:38:44,176][  INFO][PID:1494886] Worker failed build, took 2186.214994430542

Metadata Update from @praiskup:
- Issue priority set to: High

2 years ago

Metadata Update from @nikromen:
- Issue close_status updated to: MIGRATED
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata