date:20160615

Reviewed:  https://review.openstack.org/327413
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=db9e4048c4d134629d59f11ff004cbb8513e2b18
Submitter: Jenkins
Branch:master

commit db9e4048c4d134629d59f11ff004cbb8513e2b18
Author: Kevin Benton 
Date:   Wed Jun 8 05:53:28 2016 -0700

Remove MAC duplicate detection for generated macs

The previous MAC duplicate detection code relied on catching a
DBDuplicateError the correct time which resulted in two problems.
First, the duplicate could have been caused by something else being
flushed to the database at the same time.
Second, the DBDuplicate may not occur at flush time if the conflict
happens due to two concurrent port creations and it will instead
happen at commit time.

This patch just dumps the DBDuplicate catch to allow the API layer
to retry the operation since MAC collisions on a network should be
extremely rare.

Closes-Bug: #1590602
Change-Id: Idf816c07198be3ce745252ac9aa9c4aad8f11910


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

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

Title:
  duplicate mac detection is brittle

Status in neutron:
  Fix Released

Bug description:
  The duplicate mac detection logic is based on catching DBDuplicate
  exceptions at a very specific time. This results in incorrect
  classification if other things are waiting to be flushed which results
  in weird workarounds like
  
(https://review.openstack.org/#/c/292207/23/neutron/db/db_base_plugin_common.py).
  It also creates different behavior if the duplicate isn't realized
  until certification at COMMIT, at which point the retry decorator will
  restart the operation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1590602/+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 1592983] Re: callback can't unsubscribe itself in python3

Reviewed:  https://review.openstack.org/330209
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=2fbb6587df357583fe03b8616d7b95f79382af20
Submitter: Jenkins
Branch:master

commit 2fbb6587df357583fe03b8616d7b95f79382af20
Author: Kevin Benton 
Date:   Sat Jun 11 08:23:48 2016 -0700

Allow self-unsubscribing callbacks

This adjusts the notify loop logic to handle the case where
a callback causes a subscription or unsubscription that changes
the subscriber dictionary to change during iteration.

It was just using .items() which solved the problem for py27 but
was not creating an actual copy in py34. This just calls list()
on .items() to make sure we get a list in both cases.

Change-Id: Iee9d675faf30ec714b4f5c77128d8843d545ecfd
Closes-Bug: #1592983


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

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

Title:
  callback can't unsubscribe itself in python3

Status in neutron:
  Fix Released

Bug description:
  The callback manager uses .items() which is not a copy of the
  subscribers dict in python3. This means that a callback that wants to
  unsubscribe itself will die in python3 with an error:

  
 b'self.manager.notify(resources.PORT, events.BEFORE_CREATE, mock.ANY)'
  b'  File "/home/administrator/code/neutron/neutron/callbacks/manager.py", 
line 118, in notify'
  b'errors = self._notify_loop(resource, event, trigger, **kwargs)'
  b'  File "/home/administrator/code/neutron/neutron/callbacks/manager.py", 
line 143, in _notify_loop'
  b'for callback_id, callback in callbacks:'
  b'RuntimeError: dictionary changed size during iteration'
  b''

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1592983/+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 1593011] [NEW] missing iptales rules when set a network from down to up

2016-06-15 Thread xin wu

Public bug reported:

We are using liberty and running into following problem.
1. bring up a network, bring up the first vm, this vm gets its ip from dhcp.
2. set this network to down
3. bring up another vm, this vm won't get its ip address because the dhcp 
namespace doesn't have its ip address any more.
4. set the network to up, dhcp namesapce gets its ip (sometimes, it is a new ip)
5. reboot the second vm, the vm still won't get its ip address. The reason is 
because of missing an iptables rule.

the 2nd vm's iptables rule: (RETURN udp rule is missing)
[root@overcloud-compute-1 log]# iptables -L | grep neutron-bsn-agen-i1a81d969-0 
-A10
Chain neutron-bsn-agen-i1a81d969-0 (1 references)
target prot opt source   destination
RETURN all  --  anywhere anywhere state 
RELATED,ESTABLISHED /* Direct packets associated with a known session to the 
RETURN chain. */
RETURN all  --  anywhere anywhere match-set 
NIPv4d245ec59-449a-42eb-92ac- src
DROP   all  --  anywhere anywhere state INVALID /* 
Drop packets that appear related to an existing connection (e.g. TCP ACK/FIN) 
but do not have an entry in conntrack. */
neutron-bsn-agen-sg-fallback  all  --  anywhere anywhere
 /* Send unmatched traffic to the fallback chain. */


the 1st vm's iptables rule:
[root@overcloud-compute-1 log]# iptables -L | grep neutron-bsn-agen-i1b789c4c-b 
-A10
Chain neutron-bsn-agen-i1b789c4c-b (1 references)
target prot opt source   destination
RETURN all  --  anywhere anywhere state 
RELATED,ESTABLISHED /* Direct packets associated with a known session to the 
RETURN chain. */
RETURN udp  --  1.98.1.3 anywhere udp spt:bootps 
udp dpt:bootpc
RETURN all  --  anywhere anywhere match-set 
NIPv4d245ec59-449a-42eb-92ac- src
DROP   all  --  anywhere anywhere state INVALID /* 
Drop packets that appear related to an existing connection (e.g. TCP ACK/FIN) 
but do not have an entry in conntrack. */
neutron-bsn-agen-sg-fallback  all  --  anywhere anywhere
 /* Send unmatched traffic to the fallback chain. */

** 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/1593011

Title:
  missing iptales rules when set a network from down to up

Status in neutron:
  New

Bug description:
  We are using liberty and running into following problem.
  1. bring up a network, bring up the first vm, this vm gets its ip from dhcp.
  2. set this network to down
  3. bring up another vm, this vm won't get its ip address because the dhcp 
namespace doesn't have its ip address any more.
  4. set the network to up, dhcp namesapce gets its ip (sometimes, it is a new 
ip)
  5. reboot the second vm, the vm still won't get its ip address. The reason is 
because of missing an iptables rule.

  the 2nd vm's iptables rule: (RETURN udp rule is missing)
  [root@overcloud-compute-1 log]# iptables -L | grep 
neutron-bsn-agen-i1a81d969-0 -A10
  Chain neutron-bsn-agen-i1a81d969-0 (1 references)
  target prot opt source   destination
  RETURN all  --  anywhere anywhere state 
RELATED,ESTABLISHED /* Direct packets associated with a known session to the 
RETURN chain. */
  RETURN all  --  anywhere anywhere match-set 
NIPv4d245ec59-449a-42eb-92ac- src
  DROP   all  --  anywhere anywhere state INVALID 
/* Drop packets that appear related to an existing connection (e.g. TCP 
ACK/FIN) but do not have an entry in conntrack. */
  neutron-bsn-agen-sg-fallback  all  --  anywhere anywhere  
   /* Send unmatched traffic to the fallback chain. */

  
  the 1st vm's iptables rule:
  [root@overcloud-compute-1 log]# iptables -L | grep 
neutron-bsn-agen-i1b789c4c-b -A10
  Chain neutron-bsn-agen-i1b789c4c-b (1 references)
  target prot opt source   destination
  RETURN all  --  anywhere anywhere state 
RELATED,ESTABLISHED /* Direct packets associated with a known session to the 
RETURN chain. */
  RETURN udp  --  1.98.1.3 anywhere udp spt:bootps 
udp dpt:bootpc
  RETURN all  --  anywhere anywhere match-set 
NIPv4d245ec59-449a-42eb-92ac- src
  DROP   all  --  anywhere anywhere state INVALID 
/* Drop packets that appear related to an existing connection (e.g. TCP 
ACK/FIN) but do not have an entry in conntrack. */
  neutron-bsn-agen-sg-fallback  all  --  anywhere anywhere  
   /* Send unmatched traffic to the fallback chain. */

To manage notifications about this bug go to:
https://bugs.launchpad.net/neu

[Yahoo-eng-team] [Bug 1593001] [NEW] Horizon Workflows should be one experience

2016-06-15 Thread Diana Whitten

Public bug reported:

The experience of the legacy (Django) workflows and the modern (angular
based) workflows are drastically different.  They should be aligned.

** Affects: horizon
 Importance: Undecided
 Assignee: Diana Whitten (hurgleburgler)
 Status: In Progress

-- 
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/1593001

Title:
  Horizon Workflows should be one experience

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  The experience of the legacy (Django) workflows and the modern
  (angular based) workflows are drastically different.  They should be
  aligned.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1593001/+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 1580294] Re: Impossible to create another iSCSI volume after encrypted one was created

Marked as invalid, OP indicated they had resolved the issue.

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

** Changed in: cinder
   Status: New => Invalid

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

Title:
  Impossible to create another iSCSI volume after encrypted one was
  created

Status in Cinder:
  Invalid
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Description
  ===
  Tempest test for Cinder drivers which uses encrypted volumes fails. I figured 
out that test uses nova.volume.encryptors.cryptsetup.CryptsetupEncryptor.

  On setup it executes:
  cryptsetup create --key-file=- dev_name dev_path
  ln --symbolic --force /dev/mapper/dev_name symlink_path

  On remove:
  cryptsetup remove dev_name
  and it doesn't restore the link. When a driver deletes a volume and creates 
anoter one with the same name as previous, that link becomes broken and volume 
is not able to be working. When I manually replace the link with original one, 
it works fine.

  Steps to reproduce
  ==
  cd /opt/stack/tempest
  tox -eall -- --concurrency=1 test_encrypted_cinder_volumes_cryptsetup
  run the test twice

  Expected result
  ===
  the test passes every time

  Actual result
  =
  the test passes only the first time

  Environment
  ===
  I used devstack from master branch and Nexenta iSCSI driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1580294/+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 1570931] Re: Attach the Nova API log if possible." Keystoneclient.exceptions.BadRequest"

Marking this as invalid, it looks like the OP resolved their issue by
updating their configuration.

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

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

Title:
  Attach the Nova API log if possible."
  Keystoneclient.exceptions.BadRequest"

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  This bug occurs when a new instcacia is initialised at liberty
  OpenStack.

  In Horizon :

  The error message. "Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. ".
  I am using the recommended environment, and the official installation of 
OpenStack. A controller with network services. And two computers nodes.
  Also there are two networks created. One internal and one external.

  
  And 

  
  when i tried to initiate instance using following command;

  nova boot --flavor m1.tiny --image cirros --nic net-
  id=f2c94628-f774-43c7-9508-ee4cac175f1d --security-group default
  --key-name mykey public-instance

  it gives error;

  ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
   (HTTP 500) (Request-ID: 
req-2982939b-53e9-45df-a5e7-b2ceb2cf1f0c)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1570931/+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 1572055] Re: Run command "nova boot ..." raise "keystoneclient.exceptions.DiscoveryFailure"

Based on the limited information you've provided, this looks like a
configuration issue. If you need help configuring Keystone correctly,
please reach out to the OpenStack mailing list for support.

If this install worked previously and suddenly started displaying this
behavior, please feel free to reopen this bug. If you do reopen this
bug, please provide detailed information on what changed from when your
install worked to when it stopped working, including detailed steps to
reproduce if possible.

** Changed in: nova
   Status: Incomplete => New

** Changed in: nova
   Status: New => Invalid

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

Title:
  Run command "nova boot ..." raise
  "keystoneclient.exceptions.DiscoveryFailure"

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  [root@controller2 ~]# nova flavor-list
  
++---+---+--+---+--+---+-+---+
  | ID | Name  | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor 
| Is_Public |
  
++---+---+--+---+--+---+-+---+
  | 1  | m1.tiny   | 512   | 1| 0 |  | 1 | 1.0 
| True  |
  | 2  | m1.small  | 2048  | 20   | 0 |  | 1 | 1.0 
| True  |
  | 3  | m1.medium | 4096  | 40   | 0 |  | 2 | 1.0 
| True  |
  | 4  | m1.large  | 8192  | 80   | 0 |  | 4 | 1.0 
