Actions
action #156754
closed"DBIx::Class::Row::update(): Can't update OpenQA::Schema::Result::JobLocks=HASH(0x55b77ea45e28): row not found at /usr/share/openqa/script/../lib/OpenQA/Resource/Locks.pm line 139" size:S
Start date:
2024-02-12
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Observation¶
As seen in #155326
OSD journal logs show some DBIx error:
Feb 12 00:38:12 openqa openqa[11635]: [error] [ztQJ1_pAsMiS] DBIx::Class::Row::update(): Can't update OpenQA::Schema::Result::JobLocks=HASH(0x55b77ea45e28): row not found at /usr/share/openqa/script/../lib/OpenQA/Resource/Locks.pm line 139
Suggestions¶
- Specifically look into the only error in the log excerpt "[ztQJ1_pAsMiS] DBIx::Class::Row::update(): Can't update OpenQA::Schema::Result::JobLocks=HASH(0x55b77ea45e28): row not found at /usr/share/openqa/script/../lib/OpenQA/Resource/Locks.pm line 139"
Updated by okurz about 1 year ago
- Copied from action #155326: [alert] "HTTP Response" alert fired shortly on 2024-02-12 and 2024-03-04 size:M added
Updated by okurz about 1 year ago
- Related to action #106613: o3 logreports DBIx::Class::Row::update(): Can't update OpenQA::Schema::Result::JobLocks row not found added
Updated by okurz about 1 year ago
- Target version changed from Tools - Next to Ready
Updated by mkittler about 1 year ago
- Status changed from New to In Progress
- Assignee set to mkittler
Updated by mkittler about 1 year ago
- Status changed from In Progress to Feedback
Updated by okurz about 1 year ago
- Subject changed from "DBIx::Class::Row::update(): Can't update OpenQA::Schema::Result::JobLocks=HASH(0x55b77ea45e28): row not found at /usr/share/openqa/script/../lib/OpenQA/Resource/Locks.pm line 139" to "DBIx::Class::Row::update(): Can't update OpenQA::Schema::Result::JobLocks=HASH(0x55b77ea45e28): row not found at /usr/share/openqa/script/../lib/OpenQA/Resource/Locks.pm line 139" size:S
Updated by mkittler about 1 year ago
- Status changed from Feedback to Resolved
The PR has been merged. So this exact error shouldn't happen anymore judging by my local tests with DBIx. Not sure how to provoke this in production in a meaningful way so I'm considering this resolved.
Actions