action #56447
closed
- Copied from action #54902: openQA on osd fails at "incomplete" status when uploading, "502 response: Proxy Error" added
- Copied from deleted (action #54902: openQA on osd fails at "incomplete" status when uploading, "502 response: Proxy Error")
- Related to action #55328: job is considered incomplete by openQA but worker still pushes updates so that "job is not considered dead" added
- Status changed from New to Workable
- Assignee set to kraih
- Priority changed from Normal to High
- Target version set to Current Sprint
- Status changed from Workable to New
- Assignee deleted (
kraih)
- Target version deleted (
Current Sprint)
sorry, I am all wrong. the PR is not yet deployed.
- Subject changed from openQA on osd fails with empty logs to openqaworker-arm-2 is out-of-space on /was: openQA on osd fails with empty logs
- Status changed from New to In Progress
- Assignee set to okurz
- Priority changed from High to Urgent
- Target version set to Current Sprint
- Related to action #41882: all arm worker die after some time added
- Related to action #54128: [tools] openqaworker-arm-3 is broken added
I stopped salt-minion and openqa-worker.target. It looks like /var/lib/openqa/pool is on the same partition as / . I don't know what changed or how it looked like in before. Probably pool should be on NVME as well. systemctl cat openqa_nvme_prepare.service creates the pool but does not seem to do anything with it. This looks similar to #53261 only about "pool", not "cache". Could it be we deleted the "pool" symlink by mistake and should use a bind mount as well? Probably to be done properly with salt.
- change to bind mount for all,
- add that to salt
- add -3 the same and monitor all three
Done first two with https://gitlab.suse.de/openqa/salt-states-openqa/merge_requests/160
- Status changed from In Progress to Resolved
Also available in: Atom
PDF