curl -k -u admin https://localhost/policy/api/v1/infra/realized-state/status?intent_path=/infra/ip-pools/ipp_<IP-POOL-UUID>_egress/ip-allocations/<Allocation-UUID>
{ "consolidated_status" : { "consolidated_status" : "IN_PROGRESS" }, "consolidated_status_per_enforcement_point" : [ { "resource_type" : "ConsolidatedStatusPerEnforcementPoint", "enforcement_point_id" : "default", "consolidated_status" : { "consolidated_status" : "SUCCESS" } } ], "publish_status" : "UNREALIZED", "intent_version" : "0", "intent_path" : "/infra/ip-pools/ipp_<IP-POOL-UUID>_egress/ip-allocations/<Allocation-UUID>"
This issue occurs when the IpAddressAllocation is manipulated directly, normally the this is done using the Block to allocation the addresses from it.
This is a known issue impacting VMware NSX.
The issue is a cosmetic UI issue and has no impact on workloads.