No Action button in UI Network-> Public IP Addresses

[Imvedansh]

problem

Description:

When selecting multiple public IP addresses from the list view in the CloudStack UI, there are currently no action buttons available to remove or alter them. This makes it impossible to perform batch actions on public IPs, which seems like a regression or a missing feature.

Context:

I reviewed [Issue #8106 ], which was related to UI/UX overlap and positioning of the action buttons when multiple IPs were selected.

There was a proposed fix in [PR #9288], but that PR was closed without being merged.

Currently, there is no UI option to perform any action (like release or edit) on multiple selected public IPs.

Questions:

Was the decision to remove or not show the action buttons intentional?

If yes, what is the proposed alternative to allow bulk management of public IPs?

If no, could it be that the buttons were accidentally omitted in recent UI changes?

Expected Behavior:

When multiple public IP addresses are selected:

A consistent action menu or toolbar should appear.

Users should be able to perform batch actions, such as releasing multiple IPs.

Actual Behavior:

No action buttons or toolbar is displayed.

No way to manage selected IPs in bulk.

versions

Main, 4.20

The steps to reproduce the bug

Steps to Reproduce:

Go to the Network section

Navigate to the Public IP Addresses tab.

Select multiple IP addresses using checkboxes.

Observe that no action options appear.

What to do about it?

No response

[bernardodemarco]

@Imvedansh, thanks for creating the issue.

PR #10351 introduced some changes in the public IP addresses UI section.

Was the decision to remove or not show the action buttons intentional?

Changes were made to only display the disassociateIpAddress API action button in group actions for IPs that are not source NAT or system reserved (assigned to system VMs). It is not possible to directly disassociate these types of public IPs in Apache CloudStack and, previous to the PR, the UI used to display the option to disassociate them through group actions.

If yes, what is the proposed alternative to allow bulk management of public IPs?

It is possible to disassociate public IPs that are not source NAT and not assigned to system VMs.

[Imvedansh]

@bernardodemarco Thanks for explaining,
Makes sense! I was thinking instead of hiding the Disassociate button when system or source NAT IPs are selected, we could always show it, but keep it disabled and enable only when selected not systm vms
as well add a tooltip like:
“Cannot disassociate system-reserved or source NAT IPs.”

This would make the UI clearer and help users understand why the action isn’t available.
WDYT?

[bernardodemarco]

This would make the UI clearer and help users understand why the action isn’t available.

Yes, it makes total sense

[DaanHoogland]

@Imvedansh are you planning to implement this? cc @bernardodemarco

[Imvedansh]

@DaanHoogland Yes, I was working on it,been wanting to talk about it,im currently caught up with end sems ,will be done by mid of nov..
I ll push the changes , with few follow ups.
sincerely for the delay .

[DaanHoogland]

np @Imvedansh , just wanted to know. It is now set to milestone 20.3 which I’m making inventory for , hence my question.

[Imvedansh]

@DaanHoogland Cool, still i will try to get it done soon, as well had few questions regarding the changes would ask about them before pushing, Thanks