Proxmox 7 node on OVH unreachable after reboot
Hello, can somebody help me resolve following maddness pls?
Proxmox host node is OVH network dedicated (SoYouStart)
/etc/network/interfaces:
auto lo
iface lo inet loopback
iface eno3 inet manual
auto vmbr0
iface vmbr0 inet static
address 54.38.192.11/24
gateway 54.38.192.254
bridge-ports eno3
bridge-stp off
bridge-fd 0
1) After node server full reboot is network UNREACHABLE
2) But when i run SSH command:
service networking restart
network is reachable and work fine:
# ip route
default via 54.38.192.254 dev vmbr0
54.38.192.0/24 dev vmbr0 proto kernel scope link src 54.38.192.11
I do not know resolve this madness WHY after reboot mentioned config does not work = network unreachable, but after additional manual networking restart the same config works fine....
BTW: i do not want use DHCP config = default (automatic OVH install) config:
auto lo
iface lo inet loopback
iface eno3 inet manual
auto vmbr0
iface vmbr0 inet dhcp
bridge-ports eno3
bridge-stp off
bridge-fd 0
I want use STATIC config, not DHCP
many thanks in advance for each attempt to help resolve this madness
Good day and Goodbye
Thanked by (1)AlwaysSkint
Comments
is that the only network config file?
dirty fix - just add an init script in /etc/init.d/ to restart networking at every reboot.
https://webhorizon.net
update 2: after searching on net i found that several ppl report the same problem after upgrade on PROXMOX 7 (unreachable network). So probably version 7 is still pretty bugged. (maybe reason why OVH still not offers Proxmox 7 template?) I tried several changes in config but not resolved this (not found exact reason and clean solution), without success
Good day and Goodbye
Hi @miu!
Please answer a few questions from a clueless guy:
(A) In your original post,
How do you run the ssh command when the network is unreachable?
(B) What do the logs say about bringing the network up as part of the reboot? Is there something that failed?
(C) In your
interface eno3 is set to "manual."
In man (5) interfaces, it says,
Further down in the vmbr0 section, your /etc/network interfaces also has the line,
bridge-ports eno3. What is supposed to happen when ifup reaches thatbridge-ports eno3line following reboot? Could it be that there is a failure at thatbridge-ports eno3line because eno3 is called but eno3 is not present because manual configuration was specified for eno3?I have seen other similar configurations which specify
bridge-ports noneinstead ofbridge-ports eno3. Proxmox' Routed Configuration example hasbridge-ports none:Maybe your issue could be resolved by changing
bridge-ports eno3tobridge-ports none?In summary:
Could your issue be resolved by changing
bridge-ports eno3tobridge-ports none?Hope this is helpful! Best wishes from Mexico!
I hope everyone gets the servers they want!
Hello Oles, firstly thank you for your response!
ANSWER @ A) Remotely Through IPMI console
ANSWER @ B & C:
Thanks for your suggestion - this i not tried (change bridge-ports from ens 3 to none)
From time reasons after several hours of frustration i reinstalled whole node from ISO 6.4 - it works FINE (network) with my above mentioned origin static config
Maybe i will try your suggested change next time when install another Proxmox node from v7 ISO, then i will can update this
thanks! regards miu
Good day and Goodbye
So just now i can conclude only:
works on Proxmox 6.4 + SYS well (network works without any troubles)
but on new Proxmox v7 + SYS not at all (network UNREACHABLE)
Good day and Goodbye
@miu i would look at the networking service if its started at reboot.
look at the kernel logs in the console etc ...
but if its a bug in v.7 then you have to live with it until update.
@ehab Yeah. for sure, but @miu can't look at the logs after the machine is reinstalled.
I hope everyone gets the servers they want!
u r right - exactly ma face after suffering from this issue! :-D
Good day and Goodbye
I'm using a similar network config with Proxmox VE 7.0-9 and no problems at all.
But I didn't use the ISO. Installed on top of Debian.
Somehow I missed that 7 was available - still running 6.4 on my boxes. Thanks for the heads-up.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Reddit is full of people bombing their boxes with 7 upgrade. I've decided I'll wait a month or 5. There isn't really anything I need in 7...
I'll run the tests and make sure that I have done some updates on my Proxmox Backup Server.
@miu Re. networking issue; I wonder if this is the cause:
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
@miu I ran a little test.
My server (running Debian sid, not Proxmox) had
bridge-ports none.Just for fun I tried changing the "none" to "enp7s0", which is the name of my server's primary interface, corresponding to "eno3" on your server.
systemctl restart networkingfollowing this change broke networking, which was the hoped-for result.I reverted via the rescue system.
Conceivably, my little test supports the possibility that changing "eno3" to "none" on your system might have fixed the network problem?
Does anybody know how likely it is for my clueless guess to be right?
Friendly greetings from Mexico!
I hope everyone gets the servers they want!
your mixing things up here old friend.
he does not try to actually route (additional) IPs yet. he sets the initial bridge vmbr0 on the main IP (therefore ens3 config is empty/manual) and with that he MUST have something bridging to that interface - because it does not get an IP and therefore nothing can be routed to it.
if you'd later on add an additional bridge for a routed config you also do not route towards ens3 then but vmbr0. small but important difference to what you are suggesting.
TL;DR; I suggest to try and not mix up 'bridged config' and 'routed config' just yet ;-)
PS: with soyoustart/OVH the routed config does not work well anyway. but you'll get virtual macs for all additional IPs individually (even if bought in subnets). so the bridged config is correct and the better choice.
mine looks exactly the same, but I haven't looked at proxmox 7 yet and also always only install on top of debian 🤷♂️
I had this exact issue with 7 on a Hosthatch VPS.
MaxKVM VPSes upgraded without issue.
I ended up rolling back to 6.4, definitely was a bug in pve 7. Didn't seem related to the MAC address changes in bullseye.
hey @Not_Oles why not upgrade now and worry later
Good day good people!
UPDATE from another forum (credit @ polluxtroy3758) = what is in journalctl log on OVH-brands PVE7 server:
bridge port does not exist
Good day and Goodbye
and here is (mine) working network log from SYS with PVE6.4 (installed from ISO) with bridged (above mentioned) config, bridge port found and works as should:
-- Logs begin at Tue 2021-07-27 20:23:58 CEST, end at Wed 2021-07-28 13:49:12 CEST. --
Jul 27 20:24:03 pve systemd[1]: Starting Raise network interfaces...
Jul 27 20:24:04 pve ifup[1059]: Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
Jul 27 20:24:04 pve systemd[1]: Started Raise network interfaces.
Good day and Goodbye
no response from Proxmox staff on it yet (on their forum where i reported issue), when will be then i will update this thread also
Good day and Goodbye
@miu Thanks for the updates! Especially with the logs. Could you please post or PM me your Proxmox forum post link?
I hope everyone gets the servers they want!
Hello Oles (Tom)
SURE (hopefully i do not break any rules when post here URL from another forum)
https://forum.proxmox.com/threads/proxmox-node-on-ovh-soyoustart-unreachable-after-each-reboot.93470/
I will be glad when this may help to someone in future
For now as i have mentioned i have resolved it so that i have reinstalled machine from ISO 6.4 (no time, not own ability fix issue)
Good day and Goodbye
@miu Thanks again! Watching the thread on the Proxmox forum.
I hope everyone gets the servers they want!
Nothing for thanking ;-) Unfortunately non-paid (customer) support there is not very well (slow and sometime w/o response of staff ever).. But i understand that for complete and good support i should purchase paid licence
Good day and Goodbye
from that the network device simply is not ready when the networkis tried to be brought up. could be that when you use dhcp it only fires at later point in time because of different dependencies and therefore does not see the same issues.
might even be unrelated to OVH/SYS specifics, but could also be related to drivers and whatnot... interesting. a workaround could probably be to fiddle with systemd and have it bring up networking only later.
Additionally - bridged config with DHCP also does not work on OVH with PVE7 (ISO installation)
(on 6.4 ISO works)
Good day and Goodbye
oh, okay, I misread that and thought this at least would work. however, still thinking systemd simply tries to start networking to early then while the real device is not ready.
Thank you for all your contribution, time and suggestions, appreciated by me!
Good day and Goodbye
Had this exact problem when I moved to PVE7 (upgraded from 6.4). I messed with my interfaces for a while as the network appeared to be up after a restart for ~5 minutes before dying.
I'll probably have a note somewhere as to what happened on my side as I cannot remember what I changed, my interfaces file is as below now though;
Which seems to be working - will update if I can find the logs from before! This is a dedi with Skynode.
i can help you remember