When will we have access to https://openqa.stg.fedoraproject.org ?
Hello Adam, Since the infra move we do not have anymore access to https://openqa.stg.fedoraproject.org Do you know when it is planned to have access to it ? So unable to have access to openqa tests results for aarch64 and ppc64le. -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org
timing window Rawhide tests and f32 release
Hello Adam, seem there is a timing window problem between Rawhide tests and f32 release as per failure https://openqa.fedoraproject.org/tests/587422 === Cannot find HDD_1 asset hdd/disk_f32_support_5_x86_64.img! === failed Fedora-Rawhide-20200426.n.1 about an hour ago ( 0 ) failed Fedora-Rawhide-20200425.n.0 2 days ago ( 0 ) passed Fedora-Rawhide-20200423.n.0 4 days ago ( 02:00 minutes ) === There is not yet a f32 in https://fr2.rpmfind.net/linux/fedora/linux/releases/ === [DIR] 30/ 2019-04-26 22:58- [DIR] 31/ 2019-10-25 17:05- [DIR] test/ 2020-03-13 21:00- === I experienced similar problem trying createhdds for ppc64le -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org
Re: Random boot failures on openQA.stg for ppc64le f32
On 4/3/20 2:52 PM, Normand wrote: Hello Adam, I identified two tests that randomly failed on openqa.stg.fedoraproject.org (1)&(2) We do not have such problem in our IBM intranet openQA. So I am wondering if difference could be related to configuration/software versions differences of P9 hosts. Our P9 is installed with f31, but no updates since 03/17 === $rpm -qa |grep -iE ^'kernel-header|qemu-kvm|slof' |sort kernel-headers-5.5.8-200.fc31.ppc64le qemu-kvm-4.1.1-1.fc31.ppc64le SLOF-0.1.git20191022-1.fc31.noarch === Oops above if for openQA server, the P9 is: === kernel-headers-5.4.7-200.fc31.ppc64le qemu-kvm-4.1.1-1.fc31.ppc64le SLOF-0.1.git20190114-2.fc31.noarch === From last autoinst-log.txt and serial0.txt it seems you have same slof older kernel and specific qemu. Do you have other specific changes ? === Linux 5.3.16-300.fc31.ppc64le qemu-4.2.0-1.fc31.infra SLOF release 20191022 === (1) server flavor install_default_upload, failed only one time (last compose 20200402) https://openqa.stg.fedoraproject.org/tests/794105#step/_console_wait_login/8 (2) server flavor upgrade_2_minimal, failed multiple times https://openqa.stg.fedoraproject.org/tests/794304#step/_console_wait_login/22 https://openqa.stg.fedoraproject.org/tests/794304#next_previous -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org
Random boot failures on openQA.stg for ppc64le f32
Hello Adam, I identified two tests that randomly failed on openqa.stg.fedoraproject.org (1)&(2) We do not have such problem in our IBM intranet openQA. So I am wondering if difference could be related to configuration/software versions differences of P9 hosts. Our P9 is installed with f31, but no updates since 03/17 === $rpm -qa |grep -iE ^'kernel-header|qemu-kvm|slof' |sort kernel-headers-5.5.8-200.fc31.ppc64le qemu-kvm-4.1.1-1.fc31.ppc64le SLOF-0.1.git20191022-1.fc31.noarch === From last autoinst-log.txt and serial0.txt it seems you have same slof older kernel and specific qemu. Do you have other specific changes ? === Linux 5.3.16-300.fc31.ppc64le qemu-4.2.0-1.fc31.infra SLOF release 20191022 === (1) server flavor install_default_upload, failed only one time (last compose 20200402) https://openqa.stg.fedoraproject.org/tests/794105#step/_console_wait_login/8 (2) server flavor upgrade_2_minimal, failed multiple times https://openqa.stg.fedoraproject.org/tests/794304#step/_console_wait_login/22 https://openqa.stg.fedoraproject.org/tests/794304#next_previous -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org
About "Disabling cgroup usage" when starting openQA job
Hello Adam, Do you have lines with "Disabling cgroup usage ..." in the journalctl of workers host ? I noticed that since December 2019 after a dnf distro-sync seems to be related to an upstream change https://github.com/os-autoinst/openQA/blame/master/lib/OpenQA/Worker/Engines/isotovideo.pm#L320 === journalctl extract: worker[4090]: [info] +++ setup notes +++ worker[4090]: [info] Start time: 2020-02-13 12:38:28 worker[4090]: [info] Running on abanb.tlslab.ibm.com:3 (Linux 5.4.8-200.fc31.ppc64le #1 SMP Mon Jan 6 16:29:22 UTC 2020 ppc64le) worker[4090]: [info] Preparing cgroup to start isotovideo worker[4090]: [warn] Disabling cgroup usage because cgroup creation failed: mkdir /sys/fs/cgroup/systemd: Permission denied at /usr/share/perl5/vendor_perl/Mojo/File.pm line 87. worker[4090]: [info] You can define a custom slice with OPENQA_CGROUP_SLICE or indicating the base mount with MOJO_CGROUP_FS. worker[4090]: [info] Starting isotovideo container === -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org
What is "FuturWarning" while calling fifloader.py ?
Hello Adam, I am starting to use locally the fifloader.py and templates.fif.json Is the "FuturWarning" message something to be worked on ? Is it something you also have in your openQA servers ? === $./fifloader.py -w --filename xx.upstream templates.fif.json /usr/lib/python3.7/site-packages/jsonschema/_validators.py:200: FutureWarning: Possible nested set at position 7 not re.search(patrn, instance) Input template data is valid Generated template data is valid === -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org
Re: Why so many errors on stg for PowerPC for last composes ?
On 1/14/20 5:43 PM, Adam Williamson wrote: On Tue, 2020-01-14 at 11:58 +0100, Normand wrote: Hello Adam, I am surprised by the number of errors for PowerPC on openqa stg since 20200110 compose: https://openqa.stg.fedoraproject.org/group_overview/3 Is there some pending changes on those machines ? We do not have such errors in our local openqa server at IBM for same compose versions. Hi Michel! Long story short, it's: https://bugzilla.redhat.com/show_bug.cgi?id=1784961 I took out the workaround we had in the templates to set the machine to pseries-4.0 because I thought we didn't need it any more, but I've just figured out that's what's causing the problems. We're hitting the behaviour described in that bug, where the kernel checks something to do with xive, then triggers a reboot. That breaks all tests where we want to pass in kernel params, because when the reboot happens, our params get lost (our test code doesn't know to enter them again, as it's not something we envisaged when writing the tests). Kevin was trying to do a backport of the qemu fix, if he's succeeded with that I'll try it out, otherwise I'll put the pseries-4.0 workaround back in. Sorry for the inconvenience! Thanks for the details, I understand so the difference. BTW, did you notice I enabled update tests for ppc64le on staging? :) Thanks :), I missed that, I will look at tests results. -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org
still running job started 4 mont ago on
openqa.stg.fedoraproject.org has a strangely pending job that started 4 month ago ! https://openqa.stg.fedoraproject.org/tests === Medium: BuildFedora-Rawhide-20190928.n.2 of fedora-Rawhide-Server-dvd-iso.ppc64le Test: realmd_join_sssd@ppc64le (restarted) Progress: 100 % Started: 4 months ago === looking at related job, it is in 'uploading' state with infinit UI refresh. https://openqa.stg.fedoraproject.org/tests/635112 I assume it should be manually killed. -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org
Why so many errors on stg for PowerPC for last composes ?
Hello Adam, I am surprised by the number of errors for PowerPC on openqa stg since 20200110 compose: https://openqa.stg.fedoraproject.org/group_overview/3 Is there some pending changes on those machines ? We do not have such errors in our local openqa server at IBM for same compose versions. -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org
Re: git clone ... Permission denied
On 17/04/2018 15:15, Kamil Paral wrote: On Tue, Apr 17, 2018 at 2:36 PM, Normand <mailto:norm...@linux.vnet.ibm.com>> wrote: Since today, I have a problem accessing the openqa git tree from pagure. I do not understand what I am doing wrong. any suggestion ? === $git clone -v https://pagure.io/fedora-qa/os-autoinst-distri-fedora.git <https://pagure.io/fedora-qa/os-autoinst-distri-fedora.git> Cloning into 'os-autoinst-distri-fedora'... fatal: unable to access 'https://pagure.io/fedora-qa/os-autoinst-distri-fedora.git/ <https://pagure.io/fedora-qa/os-autoinst-distri-fedora.git/>': Failed to connect to pagure.io <http://pagure.io> port 443: Permission denied === Probably just a temporary pagure issue. Try again later. Btw, it works for me at the moment. Thank you Kamil for the answer, The day after it worked magically :) -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
git clone ... Permission denied
Since today, I have a problem accessing the openqa git tree from pagure. I do not understand what I am doing wrong. any suggestion ? === $git clone -v https://pagure.io/fedora-qa/os-autoinst-distri-fedora.git Cloning into 'os-autoinst-distri-fedora'... fatal: unable to access 'https://pagure.io/fedora-qa/os-autoinst-distri-fedora.git/': Failed to connect to pagure.io port 443: Permission denied === -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Rawhide compose 20180217 missing for PowerPC on openqa.stg
Hello Adam, Was there a configuration change on stg ? There is no schedule of openQA tests for PowerPC related to last Rawhide snapshots (20180217, 20180218) ? I verified that those two composes were scheduled in our own internal openQA server (with many tests failures because of fuzzy images) (1) https://openqa.stg.fedoraproject.org/group_overview/3 -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Re: missing f27 images from createhdds for PowerPC on openqa.stg
On 27/11/2017 18:01, Adam Williamson wrote: On Mon, 2017-11-27 at 09:32 +0100, Normand wrote: Hello Adam, As per openQA output failure (1) it seems the createhdds was not executed for PowerPC on openqa.stg. I do not know how it is done for x86-64, but we would probably need to do something similar for PowerPC. We already do. If the image isn't there, it means creation of it is failing and we need to figure out why... I do not know how I could help to investigate that. But what I already verified is that createhdds is correctly generating the f27 images the local Power8 host we are using for our openQA tests. -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
missing f27 images from createhdds for PowerPC on openqa.stg
Hello Adam, As per openQA output failure (1) it seems the createhdds was not executed for PowerPC on openqa.stg. I do not know how it is done for x86-64, but we would probably need to do something similar for PowerPC. (1) https://openqa.stg.fedoraproject.org/tests/210974/file/autoinst-log.txt === end time: 2017-11-26 14:05:25 result: setup failure: Cannot find HDD_1 asset hdd/disk_f27_minimal_2_ppc64le.img! === -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
what openQA packages versions on openqa.stg.fedoraproject.org
Hello Adam, What are the currently running openQA rpm versions on openqa.stg.fedoraproject.org ? I saw in (1) that this version is sorting the successive runs with most recents on top, which is an option I like. But we do not have such behaviour on our openQA server running f26 fedora with following openQA versions: === $rpm -qa |grep -i openqa |sort openqa-4.4-49.20170409gitfead7af.fc26.noarch openqa-client-4.4-49.20170409gitfead7af.fc26.noarch openqa-common-4.4-49.20170409gitfead7af.fc26.noarch openqa-httpd-4.4-49.20170409gitfead7af.fc26.noarch openqa-plugin-fedmsg-4.4-49.20170409gitfead7af.fc26.noarch openqa-worker-4.4-49.20170409gitfead7af.fc26.noarch === (1) https://openqa.stg.fedoraproject.org/group_overview/3 -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Could we have a git branch that map openQA source used by openqa.stg ?
Hello Adam,
I discovered this morning that the openQA running on openqa.stg has some
hack code (1) but this change is not visible in master or staging branch
on pagure.
So I am not able to identify if any other changes are present on the
machine.
Would it be possible to have a remote read access to the openQA source
code used by openqa.stg to help for test failure investigation ?
(1)
https://openqa.stg.fedoraproject.org/tests/156101/modules/server_cockpit_default/steps/1/src
===
sub run {
my $self = shift;
# HACK HACK HACK
assert_script_run "setenforce 0";
# check cockpit appears to be enabled and running and firewall is
setup
assert_script_run 'systemctl is-enabled cockpit.socket';
===
--
Michel Normand
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
OpenQA templates with hardcoded nfs address
I am looking at the nfs tests already defined in OpenQA templates file
for fedora (1)
I would like to try those tests locally in a PowerPC environment,
so plan to modify templates to replace the hardcoded value
by a variable to be set by fedora-openqa-schedule.
Is it something that would be acceptable ?
How is set today the nfs server at 10.0.2.110 versus the
iso file retrieved via https from compose ?
What is the exported directories of this nfs server ?
(1)
https://phab.qa.fedoraproject.org/diffusion/OPENQATESTS/browse/master/templates
===
$grep -Hn 'nfs:' openqa_fedora.upstream/templates
openqa_fedora.upstream/templates:1737:{ key =>
"REPOSITORY_GRAPHICAL", value => "nfs:10.0.2.110:/repo" },
openqa_fedora.upstream/templates:1753:{ key =>
"REPOSITORY_VARIATION", value => "nfs:10.0.2.110:/repo" },
openqa_fedora.upstream/templates:2321:{ key =>
"GRUB", value =>
"inst.ks=nfs:10.0.2.110:/export/root-user-crypted-net.ks" },
openqa_fedora.upstream/templates:2333:{ key =>
"GRUB", value => "inst.stage2=nfs:nfsvers=4:10.0.2.110:/repo" },
===
--
Michel Normand
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
How to handle patches for openqa_fedora in Pagure ?
Hello Adam, I saw you copied the git trees of openqa from Bitbucket to Pagure as per ticket T863 (1) What is the way to submit patches on openqa_fedora in Pagure ? Are there fork and pull-request functionality in Pagure ? or do I have to handle in another place my changes and submit patches by email ? (1) https://phab.qa.fedoraproject.org/T863 -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
request for blockerbugs app to specify primary or secondary
Hi there, I used the blockerbugs application at https://qa.fedoraproject.org/blockerbugs/propose_bug but found that this is restricted to the primary arch releases. Could it be possible to have it improved to support secondary arch releases (ppc64, s390, ...) ? -- Michel Normand ___ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
