Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When removing Speed and Duplex order of operations yields error: ERROR: Duplex is not Compatible with Speed #868

Open
bl1nkbl1nk opened this issue Jun 11, 2024 · 0 comments · May be fixed by #869
Labels
has_pr This issue has an associated PR.

Comments

@bl1nkbl1nk
Copy link

SUMMARY

When speed and duplex settings are removed in nxos_interfaces the order of operations should be to delete duplex first and then speed. Otherwise NXOS gives an error.

router01(config)# interface ethernet 1/9
router01(config-if)# no speed
ERROR: Duplex is not Compatible with Speed

ISSUE TYPE
  • Bug Report
COMPONENT NAME

cisco.nxos.nxos_interfaces:

ANSIBLE VERSION
ansible-prod % ansible --version
ansible [core 2.15.8]
COLLECTION VERSION
8.1.0
CONFIGURATION
no diff
OS / ENVIRONMENT

Ansible EE image

STEPS TO REPRODUCE

Try to run a config with speed and duplex to auto on an interface that currently is set to 100/full (manual)

  - description: some device
    duplex: full
    enabled: true
    mode: layer2
    name: Ethernet1/5
    speed: '100'
    
 Then after that configure this with duplex and speed removed (default auto)
 
   - description: some device
    enabled: true
    mode: layer2
    name: Ethernet1/5

 
EXPECTED RESULTS

when casting "speed" and "duplex"

When configuring

  1. Speed
  2. Duplex

When removing (no speed)

  1. Duplex
  2. Speed
ACTUAL RESULTS

Module tries to delete speed first and gets error from device:

ERROR: Duplex is not Compatible with Speed

Possible solution??

in line 380 change the order of operations? I'm not super aware of how this codebase works, but looks like the right area

@KB-perByte KB-perByte added the has_pr This issue has an associated PR. label Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has_pr This issue has an associated PR.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants