A few thoughts on the "folsom-backport-potential" tag: this fix is heavily dependent on the glance client version, as indicated by Gabriel Hurley in his review. The glance client change [0] happened between the 0.4.0 and 0.4.1 version tag.
If this fix is applied to a codebase that relies on the older client library version, the checkbox will instead always reset to "True" for is_public, which may have more serious privacy implications as users could accidentally turn private images public...
At the moment Horizon's tools/pip-requires only lists python-glanceclient<2 with no minimum version. However both Ubuntu and Fedora seem to ship 0.5.1 only, and if we assume users tracking folsom would also use a recent version of the glance client, then it is probably safe enough to consider it for a backport.
A few thoughts on the "folsom- backport- potential" tag: this fix is heavily dependent on the glance client version, as indicated by Gabriel Hurley in his review. The glance client change [0] happened between the 0.4.0 and 0.4.1 version tag.
If this fix is applied to a codebase that relies on the older client library version, the checkbox will instead always reset to "True" for is_public, which may have more serious privacy implications as users could accidentally turn private images public...
At the moment Horizon's tools/pip-requires only lists python- glanceclient< 2 with no minimum version. However both Ubuntu and Fedora seem to ship 0.5.1 only, and if we assume users tracking folsom would also use a recent version of the glance client, then it is probably safe enough to consider it for a backport.
[0] https:/ /github. com/openstack/ python- glanceclient/ commit/ 8f0d5c4f2cea6e5 dae827b5f728c54 dab4a4386b