RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1230899 - Add openstack-designate packages in RDO Kilo
Summary: Add openstack-designate packages in RDO Kilo
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: distribution
Version: Kilo
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Kilo
Assignee: Alan Pevec
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On: 1228163
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-11 17:46 UTC by Rich Megginson
Modified: 2016-04-18 06:49 UTC (History)
7 users (show)

Fixed In Version: openstack-designate-2015.1.0-1
Clone Of:
Environment:
Last Closed: 2015-07-31 00:07:45 UTC
Embargoed:

Attachments (Terms of Use)

Description Rich Megginson 2015-06-11 17:46:12 UTC 
Description of problem:

There are packages in http://trunk.rdoproject.org/centos70/current/
but not in https://repos.fedorapeople.org/repos/openstack/openstack-kilo/ or https://repos.fedorapeople.org/repos/openstack/openstack-kilo/testing/

Would like to have Designate available for RDO Kilo.  Upstream has done an official Kilo release - http://git.openstack.org/cgit/openstack/designate/commit/?h=stable/kilo&id=5f2b243c087721204ada3b569bbfb0e5558fbf56

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Rich Megginson 2015-06-11 17:47:25 UTC 
There also needs to be a bugzilla Component for openstack-designate
Comment 2 Ihar Hrachyshka 2015-06-15 16:29:50 UTC 
I've built rawhide version of the package. Is it enough from my side to see it in RDO?
Comment 3 Alan Pevec 2015-06-15 17:02:47 UTC 
yes, CBS build started https://cbs.centos.org/koji/buildinfo?buildID=1328
I'll create rdo-update when done.
Comment 4 Alan Pevec 2015-06-15 17:09:10 UTC 
https://review.gerrithub.io/236562
Comment 5 Alan Pevec 2015-07-31 00:07:45 UTC 
In RDO Kilo production.
Note You need to log in before you can comment on or make changes to this bug.