Drop --now after restarting gssproxy

[aneta-petrova]

https://issues.redhat.com/browse/SAT-26357 requests clarifying a procedure step to restart and enable gssproxy.service.

Doing a bit of archeology, I found the commit that introduced --now to that step: a4be0ab It seems that in case of this particular step, asking users to restart && enable (without --now) might help prevent some raised eyebrows.

• I am okay with my commits getting squashed when you merge this PR.
• I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

• Foreman 3.11/Katello 4.13
• Foreman 3.10/Katello 4.12
• Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9)
• Foreman 3.8/Katello 4.10
• Foreman 3.7/Katello 4.9 (Satellite 6.14)
• Foreman 3.6/Katello 4.8
• Foreman 3.5/Katello 4.7 (Satellite 6.13; orcharhino 6.6/6.7)
• We do not accept PRs for Foreman older than 3.5.

[github-actions]

The PR preview for 20870fb is available at theforeman-foreman-documentation-preview-pr-3162.surge.sh

The following output files are affected by this PR:

• Installing_Server/index-foreman-deb.html
• Installing_Server/index-foreman-el.html
• Installing_Server/index-katello.html
• Installing_Server/index-orcharhino.html
• Installing_Server/index-satellite.html

show diff

show diff as HTML

[aneta-petrova]

@ekohl Can you please review? You authored a4be0ab (see the PR description for an explanation).

[Lennonka]

My two cents.
The two commands duplicate an action, that's why they raise eyebrows probably.
Suggesting an alternative edit.

[aneta-petrova]

My two cents. The two commands duplicate an action, that's why they raise eyebrows probably. Suggesting an alternative edit.

Ah, let's wait for #3149 first, then. Because that introduces changing /etc/gssproxy/http.keytab. Restarting the service will be required. But not just yet, it seems.

[aneta-petrova]

My two cents. The two commands duplicate an action, that's why they raise eyebrows probably. Suggesting an alternative edit.

Ah, let's wait for #3149 first, then. Because that introduces changing /etc/gssproxy/http.keytab. Restarting the service will be required. But not just yet, it seems.

#3149 is nowhere near merging but based on the comments above, that doesn't have to be a blocker. Clarifying the starting/restarting/enabling of gssproxy.service was requested by an external user in https://issues.redhat.com/browse/SAT-26357 so it would be nice to be able to get the fix in.

[aneta-petrova]

Merged to "master" and cherry-picked:

ded4218..9d86041 3.11 -> 3.11
85611ea..3160b68 3.10 -> 3.10
bbd2967..76338f5 3.9 -> 3.9
fdabd10..46e9412 3.8 -> 3.8
d995cc3..583a699 3.7 -> 3.7
008b6ae..8f6139c 3.6 -> 3.6
838bd14..227475c 3.5 -> 3.5