action #37105
closedsetup openQA
Description
update job group for new release: https://openqa.opensuse.org/parent_group_overview/3
adjust description and link of the parent group if needed
Dump the templates of the previous distribution, change version and import again. E.g.
script/dump_templates --host https://openqa.opensuse.org --group "openSUSE Leap 42.3" --full > leap
Same with staging projects. Afterwards review and adjust accordingly
Add BETA=1
The staging group may need to be renamed an re-created in order to preserve old results and allow for build numbers to repeat
add upgrade tests from previous release
Updated by lnussel almost 6 years ago
- Copied from action #24746: setup openQA added
Updated by lnussel almost 6 years ago
- Due date changed from 2018-08-09 to 2018-06-29
- Category changed from QA to QA
- Assignee set to okurz
Updated by okurz almost 6 years ago
- Status changed from New to In Progress
I am proposing to rename the job groups with the name component "openSUSE Leap 15.0" to just "openSUSE Leap" as by now openQA has better support for job groups covering multiple versions with proper sorting, etc.
https://gitlab.suse.de/openqa/scripts/merge_requests/214 for the sync+trigger changes
For this I would change the existing current Leap 15.0 test schedule in the job groups with the corresponding 15.1 one.
Updated by lnussel almost 6 years ago
I don't mind if you think it is the better setup please go ahead
Updated by okurz almost 6 years ago
The mentioned merge request is ready but we would like to test against a build of the product before merging the MR and calling this done. So far it seems no builds showed up, e.g. in https://build.opensuse.org/project/show/openSUSE:Leap:15.1:ToTest
Updated by lnussel almost 6 years ago
The dashboard would need a special case if the job group name does not end in 15.1:
https://github.com/openSUSE/obs_factory/blob/master/app/models/obs_factory/distribution_strategy_opensuse.rb#L16
Updated by okurz almost 6 years ago
Good that you reference the github repo. We can take a look
Updated by lnussel almost 6 years ago
the dashboard is currently on the way into obs directy which means the code will elsewhere and harder to deploy. Can't we just speed this up and use a 15.1 job group?
Updated by okurz almost 6 years ago
lnussel wrote:
the dashboard is currently on the way into obs directy which means the code will elsewhere and harder to deploy
Why choose a solution then which is harder to deploy?
Can't we just speed this up and use a 15.1 job group?
We can always do that but I am not convinced that this is easier in the long run. Now is a way better time then say 15.1->15.2
Updated by okurz almost 6 years ago
lnussel wrote:
The dashboard would need a special case if the job group name does not end in 15.1:
https://github.com/openSUSE/obs_factory/blob/master/app/models/obs_factory/distribution_strategy_opensuse.rb#L16
In the meantime that link has vanished.
https://github.com/openSUSE/obs_factory is archived and obsoleted by
https://github.com/openSUSE/open-build-service/pull/5140 adding the code into OBS itself.
https://github.com/openSUSE/open-build-service/blob/97645f10e658c872f2484746c62a2b898042bfa5/src/api/app/models/obs_factory/distribution_strategy_opensuse.rb#L16 could be the current code line to look into now.
For now I changed all 15.0 products on https://openqa.opensuse.org/admin/products to 15.1 . Should be no problem for staging tests, let's see for validation. Simple mitigation is to rename the existing job group to 15.1 or we still create a new one and move all the stuff there.
Bumped the asset limit of the job group "openSUSE Leap 15.0" to 60 GB and increased the time to keep results and logs a bit because we want to cover more than one minor version in it.
Seeing the following errors:
+++ Rsync errors:
rsync: change_dir "/build/openSUSE:Leap:15.1:Ports:ToTest" (in opensuse-internal) failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1652) [Receiver=3.1.0]
+++ Rsync errors:
rsync: change_dir "/build/openSUSE:Leap:15.1:Images:ToTest/images" (in opensuse-internal) failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1652) [Receiver=3.1.0]
rsync done at Tue Jun 26 07:25:05 UTC 2018
rsync start at Tue Jun 26 07:30:01 UTC 2018
openSUSE-Leap-15.1-NET-x86_64-Build269.2-Media.iso: repo openSUSE-15.1-oss-i586-x86_64-Snapshot269.2 missing, skipped
openSUSE-Leap-15.1-DVD-x86_64-Build269.2-Media.iso: repo openSUSE-15.1-oss-i586-x86_64-Snapshot269.2 missing, skipped
+++ Rsync errors:
rsync: change_dir "/build/openSUSE:Leap:15.1:Ports:ToTest" (in opensuse-internal) failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1652) [Receiver=3.1.0]
+++ Rsync errors:
rsync: change_dir "/build/openSUSE:Leap:15.1:Images:ToTest/images" (in opensuse-internal) failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1652) [Receiver=3.1.0]
rsync done at Tue Jun 26 07:30:05 UTC 2018
so not-existing project as of now: openSUSE:Leap:15.1:Ports:ToTest
Additionally I wonder about some old products, e.g. should we delete 13.2 and 42.2 ?
Updated by okurz almost 6 years ago
As discussed also in the daily RM call at 1000 CEST I renamed the existing openQA job groups "openQA Leap 15.0…" to "openSUSE Leap 15…"
Btw, what do you think about deleting old products on o3, e.g. 13.2?
Current build in :ToTest is iso build 269.2 but build 269.5 so a mismatch. A rebuild triggered by maxlin should solve this. maxlin should trigger a rebuild and tail o3:/var/log/openqa_rsync_staging.log and tell me if we need to adjust anything or if the next matching iso/repo combination is properly picked up
Updated by okurz almost 6 years ago
- Status changed from In Progress to Resolved
https://openqa.opensuse.org/tests/overview?distri=opensuse&version=15.1&build=269.10&groupid=50 looks like a complete test set. Most tests fail because of missing beta warning but expected by the test.
Updated by lnussel almost 5 years ago
- Copied to action #52040: setup openQA added