So when you have puppet-classify installed and you upgrade from PE 2016 -> PE 2017 you can expect a failure to occur because the API or token auth with classification has changed which causes the catalog to not compile on the puppetmaster. This then causes the remaining changes of the PE upgrade to not finish (code-manager) which is required to get some additional services running. We were running node-manager 0.3.0 and puppet-classify-0.1.7 when we found this issue. We ended up disabling node-classification. However, since code manager stopped working we had to manually modify our puppet code on the master (old school way) and remove the node_manager stuff so we can get a successful puppet run and finish upgrading the puppet master.
Code manager fails because they Puppet mades some service name changes in the bootstrap.cfg file.
Once the puppet run was complete, code-manager starting working again.
I don't know where the problem lies, but hoping that this information will help someone in the future.
I am guessing using the latest code might have solved this issue before hand.
So when you have puppet-classify installed and you upgrade from PE 2016 -> PE 2017 you can expect a failure to occur because the API or token auth with classification has changed which causes the catalog to not compile on the puppetmaster. This then causes the remaining changes of the PE upgrade to not finish (code-manager) which is required to get some additional services running. We were running
node-manager 0.3.0andpuppet-classify-0.1.7when we found this issue. We ended up disabling node-classification. However, since code manager stopped working we had to manually modify our puppet code on the master (old school way) and remove the node_manager stuff so we can get a successful puppet run and finish upgrading the puppet master.Code manager fails because they Puppet mades some service name changes in the bootstrap.cfg file.
Once the puppet run was complete, code-manager starting working again.
I don't know where the problem lies, but hoping that this information will help someone in the future.
I am guessing using the latest code might have solved this issue before hand.