Commit error, could not set flowcontrol for eth

Hi,

can you help me, I’m having problems adding a vlan or changing the configuration on one of the interfaces, I’m using a HPE Ethernet 10Gb 2-port 530SFP+ Adapter on a Dell Poweredge R630, the following is the attached log while committing.

najib@vyos:~$ configure
[edit]
najib@vyos# set interfaces ethernet eth5 vif 1000
[edit]
najib@vyos# commit
could not set flowcontrol for eth5
[ interfaces ethernet eth5 ]
could not set flowcontrol for eth5
VyOS had an issue completing a command.

We are sorry that you encountered a problem while using VyOS.
There are a few things you can do to help us (and yourself):
- Make sure you are running the latest version of the code available at
  https://downloads.vyos.io/rolling/current/amd64/vyos-rolling-latest.iso
- Consult the forum to see how to handle this issue
  https://forum.vyos.io
- Join our community on slack where our users exchange help and advice
  https://vyos.slack.com

When reporting problems, please include as much information as possible:
- do not obfuscate any data (feel free to contact us privately if your
  business policy requires it)
- and include all the information presented below

Report Time:      2021-06-30 14:39:16
Image Version:    VyOS 1.4-rolling-202106290839
Release Train:    sagitta

Built by:         autobuild@vyos.net
Built on:         Tue 29 Jun 2021 16:38 UTC
Build UUID:       818f899d-4004-4c1b-a98d-f1b687013088
Build Commit ID:  ce49275606e303

Architecture:     x86_64
Boot via:         installed image
System type:      bare metal

Hardware vendor:  Dell Inc.
Hardware model:   PowerEdge R630
Hardware S/N:     HW2DH32
Hardware UUID:    4c4c4544-0057-3210-8044-c8c04f483332

Traceback (most recent call last):
  File "/usr/libexec/vyos/conf_mode/interfaces-ethernet.py", line 157, in <module>
    apply(c)
  File "/usr/libexec/vyos/conf_mode/interfaces-ethernet.py", line 146, in apply
    e.update(ethernet)
  File "/usr/lib/python3/dist-packages/vyos/ifconfig/ethernet.py", line 367, in update
    self.set_speed_duplex(speed, duplex)

  File "/usr/lib/python3/dist-packages/vyos/ifconfig/ethernet.py", line 219, in set_speed_duplex

    return self._cmd(cmd)
  File "/usr/lib/python3/dist-packages/vyos/ifconfig/control.py", line 51, in _cmd
    return cmd(command, self.debug)
  File "/usr/lib/python3/dist-packages/vyos/util.py", line 161, in cmd
    raise OSError(code, feedback)
PermissionError: [Errno 1] failed to run command: ethtool -s eth5 autoneg on
returned:
exit code: 1

noteworthy:
cmd 'ethtool --pause eth5 autoneg on tx on rx on'
returned (out):

returned (err):
netlink error: Invalid argument
cmd 'ethtool -K eth5 ufo off'
returned (out):

returned (err):
Could not change any device features
cmd 'ethtool -s eth5 autoneg on'
returned (out):

returned (err):
netlink error: link settings update failed
netlink error: Invalid argument

[[interfaces ethernet eth5]] failed
Commit failed
[edit]
najib@vyos# exit

Thanks.

HI maimun.najib I hope you’re doing great,

I was taking a look at your issue and seems this occurs when the interface being modified does not support flow control and then commit fails.

Try this

vyos@vyos# set interfaces ethernet eth5 disable-flow-control 
[edit]
vyos@vyos# commit
[edit]
vyos@vyos# save
Saving configuration to '/config/config.boot'...
Done

Let me know if that worked

I have disabled flow control on eth5 but when I commit it still appears the log could not set flowcontrol for eth5 is that okay?

vyos@vyos# set interfaces ethernet eth9 address 100.100.100.1/30
[edit]
vyos@vyos# commit
could not set flowcontrol for eth9
[edit]
vyos@vyos#

I find these logs if I make changes via remote ssh, whereas if I remotely via console directly I don’t find those logs when committing. is there something wrong with my ssh configuration?

It was a problem with ethtool and the format of the output for the bullseye.
Try the latest rolling image, or install 1.3-rc4

in the test I used the latest rolling release version and 1.3-rc4 but still found the same logs, now I installed 1.3-rc4 on proxmox with the same hardware and the problem has been resolved.

It is not problem, if you don’t see any other commit fails like “Traceback (most recent call last):

okay thanks for the information, I will test again without using proxmox

I installed 1.3-rc4 on proxmox with the same hardware and the problem has been resolved.