proxies: block a ip that was hitting release-monitoring.org a lot

This ip had hit release-monitoring.org like 5,000,000 times in the
course of a few hours and swamped it's web pod.

Lets block it for now and see if anyone complains.
If this is you: please add some rate limiting.

Signed-off-by: Kevin Fenzi <kevin@scrye.com>

inventory/group_vars/proxies

@@ -84,6 +84,7 @@ nft_block_rules:
   - 'add rule ip filter INPUT ip saddr 101.47.184.0/21  counter reject'
   - 'add rule ip filter INPUT ip saddr 101.47.185.0/24  counter reject'
   - 'add rule ip filter INPUT ip saddr 101.47.186.0/23  counter reject'
+  - 'add rule ip filter INPUT ip saddr 34.159.191.146/32  counter reject'
 nft_custom_rules:
   # Need for rsync from log01 for logs.
   - 'add rule ip filter INPUT ip saddr 10.16.163.39     tcp dport 873 counter accept'

roles/copr/backend/tasks/resalloc.yml

@@ -45,11 +45,6 @@
         set -- $(echo "$decoded")
         IP=$1
       fi
-      case $RESALLOC_NAME in
-      *vmhost_p09_02_prod_01867876_20260202_151259*)
-        exit 0
-        ;;
-      esac
       ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o ConnectTimeout=10 "${SSH_USER-root}@$IP" true
     mode: "0755"
     dest: /usr/local/bin/resalloc-check-vm-ip