The following are the upgrade scenarios with failure conditions after the removal of ‘$server puppet’ from the ‘/etc/hosts’.
1. SM is upgraded but contrail images are not upgraded
Problem:
SM: Provision followed by reimage will fail as SM on reimage won’t put the entry $server puppet in /etc/hosts but the provision logic expects that
SMLITE: Provision will fail as preconfig.py will not put the $server puppet entry in the /etc/hosts but puppet code still expects that entry
Solution: Add and provision the latest contrail image
2. SM is the old one but contrail images are upgraded
Problem:
SM: Cannot reimage the nodes using SM as it will insert the ‘$server puppet’ in /etc/hosts. Reimage followed by provision will fail.
SMLITE: smlite cannot be used to provision the images as it will update the /etc/hosts with the $server puppet entry but the puppet files will have the latest one without that reference. Openstack provision will fail
The following are the upgrade scenarios with failure conditions after the removal of ‘$server puppet’ from the ‘/etc/hosts’.
1. SM is upgraded but contrail images are not upgraded
Problem:
SM: Provision followed by reimage will fail as SM on reimage won’t put the entry $server puppet in /etc/hosts but the provision logic expects that
SMLITE: Provision will fail as preconfig.py will not put the $server puppet entry in the /etc/hosts but puppet code still expects that entry
Solution: Add and provision the latest contrail image
2. SM is the old one but contrail images are upgraded
Problem:
Openstack provision will fail
SM: Cannot reimage the nodes using SM as it will insert the ‘$server puppet’ in /etc/hosts. Reimage followed by provision will fail.
SMLITE: smlite cannot be used to provision the images as it will update the /etc/hosts with the $server puppet entry but the puppet files will have the latest one without that reference.
Solution: Upgrade the SM