Bug 1206742

Summary:	Installed epel-release prior to running packstack, packstack disables it on invocation
Product:	[Community] RDO	Reporter:	Dax Kelson <dkelson>
Component:	openstack-packstack	Assignee:	Gaël Chamoulaud <gchamoul>
Status:	CLOSED NOTABUG	QA Contact:	Shai Revivo <srevivo>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	Juno	CC:	aortega, derekh, dkelson, gchamoul, jpena, lars, srevivo
Target Milestone:	---
Target Release:	Kilo
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-18 14:05:46 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:

Description Dax Kelson 2015-03-27 23:09:38 UTC

Description of problem:

I installed epel-release on CentOS7, and had the epel repo enabled.

Then I simply invoked packstack --allinone and then failed because it couldn't find/install puppet and one other package.

After a chattr +i on the repo file I finally saw that packstack was disabling the repo.

I didn't use an answer file or anything.

Seems like it shouldn't disable epel if is previously enabled.

Comment 1 Lars Kellogg-Stedman 2015-03-30 20:08:59 UTC

For what it's worth, on CentOS 7 (centos-release-7-0.1406.el7.centos.2.6.x86_64), with openstack-packstack-2014.2-0.18.dev1462.gbb05296.el7.noarch, the EPEL repository is still enabled after packstack completes.

Can you attach the openstack-setup.log file generated by packstack?

Comment 4 Javier Peña 2016-05-18 14:05:46 UTC

Packstack will disable EPEL by default, as some packages in EPEL can conflict with the RDO-provided ones. There is an option to enable it (set CONFIG_USE_EPEL=y in answer file).

Comment 5 Red Hat Bugzilla 2023-09-14 02:57:14 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days