action #95929
closedaction #95863: [qe-core] Improve conflict handling in update_install
[qe-core] Investigate if update_install could be ran in the functional job group
0%
Description
Observation¶
We have a All packages and patterns test module which should be doing a similar job, however would it be feasible to add this test to a test suite that has multiple products enabled (Specially PackageHub, which is not our responsability but could help that team in early detection).
Suggestions¶
- Investigate and compare functionality of update_install vs
select all packages and patternsand other test modules that offer similar functionality. - Create a subticket if there's the need to add it to the functional job group.
Updated by apappas about 3 years ago
- Status changed from Workable to Rejected
- Assignee set to apappas
update_install installs all the released updates to the SUT, installs binaries in the update that are missing in the default installation and then adds the incident repo and installs the patches in the incident. This is all done based on info provided by SMELT.
This is not applicable to prerelease versions because they use binaries of the same build so there are definitionally no updates.