Red Hat Bugzilla – Bug 1466878
OSP9 minor update: the new ServiceNetMap from overcloud.yaml is not used
Last modified: 2018-01-29 10:05:15 EST
Description of problem:
During OSP9 minor update, the default ServiceNetMap parameter from overcloud.yaml in tripleo-heat-templates was not used. As a result network mapping were missing and the generated hieradata was incorrect.
Version-Release number of selected component (if applicable):
[stack@director ~]$ rpm -qa | grep puppet
[stack@director ~]$ rpm -qa | grep tripleo
Could not reproduce.
The generated sshd_config on compute nodes was invalid due to missing hieradata.
Forked from https://bugzilla.redhat.com/show_bug.cgi?id=1463680.
The update procedure was not followed correctly. A scale-out deployment was run after updating the undercloud but before updating the overcloud. A number of manual fixes were attempted to restore the overcloud to a good state. This may not be significant however.
I see that the portal issue is closed, can we close this bug?
I'd rather we had a root cause for this. We had to explicitly provide the correct ServiceNetMap in that case to workaround this.
Is it possible that at some point in the lifetime of that stack, ServiceNetMap had been explicitly set (e.g via an environment file) but not longer is, and this value is saved on the stack?
if it was savet at any time, then yes it's saved in the databse ( the env) forever .
I guess that could explain this one as well. Could we close it?
Yea, can close it. I've seen other instances of this happening but in all cases there was a ServiceNetMap saved on the stack.