Data Domain: Informational warning messages during BoostFS upgrade and lockbox migration

During a BoostFS RPM upgrade, one or more of the following messages may be displayed:

Message 1 warning: DDBoostFS-.rpm: Header V4 RSA/SHA256 Signature, key ID : NOKEY

Message 2 warning: /opt/emc/boostfs/etc/boostfs.conf created as /opt/emc/boostfs/etc/boostfs.conf.rpmnew

Message 3 sudo: unable to load /usr/libexec/sudo/sudoers.so: /usr/lib64/libldap.so.2: undefined symbol: EVP_md2, version OPENSSL_3.0.0 sudo: fatal error, unable to load plugins

Message 4 Lockbox files are already migrated or are in Lockbox 4.x format for /opt/emc/boostfs/lockbox/boostfs.lockbox

The upgrade completes successfully, the installed BoostFS version reflects the upgraded release, and BoostFS operations continue to function normally.

Message 1: RPM GPG NOKEY Warning

The RPM package signing key has not been imported into the local RPM database. This prevents RPM from validating the package signature but does not prevent installation or upgrade completion.

Message 2: boostfs.conf.rpmnew Created

RPM detected that the existing boostfs.conf file contains local modifications. To preserve customer configuration settings, RPM installs the updated configuration as boostfs.conf.rpmnew instead of overwriting the active configuration file.

Message 3: sudo/OpenSSL Compatibility Warning

The message is generated by the operating system's sudo component while attempting to load a library dependency that is not compatible with the OpenSSL 3.x environment. This is a system-level issue and is not related to BoostFS functionality or the BoostFS upgrade process.

Message 4: Lockbox Migration Informational Message

The Lockbox file has already been migrated to the newer Lockbox format or is already using the Lockbox 4.x format. No additional migration action is required.

No action is required for the BoostFS upgrade itself when these messages are observed and the upgrade completes successfully.

• For the RPM GPG warning, optionally import the appropriate package signing key to eliminate future NOKEY messages.
• For the .rpmnew file, compare the contents with the active boostfs.conf file and merge any required settings. The .rpmnew file may be deleted after review.
• For the sudo/OpenSSL warning, investigate and remediate the operating system library compatibility issue if sudo functionality is affected.
• For the Lockbox message, no action is required because it is informational only.

If BoostFS reports the expected upgraded version and mount operations, read/write access, and Lockbox authentication function successfully after the upgrade, these messages can be safely disregarded as they do not indicate a DDBoostFS upgrade failure.