Code fixes certainly take longer than a week, since this is an issue between Activate and IAP code. There are multiple things that need to happen to validate it's fixed and ensure it doesn't create or introduce other issues.
CJoseph's last update was:
This is a backend error. It means that there is no firmware upgrade available and it is not handled correctly by the access point. For now assume it means there is no firmware upgrade.
I will re-post when it is fixed.
The thread was closed because there's no update, and we're starting to lock threads when done because years later people re-open the thread and it creates tracking issues and makes it more confusing when people search for X and pull up a 2-3 year old thread. There's no attempt here to prevent people from asking questions, but there's no value in continuing a thread that has been answered.
If you want to track it actively, then a TAC case would be required so that you can get updates as to when it's expected to be fixed. That is the value of having a valid support contract.
Otherwise, without a support contract, as noted above, CJoseph looked it up within that other thread and relayed that it's been logged as an issue, an answer was provided as to 'what it means', and you can track the release notes for these errors to see if it's logged as a 'known issue but not fixed', or if it's been fixed in any upcoming releases as they come out in the future.
As to your assertions in the OP:
1. If we didn't care, we wouldn't be supporting and responding on this forum. And from what I've read in the bug notes, this is not really a "security" issue, it's a cosmetic message.
2. As noted above, it's not a matter of understanding, it's a matter of recognizing that bug fixes don't get root-caused across two platforms, get integrated, QA'd by TE, approved by PLM, and released into new code in 1-2 weeks.
We all appreciate your participation in the Aruba Community, but I would ask that you minimize casting aspersions on the contributors.