RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1680684 - The profile is marked as installed despite the fact that artifacts installation failed
Summary: The profile is marked as installed despite the fact that artifacts installati...
Keywords:
Status: CLOSED DUPLICATE of bug 1719679
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: dnf
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Packaging Maintenance Team
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-25 14:16 UTC by Marek Blaha
Modified: 2021-03-01 13:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-18 09:35:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Marek Blaha 2019-02-25 14:16:48 UTC 
Description of problem:

This bug is a variation on https://bugzilla.redhat.com/show_bug.cgi?id=1656782 without switching the streams.
Despite unsuccessful installation of module:stream/profile, the profile is marked as installed in `dnf module list` output.


Version-Release number of selected component (if applicable):
# rpm -q dnf libdnf
dnf-4.0.9.2-5.el8.noarch
libdnf-0.22.5-4.el8.x86_64

How reproducible:
deterministic

Steps to Reproduce:
Given we have two versions of package, each version file conflicts with the other. The first one (FileConflict-1.0-1.x86_64) came from ursine repo, the second one (FileConflict-0:2.0.streamB-1.x86_64) is part of non-enabled module.
$ cat modules.yaml 
---
document: modulemd
version: 2
data:
  name: TestModule
  stream: B
  version: 1
  context: 6c81f848
  summary: Test module
  description: >-
      This is a test module
  profiles:
    default:
      rpms:
      - FileConflict
  artifacts:
    rpms:
    - FileConflict-0:2.0.streamB-1.x86_64
...

# dnf install FileConflict-1.0-1.x86_64
# dnf module install TestModule:B/default
Last metadata expiration check: 0:02:12 ago on Mon Feb 25 14:07:34 2019.
Dependencies resolved.
==========================================================================================
 Package              Arch           Version                  Repository             Size
==========================================================================================
Upgrading:
 FileConflict         x86_64         2.0.streamB-1            fileconflicts         6.7 k
Installing module profiles:
 TestModule/default                                                                      
Enabling module streams:
 TestModule                          B                                                   

Transaction Summary
==========================================================================================
Upgrade  1 Package

Total size: 6.7 k
Is this ok [y/N]: y
Downloading Packages:
[SKIPPED] FileConflict-2.0.streamB-1.x86_64.rpm: Already downloaded                      
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transaction check error:
  file /usr/lib/FileConflict/a_dir from install of FileConflict-0:2.0.streamB-1.x86_64 conflicts with file from package FileConflict-0:1.0-1.x86_64

Error Summary
-------------

bash-4.4# echo $?
1


Actual results:

# dnf module list
Last metadata expiration check: 0:03:17 ago on Mon Feb 25 14:07:34 2019.
fileconflicts
Name                    Stream             Profiles                Summary                
TestModule              B [e]              default [i]             Test module            

Hint: [d]efault, [e]nabled, [x]disabled, [i]nstalled


Expected results:
profile "default" is not marked as installed.


Additional info:
The test of this bug is a part of ci-dnf-stack as module-install-7.feature.
Comment 1 Marek Blaha 2019-06-18 09:35:54 UTC 

*** This bug has been marked as a duplicate of bug 1719679 ***
Note You need to log in before you can comment on or make changes to this bug.