| True  |
  | 5  | m1.xlarge | 16384 | 160  | 0 |  | 8 | 1.0 
| True  |
  
++---+---+--+---+--+---+-+---+
  [root@controller2 ~]#  neutron net-list
  
+--+-+-+
  | id   | name| subnets
 |
  
+--+-+-+
  | dd38c21b-3ef0-4b67-8ccf-9d7f2d07c65b | public  | 
5680ce7d-f796-45f4-9eba-b2f3679412bb 10.0.20.0/24   |
  | 8858fa32-6c48-4bad-9c46-f435b1dee400 | private | 
7383ebeb-eb50-4e5d-8ae5-82ebfdb2ba03 192.168.8.0/24 |
  
+--+-+-+
  [root@controller2 ~]# nova boot --flavor m1.small --image cirros --nic 
net-id=8858fa32-6c48-4bad-9c46-f435b1dee400 --security-group default --key-name 
mykey private-instance
  ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
   (HTTP 500) (Request-ID: 
req-42bcb9bc-44db-4442-894e-79f6a5b98412)


  Here is some log in my nova-api.log:

  2016-04-19 17:38:19.998 2269 INFO nova.osapi_compute.wsgi.server 
[req-cc721bde-5e15-4b46-9ad1-37d15c9facc1 c647066b9fb248af85f3af547a1e4f9c 
d37e5a0f63564641b
  e9ffe65e3aed887 - - -] 10.0.20.12 "GET 
/v2/d37e5a0f63564641be9ffe65e3aed887/flavors?is_public=None HTTP/1.1" status: 
200 len: 1407 time: 0.0291429
  2016-04-19 17:38:20.028 2269 INFO nova.osapi_compute.wsgi.server 
[req-d8005687-7a32-42da-806c-6eb026f3a8d9 c647066b9fb248af85f3af547a1e4f9c 
d37e5a0f63564641b
  e9ffe65e3aed887 - - -] 10.0.20.12 "GET 
/v2/d37e5a0f63564641be9ffe65e3aed887/flavors/2 HTTP/1.1" status: 200 len: 618 
time: 0.0244541
  2016-04-19 17:38:27.751 2269 WARNING 
keystoneclient.auth.identity.generic.base 
[req-a1b416be-398e-4e13-8fd2-3308c4fa2826 c647066b9fb248af85f3af547a1e4f9c d37
  e5a0f63564641be9ffe65e3aed887 - - -] Discovering versions from the identity 
service failed when creating the password plugin. Attempting to determine 
version
   from URL.
  2016-04-19 17:38:27.752 2269 ERROR nova.api.openstack.extensions 
[req-a1b416be-398e-4e13-8fd2-3308c4fa2826 c647066b9fb248af85f3af547a1e4f9c 
d37e5a0f63564641b
  e9ffe65e3aed887 - - -] Unexpected exception in API method
  2016-04-19 17:38:27.752 2269 ERROR nova.api.openstack.extensions Traceback 
(most recent call last):
  2016-04-19 17:38:27.752 2269 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 478, 
in wra
  pped
  2016-04-19 17:38:27.752 2269 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
  2016-04-19 17:38:27.752 2269 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in 
wrapp
  er
  2016-04-19 17:38:27.752 2269 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
  2016-04-19 17:38:27.752 2269 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in 
wrapp
  er
  2016-04-19 17:38:27.752 2269 ERROR nova.api.openstack.extensi

[Yahoo-eng-team] [Bug 1553148] Re: Annotaion in rest create_user is confusing

Reviewed:  https://review.openstack.org/287704
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=16a471f6a7ca01016f18bcec0c11322eb77418c1
Submitter: Jenkins
Branch:master

commit 16a471f6a7ca01016f18bcec0c11322eb77418c1
Author: Bo Wang 
Date:   Thu Mar 3 18:35:48 2016 +0800

Clear confusing annotation in rest create_user

email should be None if not provided, ref[1]

[1] https://github.com/openstack/horizon/commit/
311bbd7d16451e53775d316d0e45e1b47711c358

Closes-Bug: #1553148
Change-Id: I0530a78f3b354f06b2d9608f5da7ce31ea80085b


** 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/1553148

Title:
  Annotaion in rest create_user is confusing

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  email is an optional argument, both '' and None could successfully create a 
new user with no email info. The difference is:
  If email=None, the value will be NULL in db.
  If email='', there is no value of email column in db.

  Clear current annotation "# not sure why email is forced to None, but
  other code does it"

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1553148/+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 1571142] Re: Unable to launch instance

Make sure you've got the latest version of oslo.messaging installed,
otherwise this is most likely a configuration issue. If you can get a
stack trace of the specific issue causing the timeout on the
oslo.messaging side, feel free to reopen this bug and provide that
information. Otherwise you can reach out to the OpenStack mailing list
to get help with setting up your OpenStack configuation.

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

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

Title:
  Unable to launch instance

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  I tried to launch an instance using the following 
  openstack server create --flavor m1.tiny --image cirros   --nic 
net-id=provider --security-group default   --key-name mykey provider-instance
  An exception was returned :2016-04-15 22:14:20.324 18294 ERROR 
nova.api.openstack.extensions [req-45fd4baf-2b19-46e3-9fdf-b19c0d01361e 
ab97d10635c04213bb9889845a601fa8 5a68df1d31e1433189a99e097fe65cfb - - -] 
Unexpected exception in API method
  I checked and listed the flavor, network, security to verify the values used 
in launching the instance and they are fine

  Steps to reproduce:
  Verify the following options are available

  rahmed@controller:~$ openstack network list

  +--+--+-+
  | ID   | Name | Subnets |
  +--+--+-+
  | dff6ba3d-d1d2-4e8a-b5f2-34fe1e7c685f | provider | |
  +--+--+-+
  rahmed@controller:~$ 
  rahmed@controller:~$ openstack security group list
  
+--+-++--+
  | ID   | Name| Description| 
Project  |
  
+--+-++--+
  | 01ac569e-8f63-4f12-ab88-13b0074d1a81 | default | Default security group | 
5a68df1d31e1433189a99e097fe65cfb |
  
+--+-++--+
  rahmed@controller:~$ openstack flavor list
  ++---+---+--+---+---+---+
  | ID | Name  |   RAM | Disk | Ephemeral | VCPUs | Is Public |
  ++---+---+--+---+---+---+
  | 0  | m1.nano   |64 |1 | 0 | 1 | True  |
  | 1  | m1.tiny   |   512 |1 | 0 | 1 | True  |
  | 2  | m1.small  |  2048 |   20 | 0 | 1 | True  |
  | 3  | m1.medium |  4096 |   40 | 0 | 2 | True  |
  | 4  | m1.large  |  8192 |   80 | 0 | 4 | True  |
  | 5  | m1.xlarge | 16384 |  160 | 0 | 8 | True  |
  ++---+---+--+---+---+---+
  rahmed@controller:~$ openstack image  list
  +--+++
  | ID   | Name   | Status |
  +--+++
  | d11d504e-9047-4487-94da-75cd620957ba | cirros | active |
  +--+++

  Actual Result:
  Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ 
and attach the Nova API log if possible.
   (HTTP 500) (Request-ID: 
req-8b87723d-61fa-472a-8e91-de29c45a497b)
  rahmed@controller:~$ openstack server create --flavor m1.tiny --image cirros  
 --nic net-id=provider --security-group default   --key-name mykey 
provider-instance

  Expected Result:
  $ openstack server list
  
+--+---++-+
  | ID   | Name  | Status | 
Networks|
  
+--+---++-+
  | 181c52ba-aebc-4c32-a97d-2e8e82e4eaaf | provider-instance | ACTIVE | 
provider=203.0.113.103 |
  
+--+---++-+



  
  Environment:
  ii  nova-api 2:13.0.0-0ubuntu2~cloud0 
 all  OpenStack Compute - API frontend
  ii  nova-cert2:13.0.0-0ubuntu2~cloud0 
 all  OpenStack Compute - certificate management
  ii  nova-common  2:13.0.0-0ubuntu2~cloud0 
 all  OpenStack Compute - common files
  ii  nova-conductor   2:13.0.0-0ubuntu2~cloud0 
 all  OpenStack Compute - conductor service
  ii  nova-consoleauth

[Yahoo-eng-team] [Bug 1588995] Re: JS error when loading Update Image Metadata modal

Reviewed:  https://review.openstack.org/325683
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=2e6e52851a38b6e576f1b98e1b3ae4380701789a
Submitter: Jenkins
Branch:master

commit 2e6e52851a38b6e576f1b98e1b3ae4380701789a
Author: Ying Zuo 
Date:   Fri Jun 3 16:13:01 2016 -0700

Fix JS error when loading metadata modal

Closes-bug: #1588995

Change-Id: I0c023a48149513b9f3fc585b02cfd4d597ba8993


** 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/1588995

Title:
  JS error when loading Update Image Metadata modal

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Steps to reproduce:

  1. create an image
  2. navigate to action tab and click on update metadata link
  3. add a simple metadata
  4. reopen the update image metadata modal
  5. note that there's a JS error on Firebug
   because the pattern is not a 
valid regexp: raw brace is not allowed in regular expression with unicode flag.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1588995/+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 1592349] Re: Page timeout in selenium integration tests is too small

Reviewed:  https://review.openstack.org/329369
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=eecb8bfe148cec0bd0afb471b7723fc5c57de4d8
Submitter: Jenkins
Branch:master

commit eecb8bfe148cec0bd0afb471b7723fc5c57de4d8
Author: Timur Sufiev 
Date:   Tue Jun 14 13:47:20 2016 +0300

Change default timeouts in integration tests

First, increase page_timeout to one minute, which should help in case
of a first couple of tests waiting for Apache workers to "warm up".

Second, reduce explicit_wait to 90 seconds (from 5 minutes), because
if something in Horizon doesn't complete in 90 seconds, then almost
for sure it won't complete in 5 minutes as well and only will spend
time, which is limited for integration tests.

Change-Id: Icb0767146fdb2682dca237ee18bbc4c3c8d976d0
Closes-Bug: #1592349


** 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/1592349

Title:
  Page timeout in selenium integration tests is too small

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The default page timeout in selenium integration tests is set to 30
  seconds, which is too small for a first couple of tests which are run
  after Apache in devstack is restarted. It takes around 30 seconds to
  just log in into Horizon, because a lot of data is fetched into the
  memory of Apache workers during these first tests, hence they time out
  and fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1592349/+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 1569739] Re: launch instance Error: Unable to create the server.

I've added Horizon to this bug and am marking invalid since everything
appears to be working correctly in Nova. If there is an issue the Nova
team needs to address, please provide those details and feel free to
reopen this issue for Nova.

** Also affects: horizon
   Importance: Undecided
   Status: New

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

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

Title:
  launch instance Error: Unable to create the server.

Status in OpenStack Dashboard (Horizon):
  New
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Trying to launch new instance from dashboard
  Fresh two centos 7 node installation
  http://docs.openstack.org/mitaka/install-guide-rdo/

  Error message: Error: Unable to create the server.

  Nova-api.log attachd

  
  1.
  openstack-nova-common-13.0.0-1.el7.noarch
  openstack-nova-conductor-13.0.0-1.el7.noarch
  python-novaclient-3.3.0-1.el7.noarch
  python-nova-13.0.0-1.el7.noarch
  openstack-nova-novncproxy-13.0.0-1.el7.noarch
  openstack-nova-cert-13.0.0-1.el7.noarch
  openstack-nova-api-13.0.0-1.el7.noarch
  openstack-nova-console-13.0.0-1.el7.noarch
  openstack-nova-scheduler-13.0.0-1.el7.noarch

  2.
  KVM

  3.
  Neutron

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1569739/+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 1563029] Re: Nova instance fail to launch: "Unexpected API Error."

Marking this bug as invalid for Nova. If this turns out to be a Nova
specific issue, please file a new bug with Nova specific information
(including reproduction steps) and reference this one.

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

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

Title:
  Nova instance fail to launch: "Unexpected API Error."

Status in kolla:
  Confirmed
Status in kolla mitaka series:
  Confirmed
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  This is a Kolla installation of openstack. The docker images build
  well and some services work great; e.g cinder, glance and neutron.

  Nova seems to have a problem that is prevent provisioning instances.
  The manila-api logs below says:

  "Returning 500 to user: Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
   __call__ 
/usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py:1070"


  1. The GIT commit level is:

  lsorrillo@ptest:~/git/kolla$ git log -1
  commit 90321d0497f14bda370908610cfc44296a940523
  Merge: 328a7e8 a789346
  Author: Jenkins 
  Date:   Sun Mar 27 23:42:47 2016 +

  Merge "Fix gate to use world writeable docker socket"
  lsorrillo@ptest:~/git/kolla$

  RPM version:

  lsorrillo@ptest:~$
  lsorrillo@ptest:~$ docker exec -ti nova_api bash
  bash-4.2$
  bash-4.2$
  bash-4.2$
  bash-4.2$ rpm -qa | grep nova
  python-novaclient-3.3.1-0.20160303082753.d63800d.el7.centos.noarch
  openstack-nova-common-13.0.0.0b4-0.20160304162843.c5a45a2.el7.centos.noarch
  python-nova-13.0.0.0b4-0.20160304162843.c5a45a2.el7.centos.noarch
  openstack-nova-api-13.0.0.0b4-0.20160304162843.c5a45a2.el7.centos.noarch
  bash-4.2$

  2.

  The following error is seen in the nova-api.log:

  2016-03-28 19:53:40.086 29 DEBUG oslo.messaging._drivers.impl_rabbit 
[req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 
9e4b40d958e741599adc497b0a9d955a - - -] Connecting to AMQP server on 
192.168.0.121:5672 __init__ 
/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:535
  2016-03-28 19:53:40.132 29 DEBUG oslo.messaging._drivers.impl_rabbit 
[req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 
9e4b40d958e741599adc497b0a9d955a - - -] Connected to AMQP server on 
192.168.0.121:5672 via [amqp] client __init__ 
/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:562
  2016-03-28 19:53:40.148 29 DEBUG oslo.messaging._drivers.pool 
[req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 
9e4b40d958e741599adc497b0a9d955a - - -] Pool creating new connection create 
/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/pool.py:109
  2016-03-28 19:53:40.151 29 DEBUG oslo.messaging._drivers.impl_rabbit 
[req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 
9e4b40d958e741599adc497b0a9d955a - - -] Connecting to AMQP server on 
192.168.0.121:5672 __init__ 
/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:535
  2016-03-28 19:53:40.205 29 DEBUG oslo.messaging._drivers.impl_rabbit 
[req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 
9e4b40d958e741599adc497b0a9d955a - - -] Connected to AMQP server on 
192.168.0.121:5672 via [amqp] client __init__ 
/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py:562
  2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions 
[req-88ffb6f7-1b1f-4332-b066-5b0b41827988 5bd4af0c54a14a789661d868a9fb1d84 
9e4b40d958e741599adc497b0a9d955a - - -] Unexpected exception in API method
  2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions Traceback 
(most recent call last):
  2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 478, 
in wrapped
  2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
  2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in 
wrapper
  2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
  2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in 
wrapper
  2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
  2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in 
wrapper
  2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
  2016-03-28 19:54:40.216 29 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packa

[Yahoo-eng-team] [Bug 1543010] Re: Nova clears DB if ESX nova-compute node restarted

It's been almost 3 months with no activity on this issue. I'm closing
this out as we don't have enough information to reproduce it. Please
feel free to reopen this bug or file a new one once you are able to
provide us with the additional information we've requested.

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

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

Title:
  Nova clears DB if ESX nova-compute node restarted

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  I had 12 ESX nova-compute cluster with 100 ESX hypervisor. For some reason 
one of nova-compute node went down.
  After couple of attempt nova-compute came up fine. But,

  1. Nova deleted all the instances running on that particular( esx-compute11) 
from its DB
  2. All the instances were deleted from the backend as well.

  Filing this bug to track if there is any issue with nova scheduler on
  ESX setup.

  Logs:

  stack@runner:~/nsbu_cqe_openstack/nested$ nova service-list | grep 
nova-compute | grep esx
  | 6 | nova-compute | esx-compute2 | nova | enabled | up | 
2016-02-03T09:45:15.00 | - |
  | 7 | nova-compute | esx-compute1 | nova | enabled | up | 
2016-02-03T09:45:17.00 | - |
  | 8 | nova-compute | esx-compute4 | nova | enabled | up | 
2016-02-03T09:45:18.00 | - |
  | 9 | nova-compute | esx-compute3 | nova | enabled | up | 
2016-02-03T09:45:21.00 | - |
  | 10 | nova-compute | esx-compute8 | nova | enabled | up | 
2016-02-03T09:45:20.00 | - |
  | 11 | nova-compute | esx-compute7 | nova | enabled | up | 
2016-02-03T09:45:19.00 | - |
  | 12 | nova-compute | esx-compute12 | nova | enabled | up | 
2016-02-03T09:45:19.00 | - |
  | 13 | nova-compute | esx-compute5 | nova | enabled | up | 
2016-02-03T09:45:19.00 | - |
  | 14 | nova-compute | esx-compute9 | nova | enabled | up | 
2016-02-03T09:45:17.00 | - |
  | 15 | nova-compute | esx-compute6 | nova | enabled | up | 
2016-02-03T09:45:19.00 | - |
  | 16 | nova-compute | esx-compute10 | nova | enabled | up | 
2016-02-03T09:45:20.00 | - |
  | 17 | nova-compute | esx-compute11 | nova | enabled | down | 
2016-02-03T09:26:53.00 | - |
  stack@runner:~/nsbu_cqe_openstack/nested$

  
  stack@controller:~$ sudo netstat -anp | grep 62.24.1.87
  tcp6 0 0 62.24.1.111:5672 62.24.1.87:58180 ESTABLISHED 8687/beam.smp
  tcp6 0 0 62.24.1.111:5672 62.24.1.87:58179 ESTABLISHED 8687/beam.smp
  stack@controller:~$

  
  2016-02-03 01:27:03.217 INFO nova.service [-] Starting compute node (version 
13.0.0)
  Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 
457, in fire_timers
  timer()
File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/timer.py", line 
58, in __call__
  cb(*args, **kw)
File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 
214, in main
  result = function(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/oslo_service/service.py", line 
671, in run_service
  service.start()
File "/opt/stack/nova/nova/service.py", line 183, in start
  self.manager.init_host()
File "/opt/stack/nova/nova/compute/manager.py", line 1313, in init_host
  context, self.host, expected_attrs=['info_cache', 'metadata'])
File 
"/usr/local/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 
172, in wrapper
  args, kwargs)
File "/opt/stack/nova/nova/conductor/rpcapi.py", line 241, in 
object_class_action_versions
  args=args, kwargs=kwargs)
File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/client.py", 
line 158, in call
  retry=self.retry)
File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/transport.py", 
line 90, in _send
  timeout=timeout, retry=retry)
File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py", 
line 464, in send
  retry=retry)
File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py", 
line 453, in _send
  result = self._waiter.wait(msg_id, timeout)
File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py", 
line 336, in wait
  message = self.waiters.get(msg_id, timeout=timeout)
File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py", 
line 239, in get
  'to message ID %s' % msg_id)
  MessagingTimeout: Timed out waiting for a reply to message ID 
5a19ba4d2a694453b5db95fb2f73f9e8
  2016-02-03 01:28:58.448 INFO oslo_messaging._drivers.amqpdriver [-] No 
calling threads waiting for msg_id : 5a19ba4d2a694453b5db95fb2f73f9e8

  
  Logs:

  M-Release, master branch

  stack@esx-compute3:/opt/stack/nova$ git log -1
  commit 197bd6dd1231f1f57cdd6c0acb1dfbdc3b2b0989
  Merge: 1ec0b56 5f5590f
  Author: Jenkins 
  Date:   Sun Feb 7 04:08:54 2016 +

  Mer

[Yahoo-eng-team] [Bug 1561310] Re: dashboard displays wrong quotas

Marking this as invalid for Nova per last comment.

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

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

Title:
  dashboard displays wrong quotas

Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  1. User try to  boot a new vm by click the button "+ Launch Instance"  in 
dashboard web->project->compute->instances.
  2. But the button "+ Launch Instance"  is disabled and shows "quota exceeded".
  3. Then user go to dashboard web->project->compute->overview perspective, but 
find Instances,VCPU and RAM haven't exceed 
  the quotas. In this case, it's shows like below:
  Instances
  Used 8 of 10
  VCPUs
  Used 18 of 20
  RAM
  Used 512MB of 50.0GB 
  This will confuse the user, is there anything incorrect?

  root cause: 
  I think one of the root cause is that the current project have another work, 
such as rebuilding vm, which obtail some quotas and mark
  the 'reserved' fields(nova->quota_usages table) to a none zero value .
  So I select *  from nova.quota_usages where project_id = 'current project 
id', and find thati in  the row 'cores' , the 'reserved' = 2. Because of this,  
the VCPU is actually Used 10 of 10. 
  Excepted result:
  The 'reserved' quota should also be taken as an used quota ,and so in 
dashboard web->project->compute->overview perspectiv, it should shows as below:
  VCPUs
  Used 20 of 20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1561310/+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 1562670] Re: nova set-password returns confusing error message

While I agree the message wording comes across awkward, the message is
vague by design to avoid revealing password information to the API
caller. There will be more useful information in your logs. If you are
unable to troubleshoot the issue after checking your logs and believe
this is a bug, please feel free to reopen this issue.

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

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

Title:
  nova set-password returns confusing error message

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  1). i had create an instance
  # nova list
  
+--+---+++-+-+
  | ID   | Name  | Status | Task State | Power 
State | Networks|
  
+--+---+++-+-+
  | 40c65eed-7339-4a3a-a838-0c564bc78bcd | test1 | ACTIVE | -  | 
Running | private=10.0.0.25, fd28:29fc:e927:0:f816:3eff:fe36:3666 |
  
+--+---+++-+-+

  2). and i forget the password.So, i have to reset the password for my instance
  # nova set-password 40c65eed-7339-4a3a-a838-0c564bc78bcd
  New password: 
  Again: 
  ERROR (Conflict): Failed to set admin password on 
40c65eed-7339-4a3a-a838-0c564bc78bcd because error setting admin password (HTTP 
409) (Request-ID: req-4bfdc3c7-058d-4742-a414-ee1f99698f68)

  at the end, i get the 409 return code.
  should i do other things before i change the password?? or this is a bug?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1562670/+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 1592985] [NEW] Instance snapshots no longer filterable

2016-06-15 Thread Travis Tripp

Public bug reported:

Nova has historically set image_type to snapshot when creating
snapshots. This is a custom property (not a core glance property). This
property is ONLY set if the image is of type snapshot.

Horizon uses this property to filter for snapshots using the Glance
client and we were also adding support for it in Searchlight [0]

Using a devstack as of Jun 13th, 2016 I can not seem to get nova to
create a snapshot where that image_type property is set.  I've tried
this from CLI and horizon.

Whenever I create the snapshot from the instance it comes through as an
image initially. Sometimes it seems to stay and sometimes it immediately
goes to the deleted state.

[0] https://bugs.launchpad.net/searchlight/+bug/1569485
[1] https://review.openstack.org/#/c/317741/

I need help in verifying that this is in fact a bug (confirm that
behavior has changed) and if so, then we need to consider the
ramifications.

** Affects: horizon
 Importance: Undecided
 Status: New

** Description changed:

-- 
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/1592985

