action #154816
closed
"Mojo::Reactor::Poll: Timer failed: Invalid characters in X-API-Key" when starting registry.suse.de/home/okurz/bci/15.5/containers_backports_updates/suse/openqa-single-instance:latest
Added by hsehic 3 months ago.
Updated 3 months ago.
Description
Observation¶
Error (full log attached):
Mojo::Reactor::Poll: Timer failed: Invalid characters in X-API-Key header at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/Headers.pm line 38.
[...]
[error] Stopping because a critical error occurred.
[error] Another error occurred when trying to stop gracefully due to an error
[error] Trying to kill ourself forcefully now
Steps to reproduce¶
Host OS SLEMicro 5.5 (GM) on kvm
transactional-update
podman pull --tls-verify=false registry.suse.de/home/okurz/bci/15.5/containers_backports_updates/suse/openqa-single-instance:latest
podman run <container>
Files
- Tags set to reactive work
- Project changed from 190 to openQA Project
- Subject changed from openQA container deployment broken to "Mojo::Reactor::Poll: Timer failed: Invalid characters in X-API-Key" when starting registry.suse.de/home/okurz/bci/15.5/containers_backports_updates/suse/openqa-single-instance:latest
- Description updated (diff)
- Category set to Regressions/Crashes
- Assignee deleted (
okurz)
- Target version set to Ready
I could not reproduce the problem with
podman run --rm -it registry.suse.de/home/okurz/bci/15.5/containers_backports_updates/suse/openqa-single-instance:latest
on Leap 15.5
Can you try that command line to run the container in interactive mode with a proper pseudo-tty configured if that also reproduces?
okurz wrote in #note-1:
I could not reproduce the problem with
podman run --rm -it registry.suse.de/home/okurz/bci/15.5/containers_backports_updates/suse/openqa-single-instance:latest
on Leap 15.5
Why are you trying it on Leap when the bugreport and the steps to reproduce explicitly mention SLEMicro?
Why are you trying it on Leap when the bugreport and the steps to reproduce explicitly mention SLEMicro?
The error looks to me like the config file is broken, like invalid characters. Mojo is inside the container and the host should be irrelevant in this case.
My suggestion would be to check your ~/.config/openqa or $OPENQA_CONFIG respectively.
hsehic wrote in #note-2:
Why are you trying it on Leap when the bugreport and the steps to reproduce explicitly mention SLEMicro?
Because I have a Leap 15.5 system directly available but not SLEMicro
- Category changed from Regressions/Crashes to Support
- Assignee deleted (
okurz)
- Priority changed from High to Normal
I know downloaded SLE Micro from https://download.suse.de/install/ as maybe you think it's specific to that OS but same observation there, no problem observed. Please provide more details how to reproduce the problem otherwise we can't help.
- Status changed from New to Resolved
okurz wrote in #note-6:
I know downloaded SLE Micro from https://download.suse.de/install/ as maybe you think it's specific to that OS but same observation there, no problem observed. Please provide more details how to reproduce the problem otherwise we can't help.
After updateting container image
*evergreen131:~ # podman pull --tls-verify=false registry.suse.de/home/okurz/bci/15.5/containers_backports_updates/suse/openqa-single-instance
Trying to pull registry.suse.de/home/okurz/bci/15.5/containers_backports_updates/suse/openqa-single-instance:latest...
Getting image source signatures
Checking if image destination supports signatures
Copying blob 6ef40564a417 done |
Copying blob 34764562482b done |
Copying config 553bd1e574 done |
Writing manifest to image destination
Storing signatures
553bd1e574958682c01209cf403142e5eeb7dae926e8a63dbdb035182b9e9582
*
openqa is now starting without any issues.
Issue can be closed.
Also available in: Atom
PDF