The following packages ended up in the wrong component in the Proposed pocket:

linux-restricted-modules-aws-5.11 5.11.0-1009.9~20.04.2 - is in universe instead of multiverse
linux-modules-nvidia-390-5.11.0-1009-aws 5.11.0-1009.9~20.04.2 - is in universe instead of multiverse
linux-modules-nvidia-390-aws-edge 5.11.0-1009.9~20.04.2 - is in restricted instead of multiverse
linux-modules-nvidia-418-server-5.11.0-1009-aws 5.11.0-1009.9~20.04.2 - is in universe instead of multiverse
linux-modules-nvidia-418-server-aws-edge 5.11.0-1009.9~20.04.2 - is in restricted instead of multiverse
linux-modules-nvidia-435-aws-edge 5.11.0-1009.9~20.04.2 - is in restricted instead of multiverse
linux-modules-nvidia-440-aws-edge 5.11.0-1009.9~20.04.2 - is in restricted instead of multiverse
linux-modules-nvidia-440-server-aws-edge 5.11.0-1009.9~20.04.2 - is in restricted instead of multiverse
linux-modules-nvidia-450-aws-edge 5.11.0-1009.9~20.04.2 - is in restricted instead of multiverse
linux-modules-nvidia-450-server-5.11.0-1009-aws 5.11.0-1009.9~20.04.2 - is in universe instead of multiverse
linux-modules-nvidia-450-server-aws-edge 5.11.0-1009.9~20.04.2 - is in restricted instead of multiverse
linux-modules-nvidia-455-aws-edge 5.11.0-1009.9~20.04.2 - is in restricted instead of multiverse
linux-modules-nvidia-460-5.11.0-1009-aws 5.11.0-1009.9~20.04.2 - is in universe instead of multiverse
linux-modules-nvidia-460-aws-edge 5.11.0-1009.9~20.04.2 - is in restricted instead of multiverse
linux-modules-nvidia-460-server-5.11.0-1009-aws 5.11.0-1009.9~20.04.2 - is in universe instead of multiverse
linux-modules-nvidia-460-server-aws-edge 5.11.0-1009.9~20.04.2 - is in restricted instead of multiverse
linux-modules-nvidia-465-5.11.0-1009-aws 5.11.0-1009.9~20.04.2 - is in universe instead of multiverse
linux-modules-nvidia-465-aws-edge 5.11.0-1009.9~20.04.2 - is in restricted instead of multiverse
linux-objects-nvidia-390-5.11.0-1009-aws 5.11.0-1009.9~20.04.2 - is in universe instead of multiverse
linux-objects-nvidia-418-server-5.11.0-1009-aws 5.11.0-1009.9~20.04.2 - is in universe instead of multiverse
linux-objects-nvidia-450-server-5.11.0-1009-aws 5.11.0-1009.9~20.04.2 - is in universe instead of multiverse
linux-objects-nvidia-460-5.11.0-1009-aws 5.11.0-1009.9~20.04.2 - is in universe instead of multiverse
linux-objects-nvidia-460-server-5.11.0-1009-aws 5.11.0-1009.9~20.04.2 - is in universe instead of multiverse
linux-objects-nvidia-465-5.11.0-1009-aws 5.11.0-1009.9~20.04.2 - is in universe instead of multiverse
linux-restricted-signatures-aws-5.11 5.11.0-1009.9~20.04.2 - is in universe instead of multiverse
linux-signatures-nvidia-5.11.0-1009-aws 5.11.0-1009.9~20.04.2 - is in universe instead of multiverse
linux-aws-edge 5.11.0.1009.9~20.04.9 - is in main instead of universe
linux-aws-edge 5.11.0.1009.9~20.04.9 - is in main instead of universe
linux-headers-aws-edge 5.11.0.1009.9~20.04.9 - is in main instead of universe
linux-headers-aws-edge 5.11.0.1009.9~20.04.9 - is in main instead of universe
linux-image-aws-edge 5.11.0.1009.9~20.04.9 - is in main instead of universe
linux-image-aws-edge 5.11.0.1009.9~20.04.9 - is in main instead of universe
linux-modules-extra-aws-edge 5.11.0.1009.9~20.04.9 - is in main instead of universe
linux-modules-extra-aws-edge 5.11.0.1009.9~20.04.9 - is in main instead of universe
linux-tools-aws-edge 5.11.0.1009.9~20.04.9 - is in main instead of universe
linux-tools-aws-edge 5.11.0.1009.9~20.04.9 - is in main instead of universe

Once this is fixed, set the promote-signing-to-proposed to Fix Released again