Skip to content

Commit 2ce907e

Browse files
Republish metadata via Hammer CLI (#4307)
* Rename modules about republishing metadata This patch prepares the splitting the modules into WebUI and CLI procedures. * Add modules to republish metadata via CLI Tested on Foreman 3.14/Katello 4.16 * Add introduction to republishing CV metadata Based on "proc_recovering-a-corrupted-repository.adoc".
1 parent 9781d58 commit 2ce907e

5 files changed

+75
-7
lines changed

guides/common/assembly_importing-content.adoc

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,9 +68,13 @@ include::modules/proc_recovering-corrupted-content-on-a-smart-proxy-server-by-us
6868

6969
include::modules/proc_recovering-corrupted-content-on-a-smart-proxy-server-by-using-cli.adoc[leveloffset=+1]
7070

71-
include::modules/proc_republishing-repository-metadata.adoc[leveloffset=+1]
71+
include::modules/proc_republishing-repository-metadata-by-using-web-ui.adoc[leveloffset=+1]
7272

73-
include::modules/proc_republishing-content-view-metadata.adoc[leveloffset=+1]
73+
include::modules/proc_republishing-repository-metadata-by-using-cli.adoc[leveloffset=+1]
74+
75+
include::modules/proc_republishing-content-view-metadata-by-using-web-ui.adoc[leveloffset=+1]
76+
77+
include::modules/proc_republishing-content-view-metadata-by-using-cli.adoc[leveloffset=+1]
7478

7579
include::modules/proc_adding-an-http-proxy.adoc[leveloffset=+1]
7680

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
:_mod-docs-content-type: PROCEDURE
2+
3+
[id="republishing-content-view-metadata-by-using-cli"]
4+
= Republishing content view metadata by using CLI
5+
6+
Republish metadata of content view versions if hosts report package checksum mismatches.
7+
You can use Hammer CLI to republish metadata of content view versions.
8+
9+
.Procedure
10+
* Republish metadata for your content view version:
11+
+
12+
[options="nowrap", subs="+quotes,attributes"]
13+
----
14+
$ hammer content-view version verify-checksum --id _My_Content_View_Version_ID_
15+
----
16+
17+
.Verification
18+
* Verify that the task completed successfully:
19+
+
20+
[options="nowrap", subs="+quotes,attributes"]
21+
----
22+
$ hammer task list --search "Verify checksum of repositories in"
23+
----

guides/common/modules/proc_republishing-content-view-metadata.adoc renamed to guides/common/modules/proc_republishing-content-view-metadata-by-using-web-ui.adoc

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,10 @@
11
:_mod-docs-content-type: PROCEDURE
22

3-
[id="Republishing_Content_View_Metadata_{context}"]
4-
= Republishing content view metadata
3+
[id="republishing-content-view-metadata-by-using-web-ui"]
4+
= Republishing content view metadata by using {ProjectWebUI}
55

6-
Use this procedure to republish content view metadata.
6+
Republish metadata of content view versions if hosts report package checksum mismatches.
7+
You can use {ProjectWebUI} to republish content view metadata.
78

89
.Procedure
910
. In the {ProjectWebUI}, navigate to *Content* > *Lifecycle* > *Content Views*.
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
:_mod-docs-content-type: PROCEDURE
2+
3+
[id="republishing-repository-metadata-by-using-cli"]
4+
= Republishing repository metadata by using CLI
5+
6+
You can republish repository metadata when a repository distribution does not have the content that should be distributed based on the contents of the repository.
7+
8+
Use this procedure with caution.
9+
{Team} recommends a complete repository sync or publishing a new content view version to repair broken metadata.
10+
11+
.Prerequisites
12+
* Ensure that the mirroring policy of your repository is not set to *Complete Mirroring*:
13+
+
14+
[options="nowrap", subs="+quotes,attributes"]
15+
----
16+
$ hammer repository info \
17+
--fields "Name,Mirroring policy" \
18+
--name "_My_Repository_Name_" \
19+
--organization-id _My_Organization_ID_ \
20+
--product "_My_Product_Name_"
21+
----
22+
23+
.Procedure
24+
* Republish metadata for your repository:
25+
+
26+
[options="nowrap", subs="+quotes,attributes"]
27+
----
28+
$ hammer repository verify-checksum \
29+
--name "_My_Repository_Name_" \
30+
--organization-id _My_Organization_ID_ \
31+
--product "_My_Product_Name_"
32+
----
33+
34+
.Verification
35+
* Verify that the task completed successfully:
36+
+
37+
[options="nowrap", subs="+quotes,attributes"]
38+
----
39+
$ hammer task list --search "Metadata generate repository"
40+
----

guides/common/modules/proc_republishing-repository-metadata.adoc renamed to guides/common/modules/proc_republishing-repository-metadata-by-using-web-ui.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
:_mod-docs-content-type: PROCEDURE
22

3-
[id="Republishing_Repository_Metadata_{context}"]
4-
= Republishing repository metadata
3+
[id="republishing-repository-metadata-by-using-web-ui"]
4+
= Republishing repository metadata by using {ProjectWebUI}
55

66
You can republish repository metadata when a repository distribution does not have the content that should be distributed based on the contents of the repository.
77

0 commit comments

Comments
 (0)