SUSE Manager/NewFeatures2.1/PackageLock

From MicroFocusInternationalWiki
Revision as of 11:35, 11 November 2014 by Kwk (Talk | contribs) (Created page with "== Package Lock == === Description === The "Package Lock" feature allows users prevent installation or upgrades of the software on the machine they need. Please note that t...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Package Lock

Description

The "Package Lock" feature allows users prevent installation or upgrades of the software on the machine they need.

Please note that this feature does not operate in a real time, but performs via scheduling requests to lock or unlock particular packages with some little time gap. This time can be even more increased by selecting date/time on the locking page.

Requirements

One or more client machines:

  • using zypper as a Package Manager (Red Hat Enterprise Linux clients are currently not supported);
  • with zypp-plugin-spacewalk package installed, version 0.9.6 or greater.

Locking a package

In order to lock a package, do the following steps:

  1. Navigate to the managed system
  2. Follow "Software/Packages/Lock" tabs.

On this page will appear the list of all the packages that can be installed on the system. Packages which are already locked have a small lock icon beside their name.

Select the packages you want to lock and then press the "Request Lock" button. In case locking should happen later or another date, please request the appropriate date/time above the "Request Lock" button.

Unlocking a package

In order to unlock a package, please do the following:

  1. Navigate to the managed system
  2. Follow the "Software/Packages/Lock" tabs.

On this page will appear the list of all the packages that can be installed on the system. Packages which are already locked have a small lock icon beside their name.

Select the packages you want to unlock and then press the "Request Unlock" button. In case unlocking should happen later or another date, please request the appropriate date/time above the "Request Unlock" button.

FAQ

Q: What happens on an attempt installing locked package?

A: An attempt installing locked package using SUSE Manager will not be successful. Such attempt will be marked as failed event by SUSE Manager, and an explanation of the error will be available as event details.

Please note that the installing locked package manually, i.e. directly on the client machine, will also fail. Installing packages manually directly on the client machine is highly discouraged and should be considered as bad practice.

Q: How locked package gets upgraded?

A: Any locked package cannot be upgraded or removed. Beware Zypper bug that ignores locked package removal, therefore make sure your client machine has latest Zypper available to the current OS installed.

Q: What happens if some locked package is a dependency of an unlocked package I am trying to install?

A: Since any package can be installed only by satisfaction its dependencies, in this case an unlocked package is indirectly locked by the dependency package, and therefore will not be installed.

Q: What happens if some locked package is a dependency of an unlocked package I am trying to install, and the locked dependency is already installed on my system?

A: If the locked dependency satisfies the conditions of new package, i.e. requiring no upgrade, then the package will be installed successfully. However, if the locked dependency also needs to be upgraded, then the package will not be installed.