Insert client's IP address into an Autoinstallation Variable

[kurzandras]

Hi all,

Just a quick question: I would like to upgrade a client from sles12sp5 to sles15sp3 and I noticed that during the autoinstallation the client tries to get its IP address from DHCP. I do not want this to happen, I would like to use the same IP what the client had before. Is there a simple solution for this? I thought that I would add an IP address variable to the Autoinstallation Variables which I could reference from the autoyast profile using bootproto static, but im not sure how to get the client's IP address from the UI dynamically. Is there a solution for this? Or any other solutions for this issue?

Thank you in advance!

[aaannz]

Hi,

check Linuxrc. This needs to be added as a kernel command line options for the autoinstallation profile.

[aaannz]

Before continuing with migrating other systems you will need to adapt that autoyast profile to contain the rest of used modules

• sle-module-web-scripting15-sp3-updates-x86_64
• sle-module-legacy15-sp3-updates-x86_64
• sle-module-live-patching15-sp3-updates-x86_64
• sle-module-packagehub-subpackages15-sp3-updates-x86_64

On this system already migrated, I can't say for sure. I would try to alter channels manually and then zypper dup on the system.
It is really strange that installer was fine with keeping SLE12 modules without having sles-release for SLE12. I would expected some error message during migration.

[kurzandras]

This is only a test system where I am trying to implement the process of an upgrade, so I will revert this host for the next test-run anyway. I did not see any errors during the installation, it was quite smooth.

Im not sure if the profile is completely fine, I just tried to compose a working initial version:

<?xml version="1.0"?>
<!DOCTYPE profile>
<profile xmlns="http://www.suse.com/1.0/yast2ns"
    xmlns:config="http://www.suse.com/1.0/configns">
    <general>
    $SNIPPET('spacewalk/sles_no_signature_checks')
        <mode>
            <confirm config:type="boolean">false</confirm>
        </mode>
    </general>
    <add-on>
      <add_on_products config:type="list">
        <listentry>
          <ask_on_error config:type="boolean">true</ask_on_error>
          <media_url>http://uyuni01.test/ks/dist/child/sle-product-sles15-sp3-updates-x86_64/$distrotree</media_url>
          <name>SLE-Product-SLES15-SP3-Updates for x86_64</name>
          <product>SUSE Linux Enterprise Server 15 SP3 x86_64</product>
          <product_dir>/</product_dir>
        </listentry>
        <listentry>
          <ask_on_error config:type="boolean">true</ask_on_error>
          <media_url>http://uyuni01.test/ks/dist/child/sles15-sp3-uyuni-client-x86_64/$distrotree</media_url>
          <name>Uyuni Client Tools for SLES15 SP3 x86_64</name>
          <product>Uyuni Client Tools 15 x86_64</product>
          <product_dir>/</product_dir>
        </listentry>
        <listentry>
          <ask_on_error config:type="boolean">true</ask_on_error>
          <media_url>http://uyuni01.test/ks/dist/child/sle-module-basesystem15-sp3-pool-x86_64/$distrotree</media_url>
          <name>SLE-Module-Basesystem15-SP3-Pool for x86_64</name>
          <product>Basesystem Module 15 SP3 x86_64</product>
          <product_dir>/</product_dir>
        </listentry>
        <listentry>
          <ask_on_error config:type="boolean">true</ask_on_error>
          <media_url>http://uyuni01.test/ks/dist/child/sle-module-basesystem15-sp3-updates-x86_64/$distrotree</media_url>
          <name>SLE-Module-Basesystem15-SP3-Updates for x86_64</name>
          <product>Basesystem Module 15 SP3 x86_64</product>
          <product_dir>/</product_dir>
        </listentry>
        <listentry>
          <ask_on_error config:type="boolean">true</ask_on_error>
          <media_url>http://uyuni01.test/ks/dist/child/sle-module-server-applications15-sp3-pool-x86_64/$distrotree</media_url>
          <name>SLE-Module-Server-Applications15-SP3-Pool for x86_64</name>
          <product>Server Applications Module 15 SP3 x86_64</product>
          <product_dir>/</product_dir>
        </listentry>
        <listentry>
          <ask_on_error config:type="boolean">true</ask_on_error>
          <media_url>http://uyuni01.test/ks/dist/child/sle-module-server-applications15-sp3-updates-x86_64/$distrotree</media_url>
          <name>SLE-Module-Server-Applications15-SP3-Updates for x86_64</name>
          <product>Server Applications Module 15 SP3 x86_64</product>
          <product_dir>/</product_dir>
        </listentry>
      </add_on_products>
    </add-on>
    <networking>
        <keep_install_network config:type="boolean">true</keep_install_network>
    </networking>
    <upgrade>
        <stop_on_solver_conflict config:type="boolean">true</stop_on_solver_conflict>
    </upgrade>
    <suse_register>
        <do_registration config:type="boolean">false</do_registration>
    </suse_register>
    <backup>
        <sysconfig config:type="boolean">true</sysconfig>
        <modified config:type="boolean">true</modified>
        <remove_old config:type="boolean">false</remove_old>
    </backup>
    <software>
        <install_recommended config:type="boolean">true</install_recommended>
        <products config:type="list">
            <product>SLES</product>
        </products>
    </software>
    <scripts>
        <!-- This script is designed to ensure the certificate is present for any 'https' repositories -->
        <pre-scripts config:type="list">
            <script>
                <rerun config:type="boolean">false</rerun>
                <debug config:type="boolean">false</debug>
                <feedback config:type="boolean">false</feedback>
                <filename>01_import_cert</filename>
                <interpreter>shell</interpreter>
                <location/>
                <notification>Importing SUMA CA certificate</notification>
                <source><![CDATA[
/usr/bin/wget -nv -r -nd --no-check-certificate https://$redhat_management_server/pub/RHN-ORG-TRUSTED-SSL-CERT
mv RHN-ORG-TRUSTED-SSL-CERT /etc/pki/trust/anchors/
/usr/sbin/update-ca-certificates
     ]]>                </source>
            </script>
        </pre-scripts>
        <init-scripts config:type="list">
        $SNIPPET('spacewalk/minion_script')
        </init-scripts>
    </scripts>
