neutron rootwarp is not updated when neutron code changes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grenade |
Incomplete
|
Undecided
|
ZongKai LI |
Bug Description
A recent grenade test output for l3.filters in log:
http://
new CommandFilter is added in neutron patch:
https:/
as a compared, tempest update it, but grenade doesn't:
http://
### update ###
Based on recent mail-list discuss, we consider that as a common part of neutron code, filters under rootwrap.d shouldn't be considered as common configures. It make sense to make neutron rootwrap.d filters always be upgraded/updated when grenade test runs.
Date: Thu, 17 Dec 2015 10:46:47 -0700
From: Carl Baldwin <email address hidden>
To: "OpenStack Development Mailing List (not for usage questions)"
<email address hidden>
Subject: Re: [openstack-dev] [neutron][grenade] l3.filters fail to
update at test server
Message-ID:
<email address hidden>
Content-Type: text/plain; charset=UTF-8
On Thu, Dec 17, 2015 at 5:12 AM, Ihar Hrachyshka <email address hidden> wrote:
> I believe that we should always unconditionally update filters with new
> versions when doing upgrades. Filters should not actually be considered
> configuration files in the first place since they are tightly coupled with
> the code that triggers commands.
+1. I was actually very surprised to learn how this is handled and
had the same thought.
Carl
Changed in grenade: | |
assignee: | nobody → ZongKai LI (lzklibj) |
status: | New → In Progress |
description: | updated |
summary: |
- l3.filters is not updated when neutron code changes + neutron rootwarp is not updated when neutron code changes |
Change abandoned by Sean Dague (<email address hidden>) on branch: master /review. openstack. org/258758
Review: https:/
Reason: no updates for 11 months