Closed valaparthvi closed 4 weeks ago
@mjura @yiannistri Can this get some love?
Fixed on Rancher v2.9-6e9cf233a87796ee9a96e73c096a82101fc9c2ff-head.
The issue is still persistent. The IP range was removed, but then it got re-added after a few minutes.
cc: @mjura @yiannistri
Tested this again on Rancher (v2.9-0ab20e8fe6275887c52b97e94e15365f33b8afab-head); Dashboard(release-2.9 https://github.com/rancher/dashboard/commit/6e45e2fabb473335ca8975560b57d1657554ff27), aks-operator(rancher-aks-operator:104.1.0+up1.9.1-rc.4).
FIXED.
Rancher: v2.9-3c4ccdc5bc9fde3510089153b5ad58fdbe604880-head Dashboard: master https://github.com/rancher/dashboard/commit/00e9eb2a64b5bde237fd9b9e03a03b460e8d7307
Adding a new IP range works as expected, but removing an IP range does not work, from UI, all the buttons are active and even the operator logs indicate that an update is in progress, but when the update finishes, there appears to be no change.
Steps to reproduce:
Authorized IP Ranges
.The removed IP range is still present in both AKSConfig and UpstreamSpec.
Notes:
Updating
state, is this expected?Ref: https://github.com/rancher/dashboard/issues/6879#issuecomment-2222294833
PR's