[Yahoo-eng-team] [Bug 1718585] [NEW] set floatingip status to DOWN during creation

[venkata anil]

Public bug reported:

floatingip status is not reliable as it is set to active during creation itself 
[1] rather than waiting for agent [2] to update it once agent finishes adding 
SNAT/DNAT rules.
[1] https://github.com/openstack/neutron/blob/master/neutron/db/l3_db.py#L1234
[2] 
https://github.com/openstack/neutron/blob/master/neutron/agent/l3/agent.py#L131

User can check floatingip status after creation and can initiate data traffic 
before agent finishes 
 processing floatingip resulting in connection failures. Also fixing this can 
help tempest tests to initiate connection only after agent has finished 
floatingip processing and avoid failures.

Also floatingip status has to be properly updated during migration of
router.

** Affects: neutron
 Importance: Undecided
 Assignee: venkata anil (anil-venkata)
 Status: New


** Tags: l3-dvr-backlog l3-ha

** Changed in: neutron
 Assignee: (unassigned) => venkata anil (anil-venkata)

** Tags added: l3-dvr-backlog l3-ha

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

Title:
  set floatingip status to DOWN during creation

Status in neutron:
  New

Bug description:
  floatingip status is not reliable as it is set to active during creation 
itself [1] rather than waiting for agent [2] to update it once agent finishes 
adding SNAT/DNAT rules.
  [1] https://github.com/openstack/neutron/blob/master/neutron/db/l3_db.py#L1234
  [2] 
https://github.com/openstack/neutron/blob/master/neutron/agent/l3/agent.py#L131

  User can check floatingip status after creation and can initiate data traffic 
before agent finishes 
   processing floatingip resulting in connection failures. Also fixing this can 
help tempest tests to initiate connection only after agent has finished 
floatingip processing and avoid failures.

  Also floatingip status has to be properly updated during migration of
  router.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1718585/+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 1714753] Re: Some links are broken after doc-migration

[OpenStack Infra]

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

commit a4d05ce55da8e4e86dfd13933bfea6250085c72d
Author: Akihiro Motoki 
Date:   Sun Sep 3 08:27:42 2017 +

Clean up broken links due to doc-migration

admin-manage-stacks.rst is dropped as we have no admin stack panel.
view-cloud-resources.rst is dropped as the metering panel was dropped
several releases ago.

Closes-Bug: 1714753

Change-Id: I483cb3dbaab23722abd2f321e8666d8beea2f7c7


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

Title:
  Some links are broken after doc-migration

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The following links in the horizon documentation are broken:
  http://paste.openstack.org/show/620281/

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1714753/+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 1640901] Re: Sorting available sources in Instance Creation angular panel does not work

[OpenStack Infra]

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

commit 4c5231c2587e9e4de8e272d1e565a160d96f9bf5
Author: Marek Lycka 
Date:   Tue Aug 22 13:52:54 2017 +0200

Restores sorting in the launch dialog source page

Replaces the (non-working) sorting attributes with parametrized callbacks.

Change-Id: I91ffee71a982e1f20e80e6f41d75e8a9268f7a44
Closes-Bug:1640901


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

Title:
  Sorting available sources in Instance Creation angular panel does not
  work

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Steps to reproduce:

  - Go to Instances panel
  - Click "Launch Instance"
  - Go to "Source" tab
  - In "Available" section click on any column

  What should happen -- table should be sorted by selected column
  What happens -- nothing

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1640901/+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 1718567] [NEW] Mention API behavior change when over quota limit

[Zhenyu Zheng]

Public bug reported:

TBA

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

Title:
  Mention API behavior change when over quota limit

Status in OpenStack Compute (nova):
  New

Bug description:
  TBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1718567/+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 1718190] Re: Instance could not be created/launched

[Matt Riedemann]

https://docs.openstack.org/ocata/install-guide-rdo/nova-controller-
install.html#finalize-installation says:


In the [glance] section, configure the location of the Image service
API:

[glance]
# ...
api_servers = http://controller:9292


So you missed a step.

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

Title:
  Instance could not be created/launched

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  During creation of instance through CLI or dashboard, i am getting
  Unexpected error in logs. please find command and other related
  openstack command outputs


  Command and error
  

  #openstack server create --flavor 73c42e28-0d38-4bc4-ad32-61b08474cdfa
  --image Roka-New --nic net-id=a973a522-3893-4f0a-a643-95cae029744a
  --security-group default --key-name mykey instance-1 --debug

  POST call to compute for 
http://172.168.1.129:8774/v2/e6da88076d2847aca65e41b1d2093396/servers used 
request id req-c809d780-5615-4521-8647-bcbfe24b3f26
  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-c809d780-5615-4521-8647-bcbfe24b3f26)
  Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/cliff/app.py", line 400, in 
run_subcommand
  result = cmd.run(parsed_args)
File "/usr/lib/python2.7/site-packages/osc_lib/command/command.py", line 
41, in run
  return super(Command, self).run(parsed_args)
File "/usr/lib/python2.7/site-packages/cliff/display.py", line 112, in run
  column_names, data = self.take_action(parsed_args)
File 
"/usr/lib/python2.7/site-packages/openstackclient/compute/v2/server.py", line 
627, in take_action
  server = compute_client.servers.create(*boot_args, **boot_kwargs)
File "/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line 
1416, in create
  **boot_kwargs)
File "/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line 779, 
in _boot
  return_raw=return_raw, **kwargs)
File "/usr/lib/python2.7/site-packages/novaclient/base.py", line 361, in 
_create
  resp, body = self.api.client.post(url, body=body)
File "/usr/lib/python2.7/site-packages/keystoneauth1/adapter.py", line 223, 
in post
  return self.request(url, 'POST', **kwargs)
File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 80, in 
request
  raise exceptions.from_response(resp, body, url, method)

  
  other related command results
  _

  [root@controller ~]# . /home/admin-openrc

  [root@controller ~]# openstack flavor list
  ++-+-+--+---+---+---+
  | ID | Name| RAM | Disk | Ephemeral | VCPUs | Is Public |
  ++-+-+--+---+---+---+
  | 0  | m1.nano |  64 |1 | 0 | 1 | True  |
  ++-+-+--+---+---+---+

  [root@controller log]# openstack project list
  +--+--+
  | ID   | Name |
  +--+--+
  | 2cf19b21164e432fb84cfed281481737 | service  |
  | 82df21eecb184130b15fbf337e3fcfbf | Roka2017 |
  | e6da88076d2847aca65e41b1d2093396 | demo |
  | f045d9ebb6f64ef0bfa580b3bc7a312e | admin|
  +--+--+

  [root@controller log]# openstack network list
  
+--+--+--+
  | ID   | Name | Subnets   
   |
  
+--+--+--+
  | 3cb5b804-f585-4455-92a4-360cefbb96f8 | outside  | 
d014432c-ec96-48c8-9a83-adb69d18d943 |
  | a973a522-3893-4f0a-a643-95cae029744a | demo-net | 
ec178c3e-8f99-428c-871c-3bb02c572d9d |
  
+--+--+--+

  [root@controller log]# openstack keypair list
  +---+-+
  | Name  | Fingerprint |
  +---+-+
  | mykey | e9:74:b4:0b:bb:7f:68:5f:8d:ab:9e:ed:18:f5:7e:58 |
  +---+-+

  [root@controller log]# openstack image list
  +--+--++
  | ID   | Name | Status |
  +--+--++
  | c7f1f1b3-4ad8-4eb1-ac31-5e1171fa4593 | New-one  | active |
  | 3195c8b9-cddb-40cd-be63-e09117308a84 | RHEL7| active |
  | fdbb6f71-e22f-4fb0-bdf6-3826a0a729c8 | Roka-New | active |

[Yahoo-eng-team] [Bug 1527121] Re: cells: instance can not evacuate in cells

[Matt Riedemann]

Cells v1 support is basically frozen, we aren't fixing latent bugs:

https://docs.openstack.org/nova/latest/user/cells.html#status

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

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

Title:
  cells: instance can not evacuate in cells

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  1. version
  kilo 2015.1.0

  There has one api cell and two child cell and four compute nodes,api cell has 
not compute node.
  I boot an instance and evacuate the instance, then return error:
  [root@apicell ~(keystone_admin)]# nova evacuate test_vm5
  ERROR (NotFound): The resource could not be found. (HTTP 404) (Request-ID: 
req-63786e5b-1199-4e2a-a5c0-a1efde0398a8)

  the error log in api cell nova-api.log in:
  http://paste.openstack.org/show/482160/

  The reason is that  nova api in api cell  first check compute node 
nova-compute status before evacuate the instance , it calls 
db.service_get_by_compute_host function, but the api cell db has not  compute 
node service record. Thus resulting in failure evacuate：
   Caught error: Compute host CL-SBCJ-5-3-4 could not be found

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1527121/+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 1718409] Re: Failed to reschedule instance in cell.

[Matt Riedemann]

Reschedules and up-calls from the cell conductor to the API database
(and scheduler) don't work in superconductor mode in devstack. I
commented on the devstack patch. Please read and understand this first:

https://docs.openstack.org/nova/latest/user/cellsv2_layout.html

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

Title:
  Failed to reschedule instance in cell.

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Description
  ===
  When instance rescheduling happens in cell:
  1. Nova compute casts to the build_instances method in cell1 conductor.
  2. In cell1 conductor, build_instances method calls the 
scheduler_client.select_destinations method, it calls to scheduler for getting 
scheduled host **without cell0 targeting**, and then, wait scheduler reply.

  Nobody could get this scheduler message in cell1 mq, because Scheduler
  just only lisening to the api cell(cell0) mq.

  flow like this:
  compute --> (reschedule) -->  cell1-conductor  -->  (call rpc to CELL1) --> 
timeout

  It seems conductor shouldn't call this message to CELL1 mq. Maybe, we
  might transfer the mq connection to api cell mq(target cell0) before
  call.

  After this, the flow as blow:
  compute --> (reschedule) -->  cell1-conductor  --> target CELL0 -->  (call 
rpc to CELL0) --> scheduler

  BTW, a devstack issue founded.
  In order to let scheduler could get instance group from nova_api database in 
code here: 
  
https://github.com/openstack/nova/blob/5bf1bb47c7e17c26592a699d07c2faa59d98bfb8/nova/conductor/manager.py#L623
  It seems we need add 'connection' config in [api_database] section, but now 
devstack doesn't deal with it.
  patch is here: https://review.openstack.org/#/c/505607/

  Steps to reproduce
  ==

  * 1. Inject some exception in compute code to reproduce a reschedule 
operation:
  raise exception.RescheduledException("reschedule trigger") in here:
  
https://github.com/openstack/nova/blob/5bf1bb47c7e17c26592a699d07c2faa59d98bfb8/nova/compute/manager.py#L1951
  * 2. nova compute cast reschedule request to cell-conductor
  * 3. cell-conductor calls to cell mq, nobody could process that.
  * 4. Instacne state stuck in BUILD(scheduling)
  stack@yikun:~/nova$ nova list
  
+--+-+++-+--+
  | ID   | Name| Status | Task 
State | Power State | Networks |
  
+--+-+++-+--+
  | af3fe405-7155-429d-97a8-a0f9f4c82911 | test_resch_instance | BUILD  | 
scheduling | NOSTATE |  |
  
+--+-+++-+--+
  * 4. Finally, Instance state is ERROR.
  stack@yikun:~/nova$ nova list
  
+--+-+++-+--+
  | ID   | Name| Status | Task 
State | Power State | Networks |
  
+--+-+++-+--+
  | af3fe405-7155-429d-97a8-a0f9f4c82911 | test_resch_instance | ERROR  | - 
 | NOSTATE |  |
  
+--+-+++-+--+

  
  Logs & Configs
  ==
  cell config show as blow:

  stack@yikun:~/nova$ cat /etc/nova/nova_cell1.conf 
  [database]
  connection = mysql+pymysql://root:1@127.0.0.1/nova_cell1?charset=utf8

  [api_database]
  connection = mysql+pymysql://root:1@127.0.0.1/nova_api?charset=utf8

  
  [conductor]
  workers = 2

  [DEFAULT]
  logging_user_identity_format = %(project_name)s %(user_name)s
  transport_url = rabbit://stackrabbit:1@XXX:5672/nova_cell1
  debug = True

  
  Log in cell conductor:
  2017-09-20 06:18:01.306 21701 ERROR nova.scheduler.utils 
[req-5890b731-4b48-4503-a446-ef3f858eda4a admin admin] [instance: 
af3fe405-7155-429d-97a8-a0f9f4c82911] Error from last host: yikun (node yikun): 
[u'Traceback (most recent call last):\n', u'  File 
"/opt/stack/nova/nova/compute/manager.py", line 1826, in 
_do_build_and_run_instance\nfilter_properties)\n', u'  File 
"/opt/stack/nova/nova/compute/manager.py", line 2057, in 
_build_and_run_instance\ninstance_uuid=instance.uuid, 
reason=six.text_type(e))\n', u'RescheduledException: Build of instance 
af3fe405-7155-429d-97a8-a0f9f4c82911 was re-scheduled: reschedule trigger\n']
  2017-09-20 06:18:01.347 21701 DEBUG oslo_db.sqlalchemy.engines 
[req-5890b731-4b48-4503-a446-ef3f858eda4a admin admin] MySQL server mode set to 

[Yahoo-eng-team] [Bug 1513410] Re: A space inserted at the end of the instance name, results in error

[Akihiro Motoki]

This cannot be reproduced now.

** Tags removed: space

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

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

Title:
  A space inserted at the end of the instance name, results in error

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  to reproduce: create an instance from an image in Horizon and add a space 
after the instance name. See the screenshots:
  
https://bugs.launchpad.net/horizon/+bug/1513410/+attachment/4513357/+files/1952.png
  
https://bugs.launchpad.net/horizon/+bug/1513410/+attachment/4513359/+files/1953.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1513410/+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 1718545] Re: [vnc]vncserver_proxyclient_address and [vnc]vncserver_listen removed without deprecation

[Eric Fried]

** Also affects: nova-powervm
   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/1718545

Title:
  [vnc]vncserver_proxyclient_address and [vnc]vncserver_listen removed
  without deprecation

Status in OpenStack Compute (nova):
  In Progress
Status in nova-powervm:
  New

Bug description:
  [0] removed options [vnc]vncserver_proxyclient_address and
  [vnc]vncserver_listen without a deprecation period.  Lemme splain:

  Take for example vncserver_proxyclient_address.  It was originally
  [DEFAULT]vncserver_proxyclient_address.  That was moved to
  [vnc]vncserver_proxyclient_address via [1].  We've had a nice long
  deprecation period (~18mo) during which either of those would work.
  So it would be reasonable at this time to remove support for
  [DEFAULT]vncserver_proxyclient_address.  But by renaming the option
  without changing its deprecated_group to `vnc`, we've instead *left*
  support for [DEFAULT]vncserver_proxyclient_address while *removing*
  support for the newer [vnc]vncserver_proxyclient_address without a
  deprecation period.

  I noticed this when running tox against nova-powervm with the latest
  nova.  nova-powervm paid attention to the deprecation and switched
  over to [vnc]vncserver_proxyclient_address.  Now it fails a test with:

  Captured traceback:
  ~~~
  Traceback (most recent call last):
File 
"/home/efried/Neo/nova-powervm/.tox/py27/local/lib/python2.7/site-packages/mock/mock.py",
 line 1305, in patched
  return func(*args, **keywargs)
File "nova_powervm/tests/virt/powervm/test_driver.py", line 1666, in 
test_get_vnc_console
  resp = self.drv.get_vnc_console(mock.ANY, self.inst)
File "nova_powervm/virt/powervm/driver.py", line 1727, in 
get_vnc_console
  host = CONF.vnc.vncserver_proxyclient_address
File 
"/home/efried/Neo/nova-powervm/.tox/py27/local/lib/python2.7/site-packages/oslo_config/cfg.py",
 line 3363, in __getattr__
  return self._conf._get(name, self._group)
File 
"/home/efried/Neo/nova-powervm/.tox/py27/local/lib/python2.7/site-packages/oslo_config/cfg.py",
 line 2925, in _get
  value = self._do_get(name, group, namespace)
File 
"/home/efried/Neo/nova-powervm/.tox/py27/local/lib/python2.7/site-packages/oslo_config/cfg.py",
 line 2942, in _do_get
  info = self._get_opt_info(name, group)
File 
"/home/efried/Neo/nova-powervm/.tox/py27/local/lib/python2.7/site-packages/oslo_config/cfg.py",
 line 3099, in _get_opt_info
  raise NoSuchOptError(opt_name, group)
  oslo_config.cfg.NoSuchOptError: no such option 
vncserver_proxyclient_address in group [vnc]

  But anyone should be able to repro by spinning up compute with
  [vnc]vncserver_proxyclient_address and trying to open a console.

  [0] https://review.openstack.org/#/c/498387/
  [1] https://review.openstack.org/#/c/263763/

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1718545/+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 1496610] Re: Access and Security API access tab doesn't reflect keystone v3 auth url

[Akihiro Motoki]

As of now, we see version-less endpoint for identity service like
http://172.27.201.206/identity


** Changed in: horizon
 Assignee: Dan Nguyen (daniel-a-nguyen) => (unassigned)

** Changed in: horizon
   Status: In Progress => New

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

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

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

Title:
  Access and Security API access tab doesn't reflect keystone v3 auth
  url

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Desc:
  -
  The Access and Security API access tab in Horizon is currently located: 
http:///project/access_and_security/
  The table displays services and corresponding service endpoints.

  The Identity row shows the endpoint from the keystone catalog in the
  session which only contains v2 regardless of what horizon has
  currently configured in local_settings.py

  This effects both the view rendered on the page and the download
  openrc option.

  Proposed fix:
  
  Replace this value with what is set in horizon's local_settings.py

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1496610/+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 1481131] Re: "Create Subnet" modal dialog has css error when "Network Address" is blank

[Akihiro Motoki]

This bug no longer exists. The error message "Specify "Network Address"
or clear "Create Subnet" checkbox in previous step." was shown at the
top header when I click Next while keeping "Network Address" blank.

** Changed in: horizon
 Assignee: qiaomin032 (chen-qiaomin) => (unassigned)

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

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

Title:
  "Create Subnet" modal dialog has css error when "Network Address" is
  blank

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Reproduce the bug:
  1, Click "Create Subnet" button in the network detail page and will open the 
modal dialog, click the "next" button when "Network Address" is blank.
  2, There will display "This field is required.", but the string has css error.
  3, I will provide a picture for more detail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1481131/+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 1714796] Re: Router interface not updated during DVR->HA, HA->DVR migratons

[OpenStack Infra]

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

commit 0afe2c201a7d114564a0f0aed03ba91ffd776023
Author: venkata anil 
Date:   Sun Sep 3 17:52:04 2017 +

Fix device_owner during DVR and HA migrations

When HA router is migrated to DVR, router's
DEVICE_OWNER_HA_REPLICATED_INT interface has to be updated
to DEVICE_OWNER_DVR_INTERFACE.

Similarly for DVR to HA migration, DEVICE_OWNER_DVR_INTERFACE
has to be updated to DEVICE_OWNER_HA_REPLICATED_INT.

Also, for Legacy to HA migration, DEVICE_OWNER_ROUTER_INTF
has to be updated to DEVICE_OWNER_HA_REPLICATED_INT.

Also added unit test cases for all possible migration cases.

Closes-Bug: 1714796
Change-Id: I23642b3f5fe8411d0c8c526750f6965caa71fc2f


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

Title:
  Router interface not updated during DVR->HA, HA->DVR migratons

Status in neutron:
  Fix Released

Bug description:
  While debugging migration tests failures for gate-tempest-dsvm-
  neutron-dvr-multinode-scenario-ubuntu-xenial-nv job, I observed that
  device_owner is not updated properly during migration.

  When HA router is migrated to DVR(i.e HA->DVR), router's
  DEVICE_OWNER_HA_REPLICATED_INT interface has to be updated to
  DEVICE_OWNER_DVR_INTERFACE. Similarly for DVR to HA migration,
  DEVICE_OWNER_DVR_INTERFACE has to be replaced with
  DEVICE_OWNER_HA_REPLICATED_INT.

  But the existing migration code [1] doesn't consider
  DEVICE_OWNER_HA_REPLICATED_INT. As DVR and HA code depends on these
  device_owner types, it has to be updated properly.

  [1]
  
https://github.com/openstack/neutron/blob/master/neutron/db/l3_dvr_db.py#L127-L137

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1714796/+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 1700926] Re: Exception Error logs shown in Citrix XenServer CI

[OpenStack Infra]

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

commit aaddd51d6fa8863a505e3f33810660b0b27be14d
Author: naichuans 
Date:   Wed Jun 28 08:36:29 2017 +

xenapi: Exception Error logs shown in Citrix XenServer CI

There are many errors in the patchs which passed our XenServer CI,
it is because when run tempest, test case will ask nova sevice to
do snapshotting, then delete image before snapshotting done. Then
nova compute service couldn't find the image when do image upload
and raise an exception.
Normally the exception can be consumed by nova service. But the
exception generated by os-xenapi can't be recognized by nova, so
the error logs come out.
Add a exception which computer service can process.
Modify vmops.py to transfer exception to Nova compute.
Add unit test for exception transfer

Change-Id: I49f1a2aab507cc4b1c4a3d6c13df96ee3e678a99
Depends-On: I16d199e93f615e4f374d49948dceeb4d1d600aa9
Depends-On: I80007bb897a1f7eda47ebda82e08fe270f97ff40
Closes-Bug: 1700926


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

Title:
  Exception Error logs shown in Citrix XenServer CI

Status in OpenStack Compute (nova):
  Fix Released
Status in os-xenapi:
  Fix Released

Bug description:
  From a patch https://review.openstack.org/#/c/459485/ which passed our 
XenServer CI, we can see there are some errors in nova 
http://dd6b71949550285df7dc-dda4e480e005aaa13ec303551d2d8155.r49.cf1.rackcdn.com/85/459485/4/check/dsvm-tempest-neutron-network/61927a4/logs/screen-n-cpu.txt.gz
  We need to figure out whether this is real problem or just configuration 
problem
  2017-04-25 03:41:04.891 5135 DEBUG nova.virt.xenapi.vm_utils 
[req-600bd486-ca26-4a98-bcae-9ed50cea1f6b 
tempest-ImagesOneServerNegativeTestJSON-218904050 
tempest-ImagesOneServerNegativeTestJSON-218904050] VHD 
00e1b23b-9926-477a-a766-6e792d1a435d has parent 
5f75df8a-b35f-447b-a731-7b1e12297271 _get_vhd_parent_uuid 
/opt/stack/new/nova/nova/virt/xenapi/vm_utils.py:1979
  2017-04-25 03:41:04.895 5135 DEBUG nova.virt.xenapi.vm_utils 
[req-600bd486-ca26-4a98-bcae-9ed50cea1f6b 
tempest-ImagesOneServerNegativeTestJSON-218904050 
tempest-ImagesOneServerNegativeTestJSON-218904050] VHD 
5f75df8a-b35f-447b-a731-7b1e12297271 has parent 
1afecff1-7ee0-405a-9f87-5e2b674657b2 _get_vhd_parent_uuid 
/opt/stack/new/nova/nova/virt/xenapi/vm_utils.py:1979
  2017-04-25 03:41:04.988 5135 DEBUG os_xenapi.client.session 
[req-600bd486-ca26-4a98-bcae-9ed50cea1f6b 
tempest-ImagesOneServerNegativeTestJSON-218904050 
tempest-ImagesOneServerNegativeTestJSON-218904050] glance.py.upload_vhd2 
attempt 1/1, callback_result: http://192.168.33.1:9292 
call_plugin_serialized_with_retry 
/opt/stack/new/os-xenapi/os_xenapi/client/session.py:242
  2017-04-25 03:41:05.233 5135 DEBUG os_xenapi.client.session 
[req-600bd486-ca26-4a98-bcae-9ed50cea1f6b 
tempest-ImagesOneServerNegativeTestJSON-218904050 
tempest-ImagesOneServerNegativeTestJSON-218904050] Got exception: 
['XENAPI_PLUGIN_FAILURE', 'upload_vhd2', 'PluginError', 'Got Permanent Error 
response [404] while uploading image [244e93c0-28f1-4951-b922-665908bef7d5] to 
glance 
http://192.168.33.1:9292/v2/images/244e93c0-28f1-4951-b922-665908bef7d5/file'] 
_unwrap_plugin_exceptions 
/opt/stack/new/os-xenapi/os_xenapi/client/session.py:295
  2017-04-25 03:41:05.448 5135 DEBUG nova.compute.manager 
[req-600bd486-ca26-4a98-bcae-9ed50cea1f6b 
tempest-ImagesOneServerNegativeTestJSON-218904050 
tempest-ImagesOneServerNegativeTestJSON-218904050] [instance: 
92c76bb9-8dfb-4b35-9ee4-137ec23b82d5] Cleaning up image 
244e93c0-28f1-4951-b922-665908bef7d5 decorated_function 
/opt/stack/new/nova/nova/compute/manager.py:235
  2017-04-25 03:41:05.448 5135 ERROR nova.compute.manager [instance: 
92c76bb9-8dfb-4b35-9ee4-137ec23b82d5] Traceback (most recent call last):
  2017-04-25 03:41:05.448 5135 ERROR nova.compute.manager [instance: 
92c76bb9-8dfb-4b35-9ee4-137ec23b82d5] File 
"/opt/stack/new/nova/nova/compute/manager.py", line 231, in decorated_function
  2017-04-25 03:41:05.448 5135 ERROR nova.compute.manager [instance: 
92c76bb9-8dfb-4b35-9ee4-137ec23b82d5] *args, **kwargs)
  2017-04-25 03:41:05.448 5135 ERROR nova.compute.manager [instance: 
92c76bb9-8dfb-4b35-9ee4-137ec23b82d5] File 
"/opt/stack/new/nova/nova/compute/manager.py", line 3128, in snapshot_instance
  2017-04-25 03:41:05.448 5135 ERROR nova.compute.manager [instance: 
92c76bb9-8dfb-4b35-9ee4-137ec23b82d5] task_states.IMAGE_SNAPSHOT)
  2017-04-25 03:41:05.448 5135 ERROR nova.compute.manager [instance: 
92c76bb9-8dfb-4b35-9ee4-137ec23b82d5] File 

[Yahoo-eng-team] [Bug 1718545] [NEW] [vnc]vncserver_proxyclient_address and [vnc]vncserver_listen removed without deprecation

[Eric Fried]

Public bug reported:

[0] removed options [vnc]vncserver_proxyclient_address and
[vnc]vncserver_listen without a deprecation period.  Lemme splain:

Take for example vncserver_proxyclient_address.  It was originally
[DEFAULT]vncserver_proxyclient_address.  That was moved to
[vnc]vncserver_proxyclient_address via [1].  We've had a nice long
deprecation period (~18mo) during which either of those would work.  So
it would be reasonable at this time to remove support for
[DEFAULT]vncserver_proxyclient_address.  But by renaming the option
without changing its deprecated_group to `vnc`, we've instead *left*
support for [DEFAULT]vncserver_proxyclient_address while *removing*
support for the newer [vnc]vncserver_proxyclient_address without a
deprecation period.

I noticed this when running tox against nova-powervm with the latest
nova.  nova-powervm paid attention to the deprecation and switched over
to [vnc]vncserver_proxyclient_address.  Now it fails a test with:

Captured traceback:
~~~
Traceback (most recent call last):
  File 
"/home/efried/Neo/nova-powervm/.tox/py27/local/lib/python2.7/site-packages/mock/mock.py",
 line 1305, in patched
return func(*args, **keywargs)
  File "nova_powervm/tests/virt/powervm/test_driver.py", line 1666, in 
test_get_vnc_console
resp = self.drv.get_vnc_console(mock.ANY, self.inst)
  File "nova_powervm/virt/powervm/driver.py", line 1727, in get_vnc_console
host = CONF.vnc.vncserver_proxyclient_address
  File 
"/home/efried/Neo/nova-powervm/.tox/py27/local/lib/python2.7/site-packages/oslo_config/cfg.py",
 line 3363, in __getattr__
return self._conf._get(name, self._group)
  File 
"/home/efried/Neo/nova-powervm/.tox/py27/local/lib/python2.7/site-packages/oslo_config/cfg.py",
 line 2925, in _get
value = self._do_get(name, group, namespace)
  File 
"/home/efried/Neo/nova-powervm/.tox/py27/local/lib/python2.7/site-packages/oslo_config/cfg.py",
 line 2942, in _do_get
info = self._get_opt_info(name, group)
  File 
"/home/efried/Neo/nova-powervm/.tox/py27/local/lib/python2.7/site-packages/oslo_config/cfg.py",
 line 3099, in _get_opt_info
raise NoSuchOptError(opt_name, group)
oslo_config.cfg.NoSuchOptError: no such option 
vncserver_proxyclient_address in group [vnc]

But anyone should be able to repro by spinning up compute with
[vnc]vncserver_proxyclient_address and trying to open a console.

[0] https://review.openstack.org/#/c/498387/
[1] https://review.openstack.org/#/c/263763/

** Affects: nova
 Importance: High
 Status: Triaged


** Tags: config

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

Title:
  [vnc]vncserver_proxyclient_address and [vnc]vncserver_listen removed
  without deprecation

Status in OpenStack Compute (nova):
  Triaged

Bug description:
  [0] removed options [vnc]vncserver_proxyclient_address and
  [vnc]vncserver_listen without a deprecation period.  Lemme splain:

  Take for example vncserver_proxyclient_address.  It was originally
  [DEFAULT]vncserver_proxyclient_address.  That was moved to
  [vnc]vncserver_proxyclient_address via [1].  We've had a nice long
  deprecation period (~18mo) during which either of those would work.
  So it would be reasonable at this time to remove support for
  [DEFAULT]vncserver_proxyclient_address.  But by renaming the option
  without changing its deprecated_group to `vnc`, we've instead *left*
  support for [DEFAULT]vncserver_proxyclient_address while *removing*
  support for the newer [vnc]vncserver_proxyclient_address without a
  deprecation period.

  I noticed this when running tox against nova-powervm with the latest
  nova.  nova-powervm paid attention to the deprecation and switched
  over to [vnc]vncserver_proxyclient_address.  Now it fails a test with:

  Captured traceback:
  ~~~
  Traceback (most recent call last):
File 
"/home/efried/Neo/nova-powervm/.tox/py27/local/lib/python2.7/site-packages/mock/mock.py",
 line 1305, in patched
  return func(*args, **keywargs)
File "nova_powervm/tests/virt/powervm/test_driver.py", line 1666, in 
test_get_vnc_console
  resp = self.drv.get_vnc_console(mock.ANY, self.inst)
File "nova_powervm/virt/powervm/driver.py", line 1727, in 
get_vnc_console
  host = CONF.vnc.vncserver_proxyclient_address
File 
"/home/efried/Neo/nova-powervm/.tox/py27/local/lib/python2.7/site-packages/oslo_config/cfg.py",
 line 3363, in __getattr__
  return self._conf._get(name, self._group)
File 
"/home/efried/Neo/nova-powervm/.tox/py27/local/lib/python2.7/site-packages/oslo_config/cfg.py",
 line 2925, in _get
  value = self._do_get(name, group, namespace)
File 

[Yahoo-eng-team] [Bug 1426816] Re: PageObject's switch_window doesn't switch to new tab

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

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

Title:
  PageObject's switch_window doesn't switch to new tab

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

Bug description:
  switch_window works when the page is opened in a new windows, but
  doesn't work when the page is opened in a new tab.

  Take test_dashboard_help_redirection for example: the help link try to open 
docs.openstack.org, the chrome browser will open the link in a new tab,  the  
  switch_window won't switch to new tab

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1426816/+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 1429792] Re: log_out doesn't work after test_dashboard_help_redirection executed

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

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

Title:
  log_out doesn't work after test_dashboard_help_redirection executed

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

Bug description:
  Test step :
  1:  Testcase test_dashboard_help_redirection executed

  2:  try to logout
  self.home_pg.go_to_home_page()  & self.home_pg.log_out()

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1429792/+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 1432373] Re: Horizon: port create missing options

[Akihiro Motoki]

All features except extra-dhcp-opts are already supported or covered by other 
bugs, so marking this as Invalid.
if extra-dhcp-opts support is needed, it should be filed as a separate specific 
bug.

** Changed in: horizon
Milestone: next => None

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

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

Title:
  Horizon: port create missing options

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  nova-manage version: 2015.1

  In Horizon, port create is missing options compared to CLI:
   --tenant-id
   --mac-address
   --fixed-ip
   --security-group
   --no-security-groups
   --extra-dhcp-opt

  *
  ubuntu@trusty1:~/devstack$ neutron help port-create
  usage: neutron port-create [-h] [-f {html,json,shell,table,value,yaml}]
 [-c COLUMN] [--max-width ]
 [--prefix PREFIX] [--request-format {json,xml}]
 [--tenant-id TENANT_ID] [--name NAME]
 [--admin-state-down] [--mac-address MAC_ADDRESS]
 [--device-id DEVICE_ID]
 [--fixed-ip subnet_id=SUBNET,ip_address=IP_ADDR]
 [--security-group SECURITY_GROUP | 
--no-security-groups]
 [--extra-dhcp-opt EXTRA_DHCP_OPTS]
 NETWORK

  Create a port for a given tenant.

  positional arguments:
NETWORK   Network ID or name this port belongs to.

  optional arguments:
-h, --helpshow this help message and exit
--request-format {json,xml}
  The XML or JSON request format.
--tenant-id TENANT_ID
  The owner tenant ID.
--name NAME   Name of this port.
--admin-state-downSet admin state up to false.
--mac-address MAC_ADDRESS
  MAC address of this port.
--device-id DEVICE_ID
  Device ID of this port.
--fixed-ip subnet_id=SUBNET,ip_address=IP_ADDR
  Desired IP and/or subnet for this port:
  subnet_id=,ip_address=.You can repeat
  this option.
--security-group SECURITY_GROUP
  Security group associated with the port. You can
  repeat this option.
--no-security-groups  Associate no security groups with the port.
--extra-dhcp-opt EXTRA_DHCP_OPTS
  Extra dhcp options to be assigned to this port:
  opt_name=,opt_value=. You can
  repeat this option.

  *

  Steps to repro:
  1. Log in Horizon as admin.
  2. At left panel, Admin->System->Networks.
  3. Select a network by clicking on the Network Name.
  4. Ports->Create Port

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1432373/+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 1252529] Re: Edit share network from topology graph not visible for admin users

[Akihiro Motoki]

It was reported long ago. Since then, there were a lot of improvements
on policy-based action and the feature now works (as of now). Marking it
as Invalid.

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

** Changed in: horizon
Milestone: next => None

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

Title:
  Edit share network from topology graph not visible for admin users

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  When a network is marked as "Shared", Admin users cannot edit them
  directly from Project -> Network Topology since the filter is only
  checking for Shared.

  The only way to do it is through Admin -> Networks.

  If it's not a feature, then:

  Steps to reproduce ( using neutron and devstack ):

  [1] Login as admin user
  [1] Mark public subnet as 'Share'
  [2] Go to project 'demo'
  [3] Click Network Topology
  [4] Click on public network
  [5] Action's is empty for Public Subnet.

  Expected Results:
   Admin shall be able to edit the subnet inside the project view.

  There's a fix also, in case that we want this behavior included.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1252529/+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 1511879] Re: Integration_tests: id_pattern not working for instances secondary row actions

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

** Tags added: integration-tests

** Changed in: horizon
   Status: In Progress => 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/1511879

Title:
  Integration_tests: id_pattern not working for instances secondary row
  actions

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

Bug description:
   id_pattern not working for instances secondary row actions

  in regions->tables.py under the class ComplexActionRowRegion

  id_patterns are handled by "src_elem.get_attribute('id')" which works
  fine for other page table, row actions but not for Instances.

  The cause is, "src_elem.get_attribute('id')" returns 
"instances__row__2665f131-01cc-48ca-aa68-c0c823d6b292" instead of 
  "instances__row_2665f131-01cc-48ca-aa68-c0c823d6b292"

  The diff is "row__", the correct id value is "row_", this could be
  handled by string.replace()

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1511879/+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 1619042] Re: Horizon integration tests lack support to login with a domain name

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

** Tags added: integration-tests

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

** Changed in: horizon
Milestone: next => None

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

Title:
  Horizon integration tests lack support to login with a domain name

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

Bug description:
  PROBLEM:

  Currently, in horizon integration tests , there is only login performed with 
username/password . 
  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/test/integration_tests/pages/loginpage.py#L69
  However in our mitaka based deployment, we have another login parameter that 
is keystone domain.  
  when trying to run integration tests, we saw this lack of support in horizon 
tests to specify domain name as login parameter , 
https://github.com/openstack/horizon/blob/master/openstack_dashboard/test/integration_tests/horizon.conf
 

  This indicates horizon integration tests are outdated , since the
  tempest-horizon had already added support to login with domain
  https://github.com/openstack/tempest-
  
horizon/blob/master/tempest_horizon/tests/scenario/test_dashboard_basic_ops.py#L106

  PROPOSED SOLUTION: add additional parameter to specify the domain in
  horizon.conf and also add it to login methods.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1619042/+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 1355748] Re: Integration tests - IE webdrivers

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

** Changed in: horizon
   Status: In Progress => 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/1355748

Title:
  Integration tests - IE webdrivers

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

Bug description:
  Currently the Integration tests only uses  Selenium's FirefoxDriver, making 
Firefox the sole browser being tested.
  Selenium WebDriver also support InternetExplorerDriver and few other less 
interesting browsers (IMHO at least).
  The integration tests should run on these browsers as well, to discover 
browser-specific issues.

  Useful info from Selenium Wiki:

  
  1. Internet Explorer Driver: 
https://code.google.com/p/selenium/wiki/InternetExplorerDriver

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1355748/+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 1405033] Re: Integration test: LoginPage doesn't support multiple regions

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

** Changed in: horizon
   Status: In Progress => 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/1405033

Title:
  Integration test: LoginPage doesn't support multiple regions

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

Bug description:
  Testing step:
  1: setup a devstack with a multi-region deployment
  2: enable multiple regions in horizon local_settings.py
  3: ./run_tests.sh --integraion
  Integration tests all failed

  openstack_dashboard.test.integration_tests.pages.loginPage.LoginPage
  doesn't work in a multiple regions deployment

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1405033/+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 1431465] Re: Switch to tabs doesn't work in Horizon Integration tests.

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

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

Title:
  Switch to tabs doesn't work in Horizon Integration tests.

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

Bug description:
  Switch to tabs doesn't work in Horizon Integration tests.

  If TabbedFormRegion from forms.py is being used to create the forms
  which have multiple tabs in the page, then switch to tabs does not
  really work.

  1. When a field element from next or any other tabbedform is being used the 
respective tab must be clicked.
  2. SUBMIT button actions does not work: When SUBMIT button available only in 
last tabs, and if user is not calling last tab then SUBMIT button will not be 
displayed until we click on the last available tab. e.g. SUBMIT in Create 
Networks form page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1431465/+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 1414757] Re: Add integration tests of instance creation and deletion

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

** Changed in: horizon
   Status: In Progress => 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/1414757

Title:
  Add integration tests of instance creation and deletion

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

Bug description:
  Currently we have integration tests for image and flavor creation/deletion. 
  It would be nice to follow similar suit like image creation, to create an 
instance from the image created from "http_image" in horizon.conf, and boot a 
test instance from that cirros image.
  As a further extension, test the vnc console when the instance is running, 
vnc console status can be checked easily as its an iframe element and selenium 
allows driver to switch between frame elements , and get access to their 
elements 
  Source for selenium usage of frames : 
https://code.google.com/p/selenium/source/browse/py/selenium/webdriver/remote/switch_to.py
  After vnc console is checked, delete the test vm in teardown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1414757/+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 1416493] Re: Cover the case of user editing his current project in integration tests

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

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

Title:
  Cover the case of user editing his current project in integration
  tests

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

Bug description:
  The regression fixed in bug 1413068 needs to be checked in integration
  tests, namely in a TestCase for projects editing. Once the commit
  https://review.openstack.org/#/c/110919/ is mature enough that would
  be possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1416493/+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 1353334] Re: Integration tests - running tests as different users

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

** Changed in: horizon
   Status: In Progress => 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/1353334

Title:
  Integration tests - running tests as different users

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

Bug description:
  It is not possible to run one test from perspective of two different
  users (also two different users roles) or run test only under admin
  user without editing the configuration file and changing the
  configuration globally for all tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1353334/+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 1406128] Re: running integration tests concurently

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

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

** Changed in: horizon
Milestone: next => None

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

Title:
  running integration tests concurently

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

Bug description:
  It is not possible right now to run horizon selenium integration tests
  concurently.

  This request emerged in [0]. Because of following reasons(quoting
  Timur Sufiev):

  I guess the whole point of running tests as more than 2 users is the
  ability to run concurrently more than 1 suite of integration tests
  against the single devstack instance (different browsers, different
  Linux versions on the horizon host) - the exact combinations are
  perhaps will be left to the people setting up the environment,
  nevertheless upstream gate is not the only place that would benefit
  from these tests.

  For example in Mirantis Openstack we need to run integration tests
  both for Horizon being deployed on CentOS and on Ubuntu. The ability
  to use a single devstack node for both sets of test could lower the
  requirements to the hardware on the gate (though I'm not sure yet that
  it will be done this exact way). It is known that concurrent running
  of 2 test suites as one user on one devstack host could pose a
  problem, at least from Keystone side (tokens handling).

  Proposed solution:

  I suggest to take advantage of nosetests argument --processes [1] and
  in each separate process create two types of users (admin and demo-
  like) using this patch [2].

  [0] https://review.openstack.org/#/c/115092
  [1] 
http://nose.readthedocs.org/en/latest/plugins/multiprocess.html#cmdoption--processes
  [2] https://review.openstack.org/#/c/143027/

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1406128/+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 1416495] Re: Cover the case of creating new project during new user creation in integration tests

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

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

Title:
  Cover the case of creating new project during new user creation in
  integration tests

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

Bug description:
  The regression fixed in bug 1410129 needs to be checked in integration
  tests, namely in a TestCase for user creation. Once both commits
  https://review.openstack.org/#/c/110919/ and
  https://review.openstack.org/#/c/143027/ are mature enough that would
  be possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1416495/+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 1568386] Re: Integration tests fail due to slow creation of an instance

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

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

Title:
  Integration tests fail due to slow creation of an instance

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

Bug description:
  If you ever encounter traceback like this in the results of gate-
  horizon-dsvm-integration job

  2016-04-09 19:32:21.451 | 2016-04-09 19:32:21.432 | Traceback (most recent 
call last):
  2016-04-09 19:32:21.453 | 2016-04-09 19:32:21.433 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/tests/test_instances.py",
 line 197, in test_filter_instances
  2016-04-09 19:32:21.455 | 2016-04-09 19:32:21.435 | 
self.assertTrue(instances_page.is_instance_active(instance_list[0]))
  2016-04-09 19:32:21.456 | 2016-04-09 19:32:21.437 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/project/compute/instancespage.py",
 line 115, in is_instance_active
  2016-04-09 19:32:21.458 | 2016-04-09 19:32:21.438 | lambda: 
row.cells[self.INSTANCES_TABLE_STATUS_COLUMN], 'Active')
  2016-04-09 19:32:21.460 | 2016-04-09 19:32:21.440 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/regions/tables.py",
 line 158, in is_cell_status
  2016-04-09 19:32:21.462 | 2016-04-09 19:32:21.443 | 
self._wait_till_text_present_in_element(cell_getter, status)
  2016-04-09 19:32:21.464 | 2016-04-09 19:32:21.444 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 110, in _wait_till_text_present_in_element
  2016-04-09 19:32:21.466 | 2016-04-09 19:32:21.446 | 
self._wait_until(predicate, timeout)
  2016-04-09 19:32:21.468 | 2016-04-09 19:32:21.448 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 94, in _wait_until
  2016-04-09 19:32:21.469 | 2016-04-09 19:32:21.449 | predicate)
  2016-04-09 19:32:21.471 | 2016-04-09 19:32:21.451 |   File 
"/opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/support/wait.py",
 line 71, in until
  2016-04-09 19:32:21.472 | 2016-04-09 19:32:21.453 | value = 
method(self._driver)
  2016-04-09 19:32:21.474 | 2016-04-09 19:32:21.454 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 107, in predicate
  2016-04-09 19:32:21.476 | 2016-04-09 19:32:21.456 | elt = element() if 
hasattr(element, '__call__') else element
  2016-04-09 19:32:21.478 | 2016-04-09 19:32:21.458 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/project/compute/instancespage.py",
 line 115, in 
  2016-04-09 19:32:21.479 | 2016-04-09 19:32:21.460 | lambda: 
row.cells[self.INSTANCES_TABLE_STATUS_COLUMN], 'Active')
  2016-04-09 19:32:21.481 | 2016-04-09 19:32:21.462 | AttributeError: 
'NoneType' object has no attribute 'cells'

  It most likely means that an instance row was tested for the presence
  of a specific status even before this row had appeared. This (slow
  Nova response) could happen, but it shouldn't cause tests to fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1568386/+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 1525226] Re: Write an integration test for joint behavior of inline cell edit & confirmation of entity deletion

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

** Changed in: horizon
   Status: In Progress => 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/1525226

Title:
  Write an integration test for joint behavior of inline cell edit &
  confirmation of entity deletion

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

Bug description:
  While fix bug 1481850 keeps entity names shown in Confirm
  Delete/whatever modal dialog up to date, we should provide a test for
  this regression. Since it's very hard to write a simple python/js unit
  test on a border of python and js functionality (see the fix at
  https://review.openstack.org/256362), the simplest approach is to test
  this by means of Selenium integration tests.

  The natural candidate here is Identity->Projects table, since it was
  the table the original bug was filed for.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1525226/+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 1496063] Re: Add an integration test for switching between 2 projects of one user

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

** Changed in: horizon
   Status: In Progress => 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/1496063

Title:
  Add an integration test for switching between 2 projects of one user

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

Bug description:
  The bug 1450963 would have been caught earlier, if we had an
  integration test which switched 2 projects for one user and checked
  for absence of error messages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1496063/+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 1544608] Re: test_image_create_delete race fails in gate-horizon-dsvm-integration with "AttributeError: 'NoneType' object has no attribute 'cells'"

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

** Tags added: integration-tests

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

Title:
  test_image_create_delete race fails in gate-horizon-dsvm-integration
  with "AttributeError: 'NoneType' object has no attribute 'cells'"

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

Bug description:
  http://logs.openstack.org/47/275747/3/gate/gate-horizon-dsvm-
  integration/b83e62a/console.html#_2016-02-09_01_25_30_551

  2016-02-09 01:25:30.551 | 2016-02-09 01:25:30.522 | Traceback (most recent 
call last):
  2016-02-09 01:25:30.555 | 2016-02-09 01:25:30.525 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/tests/test_image_create_delete.py",
 line 32, in test_image_create_delete
  2016-02-09 01:25:30.560 | 2016-02-09 01:25:30.531 | 
self.assertTrue(images_page.is_image_active(self.IMAGE_NAME))
  2016-02-09 01:25:30.562 | 2016-02-09 01:25:30.533 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/project/compute/imagespage.py",
 line 103, in is_image_active
  2016-02-09 01:25:30.569 | 2016-02-09 01:25:30.540 | 
self._wait_till_text_present_in_element(cell_getter, 'Active')
  2016-02-09 01:25:30.572 | 2016-02-09 01:25:30.543 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 107, in _wait_till_text_present_in_element
  2016-02-09 01:25:30.575 | 2016-02-09 01:25:30.546 | 
self._wait_until(predicate, timeout)
  2016-02-09 01:25:30.577 | 2016-02-09 01:25:30.548 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 91, in _wait_until
  2016-02-09 01:25:30.580 | 2016-02-09 01:25:30.551 | predicate)
  2016-02-09 01:25:30.582 | 2016-02-09 01:25:30.553 |   File 
"/opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/support/wait.py",
 line 71, in until
  2016-02-09 01:25:30.585 | 2016-02-09 01:25:30.556 | value = 
method(self._driver)
  2016-02-09 01:25:30.588 | 2016-02-09 01:25:30.559 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 104, in predicate
  2016-02-09 01:25:30.592 | 2016-02-09 01:25:30.562 | elt = element() if 
hasattr(element, '__call__') else element
  2016-02-09 01:25:30.599 | 2016-02-09 01:25:30.569 |   File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/project/compute/imagespage.py",
 line 101, in cell_getter
  2016-02-09 01:25:30.602 | 2016-02-09 01:25:30.573 | return 
row.cells[self.IMAGES_TABLE_STATUS_COLUMN]
  2016-02-09 01:25:30.604 | 2016-02-09 01:25:30.575 | AttributeError: 
'NoneType' object has no attribute 'cells'

  Looks like this started around 2/8:

  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22AttributeError%3A%20'NoneType'%20object%20has%20no%20attribute%20'cells'%5C%22%20AND%20tags%3A%5C%22console%5C%22%20AND%20build_name%3A%5C
  %22gate-horizon-dsvm-integration%5C%22=7d

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1544608/+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 1615888] Re: integration test failed with non-en locale

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

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

** Changed in: horizon
Milestone: next => None

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

Title:
  integration test failed with non-en locale

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

Bug description:
  When running integration test without en locale, it failed. I found
  that current integration test cases, e.g.,
  integration_tests/tests/test_login.py, hard code the expected text
  rather than load the text from translation messages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1615888/+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 1658961] Re: The Create Port form is missing fixed ip input

[Akihiro Motoki]

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

** This bug has been marked a duplicate of bug 1588663
   cannot specify fixed ip when user create a port

** Changed in: horizon
Milestone: next => None

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

Title:
  The Create Port form is missing fixed ip input

Status in OpenStack Dashboard (Horizon):
  Confirmed

Bug description:
  When creating a port via CLI it is possible to specify the fixed ip
  argument:

  Help text info for neutron help port-create:
--fixed-ip subnet_id=SUBNET,ip_address=IP_ADDR
  Desired IP and/or subnet for this port:
  subnet_id=,ip_address=. You can repeat
  this option.
   
  root@node1:~# neutron port-create N1 --fixed-ip ip_address=14.0.0.5
  Created a new port:
  
+-+-+
  | Field   | Value 
  |
  
+-+-+
  | admin_state_up  | True  
  |
  | binding:host_id |   
  |
  | binding:profile | {}
  |
  | binding:vif_details | {}
  |
  | binding:vif_type| unbound   
  |
  | binding:vnic_type   | normal
  |
  | device_id   |   
  |
  | device_owner|   
  |
  | fixed_ips   | {"subnet_id": "5cc9b0fa-be8c-4bc5-9f79-1325b4cf766c", 
"ip_address": "14.0.0.5"} |
  | id  | c8ae4465-39d4-4171-a07e-e30b32facba1  
  |
  | mac_address | fa:16:3e:c9:2e:28 
  |
  | name|   
  |
  | network_id  | 5d41dcfa-b71e-4dca-8df6-3a02f603fd5e  
  |
  | status  | DOWN  
  |
  | tenant_id   | 915759cca11a48a8b4de4e40a9e21840  
  |
  
+-+-+

  This input is missing from the Create Port form. Is it a bug or a new
  feature?

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1658961/+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 1627010] Re: Issues with accessing FF profile by Selenium Webdriver in integration tests

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

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

Title:
  Issues with accessing FF profile by Selenium Webdriver in integration
  tests

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

Bug description:
  Stacktrace signature can either be

  2016-09-23 12:11:39.698828 | 2016-09-23 12:11:39.698 | _StringException: 
Traceback (most recent call last):
  2016-09-23 12:11:39.700537 | 2016-09-23 12:11:39.700 | File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/helpers.py", 
line 299, in setUp
  2016-09-23 12:11:39.703591 | 2016-09-23 12:11:39.702 | super(TestCase, 
self).setUp()
  2016-09-23 12:11:39.705580 | 2016-09-23 12:11:39.704 | File 
"/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/helpers.py", 
line 162, in setUp
  2016-09-23 12:11:39.707337 | 2016-09-23 12:11:39.706 | 
desired_capabilities=desired_capabilities
  2016-09-23 12:11:39.709230 | 2016-09-23 12:11:39.708 | File 
"/opt/stack/new/horizon/horizon/test/firefox_binary.py", line 87, in __init__
  2016-09-23 12:11:39.712891 | 2016-09-23 12:11:39.712 | desired_capabilities, 
proxy)
  2016-09-23 12:11:39.715117 | 2016-09-23 12:11:39.714 | File 
"/opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/firefox/webdriver.py",
 line 60, in __init__
  2016-09-23 12:11:39.717565 | 2016-09-23 12:11:39.717 | 
capabilities.update(self.options.to_capabilities())
  2016-09-23 12:11:39.719683 | 2016-09-23 12:11:39.719 | File 
"/opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/firefox/options.py",
 line 93, in to_capabilities
  2016-09-23 12:11:39.722995 | 2016-09-23 12:11:39.721 | 
desired["firefox_profile"] = self._profile.encoded
  2016-09-23 12:11:39.725622 | 2016-09-23 12:11:39.724 | File 
"/opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/firefox/firefox_profile.py",
 line 175, in encoded
  2016-09-23 12:11:39.729062 | 2016-09-23 12:11:39.728 | zipped.write(filename, 
filename[path_root:])
  2016-09-23 12:11:39.731219 | 2016-09-23 12:11:39.730 | File 
"/usr/lib/python2.7/zipfile.py", line 1123, in write
  2016-09-23 12:11:39.733183 | 2016-09-23 12:11:39.732 | st = os.stat(filename)
  2016-09-23 12:11:39.735987 | 2016-09-23 12:11:39.735 | OSError: [Errno 2] No 
such file or directory: '/tmp/tmpUJU0SW/lock'

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1627010/+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 1356770] Re: Integration tests - selenium - checking error message occurrence

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

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

Title:
  Integration tests - selenium - checking error message occurrence

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

Bug description:
  Wrapper for all page services (public methods) should be implemented,
  wrapper should be implemented in the basepage class and should check
  appearence of error message before service (page public method)
  execution and after.

  Right now one would have to check after every public method call if
  such message does not appear - thus verify that action did not cause
  any error.

  It is not possible to do this just once in tear down, because error
  messages dissapears when interacting with website(switching
  pages/clicking on forms).

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1356770/+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 1325725] Re: tempest doesn't have integration testing on nova's quota-class API

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

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

Title:
  tempest doesn't have integration testing on nova's quota-class API

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

Bug description:
  Related: https://bugs.launchpad.net/horizon/+bug/1292589

  Nova shouldn't have been able to remove that functionality if horizon
  was using it. So we have a gap in testing the APIs that horizon is
  using.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1325725/+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 1402387] Re: Integration test doesn't support to run with Chrome

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

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

Title:
  Integration test doesn't support to run with Chrome

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

Bug description:
  Currently,  the integration test uses Firefox  as the only supported
  web browser, the horizon should be tested with Chrome too

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1402387/+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 1644168] Re: integration tests crashes

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

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

Title:
  integration tests crashes

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

Bug description:
  I'm trying to launch integrations test of Horizon stable/newton. For every 
test I get the same error as this one a:
  ==
  ERROR: 
openstack_dashboard.test.integration_tests.tests.test_credentials.TestDownloadRCFile.test_download_rc_v2_file
  --
  _StringException: Attach browser log: {{{
  Traceback (most recent call last):
    File 
"/home/lfxb1698/Documents/horizon/openstack_dashboard/test/integration_tests/helpers.py",
 line 255, in log_exception
  yield
    File 
"/home/lfxb1698/Documents/horizon/openstack_dashboard/test/integration_tests/helpers.py",
 line 244, in _attach_browser_log
  self._unwrap_browser_log(self.driver.get_log('browser')))
    File 
"/home/lfxb1698/Documents/horizon/.venv/local/lib/python2.7/site-packages/selenium/webdriver/remote/webdriver.py",
 line 980, in get_log
  return self.execute(Command.GET_LOG, {'type': log_type})['value']
    File 
"/home/lfxb1698/Documents/horizon/.venv/local/lib/python2.7/site-packages/selenium/webdriver/remote/webdriver.py",
 line 236, in execute
  self.error_handler.check_response(response)
    File 
"/home/lfxb1698/Documents/horizon/.venv/local/lib/python2.7/site-packages/selenium/webdriver/remote/errorhandler.py",
 line 192, in check_response
  raise exception_class(message, screen, stacktrace)
  WebDriverException: Message: POST 
/session/1f444c6a-daa9-47cc-b75a-371fdaef281d/log did not match a known command
  }}}

  Attach page source: {{{
  Traceback (most recent call last):
    File 
"/home/lfxb1698/Documents/horizon/openstack_dashboard/test/integration_tests/helpers.py",
 line 255, in log_exception
  yield
    File 
"/home/lfxb1698/Documents/horizon/openstack_dashboard/test/integration_tests/helpers.py",
 line 222, in _attach_page_source
  f.write(self._get_page_html_source())
    File 
"/home/lfxb1698/Documents/horizon/openstack_dashboard/test/integration_tests/helpers.py",
 line 289, in _get_page_html_source
  return html_elem.get_attribute("innerHTML").encode("utf-8")
  AttributeError: 'NoneType' object has no attribute 'encode'
  }}}

  Traceback (most recent call last):
    File 
"/home/lfxb1698/Documents/horizon/openstack_dashboard/test/integration_tests/tests/test_credentials.py",
 line 28, in setUp
  super(TestDownloadRCFile, self).setUp()
    File 
"/home/lfxb1698/Documents/horizon/openstack_dashboard/test/integration_tests/helpers.py",
 line 307, in setUp
  self.home_pg.change_project(self.HOME_PROJECT)
    File 
"/home/lfxb1698/Documents/horizon/openstack_dashboard/test/integration_tests/pages/basepage.py",
 line 66, in change_project
  self.topbar.user_dropdown_project.click_on_project(name)
    File 
"/home/lfxb1698/Documents/horizon/openstack_dashboard/test/integration_tests/regions/menus.py",
 line 278, in click_on_project
  for item in self.menu_items:
    File 
"/home/lfxb1698/Documents/horizon/openstack_dashboard/test/integration_tests/regions/menus.py",
 line 190, in menu_items
  self.open()
    File 
"/home/lfxb1698/Documents/horizon/openstack_dashboard/test/integration_tests/regions/menus.py",
 line 211, in open
  self._wait_until(predicate)
    File 
"/home/lfxb1698/Documents/horizon/openstack_dashboard/test/integration_tests/basewebobject.py",
 line 103, in _wait_until
  predicate)
    File 
"/home/lfxb1698/Documents/horizon/.venv/local/lib/python2.7/site-packages/selenium/webdriver/support/wait.py",
 line 80, in until
  raise TimeoutException(message, screen, stacktrace)
  selenium.common.exceptions.TimeoutException: Message:

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1644168/+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 1718086] Re: Login of integrations test doesn't work

[Gary W. Smith]

Integration tests have been abandoned all together by Horizon. This no
longer applies.

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

Title:
  Login of integrations test doesn't work

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

Bug description:
  When running the test_login case, there is a timeout error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1718086/+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 1343684] Re: API pagination support for heat event list

[Gary W. Smith]

** Changed in: horizon
   Status: Won't Fix => 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/1343684

Title:
  API pagination support for heat event list

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  heat events pagination:
  https://review.openstack.org/#/c/104439
  https://review.openstack.org/#/c/105110/

  Once this is merged, we can add Previous and Next pagination support
  in Horizon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1343684/+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 1243136] Re: [Horizon] [LBaaS] Missing "Disassociation from pool" operation/button available also in the Monitors view

[Akihiro Motoki]

This is related to LBaaS v1 dashboard. LBaaS v1 API and its dashboard
was dropped a while ago, so Won't Fix.

** Changed in: horizon
Milestone: next => None

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

Title:
  [Horizon] [LBaaS] Missing "Disassociation from pool" operation/button
  available also in the Monitors view

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

Bug description:
  Version
  ===
  Havana on rhel

  
  Description
  ===

  It's possible to dissociate a health monitor from pool only in the
  Pools view, I think that this operation should be available also in
  the "Edit Monitor" or under the "More" button in the Monitors view.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1243136/+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 1639041] Re: neutron shared network created in CLI cannot be deleted in Horizon

[Akihiro Motoki]

As of Queens-1, this bug no longer exists. The logic has been improved
since the bug reported. Perhaps the policy support improvement helps it.

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

** Changed in: horizon
Milestone: next => None

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

Title:
  neutron shared network created in CLI cannot be deleted in Horizon

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  An user with admin roles can create and delete a shared network in CLI
  using neutron or openstack CLI; however, this same user cannot delete
  the shared network in Horizon (Mitaka) that was previously created in
  CLI. The error message is "Error: You are not allowed to delete
  network: shared_network". This does not effect non-shared network.

  The same user can create and delete a shared network in UI with no
  problem.

  Steps to reproduce:

  From CLI create a shared network
  neutron --insecure net-create TEST_NETWORK --share

  Login to Horizon and attempt to delete TEST_NETWORK

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1639041/+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 1453676] Re: --port-security-enabled=False/True option does not exist in network creation / update

[Akihiro Motoki]

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

** This bug has been marked a duplicate of bug 1634877
   It would be good to have the abilty to turn on/off port security

** Changed in: horizon
Milestone: next => None

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

Title:
  --port-security-enabled=False/True option does not exist in network
  creation / update

Status in OpenStack Dashboard (Horizon):
  Triaged

Bug description:
  According to RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1167496
  We need to add support of port-security-enabled=False/True when creating and 
updating network.
  version :
  ]# rpm -qa |grep horizon
  python-django-horizon-2015.1.0-2.el7.noarch


  this flag relevant to port creation  but it related to this bug :
  https://bugs.launchpad.net/horizon/+bug/1432373

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1453676/+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 1718455] Re: [pike] Nova host disable and Live Migrate all instances fail.

[Matt Riedemann]

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

** No longer affects: nova/ocata

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

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

** Changed in: nova/pike
   Importance: Undecided => Medium

** Tags added: scheduler

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

Title:
  [pike] Nova host disable and Live Migrate all instances fail.

Status in OpenStack Compute (nova):
  Confirmed
Status in OpenStack Compute (nova) pike series:
  Confirmed

Bug description:
  Disabling a host in horizon and live-migrating instances off fail with
  the following error if the instances are created with a single boot
  command. eg. create 10 cirros instances through the horizon dashboard.
  The instances are all KVM and backed by Cinder Volumes.

  2017-09-19 19:02:30.588 19741 DEBUG nova.scheduler.filter_scheduler
  [req-4268ea83-0657-40cc-961b-f0ae9fb3019e
  385c60230b3f49da930dda4d089eda6b 723aa12337a44f818b6d1e1a59f16e49 -
  default default] There are 1 hosts available but 10 instances
  requested to build. select_destinations /usr/lib/python2.7/dist-
  packages/nova/scheduler/filter_scheduler.py:101

  Steps to reproduce:

  1. Create 10 instances via the horizon dashboard at the same time. 
  2. Set a compute host disabled. 
  3. Choose the migrate host option and select live-migrate as the method. 
  4. The live migration will fail all after passing the scheduler with the 
error above. 

  NOTE: Creating 10 separate instances with individual "openstack server
  create" commands or running the launch instance 10 times in horizon
  does not produce the same result and the scheduler will evacuate the
  host as expected.

  Nova version on controller:

  ii  nova-api   2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - API frontend
  ii  nova-common2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - common files
  ii  nova-conductor 2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - conductor service
  ii  nova-consoleauth   2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - Console Authenticator
  ii  nova-novncproxy2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - NoVNC proxy
  ii  nova-placement-api 2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - placement API frontend
  ii  nova-scheduler 2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - virtual machine scheduler
  ii  python-nova2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute Python libraries
  ii  python-novaclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1718455/+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 1597302] Re: Horizon documentation about creating panels is outdated

[Ying Zuo]

This will be done as part of
https://blueprints.launchpad.net/horizon/+spec/pike-docs-overhaul.

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

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

Title:
  Horizon documentation about creating panels is outdated

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  So, the docs at
  
http://docs.openstack.org/developer/horizon/topics/tutorial.html#defining-a-panel
  tell than in order to define a panel one needs to define both panel,
  dashboard and panel group in python code, while actually they can be
  already created using plugin files, see
  https://github.com/openstack/horizon/tree/master/openstack_dashboard/enabled
  - which allows for greater flexibility and pluggability than the same
  thing in python code.

  Documentation needs to be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1597302/+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 1276735] Re: Admin/Flavors View Extra Specs does not render as a modal

[Ying Zuo]

Flavors Extra Specs has been removed from Horizon a few releases back.

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

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

Title:
  Admin/Flavors View Extra Specs does not render as a modal

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Each entry in the flavors table under admin/flavors has a row_action
  "More/View Extra Specs". This renders a modal as a separate page view
  instead of a modal.

  To reproduce this problem (assuming you are running devstack):

  1. Login as admin user
  2. Select the Admin project
  3. Select the Admin panel
  4. Click on the Flavors Panel in the sidebar
  5. For one of the rows in the flavors table, click the More button and select 
"View Extra Specs"

  You will be redirected to another page showing the View Extra Specs
  form information (instead of a modal).

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1276735/+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 1234912] Re: SNAT option for neutron

[Ivan Kolodyazhny]

Looks like it's already implemented in master. Please, re-open bug if
it's still actual

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

** Changed in: horizon
 Assignee: Wim De Clercq (wim-de-clercq) => (unassigned)

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

Title:
  SNAT option for neutron

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  When setting a gateway for a router, there is an option to
  enable/disable SNAT for the router. Currently, this option isn't
  available on horizon.. Here is a simple patch for your consideration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1234912/+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 1718512] [NEW] migration fails if instance build failed on destination host

[Eric M Gonzalez]

Public bug reported:

(OpenStack Nova, commit d8b30c3772, per OSA-14.2.7)

if an instance build fails on a hypervisor the "retry" field of the
instance's request spec is populated with which host and how many times
it attempted to retry the build. this field remains populated during the
life-time of the instance.

if a live-migration for the same instance is requested, the conductor
loads this request spec and passes it on to the scheduler. the scheduler
will fail the migration request on RetryFilter since the target was
already known to have failed (albeit, for the build).

with the help of mriedem and melwitt of #openstack-nova, we determined
that migration retries are handled separately from build retries.
mriedem suggested a patch to ignore the retry field of the instance
request spec during migrations. this patch allowed the failing migration
to succeed.

it is important to note that it may fail the migration again, however
there is still sufficient reason to ignore the build's failures/retries
during a migration.

12:55 < mriedem> it does stand to reason that if this instance failed to build 
originally on those 2 hosts, that live migrating it there might fail too...but 
we don't know why it originally failed, could have been a resource claim issue 
at the time
12:58 < melwitt> yeah, often it's a failed claim. and also what if that compute 
host is eventually replaced over the lifetime of the cluster, making it a fresh 
candidate for several instances that might still avoid it because they once 
failed to build there back when it was a different machine

** Affects: nova
 Importance: Undecided
 Assignee: Matt Riedemann (mriedem)
 Status: In Progress

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

Title:
  migration fails if instance build failed on destination host

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  (OpenStack Nova, commit d8b30c3772, per OSA-14.2.7)

  if an instance build fails on a hypervisor the "retry" field of the
  instance's request spec is populated with which host and how many
  times it attempted to retry the build. this field remains populated
  during the life-time of the instance.

  if a live-migration for the same instance is requested, the conductor
  loads this request spec and passes it on to the scheduler. the
  scheduler will fail the migration request on RetryFilter since the
  target was already known to have failed (albeit, for the build).

  with the help of mriedem and melwitt of #openstack-nova, we determined
  that migration retries are handled separately from build retries.
  mriedem suggested a patch to ignore the retry field of the instance
  request spec during migrations. this patch allowed the failing
  migration to succeed.

  it is important to note that it may fail the migration again, however
  there is still sufficient reason to ignore the build's
  failures/retries during a migration.

  12:55 < mriedem> it does stand to reason that if this instance failed to 
build originally on those 2 hosts, that live migrating it there might fail 
too...but we don't know why it originally failed, could have been a resource 
claim issue at the time
  12:58 < melwitt> yeah, often it's a failed claim. and also what if that 
compute host is eventually replaced over the lifetime of the cluster, making it 
a fresh candidate for several instances that might still avoid it because they 
once failed to build there back when it was a different machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1718512/+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 1203413] Re: VM launch fails with Neutron in "admin" tenant if "admin" and "demo" tenants have secgroups with a same name "web"

[Ivan Kolodyazhny]

Looks like we've already merged patch to Horizon

** 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 Compute (nova).
https://bugs.launchpad.net/bugs/1203413

Title:
  VM launch fails with Neutron in "admin" tenant if "admin" and "demo"
  tenants have secgroups with a same name "web"

Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in OpenStack Dashboard (Horizon) kilo series:
  Fix Released
Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  Using Grizzly with Neutron: If there are multiple security groups with
  the same name (in other tenants for example), it is not possible to
  boot an instance with this security group as Horizon will only use the
  name of the security group.

  Example from logs:
  2013-07-21 03:39:12.432 ERROR nova.network.security_group.quantum_driver 
[req-aaca5681-72b8-41dc-a89c-9a5c95c7eff4 33fe423e114c4586a573514b3e98341e 
e91fe07ea4834f8487c5cec7deaa2eac] Quantum Error: Multiple security_group 
matches found for name 'web', use an ID to be more specific.
  2013-07-21 03:39:12.439 ERROR nova.api.openstack 
[req-aaca5681-72b8-41dc-a89c-9a5c95c7eff4 33fe423e114c4586a573514b3e98341e 
e91fe07ea4834f8487c5cec7deaa2eac] Caught error: Multiple security_group matches 
found for name 'web', use an ID to be more specific.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1203413/+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 1285138] Re: Horizon, python-keystoneclient treat "primary project" / tenantId differently

[Ivan Kolodyazhny]

Closing this bug according to the previous comment

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

Title:
  Horizon, python-keystoneclient treat "primary project" / tenantId
  differently

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Horizon makes the "primary project" field mandatory while it's
  optional in python-keystoneclient.  we discussed this in SUSE:

  > > if a "primary project" is mandatory in the web interface, it should be in 
the
  > > command line as well.  or vice versa.

  > Actually... why?

  because consistency.  because with the current state of things you are heading
  for a steady stream (ok, just a trickle but steady anyway) of users asking 
this
  question.  the web ui makes it seem like the "primary project" is something
  crucial, and then the command line makes clear that it's actually superfluous,
  and since the user does not know (at the beginning) which it is, s/he'll be
  wondering: is it a bug in keystone(1)?  am i going to screw something up
  horribly if i create a user with no tenantId?  you'll have to document it,
  people will miss the documentation and ask support anyway...

  > Looking at the keystone and keystoneclient code, it's indeed
  > not mandatory to provide a primary project when creating a user. But that
  > doesn't mean that the webui should follow this: the webui is a simplified 
view
  > of OpenStack and doesn't allow everything OpenStack allows.

  we have one product with different interfaces.  (perceived) complexity of the
  overall system goes *up* as the interfaces diverge.  asymmetry increases
  cognitive load.  also, simplified means "a subset of" to me, and you can't
  change the "primary project" using keystone(1), Horizon is disjoint, maybe
  complementary, but not simplified.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1285138/+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 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong

[Ivan Kolodyazhny]

** 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 Compute (nova).
https://bugs.launchpad.net/bugs/1259292

Title:
  Some tests use assertEqual(observed, expected) , the argument order is
  wrong

Status in Astara:
  Fix Released
Status in Bandit:
  Fix Released
Status in Barbican:
  Fix Released
Status in Blazar:
  Triaged
Status in Ceilometer:
  Invalid
Status in Cinder:
  Fix Released
Status in congress:
  Fix Released
Status in daisycloud-core:
  New
Status in Designate:
  Fix Released
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in Glance:
  Fix Released
Status in glance_store:
  Fix Released
Status in Higgins:
  New
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Released
Status in Mistral:
  Fix Released
Status in Murano:
  Fix Released
Status in networking-calico:
  Fix Released
Status in networking-infoblox:
  In Progress
Status in networking-l2gw:
  Fix Released
Status in networking-sfc:
  Fix Released
Status in quark:
  In Progress
Status in OpenStack Compute (nova):
  Won't Fix
Status in os-brick:
  Fix Released
Status in PBR:
  Fix Released
Status in pycadf:
  Fix Released
Status in python-barbicanclient:
  Fix Released
Status in python-ceilometerclient:
  Invalid
Status in python-cinderclient:
  Fix Released
Status in python-designateclient:
  Fix Committed
Status in Glance Client:
  Fix Released
Status in python-mistralclient:
  Fix Released
Status in python-solumclient:
  Fix Released
Status in Python client library for Zaqar:
  Fix Released
Status in Rally:
  In Progress
Status in Sahara:
  Fix Released
Status in Solum:
  Fix Released
Status in sqlalchemy-migrate:
  In Progress
Status in SWIFT:
  In Progress
Status in tacker:
  Fix Committed
Status in tempest:
  Invalid
Status in zaqar:
  Fix Released

Bug description:
  The test cases will produce a confusing error message if the tests
  ever fail, so this is worth fixing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/astara/+bug/1259292/+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 1645568] Re: keystone-manage mapping_purge fails silently

[OpenStack Infra]

Reviewed:  https://review.openstack.org/408304
Committed: 
https://git.openstack.org/cgit/openstack/keystone/commit/?id=d03f35ee6753600bcd5ddfc8f692d00376284aa3
Submitter: Jenkins
Branch:master

commit d03f35ee6753600bcd5ddfc8f692d00376284aa3
Author: Aqsa 
Date:   Wed Mar 22 11:30:27 2017 +

Add unit tests to mapping_purge

This adds unit tests to mapping_purge.

Change-Id: I01a814f03e83911461168f4dac74202b6f0537d8
Closes-Bug: 1645568


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

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

Title:
   keystone-manage mapping_purge fails silently

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  Running the command keystone-manage mapping_purge, no output is given
  but I get these messages in keystone.log

  2016-11-18 07:41:22.807 2404 CRITICAL keystone [-] ValueError: At least one 
option must be provided
  2016-11-18 07:41:22.807 2404 ERROR keystone Traceback (most recent call last):
  2016-11-18 07:41:22.807 2404 ERROR keystone   File 
"/usr/bin/keystone-manage", line 10, in 
  2016-11-18 07:41:22.807 2404 ERROR keystone sys.exit(main())
  2016-11-18 07:41:22.807 2404 ERROR keystone   File 
"/usr/lib/python2.7/site-packages/keystone/cmd/manage.py", line 43, in main
  2016-11-18 07:41:22.807 2404 ERROR keystone cli.main(argv=sys.argv, 
config_files=config_files)
  2016-11-18 07:41:22.807 2404 ERROR keystone   File 
"/usr/lib/python2.7/site-packages/keystone/cmd/cli.py", line 1257, in main
  2016-11-18 07:41:22.807 2404 ERROR keystone CONF.command.cmd_class.main()
  2016-11-18 07:41:22.807 2404 ERROR keystone   File 
"/usr/lib/python2.7/site-packages/keystone/cmd/cli.py", line 830, in main
  2016-11-18 07:41:22.807 2404 ERROR keystone validate_options()
  2016-11-18 07:41:22.807 2404 ERROR keystone   File 
"/usr/lib/python2.7/site-packages/keystone/cmd/cli.py", line 813, in 
validate_options
  2016-11-18 07:41:22.807 2404 ERROR keystone raise ValueError(_('At least 
one option must be provided'))
  2016-11-18 07:41:22.807 2404 ERROR keystone ValueError: At least one option 
must be provided
  2016-11-18 07:41:22.807 2404 ERROR keystone

  
  Using --help says arguments needed are optional.
  I used --all option to check and the command was executed successfully. The 
way I see it is some arguments have been marked optional when they are actually 
necessary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1645568/+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 1718125] Re: Missing some contents for install prerequisites

[OpenStack Infra]

Reviewed:  https://review.openstack.org/505123
Committed: 
https://git.openstack.org/cgit/openstack/glance/commit/?id=2f8edeedc88491214d2502c5b1d17a155f452a47
Submitter: Jenkins
Branch:master

commit 2f8edeedc88491214d2502c5b1d17a155f452a47
Author: ericxiett 
Date:   Tue Sep 19 16:50:14 2017 +0800

Fix missing some content of glance database creation.

The indentation of glance database creation was incorrect.
This patch fixes it.

Change-Id: If3ca607258363f5b6e8e1b86e0425fd74da2e62a
Closes-Bug: #1718125


** Changed in: glance
   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/1718125

Title:
  Missing some contents for install prerequisites

Status in Glance:
  Fix Released
Status in neutron:
  In Progress

Bug description:
  Description
  ===
  Install glance followed by 
https://docs.openstack.org/glance/pike/install/install-rdo.html.
  But it missed content for create glance database.

  'To create the database, complete these steps:
  Use the database access client to connect to the database server as the root 
user:

  $ mysql -u root -p'

  Environment
  ===
  $ git log
  commit f8426378f892f250391b3d1004e27725d462481f
  Author: OpenStack Proposal Bot 
  Date: Fri Sep 15 07:16:27 2017 +

  Imported Translations from Zanata

  For more information about this automatic import see:
  https://docs.openstack.org/i18n/latest/reviewing-translation-import.html

  Change-Id: Ie31a9ea996d8e42530a37ed9a9616cc44ebe65c8

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1718125/+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 1704798] Re: GET /os-quota-sets/{tenant_id} API is failing with SSL exception

[Matt Riedemann]

** Changed in: nova
 Assignee: Sean Dague (sdague) => jichenjc (jichenjc)

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

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

** Changed in: nova/pike
   Status: New => In Progress

** Changed in: nova/pike
 Assignee: (unassigned) => jichenjc (jichenjc)

** Changed in: nova/pike
   Importance: Undecided => Medium

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

Title:
  GET /os-quota-sets/{tenant_id} API is failing with SSL exception

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) pike series:
  In Progress

Bug description:
  In the flow of GET /os-quota-sets/{tenant_id} API, when
  project_id/tenant_id is being verified by communicating with keystone
  through secure(https)connection at
  
https://github.com/openstack/nova/blob/master/nova/api/openstack/identity.py#L32,
  it is failing in certificate validation error as below.

  
  2017-07-06 01:13:28.134 21365 ERROR nova.api.openstack.identity Traceback 
(most recent call last):
  2017-07-06 01:13:28.134 21365 ERROR nova.api.openstack.identity   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/identity.py", line 42, in 
verify_project_id
  2017-07-06 01:13:28.134 21365 ERROR nova.api.openstack.identity 
raise_exc=False)
  2017-07-06 01:13:28.134 21365 ERROR nova.api.openstack.identity   File 
"/usr/lib/python2.7/site-packages/keystoneauth1/session.py", line 758, in get
  2017-07-06 01:13:28.134 21365 ERROR nova.api.openstack.identity return 
self.request(url, 'GET', **kwargs)
  2017-07-06 01:13:28.134 21365 ERROR nova.api.openstack.identity   File 
"/usr/lib/python2.7/site-packages/positional/__init__.py", line 101, in inner
  2017-07-06 01:13:28.134 21365 ERROR nova.api.openstack.identity return 
wrapped(*args, **kwargs)
  2017-07-06 01:13:28.134 21365 ERROR nova.api.openstack.identity   File 
"/usr/lib/python2.7/site-packages/keystoneauth1/session.py", line 616, in 
request
  2017-07-06 01:13:28.134 21365 ERROR nova.api.openstack.identity resp = 
send(**kwargs)
  2017-07-06 01:13:28.134 21365 ERROR nova.api.openstack.identity   File 
"/usr/lib/python2.7/site-packages/keystoneauth1/session.py", line 678, in 
_send_request
  2017-07-06 01:13:28.134 21365 ERROR nova.api.openstack.identity raise 
exceptions.SSLError(msg)
  2017-07-06 01:13:28.134 21365 ERROR nova.api.openstack.identity SSLError: SSL 
exception connecting to 
https://xxx.xxx.xxx.xxx:5000/v3/projects/0fe761dc32934fc88c390d244acb6971: 
("bad handshake: Error([('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 
'certificate verify failed')],)",)
  2017-07-06 01:13:28.134 21365 ERROR nova.api.openstack.identity

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1704798/+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 1714240] Re: glance re-spawns a child when terminating

[OpenStack Infra]

Reviewed:  https://review.openstack.org/499592
Committed: 
https://git.openstack.org/cgit/openstack/glance/commit/?id=877cd166b56ec4b7f5530ea9bf1587077692275b
Submitter: Jenkins
Branch:master

commit 877cd166b56ec4b7f5530ea9bf1587077692275b
Author: Bernhard M. Wiedemann 
Date:   Thu Aug 31 15:11:41 2017 +0200

Avoid restarting a child when terminating

When sending a SIGTERM to the main glance-api process,
it was sending a SIGTERM to its children
but then also re-spawning its first dead child.

Closes-bug: #1714240

Change-Id: Ibef426c198d287bbdac4e764fd654edba4b7c2d6


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

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

Title:
  glance re-spawns a child when terminating

Status in Glance:
  Fix Released

Bug description:
  When sending a SIGTERM to the main glance-api process,
  api.log shows
  2017-08-31 13:10:30.996 10618 INFO glance.common.wsgi [-] Removed dead child 
10628
  2017-08-31 13:10:31.004 10618 INFO glance.common.wsgi [-] Started child 10642
  2017-08-31 13:10:31.006 10642 INFO eventlet.wsgi.server [-] (10642) wsgi 
starting up on https://10.162.184.83:5510
  2017-08-31 13:10:31.008 10642 INFO eventlet.wsgi.server [-] (10642) wsgi 
exited, is_accepting=True
  2017-08-31 13:10:31.009 10642 INFO glance.common.wsgi [-] Child 10642 exiting 
normally

  This is because kill_children sends a SIGTERM to all children
  and wait_on_children restarts one, when it notices a dead child

  We noticed this, because this triggered a fencing in our cloud's
  pacemaker setup because systemd seems to have a race condition in the
  cgroup code that should detect that all related services have
  terminated.

  
  # systemctl status openstack-glance-api
  ● openstack-glance-api.service - OpenStack Image Service API server
 Loaded: loaded (/usr/lib/systemd/system/openstack-glance-api.service; 
disabled; vendor preset: disabled)
 Active: deactivating (final-sigterm) since Thu 2017-08-31 10:13:48 UTC; 
1min 14s ago
   Main PID: 25077 (code=exited, status=0/SUCCESS)
  Tasks: 0 (limit: 512)
 CGroup: /system.slice/openstack-glance-api.service
  Aug 31 10:13:48 d08-9e-01-b4-9e-42 systemd[1]: Stopping OpenStack Image 
Service API server...
  Aug 31 10:15:21 d08-9e-01-b4-9e-42 systemd[1]: openstack-glance-api.service: 
State 'stop-final-sigterm' timed out. Killing.
  Aug 31 10:15:21 d08-9e-01-b4-9e-42 systemd[1]: Stopped OpenStack Image 
Service API server.
  Aug 31 10:15:21 d08-9e-01-b4-9e-42 systemd[1]: openstack-glance-api.service: 
Unit entered failed state.
  Aug 31 10:15:21 d08-9e-01-b4-9e-42 systemd[1]: openstack-glance-api.service: 
Failed with result 'timeout'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1714240/+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 1717582] Re: fullstack job failing to create namespace because it's already exists

[OpenStack Infra]

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

commit fd1403fd9a971cf3cbd863fa33ca68eb019fbdc1
Author: Sławek Kapłoński 
Date:   Thu Sep 14 02:11:50 2017 +

Fix for race condition during netns creation

In some cases if ip_lib.IPWrapper.ensure_namespace() method
is called more than once for same namespace in very short
period of time it could raise error that "File already exists"
for second call of this method.
It happens often e.g. in fullstack tests.
Reason of such problem is in Netlink protocol which is used
by iproute2 to communicate with kernel. This protocol, according
to http://man7.org/linux/man-pages/man7/netlink.7.html is not
reliable so it is not guaranteed when the message will be
delivered to kernel and when action will be really executed.
Because of that if on quite loaded host ensure_namespace() method
would be executed twice it can lead to error described above.

This patch is changing way how ensure_namespace() method works
to avoid raising ProcessExecutionError exception with this
error message.

Closes-Bug: #1717582
Change-Id: I1898426789c85ce1faa97665bfd47f1fa38ef727


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

Title:
  fullstack job failing to create namespace because it's already exists

Status in neutron:
  Fix Released

Bug description:
  In fullstack tests there is many times error with creating e.g. "host-" 
namespace. Error message tells that such namespace already exists and test is 
failing because of that.
  It looks that this is kind of race condition when ip.netns.exists() method 
return false but few miliseconds later namespace already exists and 
ip.netns.add() method fails.
  It is in method ensure_namespace() in 
https://github.com/openstack/neutron/blob/master/neutron/agent/linux/ip_lib.py#L204

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1717582/+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 1715317] Re: Hybrid bridge should permanently keep MAC entries

[OpenStack Infra]

Reviewed:  https://review.openstack.org/501132
Committed: 
https://git.openstack.org/cgit/openstack/os-vif/commit/?id=fa4ff64b86e6e1b6399f7250eadbee9775c22d32
Submitter: Jenkins
Branch:master

commit fa4ff64b86e6e1b6399f7250eadbee9775c22d32
Author: Sahid Orentino Ferdjaoui 
Date:   Wed Sep 6 03:35:58 2017 -0400

ovs-hybrid: should permanently keep MAC entries

The linux bridge installed for the particular vif type ovs-hybrid
should be configured to persistently keep the MAC learned from the
RARP packets sent by QEMU when starting on destination node. That to
avoid any break of the datapath during a live-migration. That because
at some point of the live-migration source and destination can be on
a same L2 and we could have the destination bridge learning from source.

Change-Id: I50775df3629a079e6ba6f167ebfa499ffa5c7cac
Closes-Bug: 1715317
Related-Bug: 1414559


** Changed in: os-vif
   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/1715317

Title:
  Hybrid bridge should permanently keep MAC entries

Status in OpenStack Compute (nova):
  Incomplete
Status in os-vif:
  Fix Released

Bug description:
  The linux bridge installed for the particular vif type ovs-hybrid
  should be configured to persistently keep the MAC learned from the
  RARP packets sent by QEMU when starting on destination node. That to
  avoid any break of the datapath during a live-migration.

  That issue can be saying when using the opflex plugin.

https://github.com/noironetworks/python-opflex-
  agent/commit/3163b9a2668f29dd1e52e9757b8c25ef48822765

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1715317/+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 1718485] Re: instance.live.migration.force.complete is not a versioned notification and not whitelisted

[Matt Riedemann]

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

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

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

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

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

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

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

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

** Changed in: nova/newton
   Importance: Undecided => Medium

** Changed in: nova/ocata
   Importance: Undecided => Medium

** Changed in: nova/pike
   Importance: Undecided => Medium

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

Title:
  instance.live.migration.force.complete is not a versioned notification
  and not whitelisted

Status in OpenStack Compute (nova):
  Confirmed
Status in OpenStack Compute (nova) newton series:
  Confirmed
Status in OpenStack Compute (nova) ocata series:
  Confirmed
Status in OpenStack Compute (nova) pike series:
  Confirmed

Bug description:
  The instance.live.migration.force.complete legacy notification does
  not have any test coverage and therefore it is missed the whitelisting
  of allowed legacy notification. We should add test coverage and
  whitelist this notification.

  This is a problem since I034b4041414a797f65ede52db2963107f2ef7456 is
  merged in the Mitaka cycle

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1718485/+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 1718485] [NEW] instance.live.migration.force.complete is not a versioned notification and not whitelisted

[Balazs Gibizer]

Public bug reported:

The instance.live.migration.force.complete legacy notification does not
have any test coverage and therefore it is missed the whitelisting of
allowed legacy notification. We should add test coverage and whitelist
this notification.

This is a problem since I034b4041414a797f65ede52db2963107f2ef7456 is
merged in the Mitaka cycle

** Affects: nova
 Importance: Medium
 Assignee: Balazs Gibizer (balazs-gibizer)
 Status: Confirmed

** Affects: nova/newton
 Importance: Medium
 Status: Confirmed

** Affects: nova/ocata
 Importance: Medium
 Status: Confirmed

** Affects: nova/pike
 Importance: Medium
 Status: Confirmed


** Tags: notifications

** Tags added: notifications

** Changed in: nova
 Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)

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

Title:
  instance.live.migration.force.complete is not a versioned notification
  and not whitelisted

Status in OpenStack Compute (nova):
  Confirmed
Status in OpenStack Compute (nova) newton series:
  Confirmed
Status in OpenStack Compute (nova) ocata series:
  Confirmed
Status in OpenStack Compute (nova) pike series:
  Confirmed

Bug description:
  The instance.live.migration.force.complete legacy notification does
  not have any test coverage and therefore it is missed the whitelisting
  of allowed legacy notification. We should add test coverage and
  whitelist this notification.

  This is a problem since I034b4041414a797f65ede52db2963107f2ef7456 is
  merged in the Mitaka cycle

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1718485/+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 1718474] [NEW] Vzstorage driver doesn't lock when connecting volume

[Evgeny Antyshev]

Public bug reported:

Occasionally, Virtuozzo Storage CI fails 1 testcase, with following error in 
nova-compute:
Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Command: 
pstorage-mount -c testcluster_uypcf0k16f -u stack -g root -m 0770 -l 
/var/log/vstorage/testcluster_uypcf0k16f/nova.log.gz 
/opt/stack/data/nova/mnt/0d5556ed3994ee64ccc877564e48b2a4
Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Exit code: 255
Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Stdout: u''
Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Stderr: u'20-09-17 
09:40:55.782 vstorage-mount: mounting vstorage://testcluster_uypcf0k16f at 
/opt/stack/data/nova/mnt/0d5556ed3994ee64ccc877564e48b2a4 with flags: 0xc06, 
params: 
fd=3,rootmode=4,user_id=0,group_id=0,allow_other,default_permissions,writeback_enable,direct_enable,umount_wait,\nvstorage-mount:
 failed to initialize log file\n20-09-17 09:40:55.832 fuse_umount: 
/opt/stack/data/nova/mnt/0d5556ed3994ee64ccc877564e48b2a4\n' {{(pid=75667) loop 
/usr/lib/python2.7/site-packages/oslo_privsep/daemon.py:449}}

full log:
http://paste.openstack.org/show/621549/
http://openstack-3rd-party-storage-ci-logs.virtuozzo.com/44/504944/3/check/dsvm-tempest-kvm/eed2bd5/console.html

This is a consequence of simultaneously connecting 2 volumes, since
connect_volume() is not synchronized, like f.e. in Quobyte driver. BTW,
many other drivers should suffer from this mistake.

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

Title:
  Vzstorage driver doesn't lock when connecting volume

Status in OpenStack Compute (nova):
  New

Bug description:
  Occasionally, Virtuozzo Storage CI fails 1 testcase, with following error in 
nova-compute:
  Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Command: 
pstorage-mount -c testcluster_uypcf0k16f -u stack -g root -m 0770 -l 
/var/log/vstorage/testcluster_uypcf0k16f/nova.log.gz 
/opt/stack/data/nova/mnt/0d5556ed3994ee64ccc877564e48b2a4
  Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Exit code: 255
  Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Stdout: u''
  Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Stderr: u'20-09-17 
09:40:55.782 vstorage-mount: mounting vstorage://testcluster_uypcf0k16f at 
/opt/stack/data/nova/mnt/0d5556ed3994ee64ccc877564e48b2a4 with flags: 0xc06, 
params: 
fd=3,rootmode=4,user_id=0,group_id=0,allow_other,default_permissions,writeback_enable,direct_enable,umount_wait,\nvstorage-mount:
 failed to initialize log file\n20-09-17 09:40:55.832 fuse_umount: 
/opt/stack/data/nova/mnt/0d5556ed3994ee64ccc877564e48b2a4\n' {{(pid=75667) loop 
/usr/lib/python2.7/site-packages/oslo_privsep/daemon.py:449}}

  full log:
  http://paste.openstack.org/show/621549/
  
http://openstack-3rd-party-storage-ci-logs.virtuozzo.com/44/504944/3/check/dsvm-tempest-kvm/eed2bd5/console.html

  This is a consequence of simultaneously connecting 2 volumes, since
  connect_volume() is not synchronized, like f.e. in Quobyte driver.
  BTW, many other drivers should suffer from this mistake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1718474/+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 1688054] Re: Flavors in Administrator Guide - confusing description for rxtx factor

[OpenStack Infra]

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

commit a76277f81a005cb48088fd9452637b4e7ee1b9f5
Author: Stephen Finucane 
Date:   Wed Sep 6 16:44:53 2017 +0100

doc: Split flavors docs into admin and user guides

There are currently two docs describing flavors in 'admin', which
contain a lot of overlapping information. Fix this by keeping the
configuration guide (how to create, delete, modify flavors) in
'admin', while moving the reference-style parts into 'user'. We
cross-reference the two internally.

Given that large chunks of this needed to be rewritten, we've taken the
opportunity to fix a poor description for the RXTX factor, closing a
longstanding bug in the process.

Change-Id: Ia57c93ef1e72ccf134ba6fc7fcb85ab228d68a47
Closes-Bug: #1688054


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

Title:
  Flavors in Administrator Guide - confusing description for rxtx factor

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  - [x] This doc is inaccurate in this way: __

  The RXTX Factor description currently states:

  "Optional property allows created servers to have a different
  bandwidth cap than that defined in the network they are attached to.
  This factor is multiplied by the rxtx_base property of the network.
  Default value is 1.0. That is, the same as attached network. This
  parameter is only available for Xen or NSX based systems."

  The compute API reference has a better and more accurate description:

  https://developer.openstack.org/api-ref/compute/?expanded=create-
  flavor-detail#create-flavor

  "The receive / transmit factor (as a float) that will be set on ports
  if the network backend supports the QOS extension. Otherwise it will
  be ignored. It defaults to 1.0."

  The admin guide description is really talking about nova-network and
  the xen virt driver, which is not untrue, but is a bit confusing (I
  don't know where the NSX part comes from).

  But the way this is used with neutron in nova is on the port if the
  QOS extension is enabled. Nova will likely deprecate this field in the
  flavor resource since nova-network is deprecated and if you're doing
  QOS on ports you should be doing that via the networking service, not
  the compute service flavors.

  ---
  Release: 15.0.0 on 2017-05-03 11:19
  SHA: 991820bc90e3f08a7ddfd1a649bc78a12a9406ab
  Source: 
https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/admin-guide/source/compute-flavors.rst
  URL: https://docs.openstack.org/admin-guide/compute-flavors.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1688054/+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 1716903] Re: Failed to live-migrate instance in cell with microversion >= 2.34

[OpenStack Infra]

Reviewed:  https://review.openstack.org/503601
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=062f5b2e876a09119e43c1905f91610cd4e5d015
Submitter: Jenkins
Branch:master

commit 062f5b2e876a09119e43c1905f91610cd4e5d015
Author: Yikun Jiang 
Date:   Wed Sep 13 19:35:49 2017 +0800

Add @targets_cell for live_migrate_instance method in conductor

With microversion < 2.34, the API casts to the migrate_server
method in super conductor which targets the context using the
@targets_cell decorator.

With microversion >= 2.34, the API casts to the live_migrate_instance
method in super conductor which does not use the @targets_cell
decorator, which results in a failure to lookup the instance action
record when recording the start of the action event with the
@wrap_instance_event decorator.

This change simply adds the decorator and provides a test which
was missing for this before. Note that the live migration CI job
didn't catch this regression since it only tests up to microversion
2.26.

Co-Authored-By: Matt Riedemann 

Closes-bug: #1716903
Change-Id: I21d3f3b7589221b7e0a46c332510afc876ca5a79


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

Title:
  Failed to live-migrate instance in cell with microversion >= 2.34

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) pike series:
  In Progress

Bug description:
  Step 1 create instance in cell1
  
+--++++-+-+
  | ID   | Name   | Status | Task State | Power 
State | Networks|
  
+--++++-+-+
  | 84038890-8d70-45e1-8240-2303f4227e11 | yikun1 | ACTIVE | -  | 
Running | public=2001:db8::a, 172.24.4.13 |
  
+--++++-+-+

  Step 2 live migrate instance
  nova live-migration 84038890-8d70-45e1-8240-2303f4227e11

  Step 3
  The instance will stuck in "MIGRATIING" state.
  
+--++---++-+-+
  | ID   | Name   | Status| Task State | 
Power State | Networks|
  
+--++---++-+-+
  | 84038890-8d70-45e1-8240-2303f4227e11 | yikun1 | MIGRATING | migrating  | 
Running | public=2001:db8::a, 172.24.4.13 |
  
+--++---++-+-+

  It seems we need add @targets_cell decorator for **live_migrate_instance** 
methods in conductor:
  https://github.com/openstack/nova/blob/master/nova/conductor/manager.py#L378

  ERROR LOG in super conductor:
  Exception during message handling: InstanceActionNotFound: Action for 
request_id req-5aa03558-ae14-458e-9c35-c3d377c7ce45 on instance 
84038890-8d70-45e1-8240-2303f4227e11 not found
  Traceback (most recent call last):
    File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", 
line 160, in _process_incoming
  res = self.dispatcher.dispatch(message)
    File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
213, in dispatch
  return self._do_dispatch(endpoint, method, ctxt, args)
    File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
183, in _do_dispatch
  result = func(ctxt, **new_args)
    File "/opt/stack/nova/nova/compute/utils.py", line 875, in 
decorated_function
  with EventReporter(context, event_name, instance_uuid):
    File "/opt/stack/nova/nova/compute/utils.py", line 846, in __enter__
  self.context, uuid, self.event_name, want_result=False)
    File 
"/usr/local/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 
184, in wrapper
  result = fn(cls, context, *args, **kwargs)
    File "/opt/stack/nova/nova/objects/instance_action.py", line 169, in 
event_start
  db_event = db.action_event_start(context, values)
    File "/opt/stack/nova/nova/db/api.py", line 1957, in action_event_start
  return IMPL.action_event_start(context, values)
    File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 250, in wrapped
  return f(context, *args, **kwargs)
    File "/opt/stack/nova/nova/db/sqlalchemy/api.py", line 6155, in 
action_event_start
  

[Yahoo-eng-team] [Bug 1718455] [NEW] [pike] Nova host disable and Live Migrate all instances fail.

[Steve Searles]

Public bug reported:

Disabling a host in horizon and live-migrating instances off fail with
the following error if the instances are created with a single boot
command. eg. create 10 cirros instances through the horizon dashboard.
The instances are all KVM and backed by Cinder Volumes.

2017-09-19 19:02:30.588 19741 DEBUG nova.scheduler.filter_scheduler
[req-4268ea83-0657-40cc-961b-f0ae9fb3019e
385c60230b3f49da930dda4d089eda6b 723aa12337a44f818b6d1e1a59f16e49 -
default default] There are 1 hosts available but 10 instances requested
to build. select_destinations /usr/lib/python2.7/dist-
packages/nova/scheduler/filter_scheduler.py:101

Steps to reproduce:

1. Create 10 instances via the horizon dashboard at the same time. 
2. Set a compute host disabled. 
3. Choose the migrate host option and select live-migrate as the method. 
4. The live migration will fail all after passing the scheduler with the error 
above. 

NOTE: Creating 10 separate instances with individual "openstack server
create" commands or running the launch instance 10 times in horizon does
not produce the same result and the scheduler will evacuate the host as
expected.

Nova version on controller:

ii  nova-api   2:16.0.0-0ubuntu1~cloud0 
  all  OpenStack Compute - API frontend
ii  nova-common2:16.0.0-0ubuntu1~cloud0 
  all  OpenStack Compute - common files
ii  nova-conductor 2:16.0.0-0ubuntu1~cloud0 
  all  OpenStack Compute - conductor service
ii  nova-consoleauth   2:16.0.0-0ubuntu1~cloud0 
  all  OpenStack Compute - Console Authenticator
ii  nova-novncproxy2:16.0.0-0ubuntu1~cloud0 
  all  OpenStack Compute - NoVNC proxy
ii  nova-placement-api 2:16.0.0-0ubuntu1~cloud0 
  all  OpenStack Compute - placement API frontend
ii  nova-scheduler 2:16.0.0-0ubuntu1~cloud0 
  all  OpenStack Compute - virtual machine scheduler
ii  python-nova2:16.0.0-0ubuntu1~cloud0 
  all  OpenStack Compute Python libraries
ii  python-novaclient

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

Title:
  [pike] Nova host disable and Live Migrate all instances fail.

Status in OpenStack Compute (nova):
  New

Bug description:
  Disabling a host in horizon and live-migrating instances off fail with
  the following error if the instances are created with a single boot
  command. eg. create 10 cirros instances through the horizon dashboard.
  The instances are all KVM and backed by Cinder Volumes.

  2017-09-19 19:02:30.588 19741 DEBUG nova.scheduler.filter_scheduler
  [req-4268ea83-0657-40cc-961b-f0ae9fb3019e
  385c60230b3f49da930dda4d089eda6b 723aa12337a44f818b6d1e1a59f16e49 -
  default default] There are 1 hosts available but 10 instances
  requested to build. select_destinations /usr/lib/python2.7/dist-
  packages/nova/scheduler/filter_scheduler.py:101

  Steps to reproduce:

  1. Create 10 instances via the horizon dashboard at the same time. 
  2. Set a compute host disabled. 
  3. Choose the migrate host option and select live-migrate as the method. 
  4. The live migration will fail all after passing the scheduler with the 
error above. 

  NOTE: Creating 10 separate instances with individual "openstack server
  create" commands or running the launch instance 10 times in horizon
  does not produce the same result and the scheduler will evacuate the
  host as expected.

  Nova version on controller:

  ii  nova-api   2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - API frontend
  ii  nova-common2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - common files
  ii  nova-conductor 2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - conductor service
  ii  nova-consoleauth   2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - Console Authenticator
  ii  nova-novncproxy2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - NoVNC proxy
  ii  nova-placement-api 2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - placement API frontend
  ii  nova-scheduler 2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - virtual machine scheduler
  ii  python-nova2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute Python libraries
  ii  python-novaclient

To manage notifications 

[Yahoo-eng-team] [Bug 1718439] Re: Apparent lack of locking in conductor logs

[Matthew Booth]

After some brief discussion in #openstack-nova I've moved this to
oslo.log. The issue here appears to be that we spawn multiple separate
conductor processes writing to the same nova-conductor.log file. We
don't want to stop doing this, as it would break people.

It seems that by default python logging uses thread logs rather than
external locks:

  https://docs.python.org/2/library/multiprocessing.html#logging

Suggest the fix might be to explicitly use multiprocessing.get_logger(),
or at least provide an option to do this when we know it's required.

** Project changed: nova => oslo.log

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

Title:
  Apparent lack of locking in conductor logs

Status in oslo.log:
  New

Bug description:
  I'm looking at conductor logs generated by a customer running RH OSP
  10 (Newton). The logs appear to be corrupt in a manner I'd expect to
  see if 2 processes were writing to the same log file simultaneously.
  For example:

  ===
  2017-09-14 15:54:39.689 120626 ERROR nova.servicegroup.drivers.db return 
self.dbapi.connect(*cargs, **cparams)
  2017-09-14 15:54:39.689 120626 ERROR nova.s2017-09-14 15:54:39.690 120562 
ERROR nova.servicegroup.drivers.db [-] Unexpected error while reporting service 
status
  2017-09-14 15:54:39.690 120562 ERROR nova.servicegroup.drivers.db Traceback 
(most recent call last):
  ===

  Notice how a new log starts part way through the second line above.
  This also results in log entries in the wrong sort order:

  ===
  2017-09-14 15:54:39.690 120562 ERROR nova.servicegroup.drivers.db return 
self.dbapi.connect(*cargs, **cparams)
  2017-09-14 15:54:39.690 120562 ERROR nova.servicegroup.drivers.db   File 
"/usr/lib/python2.7/site-packages/pymysql/__init__.py", line 88, in Connect
  2017-09-14 15:54:39.689 120626 ERROR nova.servicegroup.drivers.db return 
Connection(*args, **kwargs)
  2017-09-14 15:54:39.689 120626 ERROR nova.servicegroup.drivers.db   File 
"/usr/lib/python2.7/site-packages/pymysql/connections.py", line 657, in __init__
  ===

  Note how the first 2 lines are after the last 2 by timestamp, as
  presumably the last 2 are a continuation of a previous log entry. This
  confounds merge sorting of log files, which is exceptionally useful.

  We also see truncated lines with no timestamp which aren't a
  continuation of the previous line:

  ===
  2017-09-14 15:54:39.690 120607 ERROR nova.servicegroup.drivers.db 
DBConnectionError: (pymysql.err.OperationalError) (2013, 'Lost connection to 
MySQL server during query') [SQL: u'SELECT 1']
  2017-09-14 15:54:39.690 120607 ERROR nova.servicegroup.drivers.db 
  elf._execute_and_instances(context)
  ===

  I strongly suspect this is because multiple conductors are running in
  separate processes, and are therefore not benefiting from the thread
  safety of python's logging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oslo.log/+bug/1718439/+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 1718295] Re: Unexpected exception in API method: MigrationError_Remote: Migration error: Disk info file is invalid: qemu-img failed to execute - Failed to get shared "write" lock

[James Page]

Distro patch to unblock Ubuntu Pike UCA and Artful (needs conditional
check for general consumption).

** Patch added: "qemu-2.10-compat.patch"
   
https://bugs.launchpad.net/nova/+bug/1718295/+attachment/4953632/+files/qemu-2.10-compat.patch

** Changed in: nova
   Status: Invalid => 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/1718295

Title:
  Live migration fails with qemu-img >= 2.10: "Failed to get shared
  "write" lock\nIs another process using the image?"

Status in devstack:
  Fix Released
Status in OpenStack Compute (nova):
  Triaged
Status in qemu package in Ubuntu:
  Won't Fix

Bug description:
  Looks like this is pretty new:

  http://logs.openstack.org/01/503601/7/check/gate-tempest-dsvm-
  multinode-live-migration-ubuntu-
  xenial/b19b77c/logs/screen-n-api.txt.gz?level=TRACE#_Sep_19_17_47_11_508623

  Sep 19 17:47:11.508623 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: ERROR nova.api.openstack.extensions [None 
req-e31fde7b-317f-4db9-b225-10b6e11b2dff tempest-LiveMigrationTest-1678596498 
tempest-LiveMigrationTest-1678596498] Unexpected exception in API method: 
MigrationError_Remote: Migration error: Disk info file is invalid: qemu-img 
failed to execute on 
/opt/stack/data/nova/instances/806812af-bf9e-4dc1-8e0c-11603ccd9f62/disk : 
Unexpected error while running command.
  Sep 19 17:47:11.508805 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Command: /usr/bin/python2 -m 
oslo_concurrency.prlimit --as=1073741824 --cpu=30 -- env LC_ALL=C LANG=C 
qemu-img info 
/opt/stack/data/nova/instances/806812af-bf9e-4dc1-8e0c-11603ccd9f62/disk
  Sep 19 17:47:11.508946 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Exit code: 1
  Sep 19 17:47:11.509079 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Stdout: u''
  Sep 19 17:47:11.509233 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Stderr: u'qemu-img: Could not open 
\'/opt/stack/data/nova/instances/806812af-bf9e-4dc1-8e0c-11603ccd9f62/disk\': 
Failed to get shared "write" lock\nIs another process using the image?\n'
  Sep 19 17:47:11.509487 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Traceback (most recent call last):
  Sep 19 17:47:11.509649 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 
160, in _process_incoming
  Sep 19 17:47:11.509789 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: res = self.dispatcher.dispatch(message)
  Sep 19 17:47:11.510231 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
222, in dispatch
  Sep 19 17:47:11.510418 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: return self._do_dispatch(endpoint, method, 
ctxt, args)
  Sep 19 17:47:11.510555 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
192, in _do_dispatch
  Sep 19 17:47:11.510687 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: result = func(ctxt, **new_args)
  Sep 19 17:47:11.510829 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/opt/stack/new/nova/nova/exception_wrapper.py", line 76, in wrapped
  Sep 19 17:47:11.510959 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: function_name, call_dict, binary)
  Sep 19 17:47:11.511194 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  Sep 19 17:47:11.511713 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: self.force_reraise()
  Sep 19 17:47:11.511852 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  Sep 19 17:47:11.512037 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: six.reraise(self.type_, self.value, self.tb)
  Sep 19 17:47:11.512687 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/opt/stack/new/nova/nova/exception_wrapper.py", line 67, in wrapped
  Sep 19 17:47:11.516811 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: return f(self, context, *args, **kw)
  Sep 19 17:47:11.516966 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/opt/stack/new/nova/nova/compute/utils.py", line 876, in decorated_function
  Sep 19 17:47:11.517110 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: return function(self, context, 

[Yahoo-eng-team] [Bug 1718439] [NEW] Apparent lack of locking in conductor logs

[Matthew Booth]

Public bug reported:

I'm looking at conductor logs generated by a customer running RH OSP 10
(Newton). The logs appear to be corrupt in a manner I'd expect to see if
2 processes were writing to the same log file simultaneously. For
example:

===
2017-09-14 15:54:39.689 120626 ERROR nova.servicegroup.drivers.db return 
self.dbapi.connect(*cargs, **cparams)
2017-09-14 15:54:39.689 120626 ERROR nova.s2017-09-14 15:54:39.690 120562 ERROR 
nova.servicegroup.drivers.db [-] Unexpected error while reporting service status
2017-09-14 15:54:39.690 120562 ERROR nova.servicegroup.drivers.db Traceback 
(most recent call last):
===

Notice how a new log starts part way through the second line above. This
also results in log entries in the wrong sort order:

===
2017-09-14 15:54:39.690 120562 ERROR nova.servicegroup.drivers.db return 
self.dbapi.connect(*cargs, **cparams)
2017-09-14 15:54:39.690 120562 ERROR nova.servicegroup.drivers.db   File 
"/usr/lib/python2.7/site-packages/pymysql/__init__.py", line 88, in Connect
2017-09-14 15:54:39.689 120626 ERROR nova.servicegroup.drivers.db return 
Connection(*args, **kwargs)
2017-09-14 15:54:39.689 120626 ERROR nova.servicegroup.drivers.db   File 
"/usr/lib/python2.7/site-packages/pymysql/connections.py", line 657, in __init__
===

Note how the first 2 lines are after the last 2 by timestamp, as
presumably the last 2 are a continuation of a previous log entry. This
confounds merge sorting of log files, which is exceptionally useful.

We also see truncated lines with no timestamp which aren't a
continuation of the previous line:

===
2017-09-14 15:54:39.690 120607 ERROR nova.servicegroup.drivers.db 
DBConnectionError: (pymysql.err.OperationalError) (2013, 'Lost connection to 
MySQL server during query') [SQL: u'SELECT 1']
2017-09-14 15:54:39.690 120607 ERROR nova.servicegroup.drivers.db 
elf._execute_and_instances(context)
===

I strongly suspect this is because multiple conductors are running in
separate processes, and are therefore not benefiting from the thread
safety of python's logging.

** Affects: nova
 Importance: Undecided
 Status: New

** Summary changed:

- Apparent lack of locking in logger
+ Apparent lack of locking in conductor logs

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

Title:
  Apparent lack of locking in conductor logs

Status in OpenStack Compute (nova):
  New

Bug description:
  I'm looking at conductor logs generated by a customer running RH OSP
  10 (Newton). The logs appear to be corrupt in a manner I'd expect to
  see if 2 processes were writing to the same log file simultaneously.
  For example:

  ===
  2017-09-14 15:54:39.689 120626 ERROR nova.servicegroup.drivers.db return 
self.dbapi.connect(*cargs, **cparams)
  2017-09-14 15:54:39.689 120626 ERROR nova.s2017-09-14 15:54:39.690 120562 
ERROR nova.servicegroup.drivers.db [-] Unexpected error while reporting service 
status
  2017-09-14 15:54:39.690 120562 ERROR nova.servicegroup.drivers.db Traceback 
(most recent call last):
  ===

  Notice how a new log starts part way through the second line above.
  This also results in log entries in the wrong sort order:

  ===
  2017-09-14 15:54:39.690 120562 ERROR nova.servicegroup.drivers.db return 
self.dbapi.connect(*cargs, **cparams)
  2017-09-14 15:54:39.690 120562 ERROR nova.servicegroup.drivers.db   File 
"/usr/lib/python2.7/site-packages/pymysql/__init__.py", line 88, in Connect
  2017-09-14 15:54:39.689 120626 ERROR nova.servicegroup.drivers.db return 
Connection(*args, **kwargs)
  2017-09-14 15:54:39.689 120626 ERROR nova.servicegroup.drivers.db   File 
"/usr/lib/python2.7/site-packages/pymysql/connections.py", line 657, in __init__
  ===

  Note how the first 2 lines are after the last 2 by timestamp, as
  presumably the last 2 are a continuation of a previous log entry. This
  confounds merge sorting of log files, which is exceptionally useful.

  We also see truncated lines with no timestamp which aren't a
  continuation of the previous line:

  ===
  2017-09-14 15:54:39.690 120607 ERROR nova.servicegroup.drivers.db 
DBConnectionError: (pymysql.err.OperationalError) (2013, 'Lost connection to 
MySQL server during query') [SQL: u'SELECT 1']
  2017-09-14 15:54:39.690 120607 ERROR nova.servicegroup.drivers.db 
  elf._execute_and_instances(context)
  ===

  I strongly suspect this is because multiple conductors are running in
  separate processes, and are therefore not benefiting from the thread
  safety of python's logging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1718439/+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 1718295] Re: Unexpected exception in API method: MigrationError_Remote: Migration error: Disk info file is invalid: qemu-img failed to execute - Failed to get shared "write" lock

[ChristianEhrhardt]

Since it is a wanted behavioral change in upstream qemu setting that task to 
"Won't Fix" unless we come up with a reason to convince qemu to do so.
Once might argue that info should imply force-share or such, but unless we do 
so make clear that no qemu change is expected.
James already mentioned bug 1718133.

@James and Matt - should we dup one of those onto the other?

** Changed in: qemu (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Unexpected exception in API method: MigrationError_Remote: Migration
  error: Disk info file is invalid: qemu-img failed to execute - Failed
  to get shared "write" lock\nIs another process using the image?

Status in devstack:
  Fix Released
Status in OpenStack Compute (nova):
  Invalid
Status in qemu package in Ubuntu:
  Won't Fix

Bug description:
  Looks like this is pretty new:

  http://logs.openstack.org/01/503601/7/check/gate-tempest-dsvm-
  multinode-live-migration-ubuntu-
  xenial/b19b77c/logs/screen-n-api.txt.gz?level=TRACE#_Sep_19_17_47_11_508623

  Sep 19 17:47:11.508623 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: ERROR nova.api.openstack.extensions [None 
req-e31fde7b-317f-4db9-b225-10b6e11b2dff tempest-LiveMigrationTest-1678596498 
tempest-LiveMigrationTest-1678596498] Unexpected exception in API method: 
MigrationError_Remote: Migration error: Disk info file is invalid: qemu-img 
failed to execute on 
/opt/stack/data/nova/instances/806812af-bf9e-4dc1-8e0c-11603ccd9f62/disk : 
Unexpected error while running command.
  Sep 19 17:47:11.508805 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Command: /usr/bin/python2 -m 
oslo_concurrency.prlimit --as=1073741824 --cpu=30 -- env LC_ALL=C LANG=C 
qemu-img info 
/opt/stack/data/nova/instances/806812af-bf9e-4dc1-8e0c-11603ccd9f62/disk
  Sep 19 17:47:11.508946 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Exit code: 1
  Sep 19 17:47:11.509079 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Stdout: u''
  Sep 19 17:47:11.509233 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Stderr: u'qemu-img: Could not open 
\'/opt/stack/data/nova/instances/806812af-bf9e-4dc1-8e0c-11603ccd9f62/disk\': 
Failed to get shared "write" lock\nIs another process using the image?\n'
  Sep 19 17:47:11.509487 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Traceback (most recent call last):
  Sep 19 17:47:11.509649 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 
160, in _process_incoming
  Sep 19 17:47:11.509789 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: res = self.dispatcher.dispatch(message)
  Sep 19 17:47:11.510231 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
222, in dispatch
  Sep 19 17:47:11.510418 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: return self._do_dispatch(endpoint, method, 
ctxt, args)
  Sep 19 17:47:11.510555 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
192, in _do_dispatch
  Sep 19 17:47:11.510687 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: result = func(ctxt, **new_args)
  Sep 19 17:47:11.510829 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/opt/stack/new/nova/nova/exception_wrapper.py", line 76, in wrapped
  Sep 19 17:47:11.510959 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: function_name, call_dict, binary)
  Sep 19 17:47:11.511194 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  Sep 19 17:47:11.511713 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: self.force_reraise()
  Sep 19 17:47:11.511852 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  Sep 19 17:47:11.512037 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: six.reraise(self.type_, self.value, self.tb)
  Sep 19 17:47:11.512687 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/opt/stack/new/nova/nova/exception_wrapper.py", line 67, in wrapped
  Sep 19 17:47:11.516811 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: return f(self, context, *args, **kw)
  Sep 19 17:47:11.516966 ubuntu-xenial-2-node-rax-ord-10997038 

[Yahoo-eng-team] [Bug 1718295] Re: Unexpected exception in API method: MigrationError_Remote: Migration error: Disk info file is invalid: qemu-img failed to execute - Failed to get shared "write" lock

[Sean Dague]

This appears like it might be an issue with the ppa in pike

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

** Project changed: qemu => ubuntu

** Package changed: ubuntu => qemu (Ubuntu)

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

Title:
  Unexpected exception in API method: MigrationError_Remote: Migration
  error: Disk info file is invalid: qemu-img failed to execute - Failed
  to get shared "write" lock\nIs another process using the image?

Status in devstack:
  Fix Released
Status in OpenStack Compute (nova):
  Invalid
Status in qemu package in Ubuntu:
  New

Bug description:
  Looks like this is pretty new:

  http://logs.openstack.org/01/503601/7/check/gate-tempest-dsvm-
  multinode-live-migration-ubuntu-
  xenial/b19b77c/logs/screen-n-api.txt.gz?level=TRACE#_Sep_19_17_47_11_508623

  Sep 19 17:47:11.508623 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: ERROR nova.api.openstack.extensions [None 
req-e31fde7b-317f-4db9-b225-10b6e11b2dff tempest-LiveMigrationTest-1678596498 
tempest-LiveMigrationTest-1678596498] Unexpected exception in API method: 
MigrationError_Remote: Migration error: Disk info file is invalid: qemu-img 
failed to execute on 
/opt/stack/data/nova/instances/806812af-bf9e-4dc1-8e0c-11603ccd9f62/disk : 
Unexpected error while running command.
  Sep 19 17:47:11.508805 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Command: /usr/bin/python2 -m 
oslo_concurrency.prlimit --as=1073741824 --cpu=30 -- env LC_ALL=C LANG=C 
qemu-img info 
/opt/stack/data/nova/instances/806812af-bf9e-4dc1-8e0c-11603ccd9f62/disk
  Sep 19 17:47:11.508946 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Exit code: 1
  Sep 19 17:47:11.509079 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Stdout: u''
  Sep 19 17:47:11.509233 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Stderr: u'qemu-img: Could not open 
\'/opt/stack/data/nova/instances/806812af-bf9e-4dc1-8e0c-11603ccd9f62/disk\': 
Failed to get shared "write" lock\nIs another process using the image?\n'
  Sep 19 17:47:11.509487 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Traceback (most recent call last):
  Sep 19 17:47:11.509649 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 
160, in _process_incoming
  Sep 19 17:47:11.509789 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: res = self.dispatcher.dispatch(message)
  Sep 19 17:47:11.510231 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
222, in dispatch
  Sep 19 17:47:11.510418 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: return self._do_dispatch(endpoint, method, 
ctxt, args)
  Sep 19 17:47:11.510555 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
192, in _do_dispatch
  Sep 19 17:47:11.510687 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: result = func(ctxt, **new_args)
  Sep 19 17:47:11.510829 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/opt/stack/new/nova/nova/exception_wrapper.py", line 76, in wrapped
  Sep 19 17:47:11.510959 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: function_name, call_dict, binary)
  Sep 19 17:47:11.511194 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  Sep 19 17:47:11.511713 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: self.force_reraise()
  Sep 19 17:47:11.511852 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  Sep 19 17:47:11.512037 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: six.reraise(self.type_, self.value, self.tb)
  Sep 19 17:47:11.512687 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/opt/stack/new/nova/nova/exception_wrapper.py", line 67, in wrapped
  Sep 19 17:47:11.516811 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: return f(self, context, *args, **kw)
  Sep 19 17:47:11.516966 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/opt/stack/new/nova/nova/compute/utils.py", line 876, in decorated_function
  Sep 19 17:47:11.517110 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: return function(self, context, 

[Yahoo-eng-team] [Bug 1718409] [NEW] Failed to reschedule instance in cell.

[Yikun Jiang]

Public bug reported:

Description
===
When instance rescheduling happens in cell:
1. Nova compute casts to the build_instances method in cell1 conductor.
2. In cell1 conductor, build_instances method calls the 
scheduler_client.select_destinations method, it calls to scheduler for getting 
scheduled host **without cell0 targeting**, and then, wait scheduler reply.

Nobody could get this scheduler message in cell1 mq, because Scheduler
just only lisening to the api cell(cell0) mq.

flow like this:
compute --> (reschedule) -->  cell1-conductor  -->  (call rpc to CELL1) --> 
timeout

It seems conductor shouldn't call this message to CELL1 mq. Maybe, we
might transfer the mq connection to api cell mq(target cell0) before
call.

After this, the flow as blow:
compute --> (reschedule) -->  cell1-conductor  --> target CELL0 -->  (call rpc 
to CELL0) --> scheduler

BTW, a devstack issue founded.
In order to let scheduler could get instance group from nova_api database in 
code here: 
https://github.com/openstack/nova/blob/5bf1bb47c7e17c26592a699d07c2faa59d98bfb8/nova/conductor/manager.py#L623
It seems we need add 'connection' config in [api_database] section, but now 
devstack doesn't deal with it.
patch is here: https://review.openstack.org/#/c/505607/

Steps to reproduce
==

* 1. Inject some exception in compute code to reproduce a reschedule operation:
raise exception.RescheduledException("reschedule trigger") in here:
https://github.com/openstack/nova/blob/5bf1bb47c7e17c26592a699d07c2faa59d98bfb8/nova/compute/manager.py#L1951
* 2. nova compute cast reschedule request to cell-conductor
* 3. cell-conductor calls to cell mq, nobody could process that.
* 4. Instacne state stuck in BUILD(scheduling)
stack@yikun:~/nova$ nova list
+--+-+++-+--+
| ID   | Name| Status | Task 
State | Power State | Networks |
+--+-+++-+--+
| af3fe405-7155-429d-97a8-a0f9f4c82911 | test_resch_instance | BUILD  | 
scheduling | NOSTATE |  |
+--+-+++-+--+
* 4. Finally, Instance state is ERROR.
stack@yikun:~/nova$ nova list
+--+-+++-+--+
| ID   | Name| Status | Task 
State | Power State | Networks |
+--+-+++-+--+
| af3fe405-7155-429d-97a8-a0f9f4c82911 | test_resch_instance | ERROR  | -   
   | NOSTATE |  |
+--+-+++-+--+


Logs & Configs
==
cell config show as blow:

stack@yikun:~/nova$ cat /etc/nova/nova_cell1.conf 
[database]
connection = mysql+pymysql://root:1@127.0.0.1/nova_cell1?charset=utf8

[api_database]
connection = mysql+pymysql://root:1@127.0.0.1/nova_api?charset=utf8


[conductor]
workers = 2

[DEFAULT]
logging_user_identity_format = %(project_name)s %(user_name)s
transport_url = rabbit://stackrabbit:1@XXX:5672/nova_cell1
debug = True


Log in cell conductor:
2017-09-20 06:18:01.306 21701 ERROR nova.scheduler.utils 
[req-5890b731-4b48-4503-a446-ef3f858eda4a admin admin] [instance: 
af3fe405-7155-429d-97a8-a0f9f4c82911] Error from last host: yikun (node yikun): 
[u'Traceback (most recent call last):\n', u'  File 
"/opt/stack/nova/nova/compute/manager.py", line 1826, in 
_do_build_and_run_instance\nfilter_properties)\n', u'  File 
"/opt/stack/nova/nova/compute/manager.py", line 2057, in 
_build_and_run_instance\ninstance_uuid=instance.uuid, 
reason=six.text_type(e))\n', u'RescheduledException: Build of instance 
af3fe405-7155-429d-97a8-a0f9f4c82911 was re-scheduled: reschedule trigger\n']
2017-09-20 06:18:01.347 21701 DEBUG oslo_db.sqlalchemy.engines 
[req-5890b731-4b48-4503-a446-ef3f858eda4a admin admin] MySQL server mode set to 
STRICT_TRANS_TABLES,STRICT_ALL_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,TRADITIONAL,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
 _check_effective_sql_mode 
/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/engines.py:285
2017-09-20 06:19:01.433 21701 WARNING nova.scheduler.utils 
[req-5890b731-4b48-4503-a446-ef3f858eda4a admin admin] Retrying 
select_destinations after a MessagingTimeout, attempt 1 of 2.: 
MessagingTimeout: Timed out waiting for a reply to message ID 
5dd1a54aa6f446a696f3ab0307572f3f
2017-09-20 06:20:01.441 21701 WARNING nova.scheduler.utils 
[req-5890b731-4b48-4503-a446-ef3f858eda4a admin admin] Retrying 
select_destinations after a MessagingTimeout, attempt 2 of 2.: 
MessagingTimeout: Timed out waiting for a reply to message ID 

[Yahoo-eng-team] [Bug 1718405] [NEW] Creation of Port with subnet and Fixed IP

[lahari]

Public bug reported:

There is no option in horizon to select subnet and Fixed IP while creating ports
According to openstack horizon design, port create form either takes a subnet 
or a Fixed IP

According to the user docs
https://docs.openstack.org/releasenotes/horizon/newton.html

Port creation supports a parameter to specify subnet or fixed IP address.
Which creates confusion when there are two subnets present (one ipv4 subnet and 
other ipv6 subnet) and user tries to provide fixed ip for a port on that network

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

Title:
  Creation of Port with subnet and Fixed IP

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  There is no option in horizon to select subnet and Fixed IP while creating 
ports
  According to openstack horizon design, port create form either takes a subnet 
or a Fixed IP

  According to the user docs
  https://docs.openstack.org/releasenotes/horizon/newton.html

  Port creation supports a parameter to specify subnet or fixed IP address.
  Which creates confusion when there are two subnets present (one ipv4 subnet 
and other ipv6 subnet) and user tries to provide fixed ip for a port on that 
network

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1718405/+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 1718401] [NEW] Networking Option 1: Provider networks in neutron

[Olivier Tosello]

Public bug reported:


- [X] This doc is inaccurate in this way: package named neutron-
linuxbridge-agent is unavailable, whereas neutron-plugin-linuxbridge-
agent is.

---
Release: 11.0.1.dev75 on 2017-09-14 04:10
SHA: 8baed13677c70cf4f1a17c5cc457c3b65bfead1b
Source: 
https://git.openstack.org/cgit/openstack/neutron/tree/doc/source/install/controller-install-option1-ubuntu.rst
URL: 
https://docs.openstack.org/neutron/pike/install/controller-install-option1-ubuntu.html

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: doc

** Description changed:

- 
- This bug tracker is for errors with the documentation, use the following
- as a template and remove or add fields as you see fit. Convert [ ] into
- [x] to check boxes:
  
  - [X] This doc is inaccurate in this way: package named neutron-
  linuxbridge-agent is unavailable, whereas neutron-plugin-linuxbridge-
  agent is.
  
  ---
  Release: 11.0.1.dev75 on 2017-09-14 04:10
  SHA: 8baed13677c70cf4f1a17c5cc457c3b65bfead1b
  Source: 
https://git.openstack.org/cgit/openstack/neutron/tree/doc/source/install/controller-install-option1-ubuntu.rst
  URL: 
https://docs.openstack.org/neutron/pike/install/controller-install-option1-ubuntu.html

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

Title:
  Networking Option 1: Provider networks in neutron

Status in neutron:
  New

Bug description:

  - [X] This doc is inaccurate in this way: package named neutron-
  linuxbridge-agent is unavailable, whereas neutron-plugin-linuxbridge-
  agent is.

  ---
  Release: 11.0.1.dev75 on 2017-09-14 04:10
  SHA: 8baed13677c70cf4f1a17c5cc457c3b65bfead1b
  Source: 
https://git.openstack.org/cgit/openstack/neutron/tree/doc/source/install/controller-install-option1-ubuntu.rst
  URL: 
https://docs.openstack.org/neutron/pike/install/controller-install-option1-ubuntu.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1718401/+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 1308189] Re: Instances in error state should not have Up Time

[Akihiro Motoki]

Marking this as Won't Fix  per comment #8.

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

Title:
  Instances in error state should not have Up Time

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

Bug description:
  When launch instance fails, the instance status is set to Error and
  the Uptime is updated every time the page is loaded even when the
  instance was never up. If the instance current status is Error then
  Uptime should be either "---" or 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1308189/+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 1301534] Re: keep selected panel when switching tenant

[Akihiro Motoki]

As of Queens-1, the current panel is kept when switching projects. I am
not sure when it was implemented. Anyway the requested feature has been
implemented.

** Changed in: horizon
   Status: In Progress => New

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

Title:
  keep selected panel when switching tenant

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  When we switch a tenant in the drop-down menu, a selected panel is not kept 
and overview panel will be displayed.
  It would be nice to keep the selected panel even after switching a tenant.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1301534/+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 1718385] [NEW] neutron-lib validate_subports incorrectly blocks segmentation_id 0

[Tom Stappaerts]

Public bug reported:

When supplying a subport for a trunk with segmenation_id 0 Neutron
reports:

Invalid subport details '{u'segmentation_type': u'vlan', u'port_id':
u'449451c4-f134-4fbc-b405-df9109746e51', u'segmentation_id': 0}':
missing segmentation information. Must specify both segmentation_id and
segmentation_type from (pid=16359) validate_subports
/Ocata/local/lib/python2.7/site-
packages/neutron_lib/api/validators.py:923

This is due to the following lines: 
segmentation_id = subport.get("segmentation_id")
segmentation_type = subport.get("segmentation_type")
if (not segmentation_id or not segmentation_type) and len(subport) > 1:

Can we allow segmentation_id 0 to pass or provide a more suitable error
message?

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

Title:
  neutron-lib validate_subports incorrectly blocks segmentation_id 0

Status in neutron:
  New

Bug description:
  When supplying a subport for a trunk with segmenation_id 0 Neutron
  reports:

  Invalid subport details '{u'segmentation_type': u'vlan', u'port_id':
  u'449451c4-f134-4fbc-b405-df9109746e51', u'segmentation_id': 0}':
  missing segmentation information. Must specify both segmentation_id
  and segmentation_type from (pid=16359) validate_subports
  /Ocata/local/lib/python2.7/site-
  packages/neutron_lib/api/validators.py:923

  This is due to the following lines: 
  segmentation_id = subport.get("segmentation_id")
  segmentation_type = subport.get("segmentation_type")
  if (not segmentation_id or not segmentation_type) and len(subport) > 
1:

  Can we allow segmentation_id 0 to pass or provide a more suitable
  error message?

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1718385/+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 1296419] Re: It is better to warn when trying to delete a pool with members

[Akihiro Motoki]

This is related to LBaaS v1 API which has been dropped, and LBaas
dashboard is also no longer part of horizon. Marking this as Won't Fix.

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

** Changed in: horizon
 Assignee: Verónica Musso (veronica-a-musso) => (unassigned)

** Changed in: horizon
Milestone: next => None

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

Title:
  It is better to warn when trying to delete a pool with members

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

Bug description:
  Regarding the discussion in bug 1242338, there is a suggestion that it is 
better to check if VIP has members is being deleted.
  From UX perspective, it is better to be warned when a user try to delete a 
VIP with members.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1296419/+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 1038531] Re: Current method for toggling actions not compatible with table_actions

[Akihiro Motoki]

Perhaps this still exists in the current horizon but there is no problem for 
years, so I believe there is no need to fix this.
In addition, we are in the migration to Angular-based table.

** Changed in: horizon
 Assignee: Gabriel Hurley (gabriel-hurley) => (unassigned)

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

Title:
  Current method for toggling actions not compatible with table_actions

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

Bug description:
  If you use the current method of toggling actions (as on enable user
  for example), and also include that action in the table actions, the
  name of the action in the table header toggles inappropriately.

  Additionally, setting the toggle in the update method instead of the
  allowed method behaves erratically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1038531/+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 970693] Re: No error displayed on volume attachment fail (need to get errors that happen after initial response)

[Akihiro Motoki]

Horizon side depends on Nova change and there seems no activity in nova
side. We, horizon team, remove horizon from the affected project and
would like to file a bug or a feature request once nova supports some
kind of feature on this.

** No longer affects: horizon

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

Title:
  No error displayed on volume attachment fail (need to get errors that
  happen after initial response)

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  When trying to attach a volume over existing device (i.e we have an
  instance with disk volume, and we try to attach another volume on
  /dev/hda) :

  http://db.tt/OzTWgDJR

  The operation finished without the actual error, just the notification
  above for starting the process. In the table below the status changes
  from 'Attaching' back to 'Available'. without showing a reason for
  attachment failure reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/970693/+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 948644] Re: Service users and service tenant show up in syspanel

[Akihiro Motoki]

Per comment #6, there is nothing to do in horizon side. Marking this as
Invalid.

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

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

Title:
  Service users and service tenant show up in syspanel

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in OpenStack Identity (keystone):
  Invalid

Bug description:
  Now that we have accounts for each service in keystone the user UI
  looks like: http://i.imgur.com/Om5UT.png which seems less than ideal.
  Is there some field we can add that allows the UI to filter out
  service users?

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/948644/+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 1580746] Re: Wrong Hypervisor is being returned QEMU instead of KVM

[Akihiro Motoki]

horizon just displays hypervisor types returned from nova. This does not
affect horizon directly.

** No longer affects: horizon

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

Title:
  Wrong Hypervisor is being returned QEMU instead of KVM

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  nova.conf is configured with virt_type=kvm

  When running hypervisor-show XXX | grep hypervisor_type

  The result is always presented as QEMU

  >>> | hypervisor_type   | QEMU

  I gather that this is also the same is presented in Horizon on the
  Hypervisors tab.

  More information can be found in this thread

  http://lists.openstack.org/pipermail/openstack-
  operators/2016-May/010310.html

  I think this is visible on each and every version of OpenStack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1580746/+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 1718295] Re: Unexpected exception in API method: MigrationError_Remote: Migration error: Disk info file is invalid: qemu-img failed to execute - Failed to get shared "write" lock

[OpenStack Infra]

Reviewed:  https://review.openstack.org/505446
Committed: 
https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=ee22ca8373abd3b5a4c44a9c5c4da39c511195c8
Submitter: Jenkins
Branch:master

commit ee22ca8373abd3b5a4c44a9c5c4da39c511195c8
Author: Matt Riedemann 
Date:   Wed Sep 20 00:29:36 2017 +

Revert "Update to using pike cloud-archive"

This reverts commit a7e9a5d447b3eeacfb52d7ddc94445058a8d6fd1.

The jobs that run live migration tests are failing at about
a rate of 50% since this merged. There are no recent changes
to nova in the last 24 hours that are related to live
migration, and this is failing on the master branch only,
so I suspect the failures are due to new qemu packages
getting pulled in from this change.

Change-Id: Ic8481539c6a0cc7af08a736a625b672979435908
Closes-Bug: #1718295


** Changed in: devstack
   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/1718295

Title:
  Unexpected exception in API method: MigrationError_Remote: Migration
  error: Disk info file is invalid: qemu-img failed to execute - Failed
  to get shared "write" lock\nIs another process using the image?

Status in devstack:
  Fix Released
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Looks like this is pretty new:

  http://logs.openstack.org/01/503601/7/check/gate-tempest-dsvm-
  multinode-live-migration-ubuntu-
  xenial/b19b77c/logs/screen-n-api.txt.gz?level=TRACE#_Sep_19_17_47_11_508623

  Sep 19 17:47:11.508623 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: ERROR nova.api.openstack.extensions [None 
req-e31fde7b-317f-4db9-b225-10b6e11b2dff tempest-LiveMigrationTest-1678596498 
tempest-LiveMigrationTest-1678596498] Unexpected exception in API method: 
MigrationError_Remote: Migration error: Disk info file is invalid: qemu-img 
failed to execute on 
/opt/stack/data/nova/instances/806812af-bf9e-4dc1-8e0c-11603ccd9f62/disk : 
Unexpected error while running command.
  Sep 19 17:47:11.508805 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Command: /usr/bin/python2 -m 
oslo_concurrency.prlimit --as=1073741824 --cpu=30 -- env LC_ALL=C LANG=C 
qemu-img info 
/opt/stack/data/nova/instances/806812af-bf9e-4dc1-8e0c-11603ccd9f62/disk
  Sep 19 17:47:11.508946 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Exit code: 1
  Sep 19 17:47:11.509079 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Stdout: u''
  Sep 19 17:47:11.509233 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Stderr: u'qemu-img: Could not open 
\'/opt/stack/data/nova/instances/806812af-bf9e-4dc1-8e0c-11603ccd9f62/disk\': 
Failed to get shared "write" lock\nIs another process using the image?\n'
  Sep 19 17:47:11.509487 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: Traceback (most recent call last):
  Sep 19 17:47:11.509649 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 
160, in _process_incoming
  Sep 19 17:47:11.509789 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: res = self.dispatcher.dispatch(message)
  Sep 19 17:47:11.510231 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
222, in dispatch
  Sep 19 17:47:11.510418 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: return self._do_dispatch(endpoint, method, 
ctxt, args)
  Sep 19 17:47:11.510555 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
192, in _do_dispatch
  Sep 19 17:47:11.510687 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: result = func(ctxt, **new_args)
  Sep 19 17:47:11.510829 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/opt/stack/new/nova/nova/exception_wrapper.py", line 76, in wrapped
  Sep 19 17:47:11.510959 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: function_name, call_dict, binary)
  Sep 19 17:47:11.511194 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  Sep 19 17:47:11.511713 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]: self.force_reraise()
  Sep 19 17:47:11.511852 ubuntu-xenial-2-node-rax-ord-10997038 
devstack@n-api.service[28339]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  Sep 19 17:47:11.512037 

[Yahoo-eng-team] [Bug 1718369] [NEW] DBDeadlock occurs when delete router_gateway

[Zachary Ma]

Public bug reported:

I have 3 controllers and each controllers are running neutron-server.
When I delete router_gateway, some of the controllers occasionally crash
with DBDeadlock exceptions:

69597:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager 
[req-31af8910-b348-49c4-9082-8647f1ef94ca 0c806b3af06b4025ad180a6d6213d02c 
9d120e49c3e2484b827597bdde57f850 - default default] Error during notification 
for 
neutron.services.l3_router.l3_router_plugin.L3RouterPlugin._delete_dvr_internal_ports--9223372036852560901
 router_gateway, after_delete: DBDeadlock: (pymysql.err.InternalError) (1213, 
u'Deadlock found when trying to get lock; try restarting transaction') [SQL: 
u'DELETE FROM portsecuritybindings WHERE portsecuritybindings.port_id = 
%(port_id)s'] [parameters: {'port_id': u'f7dea1fa-5436-4a43-b0ec-0bef99371375'}]
69598:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager 
Traceback (most recent call last):
69599:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron_lib/callbacks/manager.py", line 171, 
in _notify_loop
69600:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager 
callback(resource, event, trigger, **kwargs)
69601:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/db/l3_dvr_db.py", line 272, in 
_delete_dvr_internal_ports
69602:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager 
context.elevated(), None, network_id)
69603:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/db/l3_dvr_db.py", line 288, in 
delete_floatingip_agent_gateway_port
69604:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager 
self._core_plugin.ipam.delete_port(context, p['id'])
69605:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/db/ipam_pluggable_backend.py", line 
429, in delete_port
69606:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager 
port['fixed_ips'])
69607:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/db/ipam_pluggable_backend.py", line 
95, in _ipam_deallocate_ips
69608:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager 
"external system for %s", addresses)
69609:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__
69610:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager 
self.force_reraise()
69611:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
69612:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager 
six.reraise(self.type_, self.value, self.tb)
69613:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/db/ipam_pluggable_backend.py", line 
71, in _ipam_deallocate_ips
69614:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager 
ipam_subnet = ipam_driver.get_subnet(ip['subnet_id'])
69615:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/ipam/drivers/neutrondb_ipam/driver.py",
 line 267, in get_subnet
69616:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager 
return NeutronDbSubnet.load(subnet_id, self._context)
69617:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/ipam/drivers/neutrondb_ipam/driver.py",
 line 91, in load
69618:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager ctx, 
neutron_subnet_id)
69619:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/ipam/drivers/neutrondb_ipam/db_api.py",
 line 30, in load_by_neutron_subnet_id
69620:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager 
context, neutron_subnet_id=neutron_subnet_id)
69621:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/objects/base.py", line 463, in 
get_objects
69622:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager with 
context.session.begin(subtransactions=True):
69623:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager   File 
"/usr/lib64/python2.7/site-packages/sqlalchemy/orm/session.py", line 824, in 
begin
69624:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager 
self, nested=nested)
69625:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager   File 
"/usr/lib64/python2.7/site-packages/sqlalchemy/orm/session.py", line 218, in 
__init__
69626:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager   

[Yahoo-eng-team] [Bug 1706061] Re: Missing conversion for firewall-rule in neutron-lib

[Yushiro FURUKAWA]

https://review.openstack.org/#/c/486133/  has been merged.

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

Title:
  Missing conversion for firewall-rule in neutron-lib

Status in neutron:
  Fix Released

Bug description:
  Current neutron-lib(1.9.1) is missing conversion source/destination
  port for firewall rule.  https://review.openstack.org/#/c/486133/ is
  the fix to insert conversion 'convert_to_string' for firewall rule.
  However, this fix is not included in neutron-lib 1.9.1.

  As a result, firewall rule cannot specify source/destination port as
  an integer value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1706061/+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 1715646] Re: Compute host for ironic is not mapped to a cell if no ironic node is created

[OpenStack Infra]

Reviewed:  https://review.openstack.org/502080
Committed: 
https://git.openstack.org/cgit/openstack/ironic/commit/?id=2427ffca8bd0e2ab5127020ae6ffea9decfdc915
Submitter: Jenkins
Branch:master

commit 2427ffca8bd0e2ab5127020ae6ffea9decfdc915
Author: Dmitry Tantsur 
Date:   Fri Sep 8 16:44:24 2017 +0200

Document setting discover_hosts_in_cells_interval in nova.conf

By default, starting with Ocata, an operator needs to run a nova-manage 
command
after each node is enrolled to make sure it's correctly mapped to a cell.
This is not something we can ask in all cases (especially if Ironic UI is 
used),
so let us document running a periodic task for it instead.

Change-Id: I0c7bf29b0e27bef7205880ebc164d3a82e7b0be8
Closes-Bug: #1715646


** Changed in: ironic
   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/1715646

Title:
  Compute host for ironic is not mapped to a cell if no ironic node is
  created

Status in Ironic:
  Fix Released
Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  'nova-manage cell_v2 discover_hosts' command discovers a host based on 
compute node records.
  When virt ironic driver is used, a compute node record is created after a 
node is created in ironic. If a nova compute host is set up before a node is 
created in ironic, discover_hosts command cannot discover the host. The command 
should be run after a node is created in ironic.

  I'm not sure if this is a bug.
  If not, it would be better to add a note to ironic install guide.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ironic/+bug/1715646/+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 1718356] [NEW] Include default config files in python wheel

[Jesse Pretorius]

Public bug reported:

The projects which deploy OpenStack from source or using python wheels
currently have to either carry templates for api-paste, policy and
rootwrap files or need to source them from git during deployment. This
results in some rather complex mechanisms which could be radically
simplified by simply ensuring that all the same files are included in
the built wheel.

A precedence for this has already been set in neutron [1] and glance [2]
through the use of the data_files option in the files section of
setup.cfg.

[1] 
https://github.com/openstack/neutron/blob/d3c393ff6b5fbd0bdaabc8ba678d755ebfba08f7/setup.cfg#L24-L39
[2] 
https://github.com/openstack/glance/blob/02cd5cba70a8465a951cb813a573d390887174b7/setup.cfg#L20-L21

This bug will be used for a cross-project implementation of patches to
normalise the implementation across the OpenStack projects. Hopefully
the result will be a consistent implementation across all the major
projects.

** Affects: glance
 Importance: Undecided
 Assignee: Jesse Pretorius (jesse-pretorius)
 Status: New

** Affects: neutron
 Importance: Undecided
 Assignee: Jesse Pretorius (jesse-pretorius)
 Status: New

** Affects: nova
 Importance: Undecided
 Assignee: Jesse Pretorius (jesse-pretorius)
 Status: New

** Affects: openstack-ansible
 Importance: Undecided
 Assignee: Jesse Pretorius (jesse-pretorius)
 Status: New

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

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

** Changed in: neutron
 Assignee: (unassigned) => Jesse Pretorius (jesse-pretorius)

** Changed in: glance
 Assignee: (unassigned) => Jesse Pretorius (jesse-pretorius)

** Changed in: openstack-ansible
 Assignee: (unassigned) => Jesse Pretorius (jesse-pretorius)

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

** Changed in: nova
 Assignee: (unassigned) => Jesse Pretorius (jesse-pretorius)

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

Title:
  Include default config files in python wheel

Status in Glance:
  New
Status in neutron:
  New
Status in OpenStack Compute (nova):
  New
Status in openstack-ansible:
  New

Bug description:
  The projects which deploy OpenStack from source or using python wheels
  currently have to either carry templates for api-paste, policy and
  rootwrap files or need to source them from git during deployment. This
  results in some rather complex mechanisms which could be radically
  simplified by simply ensuring that all the same files are included in
  the built wheel.

  A precedence for this has already been set in neutron [1] and glance
  [2] through the use of the data_files option in the files section of
  setup.cfg.

  [1] 
https://github.com/openstack/neutron/blob/d3c393ff6b5fbd0bdaabc8ba678d755ebfba08f7/setup.cfg#L24-L39
  [2] 
https://github.com/openstack/glance/blob/02cd5cba70a8465a951cb813a573d390887174b7/setup.cfg#L20-L21

  This bug will be used for a cross-project implementation of patches to
  normalise the implementation across the OpenStack projects. Hopefully
  the result will be a consistent implementation across all the major
  projects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1718356/+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