Bug 1158163 – sahara does not follow packaging guidelines

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1158163 - sahara does not follow packaging guidelines

Summary:	sahara does not follow packaging guidelines

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openstack-sahara (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	Unspecified Unspecified

Priority	urgent Severity urgent
Target Milestone:	Upstream M3
Target Release:	7.0 (Kilo)
Assigned To:	Elise Gafford
QA Contact:	Luigi Toscano
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2014-10-28 14:34 EDT by Steven Dake
Modified:	2016-04-26 17:02 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	openstack-sahara-2015.1.0-2.el7ost
Doc Type:	Bug Fix
Doc Text:	Prior to this update, Sahara's 'distributed' mode feature was in alpha testing. Consequently, Red Hat Enterprise Linux OpenStack Platform did not package or support the 'sahara-api' or 'sahara-engine' processes individually. With this update, the 'distributed' mode feature is considered stable, and RHEL OpenStack Platform now provides systemd unit files for the 'sahara-api' and 'sahara-engine' services. As a result, users can run Sahara in distributed mode, with separation of the API and engine node clusters.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-08-05 09:16:27 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2015:1548	normal	SHIPPED_LIVE	Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory	2015-08-05 13:07:06 EDT

Groups: None (edit)

Description Steven Dake 2014-10-28 14:34:02 EDT

Description of problem:
Sahara does not follow packaging guidelines.  There should be three packages atleast:
sahara-common
sahara-api
sahara-engine

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

How reproducible:
100%

Steps to Reproduce:
1.yum list | grep sahara
2.there is no api or engine package
3.

Actual results:


Expected results:


Additional info:

Comment 5 Elise Gafford 2015-02-18 16:46:57 EST

Changes created and dev-tested, but at this time Sahara's distributed mode (separation of api and engine) is in alpha mode. I will follow up with the Sahara upstream team to suggest a sensible milestone for repair of this bug.

Comment 6 Elise Gafford 2015-02-26 13:00:49 EST

Discussed at Sahara upstream meeting today; distributed mode is set to come out of Alpha for Kilo, so this is sensible to fix for RHOS 7 but leave unaddressed for RHOS 6.

Comment 7 Elise Gafford 2015-02-27 14:47:20 EST

Fix pending fix and release of https://bugs.launchpad.net/sahara/+bug/1426512 (not adding external bug tracker as this bug does not constitute a fix to the packaging issue, and not adding a dependency as the upstream bug is not a RH-specific issue.

Comment 9 Luigi Toscano 2015-06-10 09:22:19 EDT

Sahara services are also packaged separately, and install separate systemd units for -api and -engine (see also rhbz#1214817) in addition to the old (deprecated) -all unit, which enables the "all services mode", provided by openstack-sahara.

Moving to VERIFIED.

openstack-sahara-common-2015.1.0-2.el7ost.noarch
openstack-sahara-api-2015.1.0-2.el7ost.noarch
openstack-sahara-engine-2015.1.0-2.el7ost.noarch
openstack-sahara-2015.1.0-2.el7ost.noarch

Comment 11 errata-xmlrpc 2015-08-05 09:16:27 EDT

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/RHEA-2015:1548

Note You need to log in before you can comment on or make changes to this bug.