Skip to main content
Migration Notice
We're migrating documentation from the old portal into this one. Some things may look a little different or out of place in the meantime — we know, and we're working to get it right. If something's unclear or doesn't look right, let us know.

OpenSUSE OS Upgrade from 15.5 to 15.6

Introduction​

This guide provides step-by-step instructions for upgrading OpenSUSE from version 15.5 to 15.6 on Eyeglass and ECA (Eyeglass Cluster Appliance) virtual machines. The upgrade process includes pre-upgrade preparation, package management, and post-upgrade validation steps to ensure your system remains operational after the upgrade.

Important

This upgrade process applies to both Eyeglass and ECA VMs. Some steps are specific to each platform and are clearly marked throughout this guide.

note

The operating system is the customer's responsibility. Assisted operating system upgrades are not covered under the support contract. The supported upgrade approach is to deploy a new OVA and restore the configuration to the new operating system. Any assisted upgrade to an existing OS is provided as is and without support.

note

A VM-level snapshot must be taken before starting this procedure. In the event of a failed OS upgrade, the only recovery option is to revert to the snapshot. Support cannot recover a failed OS upgrade and will require the snapshot to be reverted, after which the supported OVA upgrade method must be scheduled.

Supported Versions​

This procedure supports the following upgrade path:

  • Source Version: OpenSUSE Leap 15.5
  • Target Version: OpenSUSE Leap 15.6
  • Supported Platforms: Eyeglass Appliance, ECA (Eyeglass Cluster Appliance)
Upgrade Path Limitation

This procedure is specifically designed for upgrading from OpenSUSE Leap 15.5 to 15.6 only. Do not use this procedure for other version combinations.

Prerequisites​

Before starting the upgrade process, ensure you have:

  • Root or sudo access to the VM
  • VM-level snapshot of the appliance (mandatory)
  • Internet connection for downloading packages
  • Sufficient disk space for the upgrade process
  • Current configuration backup (recommended)
Best Practice

Document your current system configuration before starting the upgrade process. This includes network settings, service configurations, and any custom modifications.

Pre-Upgrade Preparation​

Step 1: Take VM Snapshot​

Before proceeding with any upgrade steps, take a VM-level snapshot of your appliance:

  1. Use your hypervisor management interface (vCenter, Hyper-V Manager, etc.)
  2. Create a named snapshot (e.g., "Pre-OS-Upgrade-15.5-to-15.6")
  3. Verify the snapshot was created successfully
Critical Step

This snapshot is your only recovery option if the upgrade fails. Do not proceed without a valid snapshot.

Step 2: Log in to the VM​

Log in to the Eyeglass VM via SSH as the admin user:

ssh admin@<eyeglass-ip-address>

Switch to root user:

sudo -s

Step 3: Check Package Locks​

Check for locked packages that may interfere with the upgrade:

zypper ll

If you see the libzypp package locked, note the lock ID for the next step.

Step 4: Remove Package Locks​

Remove the lock on the libzypp package:

zypper rl <lock-id>

Replace <lock-id> with the ID shown in the previous step (e.g., 1, 2, 4).

Example:

zypper rl 1

Step 5: Refresh Package Repositories​

Refresh the package repository cache:

zypper refresh

Step 6: Update Existing Packages​

Update all currently installed packages:

zypper update

When prompted to continue, answer with y:

Continue? [y/n/v/...? shows all options] (y): y

If the system detects file conflicts, answer yes to continue:

File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content.
Continue? [yes/no] (no): yes
note

The update process may take several minutes depending on the number of packages requiring updates.

Step 7: Stop Services Before Reboot​

Stop the SCA service:

systemctl stop sca

Verify the service is stopped:

systemctl status sca

Step 8: Reboot After Initial Update​

Reboot the appliance to apply the initial updates:

reboot

Wait for the system to fully restart before proceeding.

Step 9: Reconnect and Elevate Privileges​

After the reboot completes, reconnect to the VM:

ssh admin@<eyeglass-ip-address>
sudo -s

Step 10: Backup Sudoers File​

Create a backup of the sudoers file before the upgrade:

cp /etc/sudoers /etc/sudoers.bak
Critical

This backup is essential for maintaining administrative access after the upgrade. The distribution upgrade may overwrite the sudoers file.

Updating Repository Configuration​

Step 11: Check Repository Variables​

Verify if your Leap repositories are using the $releasever variable:

