Operations grimoire/Salt - Revision history

Dereckson: /* Troubleshoot */

2024-08-20T20:57:03Z

Troubleshoot

← Older revision		Revision as of 20:57, 20 August 2024
Line 19:		Line 19:
	;Possible cause and solutions		;Possible cause and solutions
	:The master key has expired on the minion: remove it on the minion with <code>rm /etc/salt/pki/minion/minion_master.pub</code>. If you can repro faithfully a scenario with this issue, add more details at https://github.com/saltstack/salt/issues/46923		:The master key has expired on the minion: remove it on the minion with <code>rm /etc/salt/pki/minion/minion_master.pub</code>. If you can repro faithfully a scenario with this issue, add more details at https://github.com/saltstack/salt/issues/46923

			=== Upgrade considerations ===

			Do hotfixes apply correctly, like in {{D\|3392}}?

	== Best practices for configuration ==		== Best practices for configuration ==

Dereckson: /* Enable a service On FreeBSD */

2024-08-10T10:52:13Z

Enable a service On FreeBSD

← Older revision		Revision as of 10:52, 10 August 2024
Line 29:		Line 29:
	A lot of code manually create /etc/rc.conf.d/<service name> and provision it with file.managed.		A lot of code manually create /etc/rc.conf.d/<service name> and provision it with file.managed.

	In [https://devcentral.nasqueron.org/D3413#52413 D3413], a simpler approach is to let Salt create that file automatically and put <service>_enable="YES" on it. ~~That solution should be used when no other~~ service ~~option than~~ _enable ~~has~~ to be set.		In [https://devcentral.nasqueron.org/D3413#52413 D3413], a simpler approach is to let Salt create that file automatically and put <service>_enable="YES" on it.

			Decision tree:

			* Do we only have one configuration file for that service?
			** Yes -> provision a unique file /etc/rc.conf.d/<service name>
			** No -> provision a first file in the service directory: /etc/rc.conf.d/<service name>/<configuration file>

			* Do we have any service configuration in addition to <service>_enable to set in that file?
			** Yes -> provision /etc/rc.conf.d/<service name> through file.managed and a template, e.g. {{Ops file\|roles/prometheus/prometheus/service.sls}}
			** No -> use <code>service.running</code> with <code>enabled: True</code>, e.g. [https://devcentral.nasqueron.org/D3413#52413 D3413]

Dereckson: For a FreeBSD service, Salt is able to create /etc/rc.conf.d/ itself

2024-08-10T10:45:18Z

For a FreeBSD service, Salt is able to create /etc/rc.conf.d/<service name> itself

← Older revision		Revision as of 10:45, 10 August 2024
Line 20:		Line 20:
	:The master key has expired on the minion: remove it on the minion with <code>rm /etc/salt/pki/minion/minion_master.pub</code>. If you can repro faithfully a scenario with this issue, add more details at https://github.com/saltstack/salt/issues/46923		:The master key has expired on the minion: remove it on the minion with <code>rm /etc/salt/pki/minion/minion_master.pub</code>. If you can repro faithfully a scenario with this issue, add more details at https://github.com/saltstack/salt/issues/46923

	== ~~Lessons learned~~ ==		== Best practices for configuration ==

	=== UIDs and GIDs should be unique ===		=== UIDs and GIDs should be unique ===
	UIDs and GIDs are created autoincrementally by the OSes, so it's very easy to have two different usernames using the same uid on two machines. To avoid that, every user.present and group.present Salt state should specify the uid explictly. To avoid to reuse one, document it in {{Ops file\|UIDs}} and {{Ops file\|GIDs}}.		UIDs and GIDs are created autoincrementally by the OSes, so it's very easy to have two different usernames using the same uid on two machines. To avoid that, every user.present and group.present Salt state should specify the uid explictly. To avoid to reuse one, document it in {{Ops file\|UIDs}} and {{Ops file\|GIDs}}.

			=== Enable a service On FreeBSD ===

			A lot of code manually create /etc/rc.conf.d/<service name> and provision it with file.managed.

			In [https://devcentral.nasqueron.org/D3413#52413 D3413], a simpler approach is to let Salt create that file automatically and put <service>_enable="YES" on it. That solution should be used when no other service option than _enable has to be set.

Dereckson at 19:04, 11 June 2024

2024-06-11T19:04:32Z

← Older revision		Revision as of 19:04, 11 June 2024
Line 4:		Line 4:
	=== Master ===		=== Master ===
	<pre>		<pre>
	master.pub: 67:8b:e6:b2:7b:73:5b:f1:50:f4:48:38:9a:4c:1c:31:e1:b7:6e:eb:9f:47:98:40:1f:53:29:9e:86:bb:83:38		master.pub: 67:8b:e6:b2:7b:73:5b:f1:50:f4:48:38:9a:4c:1c:31:e1:b7:6e:eb:9f:47:98:40:1f:53:29:9e:86:bb:83:38
	</pre>		</pre>

Line 19:		Line 19:
	;Possible cause and solutions		;Possible cause and solutions
	:The master key has expired on the minion: remove it on the minion with <code>rm /etc/salt/pki/minion/minion_master.pub</code>. If you can repro faithfully a scenario with this issue, add more details at https://github.com/saltstack/salt/issues/46923		:The master key has expired on the minion: remove it on the minion with <code>rm /etc/salt/pki/minion/minion_master.pub</code>. If you can repro faithfully a scenario with this issue, add more details at https://github.com/saltstack/salt/issues/46923

			== Lessons learned ==

			=== UIDs and GIDs should be unique ===
			UIDs and GIDs are created autoincrementally by the OSes, so it's very easy to have two different usernames using the same uid on two machines. To avoid that, every user.present and group.present Salt state should specify the uid explictly. To avoid to reuse one, document it in {{Ops file\|UIDs}} and {{Ops file\|GIDs}}.

Dereckson: /* Master */ Update fingerprint

2024-01-12T23:20:55Z

Master: Update fingerprint

← Older revision		Revision as of 23:20, 12 January 2024
Line 4:		Line 4:
	=== Master ===		=== Master ===
	<pre>		<pre>
	master.pub: da:70:12:f8:a5:c9:55:f3:b2:d2:1f:84:16:df:32:09:7d:a1:60:3a:b4:4c:2d:34:64:b3:f6:72:3b:c2:e1:4f		master.pub: 67:8b:e6:b2:7b:73:5b:f1:50:f4:48:38:9a:4c:1c:31:e1:b7:6e:eb:9f:47:98:40:1f:53:29:9e:86:bb:83:38
	</pre>		</pre>

	This fingerprint should be used by minions in the `master_finger` value in configuration file.		This fingerprint should be used by minions in the `master_finger` value in configuration file.

			It can be updated running <code>salt-call --local key.finger</code> from Complector.

	== Troubleshoot ==		== Troubleshoot ==

Dereckson: Troubleshoot

2018-11-10T16:38:35Z

Troubleshoot

← Older revision		Revision as of 16:38, 10 November 2018
Line 7:		Line 7:
	</pre>		</pre>

	This fingerprint should be used by ~~minionns~~ in the `master_finger` value in configuration file.		This fingerprint should be used by minions in the `master_finger` value in configuration file.

			== Troubleshoot ==
			=== Request timeout ===
			;Symptoms on master
			:The minion doesn't reply with job result
			;Symptoms on minion
			:When running through <code>salt-call</code>, output shows <code>SaltReqTimeoutError, retrying. (1/7)</code>.
			;Possible cause and solutions
			:The master key has expired on the minion: remove it on the minion with <code>rm /etc/salt/pki/minion/minion_master.pub</code>. If you can repro faithfully a scenario with this issue, add more details at https://github.com/saltstack/salt/issues/46923

Dereckson: /* Master */

2018-09-15T18:21:21Z

Master

← Older revision		Revision as of 18:21, 15 September 2018
Line 6:		Line 6:
	master.pub: da:70:12:f8:a5:c9:55:f3:b2:d2:1f:84:16:df:32:09:7d:a1:60:3a:b4:4c:2d:34:64:b3:f6:72:3b:c2:e1:4f		master.pub: da:70:12:f8:a5:c9:55:f3:b2:d2:1f:84:16:df:32:09:7d:a1:60:3a:b4:4c:2d:34:64:b3:f6:72:3b:c2:e1:4f
	</pre>		</pre>

			This fingerprint should be used by minionns in the `master_finger` value in configuration file.

Dereckson: To avoid confusion, only note the public fingerprint

2018-09-15T18:20:55Z

To avoid confusion, only note the public fingerprint

← Older revision		Revision as of 18:20, 15 September 2018
Line 4:		Line 4:
	=== Master ===		=== Master ===
	<pre>		<pre>
	~~master.pem: 43:e5:55:1a:52:85:59:43:f5:05:e6:56:94:73:a6:ba:85:13:e3:32:33:7e:68:b4:ef:a9:e0:99:9e:d7:1f:06~~
	master.pub: da:70:12:f8:a5:c9:55:f3:b2:d2:1f:84:16:df:32:09:7d:a1:60:3a:b4:4c:2d:34:64:b3:f6:72:3b:c2:e1:4f		master.pub: da:70:12:f8:a5:c9:55:f3:b2:d2:1f:84:16:df:32:09:7d:a1:60:3a:b4:4c:2d:34:64:b3:f6:72:3b:c2:e1:4f
	</pre>		</pre>

Dereckson: Created page with "Salt is used for deployment. Configuration can be found in the rOPS repository. == Keys == === Master ===

 master.pem:  43:e5:55:1a:52:85:59:43:f5:05:e6:56:94:73:a6:ba:8..."

2018-09-15T18:20:19Z

Created page with "Salt is used for deployment. Configuration can be found in the rOPS repository. == Keys == === Master === <pre> master.pem: 43:e5:55:1a:52:85:59:43:f5:05:e6:56:94:73:a6:ba:8..."

New page

Salt is used for deployment. Configuration can be found in the rOPS repository.

== Keys ==
=== Master ===
<pre>
master.pem: 43:e5:55:1a:52:85:59:43:f5:05:e6:56:94:73:a6:ba:85:13:e3:32:33:7e:68:b4:ef:a9:e0:99:9e:d7:1f:06
master.pub: da:70:12:f8:a5:c9:55:f3:b2:d2:1f:84:16:df:32:09:7d:a1:60:3a:b4:4c:2d:34:64:b3:f6:72:3b:c2:e1:4f
</pre>