After update to 3.90.-16: Error running a command. cmd

Support
1

Brief description of the problem

After Update to 3.9.0.-16

Detailed step by step instructions to reproduce the problem

After Update to 3.9.0.-16 this error message occurs. Before the update there was no error becuase of the drives serial no. This is NOT virtual machine.

Web-UI screenshot

Bildschirmfoto vom 2017-07-12 17-45-34.png1904×866 125 KB

Error Traceback provided on the Web-UI

Traceback (most recent call last): File "/opt/rockstor/src/rockstor/rest_framework_custom/generic_view.py", line 41, in _handle_exception yield File "/opt/rockstor/src/rockstor/storageadmin/views/network.py", line 180, in get_queryset self._refresh_devices() File "/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/utils/decorators.py", line 145, in inner return func(*args, **kwargs) File "/opt/rockstor/src/rockstor/storageadmin/views/network.py", line 148, in _refresh_devices dmap = network.devices() File "/opt/rockstor/src/rockstor/system/network.py", line 50, in devices o2, e2, r2 = run_command([NMCLI, 'd', 'show', dev]) File "/opt/rockstor/src/rockstor/system/osi.py", line 115, in run_command raise CommandException(cmd, out, err, rc) CommandException: Error running a command. cmd = /usr/bin/nmcli d show vethda3e698. rc = 10. stdout = ['']. stderr = ["Error: Device 'vethda3e698' not found.", '']
2

@g6094199 Hello again. Yes it looks like the network setup stuff is expecting a different device name to what currently exists. ie:

Can you paste the output of the following command:

nmcli d show

I would imagine this is a bug where we are not coping well with a network device name change. I’m afraid I’m not that familiar with the network code just yet however.

Could you clarify that a little please, maybe a disks page screen shot (if possible).

Also can you show a screen shot of the network page (System- Network) if you can get to it?

Thanks.

3

[root@wvk-nas ~]#
[root@wvk-nas ~]# nmcli d show
GENERAL.GERÄT: docker0
GENERAL.TYP: bridge
GENERAL.HWADDR: 02:42:aa:aa:aa:B1
GENERAL.MTU: 1500
GENERAL.STATUS: 100 (verbunden)
GENERAL.VERBINDUNG: docker0
GENERAL.CON-PFAD: /org/freedesktop/NetworkManager/ActiveConnection/2
IP4.ADRESSE[1]: 172.17.0.1/16
IP4.GATEWAY:
IP6.ADRESSE[1]: fe80::42:79ff:fe47:48b1/64
IP6.GATEWAY:

GENERAL.GERÄT: enp1s0
GENERAL.TYP: ethernet
GENERAL.HWADDR: B8:97:aa:aa:aa:2A
GENERAL.MTU: 1500
GENERAL.STATUS: 100 (verbunden)
GENERAL.VERBINDUNG: enp1s0
GENERAL.CON-PFAD: /org/freedesktop/NetworkManager/ActiveConnection/1
WIRED-PROPERTIES.TRÄGERFREQUENZ: an
IP4.ADRESSE[1]: 192.168.x.xx/24
IP4.GATEWAY: 192.168.x.xx
IP4.DNS[1]: 192.168.x.x
IP4.DNS[2]: 192.168.x.xx
IP4.DNS[3]: 192.168.x.x
IP6.ADRESSE[1]: fe80::c407:73d4:cc54:600a/64
IP6.GATEWAY:

GENERAL.GERÄT: veth1de9c66
GENERAL.TYP: ethernet
GENERAL.HWADDR: 4E:7D:aa:aa:aa:6A
GENERAL.MTU: 1500
GENERAL.STATUS: 10 (nicht verwaltet)
GENERAL.VERBINDUNG: –
GENERAL.CON-PFAD: –
WIRED-PROPERTIES.TRÄGERFREQUENZ: an

GENERAL.GERÄT: lo
GENERAL.TYP: loopback
GENERAL.HWADDR: 00:00:00:00:00:00
GENERAL.MTU: 65536
GENERAL.STATUS: 10 (nicht verwaltet)
GENERAL.VERBINDUNG: –
GENERAL.CON-PFAD: –
IP4.ADRESSE[1]: 127.0.0.1/8
IP4.GATEWAY:
IP6.ADRESSE[1]: ::1/128
IP6.GATEWAY:
[root@wvk-nas ~]#

4

@g6094199 By way of notification / follow up I’m pretty sure that the cause of your reported issue has now been addressed by @suman in testing channel release version 3.9.1-7:

by way of pull request:

from your report of:

Hope that helps.