Skip to content

Commit 23e157c

Browse files
Improve section on post-upgrade tasks (theforeman#3907)
* Review post-upgrade tasks * Remove post-upgrade task to migrate container manifest data * Merge post-upgrade tasks into upgrading * Turn post-upgrade tasks into a snippet --------- Co-authored-by: Maximilian Kolb <mail@maximilian-kolb.de>
1 parent c8fb643 commit 23e157c

File tree

6 files changed

+16
-50
lines changed

6 files changed

+16
-50
lines changed

guides/common/modules/proc_performing-post-upgrade-tasks.adoc

Lines changed: 0 additions & 44 deletions
This file was deleted.

guides/common/modules/proc_upgrading-a-disconnected-project-server.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -150,3 +150,5 @@ include::snip_steps-needs-reboot.adoc[]
150150

151151
. In the {ProjectWebUI}, navigate to *Configure* > *Discovery Rules*.
152152
Associate selected organizations and locations with discovery rules.
153+
154+
include::snip_post-upgrade-tasks.adoc[]
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
. Perform the following post-upgrade tasks to ensure your environment is adjusted to any changes applied during the upgrade.
2+
.. If any of the templates you are using were created by cloning the default {Project} templates, verify whether the default templates changed during the upgrade.
3+
If the default templates have changed, consider updating your custom templates as well to reflect these changes.
4+
+
5+
[NOTE]
6+
====
7+
If the default provisioning templates changed during the upgrade and your custom code is executed before or after the provisioning process, you can use custom provisioning snippets to avoid recreating cloned templates.
8+
For more information about configuring custom provisioning snippets, see {ProvisioningDocURL}Creating_Custom_Provisioning_Snippets_provisioning[Creating Custom Provisioning Snippets] in _{ProvisioningDocTitle}_.
9+
====
10+
.. If your {Project} shows any discovered hosts, reboot them:
11+
... In the {ProjectWebUI}, navigate to *Hosts* > *Discovered hosts*.
12+
... Select *Any Organization* to display all discovered hosts.
13+
... Reboot all discovered hosts.

guides/common/modules/snip_upgrading-your-project-server.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -109,3 +109,4 @@ endif::[]
109109
----
110110
endif::[]
111111
include::snip_steps-needs-reboot.adoc[]
112+
include::snip_post-upgrade-tasks.adoc[]

guides/doc-Upgrading_Project/master.adoc

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,9 +33,6 @@ ifdef::satellite[]
3333
include::common/modules/proc_synchronizing-the-new-repositories.adoc[leveloffset=+2]
3434
endif::[]
3535

36-
// Performing Post-Upgrade Tasks
37-
include::common/modules/proc_performing-post-upgrade-tasks.adoc[leveloffset=+2]
38-
3936
ifdef::foreman-el,katello,satellite,orcharhino[]
4037
// Upgrading Smart Proxy Server
4138
include::common/modules/proc_upgrading-smartproxy-server.adoc[leveloffset=+2]

guides/doc-Upgrading_Project_Disconnected/master.adoc

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,9 +30,6 @@ include::common/modules/proc_upgrading-a-disconnected-project-server.adoc[levelo
3030
// Synchronizing the New Repositories
3131
include::common/modules/proc_synchronizing-the-new-repositories.adoc[leveloffset=+2]
3232

33-
// Performing Post-Upgrade Tasks
34-
include::common/modules/proc_performing-post-upgrade-tasks.adoc[leveloffset=+2]
35-
3633
// Upgrading Smart Proxy Server
3734
include::common/modules/proc_upgrading-smartproxy-server.adoc[leveloffset=+2]
3835

0 commit comments

Comments
 (0)