action #111458
Updated by JERiveraMoya almost 2 years ago
#### Motivation We now have responsibility of YaST tests in [YaST Maintenance Updates](https://openqa.suse.de/group_overview/421). This means that we will have to debug failures that could be caused by maintenance updates installed on the systems of those runs. In order to facilitate with this it would be convenient to have a tool that shows a small overview of the maintenance updates that are applied to a job. #### Acceptance criteria **AC1**: Given one openQA Write a cli tool that accepts a job ID, script can query openQA to collect all IDS in <product>_TEST_ISSUES or only id as an input and outputs a small summary of the one related with one or more products. maintenance updates. **AC2**: Script can query information for those The tool should include info about all incident IDs in all of the `.*_TEST_ISSUES` parameters of that helps to debugs problems job. **AC3**: The tool should have minimal dependencies. #### Suggestion * Using the `openQA Job ID` we should be able to construct the var.json url of the job (eg `https://openqa.suse.de/tests/8805896/file/vars.json`). We can either parse the .json file to get get the Incident IDs from `.*_TEST_ISSUES` or from the `MAINT_TEST_REPO` variables. * For each Incident ID we should be able to get the `patchinfo` of the update. Eg for Incident ID `24365` this can be done either via getting the file https://build.suse.de/source/SUSE:Maintenance:24364/patchinfo/_patchinfo , or by scraping https://build.suse.de/package/view_file/SUSE:Maintenance:24365/patchinfo/_patchinfo?expand=1 , or via osc commands. All three methods require a login first. * The tool should output a small amount of information for each Incident ID. The patchinfo file may contain more info than needed so it could need additional parsing.