Comment 1 for bug 1872439

What version are you observing this behavior with? I would defer to someone with more FWaaS expertise, but this seems like expected behavior. I don't see why this sequence of commands would lead the status of the firewall group to be anything other than ACTIVE. I wouldn't expect the status field to indicate whether it is bound to policies or not, I would simply expect status to indicate proper provisioning of the resource.