Page MenuHomeVyOS Platform

vyos_bgp_global setting neighbor passive causes module to try configuring neighbhr next-hop-self
Open, NormalPublicBUG

Description

When using module vyos_bgp_global to configure neighbor as passive, it causes ansible to try configuring 'neighbor nexthop-self'.
Commenting out the passive variable allows play to execute properly (but not set passive neighbor config).

STEPS TO REPRODUCE
Run ansible play trying to set neighbor passive and ansible will error out

# Ansible play
- name: "Configure BGP Global"
  vyos.vyos.vyos_bgp_global:
    config: "{{ bgp_global }}"

# bgp_global host variable file
bgp_global:
  as_number: 64555
  bgp_params:
    default:
      no_ipv4_unicast: true
    router_id: 10.1.1.1
    log_neighbor_changes: true
  neighbor:
    - address: 10.240.10.20
      passive: true
      remote_as: 64555
    - address: 10.240.10.30
      passive: true
      remote_as: 64555
    - address: 10.240.10.40
      passive: true
      remote_as: 64555

EXPECTED RESULTS
bgp_global moduel should configure specified neighbor as passive:

set protocols bgp 64555 neighbor 10.240.10.40 passive

ACTUAL RESULTS
Ansible tries to configure neighbor nexthop-self.

ansible.module_utils.connection.ConnectionError: set protocols bgp 64555 neighbor 10.240.10.40 nexthop-self                                                                                                                                                                                                                                     
  Configuration path: protocols bgp 64555 neighbor 10.240.10.40 [nexthop-self] is not valid                                                                             
  Set failed

Details

Version
2.8.0
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Bug (incorrect behavior)

Event Timeline

syncer triaged this task as Normal priority.
vyosbot added a project: Restricted Project.Mon, Oct 28, 6:09 AM