Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
If the EIP of Cloud Orchestrator is disassociated from Cloud Orchestrator itself to the other instance, Cloud Orchestrator will not respond since its EIP will be gone.
Display a warning message before disassociating an EIP from Cloud Orchestrator itself to the other instance
Comment | File | Size | Author |
---|---|---|---|
#2 | 3172795-2.patch | 3.06 KB | baldwinlouie |
Comments
Comment #2
baldwinlouie CreditAttribution: baldwinlouie commentedAttaching patch with this functionality. Since Cloud Orchestrator does not allow an already "associated" EIP from being associated, we don't have to handle this use case. We only need to handle the case when Cloud Orchestrator's IP is being disassociated.
This patch adds the warning message to Bulk "Disassociate Elastic IP" form as well.
Comment #3
yas@baldwinlouie
Thank you for adding the warning message. I tested the patch and it looks good. I'll merge the patch to
8.x-1.x
and8.x-2.x
,3.x
and close this issue asFixed
.Comment #6
yasComment #8
yasComment #9
yasComment #10
yas