I removed it from our dns pool for buildlogs.centos.org but the ec2 instance seems dead and in "stopping" state and can't even reboot, so clearly something to investigate
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: centos-common-infra, high-gain, medium-trouble
after investigation, the underlying hardware for that EC2 instance was having issues, so the "forced stopping" action worked to have it stopped. But on restart, it goes of course to a different hypervisor but also got a new public ipv4. It was then reflected in ansible/monitoring and node was enabled back in dns
Metadata Update from @arrfab: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.