Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

Failed Dependency on setting up network

Pages: 1 2 3

podilarius
44 Posts
April 29, 2022, 1:45 pm

After the update to 3.0.3 from 3.0.2 on reboot, I did get this dependency error again.

Network doesn't start up and its doing that on 3 of the 4 nodes updated so far.

#11

admin
2,930 Posts
April 29, 2022, 2:54 pm

Not sure what dependency error you get and how you fixed it last time ? i understood last time it was an incorrect clock/time set, and when you fixed it it worked ? do you get an error message of dependency failure ?

#12

podilarius
44 Posts
April 29, 2022, 3:05 pm

I thought it was time based, but I got it again with time fixed prior to upgrade, so I was wrong on the time.

The error message is that "RTNETLINK answers: File Exists".
Then Failed to bring up eth2.7.

Seems to think that a file already exists for this interface.
I was trying to find the dependencies for this service to start, perhaps its this file existing.

#13

admin
2,930 Posts
April 29, 2022, 3:30 pm

I suspect this is due to reboots rather than upgrades. Do you see any errors in PetaSAN.log file ? Do you see any errors after the log message "Start settings IPs" in the log file ?  Do you see the

syslog:Dec 23 17:48:12 prod-dbnk-cphsvr1 systemd[1]: Dependency failed for ifup for eth2.7.
syslog:Dec 23 17:48:12 prod-dbnk-cphsvr1 systemd[1]: ifup@eth2.7.service: Job ifup@eth2.7.service/start failed with result 'dependency'.

in syslog after or before the "Start settings IPs" message in PetaSAN.log

Is eth2.7 the interface for your management network ?

Note that PetaSAN does not rely on ifup, after boot PetaSAN does its own network configuration outside of Ubuntu /etc/network/interfaces so the setup uses a cluster wide configuration. Only the management interface is defined in  /etc/network/interfaces and started by Ubuntu in early boot phase after that PetaSAN configures all interfaces based on cluster configuration.

Can you post the following from a node with problem:

ip addr
/opt/petasan/scripts/detect-interfaces.sh
dpkg -l

files:
/etc/udev/rules.d/70-persistent-net.rules
/opt/petasan/config/cluster_info.json
/opt/petasan/config/node_info.json
/etc/network/interfaces
/opt/petasan/log/PetaSAN.log

Last edited on April 29, 2022, 3:30 pm by admin · #14

podilarius
44 Posts
May 4, 2022, 3:32 am

Yes, ETH2.7 is the management network.
I am going to change the IPs but you will get the idea.

ip addr:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:ff:6b:1e:59:0c brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:ff:6b:1e:59:0d brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:ff:6b:8b:30:2c brd ff:ff:ff:ff:ff:ff
5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:ff:6b:8b:30:2d brd ff:ff:ff:ff:ff:ff
10: eth2.7@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:ff:6b:8b:30:2c brd ff:ff:ff:ff:ff:ff
inet 10.1.7.182/24 scope global eth2.7
valid_lft forever preferred_lft forever
inet6 fe80::00:ff:6bff:fe8b:302c/64 scope link
valid_lft forever preferred_lft forever
11: eth3.17@eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:ff:6b:8b:30:2d brd ff:ff:ff:ff:ff:ff
inet 10.1.17.182/24 scope global eth3.17
valid_lft forever preferred_lft forever
inet6 fe80::00:ff:6bff:fe8b:302d/64 scope link
valid_lft forever preferred_lft forever
12: eth2.13@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether ac:1f:6b:8b:30:2c brd ff:ff:ff:ff:ff:ff
inet6 fe80::00:ff:6bff:fe8b:302c/64 scope link
valid_lft forever preferred_lft forever

/opt/petasan/scripts/detect-interfaces.sh
device=eth0,mac=00:ff:6b:1e:59:0c,pci=1a:00.0,model=Intel Corporation Ethernet Connection X722 for 10GBASE-T,path=enp26s0f0
device=eth1,mac=00:ff:6b:1e:59:0d,pci=1a:00.1,model=Intel Corporation Ethernet Connection X722 for 10GBASE-T,path=enp26s0f1
device=eth2,mac=00:ff:6b:8b:30:2c,pci=1b:00.0,model=Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (AOC-STGN-I2S [REV 1.01]),path=enp27s0f0
device=eth3,mac=00:ff:6b:8b:30:2d,pci=1b:00.1,model=Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (AOC-STGN-I2S [REV 1.01]),path=enp27s0f1

For dpkg I have not added any packages aside from what comes on the ISO and updates.sh.
Download Link for dpkg: https://ufile.io/5yymjf3f
Download Link for persitent net rules: https://ufile.io/t6ojz1v9
Download Link for cluster_info, node_info, interface and log file: https://ufile.io/f/kf47y

These links are removed after 30 days.

Let me know if you need anything further.

#15

podilarius
44 Posts
June 3, 2022, 4:23 am

I think this might have to do with trying to use a vlan without a base NIC ip.

I have also found several articles on defining this as a service "ifup@eth2.7.service".
It seems to failing as it is either already defined or doesn't know anything about a vlan 7.

The consensus is to remove this service and let networking.service define it.
The only place I can find it defined is at: /opt/petasan/config/etc/network/interfaces

I see that it is linked to /etc/network/interfaces.
I think if I can remove the ifup@eth2.7.service, I won't have this problem.

Please let me know your opinion or recommended commands.

#16

podilarius
44 Posts
June 3, 2022, 4:29 am

I don't see an ifup@.service in my lab system. I am not sure how it got in to my production. Also, is this fixed in 3.1.0?

#17

admin
2,930 Posts
June 3, 2022, 9:22 am

Can you post your

/etc/network/interfaces

#18

podilarius
44 Posts
June 4, 2022, 2:02 am

cat /etc/network/interfaces
auto eth2.7
iface eth2.7 inet static
address 10.x.y.18z
netmask 255.255.255.0
gateway 10.x.y.254
dns-nameservers 10.a.b.1

~# ll /etc/network/interfaces
lrwxrwxrwx 1 root root 42 Jan 12 16:33 /etc/network/interfaces -> /opt/petasan/config/etc/network/interfaces

#19

admin
2,930 Posts
June 4, 2022, 12:22 pm

have you manually activated any services ?

what is the status of

systemctl status ifup@eth2.7

systemctl status  systemd-networkd

Last edited on June 4, 2022, 12:24 pm by admin · #20
Pages: 1 2 3