The corresponding Network Tier like vpc-XXX-privateNetwork cannot be automatically removed

[xuanyuanaosheng]

ISSUE TYPE

• Bug Report

COMPONENT NAME

• VR, Private gateway

CLOUDSTACK VERSION

• CloudStack 4.18.0.0

CONFIGURATION

• Cloudstack zone with VXLAN
• VPC --> tier

OS / ENVIRONMENT

• oracle linux 8

SUMMARY

The VPC tier will auto add a name like vpc-XXX-privateNetwork when add a Private Gateway to a VPC. But when deleting a Private Gateway, the corresponding Network Tier like vpc-XXX-privateNetwork cannot be automatically removed.

STEPS TO REPRODUCE

• Create a VPC
• Create a tier test and dev
• Add Private gateway
• Delete the Private gateway
• Check the Networks tier and the VR status, In my env, the Private gateway only has one. but the Networks tier is still having the deleted the privateNetwork.
  

EXPECTED RESULTS

when deleting a Private Gateway, the corresponding Network Tier like vpc-XXX-privateNetwork cannot be automatically removed.

[weizhouapache]

@xuanyuanaosheng
you expect the network to be automatically removed, or not ?

[xuanyuanaosheng]

@weizhouapache I think the network should be automatically removed.

[weizhouapache]

@weizhouapache I think the network should be automatically removed.

@xuanyuanaosheng yes, it should. can you check database table network if the XXX-privateNetwork has been removed ?

[xuanyuanaosheng]

@weizhouapache I have checked the database, the XXX-privateNetwork is not removed status

select name,broadcast_domain_type,created, removed,public_mtu ,private_mtu from networks where name LIKE 'vpc-dev%' and broadcast_domain_type ='Vxlan';

[weizhouapache]

@xuanyuanaosheng
I tried just now, it looks ok

*************************** 8. row ***************************
     id: 207
   name: vpc-vpc-001-privateNetwork
created: 2023-08-22 11:10:00
removed: 2023-08-22 11:11:42
*************************** 9. row ***************************
     id: 208
   name: vpc-vpc-001-privateNetwork
created: 2023-08-22 11:10:31
removed: 2023-08-22 11:13:52
*************************** 10. row ***************************
     id: 209
   name: vpc-vpc-001-privateNetwork
created: 2023-08-22 11:14:14
removed: 2023-08-22 11:15:11
*************************** 11. row ***************************
     id: 210
   name: vpc-vpc-001-privateNetwork
created: 2023-08-22 11:14:40
removed: 2023-08-22 11:15:37
11 rows in set (0.00 sec)

any exception in your management server log ?
(I used vlan , not vxlan)

[btzq]

Hi Guys, we are encountering this same issue.

There is a random network created where:

• We are unable to view it (brings to a cannot find page).
• This happens when using normal user account to create a Private Gateway with VXLAN enabled.

[btzq]

Also, when a new PrivateGateway is created (with VXLAN) as a normal user,

Why does it create a new network? I thought it should only create a NIC in the associated network?

[weizhouapache]

@btzq
it is the record for vpc private gateway. It is not a regular guest network, you cannot deploy vm on it.

if you delete the private gateway in VPC, the record should be deleted as well. otherwise, there are something wrong.

[btzq]

Hi @weizhouapache ,

I can confirm that if we use a normal user account, to create a private gateway, and then delete the private gateway, then the network that was created will not be deleted. We had to delete it directly from the database.

If the created network is necessary for the private gateway, can i also request that:

• If the Gateway is deleted, then the network should be deleted too.
• Allow users to rename the created network (currently its some random name and its hard to remember/manage just by the name)
• When the user clicks on the network, it shows a 'cannot find network' page. (This experience should be improved otherwise users will think its a bug).

[weizhouapache]

Hi @weizhouapache ,

I can confirm that if we use a normal user account, to create a private gateway, and then delete the private gateway, then the network that was created will not be deleted. We had to delete it directly from the database.

If the created network is necessary for the private gateway, can i also request that:

• If the Gateway is deleted, then the network should be deleted too.

agree, if this is a bug, it should be fixed.
However, in my testing, when I removed the private gateway, the corresponding network vpc-<xxx>-privateGateway has been removed as well.

• Allow users to rename the created network (currently its some random name and its hard to remember/manage just by the name)

the name is not random, it uses the format vpc-<vpc name>-privateNetwork
is it necessary to rename it ?

• When the user clicks on the network, it shows a 'cannot find network' page. (This experience should be improved otherwise users will think its a bug).

maybe the link should be disabled or linked to the private gateway
they are not real "Guest" networks, and not displayed in the list of guest networks.

[btzq]

@weizhouapache are you using a normal user account? (Not Root, or Domain Admin)

Can we have the option for users to rename it? For me, id think that a format such as this is more easy to identify that it was created for PirvateGateway:

• privateGateway-

That way, when i look at the networks under the VPC, i can easily identify that this is a network created for this specific private gateway purpose (if i have a few created, being able to edit the name makes it easier to maintain). These are just my thoughts.

Yes, i agree with not displaying it in the list of guest networks. If it can be put somewhere else that is easier to identify as a guest network, it will not be as confusing.