junos-eznc: reboot function issue after upgrade from 2.7.1 to 2.7.2 version.

[chidanandpujar]

sw.reboot is not working after upgrading junos-eznc version from 2.7.1 to 2.7.2

Device details
qfx5120-32c

JUNOS version:
using 22.2R3-S4.10 and 22.2R2-S1.5. These are standalone devices

script:
This is how I call the function reboot:

            sw = SW(dev=self.session.handle)
            message = sw.reboot(in_min=0, at=None, all_re=False, on_node=None,
                                vmhost=False)

reboot works fine after reverting back to junos-eznc 2.7.1

[amummcent]

I've noted this issue impacting the juniper.device ansible collection. The device does not reboot following this action:

- name: Update the software after a request system storage cleanup
  juniper.device.software:
    local_package: "jinstall-host-qfx-5e-x86-64-23.4R2-S3.9-secure-signed.tgz"
    validate: false
    cleanfs: true
    no_copy: false
    user: "{{ username }}"
    passwd: "{{ password }}"
    reboot: true
  register: response

Also on a QFX5120-32C.

It appears related to this new code for 2.7.2 in lib/jnpr/junos/utils/sw.py, which always gets executed based on how those bool values are set, even if the device is not in a fabric. Commenting this section out restores functionality. I don't have a VC in service now to explore this further.

    if self._multi_VC_nsync is True or self._multi_VC is True:
        vc_members = [
            re.search(r"(\d+)", x).group(1)
            for x in self._RE_list
            if re.search(r"(\d+)", x)
        ]
        vc_members.remove(self.dev.facts["vc_master"])
        vc_members.insert(len(vc_members), self.dev.facts["vc_master"])

[chidanandpujar]

Fixed #1359