-
Notifications
You must be signed in to change notification settings - Fork 3.4k
az cli issue #23446
Copy link
Copy link
Open
Labels
Auto-AssignAuto assign by botAuto assign by botNetworkaz network vnet/lb/nic/dns/etc...az network vnet/lb/nic/dns/etc...Service AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.act-quality-productivity-squadbugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.
Milestone
Metadata
Metadata
Assignees
Labels
Auto-AssignAuto assign by botAuto assign by botNetworkaz network vnet/lb/nic/dns/etc...az network vnet/lb/nic/dns/etc...Service AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.act-quality-productivity-squadbugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Related command
az network nic ip-config delete -g Nable -n Service-Private-VIP --nic-name sbc-a703
az network nic ip-config create -g Nable --nic-name sbc-b276 -n Service-Private-VIP --private-ip-address 10.0.0.100
az network nic ip-config update -n Service-Private-VIP --nic-name sbc-b276 --public-ip-address Service-Public-VIP -g Nable
Describe the bug
Delete the Service-Private-VIP assigned to NIC SBC-A703 of Virtual Machine A, create the same Service-Private-VIP on NIC SBC-B276 of Virtual Machine B, and attempt to allocate the PUBLIC IP (Service-Public-VIP).
However, it takes too long for this process to proceed.
A communication disconnection time for the service-public-VIP occurs for more than 100 seconds. Can I reduce the time allocated to Virtual Machine B?
To Reproduce
Expected behavior
PRIVATE IP / PUBLIC IP used by Virtual Machine A
I hope it can be reallocated to Virtual Machine B within 10 seconds.
Environment summary
[root@sbc-a scripts]# az version
{
"azure-cli": "2.38.0",
"azure-cli-core": "2.38.0",
"azure-cli-telemetry": "1.0.6",
"extensions": {}
}
[root@sbc-a scripts]# cat /etc/redhat-release
CentOS Linux release 7.9.2009 (Core)
bash type
Additional context