grep baseurl /etc/zypp/repos.d/*.repo

You should see output with $releasever in the repository URLs:

/etc/zypp/repos.d/repo-backports-update.repo:baseurl=http://download.opensuse.org/update/leap/$releasever/backports/
/etc/zypp/repos.d/repo-debug-non-oss.repo:baseurl=http://download.opensuse.org/debug/distribution/leap/$releasever/repo/non-oss/

Step 12: Update Repository URLs (If Needed)​

If the repositories are hard-coded with version 15.5, update them to use the variable:

sed -i 's/15.5/${releasever}/g' /etc/zypp/repos.d/*.repo

Verify the changes:

grep baseurl /etc/zypp/repos.d/*.repo

Performing the Distribution Upgrade​

Step 13: Refresh Repositories with New Release Version​

Refresh the package cache using the new release version:

zypper --releasever=15.6 refresh

Step 14: Execute Distribution Upgrade​

Perform the full distribution upgrade to OpenSUSE Leap 15.6:

zypper --releasever=15.6 dup
note

The distribution upgrade command (dup) will upgrade all packages to the versions available in OpenSUSE Leap 15.6 repositories.

Step 15: Resolve Dependency Conflicts​

During the upgrade, you may encounter dependency problems. Choose the solution that involves deinstalling older packages.

Example dependency conflict:

Problem: the installed libsnmp40-5.9.3-150300.15.8.1.x86_64 requires 'snmp-mibs >= 5.9.3', but this requirement cannot be provided
  Solution 1: deinstallation of libsnmp30-5.7.3-10.12.1.x86_64
  Solution 2: deinstallation of libsnmp40-5.9.3-150300.15.8.1.x86_64
  Solution 3: keep obsolete libsnmp30-5.7.3-10.12.1.x86_64
  Solution 4: break libsnmp40-5.9.3-150300.15.8.1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c): 1

Select option 1 to deinstall the older package version.

Step 16: Confirm Upgrade Continuation​

The system will prompt you to continue with the upgrade:

217 packages to upgrade, 27 to downgrade, 45 new, 1 to reinstall, 4 to remove.
Overall download size: 748.9 MiB. Already cached: 0 B. After the operation, additional 660.4 MiB will be used.

Note: System reboot required.
Continue? [y/n/v/...? shows all options] (y): y

Answer y to proceed.

Step 17: Resolve File Conflicts​

When file conflicts are detected, answer yes to continue:

Detected 7 file conflicts:

File /etc/lighttpd/conf.d/magnet.conf from install of
lighttpd-mod_magnet-1.4.69-bp155.1.6.x86_64 (Main Repository) conflicts with file from package
eyeglass_deps-2.5.11-23140.lp15.4.x86_64 (@System)

File /etc/sudoers from install of
sudo-1.9.12p1-150500.5.1.x86_64 (Main Repository) conflicts with file from package
eyeglass_deps-2.5.11-23140.lp15.4.x86_64 (@System)

File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content.

Continue? [yes/no] (no): yes
note

File conflicts are expected during the distribution upgrade. The backup of /etc/sudoers created in Step 10 will be restored after the reboot.

Step 18: Wait for Upgrade Completion​

The distribution upgrade will proceed with downloading and installing packages. This process may take 15-30 minutes depending on your internet connection speed.

tip

Do not interrupt the upgrade process. Ensure your SSH session remains active throughout the upgrade.

Post-Upgrade Configuration​

Step 19: Restore Sudoers File​

Before rebooting, restore the original sudoers file:

cp /etc/sudoers.bak /etc/sudoers
Critical Step

Failure to restore the sudoers file before reboot may result in loss of administrative access. Verify the restore was successful:

ls -l /etc/sudoers

Step 20: Stop Services Before Reboot​

Stop the SCA service:

systemctl stop sca

Step 21: Reboot the Appliance​

Reboot the appliance to complete the upgrade:

reboot

Wait for the system to fully restart.

Post-Upgrade Validation​

Step 22: Reconnect and Verify OS Version​

After the reboot, reconnect to the VM and verify the OS version:

ssh admin@<eyeglass-ip-address>

Check the OS version:

cat /etc/os-release

You should see output indicating OpenSUSE Leap 15.6:

NAME="openSUSE Leap"
VERSION="15.6"
ID="opensuse-leap"
ID_LIKE="suse opensuse"
VERSION_ID="15.6"
PRETTY_NAME="openSUSE Leap 15.6"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.6"

Step 23: Elevate Privileges​

Switch to root user:

sudo -s

Eyeglass-Specific Post-Upgrade Steps​

Eyeglass Only

The following steps apply only to Eyeglass appliances. Skip this section if you are upgrading ECA nodes.

Remove outdated symbolic links for document generator components:

unlink /opt/superna/document_generator/startOrientDb.sh
unlink /opt/superna/document_generator/databaseScriptSca.sh
unlink /opt/superna/document_generator/eyeglassAnalyzer
unlink /opt/superna/document_generator/dbmanager
unlink /opt/superna/document_generator/orientDBManager
note

If any of these symbolic links do not exist, you will see an error message. This is expected and can be ignored.

Step 25: Install Required Development Libraries​

Install the necessary development libraries for OpenSUSE Leap 15.6:

zypper install glibc-devel libxcrypt-devel linux-glibc-devel

When prompted to continue, answer y:

The following 3 NEW packages are going to be installed:
  glibc-devel libxcrypt-devel linux-glibc-devel

3 new packages to install.
Overall download size: 1.8 MiB. Already cached: 0 B. After the operation, additional 7.5 MiB will be used.

Continue? [y/n/v/...? shows all options] (y): y

Step 26: Download Eyeglass Upgrade Installer​

Download the Eyeglass upgrade installer file compatible with OpenSUSE Leap 15.6:

note

Contact Superna Support to obtain the correct Eyeglass upgrade installer file for OpenSUSE Leap 15.6.

Transfer the installer file to the Eyeglass VM using SCP or your preferred file transfer method.

Step 27: Make Installer Executable​

Change the permissions of the upgrade installer file:

chmod 755 <eyeglass-installer-filename>

Replace <eyeglass-installer-filename> with the actual filename.

Step 28: Execute Eyeglass Upgrade​

Run the Eyeglass upgrade installer:

./<eyeglass-installer-filename>

Follow the on-screen prompts to complete the Eyeglass software upgrade.

tip

The installer will upgrade Eyeglass components to versions compatible with OpenSUSE Leap 15.6. This process may take 10-15 minutes.

Step 29: Verify Eyeglass Web UI​

After the installer completes, verify that the Eyeglass Web UI is accessible:

  1. Open a web browser
  2. Navigate to https://<eyeglass-ip-address>
  3. Log in with your administrative credentials
  4. Verify that the dashboard loads successfully

ECA-Specific Considerations​

ECA Only

The following information applies specifically to ECA nodes.

Important Notes for ECA Upgrades​

  • All nodes must be upgraded: Each ECA node in the cluster must be upgraded individually using the same procedure
  • Cluster state: Ensure the cluster remains in the down state throughout the upgrade process across all nodes
  • Service dependencies: For Search & Recover deployments, verify that search indices are backed up before performing the upgrade to avoid data loss
Search & Recover Data

If you are using Search & Recover functionality, ensure that you have backed up the search index data before upgrading the operating system. The upgrade process may result in index corruption if not properly prepared.

Post-Upgrade ECA Cluster Validation​

After upgrading all ECA nodes, bring the cluster back online:

ecactl cluster up

Verify the cluster status:

ecactl cluster status

All nodes should report as healthy and active in the cluster.

Troubleshooting​

Package Manager Issues​

If you encounter errors with zypper during the upgrade:

  1. Verify internet connectivity: ping -c 4 download.opensuse.org
  2. Clear zypper cache: zypper clean --all
  3. Refresh repositories: zypper --releasever=15.6 refresh
  4. Retry the distribution upgrade: zypper --releasever=15.6 dup

Dependency Resolution Failures​

If the distribution upgrade fails due to unresolvable dependencies:

  1. Review the dependency conflict messages carefully
  2. Choose solutions that deinstall older package versions (typically Solution 1)
  3. Avoid options that break dependencies or keep obsolete packages
  4. If stuck, document the error message and contact Superna Support

Service Startup Failures After Upgrade​

If services fail to start after the upgrade:

  1. Check service status: systemctl status <service-name>
  2. View detailed logs: journalctl -u <service-name> -n 50
  3. Verify configuration files in /etc/ are intact
  4. Check for .rpmsave or .rpmnew files that indicate configuration conflicts

Loss of Administrative Access​

If you cannot log in via SSH or sudo after the upgrade:

  1. Access the VM console via your hypervisor management interface
  2. Log in at the console
  3. Verify the sudoers file: cat /etc/sudoers
  4. If corrupted, restore from backup: cp /etc/sudoers.bak /etc/sudoers
  5. Verify permissions: chmod 440 /etc/sudoers

Rollback to Previous Version​

If the upgrade fails and the system is non-functional:

  1. Access your hypervisor management interface
  2. Power off the VM
  3. Revert to the snapshot created in Step 1
  4. Power on the VM
  5. Verify system functionality
  6. Contact Superna Support to schedule an OVA-based upgrade
Snapshot Recovery

If you need to revert to the snapshot, all changes made after the snapshot was taken will be lost. This includes the OS upgrade and any configuration changes.

Summary​

This guide covered the complete process of upgrading OpenSUSE from 15.5 to 15.6 on Eyeglass and ECA VMs, including:

  • Pre-upgrade preparation with mandatory VM snapshot
  • Package lock removal and repository configuration
  • Distribution upgrade using zypper
  • Post-upgrade sudoers file restoration
  • Eyeglass-specific installer execution
  • ECA-specific cluster management considerations
  • Validation steps to confirm successful upgrade
Post-Upgrade

After completing the upgrade, monitor your system for 24-48 hours to ensure all services are functioning correctly and no unexpected issues arise.