{"id":39759,"date":"2025-07-30T11:10:18","date_gmt":"2025-07-30T09:10:18","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=39759"},"modified":"2025-07-30T11:10:20","modified_gmt":"2025-07-30T09:10:20","slug":"patching-suse-multi-linux-manager","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/","title":{"rendered":"Patching SUSE Multi Linux Manager"},"content":{"rendered":"\n

In the last post about SUSE Multi Linux Manager we had a look at how you can schedule OpenSCAP reports using the API<\/a>. In this post we’ll look into something very basic: How can you patch the server components of SUSE Multi Linux Manager. We speak about components because you need to patch the host (which is a SLE Micro<\/a> in this case) and the container hosting the application.<\/p>\n\n\n\n

Looking at the host operating system we can see this is a SLE Micro 5.5:<\/p>\n\n\n

\nsuma:~ $ cat \/etc\/os-release \nNAME="SLE Micro"\nVERSION="5.5"\nVERSION_ID="5.5"\nPRETTY_NAME="SUSE Linux Enterprise Micro 5.5"\nID="sle-micro"\nID_LIKE="suse"\nANSI_COLOR="0;32"\nCPE_NAME="cpe:\/o:suse:sle-micro:5.5"\n<\/pre><\/div>\n\n\n
As this comes with a read only root file system we cannot directly use zypper<\/a> to patch the system. The tool to use in this case is transactional-update<\/a>. This still uses zypper in the background, but the updates are installed into a new Btrfs<\/a> snapshot. Using this approach the running system is not touched at all and the updates only become available when the system is rebooted into the new snapshot (which happens automatically when the system is rebooted). If something is wrong with the new snapshot, the system can be booted from the old snapshot and the system is back to what it was before patching.<\/p>\n\n\n\n
Before we patch the host system let’s have a look at the snapshots we currently have available:<\/p>\n\n\n
\nsuma:~ $ snapper list\n # | Type   | Pre # | Date                             | User | Used Space | Cleanup | Description           | Userdata     \n---+--------+-------+----------------------------------+------+------------+---------+-----------------------+--------------\n0  | single |       |                                  | root |            |         | current               |              \n1  | single |       | Fri 08 Mar 2024 10:45:41 AM CET  | root |   1.30 GiB | number  | first root filesystem | important=yes\n2  | single |       | Mon 07 Jul 2025 12:18:08 PM CEST | root |   1.51 MiB | number  | Snapshot Update of #1 | important=yes\n3  | single |       | Mon 07 Jul 2025 12:30:01 PM CEST | root |   1.02 MiB | number  | Snapshot Update of #2 | important=yes\n4  | single |       | Tue 08 Jul 2025 05:33:39 AM CEST | root |  39.78 MiB | number  | Snapshot Update of #3 | important=yes\n5  | single |       | Wed 16 Jul 2025 09:25:23 AM CEST | root |  45.07 MiB |         | Snapshot Update of #4 |              \n6* | single |       | Wed 23 Jul 2025 04:13:09 PM CEST | root |  58.62 MiB |         | Snapshot Update of #5 |         \n<\/pre><\/div>\n\n\n
Let’s patch and compare what we’ll have afterwards:<\/p>\n\n\n
\nsuma:~ $ zypper ref\nWarning: The gpg key signing file 'repomd.xml' has expired.\n  Repository:       SLE-Micro-5.5-Updates\n  Key Fingerprint:  FEAB 5025 39D8 46DB 2C09 61CA 70AF 9E81 39DB 7C82\n  Key Name:         SuSE Package Signing Key <build@suse.de>\n  Key Algorithm:    RSA 2048\n  Key Created:      Mon 21 Sep 2020 10:21:47 AM CEST\n  Key Expires:      Fri 20 Sep 2024 10:21:47 AM CEST (EXPIRED)\n  Rpm Name:         gpg-pubkey-39db7c82-5f68629b\nRetrieving repository 'SLE-Micro-5.5-Updates' metadata ..............................................................................................................[done]\nBuilding repository 'SLE-Micro-5.5-Updates' cache ...................................................................................................................[done]\nWarning: The gpg key signing file 'repomd.xml' has expired.\n  Repository:       SUSE-Manager-Server-5.0-Updates\n  Key Fingerprint:  FEAB 5025 39D8 46DB 2C09 61CA 70AF 9E81 39DB 7C82\n  Key Name:         SuSE Package Signing Key <build@suse.de>\n  Key Algorithm:    RSA 2048\n  Key Created:      Mon 21 Sep 2020 10:21:47 AM CEST\n  Key Expires:      Fri 20 Sep 2024 10:21:47 AM CEST (EXPIRED)\n  Rpm Name:         gpg-pubkey-39db7c82-5f68629b\nRetrieving repository 'SUSE-Manager-Server-5.0-Updates' metadata ....................................................................................................[done]\nBuilding repository 'SUSE-Manager-Server-5.0-Updates' cache .........................................................................................................[done]\nRepository 'SLE-Micro-5.5-Pool' is up to date.                                                                                                                             \nRepository 'SUSE-Manager-Server-5.0-Pool' is up to date.                                                                                                                   \nAll repositories have been refreshed.\n\nsuma:~ $ transactional-update \nChecking for newer version.\ntransactional-update 4.1.9 started\nOptions: \nSeparate \/var detected.\n2025-07-30 09:42:32 tukit 4.1.9 started\n2025-07-30 09:42:32 Options: -c6 open \n2025-07-30 09:42:33 Using snapshot 6 as base for new snapshot 7.\n2025-07-30 09:42:33 \/var\/lib\/overlay\/6\/etc\n2025-07-30 09:42:33 Syncing \/etc of previous snapshot 5 as base into new snapshot "\/.snapshots\/7\/snapshot"\n2025-07-30 09:42:33 SELinux is enabled.\nID: 7\n2025-07-30 09:42:36 Transaction completed.\nCalling zypper up\n2025-07-30 09:42:38 tukit 4.1.9 started\n2025-07-30 09:42:38 Options: callext 7 zypper -R {} up -y --auto-agree-with-product-licenses \n2025-07-30 09:42:39 Executing `zypper -R \/tmp\/transactional-update-JsIr01 up -y --auto-agree-with-product-licenses`:\nRefreshing service 'SUSE_Linux_Enterprise_Micro_5.5_x86_64'.\nRefreshing service 'SUSE_Manager_Server_Extension_5.0_x86_64'.\nLoading repository data...\nReading installed packages...\n\nThe following 21 packages are going to be upgraded:\n  boost-license1_66_0 libboost_system1_66_0 libboost_thread1_66_0 libpolkit-agent-1-0 libpolkit-gobject-1-0 mgradm mgradm-bash-completion mgrctl mgrctl-bash-completion polkit python3-pyparsing python3-pytz python3-PyYAML python3-requests python3-salt python3-simplejson python3-urllib3 salt salt-minion salt-transactional-update uyuni-storage-setup-server\n\n21 packages to upgrade.\n\nPackage download size:    16.8 MiB\n\nPackage install size change:\n              |      71.4 MiB  required by packages that will be installed\n   654.0 KiB  |  -   70.8 MiB  released by packages that will be removed\n\nBackend:  classic_rpmtrans\nContinue? [y\/n\/v\/...? shows all options] (y): y\n\n...\n2025-07-30 09:44:40 New default snapshot is #7 (\/.snapshots\/7\/snapshot).\n2025-07-30 09:44:40 Transaction completed.\n\nPlease reboot your machine to activate the changes and avoid data loss.\nNew default snapshot is #7 (\/.snapshots\/7\/snapshot).\ntransactional-update finished\n<\/pre><\/div>\n\n\n
As noted above we must reboot the system for the updates to become active. Before we do that, let’s again have a look at the snapshots:<\/p>\n\n\n
\nsuma:~ $ snapper list\n # | Type   | Pre # | Date                             | User | Used Space | Cleanup | Description           | Userdata     \n---+--------+-------+----------------------------------+------+------------+---------+-----------------------+--------------\n0  | single |       |                                  | root |            |         | current               |              \n1  | single |       | Fri 08 Mar 2024 10:45:41 AM CET  | root |   1.30 GiB | number  | first root filesystem | important=yes\n2  | single |       | Mon 07 Jul 2025 12:18:08 PM CEST | root |   1.51 MiB | number  | Snapshot Update of #1 | important=yes\n3  | single |       | Mon 07 Jul 2025 12:30:01 PM CEST | root |   1.02 MiB | number  | Snapshot Update of #2 | important=yes\n4  | single |       | Tue 08 Jul 2025 05:33:39 AM CEST | root |  39.78 MiB | number  | Snapshot Update of #3 | important=yes\n5  | single |       | Wed 16 Jul 2025 09:25:23 AM CEST | root |  45.07 MiB |         | Snapshot Update of #4 |              \n6- | single |       | Wed 23 Jul 2025 04:13:09 PM CEST | root |   4.11 MiB |         | Snapshot Update of #5 |              \n7+ | single |       | Wed 30 Jul 2025 09:42:32 AM CEST | root |  88.39 MiB |         | Snapshot Update of #6 |      \n<\/pre><\/div>\n\n\n
We got a new snapshot (number 7) which is not yet active, let’s reboot and check again:<\/p>\n\n\n
\nsuma:~ $ reboot\n...\nsuma:~ $ snapper list\n # | Type   | Pre # | Date                             | User | Used Space | Cleanup | Description           | Userdata     \n---+--------+-------+----------------------------------+------+------------+---------+-----------------------+--------------\n0  | single |       |                                  | root |            |         | current               |              \n1  | single |       | Fri 08 Mar 2024 10:45:41 AM CET  | root |   1.30 GiB | number  | first root filesystem | important=yes\n2  | single |       | Mon 07 Jul 2025 12:18:08 PM CEST | root |   1.51 MiB | number  | Snapshot Update of #1 | important=yes\n3  | single |       | Mon 07 Jul 2025 12:30:01 PM CEST | root |   1.02 MiB | number  | Snapshot Update of #2 | important=yes\n4  | single |       | Tue 08 Jul 2025 05:33:39 AM CEST | root |  39.78 MiB | number  | Snapshot Update of #3 | important=yes\n5  | single |       | Wed 16 Jul 2025 09:25:23 AM CEST | root |  45.07 MiB |         | Snapshot Update of #4 |              \n6  | single |       | Wed 23 Jul 2025 04:13:09 PM CEST | root |   4.11 MiB |         | Snapshot Update of #5 |              \n7* | single |       | Wed 30 Jul 2025 09:42:32 AM CEST | root |  88.39 MiB |         | Snapshot Update of #6 |            \n<\/pre><\/div>\n\n\n
The new snapshot became active and we’re fully patched on the host system.<\/p>\n\n\n\n
Now that the host system is fully patched, we can proceed with patching the SUSE Multi Linux Manager application. Before we do that, let’s check what we currently have:<\/p>\n\n\n
\nsuma:~ $ mgradm inspect\n10:40AM INF Welcome to mgradm\n10:40AM INF Executing command: inspect\n10:40AM INF Computed image name is registry.suse.com\/suse\/manager\/5.0\/x86_64\/server:5.0.4.1\n10:40AM INF Ensure image registry.suse.com\/suse\/manager\/5.0\/x86_64\/server:5.0.4.1 is available\nWARN[0002] Path "\/etc\/SUSEConnect" from "\/etc\/containers\/mounts.conf" doesn't exist, skipping \n10:40AM INF \n{\n  "CurrentPgVersion": "16",\n  "ImagePgVersion": "16",\n  "DBUser": "spacewalk",\n  "DBPassword": "<REDACTED>",\n  "DBName": "susemanager",\n  "DBPort": 5432,\n  "UyuniRelease": "",\n  "SuseManagerRelease": "5.0.4.1",\n  "Fqdn": "suma.dwe.local"\n}\n<\/pre><\/div>\n\n\n
The currently running version is “5.0.4.1”. Patching is quite simple as this just updates the container:<\/p>\n\n\n
\nsuma:~ $ mgradm upgrade podman\n10:41AM INF Welcome to mgradm\n10:41AM INF Use of this software implies acceptance of the End User License Agreement.\n10:41AM INF Executing command: podman\n...\n10:41AM INF No changes requested for hub. Keep 0 replicas.\n10:41AM INF Computed image name is registry.suse.com\/suse\/manager\/5.0\/x86_64\/server-hub-xmlrpc-api:5.0.5\n10:41AM INF Ensure image registry.suse.com\/suse\/manager\/5.0\/x86_64\/server-hub-xmlrpc-api:5.0.5 is available\n10:42AM INF Cannot find RPM image for registry.suse.com\/suse\/manager\/5.0\/x86_64\/server-hub-xmlrpc-api:5.0.5\n<\/pre><\/div>\n\n\n
Checking the version again:<\/p>\n\n\n
\nsuma:~ $ mgradm inspect\n10:36AM INF Welcome to mgradm\n10:36AM INF Use of this software implies acceptance of the End User License Agreement.\n10:36AM INF Executing command: inspect\n10:36AM INF Computed image name is registry.suse.com\/suse\/manager\/5.0\/x86_64\/server:5.0.5\n10:36AM INF Ensure image registry.suse.com\/suse\/manager\/5.0\/x86_64\/server:5.0.5 is available\n10:36AM ??? time="2025-07-30T10:36:20+02:00" level=warning msg="Path \\"\/etc\/SUSEConnect\\" from \\"\/etc\/containers\/mounts.conf\\" doesn't exist, skipping"\n10:36AM INF \n{\n  "CurrentPgVersion": "16",\n  "ImagePgVersion": "16",\n  "DBUser": "spacewalk",\n  "DBPassword": "<REDACTED>",\n  "DBName": "susemanager",\n  "DBPort": 5432,\n  "UyuniRelease": "",\n  "SuseManagerRelease": "5.0.5",\n  "Fqdn": "suma.dwe.local"\n}\n<\/pre><\/div>\n\n\n
Now we are on version “5.0.5” and we’re done with our patching for the server part. Clients also should be upgraded, especially the Salt<\/a> client as SUSE Multi Linux Manager uses Salt to manage the clients. You can either do that manually by using the package manager of the distributions you’re managing or you can do that from the WebUI:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
That’s it, not hard to do and an easy process to follow.<\/p>\n","protected":false},"excerpt":{"rendered":"
In the last post about SUSE Multi Linux Manager we had a look at how you can schedule OpenSCAP reports using the API. In this post we’ll look into something very basic: How can you patch the server components of SUSE Multi Linux Manager. We speak about components because you need to patch the host […]<\/p>\n","protected":false},"author":29,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[42,3391],"tags":[73,3648,2222,309],"type_dbi":[],"class_list":["post-39759","post","type-post","status-publish","format-standard","hentry","category-operating-systems","category-suse","tag-linux","tag-multi-linux","tag-suma","tag-suse"],"acf":[],"yoast_head":"\nPatching SUSE Multi Linux Manager - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Patching SUSE Multi Linux Manager\" \/>\n<meta property=\"og:description\" content=\"In the last post about SUSE Multi Linux Manager we had a look at how you can schedule OpenSCAP reports using the API. In this post we’ll look into something very basic: How can you patch the server components of SUSE Multi Linux Manager. We speak about components because you need to patch the host […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2025-07-30T09:10:18+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-07-30T09:10:20+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2025\/07\/Screenshot_20250730_104222.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1488\" \/>\n\t<meta property=\"og:image:height\" content=\"769\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Daniel Westermann\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@westermanndanie\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Daniel Westermann\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"2 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/\"},\"author\":{\"name\":\"Daniel Westermann\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"headline\":\"Patching SUSE Multi Linux Manager\",\"datePublished\":\"2025-07-30T09:10:18+00:00\",\"dateModified\":\"2025-07-30T09:10:20+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/\"},\"wordCount\":405,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2025\/07\/Screenshot_20250730_104222-1024x529.png\",\"keywords\":[\"Linux\",\"Multi Linux\",\"SUMA\",\"SuSE\"],\"articleSection\":[\"Operating systems\",\"SUSE\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/\",\"name\":\"Patching SUSE Multi Linux Manager - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2025\/07\/Screenshot_20250730_104222-1024x529.png\",\"datePublished\":\"2025-07-30T09:10:18+00:00\",\"dateModified\":\"2025-07-30T09:10:20+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2025\/07\/Screenshot_20250730_104222.png\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2025\/07\/Screenshot_20250730_104222.png\",\"width\":1488,\"height\":769},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Patching SUSE Multi Linux Manager\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\",\"name\":\"Daniel Westermann\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"caption\":\"Daniel Westermann\"},\"description\":\"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.\",\"sameAs\":[\"https:\/\/x.com\/westermanndanie\"],\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/daniel-westermann\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Patching SUSE Multi Linux Manager - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/","og_locale":"en_US","og_type":"article","og_title":"Patching SUSE Multi Linux Manager","og_description":"In the last post about SUSE Multi Linux Manager we had a look at how you can schedule OpenSCAP reports using the API. In this post we’ll look into something very basic: How can you patch the server components of SUSE Multi Linux Manager. We speak about components because you need to patch the host […]","og_url":"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/","og_site_name":"dbi Blog","article_published_time":"2025-07-30T09:10:18+00:00","article_modified_time":"2025-07-30T09:10:20+00:00","og_image":[{"width":1488,"height":769,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2025\/07\/Screenshot_20250730_104222.png","type":"image\/png"}],"author":"Daniel Westermann","twitter_card":"summary_large_image","twitter_creator":"@westermanndanie","twitter_misc":{"Written by":"Daniel Westermann","Est. reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/"},"author":{"name":"Daniel Westermann","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"headline":"Patching SUSE Multi Linux Manager","datePublished":"2025-07-30T09:10:18+00:00","dateModified":"2025-07-30T09:10:20+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/"},"wordCount":405,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2025\/07\/Screenshot_20250730_104222-1024x529.png","keywords":["Linux","Multi Linux","SUMA","SuSE"],"articleSection":["Operating systems","SUSE"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/","url":"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/","name":"Patching SUSE Multi Linux Manager - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2025\/07\/Screenshot_20250730_104222-1024x529.png","datePublished":"2025-07-30T09:10:18+00:00","dateModified":"2025-07-30T09:10:20+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2025\/07\/Screenshot_20250730_104222.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2025\/07\/Screenshot_20250730_104222.png","width":1488,"height":769},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/patching-suse-multi-linux-manager\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Patching SUSE Multi Linux Manager"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66","name":"Daniel Westermann","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","caption":"Daniel Westermann"},"description":"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.","sameAs":["https:\/\/x.com\/westermanndanie"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/daniel-westermann\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/39759","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/29"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=39759"}],"version-history":[{"count":11,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/39759\/revisions"}],"predecessor-version":[{"id":39771,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/39759\/revisions\/39771"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=39759"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=39759"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=39759"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=39759"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}