Description:
Add function list_l3_agent_hosting_routers in salt/modules/neutron.py
and salt/utils/openstack/neutron.py.
Add function list_agents in salt in salt/modules/neutron.py and
salt/utils/openstack/neutron.py.
attempting to run following state
---
/backup:
mount.mounted:
- device: joule:/backup
- fstype: nfs
- mkmnt: True
- opts: rw,nodev,nosuid
getting unexpected behavior:
----------
```
ID: /backup
Function: mount.mounted
Result: False
Comment: An exception occurred in this state: Traceback (most recent call last):
File "/usr/local/lib/python2.7/site-packages/salt/state.py", line 1591, in call
**cdata['kwargs'])
File "/usr/local/lib/python2.7/site-packages/salt/states/mount.py", line 120, in mounted
active = __salt__['mount.active'](extended=True)
File "/usr/local/lib/python2.7/site-packages/salt/modules/mount.py", line 184, in active
_active_mounts_openbsd(ret)
File "/usr/local/lib/python2.7/site-packages/salt/modules/mount.py", line 148, in _active_mounts_openbsd
'opts': parens[1].split(", "),
IndexError: list index out of range
Started: 21:51:47.764708
Duration: 38.882 ms
```
issue clarification:
---
function _active_mounts_openbsd()
expecting all mount points to have DUID
but NFS mounts do not have DUIDs generated, so line need to be parsed separately
proposal:
---
1. check length of parens array
2. and have a different parsing for lines with no DUIDs in them
testing same state after change:
---
```
Name: /etc/fstab - Function: file.blockreplace - Result: Clean
Name: /d01 - Function: mount.mounted - Result: Clean
Name: /stage - Function: mount.mounted - Result: Clean
Name: /backup - Function: mount.mounted - Result: Changed
```
---
Thanks,
Sergey.
__process_multiprocessing_logging_queue:
- A leak was observed in this process on Windows. On Windows, creating a
new process doesn't fork (copy the parent process image). Due to this, we
need to setup extended logging inside this process. The leak was due to
the temp null and temp logging handlers being active which just store
messages but don't process them. Setting up extended logging removes
those handlers and fixes the leak (as well as properly dealing with
incoming logging messages).
setup_multiprocessing_logging:
- A leak was obversed in processes that used this on Windows. Similar
to above, due to lack of fork, the new process will have the temp null
and temp logging handlers enabled, causing the leak. In this function,
removing those handlers prevents the leak.
Signed-off-by: Sergey Kizunov <sergey.kizunov@ni.com>
