action #47126
closed[functional][y] create_hdd_tumbleweed fails in welcome (accessing download.oo)
Added by coolo about 5 years ago. Updated about 5 years ago.
0%
Description
I don't think this is a valid test
Observation¶
openQA test in scenario opensuse-Tumbleweed-NET-x86_64-create_hdd_tumbleweed@64bit fails in
welcome
Test suite description¶
Reproducible¶
Fails since (at least) Build 20190202
Expected result¶
Last good: 20190201 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by coolo about 5 years ago
- Subject changed from [tw] create_hdd_tumbleweed fails in welcome (accessing download.oo) to [functional][y] create_hdd_tumbleweed fails in welcome (accessing download.oo)
I need help with this one - according to https://www.forbes.com/sites/jasonevangelho/2019/01/31/introducing-the-linux-community-challenge-2-opensuse-tumbleweed/#70e7bf5b4c6b the probem is seen in the wild as well, but we need more details
Updated by okurz about 5 years ago
[06/02/2019 11:20:32] <coolo> okurz: I need help with https://openqa.opensuse.org/tests/848003#next_previous - no idea where it's pulling it from
[06/02/2019 11:21:41] <okurz> coolo: yeah, that one … I think it's from DimStar.
[06/02/2019 11:22:44] <okurz> coolo: maybe https://openqa.opensuse.org/tests/848003#step/bootloader/10 is doing something where it pulls from?
[06/02/2019 11:24:12] <coolo> https://openqa.opensuse.org/tests/840437#comments is the only hint I got
[06/02/2019 11:24:20] <okurz> coolo: I suggest you create a ticket with "[functional][y]" and ping riafarov as he knows better about "use published repos or not"
[06/02/2019 11:25:22] <okurz> coolo: ah, right. I remember: The idea of the test suite is to create an installation from the last published snapshot so that we can do the upgrade from last_published to current snapshot_under_test as a test
[06/02/2019 11:26:01] <okurz> coolo: I added a test suite description now
[06/02/2019 11:26:32] <okurz> coolo: I guess it can never work reliably this way because it uses the wrong ISO
Updated by okurz about 5 years ago
- Due date set to 2019-03-12
- Target version set to Milestone 23
Updated by okurz about 5 years ago
- Status changed from New to Feedback
- Assignee set to okurz
@coolo do you mean https://www.forbes.com/sites/jasonevangelho/2019/02/02/my-first-24-hours-with-opensuse-tumbleweed/#52bbb6ed6432 mentioning "wrong digest"? Yes, more or less a known issue depending on the situation: The ISO must match the repos so for Tumbleweed you have to be quick to have a useable ISO which is matching the latest online state unless you do not have network which most likely will not show the problem because the online repos are not probed.
Maybe we can just schedule with ISO_URL=http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Current.iso and overwrite with ISO= to be empty. Let's try that:
openqa_clone_job_o3 --skip-chained-deps 846147 _GROUP=0 TEST=create_hdd_tumbleweed_with_downloaded_iso_poo47126 ISO= ISO_URL=http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Current.iso
Created job #848081: opensuse-Tumbleweed-NET-x86_64-Build20190202-create_hdd_tumbleweed@64bit -> https://openqa.opensuse.org/t848081
Updated by riafarov about 5 years ago
- Status changed from Feedback to New
- Assignee deleted (
okurz)
okurz wrote:
@coolo do you mean https://www.forbes.com/sites/jasonevangelho/2019/02/02/my-first-24-hours-with-opensuse-tumbleweed/#52bbb6ed6432 mentioning "wrong digest"? Yes, more or less a known issue depending on the situation: The ISO must match the repos so for Tumbleweed you have to be quick to have a useable ISO which is matching the latest online state unless you do not have network which most likely will not show the problem because the online repos are not probed.
Maybe we can just schedule with ISO_URL=http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Current.iso and overwrite with
ISO=to be empty. Let's try that:openqa_clone_job_o3 --skip-chained-deps 846147 _GROUP=0 TEST=create_hdd_tumbleweed_with_downloaded_iso_poo47126 ISO= ISO_URL=http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Current.isoCreated job #848081: opensuse-Tumbleweed-NET-x86_64-Build20190202-create_hdd_tumbleweed@64bit -> https://openqa.opensuse.org/t848081
Nice try, but didn't work =(
Updated by riafarov about 5 years ago
Is actually a bug, and I was able to reproduce it with published Net installer: https://bugzilla.suse.com/show_bug.cgi?id=1124467
Updated by okurz about 5 years ago
- Status changed from New to Feedback
- Assignee set to okurz
so why keep the ticket in new? I will track the bug as well and try again what is wrong with my iso download. That should work nevertheless, at least to reproduce the same error more easily. @riafarov feel free to track this ticket as "Blocked" on yourself though.
Updated by okurz about 5 years ago
- Status changed from Feedback to Blocked
- Assignee changed from okurz to riafarov
@riafarov assigning to you as "Blocked" as you track the bug already. I don't know what's going on exactly. I thought that would be a critical issue that would prevent any further Tumbleweed snapshots to be published but apparently that is not the case. Regarding the test scheduling parameters I tried earlier I did not find time to follow on so I will leave that aside. If you think there is nothing more to be done from our side you can of course also resolve this ticket.
Updated by riafarov about 5 years ago
- Status changed from Blocked to Resolved
okurz wrote:
@riafarov assigning to you as "Blocked" as you track the bug already. I don't know what's going on exactly. I thought that would be a critical issue that would prevent any further Tumbleweed snapshots to be published but apparently that is not the case. Regarding the test scheduling parameters I tried earlier I did not find time to follow on so I will leave that aside. If you think there is nothing more to be done from our side you can of course also resolve this ticket.
@okurz, as our investigation has shown I don't see that we need to do anything here, so to be honest I would resolve this ticket. As for the scenario itself, we might consider using published NET installer.