Actions
action #39359
closed[functional][y][sporadic] rsync.pl Can't locate object method "is_status_class" via package "Mojo::Message::Response" at /opt/openqa-scripts/rsync.pl line 1005.
Start date:
2018-08-09
Due date:
% Done:
0%
Estimated time:
Difficulty:
Description
Observation¶
SLE15SP1 build 19.3 was triggered for aarch64 but not for the other archs. That triggering seemed to have died in the middle of "isos post" execution. We can see an error message in the middle of the output of the isos post call:
'deprioritizing or cancelling currently running jobs (if any), setting '_DEPRIORITIZEBUILD'
{
"ARCH" : "ppc64le",
"BUILD" : "19.3",
"BUILD_SLE" : "19.3",
"DISTRI" : "SLE",
"FLAVOR" : "Installer-DVD",
"ISO" : "SLE-15-SP1-Installer-DVD-ppc64le-Build19.3-Media1.iso",
"MIRROR_FTP" : "ftp://openqa.suse.de/SLE-15-SP1-Installer-DVD-ppc64le-Build19.3-Media1",
"MIRROR_HTTP" : "http://openqa.suse.de/assets/repo/SLE-15-SP1-Installer-DVD-ppc64le-Build19.3-Media1",
"MIRROR_NFS" : "nfs://openqa.suse.de/var/lib/openqa/share/factory/repo/SLE-15-SP1-Installer-DVD-ppc64le-Build19.3-Media1",
"MIRROR_SMB" : "smb://openqa.suse.de/inst/SLE-15-SP1-Installer-DVD-ppc64le-Build19.3-Media1",
"REPO_0" : "SLE-15-SP1-Installer-DVD-ppc64le-Build19.3-Media1",
"REPO_10" : "SLE-15-SP1-Module-Basesystem-POOL-ppc64le-Build19.3-Media2",
"REPO_11" : "SLE-15-SP1-Module-Basesystem-POOL-ppc64le-Build19.3-Media3",
"REPO_12" : "SLE-15-SP1-Module-Desktop-Applications-POOL-pperror scheduling SLE-15-SP1-Installer-DVD-ppc64le-Build19.3-Media1.iso
500 Internal Server Error
{ error_status => 500 }Can't locate object method "is_status_class" via package "Mojo::Message::Response" at /opt/openqa-scripts/rsync.pl line 1005.
c64le-Build19.3-Media1",
"REPO_13" : "SLE-15-SP1-Module-Development-Tools-POOL-ppc64le-Build19.3-Media1",
…
}
That is in https://gitlab.suse.de/openqa/scripts/blob/master/rsync.pl#L1005 when conducting a POST request to the "api/v1/isos" route.
Seems like this is the first time occurence, probably linked to recent changes in openQA.
Impact¶
As the changes happen in rsync.pl and are hidden in log files they should be handled with higher prio as otherwise we have many people with question marks in their face why there is no new build tested.
Actions