aboutsummaryrefslogtreecommitdiffstats
path: root/firstboot
diff options
context:
space:
mode:
authorSteven Hardy <shardy@redhat.com>2015-05-13 17:08:12 -0400
committerGiulio Fidente <gfidente@redhat.com>2015-06-03 16:26:51 +0200
commitc315681cc80ec95c8e38bb0a407346525c9b0d1e (patch)
treedd32d5bafbedf9fb64d114462a8739c46f800154 /firstboot
parentebb48a23fb23c6c7ad3701f52b62e6dd8af3b230 (diff)
Remove NO_SIGNAL from puppet role templates
Currently we use NO_SIGNAL on both the NetworkConfig and subsequent config deploying the data associated with the role. This means there is a risk that should the NetworkConfig do anything interruptive (os-net-config can do interface renaming based on discovery data for example) the role configuration config could fail, and we'd never know until some later error occurs. Additionally, we need to be sure that the heiradata deployed by each of the role specicific configs is actually in-place before proceeding with any of the cluster configuration - atm this works due to the inherent delays involved deploying to bare-metal, but there's still a theoretical race if very fast deployment backends (I'm thinking containers, e.g lxc backend to nova or something) were used instead. Essentially, we should never be using NO_SIGNAL unless we want to ignore failure, which AFAICT is not the case in this instance. Change-Id: I0dbbcc87fb8df8e6bc4775c39fa616b0d0713464
Diffstat (limited to 'firstboot')
0 files changed, 0 insertions, 0 deletions