Problems after upgrade to PVE 8.1.3

[alexkenon]

Hi. After the upgrade to PVE 8.1.3 - 2 problems.

4 nodes in the cluster. The storage is Synology.

2 problems:
1. On all nodes, logs of the following type: iscsid[1363]: connection-1:0 cannot make a connection to fe80::211:32ff:fefe:dc69:3260 (-1,22)
2. Empty graphs for nodes.

I rebooted all the nodes, so they all updated to 8.1.3. As these 2 problems were, so they are. =(

IPv6 disable on Synology.

And what are the solutions to these 2 problems?

 

[bbgeek17]

Hi. After the upgrade to PVE 8.1.3 - 2 problems.

2 problems:
1. On all nodes, logs of the following type: iscsid[1363]: connection-1:0 cannot make a connection to fe80::211:32ff:fefe:dc69:3260 (-1,22)

one of the enhancements in 8.1 is ability to login to multiple portals for the iSCSI target:
https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_8.1

Storage
Improvements to the iSCSI storage backend:
Try to log into all discovered portals for a target, instead of just the single portal initially configured for the storage. This way, the storage can now become available in a multipath setup if at least one portal is online, even if the single configured portal is offline.

If you havent specifically specified IPv6, then its being discovered from synology.

---

Blockbridge: Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[alexkenon]

one of the enhancements in 8.1 is ability to login to multiple portals for the iSCSI target:
https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_8.1

Thank you for the link. In my case, then what should I do to stop these log entries?

Storage

Improvements to the iSCSI storage backend:
Try to log into all discovered portals for a target, instead of just the single portal initially configured for the storage. This way, the storage can now become available in a multipath setup if at least one portal is online, even if the single configured portal is offline.

If you havent specifically specified IPv6, then its being discovered from synology.

---

Blockbridge: Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

I have only 2 tabs in the settings of all local interfaces: IPv4 and 802.1X.
There is no IPv6 tab.
Where can I check for sure that IPv6 is turned off completely on Synology?

 

[bbgeek17]

I have only 2 tabs in the settings of all local interfaces: IPv4 and 802.1X.
There is no IPv6 tab.
Where can I check for sure that IPv6 is turned off completely on Synology?

I dont have the details on how to configure Synology. I would reach out to their support/forum.

But first, I would examine your PVE IP configuration, iscsiadm outputs, logs, etc.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[mweigelt]

I guess it's the same issue as here: https://forum.proxmox.com/threads/multipath-iscsi-problems-with-8-1.137953/

 

[alexkenon]

I guess it's the same issue as here: https://forum.proxmox.com/threads/multipath-iscsi-problems-with-8-1.137953/

Yes, you're right. The same problem and there are many such problems, it is strange that there is so little reaction from technical support. =(
Thanks for the link.

 

[RolandK]

ticket for this in proxmox bugzilla:

https://bugzilla.proxmox.com/show_bug.cgi?id=5173

 

[alexkenon]

Hi. Unfortunately, my problem has not been solved =((( is there any news on this issue? Is it possible that technical support has already been contacted?

 

[Egert143]

Did you ever got this solved ?

 

[alexkenon]

Did you ever got this solved ?

Hi. A colleague solved the problem and gave a link. I don't know what exactly he did, but he said that this link helped: github
It would be nice for developers to add to their knowledge base on this issue.

 

[Lephisto]

Same issue - got a customer with Open-E storage (which is the opposite of open).

So far the solution to mitigate the inherent split-brain issue was to have firewall rules that keep iscsi from connecting to the physical interfaces. This doesn't work any longer.

Is there any news on a fix? I am Stuck in the middle of a Cluster Upgrade from 8.0.x to 8.1.x..

regards