Bug 1303762

Summary: [RFE] Don't allow deployment of image/template combinations known to be broken
Product: Red Hat OpenStack Reporter: Steve Baker <sbaker>
Component: rhosp-directorAssignee: Florian Fuchs <flfuchs>
Status: CLOSED WONTFIX QA Contact: Amit Ugol <augol>
Severity: low Docs Contact:
Priority: low    
Version: 8.0 (Liberty)CC: apannu, beth.white, jbuchta, jcoufal, jrist, mburns, rhel-osp-director-maint
Target Milestone: Upstream M2Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: NeedsAllocation
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-24 12:27:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Steve Baker 2016-02-01 21:36:49 UTC 
The overcloud images are effectively coupled with a given version of tripleo-heat-templates. There will be images which are known *not* to work with a given version of tht but we should allow unknown images.

For example, the overcloud 7.1 images are known not to work with a 7.2 undercloud, but the deployment only fails very late in the stack.

I would like to suggest a blacklist of image checksums which lives in tripleo-heat-templates. tripleoclient can validate that the current glance overcloud-full image checksum doesn't match anything in the blacklist before starting a stack-create operation.

For stack-updates there would ideally need to be detection that a scale-up is happening, so that scale-up would fail early on a blacklisted image, but only a warning would be shown if there is no new nodes being created.
Comment 2 Mike Burns 2016-04-07 21:07:13 UTC 
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.