[Yahoo-eng-team] [Bug 1700338] [NEW] cloud-init-local would fail on NFS if no networking
Public bug reported: The cloud-init-local systemd service's executable is stored in /usr/bin. Also the service is currently run before networking has started. If a person wants to use NFS for /usr then it would mean that cloud-init- local service could not be run. See https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=805866#40 for further information. I also think that it is weird that the Debian's sysvinit file has $remote_fs as start requirement (it's the opposite of systemd service file): # Required-Start:$local_fs $remote_fs However the redhat sysvinit file doesn't have $remote_fs as requirement for start which makes this even more confusing. Files related to this bug: cloud-init/sysvinit/redhat/cloud-init-local cloud-init/sysvinit/debian/cloud-init-local cloud-init/systemd/cloud-init-local.service ** Affects: cloud-init Importance: Undecided Status: New ** Affects: cloud-init (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #805866 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805866 ** Also affects: cloud-init (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805866 Importance: Unknown Status: Unknown -- 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/1700338 Title: cloud-init-local would fail on NFS if no networking Status in cloud-init: New Status in cloud-init package in Debian: Unknown Bug description: The cloud-init-local systemd service's executable is stored in /usr/bin. Also the service is currently run before networking has started. If a person wants to use NFS for /usr then it would mean that cloud-init-local service could not be run. See https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=805866#40 for further information. I also think that it is weird that the Debian's sysvinit file has $remote_fs as start requirement (it's the opposite of systemd service file): # Required-Start:$local_fs $remote_fs However the redhat sysvinit file doesn't have $remote_fs as requirement for start which makes this even more confusing. Files related to this bug: cloud-init/sysvinit/redhat/cloud-init-local cloud-init/sysvinit/debian/cloud-init-local cloud-init/systemd/cloud-init-local.service To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1700338/+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 1700351] [NEW] port_update_postcommit doesn't see latest version of object
Public bug reported: Dragonflow's ML2 mechanism driver implements port_update_postcommit, and saves the port object (after translation) to its distributed database. In Dragonflow's tests [1], this object is compared with the object in the Neutron db (specifically the revision_number, which is translated to version on the Dragonflow object) Currently, this test fails, since the versions are different, even though there were no additional modifications to the port. [1] https://github.com/openstack/dragonflow/blob/18b89831532e4a5837e5cb61480f275f03d9d363/dragonflow/tests/unit/test_mech_driver.py#L374 ** Affects: neutron Importance: Undecided Assignee: Omer Anson (omer-anson) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Omer Anson (omer-anson) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1700351 Title: port_update_postcommit doesn't see latest version of object Status in neutron: In Progress Bug description: Dragonflow's ML2 mechanism driver implements port_update_postcommit, and saves the port object (after translation) to its distributed database. In Dragonflow's tests [1], this object is compared with the object in the Neutron db (specifically the revision_number, which is translated to version on the Dragonflow object) Currently, this test fails, since the versions are different, even though there were no additional modifications to the port. [1] https://github.com/openstack/dragonflow/blob/18b89831532e4a5837e5cb61480f275f03d9d363/dragonflow/tests/unit/test_mech_driver.py#L374 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1700351/+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 1700359] Re: test_os_service_disable_enable fails with "ERROR (NotFound): Could not find binary nova-scheduler on host"
This is the change in the API causing the issue:
https://review.openstack.org/#/c/442162/
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1700359
Title:
test_os_service_disable_enable fails with "ERROR (NotFound): Could not
find binary nova-scheduler on host"
Status in OpenStack Compute (nova):
Confirmed
Status in python-novaclient:
Confirmed
Bug description:
Seen here:
http://logs.openstack.org/41/435141/19/gate/gate-novaclient-dsvm-
functional-neutron-ubuntu-
xenial/894e11f/console.html#_2017-06-24_07_44_54_947034
2017-06-24 07:44:54.919101 | 2017-06-24 07:44:54.918 | {0}
novaclient.tests.functional.v2.test_os_services.TestOsServicesNovaClientV211.test_os_service_disable_enable
[1.927162s] ... FAILED
2017-06-24 07:44:54.920189 | 2017-06-24 07:44:54.919 |
2017-06-24 07:44:54.921445 | 2017-06-24 07:44:54.921 | Captured traceback:
2017-06-24 07:44:54.923085 | 2017-06-24 07:44:54.922 | ~~~
2017-06-24 07:44:54.924463 | 2017-06-24 07:44:54.924 | Traceback (most
recent call last):
2017-06-24 07:44:54.925897 | 2017-06-24 07:44:54.925 | File
"novaclient/tests/functional/v2/legacy/test_os_services.py", line 36, in
test_os_service_disable_enable
2017-06-24 07:44:54.927180 | 2017-06-24 07:44:54.926 | service =
self.nova('service-disable %s %s' % (host, serv.binary))
2017-06-24 07:44:54.928693 | 2017-06-24 07:44:54.928 | File
"novaclient/tests/functional/base.py", line 314, in nova
2017-06-24 07:44:54.930090 | 2017-06-24 07:44:54.929 | endpoint_type,
merge_stderr)
2017-06-24 07:44:54.932181 | 2017-06-24 07:44:54.931 | File
"/opt/stack/new/python-novaclient/.tox/functional/local/lib/python2.7/site-packages/tempest/lib/cli/base.py",
line 130, in nova
2017-06-24 07:44:54.933322 | 2017-06-24 07:44:54.933 | 'nova',
action, flags, params, fail_ok, merge_stderr)
2017-06-24 07:44:54.934956 | 2017-06-24 07:44:54.934 | File
"/opt/stack/new/python-novaclient/.tox/functional/local/lib/python2.7/site-packages/tempest/lib/cli/base.py",
line 374, in cmd_with_auth
2017-06-24 07:44:54.936084 | 2017-06-24 07:44:54.935 | self.cli_dir,
prefix=self.prefix)
2017-06-24 07:44:54.937305 | 2017-06-24 07:44:54.937 | File
"/opt/stack/new/python-novaclient/.tox/functional/local/lib/python2.7/site-packages/tempest/lib/cli/base.py",
line 71, in execute
2017-06-24 07:44:54.938430 | 2017-06-24 07:44:54.938 | result_err)
2017-06-24 07:44:54.939609 | 2017-06-24 07:44:54.939 |
tempest.lib.exceptions.CommandFailed: Command
'['/opt/stack/new/python-novaclient/.tox/functional/bin/nova', '--os-username',
'admin', '--os-tenant-name', 'admin', '--os-password', 'secretadmin',
'--os-auth-url', 'http://10.11.235.59/identity', '--os-compute-api-version',
'2.11', '--os-endpoint-type', 'publicURL', 'service-disable',
'ubuntu-xenial-osic-cloud1-s3500-9498382', 'nova-scheduler']' returned non-zero
exit status 1.
2017-06-24 07:44:54.941114 | 2017-06-24 07:44:54.940 | stdout:
2017-06-24 07:44:54.943100 | 2017-06-24 07:44:54.942 |
2017-06-24 07:44:54.945711 | 2017-06-24 07:44:54.943 | stderr:
2017-06-24 07:44:54.947034 | 2017-06-24 07:44:54.946 | ERROR (NotFound):
Could not find binary nova-scheduler on host
ubuntu-xenial-osic-cloud1-s3500-9498382. (HTTP 404) (Request-ID:
req-540e1c6a-f5b2-4d9d-be81-fe5c047a72b1)
This is due to changes in the compute API making it impossible to
disable non-nova-compute services since there is no HostMapping for
them, and the API looks up the host via host mapping to find which
cell it's in.
I'm actually surprised this isn't 100% failure:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22ERROR%20(NotFound)%3A%20Could%20not%20find%20binary
%20nova-
scheduler%20on%20host%5C%22%20AND%20tags%3A%5C%22console%5C%22&from=7d
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1700359/+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 1700362] [NEW] nova boot instance from volume not support specify the volume_type
Public bug reported: nova boot instance from volume not support specify the volume_type when cinder-volume was configured with multiple storage ** Affects: nova Importance: Undecided Assignee: kongxiangyun (kongxiangyun) Status: New ** Changed in: nova Assignee: (unassigned) => kongxiangyun (kongxiangyun) -- 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/1700362 Title: nova boot instance from volume not support specify the volume_type Status in OpenStack Compute (nova): New Bug description: nova boot instance from volume not support specify the volume_type when cinder-volume was configured with multiple storage To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1700362/+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 1700378] [NEW] Form validation error in ng-images create volume form
Public bug reported: Volume name no mandatory in cinder api, it should not restrict user input。 also, we should limit volume name and descriptions in 255 characters. ** Affects: horizon Importance: Undecided Assignee: wei.ying (wei.yy) Status: New ** Changed in: horizon Assignee: (unassigned) => wei.ying (wei.yy) -- 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/1700378 Title: Form validation error in ng-images create volume form Status in OpenStack Dashboard (Horizon): New Bug description: Volume name no mandatory in cinder api, it should not restrict user input。 also, we should limit volume name and descriptions in 255 characters. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1700378/+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 1700428] [NEW] trunk parent port/subport need limitation
Public bug reported: Currently, we use the trunk parent port to boot instance. But no limit to use trunk parent port to add router interface or use subports to boot some instances. And the trunk service only subscribe port delete, we need subscribe the port update to not allow user to use parent port to other way, and subport check to let user know the port is used by a trunk. ** Affects: neutron Importance: Undecided Assignee: zhaobo (zhaobo6) Status: New ** Changed in: neutron Assignee: (unassigned) => zhaobo (zhaobo6) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1700428 Title: trunk parent port/subport need limitation Status in neutron: New Bug description: Currently, we use the trunk parent port to boot instance. But no limit to use trunk parent port to add router interface or use subports to boot some instances. And the trunk service only subscribe port delete, we need subscribe the port update to not allow user to use parent port to other way, and subport check to let user know the port is used by a trunk. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1700428/+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 1698092] Re: Protocols for websocket should not be hardcorded
** Changed in: zun-ui 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/1698092 Title: Protocols for websocket should not be hardcorded Status in OpenStack Dashboard (Horizon): Fix Released Status in Zun-UI: Fix Released Bug description: To use serial console with any websocket protocol, the protocols should not be hardcoded. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1698092/+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 1700449] [NEW] Update firewall rule with a protocol fails
Public bug reported: Create a firewall rule via horizon with UDP protocol, and later try to update it to TCP. The Horizon UI will show this error: Error: Failed to update rule non shared rule: Invalid input for protocol. Reason: TCP is not in valid_values. Neutron server returns request_ids: ['req-66afa587-cafb-4e6d-8229-8081e8092437'] and the logs: 2017-06-26 05:35:37.708918 DEBUG:urllib3.connectionpool:http://10.160.90.203:9696 "PUT //v2.0/fw/firewall_rules/507f825b-6798-410f-bab7-41c4dcd7d99b HTTP/1.1" 400 136 2017-06-26 05:35:37.709929 ERROR openstack_dashboard.dashboards.project.firewalls.forms Failed to update rule 507f825b-6798-410f-bab7-41c4dcd7d99b: Invalid input for protocol. Reason: TCP is not in valid_values. 2017-06-26 05:35:37.709938 Neutron server returns request_ids: ['req-66afa587-cafb-4e6d-8229-8081e8092437'] 2017-06-26 05:35:37.710425 WARNING horizon.exceptions Recoverable error: Invalid input for protocol. Reason: TCP is not in valid_values. The reason is that the protocols should be sent to neutron in lower- case. ** Affects: horizon Importance: Undecided Assignee: Adit Sarfaty (asarfaty) Status: New ** Changed in: horizon Assignee: (unassigned) => Adit Sarfaty (asarfaty) -- 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/1700449 Title: Update firewall rule with a protocol fails Status in OpenStack Dashboard (Horizon): New Bug description: Create a firewall rule via horizon with UDP protocol, and later try to update it to TCP. The Horizon UI will show this error: Error: Failed to update rule non shared rule: Invalid input for protocol. Reason: TCP is not in valid_values. Neutron server returns request_ids: ['req-66afa587-cafb-4e6d-8229-8081e8092437'] and the logs: 2017-06-26 05:35:37.708918 DEBUG:urllib3.connectionpool:http://10.160.90.203:9696 "PUT //v2.0/fw/firewall_rules/507f825b-6798-410f-bab7-41c4dcd7d99b HTTP/1.1" 400 136 2017-06-26 05:35:37.709929 ERROR openstack_dashboard.dashboards.project.firewalls.forms Failed to update rule 507f825b-6798-410f-bab7-41c4dcd7d99b: Invalid input for protocol. Reason: TCP is not in valid_values. 2017-06-26 05:35:37.709938 Neutron server returns request_ids: ['req-66afa587-cafb-4e6d-8229-8081e8092437'] 2017-06-26 05:35:37.710425 WARNING horizon.exceptions Recoverable error: Invalid input for protocol. Reason: TCP is not in valid_values. The reason is that the protocols should be sent to neutron in lower- case. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1700449/+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 1700454] Re: "Quota exceeded for instances" in fwaas tempest tests
I added neutron because it doesn't seem to be networking-midonet specific.
it's seen in neutron-fwaas jobs.
http://logs.openstack.org/71/477371/1/check/gate-neutron-fwaas-v1-dsvm-tempest/c5d9fc4/
** Summary changed:
- "Quota exceeded for instances" in fwaas tests
+ "Quota exceeded for instances" in fwaas tempest tests
** Changed in: networking-midonet
Importance: Undecided => Critical
** Changed in: networking-midonet
Status: New => In Progress
** Changed in: networking-midonet
Milestone: None => 5.0.0
** Changed in: networking-midonet
Assignee: (unassigned) => YAMAMOTO Takashi (yamamoto)
** Tags added: fwaas
** Also 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/1700454
Title:
"Quota exceeded for instances" in fwaas tempest tests
Status in networking-midonet:
In Progress
Status in neutron:
New
Bug description:
eg. http://logs.openstack.org/87/199387/83/check/gate-tempest-dsvm-
networking-midonet-ml2-full-
centos-7-nv/b221d8d/logs/testr_results.html.gz
Traceback (most recent call last):
File
"/opt/stack/new/neutron-fwaas/neutron_fwaas/tests/tempest_plugin/tests/scenario/test_fwaas.py",
line 366, in test_firewall_disable_rule
allow=self._disable_rule)
File
"/opt/stack/new/neutron-fwaas/neutron_fwaas/tests/tempest_plugin/tests/scenario/test_fwaas.py",
line 305, in _test_firewall_basic
self._create_topology()
File
"/opt/stack/new/neutron-fwaas/neutron_fwaas/tests/tempest_plugin/tests/scenario/test_fwaas.py",
line 267, in _create_topology
security_group=security_group)
File
"/opt/stack/new/neutron-fwaas/neutron_fwaas/tests/tempest_plugin/tests/scenario/test_fwaas.py",
line 59, in _create_server
**kwargs)
File
"/opt/stack/new/neutron-fwaas/neutron_fwaas/tests/tempest_plugin/tests/scenario/manager.py",
line 208, in create_server
image_id=image_id, **kwargs)
File "tempest/common/compute.py", line 168, in create_test_server
**kwargs)
File "tempest/lib/services/compute/servers_client.py", line 89, in
create_server
resp, body = self.post('servers', post_body)
File "tempest/lib/common/rest_client.py", line 270, in post
return self.request('POST', url, extra_headers, headers, body, chunked)
File "tempest/lib/services/compute/base_compute_client.py", line 48, in
request
method, url, extra_headers, headers, body, chunked)
File "tempest/lib/common/rest_client.py", line 659, in request
self._error_checker(resp, resp_body)
File "tempest/lib/common/rest_client.py", line 760, in _error_checker
raise exceptions.Forbidden(resp_body, resp=resp)
tempest.lib.exceptions.Forbidden: Forbidden
Details: {u'message': u'Quota exceeded for instances: Requested 1, but
already used 10 of 10 instances', u'code': 403}
To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-midonet/+bug/1700454/+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 1696684] Re: When the router of admin_state_up becomes false, the IPSec process is not terminated
Reviewed: https://review.openstack.org/472169 Committed: https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=eaf4bfabbde50d9008819ad203bce377f549ec54 Submitter: Jenkins Branch:master commit eaf4bfabbde50d9008819ad203bce377f549ec54 Author: xiaoli Date: Wed Jun 7 09:11:46 2017 +0800 Delete the IPSec before the router is deleted The termination of the IPSec connection process requires router's netns presence to execute successfully, so the IPSec connection deletion should be executed before the router is deleted, rather than the router deletion. Closes-Bug: #1696684 Change-Id: Ia5b3576c0a53647ee273d025f1f8893348ccc6c0 ** 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/1696684 Title: When the router of admin_state_up becomes false, the IPSec process is not terminated Status in neutron: Fix Released Bug description: Router1---router2 establishes the IPSec connection, and after the IPSec connection is established, you can see two IPSec processes ps -ef |grep ipsec root 14232 1 0 Jun06 ?00:00:33 /usr/libexec/ipsec/pluto --ctlbase /var/lib/neutron/ipsec/03ff091d-091b-496f-bc41-c53b0ae38c6a/var/run/pluto --ipsecdir /var/lib/neutron/ipsec/03ff091d-091b-496f-bc41-c53b0ae38c6a/etc/ipsec.d --uniqueids --nat_traversal --secretsfile /var/lib/neutron/ipsec/03ff091d-091b-496f-bc41-c53b0ae38c6a/etc/ipsec.secrets --virtual-private %v4:172.16.1.0/24,%v4:172.16.2.0/24 --perpeerlogbase /var/lib/neutron/ipsec/03ff091d-091b-496f-bc41-c53b0ae38c6a/logs root 14826 1 0 Jun06 ?00:00:33 /usr/libexec/ipsec/pluto --ctlbase /var/lib/neutron/ipsec/7ecb91f2-a271-4365-8a89-2899a6165422/var/run/pluto --ipsecdir /var/lib/neutron/ipsec/7ecb91f2-a271-4365-8a89-2899a6165422/etc/ipsec.d --uniqueids --nat_traversal --secretsfile /var/lib/neutron/ipsec/7ecb91f2-a271-4365-8a89-2899a6165422/etc/ipsec.secrets --virtual-private %v4:172.16.2.0/24,%v4:172.16.1.0/24 --perpeerlogbase /var/lib/neutron/ipsec/7ecb91f2-a271-4365-8a89-2899a6165422/logs Operate on router1: Neutron router-update router1 --admin-state-up False The admin-state-up of router has changed to False, but the corresponding IPSec process has not been terminated Then, operate on the router1 Neutron router-update router1 --admin-state-up True The admin-state-up of router changes to True and starts the new IPSec process ps -ef |grep ipsec root 13796 1 0 16:43 ?00:00:00 /usr/libexec/ipsec/pluto --ctlbase /var/lib/neutron/ipsec/03ff091d-091b-496f-bc41-c53b0ae38c6a/var/run/pluto --ipsecdir /var/lib/neutron/ipsec/03ff091d-091b-496f-bc41-c53b0ae38c6a/etc/ipsec.d --uniqueids --nat_traversal --secretsfile /var/lib/neutron/ipsec/03ff091d-091b-496f-bc41-c53b0ae38c6a/etc/ipsec.secrets --virtual-private %v4:172.16.1.0/24,%v4:172.16.2.0/24 --perpeerlogbase /var/lib/neutron/ipsec/03ff091d-091b-496f-bc41-c53b0ae38c6a/logs root 14232 1 0 Jun06 ?00:00:33 /usr/libexec/ipsec/pluto --ctlbase /var/lib/neutron/ipsec/03ff091d-091b-496f-bc41-c53b0ae38c6a/var/run/pluto --ipsecdir /var/lib/neutron/ipsec/03ff091d-091b-496f-bc41-c53b0ae38c6a/etc/ipsec.d --uniqueids --nat_traversal --secretsfile /var/lib/neutron/ipsec/03ff091d-091b-496f-bc41-c53b0ae38c6a/etc/ipsec.secrets --virtual-private %v4:172.16.1.0/24,%v4:172.16.2.0/24 --perpeerlogbase /var/lib/neutron/ipsec/03ff091d-091b-496f-bc41-c53b0ae38c6a/logs root 14826 1 0 Jun06 ?00:00:33 /usr/libexec/ipsec/pluto --ctlbase /var/lib/neutron/ipsec/7ecb91f2-a271-4365-8a89-2899a6165422/var/run/pluto --ipsecdir /var/lib/neutron/ipsec/7ecb91f2-a271-4365-8a89-2899a6165422/etc/ipsec.d --uniqueids --nat_traversal --secretsfile /var/lib/neutron/ipsec/7ecb91f2-a271-4365-8a89-2899a6165422/etc/ipsec.secrets --virtual-private %v4:172.16.2.0/24,%v4:172.16.1.0/24 --perpeerlogbase /var/lib/neutron/ipsec/7ecb91f2-a271-4365-8a89-2899a6165422/logs To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1696684/+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
