[Yahoo-eng-team] [Bug 1584415] [NEW] Listing images with the created_at and updated_at filters fails if an operator is not specified

2016-05-21 Thread Castulo J. Martinez 
Public bug reported:

When listing images there are several optional parameters that can be
used to filter the list of images retrieved by the API. All those
optional parameters are documented in the API guide:
http://developer.openstack.org/api-ref-image-v2.html#listImages-v2. The
following two parameters are not working properly when used, the
created_at and the updated_at.

Before the Mitaka release a user could filter the list of images by
using the following options:

GET /v2/images?created_at=
GET /v2/images?updated_at=
 
Starting on the Mitaka release users can also use an operator (eq, neq, lt, 
lte, gt, gte) for comparison purposes when filtering images using the 
created_at or updated_at parameters. Something like:

GET /v2/images?created_at=:
GET /v2/images?updated_at=:

The problem is that starting on Mitaka, if the user tries to filter the
list of images by created_at and updated_at without using an operator
the API errors and fails to retrieve the list of images. This means that
the API is not backward compatible with Liberty for this operation.

The glance API should be able to work with backward compatibility with
Liberty when listing images using the created_at or updated_at filters.

Steps to recreate:

1) Using an environment with the Liberty release, try listing images
using the created_at parameter (filter). Example: GET
http://my_env:9292/v2/images?created_at=2016-05-20T20:53:15Z

Results: A list containing one image is successfully retrieved.

2) Using an environment with the Mitaka release try the same operation:
GET http://my_env:9292/v2/images?created_at=2016-05-20T20:53:15Z

Results: The API returns an error: 400 Bad Request . Bad "created_at"
query filter format. Use ISO 8601 DateTime notation.

The same API call should be consistent in both releases.

** Affects: glance
 Importance: Undecided
 Assignee: Castulo J. Martinez (castulo-martinez)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Castulo J. Martinez (castulo-martinez)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1584415

Title:
  Listing images with the created_at and updated_at filters fails if an
  operator is not specified

Status in Glance:
  New

Bug description:
  When listing images there are several optional parameters that can be
  used to filter the list of images retrieved by the API. All those
  optional parameters are documented in the API guide:
  http://developer.openstack.org/api-ref-image-v2.html#listImages-v2.
  The following two parameters are not working properly when used, the
  created_at and the updated_at.

  Before the Mitaka release a user could filter the list of images by
  using the following options:

  GET /v2/images?created_at=
  GET /v2/images?updated_at=
   
  Starting on the Mitaka release users can also use an operator (eq, neq, lt, 
lte, gt, gte) for comparison purposes when filtering images using the 
created_at or updated_at parameters. Something like:

  GET /v2/images?created_at=:
  GET /v2/images?updated_at=:

  The problem is that starting on Mitaka, if the user tries to filter
  the list of images by created_at and updated_at without using an
  operator the API errors and fails to retrieve the list of images. This
  means that the API is not backward compatible with Liberty for this
  operation.

  The glance API should be able to work with backward compatibility with
  Liberty when listing images using the created_at or updated_at
  filters.

  Steps to recreate:

  1) Using an environment with the Liberty release, try listing images
  using the created_at parameter (filter). Example: GET
  http://my_env:9292/v2/images?created_at=2016-05-20T20:53:15Z

  Results: A list containing one image is successfully retrieved.

  2) Using an environment with the Mitaka release try the same
  operation: GET
  http://my_env:9292/v2/images?created_at=2016-05-20T20:53:15Z

  Results: The API returns an error: 400 Bad Request . Bad "created_at"
  query filter format. Use ISO 8601 DateTime notation.

  The same API call should be consistent in both releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1584415/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1584350] [NEW] etc/glance-registry.conf sample file has redundant store section

2016-05-21 Thread Nikhil Komawar 
Public bug reported:

Currently, the oslo config generator takes glance_store configs in
consideration while generating sample configs for the registry. Registry
doesn't really need these configs.

It would be better to get them removed.

** Affects: glance
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1584350

Title:
  etc/glance-registry.conf sample file has redundant store section

Status in Glance:
  New

Bug description:
  Currently, the oslo config generator takes glance_store configs in
  consideration while generating sample configs for the registry.
  Registry doesn't really need these configs.

  It would be better to get them removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1584350/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1584347] [NEW] Flows can't generate when restarted ovs-agent

2016-05-21 Thread changzhi 
Public bug reported:

I deleted ovs bridge named 'br-int' by 'ovs-vsctl del-br br-int'. Then I
restart ovs-agent. Bridge 'br-int' was created by ovs-agent. But flows
can't generate by ovs-agent.

When I execute 'ovs-vsctl show', this is output:

[root@server-233 ~]# ovs-vsctl show
7b1afcdf-e1ca-4917-b97b-a53103b44dc3
Manager "ptcp:6640:127.0.0.1"
is_connected: true
Bridge br-int
fail_mode: secure
Port "tap1c3f7bf4-46"
Interface "tap1c3f7bf4-46"
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port br-int
Interface br-int
type: internal
Port "int-ovsbr3"
Interface "int-ovsbr3"
type: patch
options: {peer=nonexistent-peer}
Bridge "ovsbr3"
Port "phy-ovsbr3"
Interface "phy-ovsbr3"
type: patch
options: {peer=nonexistent-peer}
Port "ovsbr3"
Interface "ovsbr3"
type: internal
Bridge br-tun
fail_mode: secure
Port br-tun
Interface br-tun
type: internal
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
Port "qg-e84ab4c4-1a"
Interface "qg-e84ab4c4-1a"
type: internal
Port "fg-17319993-76"
Interface "fg-17319993-76"
type: internal
Port "p3p1.102"
Interface "p3p1.102"
ovs_version: "2.4.0"

