Repository navigation
LoadBalancer Rules still creating usage register after deleting public ip associated with #9443
Description
Discussed in #9439
Originally posted by KuasarCloud July 24, 2024
Hi,
In ACS 4.19.0.1 when I delete a public IP with load balancer rules attached to it the usage system continues to register usage record even the rules are deleted with public IPs
Example:
list loadbalancerrules projectid=cc4e03f3-f32a-44bf-a594-xxxxxx domainid=1abeee53-eb0c-4924-9b71-53dxxxxxxx
returns zero records for rules
but everyday with get new usage records
+----------------------------------------+-----------------------------+-----------------------------+----------+--------+
| DESCRIPTION | STARTDATE | ENDDATE | RAWUSAGE | USAGE |
+----------------------------------------+-----------------------------+-----------------------------+----------+--------+
| Loadbalancer policy usage | 2024-07-01'T'00:00:00-05:00 | 2024-07-01'T'23:59:59-05:00 | 24 | 24 Hrs |
We didn't delete the rules before only the public ip
Regards,
Ricardo P
Activity
KuasarCloud commentedon Jul 26, 2024
Hi,
Just to add to the case,
These are the events when deleting the loadbalancerrules directly from publicip
LB.DELETE | Scheduled | deleting load balancer: 272
LB.DELETE | Started | deleting load balancer. Load balancer ID: 272
LB.DELETE | Completed | Successfully completed deleting load balancer. Load balancer ID: 272
but when releasing the public IP, there is not LB.DELETE event, which is causing to populate the usage records indefinitely and the actual load balancer rules are deleted indeed
NET.IPRELEASE | Scheduled | Disassociating IP address with ID=13
NET.IPRELEASE | Started | disassociating Ip. IP ID: 13 FIREWALL.CLOSE | Started | revoking firewall rule. IP ID: 13 FIREWALL.CLOSE | Completed | Successfully completed revoking firewall rule. IP ID: 13 VPN.REMOTE.ACCESS.DESTROY | Started | removing remote access vpn. IP ID: 13 VPN.REMOTE.ACCESS.DESTROY | Completed | Successfully completed removing remote access vpn. IP ID: 13 NET.IPRELEASE | Completed | Successfully completed disassociating Ip. IP ID: 13
nvazquez commentedon Jan 13, 2026
Hi @Eden790 @KuasarCloud I tried replicating the issue on 4.22 (will verify on a 4.20.2 environment as well) and even though the events for LB.DELETE are not created, I do observe the usage events on the table
usage_eventare created with type = 'LB.DELETE' when releasing an IP containing LB rules. Are these records on theusage_eventtable also missing in your case?github-actions commentedon Sep 3, 2026
This issue is stale because it has been open for 120 days with no activity. It may be removed by administrators of this project at any time. Remove the stale label or comment to request for removal of it to prevent this.