Commits on Mar 15, 2023

1. Adding conditional update "PodmanMissingAuthFlag" for 4.11.* to 4.12.… …

   …* upgrade paths
   
   Like 034fa01 (blocked-edges/4.12.*: Declare AWSOldBootImages,
       2022-12-14, openshift#2909) and 957626a , this cnditional risk is sticky,
       because we don't have PromQL access to boot-image age, so we cannot automatically distinguish
       between "born in 4.1 and still uses the old boot images" and "born
       in 4.1, but has subsequently updated boot images".  And because of
       a cluster-version operator bug, we don't necessarily have access to
       the cluster's born-in release anyway.
   
       The CVO bug fix went back via:
   
       * 4.11.0 https://bugzilla.redhat.com/show_bug.cgi?id=2097067#c12
       * 4.10.24 https://bugzilla.redhat.com/show_bug.cgi?id=2108292#c6
       * 4.9.45 https://bugzilla.redhat.com/show_bug.cgi?id=2108619#c6
       * 4.8.47 https://bugzilla.redhat.com/show_bug.cgi?id=2109962#c6
       * 4.7.59 https://bugzilla.redhat.com/show_bug.cgi?id=2117347#c8
       * 4.6.61 https://bugzilla.redhat.com/show_bug.cgi?id=2118489#c6
   
       So it's possible for someone born in 4.1 to have spend a whole bunch
       of time in 4.9.z and be reporting a 4.9.0-rc.* or something as their
       born-in version.  Work around that by declaring this risk for AWS
       clusters where the born-in version is 4.9 or earlier, expecting that
       we'll have this issue fixed soonish, so folks with old boot images
       will be able to update to a later 4.11, and allowing us to be overly
       broad/cautious with the risk matching here.
   
   Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>

   

   LalatenduMohanty committed Mar 15, 2023
   Configuration menu

   • View commit details
   • Copy full SHA for ec2bc7e
   • Browse repository at this point

   Copy the full SHA

   ec2bc7e View commit details

   Browse the repository at this point in the history