So, a few things. ;)

1. This is more a releng ticket than infra, but thats fine...

2. We don't untag things from rawhide once they have gone out in a compose. This was tagged in March 7th (almost 2 weeks ago?). Is there some extraordinary reason we should untag it?
   I mean at this point pretty much everyone using rawhide has gotten it. I don't understand what untagging it would assist with?

Adding on to the 2nd point, better than untagging it, the best way to handle this situation is bumping the nvr and rebuilding the package either with the fix for an issue or reverting to an older version.

So, a few things. ;)

1. This is more a releng ticket than infra, but thats fine...

2. We don't untag things from rawhide once they have gone out in a compose. This was tagged in March 7th (almost 2 weeks ago?). Is there some extraordinary reason we should untag it?
   I mean at this point pretty much everyone using rawhide has gotten it. I don't understand what untagging it would assist with?
   

We've experienced broken dns with this build on some rawhide CI machines so updating or downgrading was pretty much impossible, had to manually set a dns server first, so a simple nvr bump wouldn't fix it.

However if everyone has gotten it then I guess untagging it is a moot point.

Yeah, it seems unlikely anyone using rawhide wouldn't have updated already. ;(

Do note that I didn't see this here... so must not affect everyone somehow?

It sorta happened to me, but before setting the dns manually I rebooted it and that fixed my issue.