RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1218398 - rdo kilo testing repository missing openstack-neutron-*aas
Summary: rdo kilo testing repository missing openstack-neutron-*aas
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: distribution
Version: Kilo
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: Kilo
Assignee: Alan Pevec
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-04 19:17 UTC by wes hayutin
Modified: 2016-04-18 06:47 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description wes hayutin 2015-05-04 19:17:34 UTC 
Description of problem:

rdo kilo testing repository missing openstack-neutron-lbaas

00:29:30.483 ERROR : Error appeared during Puppet run: 172.16.32.54_neutron.pp
00:29:30.483 Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list openstack-neutron-lbaas' returned 1: Error: No matching Packages to list
00:29:30.484 You will find full trace in log /var/tmp/packstack/20150504-185040-dY6HfE/manifests/172.16.32.54_neutron.pp.log

using repo:
00:19:58.731         "Repo-id      : openstack-kilo", 
00:19:58.732         "Repo-name    : Temporary OpenStack Kilo new deps", 
00:19:58.732         "Repo-revision: 1430556508", 
00:19:58.732         "Repo-updated : Sat May  2 08:48:32 2015", 
00:19:58.733         "Repo-pkgs    : 674", 
00:19:58.733         "Repo-size    : 435 M", 
00:19:58.733         "Repo-baseurl : https://repos.fedorapeople.org/repos/openstack/openstack-kilo/testing/el7/", 
00:19:58.734         "Repo-expire  : 21,600 second(s) (last: Mon May  4 18:49:30 2015)",
Comment 1 Alan Pevec 2015-05-04 22:05:30 UTC 
Yes, I'm adding openstack-neutron-*aas - they're not in Fedora yet, so I'm preparing them for CentOS CBS in github/openstack-packages rpm-kilo branches.
Comment 2 Alan Pevec 2015-05-05 01:16:10 UTC 
Fixed in kilo/testing repo as of repodata 05-May-2015 00:04 UTC
Note You need to log in before you can comment on or make changes to this bug.