Verify that the master is permanently offline.
If the master comes back online during promotion, your agents can get confused trying to connect to two active masters.
On the replica, as the root user, run puppet infrastructure promote replica
Promotion can take up to the amount of time it took to install PE initially. Don’t make code or classification changes during or after promotion.
When promotion is complete, update any systems or settings that refer to the old master, such as PE client tool configurations, Code Manager hooks, Razor brokers, and CNAME records.
Deploy updated configuration to nodes by running Puppet or waiting for the next scheduled run.
(Optional) Provision a new replica in order to maintain high availability.
Note: Agent configuration must be updated before provisioning a new replica. If you re-use your old master’s node name for the new replica, agents with outdated configuration might use the new replica as a master before it’s fully provisioned.
Refer to https://www.edureka.co/community/55971/puppet-error-while-signing-the-certificates
This addresses a similar query like ...READ MORE
Please refer the below link for setting ...READ MORE
I have a small doubt regarding puppet, ...READ MORE
Hey @Janice, this is pretty simple. Create ...READ MORE
Hey @nmentityvibes, you seem to be using ...READ MORE
Consider this - In 'extended' Git-Flow, (Git-Multi-Flow, ...READ MORE
It can work if you try to put ...READ MORE
When you use docker-compose down, all the ...READ MORE
This could probably be because you are ...READ MORE
You could do this by executing the ...READ MORE
Already have an account? Sign in.