action #49415: [functional][y] Enable test to validate generated profile to staging - qe-yam - openSUSE Project Management Tool

Custom queries

openQA Infrastructure Project
openqa-review - Closed tickets last updated by openqa-review, last 30 days
QA roadmap long-term
QA SLE functional
QA SLE Functional - closed in last 14 days
QA SLE Functional - High, need to be refined
QA SLE Functional - over cycle time median
QA SLE u
QA SLE y
QA tools (tag not necessary in openQA and subprojects)
QA tools tag (tag not necessary in openQA and subprojects; excluding tickets in "Ready" version as they are already on the backlog)
QAC - Backlog
QE tools team - backlog (ready issues)
QE tools team - backlog (w/o infra)
QE tools team - backlog SLA high
QE tools team - backlog SLA immediate
QE tools team - backlog SLA no immediate/urgent in feedback/blocked
QE tools team - backlog SLA normal
QE tools team - backlog SLA urgent
QE tools team - backlog SLO high
QE tools team - backlog SLO normal
QE tools team - backlog SLO urgent
QE tools team - backlog, high-level view (epics and higher)
QE tools team - backlog, non-reactive work, needs parent
QE tools team - backlog, top-level view (all sagas)
QE tools team - closed within last 14 days
QE tools team - closed within last 60 days
QE tools team - closed yesterday
QE Tools Team - Collaborative Session
QE tools team - due date forecast
QE tools team - exceeding due-date
QE tools team - infrastructure backlog
QE tools team - next - sorted by update time
QE tools team - next issues
QE tools team - non-estimated (unblocked) issues (w/o infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
QE tools team - update forecast
QE tools team - updated by priority
QE tools team - what members of the team are working on - Feedback (not-low)
QE Tools Team Backlog By Assignee
QE Yam backlog
QE Yam blocked issues
QE Yam closed yesterday
QE Yam issues IN_PROGRESS
QE Yam new action tickets per day
QE Yam new actions
QE Yam prio high, no updates last 4 weeks
QE Yam prio low & normal, no update for 1 year
QE Yam recjected yesterday
QE Yam resolved yesterday
QE Yam workable actions
soft failure tickets in progress
softfailure tickets resolved
softfailure tickets workable
Tools Team Retrospective
Tools Team Retrospective (not estimated or assigned)

Actions

Copy link

action #49415

closed

coordination #49157: [epic] Introduce yast2_clone to more scenarios

[functional][y] Enable test to validate generated profile to staging

Added by riafarov about 5 years ago. Updated over 3 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

ybonatakis

Target version:

SUSE QA - Milestone 30

Start date:

2019-03-18

Due date:

% Done:

Estimated time:

3.00 h

Description

Motivation¶

Too many times we got an issue that yast2-schema didn't match other packages, so autoyast profile doesn't validate.
It's hard to catch before actual medium is built, so staging is a good place for those.

Acceptance criteria¶

Test module to validate autoyast schema is executed in staging

Suggestions¶

We can execute it for Y staging only SLES.
Would be great to use new scheduling mechanism here, to modify one of the scenarios for staging only.
Test module already exists: yast2_clone_system
We just need to schedule it for staging.

History
Notes
Property changes

Actions

Copy link

Updated by SLindoMansilla about 5 years ago

Category set to New test

As a result of backlog triaging (see https://progress.opensuse.org/projects/openqatests/wiki#ticket-backlog-triaging for more information).

Please, feel free to adjust the category or the "[label]" if you think different.

Actions

Copy link

Updated by riafarov about 5 years ago

Description updated (diff)
Estimated time set to 3.00 h

Actions

Copy link

Updated by riafarov about 5 years ago

Status changed from New to Workable

Actions

Copy link

Updated by riafarov about 5 years ago

Due date deleted (~~2019-04-09~~)

Actions

Copy link

Updated by riafarov about 5 years ago

Due date set to 2019-05-07

Actions

Copy link

Updated by mloviska about 5 years ago

Assignee set to mloviska

Actions

Copy link

Updated by mloviska almost 5 years ago

Assignee deleted (~~mloviska~~)

Actions

Copy link

Updated by riafarov almost 5 years ago

Parent task set to #49157

Actions

Copy link

Updated by riafarov almost 5 years ago

Target version changed from Milestone 24 to Milestone 25

Actions

Copy link

#10

Updated by mloviska almost 5 years ago

Status changed from Workable to In Progress
Assignee set to mloviska

Actions

Copy link

#11

Updated by mloviska almost 5 years ago

REPO_SLE_MODULE_DEVELOPMENT_TOOLS is required to install xml validation tools and it is not synced in openqa.
http://eris.suse.cz/tests/13701#step/yast2_clone_system/31

SLE-15-SP1-Staging:V-Product-SLES_SAP-POOL-x86_64-Media1-CURRENT/               2019-05-02 07:59    -   
[DIR] SLE-15-SP1-Staging:Y-Installer-DVD-x86_64-BuildY.210.3-Media1/                  2019-05-01 15:28    -   
[DIR] SLE-15-SP1-Staging:Y-Installer-DVD-x86_64-BuildY.211.1-Media1/                  2019-05-02 08:09    -   
[DIR] SLE-15-SP1-Staging:Y-Module-Basesystem-POOL-x86_64-Build210.3-Media1/           2019-05-01 15:21    -   
[DIR] SLE-15-SP1-Staging:Y-Module-Basesystem-POOL-x86_64-Build211.1-Media1/           2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-Basesystem-POOL-x86_64-Media1-CURRENT/              2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-CAP-Tools-POOL-x86_64-Build210.3-Media1/            2019-05-01 13:15    -   
[DIR] SLE-15-SP1-Staging:Y-Module-CAP-Tools-POOL-x86_64-Build211.1-Media1/            2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-CAP-Tools-POOL-x86_64-Media1-CURRENT/               2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-Containers-POOL-x86_64-Build210.3-Media1/           2019-05-01 13:08    -   
[DIR] SLE-15-SP1-Staging:Y-Module-Containers-POOL-x86_64-Build211.1-Media1/           2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-Containers-POOL-x86_64-Media1-CURRENT/              2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-Desktop-Applications-POOL-x86_64-Build210.3-Media1/ 2019-05-01 14:43    -   
[DIR] SLE-15-SP1-Staging:Y-Module-Desktop-Applications-POOL-x86_64-Build211.1-Media1/ 2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-Desktop-Applications-POOL-x86_64-Media1-CURRENT/    2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-HPC-POOL-x86_64-Build210.3-Media1/                  2019-05-01 14:43    -   
[DIR] SLE-15-SP1-Staging:Y-Module-HPC-POOL-x86_64-Build211.1-Media1/                  2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-HPC-POOL-x86_64-Media1-CURRENT/                     2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-Python2-POOL-x86_64-Build210.3-Media1/              2019-05-01 14:23    -   
[DIR] SLE-15-SP1-Staging:Y-Module-Python2-POOL-x86_64-Build211.1-Media1/              2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-Python2-POOL-x86_64-Media1-CURRENT/                 2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-RT-POOL-x86_64-Build210.3-Media1/                   2019-05-01 14:43    -   
[DIR] SLE-15-SP1-Staging:Y-Module-RT-POOL-x86_64-Build211.1-Media1/                   2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-RT-POOL-x86_64-Media1-CURRENT/                      2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-SAP-Applications-POOL-x86_64-Build210.3-Media1/     2019-05-01 14:43    -   
[DIR] SLE-15-SP1-Staging:Y-Module-SAP-Applications-POOL-x86_64-Build211.1-Media1/     2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-SAP-Applications-POOL-x86_64-Media1-CURRENT/        2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-Server-Applications-POOL-x86_64-Build210.3-Media1/  2019-05-01 14:43    -   
[DIR] SLE-15-SP1-Staging:Y-Module-Server-Applications-POOL-x86_64-Build211.1-Media1/  2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Module-Server-Applications-POOL-x86_64-Media1-CURRENT/     2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Product-HA-POOL-x86_64-Build210.3-Media1/                  2019-05-01 14:43    -   
[DIR] SLE-15-SP1-Staging:Y-Product-HA-POOL-x86_64-Build211.1-Media1/                  2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Product-HA-POOL-x86_64-Media1-CURRENT/                     2019-05-02 08:03    -   
[DIR] SLE-15-SP1-Staging:Y-Product-HPC-POOL-x86_64-Build210.3-Media1/                 2019-05-01 15:05    -   
[DIR] SLE-15-SP1-Staging:Y-Product-HPC-POOL-x86_64-Build211.1-Media1/                 2019-05-02 07:56    -   
[DIR] SLE-15-SP1-Staging:Y-Product-HPC-POOL-x86_64-Media1-CURRENT/                    2019-05-02 07:56    -   
[DIR] SLE-15-SP1-Staging:Y-Product-RT-POOL-x86_64-Build210.3-Media1/                  2019-05-01 15:05    -   
[DIR] SLE-15-SP1-Staging:Y-Product-RT-POOL-x86_64-Build211.1-Media1/                  2019-05-02 07:56    -   
[DIR] SLE-15-SP1-Staging:Y-Product-RT-POOL-x86_64-Media1-CURRENT/                     2019-05-02 07:56    -   
[DIR] SLE-15-SP1-Staging:Y-Product-SLED-POOL-x86_64-Build210.3-Media1/                2019-05-01 15:05    -   
[DIR] SLE-15-SP1-Staging:Y-Product-SLED-POOL-x86_64-Build211.1-Media1/                2019-05-02 07:56    -   
[DIR] SLE-15-SP1-Staging:Y-Product-SLED-POOL-x86_64-Media1-CURRENT/                   2019-05-02 07:56    -   
[DIR] SLE-15-SP1-Staging:Y-Product-SLES-BCL-POOL-x86_64-Build210.3-Media1/            2019-05-01 15:05    -   
[DIR] SLE-15-SP1-Staging:Y-Product-SLES-BCL-POOL-x86_64-Build211.1-Media1/            2019-05-02 07:56    -   
[DIR] SLE-15-SP1-Staging:Y-Product-SLES-BCL-POOL-x86_64-Media1-CURRENT/               2019-05-02 07:56    -   
[DIR] SLE-15-SP1-Staging:Y-Product-SLES-POOL-x86_64-Build210.3-Media1/                2019-05-01 15:05    -   
[DIR] SLE-15-SP1-Staging:Y-Product-SLES-POOL-x86_64-Build211.1-Media1/                2019-05-02 07:56    -   
[DIR] SLE-15-SP1-Staging:Y-Product-SLES-POOL-x86_64-Media1-CURRENT/                   2019-05-02 07:56    -   
[DIR] SLE-15-SP1-Staging:Y-Product-SLES_SAP-POOL-x86_64-Build210.3-Media1/            2019-05-01 13:15    -   
[DIR] SLE-15-SP1-Staging:Y-Product-SLES_SAP-POOL-x86_64-Build211.1-Media1/            2019-05-02 07:56    -   
[DIR] SLE-15-SP1-Staging:Y-Product-SLES_SAP-POOL-x86_64-Media1-CURRENT/               2019-05-02 07:56    -   
[DIR] SUSE-4.0-CAASP-POOL-x86_64-Build7.4-Media1/                                     2019-03-05 17:30    -

Actions

Copy link

#12

Updated by mloviska almost 5 years ago

jing is missing.

http://eris.suse.cz/tests/13705#step/yast2_clone_system/40

Actions

Copy link

#13

Updated by mloviska almost 5 years ago

jing is available for development tools repo, which is not enabled for staging
http://dist.suse.de/ibs/SUSE:/SLE-15-SP1:/GA:/TEST/images/repo/SLE-15-SP1-Module-Development-Tools-POOL-x86_64-Media1/noarch/

On the contrary xmllint is available on installation medium

$ rpm -qf /usr/bin/xmllint 
$ libxml2-tools-2.9.9-1.1.x86_64

/tmp/mnt/x86_64/libxmlsec1-1-1.2.26-5.22.x86_64.rpm
/tmp/mnt/x86_64/libxml2-2-2.9.7-3.6.1.x86_64.rpm
/tmp/mnt/x86_64/libxml2-tools-2.9.7-3.6.1.x86_64.rpm
/tmp/mnt/x86_64/libxmlsec1-openssl1-1.2.26-5.22.x86_64.rpm

Actions

Copy link

#14

Updated by mloviska almost 5 years ago

Works fine without jings
http://eris.suse.cz/tests/13709

Actions

Copy link

#15

Updated by mloviska almost 5 years ago

Status changed from In Progress to Feedback

PR:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/7368

jings
I have asked coolo, how to enable development tools repo in staging Y.

Actions

Copy link

#16

Updated by mloviska almost 5 years ago

To enable development tools repo, I guess we need to edit https://build.suse.de/package/view_file/SUSE:SLE-15-SP1:GA:Staging:Y/000product/_multibuild?expand=1.

Actions

Copy link

#17

Updated by mloviska almost 5 years ago

I have built the staging Y project with development tools module
http://download.suse.de/ibs/home:/mloviska:/branches:/SUSE:/SLE-15-SP1:/GA:/Staging:/Y/images/repo/

Actions

Copy link

#18

Updated by mloviska almost 5 years ago

Status changed from Feedback to In Progress

Actions

Copy link

#19

Updated by mloviska almost 5 years ago

Status changed from In Progress to Feedback

Works fine
http://eris.suse.cz/tests/13743#step/yast2_clone_system/36
Repo location
http://download.suse.de/ibs/home:/mloviska:/branches:/SUSE:/SLE-15-SP1:/GA:/Staging:/Y/images/repo/SLE-15-SP1-Module-Development-Tools-POOL-x86_64-Media1/

I will ask Frederic if we can enable it in stagging Y project.

Actions

Copy link

#20

Updated by mloviska almost 5 years ago

Updated schedule:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/7368/files

No code change is needed in console/yast2_clone_system.pm and currently, we are waiting for RM to backfill development tools module in Staging:Y

Actions

Copy link

#21

Updated by JERiveraMoya almost 5 years ago

Due date changed from 2019-05-07 to 2019-05-21

We need to verify for applying this change in staging sle12sp5.
For sle15 we need to merge the PR when development tool module will be enable.

Actions

Copy link

#22

Updated by mloviska almost 5 years ago

stagging sle15sp1 is not going to be updated.

Since we are in GMC "state", I don't want to destabilize stagings, so
we'll have to defer changing stagings setup to SP2 or 12SP5.

--
Frederic Crozat
Release Manager SUSE Linux Enterprise
SUSE

Actions

Copy link

#23

Updated by JERiveraMoya almost 5 years ago

Due date changed from 2019-05-21 to 2019-06-04
Status changed from Feedback to Workable
Assignee deleted (~~mloviska~~)

Try out to install from any repo if no deps issue found is one option or we can postpone it.

Actions

Copy link

#24

Updated by riafarov almost 5 years ago

jing is not available for staging, Development Tools module is not yet enabled there yet. We still will try to avoid building whole repo just for jing and either install it there, or try to use cpan module like XML::Validate and validate profile in the code directly.

Actions

Copy link

#25

Updated by riafarov almost 5 years ago

Due date changed from 2019-06-04 to 2019-07-09
Target version changed from Milestone 25 to Milestone 26

Actions

Copy link

#26

Updated by riafarov almost 5 years ago

Due date changed from 2019-07-09 to 2020-01-14
Target version changed from Milestone 26 to Milestone 30+

Targeting SLE 15 SP2

Actions

Copy link

#27

Updated by ybonatakis over 4 years ago

Status changed from Workable to In Progress
Assignee set to ybonatakis

Actions

Copy link

#28

Updated by ybonatakis over 4 years ago

I updated the yaml and i run a VR[0] with penqa-clone-job --from https://openqa.suse.de/ 3745088 REPO_SLE_MODULE_DEVELOPMENT_TOOLS=SLE-15-SP2-Module-Development-Tools-POOL-x86_64-BuildY.94.5-Media1 but zypper returns a error code 4 which indicates problem reported by ZYPP library. I am not sure why is that and due to the days is hard to find anyone to take a look

[0] http://aquarius.suse.cz/tests/1126#step/yast2_clone_system/61

Actions

Copy link

#29

Updated by ybonatakis over 4 years ago

Status changed from In Progress to Feedback

Actions

Copy link

#30

Updated by ybonatakis over 4 years ago

The SLE-15-SP2-Module-Development-Tools-POOL-x86_64-BuildY.94.5-Media1 could not be found in the assets.
I checked the rsync scripts and the generated files. the script[0] greps for the Development_Tools but the files_repo.lst[1] doesnt have it. i cant ssh into the OSD to investigate the configuration to see whats going on there, but i assume that it would be something trivial to overcome

[0] https://openqa.suse.de/admin/obs_rsync/SUSE:SLE-15-SP2:GA:Staging:Y/runs/.run_last/download/read_files.sh
[1] https://openqa.suse.de/admin/obs_rsync/SUSE:SLE-15-SP2:GA:Staging:Y/runs/.run_last/download/files_repo.lst

Actions

Copy link

#31

Updated by mgriessmeier over 4 years ago

Target version changed from Milestone 30+ to Milestone 30

bulk moved to M30 for revisiting

Actions

Copy link

#32

Updated by ybonatakis over 4 years ago

Status changed from Feedback to In Progress

Actions

Copy link

#33

Updated by ybonatakis over 4 years ago

Status changed from In Progress to Feedback

A workaround of the problem of the unavailability of the jing package due to the lack of the development module in StagingY was to install the package and the necessary dependency from another source. I used the packages i found on https://rpmfind.net/linux/opensuse/distribution/leap. Another change is the output from the fail. in addition i removed the xmllint validation, as issues reported and its failures were not clear.

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9233

Actions

Copy link

#34