Project

General

Profile

Actions

action #113737

open

[qe-core] Improve conflict handling in update_install - read conflicts from the package metadata instead of a hash

Added by szarate over 1 year ago. Updated 9 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Spike/Research
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Difficulty:

Description

Motivation

https://build.suse.de/request/show/243640 failed in tests like https://openqa.suse.de/tests/6481025#step/update_install/56 with

the to be installed rpm-ndb-4.14.1-29.2.x86_64 conflicts with 'rpm' provided by the installed rpm-4.14.1-29.46.x86_64

https://build.suse.de/request/show/243640#comment-3694699 already explained that the conflict should be expected. https://build.suse.de/package/view_file/SUSE:Maintenance:20166/python-rpm.SUSE_SLE-15-SP3_Update/rpm-ndb.spec?expand=1 in line 64 correctly states "Conflicts: rpm"

We can skip ahead and prepare in the future for this kind of situations? Can we answer if: is it possible to read conflicts from the package metadata instead of a hash? is it feasible?

Acceptance criteria

  • AC1: Research and possible PoC is done for the question posed above.

Related issues 1 (1 open0 closed)

Copied from openQA Tests - action #95863: [qe-core] Improve conflict handling in update_installFeedbackszarate2021-07-23

Actions
Actions #1

Updated by szarate over 1 year ago

  • Copied from action #95863: [qe-core] Improve conflict handling in update_install added
Actions #3

Updated by apappas over 1 year ago

  • Target version deleted (QE-Core: Ready)

During the meeting, this ticket was deemed unclear. The PR helps the original issue but does not resolve it.

Actions #4

Updated by slo-gin 9 days ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions

Also available in: Atom PDF