action #12350
closed
[tools]version of os-autoinst on malbec+overdrive2 should be same as other workers (using salt) (was: looks like old version)
Added by okurz over 8 years ago.
Updated over 7 years ago.
Estimated time:
(Total: 0.00 h)
Description
observation¶
see logfile from https://openqa.suse.de/tests/445879/file/autoinst-log.txt
the warning
Subroutine main::diag redefined at /var/lib/openqa/share/tests/sle/products/sle/main.pm line 3.
main::BEGIN() called at /var/lib/openqa/share/tests/sle/products/sle/main.pm line 3
eval {...} called at /var/lib/openqa/share/tests/sle/products/sle/main.pm line 3
require /var/lib/openqa/share/tests/sle/products/sle/main.pm called at /usr/bin/isotovideo line 121
should not appear unless an old version of os-autoinst is installed
problem¶
It might have an effect why https://openqa.suse.de/tests/445879 failed.
suggestion¶
- someone with access to malbec should check if the package is on the same version as other workers
- maybe update salt config or something.
- Subject changed from os-autoinst on malbec looks like old version to os-autoinst on malbec and overdrive2 looks like old version
- Status changed from New to Feedback
- % Done changed from 0 to 100
Deployed malbec and overdrive2 and rescheduled the mentioned jobs and any other job I think could have been impacted.
- Status changed from Feedback to In Progress
- Priority changed from High to Low
works good, see https://openqa.suse.de/tests/446605.
Like to track this cause we don't have the same tools to orchestrate overdrive2 and malbec so I guess this problem will persist. Let's see if someone will provide salt for SLE12 GA ;-) or we have some "deployment checklist" where these exceptions are listed.
still happening (or again): overdrive still have an old version of os-autoinst causing problems: mgriessmeier assumes "Can't use string ("0") as a HASH ref while "strict refs" in use at /usr/lib/os-autoinst/testapi.pm line 943." is caused by this
- Priority changed from Low to High
there are still some jobs failing because of this issue, and since they got retriggered automatically, aarch64 testing takes a lot of time
- Status changed from In Progress to Resolved
I love how high prio issues are ignored for months
- Status changed from Resolved to In Progress
seriously, how does it help to just set a ticket to resolved?
AFAICS neither malbec nor overdrive are part of salt recipes nor are any specific instructions mentioned on https://wiki.microfocus.net/index.php/OpenQA how to handle these so not resolved.
- Project changed from openQA Project (public) to openQA Tests (public)
- Category set to Infrastructure
you mean because leaving it open for 3 months in high priority worked so well?
that is not a real and honest question buuut I will answer it anyway: We will try to improve in the future and I am working on it. First step was to create a new category "Infrastructure" in "openQA tests" repo because it has nothing to do with openQA feature development but is "SUSE specific". I will regularly review progress tickets and see about their state and try to plan accordingly. Also SUSE QA is investing more in working on this backlog based on the real priority and I am also working on this one.
- Subject changed from os-autoinst on malbec and overdrive2 looks like old version to version of os-autoinst on malbec+overdrive2 should be same as other workers (using salt) (was: looks like old version)
- Related to action #15396: malbec unusable (see parent ticket) added
ping working on overdrive?
- Target version set to Milestone 6
- Related to action #15492: Upgrade ppc64le workers to QEMU 2.6.*, i.e. current Leap or "Invalid parameter 'logfile'" added
- Related to action #16320: Random timeouts while waiting for serial output when using the virtio backend added
In progress but waiting for an xgene as a proper ARM production worker - overdrive2 will then be repurposed (probably for QAM only)
- Subject changed from version of os-autoinst on malbec+overdrive2 should be same as other workers (using salt) (was: looks like old version) to [tools]version of os-autoinst on malbec+overdrive2 should be same as other workers (using salt) (was: looks like old version)
Malbec done
Overdrive2 blocked, waiting for a fix for santi
but it's salted now - and is deployed with latest versions
- Status changed from In Progress to Resolved
Also available in: Atom
PDF