Bug 1581609

Summary:	[modularity] Removing a module does not erase version info from config file
Product:	[Fedora] Fedora	Reporter:	Rafael Fonseca <rdossant>
Component:	dnf	Assignee:	rpm-software-management
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	29	CC:	dmach, jmracek, packaging-team-maint, rpm-software-management, vmukhame
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	dnf-4.0.4	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1581615 (view as bug list)		Environment:
Last Closed:	2018-11-22 18:13:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1478068, 1581615

Description Rafael Fonseca 2018-05-23 08:38:10 UTC

Description of problem: If you remove an installed module, its config file continue showing 'version = X' even though there are no profiles installed.


Version-Release number of selected component (if applicable): 


How reproducible: always


Steps to Reproduce:
1. dnf module enable ModuleB:f26
2. dnf module install ModuleB/default
3. dnf module remove ModuleB:f26

Actual results: /etc/dnf/modules.d/ModuleB.module has 'version = 1'


Expected results: /etc/dnf/modules.d/ModuleB.module has 'version = -1'


Additional info:

Comment 1 Martin Hatina 2018-07-24 14:04:32 UTC

https://github.com/rpm-software-management/dnf/pull/1144

Comment 2 Jan Kurik 2018-08-14 11:14:03 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.