action #62108
closed
auto_review:"Can.t fcntl.*Operation not permitted at .*virtio_terminal.pm" test incompletes
Added by okurz over 4 years ago.
Updated about 4 years ago.
Category:
Regressions/Crashes
Description
Observation¶
In https://openqa.suse.de/tests/3782734
/usr/lib/os-autoinst/consoles/vnc_base.pm:62:{
"connect_timeout" => 3,
"hostname" => "localhost",
"port" => 6007
}
[2020-01-14T03:06:11.810 CET] [debug] <<< consoles::virtio_terminal::open_pipe(pipe_prefix="/var/lib/openqa/pool/17/virtio_console")
[2020-01-14T03:06:11.810 CET] [info] ::: consoles::virtio_terminal::open_pipe: Set PIPE_SZ from 65536 to 1048576
[2020-01-14T03:06:11.810 CET] [info] ::: consoles::virtio_terminal::open_pipe: Set PIPE_SZ from 65536 to 1048576
[2020-01-14T03:06:11.811 CET] [debug] <<< consoles::virtio_terminal::open_pipe(pipe_prefix="/var/lib/openqa/pool/17/virtio_console1")
[2020-01-14T03:06:11.811 CET] [info] ::: consoles::virtio_terminal::open_pipe: Set PIPE_SZ from 65536 to 1048576
[2020-01-14T03:06:11.813 CET] [debug] Backend process died, backend errors are reported below in the following lines:
Can't fcntl($fh, '1031', '1048576'): Operation not permitted at /usr/lib/os-autoinst/consoles/virtio_terminal.pm line 147
- Assignee set to cfconrad
- Priority changed from Normal to High
@cfconrad this sounds like something for you :)
Oh, no, permissions on virtio strikes again :).
I remember somebody checked AppArmor profile before, but couldn't it be caused by it?
BTW wicked has VIRTIO_CONSOLE_NUM=2 and thus virtio_console1.log (IMHO not a commonly used setup).
Hmmm very strange. Maybe the error message isn't really helpful here.
We can see that it worked /var/lib/openqa/pool/17/virtio_console but just 1ms later it failed on /var/lib/openqa/pool/17/virtio_console1.
And during the same job it worked 9 times successful, but then it failed.
- Related to action #62417: os-autoinst occasionally crashing on startup added
- Status changed from New to Resolved
- Related to deleted (action #62417: os-autoinst occasionally crashing on startup)
- Status changed from Resolved to Workable
yes, PR was merged but unfortunately the problem not fixed.
E.g. see https://openqa.suse.de/tests/3860547/file/autoinst-log.txt which is running a current "4.6.1580718127.98503bd5" :
Can't fcntl($fh, '1031', '1048576'): Operation not permitted at /usr/lib/os-autoinst/consoles/virtio_terminal.pm line 128
My first assumption is, that it's not working cause "autodie" has lexical scope: https://perldoc.perl.org/autodie.html
The autodie pragma has lexical scope, meaning that functions and subroutines altered with autodie will only change their behaviour until the end of the enclosing block, file, or eval.
So my latest change, when I moved the fcntl() calls in separate methods for mocking it, it broke it :(
But before I will provide something, okurz offered me a testsetup on openqaworker13 which I will use for verification! thx!
- Blocks action #59858: "Migrate to file failed, it has been running for more than 240 at /usr/lib/os-autoinst/backend/qemu.pm line 260." broken NVMe on openqaworker13, jobs incomplete trying to save snapshots added
- Status changed from Workable to In Progress
PR was merged. Do you have any further points you want to follow up with or do you consider this issue done? Do you still need openqaworker13?
- Status changed from In Progress to Resolved
Thx for asking,
from my side I consider it as done and don't need openqaworker13 anymore.
Also available in: Atom
PDF