[BUG] Deltaproxy __proxy_keepalive only works for 1 of 8 subproxys

[Zpell82]

Description
When setting up deltaproxy with napalm, we only get one __prox_keepalive session when expecting 8 one per subproxy

Setup
top.sls:

    base:
      'delta-*':
        - deltaproxy
      '*-lab':
        - jrouter
        - juniper_schedule

jrouter.sls:

    proxy:
      proxytype: napalm
      driver: junos
      host: {{ opts.id }}
      username: {{ salt['environ.get']('NEBULA_USER_ID') }}
      passwd: {{ salt['environ.get']('NEBULA_USER_PW') }}
      optional_args:
        port: 22

deltaproxy.sls:

    {% set delta_number = opts.id.split('-')[3] | int %}
    {% do salt.log.debug(delta_number) %}
    {% set routers = [
    'a1-304763-lab', 'm2-304765-lab', 'a1-304761-lab', 'a1-304762-lab', 'r1-304762-lab',
    'b1-304763-lab', 'b1-304761-lab', 'c2-304763-lab', 'c2-304764-lab', 'y1-304763-lab',
    'y1-304764-lab',  'c1-304762-lab',
    'y2-304761-lab', 'y2-304762-lab',  
     'm1-304765-lab'
    ] %}
    ## 'z1-304763-lab', 'z1-304764-lab', 'z1-304764-lab', 'f2-304765-lab','z1-304761-lab', 'z1-304762-lab','f1-304765-lab',

    {% set routers_per_delta = 8 %}

    {% set start_index = (delta_number - 1) * routers_per_delta %}
    {% set end_index = delta_number * routers_per_delta %}

    proxy:
      parallel_startup: False
      proxytype: deltaproxy
      ids:
        {% for index in range(start_index, end_index) %}
          {% if routers[index] is defined %}
          {% do salt.log.debug(routers[index]) %}
        - {{ routers[index] }}
          {% endif %}
      {% endfor %}

Please be as specific as possible and give set-up details.

• on-prem machine
• VM (Virtualbox, KVM, etc. please specify)
• VM running on a cloud service, please be explicit and add details
• [x ] container (Kubernetes)
• or a combination, please be explicit
• jails if it is FreeBSD
• classic packaging
• onedir packaging
• used bootstrap to install

Steps to Reproduce the Behavior
(Include debug logs if possible and relevant)

Expected behavior
expected behavior is one jobb per subproxy

Screenshots
images of logs showing only one working __proxy_keepalive when expecting 8


here is one with exact same schedule added via pillar and it works fine.

Versions Report
Salt Version:
Salt: 3006.2

Python Version:
Python: 3.10.4 (main, Apr 20 2022, 01:21:48) [GCC 10.3.1 20210424]

Dependency Versions:
cffi: 1.14.6
cherrypy: unknown
dateutil: 2.8.1
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
Jinja2: 3.1.2
libgit2: 1.1.0
looseversion: 1.0.2
M2Crypto: Not Installed
Mako: Not Installed
msgpack: 1.0.2
msgpack-pure: Not Installed
mysql-python: Not Installed
packaging: 22.0
pycparser: 2.21
pycrypto: Not Installed
pycryptodome: 3.9.8
pygit2: 1.6.1
python-gnupg: 0.4.8
PyYAML: 6.0.1
PyZMQ: 23.2.0
relenv: Not Installed
smmap: Not Installed
timelib: 0.2.4
Tornado: 4.5.3
ZMQ: 4.3.4

System Versions:
dist: alpine 3.14.6
locale: utf-8
machine: x86_64
release: 5.15.0-69-generic
system: Linux
version: Alpine Linux 3.14.6

PASTE HERE

Additional context
Add any other context about the problem here.

[welcome]

Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
Please be sure to review our Code of Conduct. Also, check out some of our community resources including:

• Community Wiki
• Salt’s Contributor Guide
• Join our Community Slack
• IRC on LiberaChat
• Salt Project YouTube channel
• Salt Project Twitch channel

There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar.
If you have additional questions, email us at saltproject@vmware.com. We’re glad you’ve joined our community and look forward to doing awesome things with you!

[Zpell82]

whats added to schedule.

schedule:
      reconnect: 
        function: status.proxy_reconnect
        maxrunning: 1
        jid_include: True
        return_job: False
        minutes: 1
        kwargs: 
          proxy_name: napalm

[garethgreenaway]

@Zpell82 Apologies for the delay on this one. Haven't been able to reproduce this one. Is there anything particular about your proxy configuration? Do you have multiprocessing enabled?

[Zpell82]

@garethgreenaway
No multiprocessing, its a straight-up deltaproxy setup, it's the same issue regarding its juniper or IOS .
it will only start 1 status.proxy_reconnect session , are u certain u getting status.proxy_reconnect sessions for all ?
what setup are you using No multiprocessing, its a straight-up deltaproxy setup, it's the same issue regarding its juniper or IOS .
it will only start 1 status.proxy_reconnect session , are u certain u getting status.proxy_reconnect sessions for all ?
what setup are you using

[garethgreenaway]

@Zpell82 By default multiprocessing is enabled but often times with some proxy minions multiprocessing needs to be disabled. That might be causing what you're seeing. I don't have access to physical switches so I have to use virtual ones and I'm using cisssh to simulate Cisco devices over SSH using the napalm proxy, but I do see scheduled jobs for each sub proxy on a regular schedule.

[Zpell82]

@garethgreenaway I use cisssh also to simulate, can I get your Dockerfile setup + config for master/minion and so on so can I test and and compare if my setup differs from yours