** Affects: neutron
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1584347

Title:
  Flows can't generate when restarted ovs-agent

Status in neutron:
  New

Bug description:
  I deleted ovs bridge named 'br-int' by 'ovs-vsctl del-br br-int'. Then
  I restart ovs-agent. Bridge 'br-int' was created by ovs-agent. But
  flows can't generate by ovs-agent.

  When I execute 'ovs-vsctl show', this is output:

  [root@server-233 ~]# ovs-vsctl show
  7b1afcdf-e1ca-4917-b97b-a53103b44dc3
  Manager "ptcp:6640:127.0.0.1"
  is_connected: true
  Bridge br-int
  fail_mode: secure
  Port "tap1c3f7bf4-46"
  Interface "tap1c3f7bf4-46"
  type: internal
  Port patch-tun
  Interface patch-tun
  type: patch
  options: {peer=patch-int}
  Port br-int
  Interface br-int
  type: internal
  Port "int-ovsbr3"
  Interface "int-ovsbr3"
  type: patch
  options: {peer=nonexistent-peer}
  Bridge "ovsbr3"
  Port "phy-ovsbr3"
  Interface "phy-ovsbr3"
  type: patch
  options: {peer=nonexistent-peer}
  Port "ovsbr3"
  Interface "ovsbr3"
  type: internal
  Bridge br-tun
  fail_mode: secure
  Port br-tun
  Interface br-tun
  type: internal
  Port patch-int
  Interface patch-int
  type: patch
  options: {peer=patch-tun}
  Bridge br-ex
  Port br-ex
  Interface br-ex
  type: internal
  Port "qg-e84ab4c4-1a"
  Interface "qg-e84ab4c4-1a"
  type: internal
  Port "fg-17319993-76"
  Interface "fg-17319993-76"
  type: internal
  Port "p3p1.102"
  Interface "p3p1.102"
  ovs_version: "2.4.0"

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1584347/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1584333] [NEW] BGP code still exist in neutron repo

2016-05-21 Thread Na Zhu 
Public bug reported:

I find the etc/policy file still has code related with bgp.

https://github.com/openstack/neutron/blob/master/etc/policy.json#L223
https://github.com/openstack/neutron/blob/master/etc/policy.json#L224
https://github.com/openstack/neutron/blob/master/etc/policy.json#L226

** Affects: neutron
 Importance: Undecided
 Assignee: Na Zhu (nazhu)
 Status: New


** Tags: l3-bgp

** Changed in: neutron
 Assignee: (unassigned) => Na Zhu (nazhu)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1584333

Title:
  BGP code still exist in neutron repo

Status in neutron:
  New

Bug description:
  I find the etc/policy file still has code related with bgp.

  https://github.com/openstack/neutron/blob/master/etc/policy.json#L223
  https://github.com/openstack/neutron/blob/master/etc/policy.json#L224
  https://github.com/openstack/neutron/blob/master/etc/policy.json#L226

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1584333/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1556887] Re: Themes setting is not translated

2016-05-21 Thread Rob Cresswell 
It seems like the string is tranlatable, but this is an i18n issue.

** Changed in: horizon
   Status: Confirmed => Incomplete

** Also affects: openstack-i18n
   Importance: Undecided
   Status: New

** Changed in: horizon
   Status: Incomplete => Invalid

** Changed in: horizon
Milestone: newton-1 => None

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1556887

Title:
  Themes setting is not translated

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in openstack i18n:
  New

Bug description:
  The theme string should be translated. The screen shot is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1556887/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1580975] Re: Some actions are unclickable

2016-05-21 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/318444
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=a0088d1856337551995a8e9504aad773f4fa347c
Submitter: Jenkins
Branch:master

commit a0088d1856337551995a8e9504aad773f4fa347c
Author: Kenji Ishii 
Date:   Thu May 19 13:45:09 2016 +0900

Fix the issue that delete actions are unclickable

In detail page like volume, image and so on, delete action
is not clickable. Delete actions are set by the code below.

https://github.com/openstack/horizon/blob/master/horizon/static/horizon/js/horizon.forms.js#L366
However, because of the change below, these no longer match this selector.
https://review.openstack.org/#/c/284421/18
This patch will fix it so as to match the selector above.

Change-Id: Ia4ef05b8811c09dedeeb4c3349e989c4e3af5122
Closes-Bug: #1580975


** Changed in: horizon
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1580975

Title:
  Some actions are unclickable

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Originally I've got the issue with murano-dashboard with the following steps:
  1. Go to Murano - Application Catalog - Environments.
  2. Create a new environment, its detail view will open.
  3. Press "Delete environment".

  Expected result: environment is deleted.
  Actual result: nothing happens.

  Environments still can be deleted from the list of environments.
  The same with "Abandon environment" action.

  I can see that some actions (but not all) in other places in horizon are also 
unavailable.
  Unavailable actions that I see:
  - actions in the instance details view: shutoff, delete instance, reboot 
instance, pause instance, suspend, shelve, lock, unlock
  - delete image from its details view
  - delete volume
  - delete network
  - delete router
  - stack actions: check, resume, delete

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1580975/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp