[PCA 2.4.3] Internal VM Storage Networking Causes Errors During Compute Node Reboot
(Doc ID 2722899.1)
Last updated on AUGUST 09, 2022
Applies to:
Private Cloud Appliance - Version 2.4.3 to 2.4.3 [Release 2.0]Linux x86-64
The ability to define Internal Storage Networks directly for VMs has been introduced in PCA 2.4.3 however it requires the application of a critical patch.
Symptoms
Starting with PCA 2.4.3 (Ethernet-based Racks only), you can configure VM Storage Networks that grant users access to the internal ZFS storage from their VMs.
We observe the VM Storage Networking introduces unexpected iscsi target(s) in Compute Nodes.
# iscsiadm -m node
192.168.40.1:3260,2 [iqn.1986-03.com|http://iqn.1986-03.com/].sun:02:fbcce094-4317-426d-be52-aff54d383142
172.31.0.254:3260,2 [iqn.1986-03.com|http://iqn.1986-03.com/].sun:02:de5ed15e-0c08-4eaf-bcaa-e33216a61a45
172.31.2.200:3260,2 [iqn.1986-03.com|http://iqn.1986-03.com/].sun:02:d8049295-9820-404f-ad0c-ac218f8e46d9
172.31.1.254:3260,2 [iqn.1986-03.com|http://iqn.1986-03.com/].sun:02:21784bc4-2096-4ce4-944a-e4f4cb5c5bd7
Only the first record for 192.168.40.1 should be presented on the Compute Nodes.
The other three came from VM storage Networking but Compute Nodes have no access to those networks.
Issues may occur with these unexpected iscsi targets.
Reboot Compute Node may timeout at starting iscsi and causing delay for about 2 minutes
Starting iscsi: iscsiadm: Could not login to [iface: default, target:iqn.1986-03.com.sun:02:4ee89e60-80ed-4ff7-bae1-a576960099a2, portal:10.10.10.100,3260].
iscsiadm: initiator reported error (8 - connection timed out)
iscsiadm: Could not log into all portals
[ OK ]
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |