Upgrading openstack packages from 1.05 to 1.05.1 fails due to incorrect package versioning

Bug #1365120 reported by Ignatious Johnson Christopher
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Won't Fix
Critical
Unassigned
R1.1
Won't Fix
Critical
Unassigned
R3.0
Won't Fix
Critical
Unassigned
R3.0.2.x
Won't Fix
Critical
Unassigned
R3.1
Won't Fix
Critical
Unassigned
Trunk
Won't Fix
Critical
Unassigned

Bug Description

Upgrading openstack packages from 1.05 to 1.05.1 fails due to incorrect package version.

From:
Subject: [Users] Update 1.05 to 1.05.1
Date: September 3, 2014 at 2:19:30 AM PDT
To: "<email address hidden>" <email address hidden>

Hello,

does anybody know how to update contrail havana at CentOS from 1.05 to 1.05.1? I cannot run yum update, because someone created bad syntax for package version. New package has lower number than old one.

openstack-nova-api-2013.2-1.05.1.234.noarch.rpm
openstack-nova-api-2013.2-1.05.211.noarch.rpm

Tags: packaging
Revision history for this message
Ignatious Johnson Christopher (ijohnson-x) wrote :

Workaround for 1.05 to 1.05.1 upgrade, is to localinstall the specific version of the package before upgrade.
yum localinstall openstack-nova-api-2013.2-1.05.1.234.noarch.rpm

Issue is targeted to be fixed in next release R1.11.

Raj Reddy (rajreddy)
information type: Proprietary → Public
Jeba Paulaiyan (jebap)
Changed in juniperopenstack:
milestone: none → r3.2.0.0-fcs
Changed in juniperopenstack:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.