Bug 1163351
Summary: | heat-cfntools should not depend on yum | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Ryan Brown <rybrown> |
Component: | heat-cfntools | Assignee: | Ryan Brown <rybrown> |
Status: | CLOSED ERRATA | QA Contact: | Amit Ugol <augol> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.0 (RHEL 6) | CC: | augol, brad, ddomingo, extras-qa, jpeeler, jschluet, nyechiel, sbaker, sclewis, shardy, walters, yeylon, zbitter |
Target Milestone: | z5 | Keywords: | ZStream |
Target Release: | 5.0 (RHEL 6) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | heat-cfntools-1.2.6-5.el6 | Doc Type: | Bug Fix |
Doc Text: |
With this release, heat-cfntools is no longer dependent on the YUM package manager. In previous releases, this prevented users from using heat-cfntools whenever they attempted to create cloud images without yum installed. Now, heat-cfntools will use yum if available, but no longer requires that it be installed.
|
Story Points: | --- |
Clone Of: | 1162706 | Environment: | |
Last Closed: | 2015-09-10 11:45:01 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: | 1161290, 1162706 | ||
Bug Blocks: |
Description
Ryan Brown
2014-11-12 14:37:15 UTC
This is the dep tree for this version: # repoquery --requires --recursive --resolve heat-cfntools heat-cfntools-0:1.2.6-5.el6.noarch python-boto-0:2.25.0-2.el6.noarch curl-0:7.19.7-46.el6.x86_64 python-0:2.6.6-64.el6.x86_64 tar-2:1.23-13.el6.x86_64 coreutils-0:8.4-37.el6.x86_64 bzip2-0:1.0.5-7.el6_0.x86_64 shadow-utils-2:4.1.4.2-19.el6_6.1.x86_64 python-setuptools-0:0.6.10-3.el6.noarch gzip-0:1.3.12-22.el6.x86_64 python-psutil-0:0.6.1-1.el6ost.x86_64 python-argparse-0:1.2.1-2.1.el6.noarch 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://rhn.redhat.com/errata/RHBA-2015-1764.html |