Found the problem and I don't know if anyone would want to fix it.
If the VPC is created after the VM is created, the VM will remain invisible to the VPC.
Ron On 12/30/24 5:01 AM, Wei ZHOU wrote:
It looks good in my testing too. Ron, do you use the default network offering for vpc networks ? -Wei On Sat, Dec 28, 2024 at 11:32 AM Daan Hoogland <daan.hoogl...@shapeblue.com> wrote:Ron, I just replayed your scenario in a lab environment - create a vpc - create a tier - create a vm - aquire a public ip - create a portforwarding rule for the ip and add the vm to it I've seen no strangeties. The only thing I can think of is the port range overlapping with something already assigned? ------------------------------ *From:* Ron Gage <r...@rongage.org.INVALID> *Sent:* 27 December 2024 22:08 *To:* users@cloudstack.apache.org <users@cloudstack.apache.org> *Subject:* Problem encountered adding an instance to a port forward entry Hi everyone! I must be doing something wrong here because I cannot enter a port forwarding rule on my VPC. CS Version 4.19.1.3. When I click on the "Add Instance" button in the UI (after specifying public and private port ranges) in the port forwarding tab, the new screen has no instances listed. The network tier searcher in the upper left of the screen is likewise empty. If I am understanding the terminology correct, I do indeed have a network tier defined as well as a couple of instances. From the VPC page: Could someone please help me figure out what I am doing wrong here? Thanks! Ron Gage Westland, MI
