Next time, please include dep3 headers such as Origin:. Given that you pinged in #ubuntu-devel to get this looked at, it would really help if you did the things that make SRU reviews easier. However this isn't a blocker. Apart from this the upload itself looks good.
> This causes the code to not fall back into the legacy mode
I don't understand how this justifies this bug for an SRU. Please could you explain the actual user impact, so I can measure that against SRU criteria? See https://wiki.ubuntu.com/StableReleaseUpdates#Procedure "An explanation of the bug on users and justification for backporting the fix to the stable release"
SRU review:
Next time, please include dep3 headers such as Origin:. Given that you pinged in #ubuntu-devel to get this looked at, it would really help if you did the things that make SRU reviews easier. However this isn't a blocker. Apart from this the upload itself looks good.
> As per https:/ /storyboard. openstack. org/#!/ story/2007371 we identified that
ubuntu clouds running the version 4.6.0 (bionic) aren't raising a 404
error when a secret container is passed.
> This causes the code to not fall back into the legacy mode
I don't understand how this justifies this bug for an SRU. Please could you explain the actual user impact, so I can measure that against SRU criteria? See https:/ /wiki.ubuntu. com/StableRelea seUpdates# Procedure "An explanation of the bug on users and justification for backporting the fix to the stable release"
> [Regression Potential]
This is missing "a discussion of how regressions are most likely to manifest, or may manifest even if it is unlikely, as a result of this change". See https:/ /wiki.ubuntu. com/StableRelea seUpdates# Procedure
Please update the bug description, fixing [Impact] and [Regression Potential] as above, and then we can reconsider your upload. Thanks!