You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a floating IP is assigned to an instance in our private cloud, the IP address remains a private address (e.g. 172.24.4.45) which does not allow SSH access. Since our current private cloud is not publicly accessible (only through UOM wireless), this issue is preventing users from accessing their instances.
Steps to Reproduce:
Assign a floating IP to an instance
Try to SSH into the instance using the assigned IP address
Expected Behavior:
User should be able to SSH into the instance using the assigned floating IP address.
Actual Behavior:
SSH access is not possible due to the assigned IP address being a private address.
The text was updated successfully, but these errors were encountered:
Description:
When a floating IP is assigned to an instance in our private cloud, the IP address remains a private address (e.g. 172.24.4.45) which does not allow SSH access. Since our current private cloud is not publicly accessible (only through UOM wireless), this issue is preventing users from accessing their instances.
Steps to Reproduce:
Assign a floating IP to an instance
Try to SSH into the instance using the assigned IP address
Expected Behavior:
User should be able to SSH into the instance using the assigned floating IP address.
Actual Behavior:
SSH access is not possible due to the assigned IP address being a private address.
The text was updated successfully, but these errors were encountered: