Saltstack [SOLVED]: How to seamlessly rename a minion?

Saltstack [SOLVED]: How to seamlessly rename a minion?

Home Forums Automation Tools Saltstack Tutorials Saltstack [SOLVED]: How to seamlessly rename a minion?

Tagged: 

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #237123

    Cloudy Point
    Keymaster

    QuestionQuestion

    I am considering to move to salt (currently using ansible) to manage a set of standalone IoT devices (Raspberry Pi in practical terms).

    The devices would be installed with a generic image, to which I would add on top the installation of salt (client side) as well as a configuration file pointing to salt-master, which is going to serve state files to be consumed by the minions.

    The state files include an HTTP query for a name, which is then applied to the device (as its hostname). The obvious problem is that at that stage the minion has already registered with salt-master under the previous (generic) name.

    How to handle such a situation? Specifically: how to propagate the new hostname to salt-master? (just changing the hostname and rebooting did not help, I assume the hostname is bundled, on the server, with the ID of the minion).

    The more general question would be whether salt is the right product for such a situatiuon (where setting the state of the minion changes its name, among others)

    #237124

    Cloudy Point
    Keymaster

    Accepted AnswerAnswer

    Your Minion ID is based on the hostname during the installation. When you change the hostname after you installed the salt-minion, the Minion ID wil not change.

    The Minion ID is specified in /etc/salt/minion_id.
    When you change the Minion ID:

    • The Minion will identify itself with the new ID to the Master and stops listening to the old ID.
    • The Master will detect the new Minion Id as a new Minion and it shows a new key in Unaccepted Keys.
    • After accepting the key on the Master you will be able to use the Minion with the new key only. The old key is still accepted on the Master but doesn’t work anymore.

    I can come up with two solutions for your situation:

    1. Use salt-ssh to provision your minions. The Master will connect to your Raspberry PI using SSH. It will setup the correct hostname, install and configure salt-minion. After this is finished, your minion will connect to the master with the correct ID. But this requires the Master to know when and where a minion is available…
    2. You mentioned the state where the hostname is set. Change the Minion ID and restart the minion service in the same state. This will change the Minion ID but you need to accept the new key afterwards. Note that the minion will never report a state as successfully finished when you restart the salt-minion service in it.

    Source: https://stackoverflow.com/questions/47648183/how-to-seamlessly-rename-a-minion
    Author: Gijs Brandsma
    Creative Commons License
    This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.