Cause: The subscription-manager package version 1.10.7 and higher now incorporates the "content override" feature, which typically requires network communication with a backend server. Certain functions of yum-validator for RHSM systems depend on this network traffic on systems where subscription-manager supports content overrides. yum-validator didn't properly handle situations where subscription-manager calls failed due to network-related issues (timeouts, connection resets, etc.) Consequence: subscription-manager related functions which had previously been virtually guaranteed to work - since they only operated on the local filesystem in older subscription-manager versions - now could raise unhandled exceptions due to network failures. Fix: Routines which depend on subscription-manager are now wrapped in exception-handling blocks, and network errors cause oo-admin-yum-validator to fail with a unique non-zero return value. Result: Scripts which depend on oo-admin-yum-validator can now detect that oo-admin-yum-validator failed due to network errors, and handle the failure appropriately. Users running oo-admin-yum-validator are now presented with a relevant error message instead of a confusing stack trace.