</profile>

Do you see any problems here?

[kurzandras]

One additional question: The documentation states that we need to create an activation key for the upgrade process, but it seems that it is not really being used at all. How/where the new activation key is linked to the upgrade process?

[aaannz]

I misted your previous question, sorry. The profile looks fine, just is missing those extra channels, so copy

        <listentry>
          <ask_on_error config:type="boolean">true</ask_on_error>
          <media_url>http://uyuni01.test/ks/dist/child/sle-module-server-applications15-sp3-updates-x86_64/$distrotree</media_url>
          <name>SLE-Module-Server-Applications15-SP3-Updates for x86_64</name>
          <product>Server Applications Module 15 SP3 x86_64</product>
          <product_dir>/</product_dir>
        </listentry>

and add those missing channels from my previous comment. Should fix that leftover SLE12 repositories.

About the activation key, it's in the minion_script snippet, see https://github.com/uyuni-project/uyuni/blob/master/java/conf/cobbler/snippets/minion_script#L22

[kurzandras]

Thank you @aaannz for your answer! I have successfully upgraded a system from SLES12 to SLES15, and afterwards I have installed some patches for SLES15 too. Everything seems to be fine except one thing: Uyuni states that "The system requires a reboot", which does not disappear after reboot. Moreover when I click on "Apply Highstate" the task will get stuck in picked-up state:

Hardware list refresh too:

Other things like package list update and patching are working fine. I could not see any issues in the server / client logs. How does Uyuni know which system needs to be rebooted? Could you please point me to the right direction regarding troubleshooting?

Thank you very much in advance!