<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1733651464;
mso-list-type:hybrid;
mso-list-template-ids:14732824 67698713 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">You are right, this is caused by the dnf modularity. For just test purpose, do you know whether can adding “#!/bin/sh echo
</span><span style="color:#1F497D">module_hotfixes=true</span><span style="color:#1F497D"> >> ‘/etc/dnf/dnf.conf’” in the “%pre” section of kickstart cfg,
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I tried but failed to update “/etc/dnf/dnf.conf” on target.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Actually the below commit[0] making the normal repodata to module repo with the upstream “modules.yaml”:
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="http://mirror.centos.org/centos/8.1.1911/AppStream/x86_64/os/repodata/1feb2b0b68761a17ebdf1084518e3f53cec4ec5f317dc1dc7c780a2b041ec3b6-modules.yaml.gz">http://mirror.centos.org/centos/8.1.1911/AppStream/x86_64/os/repodata/1feb2b0b68761a17ebdf1084518e3f53cec4ec5f317dc1dc7c780a2b041ec3b6-modules.yaml.gz</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">this gz file has been deprecated , after updated the above one with the modules.yaml in
<a href="https://vault.centos.org/8.1.1911/AppStream/x86_64/os/repodata/"><span style="color:#1F497D;text-decoration:none">https://vault.centos.org/8.1.1911/AppStream/x86_64/os/repodata/</span></a>,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">the pyton36/python36-devel excluding issue gone, but the same issues for qemu-kvm-ev. I think this can be explained for that “qemu-kvm-ev” is not from vault AppStream, but built locally. This means
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">we have to create module repo for these packages built locally. I found below tools set that can do this:<o:p></o:p></span></p>
<pre><span style="color:black"><a href="https://github.com/rpm-software-management/modulemd-tools">https://github.com/rpm-software-management/modulemd-tools</a></span><span style="color:#1F497D"><o:p></o:p></span></pre>
<p class="MsoNormal"><span style="color:#1F497D">These tools requires that the “libmodulemd” must be upgraded to 2.0 which will cause python “__common_types” issue. I am still working on this.<o:p></o:p></span></p>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<p class="MsoNormal"><span style="color:#1F497D">[0] ===================================================<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">commit 3139368079e66aba19dab4e4ed58665df5f55ca1 (HEAD)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Author: Yong Fu <fuyong@neusoft.com><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Date: Wed Jul 8 11:29:04 2020 +0800<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> CentOS 8: Add modular repository to fix ISO installation problems.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> In the centos8.1 environment,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> "dnf: No available modular metadata for modular package"<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> error occurs in ISO installation.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> Modular repository must contain the modular metadata (modulemd) in<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> the repodata. Excluding the metadata will cause all the modular packages<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> to become standalone packages which could have negative consequences.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> 'modules.yaml' get from<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> http://mirror.centos.org/centos/8.1.1911/AppStream/x86_64/os/repodata/1feb2b0b68761a17ebdf1084518e3f53cec4ec5f317dc1dc7c780a2b041ec3b6-modules.yaml.gz<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> Change-Id: I92a7f1a3c74197d7a9cec1fb5f0cc5fa5e961900<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> Story: 2006729<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> Task: 40294<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> Signed-off-by: Yong Fu <fuyong@neusoft.com><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">diff --git a/build-tools/build-iso b/build-tools/build-iso<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">index b9ad63d..4e8d962 100755<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">--- a/build-tools/build-iso<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">+++ b/build-tools/build-iso<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">@@ -458,7 +458,8 @@ function final_touches {<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> # create the repo<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> \cd $OUTPUT_DIST_DIR/isolinux<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> $CREATEREPO -q -g ../comps.xml .<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">-<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">+ # add modulemd<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">+ modifyrepo_c --mdtype=modules $MY_REPO/build-tools/modularity/modules.yaml ./repodata<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> # build the ISO<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> printf "Building image $OUTPUT_FILE\n"<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> \cd $OUTPUT_DIST_DIR<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">diff --git a/build-tools/modularity/modules.yaml b/build-tools/modularity/modules.yaml<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">=============================================<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Penney, Don <Don.Penney@windriver.com> <br>
<b>Sent:</b> Monday, December 7, 2020 5:27 PM<br>
<b>To:</b> Bai, Haiqing <Haiqing.Bai@windriver.com>; starlingx-discuss@lists.starlingx.io<br>
<b>Subject:</b> RE: [CentOS8] build-pkgs/build-iso completed successfully, but installer reports dependency issues<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">It sounds like this new RHEL8 feature, modularity:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="https://dnf.readthedocs.io/en/latest/modularity.html#hotfix-repositories">https://dnf.readthedocs.io/en/latest/modularity.html#hotfix-repositories</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">It looks like it could be disabled with module_hotfixes=true in the repo config file, but I don’t see any way of passing this to the kickstart repo command.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I expect there will need to be some investigation of the differences in the installation of centos8 vs centos7, maybe look at the stock installation media to look at how the software repositories are setup. The
introduction of modularity and “AppStream” could necessitate some changes in how we setup our ISO and software repositories.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Bai, Haiqing <<a href="mailto:Haiqing.Bai@windriver.com">Haiqing.Bai@windriver.com</a>>
<br>
<b>Sent:</b> Monday, December 7, 2020 3:45 AM<br>
<b>To:</b> <a href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a><br>
<b>Subject:</b> [Starlingx-discuss] [CentOS8] build-pkgs/build-iso completed successfully, but installer reports dependency issues<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi, all:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Is there anyone knows why “build-pkgs” and “build-iso” completed successfully and bootimage.iso created, but the target installer has below errors:
<o:p></o:p></p>
<p class="MsoNormal">(I have checked that “python36” and “python36-devel” are in dist/comps.xml and the type is “mandatory” of group ID “platform-controller”, “platform-controller-worker”, “platform-controller-worker-lowlatency”,<o:p></o:p></p>
<p class="MsoNormal">and the kickstarts cfg files include the related group in “%packages” ). Thanks.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">========================================<o:p></o:p></p>
<p class="MsoNormal">Error<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The following software marked for installation has errors. This is likely
<o:p></o:p></p>
<p class="MsoNormal">caused by an error with<o:p></o:p></p>
<p class="MsoNormal">your installation source.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Problem 1: package patch-alarm-1.0-2.tis.x86_64 requires python3-devel, but<o:p></o:p></p>
<p class="MsoNormal">none of the providers can be installed<o:p></o:p></p>
<p class="MsoNormal"> - conflicting requests<o:p></o:p></p>
<p class="MsoNormal"> - package python36-devel-3.6.8-2.module_el8.1.0+245+c39af44f.x86_64 is<o:p></o:p></p>
<p class="MsoNormal">excluded<o:p></o:p></p>
<p class="MsoNormal">Problem 2: package grubby-8.40-34.el8.tis.1.x86_64 requires python3-devel, but<o:p></o:p></p>
<p class="MsoNormal">none of the providers can be installed<o:p></o:p></p>
<p class="MsoNormal"> - conflicting requests<o:p></o:p></p>
<p class="MsoNormal"> - package python36-devel-3.6.8-2.module_el8.1.0+245+c39af44f.x86_64 is<o:p></o:p></p>
<p class="MsoNormal">excluded<o:p></o:p></p>
<p class="MsoNormal">Problem 3: package cgcs-patch-1.0-28.tis.x86_64 requires python3-devel, but<o:p></o:p></p>
<p class="MsoNormal">none of the providers can be installed<o:p></o:p></p>
<p class="MsoNormal"> - conflicting requests<o:p></o:p></p>
<p class="MsoNormal"> - package python36-devel-3.6.8-2.module_el8.1.0+245+c39af44f.x86_64 is<o:p></o:p></p>
<p class="MsoNormal">excluded<o:p></o:p></p>
<p class="MsoNormal">Problem 4: package worker-utils-1.0-5.tis.x86_64 requires /usr/bin/python3, but<o:p></o:p></p>
<p class="MsoNormal">none of the providers can be installed<o:p></o:p></p>
<p class="MsoNormal"> - package worker-utils-1.0-5.tis.x86_64 requires python3, but none of the<o:p></o:p></p>
<p class="MsoNormal">providers can be installed<o:p></o:p></p>
<p class="MsoNormal"> - conflicting requests<o:p></o:p></p>
<p class="MsoNormal"> - package python36-3.6.8-2.module_el8.1.0+245+c39af44f.x86_64 is excluded<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Press ENTER to continue: <o:p></o:p></p>
</div>
</body>
</html>