Bug 1221076 – python-neutron-fwaas rpm lacks db upgrade 'versions' directory

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

Bug 1221076 - python-neutron-fwaas rpm lacks db upgrade 'versions' directory

Summary:	python-neutron-fwaas rpm lacks db upgrade 'versions' directory

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openstack-neutron (Show other bugs)
Sub Component:
Version:	7.0 (Kilo)
Hardware:	Unspecified Unspecified

Priority	high Severity urgent
Target Milestone:	ga
Target Release:	7.0 (Kilo)
Assigned To:	lpeer
QA Contact:	Roey Dekel
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2015-05-13 05:23 EDT by Roey Dekel
Modified:	2016-04-26 23:38 EDT (History)
CC List:	8 users (show)

See Also:
Fixed In Version:	openstack-neutron-fwaas-2015.1.0-3.el7ost
Doc Type:	Known Issue
Doc Text:	Due to a known issue with the 'python-neutron-fwaas' package, Firewall-as-a-Service (FWaaS) may fail to work. This is a result of the 'python-neutron-fwaas' package missing the database upgrade 'versions' directory. In addition, upgrading the database schemas between version releases may not function correctly at this time.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-08-05 09:23:28 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 Roey Dekel 2015-05-13 05:23:02 EDT

Description of problem:
Tried to work with fwaas and got error as described below

Version-Release number of selected component (if applicable):
python-neutron-fwaas-2015.1.0-2.el7ost.noarch
openstack-neutron-fwaas-2015.1.0-2.el7ost.noarch

How reproducible:
3/3

Steps to Reproduce:
1. Install RHEL-OSP 7 via packstack
2. Try to work with fwaas

Actual results:
http://pastebin.test.redhat.com/282742

Additional info:
Same as Bug 1221034, but fwaas related

Fixed manually buy adding versions dir to db and use:
neutron-db-manage --service fwaas --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head

Comment 6 Roey Dekel 2015-06-10 08:13:45 EDT

Verified on Kilo with:

Version-Release number of selected component:
---------------------------------------------
Puddle: 2015-06-02.1
openstack-neutron-fwaas-2015.1.0-3.el7ost.noarch

Reproduce steps:
----------------
1. Install RHEL-OSP 7 via packstack
2. Fixed manually by using:
neutron-db-manage --service fwaas --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head

Results:
--------
As expected:
[root@controller ~(keystone_demo)]# neutron firewall-create policy1
Created a new firewall:
+--------------------+--------------------------------------+
| Field              | Value                                |
+--------------------+--------------------------------------+
| admin_state_up     | True                                 |
| description        |                                      |
| firewall_policy_id | f423b2af-8df4-4d72-994d-3ed1b24f8ab3 |
| id                 | bf87fb30-c294-4060-91fa-428bbf831112 |
| name               |                                      |
| router_ids         | fe56731b-90f3-4a57-b3a5-540794f6d187 |
| status             | PENDING_CREATE                       |
| tenant_id          | 69def02bcd2d431f972695541a5d4e2a     |
+--------------------+--------------------------------------+

Comment:
--------
db upgrade still needed in order to use fwaas

Comment 10 errata-xmlrpc 2015-08-05 09:23:28 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.