This bug description sounds a lot like a class B2 according to VMT taxonomy: https://security.openstack.org/vmt-process.html#incident-report-taxonomy .
Since we are considering reverting the CVE-2017-16239 fix before newton-eol, should we request an embargo exception (e.g. make this report public) to facilitate coordination? ( https://security.openstack.org/vmt-process.html#embargo-exceptions )
This bug description sounds a lot like a class B2 according to VMT taxonomy: https:/ /security. openstack. org/vmt- process. html#incident- report- taxonomy .
Since we are considering reverting the CVE-2017-16239 fix before newton-eol, should we request an embargo exception (e.g. make this report public) to facilitate coordination? ( https:/ /security. openstack. org/vmt- process. html#embargo- exceptions )