Title:
  Instance snapshots no longer filterable

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Nova has historically set image_type to snapshot when creating
  snapshots. This is a custom property (not a core glance property).
  This property is ONLY set if the image is of type snapshot.

  Horizon uses this property to filter for snapshots using the Glance
  client and we were also adding support for it in Searchlight [0]

  Using a devstack as of Jun 13th, 2016 I can not seem to get nova to
  create a snapshot where that image_type property is set.  I've tried
  this from CLI and horizon.

  Whenever I create the snapshot from the instance it comes through as
  an image initially. Sometimes it seems to stay and sometimes it
  immediately goes to the deleted state.

  [0] https://bugs.launchpad.net/searchlight/+bug/1569485
  [1] https://review.openstack.org/#/c/317741/

  I need help in verifying that this is in fact a bug (confirm that
  behavior has changed) and if so, then we need to consider the
  ramifications.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1592985/+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 1592982] [NEW] Cannot create password-authenticated BGP peer

2016-06-15 Thread Paulo Matias

Public bug reported:

When trying to create a password-authenticated BGP peer, it fails with
an error message in the log (below).

Step-by-step reproduction steps:

neutron bgp-peer-create --peer-ip 2001:db8::1 --remote-as 65001 --auth-
type md5 --password plaintext bgp-peer1

Actual output:

2016-06-10 15:59:00.329 3181 ERROR ryu.lib.hub [-] hub: uncaught exception: 
Traceback (most recent call last):
  File 
"/openstack/venvs/neutron-13.1.2/lib/python2.7/site-packages/ryu/lib/hub.py", 
line 52, in _launch
func(*args, **kwargs)
  File 
"/openstack/venvs/neutron-13.1.2/lib/python2.7/site-packages/ryu/services/protocols/bgp/peer.py",
 line 1072, in _connect_loop
password=password)
  File 
"/openstack/venvs/neutron-13.1.2/lib/python2.7/site-packages/ryu/services/protocols/bgp/base.py",
 line 411, in _connect_tcp
sockopt.set_tcp_md5sig(sock, peer_addr[0], password)
  File 
"/openstack/venvs/neutron-13.1.2/lib/python2.7/site-packages/ryu/lib/sockopt.py",
 line 69, in set_tcp_md5sig
impl(s, addr, key)
  File 
"/openstack/venvs/neutron-13.1.2/lib/python2.7/site-packages/ryu/lib/sockopt.py",
 line 41, in _set_tcp_md5sig_linux
tcp_md5sig = ss + struct.pack("2xH4x80s", len(key), key)
error: argument for 's' must be a string

Version: stable/mitaka deployed with OpenStack-Ansible on Ubuntu Trusty

Environment: multi-node

Pre-conditions: Add init script for BGP DrAgent (does not come by
default with the OSA deployment)

Perceived severity: Blocks usage of authenticated BGP. Unauthenticated
BGP still works.

Comments:

The database model returns (get_bgp_peer) the password as an unicode
string, which is passed around until it reaches the Ryu library, causing
the error shown in the stacktrace above.

I tried to follow the Neutron codebase's standard solution to deal with
this. Several places do encode unicode strings which have been read from
the database before passing them around, e.g.:

neutron/agent/linux/utils.py:if isinstance(dev, six.text_type):
neutron/agent/linux/utils.py-dev = dev.encode('utf-8')
--
neutron/agent/metadata/agent.py:if isinstance(secret, six.text_type):
neutron/agent/metadata/agent.py-secret = secret.encode('utf-8')
neutron/agent/metadata/agent.py:if isinstance(instance_id, 
six.text_type):
neutron/agent/metadata/agent.py-instance_id = 
instance_id.encode('utf-8')

The attached patch fixes this issue (tested and working on
stable/mitaka) using the same strategy. Should I open a review request
for that in gerrit?

Thanks

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: l3-bgp

** Patch added: "bgp_dragent_password_encode.diff"
   
https://bugs.launchpad.net/bugs/1592982/+attachment/4684533/+files/bgp_dragent_password_encode.diff

** Description changed:

  When trying to create a password-authenticated BGP peer, it fails with
  an error message in the log (below).
  
  Step-by-step reproduction steps:
  
  neutron bgp-peer-create --peer-ip 2001:db8::1 --remote-as 65001 --auth-
  type md5 --password plaintext bgp-peer1
  
  Actual output:
  
  2016-06-10 15:59:00.329 3181 ERROR ryu.lib.hub [-] hub: uncaught exception: 
Traceback (most recent call last):
-   File 
"/openstack/venvs/neutron-13.1.2/lib/python2.7/site-packages/ryu/lib/hub.py", 
line 52, in _launch
- func(*args, **kwargs)
-   File 
"/openstack/venvs/neutron-13.1.2/lib/python2.7/site-packages/ryu/services/protocols/bgp/peer.py",
 line 1072, in _connect_loop
- password=password)
-   File 
"/openstack/venvs/neutron-13.1.2/lib/python2.7/site-packages/ryu/services/protocols/bgp/base.py",
 line 411, in _connect_tcp
- sockopt.set_tcp_md5sig(sock, peer_addr[0], password)
-   File 
"/openstack/venvs/neutron-13.1.2/lib/python2.7/site-packages/ryu/lib/sockopt.py",
 line 69, in set_tcp_md5sig
- impl(s, addr, key)
-   File 
"/openstack/venvs/neutron-13.1.2/lib/python2.7/site-packages/ryu/lib/sockopt.py",
 line 41, in _set_tcp_md5sig_linux
- tcp_md5sig = ss + struct.pack("2xH4x80s", len(key), key)
+   File 
"/openstack/venvs/neutron-13.1.2/lib/python2.7/site-packages/ryu/lib/hub.py", 
line 52, in _launch
+ func(*args, **kwargs)
+   File 
"/openstack/venvs/neutron-13.1.2/lib/python2.7/site-packages/ryu/services/protocols/bgp/peer.py",
 line 1072, in _connect_loop
+ password=password)
+   File 
"/openstack/venvs/neutron-13.1.2/lib/python2.7/site-packages/ryu/services/protocols/bgp/base.py",
 line 411, in _connect_tcp
+ sockopt.set_tcp_md5sig(sock, peer_addr[0], password)
+   File 
"/openstack/venvs/neutron-13.1.2/lib/python2.7/site-packages/ryu/lib/sockopt.py",
 line 69, in set_tcp_md5sig
+ impl(s, addr, key)
+   File 
"/openstack/venvs/neutron-13.1.2/lib/python2.7/site-packages/ryu/lib/sockopt.py",
 line 41, in _set_tcp_md5sig_linux
+ tcp_md5sig = ss + struct.pack("2xH4x80s", len(key), key)
  error: argument for 's' must be a string
  
  Version: stable/mitaka deployed with OpenStack-Ansible on Ubuntu Trusty

[Yahoo-eng-team] [Bug 1592983] [NEW] callback can't unsubscribe itself in python3

2016-06-15 Thread Kevin Benton

Public bug reported:

The callback manager uses .items() which is not a copy of the
subscribers dict in python3. This means that a callback that wants to
unsubscribe itself will die in python3 with an error:


   b'self.manager.notify(resources.PORT, events.BEFORE_CREATE, mock.ANY)'
b'  File "/home/administrator/code/neutron/neutron/callbacks/manager.py", 
line 118, in notify'
b'errors = self._notify_loop(resource, event, trigger, **kwargs)'
b'  File "/home/administrator/code/neutron/neutron/callbacks/manager.py", 
line 143, in _notify_loop'
b'for callback_id, callback in callbacks:'
b'RuntimeError: dictionary changed size during iteration'
b''

** Affects: neutron
 Importance: Low
 Assignee: Kevin Benton (kevinbenton)
 Status: In Progress

** Changed in: neutron
 Assignee: (unassigned) => Kevin Benton (kevinbenton)

** Changed in: neutron
   Importance: Undecided => Low

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

Title:
  callback can't unsubscribe itself in python3

Status in neutron:
  In Progress

Bug description:
  The callback manager uses .items() which is not a copy of the
  subscribers dict in python3. This means that a callback that wants to
  unsubscribe itself will die in python3 with an error:

  
 b'self.manager.notify(resources.PORT, events.BEFORE_CREATE, mock.ANY)'
  b'  File "/home/administrator/code/neutron/neutron/callbacks/manager.py", 
line 118, in notify'
  b'errors = self._notify_loop(resource, event, trigger, **kwargs)'
  b'  File "/home/administrator/code/neutron/neutron/callbacks/manager.py", 
line 143, in _notify_loop'
  b'for callback_id, callback in callbacks:'
  b'RuntimeError: dictionary changed size during iteration'
  b''

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1592983/+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 1526818] Re: Incorrect and excess ARP responses in tenant subnets

Thanks Michael! I'm going to close this out for Nova, and add this as an
issue to the doc team to update that documentation.

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

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

** Summary changed:

- Incorrect and excess ARP responses in tenant subnets
+ Install guide should suggest  net.ipv4.conf.all.arp_ignore=1

** Summary changed:

- Install guide should suggest  net.ipv4.conf.all.arp_ignore=1
+ Install guide should suggest enabling arp_ignore in sysctl.conf with the 
other IP options

** Summary changed:

- Install guide should suggest enabling arp_ignore in sysctl.conf with the 
other IP options
+ Install guide: Add arp_ignore (sysctl.conf) to the other IP options

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

Title:
  Install guide: Add arp_ignore (sysctl.conf) to the other IP options

Status in neutron:
  New
Status in OpenStack Compute (nova):
  Invalid
Status in openstack-manuals:
  New

Bug description:
  We are facing a very strange behaviour of ARP in tenant networks,
  causing Windows guests to incorrectly decline DHCP addresses. These
  VMs apparently do an ARP request for the address they have been
  offered, discarding them in case a different MAC is reporting to own
  that IP already.

  We are using openvswitch-agent with ml2 plugin.

  Investigating this issue using Linux guests. Please look at the
  following example. A VM with the fixed-ip 192.168.1.15 reports the
  following ARP cache:

 root@michael-test2:~# arp
 Address  HWtype  HWaddress   Flags Mask
Iface
 host-192-168-1-2.openst  ether   fa:16:3e:de:ab:ea   C 
eth0
 192.168.1.13 ether   a6:b2:dc:d8:39:c1   C 
eth0
 192.168.1.119(incomplete)  
eth0
 host-192-168-1-20.opens  ether   fa:16:3e:76:43:ce   C 
eth0
 host-192-168-1-19.opens  ether   fa:16:3e:0d:a6:0b   C 
eth0
 host-192-168-1-1.openst  ether   fa:16:3e:2a:81:ff   C 
eth0
 192.168.1.14 ether   0e:bf:04:b7:ed:52   C 
eth0
 
  Both 192.168.1.13 and 192.168.1.14 do not exist in this subnet, and their MAC 
addresses a6:b2:dc:d8:39:c1 and 0e:bf:04:b7:ed:52 actually belong to other 
instance qbr* and qvb* devices, living on their respective hypervisor hosts!

  Looking at 0e:bf:04:b7:ed:52, for example, yields

 # ip link list | grep -C1 -e 0e:bf:04:b7:ed:52
 59: qbr9ac24ac1-e1:  mtu 1500 qdisc 
noqueue state UP mode DEFAULT group default 
 link/ether 0e:bf:04:b7:ed:52 brd ff:ff:ff:ff:ff:ff
 60: qvo9ac24ac1-e1:  mtu 1500 
qdisc pfifo_fast master ovs-system state UP mode DEFAULT group default qlen 1000
 --
 61: qvb9ac24ac1-e1:  mtu 1500 
qdisc pfifo_fast master qbr9ac24ac1-e1 state UP mode DEFAULT group default qlen 
1000
 link/ether 0e:bf:04:b7:ed:52 brd ff:ff:ff:ff:ff:ff
 62: tap9ac24ac1-e1:  mtu 1500 qdisc 
pfifo_fast master qbr9ac24ac1-e1 state UNKNOWN mode DEFAULT group default qlen 
500

  on the compute node. Using tcpdump on qbr9ac24ac1-e1 on the host and
  triggering a fresh ARM lookup from the guest results in

 # tcpdump -i qbr9ac24ac1-e1 -vv -l | grep ARP
 tcpdump: WARNING: qbr9ac24ac1-e1: no IPv4 address assigned
 tcpdump: listening on qbr9ac24ac1-e1, link-type EN10MB (Ethernet), capture 
size 65535 bytes
 14:00:32.089726 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
192.168.1.14 tell 192.168.1.15, length 28
 14:00:32.089740 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.1.14 
is-at 0e:bf:04:b7:ed:52 (oui Unknown), length 28
 14:00:32.090141 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.1.14 
is-at 7a:a5:71:63:47:94 (oui Unknown), length 28
 14:00:32.090160 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.1.14 
is-at 02:f9:33:d5:04:0d (oui Unknown), length 28
 14:00:32.090168 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.1.14 
is-at 9a:a0:46:e4:03:06 (oui Unknown), length 28

  Four different devices are claiming to own the non-existing IP
  address! Looking them up in neutron shows they are all related to
  existing ports on the subnet, but different ones:

 # neutron port-list | grep -e 47fbb8b5-55 -e 46647cca-32 -e e9e2d7c3-7e -e 
9ac24ac1-e1
 | 46647cca-3293-42ea-8ec2-0834e19422fa |   
| fa:16:3e:7d:9c:45 | {"subnet_id": 
"25dbbdc0-f438-4f89-8663-1772f9c7ef36", "ip_address": "192.168.1.8"}   |
 | 47fbb8b5-5549-46e4-850e-bd382375e0f8 |   
| fa:16:3e:fa:df:32 | {"subnet_id": 
"25dbbdc0-f438-4f89-8663-1772f9c7ef36", "ip_address": "192.168.1.7"}   |
 | 9ac24ac1-e157-484e-b6a2-a1dded4731ac |

[Yahoo-eng-team] [Bug 1502472] Re: deprecate OPENSTACK_TOKEN_HASH_ENABLED

Reviewed:  https://review.openstack.org/284845
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=bf9ad6048dc3b776338339d6c062661308011dfe
Submitter: Jenkins
Branch:master

commit bf9ad6048dc3b776338339d6c062661308011dfe
Author: Brad Pokorny 
Date:   Wed Feb 24 03:23:10 2016 -0800

Deprecate the OPENSTACK_TOKEN_HASH_ENABLED option

Hashing PKI tokens is now working again, and Keystone will soon
deprecate usage of PKI tokens. Remove this option, as it's now
superfluous.

Change-Id: Ie67000ac20915ac12056a1a0aed13f6731a1c3c9
Closes-Bug: #1502472


** 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/1502472

Title:
  deprecate OPENSTACK_TOKEN_HASH_ENABLED

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  I was going through all the configuration parameters in Horizon and I
  came across the description of OPENSTACK_TOKEN_HASH_ENABLED. It
  mentions that token hashing for PKI tokens is broken. I filed a bug a
  while ago that has since been resolved:

  https://bugs.launchpad.net/django-openstack-auth/+bug/1486745

  This bug was resolved as a duplicate of:

  https://bugs.launchpad.net/bugs/1484499

  But my bug report had an explanation of the root cause, which seems to
  correlate with the underlying reason for this parameter. Since the bug
  has been resolved I believe this parameter is no longer needed.

  bpokorny: We need the fix for this bug as well for PKI to work
  completely:

  https://bugs.launchpad.net/django-openstack-auth/+bug/1487372

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1502472/+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 1592963] [NEW] Showing server details on a deleted instance fails for >=v2.26

2016-06-15 Thread Matt Riedemann

Public bug reported:

This failed in a python-novaclient functional CI run for newton (current
master):

http://logs.openstack.org/11/328211/5/gate/gate-novaclient-dsvm-
functional/cd6a3d2/logs/screen-n-api.txt.gz?level=TRACE

2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions 
[req-7b05c7c9-153d-4571-9d56-5a421159af1a admin admin] Unexpected exception in 
API method
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions Traceback 
(most recent call last):
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/api/openstack/extensions.py", line 453, in wrapped
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/api/openstack/compute/servers.py", line 543, in show
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions return 
self._view_builder.show(req, instance)
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/api/openstack/compute/views/servers.py", line 317, in 
show
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions 
server["server"]["tags"] = [t.tag for t in instance.tags]
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions   File 
"/usr/local/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 
67, in getter
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions 
self.obj_load_attr(name)
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/objects/instance.py", line 985, in obj_load_attr
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions 
self._load_generic(attrname)
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/objects/instance.py", line 765, in _load_generic
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions 
expected_attrs=[attrname])
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions   File 
"/usr/local/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 
181, in wrapper
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions result = 
fn(cls, context, *args, **kwargs)
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/objects/instance.py", line 416, in get_by_uuid
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions 
use_slave=use_slave)
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/db/sqlalchemy/api.py", line 225, in wrapper
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/objects/instance.py", line 408, in 
_db_instance_get_by_uuid
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions 
columns_to_join=columns_to_join)
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/db/api.py", line 692, in instance_get_by_uuid
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions return 
IMPL.instance_get_by_uuid(context, uuid, columns_to_join)
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/db/sqlalchemy/api.py", line 169, in wrapper
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/db/sqlalchemy/api.py", line 270, in wrapped
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions return 
f(context, *args, **kwargs)
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/db/sqlalchemy/api.py", line 1814, in 
instance_get_by_uuid
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions 
columns_to_join=columns_to_join)
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/db/sqlalchemy/api.py", line 1823, in 
_instance_get_by_uuid
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions raise 
exception.InstanceNotFound(instance_id=uuid)
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions 
InstanceNotFound: Instance a7c3ed25-c0dd-47a9-8eb5-b268dd0c3ad4 could not be 
found.
2016-06-15 19:42:01.313 12360 ERROR nova.api.openstack.extensions 

The test is waiting for the server to be deleted. It blows up here
because we didn't lazy-load the instance tags:

https://github.com/openstack/nova/blob/537df23d85e0f7c461643efe6b6501d267ae99d0/nova/api/openstack/compute/views/servers.py#L316

And because we don't handle lazy-loading 'tags' specifically it does the
load-generic with a join on the tags table, but the instance is

[Yahoo-eng-team] [Bug 1592965] [NEW] i18n: babel_extract_angular should trim whitespaces in AngularJS templates

2016-06-15 Thread Akihiro Motoki

Public bug reported:

This is "AngularJS templates" version of bug 1583757.

At now, translators will get source strings with meaningless newlines
and whitespaces like below. Zanata (translation check site) checks the
number of newlines, so translators need to insert newlines to silent
Zanata validations. It is really annoying and meaningless.

For Django templates, Django provides 'trimmed' option to trim
whitespaces in extracted messages. It would be nice if we have the
similar behavior to Django 'trimmed' option for AngularJS template
message extraction. In HTML case, we don't need to care consecutive
whitespaces, so we can simply trim whitespaces in AngularJS HTML
templates.

#:
openstack_dashboard/dashboards/project/static/dashboard/project/containers/create-container-modal.html:40
msgid ""
"A container is a storage compartment for your data and provides a way\n"
" for you to organize your data. You can think of a container as "
"a\n"
" folder in WindowsÂ® or a directory in UNIXÂ®. The primary "
"difference\n"
" between a container and these other file system concepts is "
"that\n"
" containers cannot be nested. You can, however, create an "
"unlimited\n"
" number of containers within your account. Data must be stored "
"in a\n"
" container so you must have at least one container defined in "
"your\n"
" account prior to uploading data."
msgstr ""

We would like to have a string like:

#:
openstack_dashboard/dashboards/project/static/dashboard/project/containers/create-container-modal.html:40
msgid ""
"A container is a storage compartment for your data and provides a way for"
" you to organize your data. You can think of a container as a folder in "
"Windows® or a directory in UNIX®. The primary difference between a "
"container and these other file system concepts is that containers cannot "
"be nested. You can, however, create an unlimited number of containers "
"within your account. Data must be stored in a container so you must have "
"at least one container defined in your account prior to uploading data."
msgstr ""

** Affects: horizon
Importance: Medium
Assignee: Akihiro Motoki (amotoki)
Status: New

** Tags: i18n

--
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/1592965

Title:
i18n: babel_extract_angular should trim whitespaces in AngularJS
templates

Status in OpenStack Dashboard (Horizon):
New

Bug description:
This is "AngularJS templates" version of bug 1583757.

We would like to have a string like:

#:
openstack_dashboard/dashboards/project/static/dashboard/project/containers/create-container-modal.html:40
msgid ""
"A container is a storage compartment for your data and provides a way for"
" you to organize your data. You can think of a container as a folder in "
"Windows® or a directory in UNIX®. The primary difference between a "
"container and these other file system concepts is that containers cannot "
"be nested. You can, however, create an unlimited number of containers "
"within your account. Data must be stored in a container so you must have "
"at least one container defined in your account prior to uploading data."
msgstr ""

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

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

[Yahoo-eng-team] [Bug 1592940] [NEW] Horizon makes duclicated and extra requests

2016-06-15 Thread Andrey Grebennikov

Public bug reported:

Horizon Liberty

User reports slowness of the dashboard for most of the tabs.
Investigation shows that Horizon makes duplicated requests when it is trying to 
request information related to the networking. It also waits for about 4 
seconds right after the initial user's successfull authentication before it 
proceeds with the first API call.

Here is the log of Horizon representing the delay:

2016-06-15 18:24:16,385 113992 DEBUG openstack_auth.backend Beginning user 
authentication
2016-06-15 18:24:16,387 113992 DEBUG openstack_auth.plugin.password Attempting 
to authenticate for admin
2016-06-15 18:24:16,387 113992 DEBUG keystoneclient.auth.identity.v3.base 
Making authentication request to http://192.168.210.69:5000/v3/auth/tokens
2016-06-15 18:24:16,481 113992 DEBUG keystoneclient.session REQ: curl -g -i 
--insecure -X GET http://192.168.210.69:5000/v3/ -H "Accept: application/j
son" -H "User-Agent: python-keystoneclient"
2016-06-15 18:24:16,503 113992 DEBUG keystoneclient.session RESP: [200] 
content-length: 253 vary: X-Auth-Token server: Apache connection: close date: 
Wed, 15 Jun 2016 18:24:16 GMT content-type: application/json 
x-openstack-request-id: req-258d4e76-6500-414d-a565-0788dc0d4f90 
RESP BODY: {"version": {"status": "stable", "updated": "2015-03-30T00:00:00Z", 
"media-types": [{"base": "application/json", "type": "application/vnd.o
penstack.identity-v3+json"}], "id": "v3.4", "links": [{"href": 
"http://192.168.210.69:5000/v3/";, "rel": "self"}]}}

2016-06-15 18:24:16,503 113992 DEBUG keystoneclient.session REQ: curl -g -i 
--insecure -X GET http://192.168.210.69:5000/v3/users/51e3873fe48f4948bef2
32865c7bc84f/projects -H "User-Agent: python-keystoneclient" -H "Accept: 
application/json" -H "X-Auth-Token: {SHA1}561e3b22c0693b6ff8dfad099a2492d95ed
8e9c1"
2016-06-15 18:24:16,561 113992 DEBUG keystoneclient.session RESP: [200] 
content-length: 412 vary: X-Auth-Token server: Apache connection: close date: 
Wed, 15 Jun 2016 18:24:16 GMT content-type: application/json 
x-openstack-request-id: req-765b3844-feb3-40b9-a843-f5cc2341afde 
RESP BODY: {"links": {"self": 
"http://192.168.210.69:5000/v3/users/51e3873fe48f4948bef232865c7bc84f/projects";,
 "previous": null, "next": null}, "proje
cts": [{"is_domain": false, "description": "admin tenant", "links": {"self": 
"http://192.168.210.69:5000/v3/projects/49cdffc876ca4927af2ea7505ad27264";
}, "enabled": true, "id": "49cdffc876ca4927af2ea7505ad27264", "parent_id": 
null, "domain_id": "default", "name": "admin"}]}

2016-06-15 18:24:16,561 113992 DEBUG keystoneclient.auth.identity.v3.base 
Making authentication request to http://192.168.210.69:5000/v3/auth/tokens
2016-06-15 18:24:16,657 113992 DEBUG openstack_auth.backend Authentication 
completed.
2016-06-15 18:24:16,657 113992 INFO openstack_auth.forms Login successful for 
user "admin".
2016-06-15 18:24:20,167 113996 DEBUG neutronclient.client REQ: curl -i 
https://domain.com:9696/v2.0/extensions.json -X GET -H "User-Agent: pyt
hon-neutronclient" -H "X-Auth-Token: 
{SHA1}04486c34b57ca19787b77e6d5e6e9fad48914b67"

Last 2 rows represent the issue.

I'll attach parsed logs for each tab opening in order to show duplicated
requests.

** Affects: horizon
 Importance: Undecided
 Status: New

-- 
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/1592940

Title:
  Horizon makes duclicated and extra requests

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Horizon Liberty

  User reports slowness of the dashboard for most of the tabs.
  Investigation shows that Horizon makes duplicated requests when it is trying 
to request information related to the networking. It also waits for about 4 
seconds right after the initial user's successfull authentication before it 
proceeds with the first API call.

  Here is the log of Horizon representing the delay:

  2016-06-15 18:24:16,385 113992 DEBUG openstack_auth.backend Beginning user 
authentication
  2016-06-15 18:24:16,387 113992 DEBUG openstack_auth.plugin.password 
Attempting to authenticate for admin
  2016-06-15 18:24:16,387 113992 DEBUG keystoneclient.auth.identity.v3.base 
Making authentication request to http://192.168.210.69:5000/v3/auth/tokens
  2016-06-15 18:24:16,481 113992 DEBUG keystoneclient.session REQ: curl -g -i 
--insecure -X GET http://192.168.210.69:5000/v3/ -H "Accept: application/j
  son" -H "User-Agent: python-keystoneclient"
  2016-06-15 18:24:16,503 113992 DEBUG keystoneclient.session RESP: [200] 
content-length: 253 vary: X-Auth-Token server: Apache connection: close date: 
  Wed, 15 Jun 2016 18:24:16 GMT content-type: application/json 
x-openstack-request-id: req-258d4e76-6500-414d-a565-0788dc0d4f90 
  RESP BODY: {"version": {"status": "stable", "updated": 
"2015-03-30T00:00:00Z", "media-types": [{"base": "application/json", "type": 
"application/vnd.o
  penstack.i

[Yahoo-eng-team] [Bug 1592543] Re: Images registration is using old registration technique

Reviewed:  https://review.openstack.org/329656
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=f85891aa8a3788ef59d14057fc8ceb83dc6bc3f3
Submitter: Jenkins
Branch:master

commit f85891aa8a3788ef59d14057fc8ceb83dc6bc3f3
Author: Matt Borland 
Date:   Tue Jun 14 13:54:38 2016 -0600

Register Image Names via .setNames()

The Image registry is using an unsupported method of setting values for 
names.
This patch fixes that by using the supported .setNames() method.

Change-Id: I54ea5bea45ce71c8ca60683bcb55aff6d3f5aa9a
Closes-Bug: 1592543


** 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/1592543

Title:
  Images registration is using old registration technique

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The Images module is using an experimental version of
  getResourceType() to register names instead of the .setNames()
  registry feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1592543/+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 1567673] Re: [OSSA-2016-010] Possible client side template injection in horizon (CVE-2016-4428)

Reviewed:  https://review.openstack.org/329998
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=62b4e6f30a7ae7961805abdffdb3c7ae5c2b676a
Submitter: Jenkins
Branch:master

commit 62b4e6f30a7ae7961805abdffdb3c7ae5c2b676a
Author: Richard Jones 
Date:   Tue May 3 15:51:49 2016 +1000

Escape angularjs templating in unsafe HTML

This code extends the unsafe (typically user-supplied) HTML escape
built into Django to also escape angularjs templating markers. Safe
HTML will be unaffected.

Closes-bug: 1567673
Change-Id: I0cbebfd0f814bdf1bf8c06833abf33cc2d4748e7


** 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/1567673

Title:
  [OSSA-2016-010] Possible client side template injection in horizon
  (CVE-2016-4428)

Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in OpenStack Security Advisory:
  Fix Committed

Bug description:
  I'm working through my groups process to deploy a new web app so that
  we can provide openstack in our production environment. Part of that
  process is having an authenticated security scan done by Acunetix.

  I've attached a screenshot of the report for the alert received during
  the scan.

  Unfortunately I'm not a dev, so I'm not sure if this is a false alarm
  or not.

  Quick research found the following link which talks about the issue in
  general: http://blog.portswigger.net/2016/01/xss-without-html-client-
  side-template.html

  Any input would be greatly appreciated.

  Thanks!
  Brandon

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1567673/+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 1290455] Re: libvirt inject_data assumes instance with kernel_id doesn't contain a partition table

Fix proposed to branch: master
Review: https://review.openstack.org/330140

** Changed in: nova
   Status: Opinion => In Progress

** Changed in: nova
 Assignee: (unassigned) => Alexandru Avadanii (alexandru-avadanii)

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

Title:
  libvirt inject_data assumes instance with kernel_id doesn't contain a
  partition table

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  libvirt/driver.py passes partition=None to disk.inject_data() for any
  instance with kernel_id set. partition=None means that inject_data
  will attempt to mount the whole image, i.e. assuming there is no
  partition table. While this may be true for EC2, it is not safe to
  assume that Xen images don't contain partition tables. This should
  check something more directly related to the disk image. In fact,
  ideally it would leave it up to libguestfs to work it out, as
  libguestfs is very good at this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1290455/+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 1589328] Re: Alembic branch checks do not detect Add/DropColumn violations

Reviewed:  https://review.openstack.org/325699
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=28bc1d79361ddbe53b67058a6c995e2d9ac19e3a
Submitter: Jenkins
Branch:master

commit 28bc1d79361ddbe53b67058a6c995e2d9ac19e3a
Author: Henry Gessau 
Date:   Sun Jun 5 22:05:33 2016 -0400

Check for alembic Add/DropColumn exceptions in migrations

Columns are added/dropped by alembic clauses in migrations, and
checking for them differs from how sqlalchemy clauses are checked.

Closes-Bug: #1589328

Change-Id: Ia0f39697afddec7cd04f870746a4bdd8b9410a32


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

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

Title:
  Alembic branch checks do not detect Add/DropColumn violations

Status in neutron:
  Fix Released

Bug description:
  In the test_branches test we check that elements are not added in the
  contract branch, and that elements are not removed in the expand
  branch. However, this check is not working for Add/DropColumn because
  they are processed as alembic clauses which have no element property.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1589328/+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 1592043] Re: os-brick 1.4.0 increases volume setup failure rates

2016-06-15 Thread Matt Riedemann

** Also affects: oslo.privsep
   Importance: Undecided
   Status: New

** Also affects: nova
   Importance: Undecided
   Status: New

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

Title:
  os-brick 1.4.0 increases volume setup failure rates

Status in OpenStack Compute (nova):
  New
Status in os-brick:
  In Progress
Status in oslo.privsep:
  New

Bug description:
  Since merging upper constraints 1.4.0 into upper-constraints, the
  multinode grenade jobs are hitting a nearly 1/3 failure rate on boot
  from volume scenarios around volume setup. This would be on Newton
  code using Mitaka configs.

  Representative failures are of the following form:
  http://logs.openstack.org/71/327971/5/gate/gate-grenade-dsvm-neutron-
  
multinode/f2690e3/logs/new/screen-n-cpu.txt.gz?level=WARNING#_2016-06-13_15_22_59_095

  The 1/3 failure rate is suspicious, and in the past has often hinted
  towards a race condition interacting between parallel API requests.

  The failure rate increase can be seen here -
  http://tinyurl.com/zrq35e8

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1592043/+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 1592918] [NEW] [RFE] Adding Port Statistics to Neutron Metering Agent

2016-06-15 Thread Sana Khan

Public bug reported:

[Existing Implementation]
Currently the Neutron Metering Agent only measures the bandwidth usage of the 
Routers. 

[Proposal]
The Neutron Metering Agent will be extended to also support Port statistics.

{collisions=0, 
rx_bytes=874, 
rx_crc_err=0, 
rx_dropped=0, 
rx_errors=0, 
rx_frame_err=0, 
rx_over_err=0, 
rx_packets=11, 
tx_bytes=70, 
tx_dropped=0, 
tx_errors=0, 
tx_packets=1}

In this implemention, the support for Port statistics will be added
using the OpenvSwitch tools.

[Suggesting Initial Implementation]
- Add method _notify_port_stats which collects ports statistics from ovsdb and 
sends the notification.
- The method _notify_port_stats is called the from _metering_loop to keep 
sending the port statistics.

Looking forward to feedbacks and suggestions.

[Benefits]
These metrics can further be exposed to Ceilometer and can be helpful for 
metering and monitoring purposes.  

[Related Information]
https://wiki.openstack.org/wiki/Internship_ideas

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: ovs

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

Title:
  [RFE] Adding Port Statistics to Neutron Metering Agent

Status in neutron:
  New

Bug description:
  [Existing Implementation]
  Currently the Neutron Metering Agent only measures the bandwidth usage of the 
Routers. 

  [Proposal]
  The Neutron Metering Agent will be extended to also support Port statistics.

  {collisions=0, 
  rx_bytes=874, 
  rx_crc_err=0, 
  rx_dropped=0, 
  rx_errors=0, 
  rx_frame_err=0, 
  rx_over_err=0, 
  rx_packets=11, 
  tx_bytes=70, 
  tx_dropped=0, 
  tx_errors=0, 
  tx_packets=1}

  In this implemention, the support for Port statistics will be added
  using the OpenvSwitch tools.

  [Suggesting Initial Implementation]
  - Add method _notify_port_stats which collects ports statistics from ovsdb 
and sends the notification.
  - The method _notify_port_stats is called the from _metering_loop to keep 
sending the port statistics.

  Looking forward to feedbacks and suggestions.

  [Benefits]
  These metrics can further be exposed to Ceilometer and can be helpful for 
metering and monitoring purposes.  

  [Related Information]
  https://wiki.openstack.org/wiki/Internship_ideas

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1592918/+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 1563419] Re: [UI] sahara uses UTC time instead of set timezone

2016-06-15 Thread Vitaly Gridnev

http://docs.openstack.org/project-team-guide/stable-branches.html

** Also affects: sahara/mitaka
   Importance: Undecided
   Status: New

-- 
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/1563419

Title:
  [UI] sahara uses UTC time instead of set timezone

Status in OpenStack Dashboard (Horizon):
  New
Status in Sahara:
  Fix Released
Status in Sahara mitaka series:
  New

Bug description:
  All time values that are shown in sahara dashboard are in UTC no
  matter what kind of timezone we have set in settings. It affects the
  Data Sources, Job Execution detail views and Cluster provision steps
  table

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1563419/+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 1299188] Re: qunit and jasmine urlpatterns should be defined only for test

Not going to fix this.

Deployments shouldn't put tests in production, and regardless, you must
expect some odd behavior if you place a production environment into
DEBUG mode.  This is also harmless behavior, so I'm not really worried
about it.

** Changed in: horizon
   Status: New => Won't Fix

-- 
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/1299188

Title:
  qunit and jasmine urlpatterns should be defined only for test

Status in OpenStack Dashboard (Horizon):
  Won't Fix

Bug description:
  qunit and jasmine urlpatterns are defined in horizon/site_urls.py if 
settings.DEBUG is True.
  DEBUG=True is a valid situation without dev env (it is reasonable when 
testing).

  It is better to use another flag other than DEBUG and define
  url_pattern "jasmine" and "qunit" only if the new flag is True.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1299188/+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 1425049] Re: Pagination doesn't work for images by normal user

This was already fixed apparently.  I notice Angular's Images table
doesn't respect the limit, but that's a different way of paginating.

** Changed in: horizon
   Status: New => 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/1425049

Title:
  Pagination doesn't work for images by normal user

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The current pagination scheme using limit and marker
  doesn't work by normal user for images.

  Steps to Reproduce:

  1. Set "Items Per Page" to 3 under "settings" using Horizon
  2. Ensure that, you have more than 3 images
  3. Log in by Normal user.
  4. Click on Images

  It show all available images for that particular user on same page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1425049/+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 1468353] Re: [RFE] QoS DSCP marking rule support

Reviewed:  https://review.openstack.org/288392
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=73546f8503f0d26c90aae9f7c2aa108d710870c8
Submitter: Jenkins
Branch:master

commit 73546f8503f0d26c90aae9f7c2aa108d710870c8
Author: Nate Johnston 
Date:   Fri Mar 4 11:17:31 2016 +0100

QoS DSCP fullstack tests

This patch introduces fullstack testing for the QoS/DSCP
Open vSwitch implementation. It depends on the python-neutronclient
patches, therefore it could not be merged in the main patch.

Co-Authored-By: Miguel Angel Ajo 
Change-Id: I0ab6a1a0d1430c5791fea1d5b54106c6cc93b937
Closes-Bug: #1468353
Depends-On: I25ad60c1b9a66e568276a772b8c496987d9f8299


** Changed in: neutron
   Status: Fix Committed => Fix Released

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

Title:
  [RFE] QoS DSCP marking rule support

Status in neutron:
  Fix Released

Bug description:
  The QoS API [#qos_api_spec]_ introduces an interface to configure QoS
  policies to neutron ports. We need to be able to mark outgoing dscp
  rules to tag traffic.

  Changes:

  * DB Model for new rule type
  * API changes to allow for DSCP API modifications
  * Client changes to allow for DSCP values being set for qos_rule list and 
update
  * OVS agent integration to hand down the QoS information to the driver as new 
ports are created or updates are received.
  * Open flow integration within OVS driver to add qos_dscp marking 
functionality

  Dependencies:
  * QoS API implementation #[qos_api_spec]_
  * QoS RPC and plugin integration
  * L2 agent extension for QoS (done in front of SR-IOV / OVS support)

  Link to the Blueprint:
  https://review.openstack.org/#/c/190285/1

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1468353/+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 1486607] Re: tenants seem like they were able to detach admin enforced QoS policies from ports or networks

Reviewed:  https://review.openstack.org/217092
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=4ec6932c93764fd7731928f1faa24b6c88fa9493
Submitter: Jenkins
Branch:master

commit 4ec6932c93764fd7731928f1faa24b6c88fa9493
Author: Tong Li 
Date:   Tue Sep 15 17:23:42 2015 -0400

Respond negatively to tenant detachment of enforced QoS policies

Currently when the tenant attempts to detach an enforced QoS policy
for a port or network set by admin, the attempt fails but the API
feedback indicates that it was successful.  This change will
fix the API response so the failure is accurately signalled
to the tenant.

Co-Authored-By: litong01 
Co-Authored-By: gong yong sheng 
Co-Authored-By: Nate Johnston 
Co-Authored-By: Margaret Frances 

Change-Id: I977feecc6cce378abc1e6092afbaf9f2681b2ec6
Closes-bug: #1486607


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

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

Title:
  tenants seem like they were able to detach admin enforced QoS policies
  from ports or networks

Status in neutron:
  Fix Released

Bug description:
  NOTE: Even if the API responds with "ok" to the port update, it's not really 
changing the admin enforced policy, we should just provide a better
  error / response code.

  If the CSP is using manually tagging specific tenant networks to
  follow specific qos profiles, a tenant could use

  neutron port-update  --no-qos-policy

  or

  neutron net-update  --no-qos-policy

  It will seem like if the port or net was correctly updated, but it
  isn't. We can lower the importance of this bug to low/medium.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1486607/+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 1501116] Re: "Image Registry" window contains a text box which overlaps with buttons (Japanese and German)

Reviewed:  https://review.openstack.org/316027
Committed: 
https://git.openstack.org/cgit/openstack/sahara-dashboard/commit/?id=ce9b93410bf8f27903041388cb10353f011c70bc
Submitter: Jenkins
Branch:master

commit ce9b93410bf8f27903041388cb10353f011c70bc
Author: sharat.sharma 
Date:   Fri May 13 16:36:59 2016 +0530

Clean up Image Registry form tag fields

This patch updates the tag fields on the Image Registry form so they
have labels and use the form-group class. It also updates the "Add"
buttons so just an icon is displayed. This will fix problems with
translated text making the button too wide.

Change-Id: I8c97952e7f1789e4c8272c7e518bd121e670cd1d
Closes-Bug: #1501116


** Changed in: sahara
   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/1501116

Title:
  "Image Registry" window contains a text box which overlaps with
  buttons (Japanese and German)

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in Sahara:
  Fix Released

Bug description:
  Project > Data Processing > Image Registry > Register Image

  The "Register Image" window, "Image Registry tool" text box becomes
  larger when it contains translated text (only confirmed in German and
  Japanese, but could be affecting more languages). It overlaps with
  buttons and other text.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1501116/+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 1549481] Re: Nova fails listing floating ips when using provider networks

2016-06-15 Thread Anusha Unnam

Yolanda Robla, This bug lacks the necessary information to effectively
reproduce and fix it, therefore it has been closed. Feel free to reopen
the bug by providing the requested information and set the bug status
back to ''New''.

** Changed in: nova
   Status: In Progress => Invalid

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

Title:
  Nova fails listing floating ips when using provider networks

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  When using provider networks in neutron, not using floating ips, nova is not 
able to list them.
  Nova still has extension os-floating-ip enabled on that case, so API calls 
about floating ips should work.
  But when executing a floating ip list with the client, we are receiving 
following error:

  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack Traceback (most recent 
call last):
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack   File 
"/usr/lib/python2.7/dist-packages/nova/api/openstack/__init__.py", line 125, in 
__call__
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack return 
req.get_response(self.application)
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack   File 
"/usr/lib/python2.7/dist-packages/webob/request.py", line 1320, in send
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack application, 
catch_exc_info=False)
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack   File 
"/usr/lib/python2.7/dist-packages/webob/request.py", line 1284, in 
call_application
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack app_iter = 
application(self.environ, start_response)
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack   File 
"/usr/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack return 
resp(environ, start_response)
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack   File 
"/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", 
line 634, in __call__
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack return 
self._call_app(env, start_response)
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack   File 
"/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", 
line 554, in _call_app
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack return 
self._app(env, _fake_start_response)
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack   File 
"/usr/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack return 
resp(environ, start_response)
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack   File 
"/usr/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack return 
resp(environ, start_response)
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack   File 
"/usr/lib/python2.7/dist-packages/routes/middleware.py", line 131, in __call__
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack response = 
self.app(environ, start_response)
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack   File 
"/usr/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack return 
resp(environ, start_response)
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack   File 
"/usr/lib/python2.7/dist-packages/webob/dec.py", line 130, in __call__
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack resp = 
self.call_func(req, *args, **self.kwargs)
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack   File 
"/usr/lib/python2.7/dist-packages/webob/dec.py", line 195, in call_func
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack return 
self.func(req, *args, **kwargs)
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack   File 
"/usr/lib/python2.7/dist-packages/nova/api/openstack/wsgi.py", line 756, in 
__call__
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack content_type, body, 
accept)
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack   File 
"/usr/lib/python2.7/dist-packages/nova/api/openstack/wsgi.py", line 821, in 
_process_stack
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack action_result = 
self.dispatch(meth, request, action_args)
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack   File 
"/usr/lib/python2.7/dist-packages/nova/api/openstack/wsgi.py", line 911, in 
dispatch
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack return 
method(req=request, **action_args)
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack   File 
"/usr/lib/python2.7/dist-packages/nova/api/openstack/compute/contrib/floating_ips.py",
 line 108, in index
  2016-02-24 20:58:01.624 5857 TRACE nova.api.openstack floating_ips = 
self.network_api.get_floating_

[Yahoo-eng-team] [Bug 1563419] Re: [UI] sahara uses UTC time instead of set timezone

2016-06-15 Thread Alexey Stupnikov

This bug is also found in Horizon's kilo and liberty branches.

** Also affects: horizon
   Importance: Undecided
   Status: New

** Changed in: horizon
 Assignee: (unassigned) => Alexey Stupnikov (astupnikov)

-- 
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/1563419

Title:
  [UI] sahara uses UTC time instead of set timezone

Status in OpenStack Dashboard (Horizon):
  New
Status in Sahara:
  Fix Released

Bug description:
  All time values that are shown in sahara dashboard are in UTC no
  matter what kind of timezone we have set in settings. It affects the
  Data Sources, Job Execution detail views and Cluster provision steps
  table

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1563419/+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 1576093] Re: block migration fail with libvirt since version 1.2.17

2016-06-15 Thread James Page

** Also affects: ubuntu (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nova (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: ubuntu (Ubuntu)

** Also affects: nova (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: cloud-archive
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/mitaka
   Importance: Undecided
   Status: New

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

Title:
  block migration fail with libvirt since version  1.2.17

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive mitaka series:
  New
Status in OpenStack Compute (nova):
  Fix Released
Status in nova package in Ubuntu:
  Confirmed
Status in nova source package in Xenial:
  Confirmed

Bug description:
  Try to do block migration but fail and libvirt reports that

  "Selecting disks to migrate is not implemented for tunneled migration"

  Nova:  a4e15e329f9adbcfe72fbcd6acb94f0743ad02f8

  libvirt: 1.3.1

  reproduce:

  default devstack setting and do block migration (no shared
  instance_dir and shared instance storage used)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1576093/+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 1568708] Re: translation sync broken due to wrong useage of venv

2016-06-15 Thread Andreas Jaeger

http://logs.openstack.org/periodic/networking-midonet-propose-
translation-update/b53e686/

** Also affects: networking-midonet
   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/1568708

Title:
  translation sync broken due to wrong useage of venv

Status in networking-midonet:
  New
Status in networking-ovn:
  Confirmed
Status in neutron:
  Fix Committed
Status in Sahara:
  New

Bug description:
  post jobs cannot use zuul-cloner and have no access currently to
  upper-constraints. See how nova or neutron itself handle this.

  Right now the sync with translations fails:

  https://jenkins.openstack.org/job/neutron-fwaas-propose-translation-
  update/119/console

  Please fix venv tox environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-midonet/+bug/1568708/+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 1572543] Re: Request stable/liberty release for openstack/networking-hyperv

2016-06-15 Thread Claudiu Belu

** Changed in: networking-hyperv
   Importance: Undecided => Medium

** Changed in: networking-hyperv
 Assignee: (unassigned) => Claudiu Belu (cbelu)

** Changed in: networking-hyperv
   Status: New => Fix Released

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

Title:
  Request stable/liberty release for openstack/networking-hyperv

Status in networking-hyperv:
  Fix Released
Status in neutron:
  Won't Fix

Bug description:
  Please release the new version for stable/liberty branch of
  networking-hyperv.

  commit id: 13401e80e3360b9f25797879c7ade7b768ca034f
  tag: 1.0.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-hyperv/+bug/1572543/+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 1580357] Re: Launch Instance NG does not auto select default security group or default to selecting the only network in a Project

*** This bug is a duplicate of bug 1587681 ***
https://bugs.launchpad.net/bugs/1587681

** This bug has been marked a duplicate of bug 1587681
   new launch instance wizard defaults

-- 
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/1580357

Title:
  Launch Instance NG does not auto select default security group or
  default to selecting the only network in a Project

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  In the Mitaka Release of Horizon, the Launch Instance NG panels do not
  select the 'default' security group and if there is only one network
  in a Project it does not default to that network.  In the Launch
  Instance Legacy workflow, this defaulted to the 'default' security
  group and if you only had one network it defaulted to select that
  network.  In Mitaka, the Launch Instance Legacy workflow no longer
  selects the 'default' security group since it is defaulting to using
  the string instead of the id of the 'default' network and this change
  broke that [0].  I'm not expecting the Launch Instance Legacy workflow
  to be fixed, just documenting that fact since I switched back to that
  workflow expecting it to work like the Kilo dashboard.

  [0]: https://github.com/openstack/horizon/commit/5562694

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1580357/+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 1588408] Re: Volume pagination doesn't really work

2016-06-15 Thread Liyingjun

Can't reproduce, i used the master branch, and it's paginated as
expected.

** Changed in: horizon
   Status: New => Opinion

-- 
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/1588408

Title:
  Volume pagination doesn't really work

Status in OpenStack Dashboard (Horizon):
  Opinion

Bug description:
  1. Login into Horizon as admin user
  2. Go to User Settings page and set 'Items Per Page' to 1
  3. Create a few volumes

  Actual result: there is no pagination available. All the items are
  shown on one page

  Expected behaviour: pagination should be available and one items per
  page should be shown. As it was implemented on project/instances/ or
  project/images/ pages.

  Note: log out/log in didn't help. got the same result.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1588408/+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 1589501] Re: Request Mitaka maintenance release for networking-bgpvpn

2016-06-15 Thread Thomas Morin

** Changed in: bgpvpn
   Status: New => Fix Released

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

Title:
  Request Mitaka maintenance release for networking-bgpvpn

Status in bgpvpn:
  Fix Released
Status in neutron:
  Fix Committed

Bug description:
  Please release a maintenance version of networking-bgpvpn from our
  stable/mitaka branch, tag abe26499aae8b4b875789c20a9825cd96b3e4b52,
  with release number 4.0.1 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/bgpvpn/+bug/1589501/+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 1591222] Re: Shared filter is broken for QoS policies since Mitaka

Reviewed:  https://review.openstack.org/328313
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=389f7b0b08455b77db24d41280e8cc00a0d2260b
Submitter: Jenkins
Branch:master

commit 389f7b0b08455b77db24d41280e8cc00a0d2260b
Author: Ihar Hrachyshka 
Date:   Fri Jun 10 16:03:31 2016 +0200

qos: fix shared filter for policies

The filter was working in Liberty, but was broken in Mitaka when
the field became synthetic as part of RBAC enablement for the resource.

_get_collection already knows how to handle the filter on database
level, so we just need to register the filter to pass it deeper into
db_api.

Change-Id: I40657bd15d9bf1e2bc6b0224254c916c35391cd1
Closes-Bug: #1591222


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

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

Title:
  Shared filter is broken for QoS policies since Mitaka

Status in neutron:
  Fix Released

Bug description:
  The filter was working in Liberty, but was broken in Mitaka when 
  the field became synthetic as part of RBAC enablement for the resource.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1591222/+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 1591381] Re: Instance tags can be set before an instance is active

Reviewed:  https://review.openstack.org/329304
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=4cb366f831d54a0ca80d1f946eb25e862364d566
Submitter: Jenkins
Branch:master

commit 4cb366f831d54a0ca80d1f946eb25e862364d566
Author: melanie witt 
Date:   Tue Jun 14 03:39:57 2016 +

Disallow instance tag set for invalid instance states

Currently, instance tags can be set at any time during the instance
lifecycle, possibly because it does not go through the compute API.

This makes the valid instance states for the instance tag update API
consistent with the instance metadata update API. If instance tag
update is requested outside of the valid states, a 409 conflict error
will be returned.

Closes-Bug: #1591381

Change-Id: Id53a31654e105854f4942e6d47a1bea90a3e9c3b


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

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

Title:
  Instance tags can be set before an instance is active

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  As opposed to metadata or other attributes of an instance tags can be
  set very early in the instance lifecycle. This will eventually lead to
  issues if the boot process makes use of these tags because setting
  them before boot will be a race condition. And there is a proposed
  spec which intends to do exactly that, use tags in the scheduling
  process.

  To be consistent and to avoid future racy behavior instance tags
  should only be settable after a boot request after it has gone to
  ACTIVE status. Passing instance tags in as part of the boot request
  would be desirable behavior but requires a spec and is outside the
  scope of this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1591381/+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 1592594] Re: DHCP: delete config option dnsmasq_dns_server

2016-06-15 Thread Matt Kassawara

The central documentation references dnsmasq_dns_servers instead of
dnsmasq_dns_server.

** Changed in: openstack-manuals
   Status: New => Invalid

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

Title:
  DHCP: delete config option dnsmasq_dns_server

Status in neutron:
  Invalid
Status in openstack-manuals:
  Invalid

Bug description:
  https://review.openstack.org/329306
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit eb965f99ded8a46db220d540bcaea5d67f5b2d08
  Author: Gary Kotton 
  Date:   Tue Jun 14 00:47:14 2016 -0700

  DHCP: delete config option dnsmasq_dns_server
  
  This field was marked as deprecated In commit
  a269541c603f8923b35b7e722f1b8c0ebd42c95a. That was in Kilo
  which has provided enough time for admins to addjust to this.
  
  In addition to this the patch sets the default value as [].
  If a value is not specified this is None and that should not be
  the default list.
  
  DocImpact
  UpgradeImpact
  
  Change-Id: Ieaf18ffc9baf7e1caebe9de47017338bebd92c84

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1592594/+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 1592594] Re: DHCP: delete config option dnsmasq_dns_server

2016-06-15 Thread Darek Smigiel

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

** Changed in: neutron
   Status: New => Invalid

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

Title:
  DHCP: delete config option dnsmasq_dns_server

Status in neutron:
  Invalid
Status in openstack-manuals:
  Invalid

Bug description:
  https://review.openstack.org/329306
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit eb965f99ded8a46db220d540bcaea5d67f5b2d08
  Author: Gary Kotton 
  Date:   Tue Jun 14 00:47:14 2016 -0700

  DHCP: delete config option dnsmasq_dns_server
  
  This field was marked as deprecated In commit
  a269541c603f8923b35b7e722f1b8c0ebd42c95a. That was in Kilo
  which has provided enough time for admins to addjust to this.
  
  In addition to this the patch sets the default value as [].
  If a value is not specified this is None and that should not be
  the default list.
  
  DocImpact
  UpgradeImpact
  
  Change-Id: Ieaf18ffc9baf7e1caebe9de47017338bebd92c84

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1592594/+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 1592849] [NEW] XenAPI: Invalid domid detection incorrect

2016-06-15 Thread Bob Ball

Public bug reported:

https://git.openstack.org/cgit/openstack/nova/tree/nova/virt/xenapi/vmops.py#n2048

def _get_dom_id(self, instance=None, vm_ref=None, check_rescue=False):
vm_ref = vm_ref or self._get_vm_opaque_ref(instance, check_rescue)
domid = self._session.call_xenapi("VM.get_domid", vm_ref)
if not domid or domid == -1:
raise exception.InstanceNotFound(instance_id=instance['name'])
return domid

VM.get_domid will return a string, which will never be equal to an
integer.

** Affects: nova
 Importance: High
 Assignee: Bob Ball (bob-ball)
 Status: Confirmed

** Changed in: nova
   Importance: Undecided => High

** Changed in: nova
 Assignee: (unassigned) => Bob Ball (bob-ball)

** Changed in: nova
   Status: New => Confirmed

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

Title:
  XenAPI: Invalid domid detection incorrect

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  
https://git.openstack.org/cgit/openstack/nova/tree/nova/virt/xenapi/vmops.py#n2048

  def _get_dom_id(self, instance=None, vm_ref=None, check_rescue=False):
  vm_ref = vm_ref or self._get_vm_opaque_ref(instance, check_rescue)
  domid = self._session.call_xenapi("VM.get_domid", vm_ref)
  if not domid or domid == -1:
  raise exception.InstanceNotFound(instance_id=instance['name'])
  return domid

  VM.get_domid will return a string, which will never be equal to an
  integer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1592849/+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 1592835] [NEW] hz-dynamic-table has empty div when no facets

Public bug reported:

hz-dynamic-table displays a weird empty div when there are no facets and
the user has clicked in the search area.

** Affects: horizon
 Importance: Undecided
 Status: New


** Tags: angularjs

** Tags added: angularjs

-- 
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/1592835

Title:
  hz-dynamic-table has empty div when no facets

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  hz-dynamic-table displays a weird empty div when there are no facets
  and the user has clicked in the search area.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1592835/+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 1592553] Re: Port Validator Failing

Reviewed:  https://review.openstack.org/329777
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=68ce548f8193e1b29475f1ed4d0d6c2506a1ffab
Submitter: Jenkins
Branch:master

commit 68ce548f8193e1b29475f1ed4d0d6c2506a1ffab
Author: Matthias Runge 
Date:   Wed Jun 15 08:48:45 2016 +0200

Fix port validator

A recent change in netutils now allows a port number 0
as valid port number. This made tests fail.

Change-Id: Ic290b76daa59387d8a13ce3712f7cd9416ac80c5
Closes-bug: #1592553


** 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/1592553

Title:
  Port Validator Failing

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  A recent update to netutils allows users to select port number 0. This
  change is causing the below to fail.

  ==
  FAIL: test_port_range_validator (horizon.test.tests.utils.ValidatorsTests)
  --
  Traceback (most recent call last):
File "/opt/stack/horizon/horizon/test/tests/utils.py", line 257, in 
test_port_range_validator
  self.assertRaises(ValidationError, test_call, prange)
  AssertionError: ValidationError not raised

  
  ==
  FAIL: test_port_validator (horizon.test.tests.utils.ValidatorsTests)
  --
  Traceback (most recent call last):
File "/opt/stack/horizon/horizon/test/tests/utils.py", line 207, in 
test_port_validator
  port)
  AssertionError: ValidationError not raised

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1592553/+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 1592808] [NEW] Snapshot failed during inconsistencies in glance v2 image schema

2016-06-15 Thread Mike Fedosin

Public bug reported:

When trying to create a snapshot with Glance v2 with nodepool the bug
appears: http://paste.openstack.org/show/516238/

It happens because in glance v1 it was possible to set empty string to
kernel_id or ramdisk_id. In v2 it's forbidden.

** Affects: nova
 Importance: Undecided
 Assignee: Mike Fedosin (mfedosin)
 Status: Confirmed

** Changed in: nova
   Status: New => Confirmed

** Changed in: nova
 Assignee: (unassigned) => Mike Fedosin (mfedosin)

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

Title:
  Snapshot failed during inconsistencies in glance v2 image schema

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  When trying to create a snapshot with Glance v2 with nodepool the bug
  appears: http://paste.openstack.org/show/516238/

  It happens because in glance v1 it was possible to set empty string to
  kernel_id or ramdisk_id. In v2 it's forbidden.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1592808/+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 1592834] [NEW] hz-dynamic-table inline batch actions not aligned

Public bug reported:

If you use hz-dynamic-table's batch actions inline with the search bar,
it doesn't format them particularly well, placing them generally in the
space given, not pushing them to the right.

** Affects: horizon
 Importance: Undecided
 Status: New


** Tags: angularjs

** Tags added: angularjs

-- 
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/1592834

Title:
  hz-dynamic-table inline batch actions not aligned

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  If you use hz-dynamic-table's batch actions inline with the search
  bar, it doesn't format them particularly well, placing them generally
  in the space given, not pushing them to the right.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1592834/+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 1591916] Re: Named arguments should be used for assertValidUserResponse() in unittest case