Bug 1163363
Summary: | openstack-puppet-modules leaves directory behind on uninstall | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Marko Myllynen <myllynen> | |
Component: | openstack-puppet-modules | Assignee: | Javier Peña <jpena> | |
Status: | CLOSED ERRATA | QA Contact: | Ofer Blaut <oblaut> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | low | |||
Version: | 5.0 (RHEL 7) | CC: | jpena, jschluet, nbarcet, sclewis, yeylon | |
Target Milestone: | z1 | Keywords: | ZStream | |
Target Release: | 7.0 (Kilo) | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | openstack-puppet-modules-2014.2.15-5.el7ost | Doc Type: | Bug Fix | |
Doc Text: |
Previously, the openstack-puppet-module package did not own its directories. As a consequence, when uninstalled, the package left unused directories in the file system. This update has fixed the package specification, so the package does not leave any directory on uninstall.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1257701 (view as bug list) | Environment: | ||
Last Closed: | 2015-09-03 17:27:45 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: | 1257701 |
Description
Marko Myllynen
2014-11-12 14:54:04 UTC
I've reproduced this behaviour installing and uninstalling only the openstack-puppet-modules package by itself Gonna check the spec file to see how to deal with this problem The spec file for OPM did not contain the directories, just the files inside them. I have proposed https://review.gerrithub.io/243202 for RDO Trunk. Once it is verified, we will cascade the fix to the specs for other releases. tested [root@controller ~(keystone_admin)]# yum remove openstack-puppet-modules Resolving Dependencies --> Running transaction check ---> Package openstack-puppet-modules.noarch 0:2015.1.8-12.el7ost will be erased --> Processing Dependency: openstack-puppet-modules >= 2014.2.10 for package: openstack-packstack-2015.1-0.11.dev1589.g1d6372f.el7ost.noarch --> Running transaction check ---> Package openstack-packstack.noarch 0:2015.1-0.11.dev1589.g1d6372f.el7ost will be erased --> Finished Dependency Resolution Dependencies Resolved ============================================================================================================================================================================================== Package Arch Version Repository Size ============================================================================================================================================================================================== Removing: openstack-puppet-modules noarch 2015.1.8-12.el7ost @rhelosp-7.0-puddle 5.4 M Removing for dependencies: openstack-packstack noarch 2015.1-0.11.dev1589.g1d6372f.el7ost @rhelosp-7.0-puddle 978 k Transaction Summary ============================================================================================================================================================================================== Remove 1 Package (+1 Dependent package) Installed size: 6.4 M Is this ok [y/N]: y Downloading packages: Running transaction check Running transaction test Transaction test succeeded Running transaction Erasing : openstack-packstack-2015.1-0.11.dev1589.g1d6372f.el7ost.noarch 1/2 Erasing : openstack-puppet-modules-2015.1.8-12.el7ost.noarch 2/2 Verifying : openstack-packstack-2015.1-0.11.dev1589.g1d6372f.el7ost.noarch 1/2 Verifying : openstack-puppet-modules-2015.1.8-12.el7ost.noarch 2/2 Removed: openstack-puppet-modules.noarch 0:2015.1.8-12.el7ost Dependency Removed: openstack-packstack.noarch 0:2015.1-0.11.dev1589.g1d6372f.el7ost Complete! [root@controller ~(keystone_admin)]# ll /usr/share/openstack-puppet/modules/ total 0 drwxr-xr-x. 5 root root 77 Aug 30 09:52 packstack Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2015:1720 |