Bug 1298610 - Update python-networking-cisco spec to 2.0.0
Summary: Update python-networking-cisco spec to 2.0.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-cisco
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: ga
: 8.0 (Liberty)
Assignee: Mike Burns
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks: 1313941 1313943 1313965 1313970 1314083 1321147 1321149 1322024
TreeView+ depends on / blocked
 
Reported: 2016-01-14 14:51 UTC by Brian Demers
Modified: 2016-04-07 21:22 UTC (History)
4 users (show)

Fixed In Version: python-networking-cisco-2.0.0-3.el7ost
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Clone Of:
: 1313941 1313943 1313970 (view as bug list)
Environment:
Last Closed: 2016-04-07 21:22:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
update version and release (remove XXX from RDO version) (1.48 KB, application/mbox)
2016-01-14 14:51 UTC, Brian Demers
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:0603 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 8 Enhancement Advisory 2016-04-08 00:53:53 UTC

Description Brian Demers 2016-01-14 14:51:51 UTC
Created attachment 1114835 [details]
update version and release (remove XXX from RDO version)

The current osp8 branch still has the kilo version of python-networking-cisco

In order to update to the liberty version (2.0.0),
cherry-pick the following from upstream (https://github.com/openstack-packages/python-networking-cisco/commits/rpm-liberty):
880f258bffb97d18c9e16d241f21c1642018744e
091c9ab38cf34136134c53655d1a69756d03c033

And apply the attached patch. (I don't have access to update the spec repo)

Let me know if additional updates are needed

Scratch build results: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=10343207

Comment 2 Mike Burns 2016-01-14 17:59:49 UTC
Looking at the rebase, it says that you need ciscoconfparse -- does that need to be a requirement?

Comment 3 Mike Burns 2016-01-14 18:05:02 UTC
build done without ciscoconfparse

Comment 5 Mike Burns 2016-01-15 22:42:03 UTC
The reason the build failed: 

RPM build errors:
    Installed (but unpackaged) file(s) found:
   /usr/bin/fabric-enabler-agent
   /usr/bin/fabric-enabler-cli
   /usr/bin/fabric-enabler-server
   /usr/bin/neutron-cisco-apic-host-agent
   /usr/bin/neutron-cisco-apic-service-agent
   /usr/etc/saf/enabler_conf.ini
   /usr/etc/saf/init/fabric-enabler-agent.conf
   /usr/etc/saf/init/fabric-enabler-agent.service
   /usr/etc/saf/init/fabric-enabler-server.conf
   /usr/etc/saf/init/fabric-enabler-server.service

The /usr/bin entries are easy enough to fix, but the /usr/etc/* files shouldn't be going into /usr/etc.  Those are things that should probably go in /etc.  This needs to be fixed by in the package first.

Comment 6 Brian Demers 2016-01-19 17:41:05 UTC
I was thinking the OSP8 branch would start from the upstream rpm-liberty, so this branch is two commits to resolve this:
880f258bffb97d18c9e16d241f21c1642018744e
091c9ab38cf34136134c53655d1a69756d03c033

How should we proceed ? Do you want separate BZ's to track a back port of each of those?  Or should I just attach a patch that contains the delta between rpm-liberty and the downstream spec repo ?

Comment 7 Mike Burns 2016-01-19 19:40:43 UTC
Ahh I had missed the spec updates in stable liberty.  With those, the build works.

Comment 13 Brian Demers 2016-03-29 03:48:07 UTC
I created a patches branch on code.eng 'rhos-8.0-patches'  This can be applied to the spec repo with `# patches_base=+2`, please review the branch and apply.

The first one updates the .gitreview to stable/liberty, the second for code.eng

We were going to cut a new release from stable/liberty, but given the uncertain stadium policy (and short time frame) we created a patches branch (all changes have been merged to master, and proposed to stable/liberty on review.openstack.

I'll update the referenced blockers above in the morning.

Comment 15 errata-xmlrpc 2016-04-07 21:22:29 UTC
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/RHEA-2016-0603.html


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