action #44948
closed
[functional][y] Simplify PCM tests further with EXIT_AFTER_START_INSTALL and no publishing of images
Added by okurz over 5 years ago.
Updated over 5 years ago.
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 22
Description
Motivation¶
See #44072#note-2 . Also, we currently publish qcow images which are not used.
Acceptance criteria¶
- AC1: We only publish qcow images where used for all SLE codestreams
- AC2: The public cloud related tests are only doing the necessary steps to check installability of patterns unless we have a good "validation" downstream scenario
Suggestions¶
Probably we should only schedule any "create_hdd_…" jobs for PCM when we need them, e.g. if the images are used and instead use installer related tests with EXIT_AFTER_START_INSTALL=1.
https://openqa.suse.de/tests/2300629#dependencies shows the dependencies on SLE12 where we have the additional scenario for the test suite "pcm_aws_validation" which we also have for SLE15. Same goes for "azure_validation" which we only have on SLE12.
- Replace "create_hdd_pcm_azure", "…googlecloud" from SLE15 schedule with "pcm_azure", "…googlecloud" with EXIT_AFTER_START_INSTALL=1 and no PUBLISH_HDD_1
- Replace "create_hdd_pcm_googlecloud" from SLE12 schedule with "pcm_googlecloud" as above
- Update dependencies accordingly
- Assignee set to JERiveraMoya
- Related to action #40331: [functional][y] select_patterns_and_packages ignores dependency issues added
Renaming performed. The only thing missing is unlink validation and creation of images for azure and aws (for googlecloud we didn't implement validation so we are fine there), removing PUBLISH_HDD_1 from parent jobs.
- Priority changed from Normal to High
JERiveraMoya wrote:
Renaming performed.
Hm, I see in https://openqa.suse.de/admin/test_suites that we have test suites now that are called "pcm_aws" and alike but they have now "EXIT_AFTER_START_INSTALL=1" and INSTALLONLY=1 and PUBLISH_HDD_1. I am not sure this works but to me it does not make sense to combine these options. My suggestion was to replace, not to rename, because the jobs should not actually be image creation jobs when we do not use the image. I tried to make sure in the suggestions as I have written what exactly needs to be done. The important difference is that for SLE15 we do not azure validation and we do not need it but for SLE12 we do so I doubt you can reuse the same test suite for both SLE15 and SLE12 in this case.
- Due date changed from 2019-01-22 to 2019-01-15
I think I messed up the "due date" which should be 2019-01-15 for the current sprint, not the week later.
Right, I wrote wrongly that combination because I misinterpret the ellipsis (...). thanks for clarification.
- Status changed from Workable to In Progress
Now we have following chain deps:
create_hdd_pcm_aws --> pcm_aws_validation
|
--> create_hdd_pcm_azure --> pcm_azure_validation (specific for sle12sp4 with PUBLISH_HDD_1)
|
--> pcm_azure (specific for sle15sp1 with EXIT_AFTER_START_INSTALL=1 and no PUBLISH_HDD_1)
|
--> pcm_googlecloud
- Project changed from 46 to openQA Tests
- Category set to Enhancement to existing tests
ok. That looks very good now. Additionally I removed INSTALLONLY=1 from the test suites that already specify EXIT_AFTER_START_INSTALL=1 as EXIT_AFTER_START_INSTALL will stop the test execution already in an earlier step.
Could you please add a test suite description to the new test suite "pcm_azure"?
Updated rest of comments to differentiate the ones creating an image from the ones not doing it.
- Status changed from In Progress to Feedback
Waiting for next sle15 build to verify.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF