[Yahoo-eng-team] [Bug 1593573] Re: flavor image listing failed while calling Nova API with token from http://[host-ip]/identity/v3

2017-09-01 Thread Launchpad Bug Tracker 
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

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

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

Title:
  flavor image listing failed while calling Nova API with token from
  http://[host-ip]/identity/v3

Status in OpenStack Compute (nova):
  Expired

Bug description:
  With OpenStack Mitaka 14.0 release:

  Running list server, images and flavor with http://[host-
  ip]/identity/v2.0 token has no issue but when switching to http
  ://[host-ip]/identity/v3, error is returned for image listing and
  flavor listing but server listing is working fine.

  I did:

  (A) Obtaining a token from http://[host-ip]/identity/v2.0, token
  [203f7cfba41645cabddf06ea644dcc66]

  (B) Obtaining a token from http://[host-ip]/identity/v3, token
  [9cb08a8f126844318e7052ab7f62f14f]

  And by using the tokens, I did:

  a) With token from v2.0 [203f7cfba41645cabddf06ea644dcc66]

  - Get server listing

  curl --request GET 'http://[host-ip]:8774/v2.1/servers' --header 'X
  -Auth-Token:203f7cfba41645cabddf06ea644dcc66'

  Outcome: Get server listing with no error. Result in JSON is returned.

  -  Get image listing

  curl --request GET 'http://[host-ip]:8774/v2.1/images' --header 'X
  -Auth-Token:203f7cfba41645cabddf06ea644dcc66'

  Outcome: Get image listing with no error. Result in JSON is returned.

  - Get flavor listing

  curl --request GET 'http://[host-ip]:8774/v2.1/flavors' --header 'X
  -Auth-Token:203f7cfba41645cabddf06ea644dcc66'

  Outcome: Get flavor listing with no error. Result in JSON is returned.

  All above are working perfectly with v.20 token.

  b) With token from v3 [9cb08a8f126844318e7052ab7f62f14f]

  - Get server listing
  curl --request GET 'http://[host-ip]:8774/v2.1/servers' --header 
'X-Auth-Token:9cb08a8f126844318e7052ab7f62f14f'

  Outcome: Get server listing with no error. Result in JSON is returned.

  -  Get image listing

  curl --request GET 'http://[host-ip]:8774/v2.1/images' --header 'X
  -Auth-Token:9cb08a8f126844318e7052ab7f62f14f'

  {
   "computeFault": {
    "message": "Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.\n",
    "code": 500
   }
  }

  Outcome: Error

  - Get flavor listing

  curl --request GET 'http://[host-ip]:8774/v2.1/flavors' --header 'X
  -Auth-Token:9cb08a8f126844318e7052ab7f62f14f'

  {
   "computeFault": {
    "message": "Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.\n",
    "code": 500
   }
  }

  Outcome: Error

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1593573/+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 1697588] Re: update tempest plugin after removal of cred manager aliases

2017-09-01 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/482091
Committed: 
https://git.openstack.org/cgit/openstack/tap-as-a-service/commit/?id=c7c497cc3a07dc69187efb8d3459c3a65c08c010
Submitter: Jenkins
Branch:master

commit c7c497cc3a07dc69187efb8d3459c3a65c08c010
Author: bhavani.cr 
Date:   Mon Jul 10 16:15:35 2017 +0530

Replace the usage of 'admin_manager' with 'os_admin'

In tempest, alias 'admin_manager' has been moved to 'os_admin'
'alt_manager' to 'os_alt' and 'manager' to 'os_primary' in
version Pike, and it will be removed in version Queens[1].

[1]I5f7164f7a7ec5d4380ca22885000caa0183a0bf7

Change-Id: I162d5e4a7a9aa65d7abefbe74c1571e3106edcaf
Closes-bug: 1697588


** Changed in: tap-as-a-service
   Status: New => Fix Released

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

Title:
  update tempest plugin after removal of cred manager aliases

Status in networking-midonet:
  Fix Released
Status in networking-sfc:
  Fix Released
Status in neutron:
  Fix Released
Status in tap-as-a-service:
  Fix Released

Bug description:
  Update after tempest change I5f7164f7a7ec5d4380ca22885000caa0183a0bf7

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-midonet/+bug/1697588/+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 1702854] Re: Next steps in Installation Guide - Customize the dashboard link does not work

2017-09-01 Thread Petr Kovar 
Addressed by: https://review.openstack.org/#/c/500074/

** Project changed: openstack-manuals => horizon

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

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

Title:
  Next steps in Installation Guide -  Customize the dashboard link does
  not work

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:

  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:  Customize the dashboard. link does 
not work. 
(https://docs.openstack.org/admin-guide/dashboard-customize-configure.html)
  - [ ] This is a doc addition request.
  - [ ] I have a fix to the document that I can paste below including example: 
input and output. 

  If you have a troubleshooting or support issue, use the following
  resources:

   - Ask OpenStack: http://ask.openstack.org
   - The mailing list: http://lists.openstack.org
   - IRC: 'openstack' channel on Freenode

  ---
  Release: 0.1 on 2017-06-29 19:44
  SHA: 3d8cb4ddcef823e5edab04e30ca1a6678c6a8ecd
  Source: 
http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/horizon-next-steps.rst
  URL: 
https://docs.openstack.org/newton/install-guide-ubuntu/horizon-next-steps.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1702854/+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 1702855] Re: Next steps in Installation Guide - "https://docs.openstack.org/admin-guide/dashboard-sessions.html" does not work

2017-09-01 Thread Petr Kovar 
Addressed by: https://review.openstack.org/#/c/500074/

** Project changed: openstack-manuals => horizon

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

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

Title:
  Next steps in Installation Guide - "https://docs.openstack.org/admin-
  guide/dashboard-sessions.html" does not work

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:

  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: 
"https://docs.openstack.org/admin-guide/dashboard-sessions.html; link does not 
work.
  - [ ] This is a doc addition request.
  - [ ] I have a fix to the document that I can paste below including example: 
input and output. 

  If you have a troubleshooting or support issue, use the following
  resources:

   - Ask OpenStack: http://ask.openstack.org
   - The mailing list: http://lists.openstack.org
   - IRC: 'openstack' channel on Freenode

  ---
  Release: 0.1 on 2017-06-29 19:44
  SHA: 3d8cb4ddcef823e5edab04e30ca1a6678c6a8ecd
  Source: 
http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/horizon-next-steps.rst
  URL: 
https://docs.openstack.org/newton/install-guide-ubuntu/horizon-next-steps.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1702855/+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 1702855] [NEW] Next steps in Installation Guide - "https://docs.openstack.org/admin-guide/dashboard-sessions.html" does not work

2017-09-01 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:


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: 
"https://docs.openstack.org/admin-guide/dashboard-sessions.html; link does not 
work.
- [ ] This is a doc addition request.
- [ ] I have a fix to the document that I can paste below including example: 
input and output. 

If you have a troubleshooting or support issue, use the following
resources:

 - Ask OpenStack: http://ask.openstack.org
 - The mailing list: http://lists.openstack.org
 - IRC: 'openstack' channel on Freenode

---
Release: 0.1 on 2017-06-29 19:44
SHA: 3d8cb4ddcef823e5edab04e30ca1a6678c6a8ecd
Source: 
http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/horizon-next-steps.rst
URL: 
https://docs.openstack.org/newton/install-guide-ubuntu/horizon-next-steps.html

** Affects: horizon
 Importance: High
 Assignee: Petr Kovar (pmkovar)
 Status: Confirmed


** Tags: install-guide
-- 
Next steps in Installation Guide - 
"https://docs.openstack.org/admin-guide/dashboard-sessions.html; does not work
https://bugs.launchpad.net/bugs/1702855
You received this bug notification because you are a member of Yahoo! 
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).

-- 
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 1702854] [NEW] Next steps in Installation Guide - Customize the dashboard link does not work

2017-09-01 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:


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:  Customize the dashboard. link does 
not work. 
(https://docs.openstack.org/admin-guide/dashboard-customize-configure.html)
- [ ] This is a doc addition request.
- [ ] I have a fix to the document that I can paste below including example: 
input and output. 

If you have a troubleshooting or support issue, use the following
resources:

 - Ask OpenStack: http://ask.openstack.org
 - The mailing list: http://lists.openstack.org
 - IRC: 'openstack' channel on Freenode

---
Release: 0.1 on 2017-06-29 19:44
SHA: 3d8cb4ddcef823e5edab04e30ca1a6678c6a8ecd
Source: 
http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/horizon-next-steps.rst
URL: 
https://docs.openstack.org/newton/install-guide-ubuntu/horizon-next-steps.html

** Affects: horizon
 Importance: High
 Assignee: Petr Kovar (pmkovar)
 Status: Confirmed


** Tags: install-guide
-- 
Next steps in Installation Guide -  Customize the dashboard link does not work
https://bugs.launchpad.net/bugs/1702854
You received this bug notification because you are a member of Yahoo! 
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).

-- 
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 1670738] Re: man page needed for "nova-manage db online_data_migrations"

2017-09-01 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/493442
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=9e1e1a52de48877fd4eb9bcd783e7c187e09a2ab
Submitter: Jenkins
Branch:master

commit 9e1e1a52de48877fd4eb9bcd783e7c187e09a2ab
Author: Hesam Chobanlou 
Date:   Mon Aug 14 02:09:30 2017 -0400

add online_data_migrations to nova docs

adding cli documentation for online_data_migrations to clarify
when the command is complete.

Closes-Bug: #1670738

Change-Id: If50bd044091250611a7d3d67438d732279510d5b


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

Title:
  man page needed for "nova-manage db online_data_migrations"

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  This came up in the openstack-operators mailing list:

  http://lists.openstack.org/pipermail/openstack-
  operators/2017-March/012864.html

  There is confusion around the online_data_migrations CLI for knowing
  when it's complete. There are sort of two answers:

  1. There is no summary table output.

  2. The command exits with 0 meaning there were no migrations
  performed. This is probably the best case to follow when
  checking/scripting for this.

  We need a man page explaining this in the nova docs:

  https://github.com/openstack/nova/blob/master/doc/source/man/nova-
  manage.rst

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1670738/+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 1704458] Re: The use_ipv6 flag not only influences nova networking

2017-09-01 Thread Stephen Finucane 
OK, so this really looks like it was fixed in [1]. We don't always
expose IPv6 [2], but we seem to do so if the instance's 'network_info'
object contains IPv6 subnets [3].

I'm not 100% on this, but I'm sure enough to mark this as invalid.
Please reopen if I've missed something.

[1] https://review.openstack.org/#/c/430910/6/nova/virt/netutils.py
[2] 
https://github.com/openstack/nova/blob/16.0.0/nova/virt/netutils.py#L162-L164
[3] https://github.com/openstack/nova/blob/16.0.0/nova/virt/netutils.py#L131

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

Title:
  The use_ipv6 flag not only influences nova networking

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Description
  ===

  The use_ipv6 flag is marked as deprecated in the Ocata release 
(https://docs.openstack.org/ocata/config-reference/compute/config-options.html 
) because it Nova networking is planed to be removed. However this flag also 
influences the data generated in the network_data.json. If the flag is set to 
false the IPv6 networks are missing from the JSON. If the value is true the 
JSON contains the IPv6 interfaces. Further details can be found here:
  https://bugs.launchpad.net/nova/+bug/1514082

  If default value (false) is also inconsistent with the data returned
  by Neutron through the meta data service.
  http://169.254.169.254/openstack/latest/network_data.json

  Steps to reproduce
  ==

  1. Boot a server with 2 interfaces one IPv4 and one IPv6
  2. mount /dev/sr0 /mnt
  3. The /mnt/openstack/latest/network-data.json does not contain IPv6 addresses

  0. Change the use_ipv6 flag to true on all compute nodes and restart the 
compute service
  1. Boot a server with 2 interfaces one IPv4 and one IPv6
  2. mount /dev/sr0 /mnt
  3. The /mnt/openstack/latest/network-data.json does not contain IPv6 addresses

  Expected result
  ===

  Option 0: Nova should donwload the network-data.json from the Neutron
  metadata service and expose it as is on the config drive.

  Option 1: Change the description of the use_ipv6 to: "Configures if the IPv6 
addresses should be included in the config drive. (Remove deprecation warning)
  Change the default value to true to be in sync with neutron behaviour.

  Option 2: The generation of the network-data.json on config drive
  should always include the IPv6 addresses.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1704458/+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 1705125] Re: ArgumentError: Could not parse rfc1738 URL from string 'nova'

2017-09-01 Thread Stephen Finucane 
Cool. Thanks Jessica. Marking as invalid.

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

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

Title:
  ArgumentError: Could not parse rfc1738 URL from string 'nova'

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  openstack newton - Fresh install
  centos 7
  openstack-nova 14.0.7-1.el7 
  LVM storage
  libvirt, qemu
  Currently using keystone v2.0 by request cannot move to v3 yet.

  Cannot refresh page with out an error "Cannot retrieve instances"
  which I would expect with nova being broken. Can click the launch
  instance button but nothing happens horizon dashboard hangs.

  I have attempted to find the 'nova' in any config file and cannot find it.
  I have reinstalled all my nova packages
  I have tried to see if nova is hard coded anywhere in python but it seems 
only in test

  If something is misconfigured I'd like to know I just can't seem to
  see it.

  nova-api.log

  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions 
[req-4a06e750-b00c-4d1f-8d1d-6bcd03a85cc9 9d417694512546ce86db98f632b3990a 
ad008271d8e345468c55fdaca4f1e6bc - default default] Unexpected exception in API 
method
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions Traceback 
(most recent call last):
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 338, 
in wrapped
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/compute/servers.py", line 
207, in detail
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions 
servers = self._get_servers(req, is_detail=True)
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/compute/servers.py", line 
347, in _get_servers
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions 
sort_keys=sort_keys, sort_dirs=sort_dirs)
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/compute/api.py", line 2330, in get_all
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions 
sort_dirs=sort_dirs)
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/compute/api.py", line 2407, in 
_get_instances_by_filters
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions 
expected_attrs=fields, sort_keys=sort_keys, sort_dirs=sort_dirs)
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/oslo_versionedobjects/base.py", line 184, in 
wrapper
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions result 
= fn(cls, context, *args, **kwargs)
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/objects/instance.py", line 1198, in 
get_by_filters
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions 
use_slave=use_slave, sort_keys=sort_keys, sort_dirs=sort_dirs)
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 225, in 
wrapper
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/objects/instance.py", line 1182, in 
_get_by_filters_impl
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions 
sort_keys=sort_keys, sort_dirs=sort_dirs)
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/db/api.py", line 763, in 
instance_get_all_by_filters_sort
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions 
sort_dirs=sort_dirs)
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 169, in 
wrapper
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 269, in 
wrapped
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions with 
ctxt_mgr.reader.allow_async.using(context):
  2017-07-18 16:25:57.319 126744 ERROR nova.api.openstack.extensions   File 
"/usr/lib64/python2.7/contextlib.py", line 17, in __enter__
  2017-07-18 16:25:57.319 126744 ERROR

[Yahoo-eng-team] [Bug 1693689] Re: Could not determine host ip address

2017-09-01 Thread Thomas Morin 
Aaarg, hitting the same issue I digged logs and devstack gate script
shell, came to the conclusion that neutron fullstack jobs should have
solved this issue (since n8g-bagpipe fullstack gate hook was stolen from
neutron's), ran a git blame on neutron's gate_hook.sh and ended up here,
and found a mention on n8g-bagpipe failure in the bug description.

An "affected project: networking-bagpipe" would have spared me quite some 
time... 
I just added n8g-bapipe and group-based-policy as affected projects.

But, well at least the solution is ready!

** Also affects: networking-bagpipe
   Importance: Undecided
   Status: New

** Also affects: group-based-policy
   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/1693689

Title:
  Could not determine host ip address

Status in Group Based Policy:
  New
Status in BaGPipe:
  New
Status in neutron:
  Fix Released

Bug description:
  it seems affecting the following jobs.

  gate-neutron-dsvm-fullstack-ubuntu-xenial
  gate-neutron-dsvm-functional-ubuntu-xenial-nv
  gate-neutron-dsvm-functional-ubuntu-xenial
  gate-networking-bagpipe-dsvm-fullstack-ubuntu-xenial-nv

  to me it seems happening only on citycloud.

  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%20%5C%22Could%20not%20determine%20host%20ip%20address.%5C%22

  eg. http://logs.openstack.org/75/437775/10/check/gate-neutron-dsvm-
  functional-ubuntu-xenial/22dbc16/

  2017-05-26 03:22:08.617415 | +++ functions-common:address_in_net:2286 :   
network=10.0.0.0
  2017-05-26 03:22:08.618918 | +++ functions-common:address_in_net:2287 :   
local subnet
  2017-05-26 03:22:08.620812 | + functions-common:address_in_net:2288 : 
  cidr2netmask 22
  2017-05-26 03:22:08.621827 | + functions-common:cidr2netmask:2304   : 
  local 'maskpat=255 255 255 255'
  2017-05-26 03:22:08.622784 | + functions-common:cidr2netmask:2305   : 
  local 'maskdgt=254 252 248 240 224 192 128'
  2017-05-26 03:22:08.623706 | + functions-common:cidr2netmask:2306   : 
  set -- 255 255 252
  2017-05-26 03:22:08.624637 | + functions-common:cidr2netmask:2307   : 
  echo 255.255.252.0
  2017-05-26 03:22:08.626091 |  functions-common:address_in_net:2288 :  
 maskip 10.0.1.215 255.255.252.0
  2017-05-26 03:22:08.627654 |  functions-common:maskip:2361 :  
 local ip=10.0.1.215
  2017-05-26 03:22:08.628849 |  functions-common:maskip:2362 :  
 local mask=255.255.252.0
  2017-05-26 03:22:08.629910 |  functions-common:maskip:2363 :  
 local l=10.0.1
  2017-05-26 03:22:08.631051 |  functions-common:maskip:2363 :  
 local r=0.1.215
  2017-05-26 03:22:08.632372 |  functions-common:maskip:2363 :  
 local n=255.255.252
  2017-05-26 03:22:08.633835 |  functions-common:maskip:2363 :  
 local m=255.252.0
  2017-05-26 03:22:08.634883 |  functions-common:maskip:2364 :  
 local subnet
  2017-05-26 03:22:08.636020 |  functions-common:maskip:2365 :  
 subnet=10.0.0.0
  2017-05-26 03:22:08.637027 |  functions-common:maskip:2366 :  
 echo 10.0.0.0
  2017-05-26 03:22:08.639064 | +++ functions-common:address_in_net:2288 :   
subnet=10.0.0.0
  2017-05-26 03:22:08.640696 | +++ functions-common:address_in_net:2289 :   
[[ 10.0.0.0 == 10.0.0.0 ]]
  2017-05-26 03:22:08.642357 | +++ functions-common:get_default_host_ip:684 :   
echo
  2017-05-26 03:22:08.643625 | ++ stackrc:source:815   :   
HOST_IP=
  2017-05-26 03:22:08.644779 | ++ stackrc:source:816   :   
'[' '' == '' ']'
  2017-05-26 03:22:08.645754 | ++ stackrc:source:817   :   
die 817 'Could not determine host ip address.  See local.conf for suggestions 
on setting HOST_IP.'
  2017-05-26 03:22:08.646787 | ++ functions-common:die:186 :   
local exitcode=0
  2017-05-26 03:22:08.647956 | ++ functions-common:die:187 :   
set +o xtrace
  2017-05-26 03:22:08.648111 | [Call Trace]
  2017-05-26 03:22:08.648178 | ./stack.sh:191:source
  2017-05-26 03:22:08.648217 | /opt/stack/new/devstack/stackrc:817:die
  2017-05-26 03:22:08.650467 | [ERROR] /opt/stack/new/devstack/stackrc:817 
Could not determine host ip address. See local.conf for suggestions on setting 
HOST_IP.
  2017-05-26 03:22:09.655121 | + 
/opt/stack/new/neutron/neutron/tests/contrib/gate_hook.sh:main:1 :   rm -rf 
/tmp/tmp.nAvEK2rZvR
  2017-05-26 03:22:09.657520 | ERROR: the main setup script run by this job 
failed - exit code: 1
  2017-05-26 03:22:09.657561 | please look at the relevant log files to 
determine the root cause
  2017-05-26 03:22:09.657575 | Running devstack worlddump.py
  2017-05-26 03:22:09.866930 | Cleaning up host
  2017-05-26 03:22:09.867026 | ... this takes 3 - 4 minutes

[Yahoo-eng-team] [Bug 1714528] [NEW] l2pop config opts not documented

2017-09-01 Thread Boden R 
Public bug reported:

In ocata we had config reference for l2pop config opts [1].
However these seem to be missing in pike [2] and are referenced in the 
config-ml2.rst doc.


[1] 
https://docs.openstack.org/ocata/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-l2-population-mechanism-configuration-options
[2] https://docs.openstack.org/neutron/pike/configuration/ml2-conf.html

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: doc

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

Title:
  l2pop config opts not documented

Status in neutron:
  New

Bug description:
  In ocata we had config reference for l2pop config opts [1].
  However these seem to be missing in pike [2] and are referenced in the 
config-ml2.rst doc.

  
  [1] 
https://docs.openstack.org/ocata/config-reference/networking/networking_options_reference.html#modular-layer-2-ml2-l2-population-mechanism-configuration-options
  [2] https://docs.openstack.org/neutron/pike/configuration/ml2-conf.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1714528/+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 1713974] Re: payload samples are not hidden in the notification devref by default

2017-09-01 Thread Matt Riedemann 
** Also affects: nova/pike
   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/1713974

Title:
  payload samples are not hidden in the notification devref by default

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

Bug description:
  With the new doc template the showing and hiding of the notification
  samples in the notification dev-ref[1] isn't working and therefore
  every sample shown by default that makes the document hard to read.

  Most probably the html structure has been changed in a way that breaks
  the javascript doing the hiding.

  [1]
  https://docs.openstack.org/nova/latest/reference/notifications.html
  #existing-versioned-notifications

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1713974/+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 1703413] Re: Allow to set UDP ports for VXLAN in Linuxbridge agent

2017-09-01 Thread Boden R 
After scanning our docs, I'm not seeing any updates that need to be made
here.

We touch on linuxbridge agent config in [1], but without much depth and
just refer to the config reference. Given the config options added as
part of this feature are well documented, IMO the config reference is
sufficient rather than adding new docs to address this.

However we need to fix [2], so the latest config options show up in our
public docs.


[1] https://docs.openstack.org/neutron/latest/admin/config-ml2.html#l2-agent
[2] https://bugs.launchpad.net/neutron/+bug/1714516

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

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

Title:
  Allow to set UDP ports for VXLAN in Linuxbridge agent

Status in neutron:
  Invalid

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

  commit d7c4428525dac6cbde005f51bcd44b12ebc3bc0a
  Author: Gyorgy Szombathelyi 
  Date:   Mon May 29 16:21:15 2017 +0200

  Allow to set UDP ports for VXLAN in Linuxbridge agent
  
  Introduce vxlan.{udp_srcport_min, udp_srcport_max and udp_dstport}
  for setting the port range used for VXLAN communication.
  
  Change-Id: I9788090eee7aee9b533ac1dad2de95b29cbe
  Closes-Bug: #1483853
  DocImpact:  vxlan.{udp_srcport_min, udp_srcport_max and udp_dstport}
  can be used to set UDP port numbers used for VXLAN in LinuxBridge
  agent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1703413/+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 1714516] [NEW] doc refs to ocata based URLs

2017-09-01 Thread Boden R 
Public bug reported:

Today we have a number of static links to ocata based pages in our docs
[1].

For example a number of our config guides have static links to ocata
config-reference pages. While these links are not dead, they are
outdated and thus don't contain the latest content for our pike release.


[1] http://codesearch.openstack.org/?q=ocata=nope==neutron

** Affects: neutron
 Importance: Medium
 Assignee: Boden R (boden)
 Status: New


** Tags: doc

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

Title:
  doc refs to ocata based URLs

Status in neutron:
  New

Bug description:
  Today we have a number of static links to ocata based pages in our
  docs [1].

  For example a number of our config guides have static links to ocata
  config-reference pages. While these links are not dead, they are
  outdated and thus don't contain the latest content for our pike
  release.


  [1]
  http://codesearch.openstack.org/?q=ocata=nope==neutron

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1714516/+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 1675351] Re: glance: creating a public image fails during installation

2017-09-01 Thread Dr. Jens Harbott 
Yes, this issue was only caused by me misinterpreting the default glance
config.

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

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

Title:
  glance: creating a public image fails during installation

Status in Glance:
  Invalid
Status in openstack-manuals:
  Invalid

Bug description:
  Following the instructions at https://docs.openstack.org/ocata
  /install-guide-ubuntu/glance-verify.html I am getting this error when
  trying to upload the test image:

  $ openstack image create "cirros2"   --file cirros-0.3.5-x86_64-disk.img   
--disk-format qcow2 --container-format bare  --public
  403 Forbidden
  You are not authorized to complete publicize_image action.
  (HTTP 403)
  $

  Creating the image without the "--public" option works fine. I did
  verify that I do have the admin role as specified in
  /etc/glance/policy.json:

  "publicize_image": "role:admin",

  $ openstack role assignment list --na
  +---++---+-++---+
  | Role  | User   | Group | Project | Domain | Inherited |
  +---++---+-++---+
  | user  | demo@Default   |   | demo@Default|| False |
  | admin | admin@Default  |   | admin@Default   || False |
  | admin | glance@Default |   | service@Default || False |
  +---++---+-++---+
  $

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1675351/+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 1682244] Re: API Docs do not mention dns_name in port resource

2017-09-01 Thread Boden R 
This doc work was completed with
Ia5630ceb97d833b85d88cef323bcd2d6c9780c81 under bug
https://bugs.launchpad.net/neutron/+bug/1711992

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

Title:
  API Docs do not mention dns_name in port resource

Status in neutron:
  Fix Released

Bug description:
  I did a port list on citycloud and got this:

  {u'admin_state_up': True,
   u'allowed_address_pairs': [],
   u'binding:vnic_type': u'normal',
   u'created_at': u'2017-02-06T20:59:45',
   u'description': u'',
   u'device_id': u'f80e3ad0-e13e-41d4-8e9c-be79bccdb8f7',
   u'device_owner': u'compute:None',
   u'dns_name': None,
   u'extra_dhcp_opts': [],
   u'fixed_ips': [{u'ip_address': u'10.4.0.16',
   u'subnet_id': u'f0ad1df5-53ee-473f-b86b-3604ea5591e9'}],
   u'id': u'a767944e-057a-47d1-a669-824a21b8fb7b',
   u'mac_address': u'fa:16:3e:e8:7f:03',
   u'name': u'',
   u'network_id': u'2c9adcb5-c123-4c5a-a2ba-1ad4c4e1481f',
   u'security_groups': [u'9fb5ba44-5c46-4357-8e60-8b55526cab54'],
   u'status': u'ACTIVE',
   u'tenant_id': u'65222a4d09ea4c68934fa1028c77f394',
   u'updated_at': u'2017-02-06T20:59:49'}

  which, as you can see, has a field called "dns_name". Sadly, that
  field is not listed here:

  https://developer.openstack.org/api-ref/networking/v2/?expanded=show-
  port-details-detail

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1682244/+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 1653862] Re: hyper-v: Exception dispatching event Stopped>:

2017-09-01 Thread Lucian Petrut 
This has been fixed at the os-win level, which is now raising a
HyperVVMNotFoundException exception that can properly be handled by the
Nova Hyper-V driver.

Note that a debug message will still be logged in this situation [1], as
seen on a recent Hyper-V CI run[2].

[1] 2017-08-31 12:26:16.625 2336 90871568 MainThread DEBUG os_win._utils 
[req-69dcf4f7-c61f-4fd0-b7fc-c8adb1026821 - - - - -] x_wmi: Not Found exception 
raised while running get_vm_summary_info inner 
C:\Python27\lib\site-packages\os_win\_utils.py:244
[2] 
http://cloudbase-ci.com/nova/499690/2/Hyper-V_logs/192.168.5.111-compute01/nova-compute.log.gz

FWIW, the CI hardware is being moved, for which reason old CI result
URLs may be unavailable.

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

Title:
  hyper-v: Exception dispatching event  Stopped>: 

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  I see these errors quite a bit in the n-cpu logs for hyperv CI runs:

  2017-01-03 23:15:08.141 10848 80822320 MainThread ERROR
  nova.virt.driver [req-050d06ec-3636-4a5d-8b73-0531ef62055a - - - - -]
  Exception dispatching event  Stopped>: 

  http://64.119.130.115/nova/140045/51/Hyper-V_logs/c2-r22-u04-n03/nova-
  compute.log.gz

  I assume this is a lifecycle event for an instance that has been
  deleted. We're logging an error because of a problem dispatching the
  event.

  I'm not totally sure how to handle this, but if the virt driver could
  raise a NotFound or something we could handle that and not log it as
  an ERROR in the n-cpu logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1653862/+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 1714495] [NEW] Archlinux Netctl Bringup

2017-09-01 Thread Rich Lees 
Public bug reported:

I have been banging my head a bit with this one, especially as I am sure
it *used* to work although in theory it should never have done! I would
imagine a systemd update would have broken things.

I can't get cloud-init to configure the network when using `distro:
arch`. What seems to happen is this:

  - systemd looks at current units/services to start and begins boot.
  - cloud-init-local.service runs, mode in cmd/main.py is 'local'.
  - init.apply_network_config happens with bringup=False.
  - arch.py writes out a netctl config and enables it using netctl reenable 
enp0s3.
  - netctl creates a new systemd unit (netctl@enp0s3) and enables it
  - systemd list of services already resolved, so does not start netctl@enp0s3 
as it was created after the boot process started

So after the system is fully brought up, the interface is configured but
NOT started. A subsequent reboot makes the network become available.

A few things and thoughts:

  - I tried making bringup=True by force but cloud-init-local is too early in 
the boot process and netctl barfs when trying to do a restart on an interface 
here.
  - Debian and RHEL based seem to have their own ways of managing network that 
involve putting files in a certain place that an *already existing* service 
then comes along and processes later.
  - Tried from "master" and from 0.7.9.tar.gz

I can't think of a way netctl could ever work with cloud-init. Possibly
using systemd-networkd instead would be wise but then things like
Vagrant and no doubt other "cloud" providers expect Arch to be using
netctl.

Thoughts? Ideas? Even a .patch so I can bodge something to work would be
a big help right now but everything I have tried fails for one reason or
another.

** Affects: cloud-init
 Importance: Undecided
 Status: New

** Description changed:

  I have been banging my head a bit with this one, especially as I am sure
  it *used* to work although in theory it should never have done! I would
  imagine a systemd update would have broken things.
  
  I can't get cloud-init to configure the network when using `distro:
  arch`. What seems to happen is this:
  
-   - systemd looks at current units/services to start and begins boot.
-   - cloud-init-local.service runs, mode in cmd/main.py is 'local'.
-   - init.apply_network_config happens with bringup=False.
-   - arch.py writes out a netctl config and enables it using netctl reenable 
enp0s3.
-   - netctl creates a new systemd unit (netctl@enp0s3) and enables it
-   - systemd list of services already resolved, so does not start 
netctl@enp0s3 as it was created after the boot process started
+   - systemd looks at current units/services to start and begins boot.
+   - cloud-init-local.service runs, mode in cmd/main.py is 'local'.
+   - init.apply_network_config happens with bringup=False.
+   - arch.py writes out a netctl config and enables it using netctl reenable 
enp0s3.
+   - netctl creates a new systemd unit (netctl@enp0s3) and enables it
+   - systemd list of services already resolved, so does not start 
netctl@enp0s3 as it was created after the boot process started
  
  So after the system is fully brought up, the interface is configured but
- NOT started. A subsequent reboot makes the system become available.
+ NOT started. A subsequent reboot makes the network become available.
  
  A few things and thoughts:
  
-   - I tried making bringup=True by force but cloud-init-local is too early in 
the boot process and netctl barfs when trying to do a restart on an interface 
here.
-   - Debian and RHEL based seem to have their own ways of managing network 
that involve putting files in a certain place that an *already existing* 
service then comes along and processes later.
-   - Tried from "master" and from 0.7.9.tar.gz
+   - I tried making bringup=True by force but cloud-init-local is too early in 
the boot process and netctl barfs when trying to do a restart on an interface 
here.
+   - Debian and RHEL based seem to have their own ways of managing network 
that involve putting files in a certain place that an *already existing* 
service then comes along and processes later.
+   - Tried from "master" and from 0.7.9.tar.gz
  
  I can't think of a way netctl could ever work with cloud-init. Possibly
  using systemd-networkd instead would be wise but then things like
  Vagrant and no doubt other "cloud" providers expect Arch to be using
  netctl.
  
  Thoughts? Ideas? Even a .patch so I can bodge something to work would be
  a big help right now but everything I have tried fails for one reason or
  another.

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

Title:
  Archlinux Netctl Bringup

Status in cloud-init:
  New

Bug description:
  I have been banging my head a bit with this one, especially as I am
  sure it *used* to work although in theory it should never have

[Yahoo-eng-team] [Bug 1708006] Re: update man page paths in doc/source/conf.py

2017-09-01 Thread Gleb Zimin 
And it's already released.

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

Title:
  update man page paths in doc/source/conf.py

Status in Glance:
  Fix Released

Bug description:
  Pike commit 1c7f556d4f77d2dd7f282f2b41bdfb2abb6e5740 ("rearrange
  existing documentation to follow the new layout standard") moved man
  pages from doc/source/man to doc/source/cli. However the paths in
  doc/source/conf.py weren't updated accordingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1708006/+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 1714434] [NEW] VPNaas: ipsec process residue

2017-09-01 Thread XieYingYun 
Public bug reported:

   When I deleted the ipsec-site-connection and vpn service, I found the ipsec 
process residue at the network node. The ipsec configuration file in the 
directory / var / lib / neutron / ipsec has been deleted, but the ipsec process 
still exists.   
   I think there is a problem in the process of deleting the process. process 
the state is wrong, did not stop the porcess, then the implementation of the 
deletion of the configuration file.

** Affects: neutron
 Importance: Undecided
 Assignee: XieYingYun (smokony)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) => XieYingYun (smokony)

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

Title:
  VPNaas: ipsec process residue

Status in neutron:
  New

Bug description:
 When I deleted the ipsec-site-connection and vpn service, I found the 
ipsec process residue at the network node. The ipsec configuration file in the 
directory / var / lib / neutron / ipsec has been deleted, but the ipsec process 
still exists.   
 I think there is a problem in the process of deleting the process. process 
the state is wrong, did not stop the porcess, then the implementation of the 
deletion of the configuration file.

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