SLBA-2016:2613-1This update fixes the following bugs: * Due to a bug in the lvm2-2.02.166-1.el package, released in Scientific Linux 7.3, the library was incompatible with previous versions of Scientific Linux 7. The incompatibility could cause device monitoring to fail and become lost during an upgrade. As a consequence, device failures could go unnoticed (RAID) or out-of-space conditions were not handled properly (thin-p). This update fixes the incompatibility and the logical volume monitoring now works as expected. * Due to a regression in the lvm2-2.02.166-1.el package, released in Scientific Linux 7.3, the "lvconvert --repair" command could not be run properly on cache logical volumes. As a consequence, the "Cannot convert internal LV" error message was returned. This bug has been fixed and the command now works as expected.Scientific LinuxScientific Linux 7device-mapper-devel-1.02.135-1.el7_3.1.i686.rpmea8af2522fe22d2e3112bf7ca8b52d81f4db330fc90b6ce96638d21e58998a86device-mapper-event-libs-1.02.135-1.el7_3.1.x86_64.rpm20d42327dbf13afa031fdc9ff841d0bdd4a3da7a47b7397c115f5c252d54afaflvm2-python-libs-2.02.166-1.el7_3.1.x86_64.rpmbaae5438bf8902ac78da460fec74c6946b397356f8e10a6c3dec93892f98f88fdevice-mapper-1.02.135-1.el7_3.1.x86_64.rpm4822cc0cb24a5bf12f428da82e4ac427e1f054da49f05cb1606315f8f24963e9lvm2-lockd-2.02.166-1.el7_3.1.x86_64.rpmdd1824578d1ef2c46a1943255ef8c9a37c872c575ba905060a66ff01b20b7b0clvm2-libs-2.02.166-1.el7_3.1.i686.rpmce7ebedd4152a3c65908ea01db0bd546c375d3e65bcedf8ab54a88e00b6f7b05device-mapper-libs-1.02.135-1.el7_3.1.x86_64.rpm10280bede85deb5516427704af748fc448613b540b6c4f78fd34e285dea706badevice-mapper-event-devel-1.02.135-1.el7_3.1.i686.rpm5cbeb0dfbd0cdd1c4b576efc5a5d60d92d697a335e0614086e5dbc2fe0b9cc2fdevice-mapper-event-1.02.135-1.el7_3.1.x86_64.rpmf4557f2adf9b5cdfe5ebc410f6d1f770169c159605517d79f21c081502b85efalvm2-cluster-2.02.166-1.el7_3.1.x86_64.rpm6cd04e13433c9d9550c3c3c03b330a78450019f408b527bacb4999c65624a07ecmirror-standalone-2.02.166-1.el7_3.1.x86_64.rpma5ba72adeffc314aee647a32af433735e1fa26dc91bbc545da2dd7648c0ffbd7device-mapper-devel-1.02.135-1.el7_3.1.x86_64.rpm3021cacf9515815d59447ed9db6d641c2ef89a2a5148c31ba119ba7e3739f2ebdevice-mapper-event-libs-1.02.135-1.el7_3.1.i686.rpm3eb0ae0d55e566de4cbe7391333faeb155af5697b14563ca6dfcaaf1dc26fab5lvm2-cluster-standalone-2.02.166-1.el7_3.1.x86_64.rpmeccd644c0ff4f0668453598364e399fe280995046ce6a26ccfb61c915bb8bb4blvm2-2.02.166-1.el7_3.1.x86_64.rpm67a44b40bd9cb5efdd1d1b63eade97a70db34e2daa97b1719b6cb224472e3ba5device-mapper-event-devel-1.02.135-1.el7_3.1.x86_64.rpm882eac3579d2dfbae05767e4ee752182eaacb7cb55e13fb998abeb0cd9f8f503lvm2-libs-2.02.166-1.el7_3.1.x86_64.rpm84263ad23b5dfac1a3622f577736d842c14023ea3c960fa144fc47d3f1dddc24device-mapper-libs-1.02.135-1.el7_3.1.i686.rpm7da110b40d6b006dae9ea61a903aace0fcf1c7ba8338b0bf466445bde9a36402cmirror-2.02.166-1.el7_3.1.x86_64.rpm47a5fc79a819a018cebd19e1c6d01b1d02ce1526a3091f2c4259d69b4682f237lvm2-devel-2.02.166-1.el7_3.1.i686.rpm619e47066f45539b9593bbc3dd6cb5bf04eea496291a1eef7740a7839a1f1220lvm2-sysvinit-2.02.166-1.el7_3.1.x86_64.rpmcd8bd59929c11c5793cb86c570b4fa0ec387dba09c26390e878aa8e246629577lvm2-devel-2.02.166-1.el7_3.1.x86_64.rpm59eea3b39ba502620527a6fc3ca05e6e68aaf64f273a99d829d1640524350c5cSLBA-2016:2698-1This update fixes the following bugs:Scientific LinuxtrueScientific Linux 7systemd-219-30.el7_3.6.x86_64.rpm89bac6564157175ff5ac159f09af3074d94e89f709687ff1e1d96fa0b4377911systemd-journal-gateway-219-30.el7_3.6.x86_64.rpm493e5e34e4ab25af664efeb9d21291da181968bab82260770ce05459860ba98flibgudev1-devel-219-30.el7_3.6.i686.rpm6ad3c50be8ea8aacfcae41359c12d4b0eee80574fbd9fe03246e7b2c5da2d919systemd-libs-219-30.el7_3.6.i686.rpm2a605ab633a767f6232b33317d3a5f1f63b23ee72389db382f187199b6df4505systemd-resolved-219-30.el7_3.6.i686.rpm462bb3828e933a4da333052b02114cc19f55990c5a7b4f23d22b4054b46652d2systemd-resolved-219-30.el7_3.6.x86_64.rpmf01069e3458c121b10f31fb280b88bfea7d3ccd035ce4a63cc8329f0e04bc6f7systemd-devel-219-30.el7_3.6.x86_64.rpmd06cdd547e33c67d8b0a17c6e370d101a78176a2fa037d08cdb68e2bf8899e9fsystemd-libs-219-30.el7_3.6.x86_64.rpm5a10519fa74b1c8df1c01700073690cedec60530f31e8c35a57f4b4fb0b4ed25systemd-devel-219-30.el7_3.6.i686.rpm31fd34afc04149d8a6a7413f596fca9bceaab87b4ea61e9ffe67acb7f8e33858libgudev1-219-30.el7_3.6.x86_64.rpm8ce1fc8496843cc3d9ae752e7037b1e5557ab5a2ecc8c256d88b13b857ce912dsystemd-sysv-219-30.el7_3.6.x86_64.rpmc77e4881e9e5e1cf9c09d2cea24309abbb10d94a9c7718b061358b9e179a0ed0libgudev1-219-30.el7_3.6.i686.rpm778cd6abc87c581778f3171c162849f0042b4b0786704722f7e10be2326ec376systemd-python-219-30.el7_3.6.x86_64.rpmb8e5df1163ae1fc28aca15ec40301c760551cfe9b808afd3bc09548bbc942663libgudev1-devel-219-30.el7_3.6.x86_64.rpm7b9a0ba02abbc29c5771db777a0dfbbdb0c9d7dfdde7fb5df59b4d9ca2a7cbdcsystemd-networkd-219-30.el7_3.6.x86_64.rpm8a53217c4b00d035d84fec2c27ea9027792d09b8f08ef63314225799f4cc4621SLBA-2016:2858-1This update fixes the following bug: * Due to a bug in trap signal handling, bash in some cases terminated unexpectedly after performing the longjmp() function from the wait_sigint_handler() function to the wait_builtin() function. This update fixes the bug and thus prevents the described crashes from occurring.Scientific LinuxScientific Linux 7bash-4.2.46-21.el7_3.x86_64.rpmb56b52b3bb2411d8f04fd349fe65a388abd88dac2303692954752b2dc370c67ebash-doc-4.2.46-21.el7_3.x86_64.rpm45fd2cf766b7598dafaef0c54a1eea504cb19ad1d58fa0ecea90850c4074b9a6SLBA-2016:2861-1This update fixes the following bugs: * Previously, Name Service Switch (NSS) module using hash-indexed files (nss_db) initialized itself incorrectly. Consequently, when nss_db module was enabled and any of the get*ent functions, such as getservent(), was called before a corresponding set*ent call, the application that called get*ent terminated unexpectedly. With this update, nss_db initialization sequence is fixed. As a result, calling get*ent functions without first calling set*ent works as expected, and the application no longer crashes. * The nss_db module failed to request larger result buffers when parsing group entries. As a consequence, group entries with a size in a specific range were skipped. With this update, nss_db detects when a group list does not fit into the result buffer and requests a larger buffer. As a result, group entries in the affected size range are processed correctly. * Previously, installing an Identity Management (IdM) server or client did not add the "sss" option to the "initgroups" lookup entry in the /etc/nsswitch.conf file. As a consequence, looking up secondary groups for users managed by the System Security Services Daemon (SSSD) did not work as expected. With the update, looking up secondary groups works correctly. * Previously, the nss_db module did not properly handle a protocol mismatch during lookups in the service database. As a consequence, lookups in the service database could enter an infinite loop. Now, nss_db deals with protocol mismatches and proceeds with the next entry. As a result, service entries are found as expected without entering an infinite loop.Scientific LinuxtrueScientific Linux 7glibc-2.17-157.el7_3.1.i686.rpmb5d542d4f96225998dab23742a663a30bb5832f2eff9322517a8c3c3943bb1caglibc-utils-2.17-157.el7_3.1.x86_64.rpm4f8fa4c9e65759b1155e11610c43b5cc8efd670246a380907fb08f248700e1c6glibc-2.17-157.el7_3.1.x86_64.rpm8c0ea085fa514c9410b2006762b85a5c86b8c158d67c162693ddaaba5aa6f9bbglibc-common-2.17-157.el7_3.1.x86_64.rpmdcd6278f00b958d33e57f3e1c082e8a1d30538af40d97a735c682a6ce2bf625eglibc-static-2.17-157.el7_3.1.i686.rpme17fbb9c161298b18462a052b852a12dc2e8ca2cb291071191b2669645844aceglibc-headers-2.17-157.el7_3.1.x86_64.rpm6c7e313cc983667c1102bf24170fbe0c23d2c38e7afe33b633bec0fe23fff792glibc-static-2.17-157.el7_3.1.x86_64.rpmf919fdcf8adebe19d12705f77e0445372dc752896290b8c63dd99e1a616c458bglibc-devel-2.17-157.el7_3.1.x86_64.rpm2f3f56d88c3755bfe9cd2576088e27fa05718bb861999f9a6c835b039e3607c4nscd-2.17-157.el7_3.1.x86_64.rpm661a9cb07aa84f40e36a0c387b3c2d7ecc87242e1c67a604edf1db693a93dc5bglibc-devel-2.17-157.el7_3.1.i686.rpm82b148a61ccfb012246dbd5c2e8c5b505e578b94045846a20ed9faf0dd343f67SLBA-2016:2862-1To see the complete list of bug fixes and enhancements, users are directed to the related Knowledge Article: This update also fixes the following bugs: * Previously, using a floating IP address inside a network namespace in some cases failed with the following error message: "bind: Cannot assign requested address". With this update, the kernel respects setting of the net.ipv4.ip_nonlocal_bind parameter to 1 in namespaces, and the floating IP address is now assigned as expected. * In the OpenStack Platform (OSP) environment with multiple guests on the same network, "no route to host" errors occurred when attempting to ping all the guests from a single virtual machine. With this update, the deffering policy of the Open vSwitch data path has been fixed, and the described error no longer occurs. * Scientific Linux in some cases failed to boot on platforms due to High Performance Event Timer (HPET) clock access contention. On systems with a Time Stamp Counter (TSC) clock and an HPET, the HPET is used to calibrate the TSC. On some large CPU count systems, this in some cases led to access contention on HPET, which caused a system lockup followed by Nonmaskable Interrupt (NMI) softlockup watchdog. This update reduces HPET counter read contention, thus fixing this bug. As a result, Scientific Linux now boots as expected on affected platforms. * Previously, when two NFS shares with different security settings were mounted, the I/O operations to the kerberos-authenticated mount caused the RPC_CRED_KEY_EXPIRE_SOON parameter to be set, but the parameter was not unset when performing the I/O operations on the sec=sys mount. Consequently, writes to both NFS shares had the same parameters, regardless of their security settings. This update fixes this problem by moving the NO_CRKEY_TIMEOUT parameter to the auth->au_flags field. As a result, NFS shares with different security settings are now handled as expected. * Due to an incorrect value in the virtual time base (VTB) register, the kernel of an IBM POWER8 KVM guest in some cases incorrectly detected a soft lockup condition, logged a call trace, and reported the following error: "NMI watchdog: BUG: soft lockup - CPU#x stuck for XXs". This update applies a set of patches to fix these problems. As a result, the soft lockups and error messages no longer occur in the described situation. * Previously, a packet loss occurred on transmit when Scientific Linux had complex network configuration and was running as a guest on a Xen hypervisor. An upstream patch has been backported that fix the xen- netfront driver to avoid packet loss when ethernet header crosses page boundary. As a result, the packet loss no longer occurs in the described scenario. * After migration to Scientific Linux 7.3, the Unified Extensible Firmware Interface (UEFI) boot failed due to a bug that prevented the kernel from booting through the PE/COFF image entry, which is used by the Extensible Firmware Interface (EFI) ipxe boot loader. This update fixes the alignment parameter on the call to the efi_low_alloc() function, and the kernel now boots as expected. The system must be rebooted for this update to take effect.Scientific LinuxtrueScientific Linux 7kernel-headers-3.10.0-514.2.2.el7.x86_64.rpmeb0426206787e1f177457cefa5dcb7ba6d61227c0b0de80a75e3423bcb9e93d5perf-3.10.0-514.2.2.el7.x86_64.rpmb54fbd0ec6e9c8691cfb4ac11a12271e8c159b941ad2b70815a307fb70768c34kernel-debug-devel-3.10.0-514.2.2.el7.x86_64.rpm8f9cd6ea895c647c3e21e0eef8dec71f5df38e5d690eeb7c1e20dd16b0a2cdc1kernel-doc-3.10.0-514.2.2.el7.noarch.rpm61cd7f1ad30e76af3f26ef357dafc8db2d40d06cf9c5b1fc0d2c27b8eee1ead7kernel-tools-libs-devel-3.10.0-514.2.2.el7.x86_64.rpm4043008b3dcdc7dd13d656b77cc71baac662a0d0e251596b81b27f991f4c50a4python-perf-3.10.0-514.2.2.el7.x86_64.rpmbab0a6517d66c12afc79da7bc5f6d92aa84f112b97d594eb0d1ac838ae823fe6kernel-devel-3.10.0-514.2.2.el7.x86_64.rpme0dc7482eff834e33fe68f98ed55b5023d183a9df6b851b37920fc8d2a91a5c5kernel-debug-3.10.0-514.2.2.el7.x86_64.rpm5fbb504551109618c0138fe0fba5f33ed40d8e7900da690793a19addc0ee6c03kernel-3.10.0-514.2.2.el7.x86_64.rpmdfbab57ae827862ca0676ea8399dd6946e0d27baa54f5977a7843585b1d0648ckernel-tools-3.10.0-514.2.2.el7.x86_64.rpm8603d0e7782f7bf370ff0c585658f282dd2ef2a5442413a9efa00ccb9158ec8ckernel-abi-whitelists-3.10.0-514.2.2.el7.noarch.rpm88572dd90dbdde5995f0fc4285562224901823ff5109fbade0af292a5d3a72e5kernel-tools-libs-3.10.0-514.2.2.el7.x86_64.rpm851a599fb247ffcc6bf582081e7c869c5d2adb9eed32f7b8afb13c9de9465286SLBA-2016:2863-1This update fixes the following bugs: * When using a previously-installed third-party certificate to sign the certificate signing request (CSR) during an Identity Management (IdM) external certificate authority (CA) installation, the third-party certificate trust flags in the network security services (NSS) database were reset. Consequently, the certificate was no longer marked as trusted, and the IdM CA installation failed. This update applies a patch and as a result, installing an IdM CA works correctly in the described scenario. * Previously, the Identity Management (IdM) web UI was unable to determine if a certificate has been revoked. As a consequence, some certificate- related user interface elements behaved incorrectly. A patch has been provided to fix the problems. As a result, the IdM web UI is now able to determine if a certificate has been revoked. * Previously, when installing a third-party service certificate, the ipa- server-certinstall utility did not verify if the certificate was issued by a certificate authority (CA) known to Identity Management (IdM). Consequently, certificates issued by an unknown CA could be installed, and services using these certificates failed to start or worked incorrectly. A patch has been applied and as a result, the ipa-server-certinstall utility now verifies if the certificate to be installed has been issued by a CA known to IdM. * Previously, due to a bug in the principal name normalization, the "ipa passwd" command failed to convert user names to lower case. As a consequence, users synchronized from Active Directory (AD) with a mixed case user name were unable to change their passwords. The user principal name normalization has been fixed and as a result, the "ipa passwd" command now works correctly. * Previously, after running the ipa-replica-install command to set up a new Identity Management (IdM) replica in domain level 1, the certificate authority (CA) certificate was not published. As a consequence, users were not able to download the certificate from the replica to, for example, import into certificate it in the web browser. The CA certificate publishing process has been enhanced and is now independent of the IdM domain level. As a result, the CA certificate is now correctly stored in the "/usr/share/ipa/html/ca.crt" file and users are able to download it from the web server. * A bug in the Identity Management (IdM) LDAP server caused replication to fail in certain scenarios with a replica that ran an older version of the 389-ds-base package. Consequently, the "ipa-replica-install" command failed when the replication partner on Scientific Linux 6. The problem has been fixed and as a result, the "ipa-replica-install" command no longer fails when the replication partner runs an older version of the 389-ds- base package. * Services created in Identity Management (IdM) before version 4.4 do not have a canonical name set. However, IdM 4.4 uses the canonical name to list services in the web UI. As a consequence, when upgrading to IdM 4.4, services created in earlier versions were not displayed in the web UI. A patch has been applied to support both canonical and principal names. As a result, all services are now displayed correctly in the IdM web UI. * Previously, Kerberos failed to reopen libkrad sockets. Consequently, one-time password (OTP) authentication could fail when the socket changed the state. A patch has been provided to fix the problem. As a result, two- factor authentication no longer fails in the described situation.Scientific LinuxScientific Linux 7libkadm5-1.14.1-27.el7_3.i686.rpm3a5f26a019782530a6064da9e607431c2159ff60937e8561cde2522cf16913f7krb5-libs-1.14.1-27.el7_3.i686.rpmc6addc699c8829beade65ad7b98548cba2c852120a3565016dfffbf136e0d3f5krb5-devel-1.14.1-27.el7_3.x86_64.rpmbeeb7929a9d19a8ebaf5e476b5ba0b6e9c1717d488135e916a4dcc559fc57726krb5-devel-1.14.1-27.el7_3.i686.rpm7c72ca683176cd50b4078d0c10ba18c0194f92d2bf7e08030e3b1ac829eb690fkrb5-server-1.14.1-27.el7_3.x86_64.rpma444cdd43f651938413286eeb6b53965571acd619e13f2269ec2c40e7e2ceec5ipa-admintools-4.4.0-14.sl7_3.noarch.rpm5a96146d648e21f5a72794afc2e41f5286a86a70e40519099426af2265ce2c68ipa-client-common-4.4.0-14.sl7_3.noarch.rpm599c76129c7ec0d04d643b8f2ef005054cd1e75c88538ac6f92ceae1864d2ccckrb5-workstation-1.14.1-27.el7_3.x86_64.rpm4f110796480d950ee77c983a11d7023ef0184c0ef5d0de8ed350ed707e7e3a16krb5-pkinit-1.14.1-27.el7_3.x86_64.rpm83c14ee94bde76557cd53aa9bdfa06a6f75652d3344a85c8728da3bdd1b4a8fbipa-python-compat-4.4.0-14.sl7_3.noarch.rpm434db563b6b648483994116b46ec13aeef90643e82a1b4065feaadaf49a04864ipa-common-4.4.0-14.sl7_3.noarch.rpmae99d0e9bc8d6fba2b314a852fdda60350d0b229836e6f6af09670327fdbd5f1ipa-client-4.4.0-14.sl7_3.x86_64.rpmf240020483aa7c719c4d640fd58c680f1a4326afc8d36e27c07e2586ccbde70fipa-server-dns-4.4.0-14.sl7_3.noarch.rpm94b8bc49619e916783f97fca253802a5b220c78eabb6c74f1e94b3039939fa08python2-ipaserver-4.4.0-14.sl7_3.noarch.rpm416265c5f650a2a650d74391393f0c6e0461eb67c6c361a54bc4f564d5b2fd9ekrb5-libs-1.14.1-27.el7_3.x86_64.rpmc92161d96bd12bce866acbd225545ab59ff522b0d35bc1b7280f03675ab4cb16libkadm5-1.14.1-27.el7_3.x86_64.rpmdeb6823d7b7c913b80182bcd2cc3cf3d70a4e0960f4060af071044933c7fbe62ipa-server-trust-ad-4.4.0-14.sl7_3.x86_64.rpm394a9cca6eb78adf15288fb2f8f86d6f7f5c576ab02ffe3b9d5efab8eefef454python2-ipalib-4.4.0-14.sl7_3.noarch.rpmabced6388fd4e18e2543193028de3dc16ffcf2f4f5bdc9ebd2de3dd1a381a8b0python2-ipaclient-4.4.0-14.sl7_3.noarch.rpm18dd1ccd176d5fe9bb83dbbcb815133668ab4d90086ad50d7293269b61361a18ipa-server-common-4.4.0-14.sl7_3.noarch.rpm6a4ac378ffc449cd25296274cb3c077b814bcab9f709ac54c8aa630b6a587c9eipa-server-4.4.0-14.sl7_3.x86_64.rpmdad6f88e4c3172fc82543a8363221b0dc33b8e2ec8adf39524333b728a708473krb5-server-ldap-1.14.1-27.el7_3.x86_64.rpm323714339d5cc1ea65b919a38b042cfc2fa310542d289c606976d7e1fdc1b9caSLBA-2016:2865-1This update fixes the following bugs: * Previously, SELinux policy targeted warnings and errors appeared when updating from Scientific Linux 7.2 to 7.3. This bug has been fixed by executing the policy migration script in the %postinstall phase only if the semanage utility exists on the system. As a result, the update proceeds without the errors or warnings. (BZ #1393045) * Previously, when the Ganesha NFS was configured, SELinux Access Vector Cache (AVC) messages appeared in the audit.log file. Consequently,the AVC messages blocked communication between the cluster_t and fprintd_t domains through the DBus message system. This bug has been fixed by allowing the communication between the cluster_t and fprintd_t domains in the SELinux policy. As a result, the cluster_t and fprintd_t domains now communicate through the DBus message system as expected. (BZ #1393494) * During the update from Scientific Linux 7.2 to 7.3, when updating the systemd package and then the selinux-policy package in two independent updates, systemd generated USER_AVC messages and returned "Access Denied" errors to DBus clients, because SELinux prevented systemd from accessing DBus.To systemd is restarted after updating the SELinux policy package, during update from Scientific Linux 7.2 to 7.3. As a result, systemd now does not generate AVC denials. (BZ #1394715)Scientific LinuxScientific Linux 7selinux-policy-minimum-3.13.1-102.el7_3.7.noarch.rpma2ac6470d2c4f01add9f3030f44132b4d7a810db8ab4de13f7ac8b95f4fa35easelinux-policy-mls-3.13.1-102.el7_3.7.noarch.rpm21e63b25563cb8cae1e8352debfe7bf74d6b38092a8d0ed1ab26d8a85a82ada7selinux-policy-doc-3.13.1-102.el7_3.7.noarch.rpm338da6b81597af8f3718ebf4bf24348c0e4fc0c067cc5a1e42cd0e0b6b7f661dselinux-policy-sandbox-3.13.1-102.el7_3.7.noarch.rpm43f8c6526e1948e01be149fee9c3806c4eeb863010b869e6a09e161c6521176bselinux-policy-targeted-3.13.1-102.el7_3.7.noarch.rpmab2997c7d96582c30c499486a0109f881d30e5a575aab788aeda83c458b67ffcselinux-policy-devel-3.13.1-102.el7_3.7.noarch.rpm9783581929333c8e7949f89f4497f2f5a596c7c0d3115f09b3810418b3140e51selinux-policy-3.13.1-102.el7_3.7.noarch.rpm7aef7d3122f66f7604ab58a8f7efe76d071cc447e2a20dbc235d0aae70ea7db8SLBA-2016:2867-1The sos package contains a set of utilities that gather information from system hardware, logs, and configuration files. The information can then be used for diagnostic purposes and debugging. This update fixes the following bug: * Previously, the networking plug-in terminated unexpectedly when a network name contained single quotation marks. With this update, single quotation marks are properly parsed as the arguments of the previously failing sosreport command. As a result, the networking plug-in no longer crashes.Scientific LinuxScientific Linux 7sos-3.3-5.el7_3.noarch.rpm5d221841f5d77f33d3781f06484d04e07246893c465c3ebdeb3ad160b6eaf1fdSLBA-2016:2870-1This update fixes the following bugs: * Previously, the IPA subdomain provider code contained an unitialized variable. As a consequence, the sssd_be process was at a risk of terminating unexpectedly. The underlying source code has been modified to prevent sssd_be from crashing. * Previously, the System Security Services Daemon (SSSD) was not able to resolve a Domain-Local group that was a parent group of a universal group while the domain-local group was from a different domain. This setup is sometimes called the AGGUDLP setup. A patch has been applied to and SSSD now works correctly in the described situation.Scientific LinuxScientific Linux 7sssd-ad-1.14.0-43.el7_3.4.x86_64.rpmd1ba33e4795cc62af580ca11bad3e70ec47be896478f68c9cc6e64f94ea7d2absssd-tools-1.14.0-43.el7_3.4.x86_64.rpmdac7b30d7d2e44a3d7f0483af2c96c7e10f56c339ed0562c02d80a620e98e23asssd-proxy-1.14.0-43.el7_3.4.x86_64.rpmbd4bfa074167f2874795141152359a6fc2d13a2899084e494fd6e155cff8b2c8sssd-krb5-common-1.14.0-43.el7_3.4.i686.rpm1d6cce6cb9bedda9a2a3e68cd79352dd0a17bc64e01e711307d7ca491b2aca9dsssd-winbind-idmap-1.14.0-43.el7_3.4.x86_64.rpm9627a1b0ff8fbb55d60ef741a7b21b4f95cb9241fff0cb40d441bea06c047d4dlibipa_hbac-1.14.0-43.el7_3.4.i686.rpme2fd2bac62b13da0e8bb8f60655d20da51124ec5fc4a223baa729e6d8c485635python-libsss_nss_idmap-1.14.0-43.el7_3.4.x86_64.rpmf85cb98dc61b41a6d9340b65f23568d4e7b25885c09cadc6cda21de29e0b65c8python-sss-1.14.0-43.el7_3.4.x86_64.rpmc140a429541c1b741ccd08f1d7fda0ca83bbfbaa510e2d8fe60f49075998aa2bsssd-krb5-1.14.0-43.el7_3.4.x86_64.rpm33e32dd64dd38fd55d90c7a725292bf2803b13288f17cd4bf9f403ab33781a7blibsss_idmap-1.14.0-43.el7_3.4.i686.rpm89b84ee6ef75efbde2ca977da0e402f6572d706501bc24aa5edabec5932e7dfblibsss_idmap-devel-1.14.0-43.el7_3.4.i686.rpm4c602019fe48db46c6659b81cd6d103d9bfe70d8c0ffb2e148800ca30a534acdsssd-common-1.14.0-43.el7_3.4.x86_64.rpm3a8915fc3c83ee7d7f43200da87eb0ad54dc12730c266ffe1a4b9a965f88b4a0sssd-libwbclient-devel-1.14.0-43.el7_3.4.i686.rpm59480c82736d0ff4418129c90f194f78d329ad11f49510290016576622e44779libsss_autofs-1.14.0-43.el7_3.4.x86_64.rpmfb4d9bbb3449f5573db33b080e027cb49441bf6474bc5c9e045dd4e6bb7196balibipa_hbac-devel-1.14.0-43.el7_3.4.i686.rpm97db0eff1d5539e67d7d725f832c4e2dc00b1e0ee6138ca3b1cef360109402b2sssd-1.14.0-43.el7_3.4.x86_64.rpm90d592c351f61e7eb74367beb3e752623ea4e5f5ab7cd0cf5fcab374e99f1e33sssd-libwbclient-1.14.0-43.el7_3.4.x86_64.rpm8a42b29bfcb17064559d0f225f95687b29c4308049945fdc82f770b9fe07a4falibsss_simpleifp-devel-1.14.0-43.el7_3.4.i686.rpmea6b17372395045036fe54d5cb4ff544859cf83aa4a69be94d2457ce5a0986cdsssd-common-1.14.0-43.el7_3.4.i686.rpm5dfce74a901846ed86f7e9044b988e31819c88f65ea8c86d50e350a1dd36bd4dpython-sssdconfig-1.14.0-43.el7_3.4.noarch.rpm943522868a13f7da02119548cf34d3733bb7c1a04fb8309967464dd64899971flibsss_nss_idmap-devel-1.14.0-43.el7_3.4.i686.rpm1f03c260d7125c924e13046f51bdaf33ffce74b0736c89130569680968135638sssd-dbus-1.14.0-43.el7_3.4.x86_64.rpmeddacb144d51b9442c9ac57f4b2fd791d3379c88ea3b668b17436eadb6d7875clibsss_simpleifp-1.14.0-43.el7_3.4.x86_64.rpma0aeb2bf675390d754f6b84fdba4559d5f7900d159d286661be0fbc84f3e8e61libsss_sudo-1.14.0-43.el7_3.4.x86_64.rpm72ab6172207fab43a490e13378fb5c792103b86a8cf7cff085cfdea63cd60bf6sssd-ipa-1.14.0-43.el7_3.4.x86_64.rpm83d3a2d7c2f564e962c008f2de9b31cc937da572de930048ac0f723b73500474libipa_hbac-1.14.0-43.el7_3.4.x86_64.rpm6634a23a418e5c39059d92dc064d6da77ecf732bf2c41624c6538e398e980555libsss_nss_idmap-1.14.0-43.el7_3.4.x86_64.rpm245fdd07e8490da308fea4d929e036458b3d4f3a4442fb367ec5a585c4782b9blibsss_idmap-devel-1.14.0-43.el7_3.4.x86_64.rpmb9132b1392763067be439f0528c16b1bd984b0d0db9bfde6227343499a6ad121sssd-libwbclient-1.14.0-43.el7_3.4.i686.rpmc9154d5d868a2d5089886dde0340db85d389baa6a7767ab591428781ce4212aesssd-libwbclient-devel-1.14.0-43.el7_3.4.x86_64.rpm6f94cb4079b4fbd8c236024bc2d76e111cccf5bb022589f4bc20021ed38212c1libsss_idmap-1.14.0-43.el7_3.4.x86_64.rpm1a61672d1c2830fdac1ad68d99c63fa840de6d44345afd50a28111ef7551cf1asssd-polkit-rules-1.14.0-43.el7_3.4.x86_64.rpm1857424eca3407f3935188461e2a50622560e2667620383b1c5fe124b5f475f3libsss_sudo-1.14.0-43.el7_3.4.i686.rpmbe49341747440d446b3ada8a8ad48736d0691536389692a3f37278f362e3007asssd-client-1.14.0-43.el7_3.4.x86_64.rpm51852fecc5f57d8e70d3fa61c627ee43473b0d7fcd7ab6b39b1dc78c6b037e9elibipa_hbac-devel-1.14.0-43.el7_3.4.x86_64.rpm5d40e9052b1dcc4d93edc5bd8db303b45e574503ec5e7b77dbb06f8e7636e6f1sssd-ldap-1.14.0-43.el7_3.4.x86_64.rpm6fb1a516e05bf73cb2802ab79bfa41d63655acef54b10870152cf78cd8be5408sssd-client-1.14.0-43.el7_3.4.i686.rpm067cc70f3a7322d02eaa8cea8c0a3ea52ce1ddcc33a8499093d05dd9e6b20fc0libsss_simpleifp-1.14.0-43.el7_3.4.i686.rpm452dd445aa84b7cf46713ce7427ffece304165b63a24210a9c23aa2a2b1fb304libsss_nss_idmap-1.14.0-43.el7_3.4.i686.rpm8b8665e894272d441f41f78ea445c08c7a7c96f92d4bb6040c90be843fb62208sssd-krb5-common-1.14.0-43.el7_3.4.x86_64.rpmcf9e5332e396d34e0325f6e1d1f94c56cde57d589b56bfe178d04a2a277ef038python-libipa_hbac-1.14.0-43.el7_3.4.x86_64.rpmf10f4edf72b493f1c638701560602c5d04dc800d7381a83666c33d673d428345libsss_autofs-1.14.0-43.el7_3.4.i686.rpmbba911090a1b59b66825f746299bea86c981fb96b1b922961871ed142e248bd9libsss_nss_idmap-devel-1.14.0-43.el7_3.4.x86_64.rpm6911619f6f3e850f6d51543455227a81703748c5aa962e86c42e74015de94efflibsss_simpleifp-devel-1.14.0-43.el7_3.4.x86_64.rpmb5b7fd6c694786692623b2ac68e2872b57c327e10b2cae42decd84b09bba1e96sssd-common-pac-1.14.0-43.el7_3.4.x86_64.rpma2bb4b940b4881a3ff37b385d71a2e1c73846f437b717c0b881d43c883615b78python-sss-murmur-1.14.0-43.el7_3.4.x86_64.rpm4cd2843b374edf036ba90d58be90ddd4c86f026f1731e9b8e929557d89eba32aSLBA-2016:2875-1This update fixes the following bug: * Previously, the openhpi log files were always created with read permissions for all users on the system, which caused a potential security risk. With this update, the umask value in the openhpi daemon corresponds with the system umask, and as a result, the permissions on openhpi files properly reflect the system permission settings.Scientific LinuxScientific Linux 7openhpi-3.4.0-4.el7_3.1.x86_64.rpm37937e68c97d445ff1d84ac0f16eb8eb3a0f95b6548e75d81ae64c038e71c310openhpi-devel-3.4.0-4.el7_3.1.i686.rpme47842e0f33ebe4fa95b7911cf0bf0476695dff9149ced1bfb8fe310a75f3557openhpi-libs-3.4.0-4.el7_3.1.i686.rpm45fb099abfd34489331f5b4531a20dda3a9fb5c9018489e7a92e82fc880d2afcopenhpi-devel-3.4.0-4.el7_3.1.x86_64.rpm17109027e84970022b1098b5b02ec7ef931c66bb034b3ee5f42dd5407f406844openhpi-libs-3.4.0-4.el7_3.1.x86_64.rpmd72e94b669fbda7d1037b4fc76a7e03f815123ce3321cdd1b8fa5de943256d7eopenhpi-3.4.0-4.el7_3.1.i686.rpm08d5fb0409b10ec32f7dfd9fceeae5cba87c7e3b9ac037267fab69cf82290947SLBA-2016:2877-1OProfile is a low-overhead, system-wide profiler that uses the performance monitoring hardware on the processor to retrieve information about the kernel and executables on the system. This update fixes the following bug: * Previously, for Intel's next generation Atom processor, OProfile incorrectly configured the performance monitoring hardware to count processor cycles for the default event. As a result, on these processors, the default cycle count event used by OProfile did not work. This resulted in no samples recorded by operf and zero counts by ocount for the default cycle count event. With this update, OProfile correctly configures the performance monitoring hardware for Intel's next generation Atom processor.Scientific LinuxScientific Linux 7oprofile-0.9.9-21.el7_3.x86_64.rpm3cefb370a7900f28ebc315dc8dbea3300bd2fdb8af0dd82ec53a06dbbb6f8fe9oprofile-gui-0.9.9-21.el7_3.x86_64.rpm39adfb9b1eb06dd1db875ae18451e34a7def472e84a12da83d082aac576948e6oprofile-devel-0.9.9-21.el7_3.x86_64.rpmd90ddc87de0e2e51ee633b3dcfb8192bd3e12e20f2241d75431bb11402c8a39doprofile-devel-0.9.9-21.el7_3.i686.rpmf60576a36a19d0621ecc8885c99c4748a29043b2ac0eef17f725fc3ad532d9d5oprofile-jit-0.9.9-21.el7_3.i686.rpmc4d5e65e3d586acf9ade81df5785658d2e86adf436e707252ee4afb68a07ce9aoprofile-jit-0.9.9-21.el7_3.x86_64.rpm38e9e6cc24b56b89fc11d775eaf96f0a6518a274d2070520c6e4ac11153dc378SLBA-2016:2878-1This update fixes the following bug: * Previously, the following warning message was generated when updating the mcelog packages: warning: %postun(mcelog-3:101-3.9de4924.el7.x86_64) scriptlet failed, exit status 1 The underlying source code has been modified to and updating mcelog now completes successfully without generating the aforementioned warning message.Scientific LinuxScientific Linux 7mcelog-136-2.e4aca63.el7_3.x86_64.rpmea09ff19fb158456aaf279c5a1a8d04a88fe31cc780c24df34d551d434876bf2SLBA-2016:2880-1This update fixes the following bug: * A regression introduced in an earlier bug fix caused ldapjdk to fail in parsing the LDAP URL, when the "host:port" part was not specified. A patch has been provided to fix the problem and as a result, ldapjdk now correctly parses LDAP URLs in the described situation.Scientific LinuxScientific Linux 7ldapjdk-4.18-16.el7_3.noarch.rpm177ace4b567318c2efddd73814f986d2e5bc191f57f58ca758b94f29a45dda82ldapjdk-javadoc-4.18-16.el7_3.noarch.rpm4915cae25d60119fb91459f6bba5aed9d2a5574d313329065734dfba5e2c3810SLBA-2016:2881-1This update fixes the following bugs: * Previously, during two-step installation, Certificate System attempted to perform a lightweight CA key replication because the CA signing key was not available. This caused the installation to fail because lightweight CA key replication attempts to read the CA's UUID, which was not yet assigned at this point. With this update, two-step installation does not attempt to perform a lightweight CA key replication, and can now complete successfully. * Previously, when the CA's Subject Distinguished Name contained values that used string encodings other than "UTF8String", the string always compared as unequal to itself when parsed from a string. This caused Certificate System to add a new LDAP authority entry to the main CA every time the CA was started. With this update, Certificate System compares string representations of the Subject DNs instead of "X500Name" values used previously, which fixes the underlying problem and prevents unneeded LDAP authority entries from being added on every startup.Scientific LinuxScientific Linux 7pki-kra-10.3.3-14.el7_3.noarch.rpm207c26683d38739f81c6fb65fb774a70d205d1694a55c747c8292ee73f34e3e2pki-javadoc-10.3.3-14.el7_3.noarch.rpm2ab49abc60cef89523225e9c8b24e8112693fd1b87b23099f503207216da0e94pki-base-10.3.3-14.el7_3.noarch.rpm436a5dd5beff417d3982ecbb8e9b9c51c1e45b24e053eec3e4bf0bc08aa40f99pki-symkey-10.3.3-14.el7_3.x86_64.rpma8b858b6e20ae41f03d6f8b8a3d295d6da9eb9ac1d3b6c1879590670b54f1c72pki-base-java-10.3.3-14.el7_3.noarch.rpm28c0027fee65ebad7a75ad64ffa11a6bd4d5d1eb0871bcc8e2ad95a75ba8ae10pki-tools-10.3.3-14.el7_3.x86_64.rpm832691abc61281bc95884e5cae2fbdb973d020a017eb196cb2f8469eb4538d81pki-server-10.3.3-14.el7_3.noarch.rpmf3deee1831eb01837c905000bc461c313d19d5aa53d4628f37fd2390177e3152pki-ca-10.3.3-14.el7_3.noarch.rpm9377c2557855da12581a0d0dc606a2a0e0ac1d754bd3e52ce09eef2361cd79c6SLBA-2016:2882-1This update fixes the following bugs: * Previously, when the NetworkManager utility was stopped, in some cases, wired network devices were deactivated and became unreachable. With this update, wired network devices remain reachable after NetworkManager is stopped.Scientific LinuxScientific Linux 7NetworkManager-1.4.0-13.el7_3.x86_64.rpm88bcbdfa788c2091a2b7a59e1bf89fa97181c9d6b16d0078077f7cc4b5e135d4NetworkManager-wwan-1.4.0-13.el7_3.x86_64.rpm18d4b0f0ae5e9515b8d3c900716b18ffd770b6e8c4cde48921855dc4a25a76f2NetworkManager-config-server-1.4.0-13.el7_3.x86_64.rpmf9db49acad5347874dbfc82968245f5ab583d6b8e4c5e147c28c5fee6803a788NetworkManager-wifi-1.4.0-13.el7_3.x86_64.rpm6e4a3d8cbf9f81d6554932d3efa16bbb848be5a107e0ae89fa86dd0b8254aa25NetworkManager-1.4.0-13.el7_3.i686.rpm486eed702c185f9223d2294ea6d03557b194a41575887185e9092468cea2b080NetworkManager-libnm-1.4.0-13.el7_3.i686.rpmd363e927c2e8c37f8fac3b25d6e7eacb14d1b93ab8d53a4b339aa9bf5e2e3b60NetworkManager-glib-1.4.0-13.el7_3.i686.rpm16478340a238723ad8e55d2c21626b66904727ba421627b2b5f1d2ce0f1318e0NetworkManager-glib-1.4.0-13.el7_3.x86_64.rpm0a4bab38b8f2161d167d020038bafd638e93b5e6a66a2f9de77e87989737d29fNetworkManager-glib-devel-1.4.0-13.el7_3.i686.rpm1f8b9de99605433ae9bd79f248c5e8a93a89e3d1a071b85d5e43b6e48d054aa7NetworkManager-libnm-1.4.0-13.el7_3.x86_64.rpm7cc93189020c656160a948467e48a2430282369987a523c80ac2194784942bd3NetworkManager-tui-1.4.0-13.el7_3.x86_64.rpme4963b962932423ae4261b520f3076ae4b544d3677591dbf50f76a749c50201eNetworkManager-dispatcher-routing-rules-1.4.0-13.el7_3.noarch.rpm63fdd943b8b50dbd6bf76d1cd3f08299463827c94e153c7307f68a3d9ddf2651NetworkManager-team-1.4.0-13.el7_3.x86_64.rpm6b10caa805ec21c4b69e6cb9be37d18ebf189bfcd1f2ddc174ed1682d668aa41NetworkManager-libnm-devel-1.4.0-13.el7_3.x86_64.rpm4238562d2c7851a57c912323bb1ff341c370f761414d95e10496af37f7a4b731NetworkManager-libnm-devel-1.4.0-13.el7_3.i686.rpm6ed4ee0d47aa252aa417d057524dd91438e501438c46e281b1e0b989315d557cNetworkManager-bluetooth-1.4.0-13.el7_3.x86_64.rpmba2ed6ae04225398ce1c95797c4de4f67e4f5a77ec1f61942c164dbd09cd95b6NetworkManager-adsl-1.4.0-13.el7_3.x86_64.rpmb81d641c4476c711bd28dc8c5ad9ce6ed2c5a1f45fa81f0424ca239f0ad3e0d6NetworkManager-glib-devel-1.4.0-13.el7_3.x86_64.rpm660ecaab40b598f07794d93c19b03acd94aa2e7144d76ca8f2d7a4423b595d13SLBA-2016:2884-1This update fixes the following bug: Previously, when nfsserver was started, custom nfs options in the /etc/sysconfig/nfs file were removed with resource- agents-3.9.5-54.el7_2.9.x86_64. With this update, nfs options are maintained in the /etc/sysconfig/nfs file.Scientific LinuxScientific Linux 7resource-agents-3.9.5-82.el7_3.1.x86_64.rpm8e524c4975cad3d35d2b635ac1fdd38a6c61658b41f4dae9419f8d6f4ee41cfaSLBA-2016:2885-1This update fixes the following bugs: * Previously, the libvirt library allowed only use of slot 0 on the pcie- expander-bus controllers, even though slots 0 - 31 could be used. The restriction has been removed and slots 0 - 31 now can be used. * Previously, the libvirt library did not disable post-copy on the destination when a migration completed. As a consequence, it was not possible to save such a domain on a disk. With this update, libvirt properly disables post-copy after the migration finishes. As a result, subsequent migration does not use post-copy unless it is requested, and saving the domain to a disk succeeds. After installing the updated packages, libvirt will be restarted automatically.Scientific LinuxScientific Linux 7libvirt-docs-2.0.0-10.el7_3.2.x86_64.rpmd18f2f6ecdd54d7d55f24a3af62979b77a518ada40889183bdfca920a24589c5libvirt-daemon-2.0.0-10.el7_3.2.x86_64.rpme5f64ac21e7ea7fa1cd75a070a76d9e28ddb710890b853bbe31f59b3f9b46bb9libvirt-daemon-driver-storage-2.0.0-10.el7_3.2.x86_64.rpm3b458830242b3550f784b8f24ff09809eb5c15fa6241f4f79f9b0682a4284464libvirt-daemon-config-network-2.0.0-10.el7_3.2.x86_64.rpm35c993521ee08f7c65fcaa5261300171a79dd4c1adc33b897dc8d19ec3ebdaaalibvirt-daemon-driver-nwfilter-2.0.0-10.el7_3.2.x86_64.rpm76139507ba05e61cd57e489781b57914c9e955edd9b683af72bf6313b305c051libvirt-2.0.0-10.el7_3.2.x86_64.rpm30d43b6054fd0f74f5ca0fe9de47565d68a3748264ec761e52f2e75fa8cf3df3libvirt-login-shell-2.0.0-10.el7_3.2.x86_64.rpmfe1689dcfc00c2a4fe5d46b234236f74ea725b35c09bd552f12e0559df792caclibvirt-daemon-driver-secret-2.0.0-10.el7_3.2.x86_64.rpm3d5643c98d99e3395601a99dea5ac2b7d88fdce3c12bedc75cee6625bdb89378libvirt-nss-2.0.0-10.el7_3.2.x86_64.rpm79654956f32e79c2df633fc74a476e1b2cd89c95ee5a61a63bcbe83a4469dae8libvirt-daemon-kvm-2.0.0-10.el7_3.2.x86_64.rpm9bd7de6c2c7db6ccad19747a361bf85dee5ebd595118675349efe9bde6ccfe05libvirt-daemon-driver-nodedev-2.0.0-10.el7_3.2.x86_64.rpm38aea53f6a987762cc42f41cee556a95448d7de2440e864f61ade70e5619d135libvirt-daemon-driver-network-2.0.0-10.el7_3.2.x86_64.rpm3d1669b6f01f988399b512330bd9737c45b45df19c26a247225cc0ed85587848libvirt-nss-2.0.0-10.el7_3.2.i686.rpmcaf8a9cd02116eb4ab03477f6c3bc5f2073a7930aa31fa537150188b0f4404d0libvirt-devel-2.0.0-10.el7_3.2.x86_64.rpm09034f84bdde11926128b2abb201709e41fb662468963c09a7a3c30046d5a02blibvirt-daemon-config-nwfilter-2.0.0-10.el7_3.2.x86_64.rpm3f0d36815d848b4528e904fb8d5cd14a9fc4059a4ec7eb5aa8baf04c3cd55a96libvirt-daemon-driver-qemu-2.0.0-10.el7_3.2.x86_64.rpmd31e5786e4155eb0aad6c3544910f2764262ffb768ab35c33c1f0f60e3a1e38flibvirt-devel-2.0.0-10.el7_3.2.i686.rpmc996960849f7da2c910fccc407874158d66829ce7afaa6e943dd219ef3950957libvirt-lock-sanlock-2.0.0-10.el7_3.2.x86_64.rpm4c901f8ddab805b45c5dfbe868097bcc1ef413274b213ff8169d540a551d39b4libvirt-client-2.0.0-10.el7_3.2.x86_64.rpme1cba59fa77ae736e8d2ea25112160425c811c11bcb587f052c70373ea3f5155libvirt-daemon-driver-lxc-2.0.0-10.el7_3.2.x86_64.rpm07c508727c230b73408cd5682f7b51ee757d43e8e2b0400b9609b699ec158f15libvirt-client-2.0.0-10.el7_3.2.i686.rpm8c59c8229f07a7e47268a566f1a9fcb6f2a9bdda27b0b939b0531373b0477c9flibvirt-daemon-lxc-2.0.0-10.el7_3.2.x86_64.rpmcbce62ac9e82524c3bd1e6ba22ddf4d39ddcc88c76515b78c24a692ea0d585d8libvirt-daemon-driver-interface-2.0.0-10.el7_3.2.x86_64.rpm07c7999ae29d86f26ca704d71752b0ce8b936b1e91d2893886dd12503728e891SLBA-2016:2886-1This update fixes the following bug: * Previously, the tuned-adm profile NONEXISTENT returned to the shell after timeout, which blocked the execution of oVirt. With the fix, the profile returns to the shell immediately.Scientific LinuxScientific Linux 7tuned-profiles-compat-2.7.1-3.el7_3.1.noarch.rpmb135dd85e7117b57e118f08128a7a42789f5af4edf737dee8349eb01ff088818tuned-utils-systemtap-2.7.1-3.el7_3.1.noarch.rpmc384315909d5027a4a703ca749b3347512383d944d645bdfee4255ddf709854etuned-2.7.1-3.el7_3.1.noarch.rpm5bc82ba1ca32f3fcc14a53cd19eee3c363c13cc45eac54a967b7c5b991d5b4e4tuned-profiles-atomic-2.7.1-3.el7_3.1.noarch.rpm681719a4dc3c2275186ff7b9046b04b82121a6144e517741c834bec19e9d064dtuned-utils-2.7.1-3.el7_3.1.noarch.rpm627911456c473d6932e0ef66439cf9b2a41f551b7e808a77afde401791a40a6ctuned-gtk-2.7.1-3.el7_3.1.noarch.rpm0ba6028580c5f53511a4e0a6724f1161ff07464fde16e99f641d35868476c1c8tuned-profiles-realtime-2.7.1-3.el7_3.1.noarch.rpmcc71c0cc3b8601a8c28032c8be19a64da8b0f7b2a5b4b219c52e5a36bee024d9SLBA-2016:2887-1This update fixes the following bug: * When chronyd was configured with the smoothtime directive and the leaponly option to perform a server leap smear, the direction of smoothing could be determined incorrectly due to numerical errors in floating point operations. This consequently caused an assertion failure and chronyd terminated unexpectedly. A patch has been applied, which ensures that the direction is calculated and applied correctly when small offsets are employed in a time update.Scientific LinuxScientific Linux 7chrony-2.1.1-4.el7_3.x86_64.rpmb741b791fae86597937cf6da16c6f1e772dcc8e4a2acff8906bc563be4efea7cSLBA-2016:2929-1This update fixes the following bug: * Previously, the rundir directory had incorrect SELinux permissions. As a consequence, the REmote DIctionary Server (Redis) failed to start. A patch has been applied to and Redis no longer fails to start.Scientific LinuxScientific Linux 7resource-agents-3.9.5-82.el7_3.3.x86_64.rpm67d0edfc86a4d55ed0fb36e023a7055b0ec2cfd064774b33c12ed1783e4f5a77SLBA-2016:2930-1This update fixes the following bugs: * Instance High Availability (HA) on Red Hat OpenStack Platform 10 prevented the agent from functioning correctly. Consequently, the agent was not able to fix a domain name based on the hypervisor list and the force_down compute service did not function correctly. This bug has been fixed, and the agent now functions as expected. * Previously, monitor action for fence agents was able to succeed even when the fence device was not available. With this update, monitor action properly detects if fence device is working.Scientific LinuxScientific Linux 7fence-agents-ilo-moonshot-4.0.11-47.el7_3.2.x86_64.rpmd9cf08ea6951e714c6e08e8484c6aaa7b99857313c08dbab1373d6ea068be556fence-agents-ilo-ssh-4.0.11-47.el7_3.2.x86_64.rpm9b22d5077fac701c461ca6e26ca18e84bad4b5c4118a92dc1f1f2b817869d9cdfence-agents-ibmblade-4.0.11-47.el7_3.2.x86_64.rpmb01ec3e814dd3d74183ed7061b29eb48f7a3585299d23832766af81696c51812fence-agents-bladecenter-4.0.11-47.el7_3.2.x86_64.rpm978a808d79f49c3f47198ac596d92d60953a5382b7db7ff0afe2ae56deacc5e8fence-agents-apc-snmp-4.0.11-47.el7_3.2.x86_64.rpm465bc7a4f336d1222dbfb6db83f63e6917ac215fefa360a6b83274bcf45ed5eafence-agents-ilo-mp-4.0.11-47.el7_3.2.x86_64.rpm57864f8e80fde8074358bcd5a0da1c8c24a2870fdecc5ba0db6bff10ad8a5da0fence-agents-mpath-4.0.11-47.el7_3.2.x86_64.rpmebcbb263ea916d28bc7ea645cffc3d517327a22e28b9ff49c79edb5ae073af95fence-agents-eps-4.0.11-47.el7_3.2.x86_64.rpmc44815ad482394e2f4dbcea98cea0a1c0d6e8ede2d7b39c0867142b9c4168924fence-agents-ipdu-4.0.11-47.el7_3.2.x86_64.rpm81b4c4980f9437f2b253d72639443156f420e15f2517bbc7c8586396dd96c5b1fence-agents-scsi-4.0.11-47.el7_3.2.x86_64.rpm0d864cd85e705202175b6d82056f2032efef4a7156e1b1eadf86daadfff3707efence-agents-eaton-snmp-4.0.11-47.el7_3.2.x86_64.rpmd517f60ee39bdcccc7e0c7ca5b0e7c7d9dd7f8e7a45dcc8f3ff37955cd025ca4fence-agents-all-4.0.11-47.el7_3.2.x86_64.rpm40287268fb2dd9a49faf1dd4d3a177105f4c4fc6c18e38e8aa7f4495b3757b90fence-agents-rsb-4.0.11-47.el7_3.2.x86_64.rpmd6598ea93bfa3091d99dc00a1f6dc5650a054e63638112bb27c0a96a347cdfccfence-agents-wti-4.0.11-47.el7_3.2.x86_64.rpm184735c3ef01b39bb606da82e58dacb17fbfed94c8f87468d9514593d3216c60fence-agents-common-4.0.11-47.el7_3.2.x86_64.rpm18291abfd3a45750da59c8bee1305566cc2559ab349b29148a21a83bb829d6ecfence-agents-rhevm-4.0.11-47.el7_3.2.x86_64.rpmf239ff5253969e9de392e7a6ef8e27fa55fb9535d0bb9466929f5491ca7fd554fence-agents-drac5-4.0.11-47.el7_3.2.x86_64.rpmad01a1cb2e8396342407a69483956dedd36505d5ff768c4f76e38d0dfeadd4a7fence-agents-ilo2-4.0.11-47.el7_3.2.x86_64.rpm5ecc80c3a6e71d9202538fe4d8300ea3f4b63cda54ff913d1d9f537f9da172bcfence-agents-virsh-4.0.11-47.el7_3.2.x86_64.rpm8f9bbe1671a100a09eab626a1a34211639f99a93cfbc87f15cac925f7b9bcd90fence-agents-apc-4.0.11-47.el7_3.2.x86_64.rpm597dbc0b2a40016b64e90f326489f6870f022de2ea2f2756d5b8fc73340973c4fence-agents-emerson-4.0.11-47.el7_3.2.x86_64.rpm5d0e7f01d9c05502ded7b0f6078c4d23e6a705895f1c356d70d5273da4c117f5fence-agents-compute-4.0.11-47.el7_3.2.x86_64.rpm00d96754f49110b4e2454494f88e68f9b06868cba92bc797cb966f050316eb3afence-agents-cisco-mds-4.0.11-47.el7_3.2.x86_64.rpm6e5ffc10ac193786a80209a986056b91a81c29053ee7ec7b752749e5cc204b65fence-agents-cisco-ucs-4.0.11-47.el7_3.2.x86_64.rpm89b68bee09ec20415e47732f7b6bbafbcab2a14d0653f3d3c54874d95cf35a42fence-agents-ipmilan-4.0.11-47.el7_3.2.x86_64.rpm141770193a21b83ea0e3e60b41b4d6759b13497b21c0789b1c0d8745707e2827fence-agents-vmware-soap-4.0.11-47.el7_3.2.x86_64.rpm82658f50fba52d53dfa0abdd0ee802bbe8a7d307cd4d11a00c156c1ef3525a1ffence-agents-ifmib-4.0.11-47.el7_3.2.x86_64.rpm83a59b5dbe5a086930f3044ea287a8cb8f7a2c41263bc44c1e665c3dee86089bfence-agents-intelmodular-4.0.11-47.el7_3.2.x86_64.rpma4f3d9e063c73eb4686b18647b9aa57078f6dbed99a3f93a22da5651b98578cffence-agents-brocade-4.0.11-47.el7_3.2.x86_64.rpmbd723c93d169306952cc7be606e606879635cb0a16f451ae4fce960b7ca902aafence-agents-kdump-4.0.11-47.el7_3.2.x86_64.rpm97d72fb895e23aaddb0f96b762e4c084d0688f65e475438d7aa459142946d1f6fence-agents-rsa-4.0.11-47.el7_3.2.x86_64.rpm1da87a2603e6d7a5ef31ebe0563c3b45c6b88a96f2c83948e3bafbf4063432e3fence-agents-hpblade-4.0.11-47.el7_3.2.x86_64.rpm444fbebce40c130395b7deb26124b9f690a9d972ac76fb7ae1160de6cdb99641SLBA-2016:2931-1This update fixes the following bug: * Previously, the haproxy-systemd-wrapper reported an incorrect exit status when the haproxy server failed to start. For example, when the haproxy server attempted to bind a port that was already in use, the haproxy-systemd-wrapper incorrectly returned a zero exit status, indicating success. This bug has been fixed, and haproxy-systemd-wrapper now correctly reports an error when the haproxy server fails to start.Scientific LinuxScientific Linux 7haproxy-1.5.18-3.el7_3.1.x86_64.rpm15560f7d2ee6eb29e3d80ff8e02730bf5fe57bc8b181cc0fe559881bc4966583SLBA-2017:0028-1This update fixes the following bug: * The microcode_ctl package attempts a live update of the CPU's microcode during the package installation. On certain CPU models (Intel Xeon v4, family 6, model 79), updating microcode_ctl could previously cause the system to become unresponsive or reboot instantly. As a consequence, this could leave the system in an unbootable state and with duplicate packages in the RPM database. To the live update is skipped on the affected CPU models, and the described problem no longer occurs. Note: a system reboot is necessary for this update to take effect.Scientific LinuxScientific Linux 7microcode_ctl-2.1-16.1.el7_3.x86_64.rpm3a4587eef0588cfc5d07d86aeb8a833119d154c4e818d080bceab1e311bb743cSLBA-2017:0068-1This update fixes the following bug: * Previously, when mirroring files with the lftp utility over SFTP, lftp sometimes received EOF from SSH before it was able to flush the rest of the data buffer. As a consequence, the last data packet was lost. This update adds a condition to ensure that if there is some data left in the buffer in the described situation, the data is safely passed to the internal buffer. As a result, data packets are no longer lost in the described scenario.Scientific LinuxScientific Linux 7lftp-scripts-4.4.8-8.el7_3.2.noarch.rpm7f280bc98619a8ed1589ae344c809e557e5b0f1c6057fd442b1867535b358ee6lftp-4.4.8-8.el7_3.2.i686.rpmd66e0b716c567ac47af768d7afce0cf12e8274e81d2394a32a788efa3e5f8edflftp-4.4.8-8.el7_3.2.x86_64.rpmfe9fd16bfe0aa91314c6257480642f8cc1c25fa5be4eebb552901d1bdf03182dSLBA-2017:0069-1This update fixes the following bugs: * Previously, when Samba was configured as a domain member in an Active Directory (AD), the "%G" configuration variable in the /etc/samba/smb.conf file was not replaced with the primary group name of the session user name in some scenarios. As a consequence, if the variable was used, for example with the "template homedir" parameter, users were not able to access their home directories, or the share worked incorrectly. A patch has been applied to fix the "%G" variable replacement. As a result, users are now able to access shares in the mentioned scenario. * Previously, the "nss_wins.so" library was not correctly linked against "libreplace". As a consequence, the name service switch (NSS) failed to load the library and applications failed to use the NSS Windows internet name service (WINS) resolution. The library has been linked correctly and as a consequence, NSS is now able to load the library. * Previously, the "nss_wins" library used incorrect function definitions for "gethostbyname" functions. Consequently, applications failed when using the Name Service Switch (NSS) with the "nss_wins" library. The function definitions have been fixed and as a result, applications using the NSS "nss_wins" library now work correctly. * Previously, when the "smbclient" utility did not receive a mechanism list message integrity code (mechListMIC) token, the connection to a share was not established. As a consequence, "smbclient" failed to connect to shares on Microsoft Azure or Apple Mac OS X. A patch has been applied to enable connections without receiving a mechListMIC token. As a result, the "smbclient" utility is now able to connect to shares on Microsoft Azure or Apple Mac OS X. After installing this update, the smb service will be restarted automatically.Scientific LinuxScientific Linux 7samba-4.4.4-12.el7_3.x86_64.rpm5448f1402fa482ef38d775367947981ad551bef9783258a57737c6383a4d89e3samba-common-4.4.4-12.el7_3.noarch.rpmb136aa5b6825b1f0b210561a266b7b869737a9c47e662a768edf52ef4faae777samba-dc-4.4.4-12.el7_3.x86_64.rpm89f4a4210ed1ebe4c610984c4d57bf82296628c71f5d3a8d0c68a2a246967565libwbclient-4.4.4-12.el7_3.i686.rpm1bfbe30d1759255d790559fdafbb6b6e391cb9720bc3c04ac65f2f28aafb596elibwbclient-devel-4.4.4-12.el7_3.x86_64.rpm57c593fa4e20684b757c341bcb34e9ba70e91c179eb63f7495f0dc4f8a016ba8samba-vfs-glusterfs-4.4.4-12.el7_3.x86_64.rpm63f8ecd3b81e2b8340a649f1ea38a03acce6994da2ee14910816224cf208c5aasamba-client-libs-4.4.4-12.el7_3.x86_64.rpmfb78ab386eff87a5c38daecfaab2aff69d3780e3bc2e58de0d12c7b2a128dc4fsamba-krb5-printing-4.4.4-12.el7_3.x86_64.rpm03e97db159d9edf7a543bf41b68548d8d46c097e696f78b97765620f9ad43979libsmbclient-devel-4.4.4-12.el7_3.i686.rpm03ff383e3808939eb7575986137df93895e2e70a90e70f7a4d85f80bd6add27esamba-devel-4.4.4-12.el7_3.i686.rpmbeacb004f4c3a1376eb38784ebb4ddf504d6cb32e18279a883cd03b69c0d240esamba-test-4.4.4-12.el7_3.x86_64.rpm4bcc2f437b6fe33d83bf0dbc6870fb0a561a2c95dcb97b053523a7c6b7577d1esamba-winbind-4.4.4-12.el7_3.x86_64.rpm258c9fd3dd5795c00cf455ce78da5015a0fbe83ceb1352b96743cd932ee4edc5samba-client-4.4.4-12.el7_3.x86_64.rpmf6d89e52051e6f8be89bc426f86fb5b43a7671d99949fe5ff6badf838e568f0blibsmbclient-4.4.4-12.el7_3.x86_64.rpm57bc9626d02372bf085111f82d21626cb5da8e0a24c084a2e01711488d2b4178samba-common-tools-4.4.4-12.el7_3.x86_64.rpmb40dadf87438ddc2baf50f7330aa69835af1f9b4ce3f1e11e9b8fdee97134bc2libsmbclient-devel-4.4.4-12.el7_3.x86_64.rpm93a42275becb1411af9a0cf77c5db9d5384edcd4b29763767eb84b1f67f3e87fsamba-pidl-4.4.4-12.el7_3.noarch.rpm47bc6ae0c7bb8db48488a260de881b89f1af838f35d712a115c106e659ec2bc5ctdb-4.4.4-12.el7_3.x86_64.rpm0ca2ead6df7392ac578fef57bf7002d36b701e998207c3829f8d23d74d926856samba-winbind-clients-4.4.4-12.el7_3.x86_64.rpmc7e3b54fb2f9b9a7a613e951d4e357f1f3e39a6d55f2d5eac21b74d9acf8e9d2samba-test-libs-4.4.4-12.el7_3.i686.rpmcc97d35de6432fe2214b9b3ffb1a98cd72fc5c3e07274a530674c57c66b6826esamba-dc-libs-4.4.4-12.el7_3.x86_64.rpm56f63f379d8290553b6274ee211001a0d7240e25e57aa75654207415596bbd22samba-devel-4.4.4-12.el7_3.x86_64.rpmb4538b095c459f7b75542995c79c771f9cee129f13317197d550a815bdfffe61libsmbclient-4.4.4-12.el7_3.i686.rpm262a9c839ac669a78837dc3f1b590d79262c8e74e3941bbe42d568785a3cd355samba-libs-4.4.4-12.el7_3.x86_64.rpm396282bfb5e148aa50f5da82fbaad3bdbac23b3e92b252be480d8e6a3f9af228samba-winbind-krb5-locator-4.4.4-12.el7_3.x86_64.rpma5218fe1b7eb56defcd92bee66a0e54b173f915a6fd2762529a4cbed140b46dasamba-test-libs-4.4.4-12.el7_3.x86_64.rpmfa4cde282056050ebd387ca6fc4ad31bf805e792d62ddca1b836d132e5788a64samba-winbind-modules-4.4.4-12.el7_3.i686.rpm9497c3b17d20657de3ae9653521b1b15d08fa356aaa200dd6aa586a1334b5e8blibwbclient-4.4.4-12.el7_3.x86_64.rpm0c78beb0bf93a227833f13d7a1e65a9eff78d295f90224310b437358a5157380samba-winbind-modules-4.4.4-12.el7_3.x86_64.rpmd07aaa2d12d1cc5775ad78d5c2396f46574ee334eb9fe989a0aaef88cc8f2d95libwbclient-devel-4.4.4-12.el7_3.i686.rpm0c65055d246a2e5e041639fbad3d6495a9388c0b1ffca075f8f13aa8ca85c6aasamba-common-libs-4.4.4-12.el7_3.x86_64.rpm6b5a904cfe4060c2dbf67c378eda145cf9394de012757ebdc6ded86a2670627esamba-libs-4.4.4-12.el7_3.i686.rpm645beaa7a67a4e8bc4b632aa84314aef33039df76fd3aa4d695949610889beb8samba-python-4.4.4-12.el7_3.x86_64.rpm2a41897500dea1d4f35eec94488637623001eb1be385ffca79ad20c060b214f5samba-client-libs-4.4.4-12.el7_3.i686.rpmdfb9bcc550d50a37f298fd540c31799f602476c4a1ba98d0d3ff5ebb46703d89SLBA-2017:0070-1This update fixes the following bug: * Previously, converting the system clipboard contents to text did not work correctly. As a consequence, the spice-gtk tool terminated unexpectedly when clipboard contents could not be converted to text. The underlying source code has been modified to and the spice-gtk tool no longer crashes in the described situation.Scientific LinuxScientific Linux 7spice-gtk-0.31-6.el7_3.2.i686.rpme8379cde8539b6f4b6ed06802dc800dbf4a81117707a6a334f84e23031a26adbspice-gtk-python-0.31-6.el7_3.2.x86_64.rpmc641423d15c248878effd225dc19edb8ac847966155bb5d94cab764e10b4bd85spice-gtk3-vala-0.31-6.el7_3.2.x86_64.rpmada63f6f27733df21153eb88da6e06d65ed918f0d4259d085d166da98d93b763spice-glib-devel-0.31-6.el7_3.2.i686.rpm4b7f0208e96ea855b2926a5dae0eeabf998ed2ddb73ee7c52f2e7b6f28ee0d6aspice-gtk3-devel-0.31-6.el7_3.2.i686.rpm8f7515b3b44f816a26814b5a5c44b13aa883587c7a5a2afd19a84dab56533fdaspice-glib-devel-0.31-6.el7_3.2.x86_64.rpm4cec9c0ee2ae68a4f5c80956dff34026f90e925e7d5c43490b0bf740eb3bf54espice-glib-0.31-6.el7_3.2.i686.rpm0add77769fc974140b12c0fdc19e411990b74ee8e22ce99d210f062fdadc422fspice-gtk3-0.31-6.el7_3.2.x86_64.rpm14a5e757d172e35214202dd1e1f0a29988ea6811863325cf1ba88d806099967espice-gtk-0.31-6.el7_3.2.x86_64.rpm8fa1c82ad8bb931b990fbdddf89095e1c2e6dfa85510f79c1231fbbfa0ffcad1spice-gtk-devel-0.31-6.el7_3.2.i686.rpm26543fe8eca7611ea67f23e4c4b01f0a1223345d7a9707d773e8c2c7a462c711spice-gtk-devel-0.31-6.el7_3.2.x86_64.rpme8449ddefdbbcefa515a7027eecafd7ddfc2e7ab8f0eeb7e3129d42ee160084fspice-gtk3-0.31-6.el7_3.2.i686.rpm5aff05a320f4d747bc54814ca0eb6162caae641299c699a1e7b7877a2ccf1c3dspice-gtk3-devel-0.31-6.el7_3.2.x86_64.rpm8b01960c469317da47b2f2a496d0d142c4724fd80bf7034f02ca1e1a4b612077spice-gtk-tools-0.31-6.el7_3.2.x86_64.rpm01ffd6fcc6da8b311904062cde17de49c2dd3b05376ea6ea128a4d245bedf941spice-glib-0.31-6.el7_3.2.x86_64.rpm2611be6c8e8b499f8b23101714ee58a960d0eb425d2350177e45973bb221603fSLBA-2017:0071-1This update fixes the following bugs: * Previously, Scientific Linux 5.11 guests failed to shut down, and stopped at the "system halted" status. A patch has been applied to and Scientific Linux 5.11 guests shut down as expected. * Previously, using the qemu-kvm system_reset utility when no space was left on on the host caused the qemu-kvm service to terminate with a segmentation fault. The underlying source code has been modified to As a result, the qemu-kvm process stays active, and guest systems can be reset without an error. After installing this update, shut down all running virtual machines. Once all virtual machines have shut down, start them again for this update to take effect.Scientific LinuxScientific Linux 7qemu-kvm-tools-1.5.3-126.el7_3.1.x86_64.rpm3d90ea67a0c620d4570680074494c510f12a4e30f48a91171ed6786e81b177faqemu-img-1.5.3-126.el7_3.1.x86_64.rpmffab74c3f9d7827d5cda075348b2cdf2805cf95aabd8373d8fb4a69bd2a4605dqemu-kvm-common-1.5.3-126.el7_3.1.x86_64.rpmd3354663a074ddc0445999319a2638ae63fb29d447ea33f3a4a279929d9b6499qemu-kvm-1.5.3-126.el7_3.1.x86_64.rpm33ea163c44592b6149436b750aae290d8788373c58a2c9e6da5871cd1eb1c26aSLBA-2017:0072-1This update fixes the following bug: * Previously, the FreeRADIUS server exported symbols that were conflicting with symbols defined in the libltdl library. When the FreeRADIUS server tried to open a connection to the MSSQL server using the rlm_sql_odbc interface and UnixODBC was configured to use the FreeTDS library, the connection failed with the following error message: "undefined symbol: get_vtable" This update renames the conflicting symbols. As a result, connections to MSSQL servers no longer fail in the described situation.Scientific LinuxScientific Linux 7freeradius-mysql-3.0.4-7.el7_3.x86_64.rpmcf0189f229f73b0c71d730da550aa0bdde3d5d6824920a838dd7a32246145eccfreeradius-krb5-3.0.4-7.el7_3.x86_64.rpm8fe2e2af1a7d6b3240076226f344aa373b41759b4130dd930beb0b3a66f1ccabfreeradius-3.0.4-7.el7_3.x86_64.rpm3e6f0eecfa300fefc4a942781003c82246055b212dc3c8685778d6a6a1422cbafreeradius-sqlite-3.0.4-7.el7_3.x86_64.rpm63f055e6e0f46d894ed9bb740653bd8dc022b18e0f8175a19ae432071a4106d9freeradius-ldap-3.0.4-7.el7_3.x86_64.rpma36ce95a23ee612da20eeedf8d052598f0c37d5dd92a46df7d9a627c4c4a2d64freeradius-doc-3.0.4-7.el7_3.x86_64.rpm3011bebbc0dda5e4f1c23f54552f2dd1221540570c5464f12747aa3cad81cbc6freeradius-utils-3.0.4-7.el7_3.x86_64.rpm123fa95995d97ba9a3f5275c000c3b4b42f62854f3609fc6e88694409295fbc7freeradius-perl-3.0.4-7.el7_3.x86_64.rpmc0ea9a40ac2e7dbbff334c6e5dfa1800942a741932e5016d2175815de5226e8cfreeradius-unixODBC-3.0.4-7.el7_3.x86_64.rpm595cb839c0d1da54035fc4407b612515bfa68b73b8d4f05f0b2ff764923ea026freeradius-python-3.0.4-7.el7_3.x86_64.rpma3d7fe8b3fb170039fb0c6ccffac300d4e4cacecf71a61c781117815563047c7freeradius-postgresql-3.0.4-7.el7_3.x86_64.rpmefeb991743ef47890ae06250975989deee57ad8be332914ded96cbac8e42cae1freeradius-devel-3.0.4-7.el7_3.x86_64.rpm3d7d80472bed86f376ac08a2d023a69c23c9349672a39d2b550895e04c3130e6freeradius-devel-3.0.4-7.el7_3.i686.rpm57fecc75e8a8961d789bf7211e560f4286ce78f75b46fc93337422dd18b6a07bSLBA-2017:0074-1This update fixes the following bug: * After creating RAID4 logical volumes on Scientific Linux version 7.3, or after upgrading a system that has existing RAID4 or RAID10 logical volumes to version 7.3, the system sometimes failed to activate these volumes. With this update, the system activates these volumes successfully.Scientific LinuxScientific Linux 7device-mapper-event-libs-1.02.135-1.el7_3.2.x86_64.rpmee82f14fa2bfefe570985904f1966be619abe71fb31bca9113a649f1e835c46cdevice-mapper-event-1.02.135-1.el7_3.2.x86_64.rpm137e560f0f1ab9c9162f8bd3785e369df3cc51d2d0f516b1ed73bdd0a08dad79cmirror-2.02.166-1.el7_3.2.x86_64.rpm15534cf65589b271a3dd6ff3d55722bff377f3d7e8074cc50892ea8ba733f3c8lvm2-python-libs-2.02.166-1.el7_3.2.x86_64.rpm505044de37ec6c7bee781989a75d83dec18137fbab35436ee7dab639e911dd67device-mapper-1.02.135-1.el7_3.2.x86_64.rpmc9e30911620cfc021a8619203a3b787fc4631a1494a2b6ca36f5f3be5cb8127alvm2-cluster-2.02.166-1.el7_3.2.x86_64.rpm9245f35e171abfcf7d6003d78fd5ef4af019b41f2a68748a7f9d2ddc2bbd190adevice-mapper-event-libs-1.02.135-1.el7_3.2.i686.rpmf4a17b17d1d34245b95e0a614b64e0fdc44792a7d0fdbcf2238d0cd1b667523ddevice-mapper-libs-1.02.135-1.el7_3.2.i686.rpm6f333fdba1d1c67458acd7d44d2644523eef0148368eea34107ffd1ef8a282d9device-mapper-event-devel-1.02.135-1.el7_3.2.x86_64.rpm1e46e7311a9a26704973514b3e945a8c38e5365649acde9154404d64028091e7lvm2-sysvinit-2.02.166-1.el7_3.2.x86_64.rpm56c7007d09d5e1d7dd9f43e72d94f4ab9df3fe3185ea1945902effffaa65626bdevice-mapper-event-devel-1.02.135-1.el7_3.2.i686.rpmae79fdce690d17cd5080858b28377a441daa494c3b813f2f580d0f44413a6709lvm2-lockd-2.02.166-1.el7_3.2.x86_64.rpm00406b839c1838dc42836a7354de03b037d3769e00bd03b8dc2616e8b51046fblvm2-libs-2.02.166-1.el7_3.2.x86_64.rpm60b531cf9ca2d9302ceb695f2025cb8f0cdc969a109de5a6c146b2e7647b17aalvm2-2.02.166-1.el7_3.2.x86_64.rpm606cb313f57acd641e4770c0ff6f4442f78605ba4c9c3e275d6a464630111a9cdevice-mapper-devel-1.02.135-1.el7_3.2.i686.rpm34dfe5bd886c43ea13a7e5bb360338f2149bdcf4788fad1478ac95b54ebcfff3cmirror-standalone-2.02.166-1.el7_3.2.x86_64.rpmf751a9d8a1e8bf71c27b1bf8e43688145c6fa12af8762a735aee36fe14b42281device-mapper-devel-1.02.135-1.el7_3.2.x86_64.rpm6a7ba53aefd29923eff55b357d72af206fd2c03e820846a1136085a3c193f481lvm2-devel-2.02.166-1.el7_3.2.i686.rpma39e1bce2672149d2d265cc5435b31bffec844c8d997d8067c384b5bd4ea83f2lvm2-devel-2.02.166-1.el7_3.2.x86_64.rpm7f5a467126c07189a831f48bf698607e2054c4c8ee3aa4eea09c2fc82b2d35b6device-mapper-libs-1.02.135-1.el7_3.2.x86_64.rpmb1c85f16f346de4072210bb21c9c177d6238904e68ca4c8c96303563e99152ealvm2-cluster-standalone-2.02.166-1.el7_3.2.x86_64.rpm84c31fa246c274a0a840bb113df2ee448c5bbba064687986c6c6822a28fdc0aflvm2-libs-2.02.166-1.el7_3.2.i686.rpmaefbb9af312565ff9cb8e111e88c39e823887aabbd1624789faefd87dfcce558SLBA-2017:0075-1The policycoreutils packages contain the core policy utilities required to manage a SELinux environment. This update fixes the following bugs: * In Scientific Linux 7.3, the semodule tool did not show module versions. Consequently, tools such as Puppet, which expect module version in the output of the "semodule -l" command, stopped working or worked incorrectly. The libsemanage and semodule tools have been fixed to return a module version. If there is no module version available, "(null)" is printed. * Previously, the "semanage fcontext -m" operation returned "OSError: No such file or directory" and failed to modify the target file context. A patch has been applied, and the exception is handled correctly. As a result, it is possible to modify the file context with the "semanage fcontext -m" command.Scientific LinuxScientific Linux 7policycoreutils-newrole-2.5-11.el7_3.x86_64.rpme83076880039e17a3db277f4548810b9de7fad94baac7ef2ce7f6a003648db80libsemanage-devel-2.5-5.1.el7_3.x86_64.rpm4cb9d57fac99d07e8ebf156ddf8df8d19b2a0fbf161c2f5ee4696db612853475libsemanage-static-2.5-5.1.el7_3.x86_64.rpmf1c09957fd49505c5f7f211eaccc47c808776acb26e0d87f86ccbf27426f0680libsemanage-2.5-5.1.el7_3.x86_64.rpm8ebde6b0bebd6fb091849718a03fad21c22fa2798c53cf73621c704e09cd2de6policycoreutils-devel-2.5-11.el7_3.i686.rpm0da3d81a33a2d9023d632b0991ea210276918e27077bde3c4e2a3cd05a6e0c67policycoreutils-2.5-11.el7_3.x86_64.rpm7633906501e8bd241303981ed368f891bc22cb9700c4279e67b4d77d1103fb52policycoreutils-restorecond-2.5-11.el7_3.x86_64.rpm7e14f66808f4d855f8e1522f29d6041b3d41d26f154a9a9cfc796397209d9675policycoreutils-python-2.5-11.el7_3.x86_64.rpmfcd4b0d1f44d8dea1b5dd3cb3a7fbcdbda5872bcf105f16e7d0e38f73243bfeflibsemanage-static-2.5-5.1.el7_3.i686.rpmdcb75da130107d8a1be8e8d0b45c7717c997a2cbd695d1cd25d9a231652a176dlibsemanage-devel-2.5-5.1.el7_3.i686.rpm5bd808b2ba40cea21886f059ad74afd64bfc6ecc22e079febeff9db25f83560cpolicycoreutils-gui-2.5-11.el7_3.x86_64.rpmbe659058e20fde76285823f8fe64b603965d93880d933d9799c6ae3277a33407libsemanage-python-2.5-5.1.el7_3.x86_64.rpm782c3af04b22598fb5f63e2099554075c9ed58f5ed7b853ea62a3f4fcb316e75policycoreutils-sandbox-2.5-11.el7_3.x86_64.rpm9d20f37582c9dbb0a9f659e9ccd612752764548eef625474b39f84acdff41127libsemanage-2.5-5.1.el7_3.i686.rpmf3d81cb799d225536d4dd516fc57e3949a71b1ddc2284d47f52f23b25f80803epolicycoreutils-devel-2.5-11.el7_3.x86_64.rpma52c42440f7c05c519291be35f07c3d0249740048c3f3093af2c2798998fc105SLBA-2017:0076-1This update fixes the following bug: * Previously, when a Ceph RADOS Block Device (RBD) image was exported using multiple iSCSI targets, the RBD kernel module set an exclusive lock when it received a write request. As a consequence, if a write request got unresponsive in the RBD module, and the iSCSI initiator and multipath layer decided to fail the request to the application, read requests sent after the failure did not always reflect the state of the write requests. With this update, the RBD module sets an exclusive lock for both read and write requests. This causes hung write requests to be flushed or failed before executing read requests. As a result, read requests sent after failed write requests always return the same data.Scientific LinuxScientific Linux 7device-mapper-multipath-libs-0.4.9-99.el7_3.1.i686.rpm13e8bf4a7ac3fa1f7ed8ca94e339033cfcef87b65baa649565cb569da41d45dckpartx-0.4.9-99.el7_3.1.x86_64.rpm02d5fed26276e1ba79e01e9cb7aa35f5574f8e2b5435e02fc3093f2abf7940a4device-mapper-multipath-sysvinit-0.4.9-99.el7_3.1.x86_64.rpmb9649a1a8753f41e63f54022917ad940d24d7659667b47665055b7f603b396f9device-mapper-multipath-libs-0.4.9-99.el7_3.1.x86_64.rpm225d873f5546445302c0318a67a030ba1ce25963a6fbeeff0e4a7fe8e0c5529ddevice-mapper-multipath-0.4.9-99.el7_3.1.x86_64.rpme07e1cebe3519cb2871c85caca6e7afae1fa7cc9fcfa0b8a6ab7d5a8aae1e68aSLBA-2017:0078-1This update fixes the following bugs: * Due to an update in Scientific Linux 7.3, in a case-insensitive domain, the sudoUser attribute only matched the lowercase version of the LDAP user or group name. As a consequence, configurations using case-insensitive sudoUser attribute values failed. This update re-enables SSSD to match the sudoUser attribute regardless of case and now both lowercase and case- sensitive can be configured. * Previously, the System Security Services Daemon (SSSD) only used the domain name set in the /etc/sssd/sssd.conf file to match found entries if multiple entries matched the search result. Consequently, if two users with the same sAMAccountName attribute were present in two nested Active Directory (AD) domains and the domain name set in the /etc/sssd/sssd.conf file was different than the AD domain name, SSSD failed to resolve supplementary groups for these accounts. SSSD now uses the domain name set in the configuration file and additionally the remote domain name. As a result, secondary groups are now resolved correctly. * Previously, if the "ipa" or "ad" subdomain provider was set in the /etc/sssd/sssd.conf file, the System Security Services Daemon (SSSD) accessed only data that the respective authentication provider sets up. As a consequence, if the user configured the "ipa" or "ad" subdomain provider with a different authentication provider, SSSD accessed uninitialized memory and terminated unexpectedly. A patch has been applied and SSSD now only accesses data if the same authentication and subdomain provider are configured. As a result, SSSD no longer fails in the described scenario. * Previously, the Security Services Daemon (SSSD) did not store group names and group member names correctly if the ldap_nesting_level parameter was set to 0 in the /etc/sssd/sssd.conf file. As a consequence, resolving group members or group names failed. A patch has been applied to fix the problem and as a result, SSSD now works correctly in setups have the LDAP nesting level set to 0. * The System Security Services Daemon's (SSSD) cache in Scientific Linux 7.3 uses a different format to store user and group names than previous versions. SSSD automatically migrates the cache when the service is started after updating to Scientific Linux 7.3. However, on clients with a large cache, the migration can take a long time and as a consequence, the SSSD process watchdog terminated the process and the service failed to start. This update disables the watchdog for the "sssd" process and as a result, large caches are now successfully migrated and SSSD starts correctly. * Previously, if the System Security Services Daemon (SSSD) failed to contact the autofs LDAP data provider, the autofs responder did not return data that was already cached locally. To fix the problem, the autofs responder has been updated and as a result, SSSD now returns cached autofs data if the LDAP server is not available. * Previously, if the socket that the System Security Services Daemon (SSSD) uses to communicate with the DNS server was writable and readable, and additionally an error occurred while processing the first event, SSSD accessed freed memory and the service terminated unexpectedly. A patch has been applied and SSSD now processes both events using the same resolver callback call. As a result, SSSD no longer fails in the described scenario.Scientific LinuxScientific Linux 7libsss_simpleifp-1.14.0-43.el7_3.11.i686.rpmbd9ad04fb2c11684413d02941613e685c537682c5458eda08754f27c152173e5sssd-polkit-rules-1.14.0-43.el7_3.11.x86_64.rpm9e6377cbf453712e3bc5b60a4ee37d7f4b05b7a883024e7365e8288d309f6131sssd-common-pac-1.14.0-43.el7_3.11.x86_64.rpm5195a67b084b0b0f6a2301f9f7fe5b7e26428db86134a6cc9d67fc5693e2b6c1libipa_hbac-devel-1.14.0-43.el7_3.11.i686.rpmfff4e08d837e6d33ff792cb587fe95a6a9bf5ec92a0df142df7b8b65d54f08f0sssd-winbind-idmap-1.14.0-43.el7_3.11.x86_64.rpm87e2b80f4e20116754023cce3566fe3afa58ad3f50f623c43241357538a2b4eclibsss_autofs-1.14.0-43.el7_3.11.x86_64.rpmf5fee64adc39875c8f4587674f3767afe486f41178a9f3a1d34ebd4a81c28c47libsss_nss_idmap-1.14.0-43.el7_3.11.i686.rpm6cfb47ec971411d8256fff3e2e5e73561cf9e64769f795d1b55c4526ab36a3f3python-sssdconfig-1.14.0-43.el7_3.11.noarch.rpma86eea59b14771c076992f2b9814fdf977410fd13c4e43aef55e593d09f25af4python-libipa_hbac-1.14.0-43.el7_3.11.x86_64.rpm425edcef3e05746c63c9969994d93804da0205027fa3d3dd39b3794907638d65libsss_nss_idmap-devel-1.14.0-43.el7_3.11.i686.rpme8be9d01fc6c0ff73992df300a67ca59e190e7ddca9c4ca9b3ecfa59ffdf5ce9libsss_idmap-devel-1.14.0-43.el7_3.11.i686.rpm486af108f9c49e2bf7b9995aa3c6552a0a408495e01832138d20cf4af6f7bbb1python-sss-1.14.0-43.el7_3.11.x86_64.rpmb80631eda3943974a617c247413087178f1803843de8d6296f8597001c688dfesssd-ipa-1.14.0-43.el7_3.11.x86_64.rpmd4da9977c8d581eea3138aee9fa663bcfbc2b4ec22c374158284636168b86934libsss_idmap-devel-1.14.0-43.el7_3.11.x86_64.rpm3db620d67948c6de38be9eaa5142d99f0b3dbc6424a61e8bc5c96ce117e0bc49sssd-krb5-1.14.0-43.el7_3.11.x86_64.rpm537bfe7ca46c2ff4df554a97c2b37dbb0cb1e2e4ba1bc17050e536299b07db89sssd-krb5-common-1.14.0-43.el7_3.11.i686.rpm889346147a52f8cfabe1ec671a5010dbda10bc0f653e12eeaa87d1a78d2b16f8python-libsss_nss_idmap-1.14.0-43.el7_3.11.x86_64.rpm5a2985b436a7878f8d237701a3ba61c2b80d66c532f7a7d591d3800ec7964b9asssd-libwbclient-devel-1.14.0-43.el7_3.11.i686.rpm8a6a715a6bb23047af3c9d8ab8539c301afd8f4f6bbadd1b2314a8ea7a04cb2blibipa_hbac-1.14.0-43.el7_3.11.i686.rpm15f701e9781a71dbd814ab8ab9d574b99dc2a72afd872184ae3bfebd3ddc492clibsss_simpleifp-1.14.0-43.el7_3.11.x86_64.rpmfe0d118c0b651e162bc87b156768cbb5bac080e196c78f18cc18bf65eabd1b81sssd-1.14.0-43.el7_3.11.x86_64.rpm80d124dc469df48a52da3221ded559beed623323c493e8e4669ee1dcbd760c36sssd-libwbclient-1.14.0-43.el7_3.11.i686.rpm016a9053082d59e81a58fa5b96e35b9136ebe27f61f5647bba9c0eaf126e471flibsss_simpleifp-devel-1.14.0-43.el7_3.11.i686.rpm6af681eab8fde3a9818e389edc134e76cab7dd477f0a32f601c4f67890d50874libsss_autofs-1.14.0-43.el7_3.11.i686.rpmde99982463df2b385f77b201a355eff8a06f78afbad6ee2762ef0678f5921b7dlibipa_hbac-devel-1.14.0-43.el7_3.11.x86_64.rpm3ca26420d071cbd6ac119d7f58008e78ff9025a4bb526dc391914e072251f4bbsssd-libwbclient-1.14.0-43.el7_3.11.x86_64.rpm402a422ba00fb4df09a604fc92954cd6c89b09422a59351009a5e31e063a37edsssd-krb5-common-1.14.0-43.el7_3.11.x86_64.rpm4cc05ca30f119989cfbc1083409dce26e178d82684c8d78ea7a6f9931eda91f1sssd-libwbclient-devel-1.14.0-43.el7_3.11.x86_64.rpm877e6b61ef07246dce2107eae1db0b3710334385b282124f1434c702aacd1d89sssd-tools-1.14.0-43.el7_3.11.x86_64.rpmd036c6e0c2e877994b107cf5a592f734baeb80cb4f9e7d78a85d7d9953857b86libsss_idmap-1.14.0-43.el7_3.11.i686.rpmd7f879a42767c58c6874feaebf5df4718bd4770a994ec350748888a616883076libipa_hbac-1.14.0-43.el7_3.11.x86_64.rpmb07ca1807df03b989a43e6db7dedf7dcdb7b51f47f0168c3c012b860436ee76blibsss_idmap-1.14.0-43.el7_3.11.x86_64.rpmb2e40f9288224ada0b5d0bd0524a63bf2e470c369d79aee091bda04ae46cdadbsssd-common-1.14.0-43.el7_3.11.x86_64.rpma7baa393c8c3f249ff78657cfa745fdca4dd3f2ba971efd871fde5281c7c839asssd-client-1.14.0-43.el7_3.11.x86_64.rpma5287b5852555d7f3701a171b69fe005ffcdc19f16453736118d1b01c2ff189alibsss_nss_idmap-devel-1.14.0-43.el7_3.11.x86_64.rpme151eae704add792e08f2b8e76a909faf97146f3c751730c85f3a79559ac740bsssd-common-1.14.0-43.el7_3.11.i686.rpm8b2efac6791179d7c57018cafb1064ad8bad2aefff8e2ea781f898cb77f4ef4clibsss_nss_idmap-1.14.0-43.el7_3.11.x86_64.rpm67250ce483f04d91fe45288cd700ba350b1cb5cf386ff3c0ee705797d110b3afsssd-dbus-1.14.0-43.el7_3.11.x86_64.rpm63dd22fb2f56406967b22b8e340b0bdb054773fdfb8e68afe8adb7e89bd73aa7libsss_simpleifp-devel-1.14.0-43.el7_3.11.x86_64.rpma88818002a0ba0b939aa3125cf55422e915c7ce5edfcb35432e9aea56acb7f01python-sss-murmur-1.14.0-43.el7_3.11.x86_64.rpm748f5dcbd7b2c8752266351818603f3b3e015ff7828e65b002fa5ca001446ef5libsss_sudo-1.14.0-43.el7_3.11.i686.rpm5c247bb3b0e3abc4d347c2757859ab77421c54f79b3053902eac917d655b466csssd-proxy-1.14.0-43.el7_3.11.x86_64.rpm51ac8cf632da7861316b27723a3956a17e2231bb9b60336e68a359c75449ef7fsssd-client-1.14.0-43.el7_3.11.i686.rpm9aa6aeafcc3b71f6bd99ca8f58c763fa0e00d0329b365b6925b52532ed9ab447libsss_sudo-1.14.0-43.el7_3.11.x86_64.rpmcf68e36f4d21e73d70135985c8f762d2ac3dbddf7dd5cda5bb57e53bd27f1f3fsssd-ad-1.14.0-43.el7_3.11.x86_64.rpm6f628810ad47ca4dd2e14784f91521b11f5057e5e7136de459324d89dded427dsssd-ldap-1.14.0-43.el7_3.11.x86_64.rpmce29ab87b2047ba5d9325bb6644f0cbb1bf1a9320bd084ffd386f151876cc48aSLBA-2017:0079-1This update fixes the following bug: * Due to a Windows bug that caused incompatibility with SeaBIOS, Windows 10 RS1 and Windows Server 2016 guest virtual machines running on the KVM hypervisor were unable to generate the kernel crash dump. The bug has been fixed, and the update ensures that Windows guests are compatible with SeaBIOS. As a result, the kernel crash dump can now be generated on these guests as expected.Scientific LinuxScientific Linux 7seabios-bin-1.9.1-5.el7_3.1.noarch.rpmd95018d6e9506cc993976bfff9583440f81e31f3050adb8961e4afbee2fc773bseavgabios-bin-1.9.1-5.el7_3.1.noarch.rpmc7e414e328877fbcffd5c5744cce98885d4b080feaacad134b55b8c349ad89a8seabios-1.9.1-5.el7_3.1.x86_64.rpmcb16824fee15932c14ac5c8de21c6d250b933dec4fc27661e4d731e959469872SLBA-2017:0080-1This update fixes the following bug: * Previously, due to a bug in the code that underlies command substitution, the Z shell (zsh) terminated unexpectedly after reallocating a token string. This update fixes the bug, and zsh no longer crashes in this situation.Scientific LinuxScientific Linux 7zsh-5.0.2-25.el7_3.1.x86_64.rpmbd728bd475cd3c48f7ef44f9515303dc2d0327da13d4dda8edd1a597498d70f1zsh-html-5.0.2-25.el7_3.1.x86_64.rpmb7ceb9fe96308da8879ecb584a4765fd1552bbe1fb21a4edaaf67ade6e0d4c9fSLBA-2017:0081-1This update fixes the following bugs: * In Scientific Linux 7.3, the chroot setup in OpenSSH did not work properly. Secondary groups of users in chroot were not correctly initialized, and capabilities were trimmed for these users. The chroot setup was fixed to match earlier behavior, and groups and capabilities of users set up using OpenSSH chroot now work as expected. * Previously, a race condition in an Audit-related part of the OpenSSH code was not fixed properly. As a consequence, OpenSSH clients were unable to connect to servers with large Message of the Day (MOTD). The Audit- related part of the code is now executed before sending the MOTD, and the client connections work even if the server sends a very large message.Scientific LinuxScientific Linux 7openssh-server-6.6.1p1-33.el7_3.x86_64.rpm936f377e99a39b0f81e4cf520e48c83d2965247baadcfaedd49df3c7dae1704dopenssh-server-sysvinit-6.6.1p1-33.el7_3.x86_64.rpm840dc67839eb8b34d1cb67a467c8f8f38d55866d9d196e10d3f20f41e16fcffaopenssh-clients-6.6.1p1-33.el7_3.x86_64.rpm964dc1c88afa2f0b681fe359aabfca0a822f78f5f128ed0bcc4dc1c16709169fpam_ssh_agent_auth-0.9.3-9.33.el7_3.x86_64.rpmd95c12d014a9e86e146059340b8a14b26114abab261598c3c16447b336370da1openssh-keycat-6.6.1p1-33.el7_3.x86_64.rpmdd4d3f31bce917dcbc97c5fde3a04d0483b58f60165c57bb2fab225f9246a495openssh-ldap-6.6.1p1-33.el7_3.x86_64.rpma69eb6629c0a24d2e68c1e79a5cda1b93eaf3afd2033c4145797649043b8db34pam_ssh_agent_auth-0.9.3-9.33.el7_3.i686.rpm37e9b07c9ded91cd3d99c49e56a0b28a61d08c690e173027b872aa268a1ef7b8openssh-6.6.1p1-33.el7_3.x86_64.rpm00da91c231cabe0a2f23ca1f9e1b82ac5011d3e4878431c45bf4980de4dad1f3openssh-askpass-6.6.1p1-33.el7_3.x86_64.rpm6e25473cca262fbc2187b04e6751f2311b3f0f04b58604cdca3a4d14df564c0eSLBA-2017:0082-1This update fixes the following bug: * Previously, the X.org server failed to start on machines with 32-bit PCI domains. A PCI domain does not need to be limited to the 16-bits. The Linux kernel currently supports 32-bit domains, which cause the startx utility to fail with segmentation fault. However, updating libpciaccess to support 32-bit domains breaks the library's application binary interface (ABI), and domains that require 32-bits are not necessary for startx. Therefore, this patch ignores these domains, and the problem no longer occurs.Scientific LinuxScientific Linux 7libpciaccess-0.13.4-3.el7_3.i686.rpmab4370816ae4faea2677466c1472c1408b64ebafb31890cf3dbd5e75e57a15f8libpciaccess-devel-0.13.4-3.el7_3.x86_64.rpm626eb3d455e245f48d78c2fa85d4b47cc63925e43ad987de68df55708202ca9flibpciaccess-0.13.4-3.el7_3.x86_64.rpm058ed89467956ba9981fc5791ebfc78320e957590af2c5a95ade596f5414902elibpciaccess-devel-0.13.4-3.el7_3.i686.rpm57ec0a0d743713670b49dbc7646bb9cefdaec10d88a7e5b697e2e3d2a0709b19SLBA-2017:0084-1This update fixes the following bugs: * In Scientific Linux 7.3, SELinux denied communication between the Puppet configuration tool and the D-Bus interface when using the timedatectl command. The selinux-policy packages have been updated, and Puppet can now run timedatectl. * Prior to this update, SELinux policy was rebuilt during online update. Consequently, updating the selinux-policy-targeted package using Yum failed with a traceback. The selinux-policy migration script has been fixed, and the selinux-policy update now works properly. * Previously, a rule for the Clustered Trivial Database (CTDB) was missing. As a consequence, SELinux denied successful finish of a CTDB failover. The transition rule for the "ctbd_t" domain was added, and a CTDB failover now succeeds. * Due to a missing SELinux rule, when two nodes of a Red Hat Gluster Storage (RHGS) server were restarted, the Pacemaker tool stopped services on all nodes. The rule for the "glusterd_t" domain has been added, and SELinux denials no longer occur during an RHGS server restart. * Due to missing policy rules, SELinux denied running systemd in a container. The rules to allow containers to write to "unix_sysctls" and to use file descriptors leaked to them from parent processes were added, and the SELinux denials no longer occur. * A missing SELinux rule was previously causing errors when adding a webhook using the gluster-eventsapi command. The rule to allow "glusterd_t" domain binds on glusterd UDP port has been added, and adding a webhook using gluster-eventsapi now works properly.Scientific LinuxScientific Linux 7selinux-policy-targeted-3.13.1-102.el7_3.13.noarch.rpmb43767b05bcf186be03fa48659bc090379b0c61f178aa9cb3093d1939e709adfselinux-policy-devel-3.13.1-102.el7_3.13.noarch.rpm22a8a01fb8f88928bd9f625005a2196a1d3715e87f039e4f1d187ecbda1c8be4selinux-policy-minimum-3.13.1-102.el7_3.13.noarch.rpm0f8a47dc70be8019f77da959f7d2cc1c1f29ef5c47029004ecac73462e21618eselinux-policy-3.13.1-102.el7_3.13.noarch.rpmd26b277ea7d60e3036623a103373ee870559c2efa1c50dbe3d067e4dcaa6fdd2selinux-policy-mls-3.13.1-102.el7_3.13.noarch.rpmf7be20580fca5d29baf27a1d7c1f23247b148bcfd9809366a53bc9b9e873255aselinux-policy-sandbox-3.13.1-102.el7_3.13.noarch.rpm20aab101c5f0d14220e6637fb62c97372b778d2d2763bd6ab36ced714f4e1d8fselinux-policy-doc-3.13.1-102.el7_3.13.noarch.rpm690d1c9ca97d4436ac6ebb0081c7b241c9259419b1ae4c95fee2dfaec81b9873SLBA-2017:0085-1This update fixes the following bugs: * When replicating NIS maps from a Windows NIS master server over a low- quality connection, ypserv in some cases did not transfer the masterOrderNum value, and the slave server used the UNIX timestamp value instead. This sometimes caused a variety of problems, including migration failure and data corruption on the slave server. With this update, masterOrderNum is not set to the UNIX timestamp value when the transfer fails, and ypserv reports an error. As a result, replication from the Windows NIS master server to the slave server works as expected. * Previously, when migrating a NIS database over a low-quality connection, migration sometimes failed due to the use of an incorrect file handle when processing the ypxfr_foreach request. This update ensures that ypserv uses the correct file handle in the described scenario, and the migration thus succeeds as expected.Scientific LinuxScientific Linux 7ypserv-2.31-9.el7_3.x86_64.rpm3750193943ea113a2825f2768b0e4ca5c430837e30c65f0ba1b1fdd9391560b0SLBA-2017:0087-1This update fixes the following bug: * Due to a race condition, a reshape of an Intel Matrix Storage Manager (IMSM) RAID array previously became unresponsive at 0%, 1st checkpoint, if the reshape started immediately after a resync was completed. With this update, the race condition has been resolved, and a reshape completes as expected in the described situation.Scientific LinuxScientific Linux 7mdadm-3.4-14.el7_3.1.x86_64.rpm79761118b1cea208587ac6844d983ae690acd21bfaade479ce6d11197f8b8566SLBA-2017:0088-1This update fixes the following bugs: * Previously, deleting a non-tombstone entry failed when the generated tombstone was added to the cache. This update fixes the bug. As a result, deleting non-tombstone entries now works correctly. * Previously, when the master ran into missing change sequence number (CSN), the replication entered a fatal state. This update enables you to configure how Directory Server handles missing CSNs. For further details, see the solution provided in the references. * Previously, nsEncryptionConfig schema definition diverged between Scientific Linux 6 and 7. This was due to the schema learning mechanism not merging schemas with the consequence that replication failed. This patch adds the nsTLS10, nsTSL11, and nsTLS12 attributes to the list of allowed attributes in the Scientific Linux 7 Directory Server's schema. As a result, the replication from Scientific Linux 6 to 7 now works correctly. After installing this update, the 389 server service will be restarted automatically.Scientific LinuxScientific Linux 7389-ds-base-snmp-1.3.5.10-15.el7_3.x86_64.rpm4982262302fc6a4d138ce46c3a5817191d456cd85389b7d21550a3e24c9afe38389-ds-base-1.3.5.10-15.el7_3.x86_64.rpm8044d5786d30df47bb6855831ee5af5aba30c0e9fcd5ded164e7e31ed51677ad389-ds-base-devel-1.3.5.10-15.el7_3.x86_64.rpm14f1da4b9adaef8b50c6f55e25de9a3ac9ef34d1d452826718f5bbb830185d56389-ds-base-libs-1.3.5.10-15.el7_3.x86_64.rpmc643f05c68696a3152d0451aadd77f6e7962250688ec3a8fb7949f55261ef7afSLBA-2017:0089-1This update fixes the following bugs: * Previously, a bug prevented new Identity Management (IdM) certificate authority (CA) replica installations to update the CA master. Thus, during the CA replica installation, the temporary CA admin entry could not be submitted to the remote IdM CA master server. Consequently, the CA installation on the replica become unresponsive when polling the master indefinitely for this entry. The code that configures the CA replication on the remote master has been fixed to set all attributes required for the correct evaluation of access rules. As a consequence, updates from the CA replica to the master now work correctly and the CA installation no longer hangs. * The Identity Management (IdM) server upgrade procedure failed to detect if the DNS service on the host is managed by IdM. As a consequence, while upgrading an IdM replica that was installed without the DNS back end, the "named-pkcs11" service was restarted and the upgrade failed. The DNS installation status code has been fixed and now verifies correctly if IdM manages the BIND configuration file on the replica. As a result, upgrading IdM on a replica without DNS back end works correctly. * Previously, an Identity Management (IdM) 3.0 master on Scientific Linux 6 rejected IdM 4.0 and later replicas running on Scientific Linux 7. When installing the replicas, some attributes were not added to the replica config entry during the initial replication. Consequently, for example in migration scenarios, adding a Scientific Linux 7 IdM replica to an existing Scientific Linux 6 IdM master failed. The replica configuration routines have been updated. As a result, IdM now falls back to a Scientific Linux 6-compatible mode during the initial replication in the described scenario. * Previously, if an Identity Management (IdM) upgrade ran simultaneously on multiple servers, replication conflict entries were sometimes generated in the "cn=topology" subtree. If the domain level was raised while the conflict entries existed, the generated topology segment was sometimes distributed between correct and conflict entries. Also, one-directional segments fail to receive the data. As a consequence, IdM clients and commands fail. A patch has been applied to reject raising the domain level if replication conflicts exists. As a result, topology segments are created now only in a database without conflict entries.Scientific LinuxScientific Linux 7ipa-server-4.4.0-14.sl7_3.4.x86_64.rpm852517cecbb2ebe6dc445926756ddd8a80ac9b4c250078263fc893a954cb6eadpython2-ipaserver-4.4.0-14.sl7_3.4.noarch.rpm82f452866948b9377e96ffce646822b4e0e6e24c1ae07b55bf961bd488c9db4bpython2-ipalib-4.4.0-14.sl7_3.4.noarch.rpmb05e5a329825494fc0d0fecb156bea21a9f3ba2ba8994bf297865f7f7a780809ipa-common-4.4.0-14.sl7_3.4.noarch.rpme75f55c0bfe7e81dc416d057d11e15eb3e8ac7f4ad154abd9a12d1667ffb5490ipa-server-trust-ad-4.4.0-14.sl7_3.4.x86_64.rpm2db7a685aa850e573a9cbd68cc49fabebaa284013cedba369bb8dafb75218949ipa-admintools-4.4.0-14.sl7_3.4.noarch.rpm5c32e770b201def1ae39872c3d8cde364b7ab20823650c9e015297dfe9cf769apython2-ipaclient-4.4.0-14.sl7_3.4.noarch.rpma25a72a7d39da5c86b86ff05c10e44d364e7e02fa4cbdcf9c240276f327b4841ipa-server-dns-4.4.0-14.sl7_3.4.noarch.rpmcb02c0f76a28115486d255601c1d059190b0579c50594565f5b4738af48df54dipa-server-common-4.4.0-14.sl7_3.4.noarch.rpm3fa0d17cbf259442bf40dfbc93cbf5f6ac362ba88d848814fc5db0cd04d79639ipa-python-compat-4.4.0-14.sl7_3.4.noarch.rpme375355eb424bf372fa59e55e93c0cac4696ef9ec9443225f017c327e8f19a39ipa-client-common-4.4.0-14.sl7_3.4.noarch.rpme7d061ec6920bd166e418c6571dc71b017797cf7b2d4f96240dcf5631253ce14ipa-client-4.4.0-14.sl7_3.4.x86_64.rpm8aea2740fd6200527a1dbaf69aa1877f801eaa0a8a581d3d8e6212432b4f4a29SLBA-2017:0090-1This update fixes the following bug: * Starting with Scientific Linux 7.3, XFS file systems are created with the Cyclic Redundancy Check (CRC) feature enabled by default. Rear did not previously consider this change in behavior, and formatted the /boot partition with an incompatible UUID flag, which caused the recovery process to fail. With this update, rear checks for the CRC feature, and properly preserves UUID during recovery.Scientific LinuxScientific Linux 7rear-1.17.2-7.el7_3.x86_64.rpmeadebe2310c069b9c0b6534d6af304a077aaf92719a31bd4ba376b5abdbf686eSLBA-2017:0092-1This update fixes the following bug: * Previously, when the udev helper utility was renaming a networking interface, NetworkManager occasionally confused interfaces due to a race condition. Consequently, NetworkManager assigned wrong MAC addresses. With this update, NetworkManager does not access an interface before udev finishes the renaming, and this problem no longer occurs.Scientific LinuxScientific Linux 7NetworkManager-glib-1.4.0-14.el7_3.i686.rpmc4c75a81b12b4a6cd14c2967b6b1f16ba59e3e27fc65fa6a2c08d479667731e1NetworkManager-glib-devel-1.4.0-14.el7_3.i686.rpma8ada5049b667c6b797e59da5e3afd572a034bb8f483662c7df36733f1e86b30NetworkManager-1.4.0-14.el7_3.i686.rpm770f2beb4db012742b5a0e90b9b4930ef977c8c8553507fa464011c9efa88af1NetworkManager-libnm-devel-1.4.0-14.el7_3.x86_64.rpm55a7ddb4d727d999c17eedbd8126eae6bd5138c5bd4e5e0241ea566c1d6021e9NetworkManager-1.4.0-14.el7_3.x86_64.rpm70fe614adc7766e0e3f2932e1f295d9de26adc9d45ad364010af7e4e97a2de30NetworkManager-glib-devel-1.4.0-14.el7_3.x86_64.rpm4beb33973bd70a0b0cb208c33d1e4af477cb45ee2199e41ca01701f1c1613496NetworkManager-wwan-1.4.0-14.el7_3.x86_64.rpm80e8c26cebe3d70e01bf115805d5743fd5e4b8d46d560d03b006bcfcaa5f617fNetworkManager-bluetooth-1.4.0-14.el7_3.x86_64.rpmae30dd48fabe6e01e618543a485e457747b25ba2c4ece35ee818afb45c9c917eNetworkManager-glib-1.4.0-14.el7_3.x86_64.rpm8f161dfe162d480e540939f8bf982ee001090d4b68debf67baf2acbcb5f222bbNetworkManager-adsl-1.4.0-14.el7_3.x86_64.rpmf75fa8af931a2bbc97215736b67aee3e1e74fb95dea5e250d522cc2d5453d581NetworkManager-team-1.4.0-14.el7_3.x86_64.rpm3629fe9844feae8c77f447a216f6b1414a158aff0dddc3a757f057844c3ed5ccNetworkManager-dispatcher-routing-rules-1.4.0-14.el7_3.noarch.rpmcc3252207830574006fbb8db67ae9b3a3c2f2073ad0050a00b3c1641bd4f7acbNetworkManager-wifi-1.4.0-14.el7_3.x86_64.rpm579fb7894f817579ffdda40fede017f3ff294a787839e403099a132870338d57NetworkManager-tui-1.4.0-14.el7_3.x86_64.rpm358a921f216cf0845cdc988e0a9eb9211d8722c483331dacfae8b02370ac6ae8NetworkManager-libnm-1.4.0-14.el7_3.i686.rpm7928db83c21a183e24b330f9565144bc249a435e132453ea401089a5b8ca1466NetworkManager-config-server-1.4.0-14.el7_3.x86_64.rpmc523594df6bc8ede3950eb5c936d13a4b036582bfb77ae03410a552af2538bbfNetworkManager-libnm-1.4.0-14.el7_3.x86_64.rpm794e082cf1529dab35de5b2477f5abb0e3535e33c94b9b88da9e4263688b6cb7NetworkManager-libnm-devel-1.4.0-14.el7_3.i686.rpmf770ed6790f3c7ba6cc8f630ebd86472becdeefc3c00d1b73fa052c7deb47f80SLBA-2017:0093-1This update fixes the following bugs: * Previously, subordinate certificate authority (sub-CA) installation failed due to a bug in the Network Security Services (NSS) library, which generated the "SEC_ERROR_TOKEN_NOT_LOGGED_IN" error. This update adds a workaround for this problem to the installer which allows the installation to proceed. If the error is still displayed, it can now be ignored. * Using the "pki user-cert-add" command with the "--serial" parameter previously used an improperly set up SSL connection to the certificate authority (CA), causing certificate retrieval to fail. With this update, the command uses a properly configured SSL connection to the CA, and the operation now completes successfully. * Previously, menu items grouped under the "System" menu in the Token Processing System (TPS) user interface were determined statically based on user roles. In certain circumstances, the displayed menu items did not match components actually accessible by the user. With this update, the "System" menu in the TPS user interface only displays menu items based on the "target.configure.list" parameter for TPS administrators, and the "target.agent_approve.list" parameter for TPS agents. These parameters can be modified in the instance CS.cfg file to match accessible components.Scientific LinuxScientific Linux 7pki-tools-10.3.3-16.el7_3.x86_64.rpma1f351a9b17a7c295d1695eef8137a5742aec60c7796366a9b68aa17d339044fpki-server-10.3.3-16.el7_3.noarch.rpm70da2afd45068893430ad869ff4b053e31c3bc44ad5a79f94fe843ef70aeb6c2pki-ca-10.3.3-16.el7_3.noarch.rpmf7624782613de3f0a644e1985b9346b6dae83290a546e127be27d919da9bbf0dpki-kra-10.3.3-16.el7_3.noarch.rpm7affaf8695325ecda4795c7712e7436ce27bf2fdd6048fedb2a74f1af6a53322pki-base-10.3.3-16.el7_3.noarch.rpm9a2e477418d279a97db22c284a3f3b9e3283268cb9cb33b0a2bb93f171db9cebpki-javadoc-10.3.3-16.el7_3.noarch.rpmd7300de03be161f92b58335ddc3ea947cdee9abf222817d9819f686b1181571cpki-base-java-10.3.3-16.el7_3.noarch.rpm616160370c0367dcf99849773ab9ea73e5dba239b5ae3a2fb1f808519fc5e1b6pki-symkey-10.3.3-16.el7_3.x86_64.rpmc20a5dc5d1007ac656b32ff911b929c17c62231f40155fab615fc435425d5558SLBA-2017:0094-1This update adds the following enhancement: * With this update, the coolkey package now supports using the Gemalto Cyberflex Access 64k V2c in Common Access Card (CAC) configuration. As a result, users can now use this card with Scientific Linux 7.Scientific LinuxScientific Linux 7coolkey-1.1.0-36.el7_3.i686.rpm9e869054427e166ee86397565c7a054cf624632ab9476f9ecb5ec4cc18fc1ba1coolkey-devel-1.1.0-36.el7_3.x86_64.rpm466b1023ce748dabfa15a2014dc73933c8511f91cf10de91b3a0211cd7ce46f4coolkey-1.1.0-36.el7_3.x86_64.rpmae475e095529dc8a8a43dc2bcbf9c069ef869b249d1ac77861129a2774768a59coolkey-devel-1.1.0-36.el7_3.i686.rpm16c25a7207a069dd59da5abbd07b9c1a8ddc068b48cea62cc89af291176b1d7bSLBA-2017:0095-1This update fixes the following bugs: * Prior to this update, the virt-who agent did not respect the interval setting. Consequently, the traffic to configured entitlement servers increased. The bug has been fixed, and the virt-who agent now sends updates less frequently than is specified in the interval setting. (#BZ 1405618) * Prior to this update, when connected to the VMware ESX/Vsphere virtual machines, the virt-who agent on virtual machines reported having no universally unique identifier (UUID). This caused unexpected behavior in configured entitlement servers. The bug has been fixed, and the virt-who agent no longer reports virtual machines from VMware ESX/Vsphere which do not have a UUID.Scientific LinuxScientific Linux 7virt-who-0.17-11.el7_3.noarch.rpmec49a94ea45f92840d41ce9370b9dd422c9d78b67bd10bdeb8ec6ec052d14bf4SLBA-2017:0096-1This update fixes the following bug: * In Scientific Linux 7.3 release, the Internet Content Adaptation Protocol was disabled by mistake after the squid package rebase. To the build option has been enabled again. As a result, the Internet Content Adaptation Protocol now works as expected. After installing this update, the squid service will be restarted automatically.Scientific LinuxScientific Linux 7squid-3.5.20-2.el7_3.1.x86_64.rpm5ab19088bda9236544d7bcfa34d820f853a57acc38228b3a838df502ea665568squid-migration-script-3.5.20-2.el7_3.1.x86_64.rpmdd35d3acf82d506ebee29a38a98a2bac37c69f02bbafdb9a91567fdbd531b9f0squid-sysvinit-3.5.20-2.el7_3.1.x86_64.rpm75946b3275a454a9b02ba1927dc9e740b15facc84d6506fc94260506bd9f9da7SLBA-2017:0098-1This update fixes the following bugs: * Previously, the libvirt library was using wrong set of commands on the QEMU monitor, when trying to hotplug vhost-user interface to a guest. As a consequence, the hot plug of the vhost-user interface failed. This update corrects the hot-plug code for vhost-user devices. As a result, the hotplug now succeeds as expected. * Prior to this update, the libvirt service was not able to attach vhost- user type interface to running QEMU machine. To fix the bug, an implementation has been introduced to libvirt that enables it to attach and detach vhost-user type interfaces. * Previously, when taking a live snapshot, the libvirt service attempted to acquire an already locked sanlock lease. As a consequence, the live snapshot failed to be captured. This update improves the code that tracks whether the virtual machine needs to be resumed after the snapshot. In addition, the update prevents the code acquiring the locks from being invoked if not necessary. As a result, the described problem no longer occurs. After installing the updated packages, libvirtd will be restarted automatically.Scientific LinuxScientific Linux 7libvirt-daemon-driver-lxc-2.0.0-10.el7_3.4.x86_64.rpm5f3fb7d4de39ef114364548794daf7fb1e06675cb46a95ad5346bce5d8fc8d59libvirt-docs-2.0.0-10.el7_3.4.x86_64.rpm31510afa465f0ed34faa00b3dc45099f9819d66eafcbb3b5c4645df962af7e57libvirt-login-shell-2.0.0-10.el7_3.4.x86_64.rpmf9131fd5de815bc7130b2a8c64343ffb66aec839443c66c0d5a9e31dee392891libvirt-daemon-driver-nwfilter-2.0.0-10.el7_3.4.x86_64.rpm7832d1e0aad53e70af590480cf6b72a1f6f8a14b3efa4497fcf7bfdfa2ea25aclibvirt-lock-sanlock-2.0.0-10.el7_3.4.x86_64.rpm3a49ac4a1376ace7be9b2f350c035b06be0ab6f60913180967f9f75fbe92e42alibvirt-daemon-driver-qemu-2.0.0-10.el7_3.4.x86_64.rpm9f311ef4467de5c1e85aa92281327ba0452ccfef6932c0ba1e803809cf4d97ddlibvirt-daemon-driver-nodedev-2.0.0-10.el7_3.4.x86_64.rpm78f963c15ba921ef44757070627a2aabd73926c019852a5afe95244e76b81697libvirt-daemon-config-network-2.0.0-10.el7_3.4.x86_64.rpmd161d5d9ad9888fa55b60a0ac8154d2e8ebb03a5d5e32c7de3e585d3dad14886libvirt-daemon-config-nwfilter-2.0.0-10.el7_3.4.x86_64.rpma249a0a85a2b2ece2061d02ce7f3aef65ee2d7bb71d314e6be43aba69b333b9alibvirt-daemon-2.0.0-10.el7_3.4.x86_64.rpm99dd38eec62e11bc1f92be8666749c067d3a37b0de50e96dc9f730fc2e4286c9libvirt-daemon-driver-secret-2.0.0-10.el7_3.4.x86_64.rpmf504e9ffd1f0d3b1acff9fe90597df5473e968d7c85dcb86d97cbab363773a42libvirt-client-2.0.0-10.el7_3.4.i686.rpm7b30dfed0c86327c96840b8b5af9858149cd2bdf39eacd98b3f9b4adc5714436libvirt-daemon-driver-storage-2.0.0-10.el7_3.4.x86_64.rpm75a19120d10fc6de56e2ee9dafecad29baeeb93215955b441c1013517806a6f6libvirt-devel-2.0.0-10.el7_3.4.i686.rpm843819b3c51b26ad9dce59c4b7b48f719d297161a505a41a56ae4f01c24288felibvirt-nss-2.0.0-10.el7_3.4.i686.rpm68549a17d15fc17f7782a62c1ad806a873d9d369c36129b2983593e7cb65cfbblibvirt-daemon-driver-network-2.0.0-10.el7_3.4.x86_64.rpm9a311639a7eeaa26492746e0fe949421674ea55b9a2c7cc67e7d9d9d36ea27f8libvirt-2.0.0-10.el7_3.4.x86_64.rpm69088997fd66f41a95efe86dee876c5f59e44d6f8b2a6ddc1998f395ac5cefa7libvirt-client-2.0.0-10.el7_3.4.x86_64.rpmb342d174afb9faf6b6789b6d7aede83b3b69305cf3448a1e1c65f72b571aca50libvirt-daemon-driver-interface-2.0.0-10.el7_3.4.x86_64.rpme2f9f09ad54a8e7c7adc931f4c01dcd41939508ef5e2c7316840b22a1d264a75libvirt-daemon-kvm-2.0.0-10.el7_3.4.x86_64.rpmf89357bd1dda5969b9589852b1a96cd95f9ca2a57fd48f13c10e6939525d24d7libvirt-daemon-lxc-2.0.0-10.el7_3.4.x86_64.rpm4b51041cfb11aa0e201fb0e03c39b6376e331a0fee0fd3850ccb4ebee5e7012dlibvirt-devel-2.0.0-10.el7_3.4.x86_64.rpmbc78aeff2144c390807e777dbee6deef30ae165ab9c2891b304ddcac143885b3libvirt-nss-2.0.0-10.el7_3.4.x86_64.rpmf59340880bebc0d556b82054eb0af97b12ea140b902f0e50b2359697f0d08dccSLBA-2017:0099-1This update fixes the following bugs: * Previously, the libguestfs library did not recognize guest operating systems when the /usr/ directory was not in the same partition as root directory ( / ). As a consequence, the libguestfs tools did not perform as expected. With this update, the libguestfs library recognizes guest operating systems when the /usr/ directory is not located in the same partition as root. As a result, the libguestfs tools perform as expected. * Previously, the virt-v2v utility rejected the import of Open Virtual Appliances (OVA) without the <ovf:Name> attribute. As a consequence, the virt-v2v utility did not import OVAs exported by Amazon Web Services (AWS). To virt-v2v now uses the base name of the disk image file as the name of the virtual machine, if the <ovf:Name> attribute is missing. As a result, the virt-v2v utility now imports OVAs exported by Amazon Web Services. In addition, this update adds the following enhancement: * The virt-v2v utility now exports disk images compatible with qcow2 format version 1.1 when using the -o rhev option. In addition, virt-v2v adds the --vdsm-compat=COMPAT option for the vdsm output mode. This option specifies which version of the qcow2 format virt-v2v uses, when exporting images with the -o vdsm option.Scientific LinuxScientific Linux 7libguestfs-rescue-1.32.7-3.el7_3.2.x86_64.rpmaecea62c078fbf527a2d2a64ce8b978d094a145a4dcaa9d7470974695cdc0626libguestfs-rsync-1.32.7-3.el7_3.2.x86_64.rpm655da7992da236d745df23d94ba1873586d048b65944159a063f86823545f333ocaml-libguestfs-1.32.7-3.el7_3.2.x86_64.rpm726c99564bb02ebd6aebeda195f672919370204991e71b94781a0e9b5faaad8elibguestfs-man-pages-uk-1.32.7-3.el7_3.2.noarch.rpm221bf933fd80417c986e2c4e5ae3315c32c31bc735710bf856b719e45b2f11d7libguestfs-gobject-devel-1.32.7-3.el7_3.2.x86_64.rpm27448c1503b8db1b1f381cc2612f955645c2495fb320bdf7f9cbfa9d095e4fb7libguestfs-java-1.32.7-3.el7_3.2.x86_64.rpm2731bcc901ec837a3be2876d2a061b5f8dee20b9bed775f42deb4249108f5191libguestfs-gobject-1.32.7-3.el7_3.2.x86_64.rpm84bf491c452252060c0caff87e8982fbae29de0f4f79cb1156b76b5622e54787libguestfs-inspect-icons-1.32.7-3.el7_3.2.noarch.rpmd5e98cb21e01f388a108488c522efc887ca9a6e6ba78732578da59e8542576f6perl-Sys-Guestfs-1.32.7-3.el7_3.2.x86_64.rpm16ef0fcbcd5edc9f8bd4cfc643921f6bb007163706c6a8df977f4168d466a0a7libguestfs-tools-1.32.7-3.el7_3.2.noarch.rpm5a1be37561d33edb8bf4353cbccb17934f574186960d927f4dfdd088a0002c2clibguestfs-1.32.7-3.el7_3.2.x86_64.rpm2538e6752f1ec681e38da01342f623cfd9d2015554be5e247e1039580e2c910bvirt-dib-1.32.7-3.el7_3.2.x86_64.rpm450aa192b78683cbe6ca495f8343da73e5d911c91c71a7a265f8fbe479b7f307virt-v2v-1.32.7-3.el7_3.2.x86_64.rpm6ae932c1b819f93651b3301f318c48791697123c7f8778f0fb5aab649d04e45blibguestfs-java-devel-1.32.7-3.el7_3.2.x86_64.rpm257f32ea219d5e16952a55a62b17c72f365c6d4a928b508e069d149087da1ca6libguestfs-gobject-doc-1.32.7-3.el7_3.2.noarch.rpm5f60624a1822e626ecabf2bb318ba485c1459b01b2675d4253badf9324072514libguestfs-javadoc-1.32.7-3.el7_3.2.noarch.rpm22f70ccc8761bd28c87ff4503973509f0bdb12eac8be755b292c8211138727ecruby-libguestfs-1.32.7-3.el7_3.2.x86_64.rpmcba50f8ae972097edcd2d03edbf919a87b25c81e4af6605521df028ea8c796b1ocaml-libguestfs-devel-1.32.7-3.el7_3.2.x86_64.rpm189e29b8c38dd876ec28d15aad9e925ccd9e2a8e92ae36f17d1f8d5e28c3b9bclibguestfs-bash-completion-1.32.7-3.el7_3.2.noarch.rpmbf23805502f98e97fd64ad46558393db92cc8c5a1dab432b72bd446c2aafe745libguestfs-man-pages-ja-1.32.7-3.el7_3.2.noarch.rpm8a3469343475e5cafd7d2882137271d2a7ad4759f6b505bef3f72d78fc32f481libguestfs-tools-c-1.32.7-3.el7_3.2.x86_64.rpm9af4940a2d19793ad5a1a5e9886e0c7d24b1ea4ae7363d26b8d5be05c22fe681lua-guestfs-1.32.7-3.el7_3.2.x86_64.rpm541993b8922a183160ecd281517767c49a33da975cd66194eec9baca9311300bpython-libguestfs-1.32.7-3.el7_3.2.x86_64.rpm60ef9ae5b860a6b0e945e8432d71107c4cc3128e8adf1c062ad6ee3931e57c6flibguestfs-devel-1.32.7-3.el7_3.2.x86_64.rpm7a1eb47039f8aba9742250596425707a9de4a80caca7ee561c7aa53350164156libguestfs-gfs2-1.32.7-3.el7_3.2.x86_64.rpme34312e8bc6eea38d86026e318ec7c9948b3c4ad79541e713e6f220f3355a593libguestfs-xfs-1.32.7-3.el7_3.2.x86_64.rpm0faad9dee3f57ab9376ea9e59a3f3696ffd8accdd1b302d32239053f51711674SLBA-2017:0100-1This update fixes the following bug: * The xfs_repair utility is currently unable to correct an extended attribute leaf that contains 0 attributes. As a consequence, runtime errors from the kernel occurred when the attribute was accessed in the described condition. With this update, xfs_repair removes the empty leaf, and runtime errors no longer occur in the described situation.Scientific LinuxScientific Linux 7xfsprogs-devel-4.5.0-9.el7_3.i686.rpm7d03b8693e6e6d13c29d1338d4d6f2a94c9848cfda17d4257fa93abd4e42d5fbxfsprogs-4.5.0-9.el7_3.i686.rpm220a185592a72c1b4e40e950c20d4edc5d68b8e1b807b16fd318e12a9f8db510xfsprogs-4.5.0-9.el7_3.x86_64.rpme95cdf0431993ff84fcbea8c15d726c01323985ee090726021d8211596ec630dxfsprogs-devel-4.5.0-9.el7_3.x86_64.rpmd1e11b58e35c0a1bb087847655db08a70b1b68995c8f7a0a39f41867faa7c737SLBA-2017:0101-1This update fixes the following bug: * Previously, the portblock resource agent did not use the -w parameter of the iptables command. As a consequence, the portblock resources randomly failed when several resources were running at the same time. The bug has been fixed. As a result, the portblock resources wait for other iptables actions to complete, and no longer fail. (#BZ1409513)Scientific LinuxScientific Linux 7resource-agents-3.9.5-82.el7_3.4.x86_64.rpmdcd38b3b3c9516133f1a2efc27cf9a86622ca351f51121bc8e2870355759c8d6SLBA-2017:0103-1This update fixes the following bug: * Previously, firewalld created the ifcfg backup file with the OLD extension when the ZONE setting of an interface with ifcfg was modified by the firewalld D-Bus interface or the command-line tools. As a consequence, the ZONE setting in the ifcfg file was set to a blank value by firewalld on reboot if NetworkManager and the network service were both enabled. With this update, firewalld creates the ifcfg backup file with the BAK extension, and the ZONE setting remains correct.Scientific LinuxScientific Linux 7firewall-config-0.4.3.2-8.1.el7_3.noarch.rpmd79a407010d7e48d8383043515d5b7ed43d75fb7c9990df14873578daabae3d8firewalld-0.4.3.2-8.1.el7_3.noarch.rpmcd429c3c0fa1a95911200416760e5b519df61d2b0df559129ecd6a0fd52fb678firewall-applet-0.4.3.2-8.1.el7_3.noarch.rpm21024cec91f11b24b439238e095fb22ff9d7f1a0065d49755c68a8371436023apython-firewall-0.4.3.2-8.1.el7_3.noarch.rpme3de0e57498b224fd7935f2ec80f86d1628531dc32e4f4da9b564e550eb7be4dfirewalld-filesystem-0.4.3.2-8.1.el7_3.noarch.rpm39f6f66424a614928702d7ca1d394ed2b8e5e1327e8dc25734d34e519a6fa566SLBA-2017:0104-1This update fixes the following bug: * Previously, the libnl3 library used a fixed buffer size by default, resulting in the loss of messages larger than this size. In certain cases, this prevented the libvirtd daemon from starting. With this update, the default behavior of the libnl3 library prevents messages from being lost this way, and libvirtd now starts correctly.Scientific LinuxScientific Linux 7libnl3-doc-3.2.28-3.el7_3.x86_64.rpm7693d8c131141f7bf72813a1ab996ce38a5dc31bb4bb8cd75dbea2e9c4d3ad47libnl3-devel-3.2.28-3.el7_3.i686.rpm38b09510e401c3477cacb644ae7d581d7fa8c3eb3278d758d890be900b1ce6c4libnl3-cli-3.2.28-3.el7_3.i686.rpm24d95e40ce5995ccd76c791b74639901379e2068c14c0dcaeaddb5413a8211a2libnl3-3.2.28-3.el7_3.x86_64.rpmb3b27b51691f9dc04958e822831ffbe978f3d436a17536335b28606777f28de4libnl3-devel-3.2.28-3.el7_3.x86_64.rpm3e598ce0a5718d02fd2e8c4ff124fcf720bfabf3405e0519218d73ad5cd916b5libnl3-cli-3.2.28-3.el7_3.x86_64.rpm7be9019e9645aa122cc9c77876f6f8489e56faa245842481f56d8853bcedecealibnl3-3.2.28-3.el7_3.i686.rpm5e2e7603a92af524f89478a9867b530c44c8a369c2271ed4e8793cc5bf39b802SLBA-2017:0210-1This update fixes the following bugs: * Previously, the pcs utility did not recognize names of resource agents based on systemd services that support multiple instances, because these names contain the "@" character. As a consequence, an attempt to create a resource based on such a name lead to an error. This update fixes the validation of systemd resource agent names. As a result, these names can be used for creating resources and the error no longer occurs. * Previously, the pcs utility only offered an option to replace the entire contents of Cluster Information Base (CIB). Consequently, a race condition leading to data loss could occur. With this update, it is possible to change the CIB only partially. As a result, concurrent changes are no longer overwritten and this bug is prevented.Scientific LinuxScientific Linux 7pcs-0.9.152-10.sl7_3.1.x86_64.rpm4885efcc24909f8cd7b3a23c63cd922f47ccb97887db1b968abf7cb042430426SLBA-2017:0371-1This update fixes the following bugs: * Previously, there was a bug in the way systemd handled resource limits. As a consequence, setting resource limits failed, displaying the error "Failed to parse resource value, ignoring". This bug has been fixed, and systemd no longer fails when setting resource limits. * Previously, there was a bug in the add_random function in systemd. This caused systemd to terminate unexpectedly under certain circumstances. This update fixes the bug, and systemd no longer crashes in these situations.Scientific LinuxtrueScientific Linux 7systemd-libs-219-30.el7_3.7.i686.rpmc6ab54f9ca8fcda6092e62be4bb3e9c89af1fca59187c769cb23ed86a2166f67systemd-resolved-219-30.el7_3.7.x86_64.rpmf85aa32e0d03ea88eb99be0fb91c3b9919b1227bc97221047708e60b3dc18b19systemd-devel-219-30.el7_3.7.i686.rpmf94a8218b50b16862fba03c2afc3e7097b33469afa50e0078dc4cc72ed58fccalibgudev1-219-30.el7_3.7.i686.rpm2925b4dd5800239c10eee8a5065ee4f9985c803693d7b7c028a39a4cbcc15f65systemd-devel-219-30.el7_3.7.x86_64.rpmcfe1b5d735496618528e0c28ddb2120c228632ca552d606472fbb9d839451336systemd-resolved-219-30.el7_3.7.i686.rpm96cc45b15daa77e4bf6f9057a5b9a3d3a63a7801f1f38c59c93cc4257a6d2a66systemd-sysv-219-30.el7_3.7.x86_64.rpmda463c97d4e34312ff1e12181ba02ec1cc5f80d2c9f93c71dac734adf4a39306systemd-libs-219-30.el7_3.7.x86_64.rpmaab92d9ebd7b67216af44616ceb038d8131d7ad2d0f71338cd6b0d3aba07f335libgudev1-devel-219-30.el7_3.7.x86_64.rpmada0c64eabab4f0bd017b575d1c83b6f13e4b5a73230cc62c5353fb64ef38615systemd-networkd-219-30.el7_3.7.x86_64.rpmab1a00b6445137a8f511a06fc45a91449cbb9550bf97ac767b9c7a1863ce5a72systemd-journal-gateway-219-30.el7_3.7.x86_64.rpm66426ff71ad1f3404c0c9ddf9b7665dd7d633d45b7ca94e2699aec22484e2964systemd-python-219-30.el7_3.7.x86_64.rpm10ee36957445b39560a072d22a03271ffbb4f0e12ae46b3733e44c4953badbfblibgudev1-devel-219-30.el7_3.7.i686.rpm9dce3c51d713e4c7d65c83240724ab1eb7588a343575dfc121022b0c2fce9c0alibgudev1-219-30.el7_3.7.x86_64.rpme5bf94fced8f4d225bb99fa4a744d55d5310c140b1e4713b53831bd22fc44e8bsystemd-219-30.el7_3.7.x86_64.rpm47342a3f0d72142888f9fa2f3b54231c5c24a751216d71230c0a363f2ccad159SLBA-2017:0373-1This update fixes the following bug: * Previously, a bug caused the systemd initialization system to launch the wpa_supplicant utility with duplicate "-u" and "-f /var/log/wpa_supplicant.log" arguments. With this update, the bug is fixed, and systemd no longer launches wpa_supplicant with duplicate arguments.Scientific LinuxScientific Linux 7wpa_supplicant-2.0-21.el7_3.x86_64.rpm0fb2133ff012907e0192430a800d4dc2867848a322761ac1394cab3f3f771ff4SLBA-2017:0374-1This update fixes the following bug: * Previously, there was incorrect quoting in the "ExecStart" line, which caused the microcode.service systemd service to fail. This update removes double quotes from the ExecStart line, and microcode.service now works as expected. Note: a system reboot is necessary for this update to take effect.Scientific LinuxScientific Linux 7microcode_ctl-2.1-16.3.el7_3.x86_64.rpm144cf861720c830e48e7817b0ebd7a8401311182b9d3d7ab557cda3395819740SLBA-2017:0376-1This update fixes the following bug: * Previously, systemd failed to mount the rpc_pipefs file system because the /var/lib/nfs/rpc_pipefs/ directory was not yet created by the systemd- tmpfiles service. With this update, systemd-tmpfiles runs before the mount. As a result, systemd now mounts rpc_pipefs as expected. After installing this update, the nfs service will be restarted automatically.Scientific LinuxScientific Linux 7nfs-utils-1.3.0-0.33.el7_3.x86_64.rpm3410d553ea16650e3ef925c07d4922c99560e818051f5910d4f98ff69e825869SLBA-2017:0377-1This update fixes the following bugs: * Previously, when creating a Team, Bridge, or Bond slave, NetworkManager wrote the Universally Unique Identifier (UUID) of the master connection to the ifcfg file. This was not compatible with the legacy network service that supports only using the device interface name. With this update, NetworkManager attempts to write a device name in addition to the connection UUID, and compatibility with the legacy network service has been improved. Note that only UUID is used in case NetworkManager is not able to resolve the master connection into a device name. That is currently the case when slave connections are added before the master connection is saved in the nmtui tool. * Previously, after a restart of the NetworkManager service, a connection with an already-set DHCP_HOSTNAME property was duplicated. Consequently, a DHCP lease was not always renewed upon its expiry. With this update, the connection is no longer duplicated, and a DHCP lease is correctly renewed in this scenario. * Prior to this update, NetworkManager did not respect a specified order of added IPv4 addresses. Consequently, a primary IPv4 address could inadvertently change. The bug has been fixed, and IPv4 addresses are now applied in the correct order.Scientific LinuxScientific Linux 7NetworkManager-libnm-devel-1.4.0-17.el7_3.x86_64.rpm629a1494fed75ea174dc5d9b2e8d851a999a3c249cfa134e8a4468d52b3a46d8NetworkManager-wifi-1.4.0-17.el7_3.x86_64.rpme86a1a0f0e1e7cec33bbc31575ab21d337bef5353391eee259f1924bdd72865fNetworkManager-libnm-1.4.0-17.el7_3.x86_64.rpmfeeb89b53ebb1bd1bf23e4faf893dbb44283b2d5a01f4be01b445cdb2a340d1aNetworkManager-wwan-1.4.0-17.el7_3.x86_64.rpm262ecb9bb36d5091cc80280cbcfa71c8326792efcc95ddc485d7c2294ec82d19NetworkManager-bluetooth-1.4.0-17.el7_3.x86_64.rpm6f9d65dc4e86989b25456d115393629193629a02014dfb280161388e32eb9953NetworkManager-dispatcher-routing-rules-1.4.0-17.el7_3.noarch.rpmd4ad6babe8af71ebb8c0aa4d3cb0c640fb608b6568e772fcb9da8828095c6c06NetworkManager-glib-1.4.0-17.el7_3.i686.rpma05b0782cbd2d7718e81e5d4dfb9c00413783e358413849f543cd72158734aebNetworkManager-team-1.4.0-17.el7_3.x86_64.rpm5a646ae88faf34ef432ee55e8b18fdfda8b013221dd5afbca07169b3a9b5542fNetworkManager-libnm-devel-1.4.0-17.el7_3.i686.rpm62f85495feae0a5b15a7fe23396326c82aaba7c5da30ced104b5a85c59726681NetworkManager-adsl-1.4.0-17.el7_3.x86_64.rpm6a484577df2220c18082af4fdbfe65cee51c9c16cdd138d942f25431a19724d0NetworkManager-1.4.0-17.el7_3.i686.rpm92a8fed653276af6ac0df955e04d668a7033885426d5c83b4b11bf865a437ac9NetworkManager-glib-1.4.0-17.el7_3.x86_64.rpmc46344e0c6fa9945a1c62f4c77e483f8cf7fb9d2f668fb6a2ac3aaa26d28cbf1NetworkManager-1.4.0-17.el7_3.x86_64.rpmb94ee4a56230e2e7fdaab7108bbb9ca3f83bb69bf5830b4ad010bfc47f997559NetworkManager-libnm-1.4.0-17.el7_3.i686.rpm647a2a27c3abece9741e48adb9411cddc3e830ac703259ebb2f40e2cae4ce43bNetworkManager-glib-devel-1.4.0-17.el7_3.x86_64.rpm2e9ee5542e8d29659ede1bf106439702c84dec56cc82eff84b5f720eeca8a24bNetworkManager-glib-devel-1.4.0-17.el7_3.i686.rpm726b4a64be1d521024e0ad0ed74ba6287efdae2344ef333914d63b166bd62ef0NetworkManager-tui-1.4.0-17.el7_3.x86_64.rpmbfe4d6e8ff63ec59e244cdd306536ddc89fdfa116971ed705f0782515b670602NetworkManager-config-server-1.4.0-17.el7_3.x86_64.rpm166860a34a5ac193dac9a7b401cb077cf447f5b8c1529900f58e5cdc8b1e7a91SLBA-2017:0378-1This update fixes the following bug: * Previously, the Emacs editor tried to save its environment state from being overwritten. Consequently, when loading the state, Emacs terminated unexpectedly with a segmentation fault. This bug has been fixed, and saving its environment state no longer causes Emacs to crash.Scientific LinuxScientific Linux 7emacs-filesystem-24.3-19.el7_3.noarch.rpm71342c562931e8d0f7aa67262ee023dc0477e8252671108e608bb3b837a3aba1emacs-nox-24.3-19.el7_3.x86_64.rpmbf85b86b0b145161da70eb1d7bdb5b085b3f883f1c735fbdf438e81d491917f0emacs-el-24.3-19.el7_3.noarch.rpm56847651f21b4df19e2da5977fbd8c17379c591947ffb7e39175a8f2d628ea4cemacs-common-24.3-19.el7_3.x86_64.rpm4633ec5d401a688a3d1537e1e0058980a098a3405b6ec21dde024ecd848db944emacs-terminal-24.3-19.el7_3.noarch.rpmac75bd20869e0569fcd7b68e9a88c7bc28edd2f5c092c2a4c789288a228e2fd4emacs-24.3-19.el7_3.x86_64.rpm02baca4fe57d9632aeb767bc0a18daa1dc023793727ae0106f6cf77a222aa688SLBA-2017:0379-1This update fixes the following bug: * Previously, converting a postscript file to PDF in some cases caused the ps2pdf utility to terminate unexpectedly with a segmentation fault. This bug has been fixed, and converting postscript to PDF no longer causes ps2pdf to crash.Scientific LinuxScientific Linux 7ghostscript-doc-9.07-20.el7_3.3.noarch.rpm4c0dfefb1b87460743f75b367922bece20ddf524a7dcbf198fed4b8b4ff41cdcghostscript-devel-9.07-20.el7_3.3.i686.rpm7137cca8715e97f30b83c197016d86277ff3be6941dba5ca47148c1690a4d503ghostscript-devel-9.07-20.el7_3.3.x86_64.rpm085a05c2fbcd7f3355aa09c80291d3df622144578867447c71072e4fbb8f400fghostscript-9.07-20.el7_3.3.x86_64.rpmad5445f35b36786663f2a661dc22aff86f35b48efa44be8cc588372d753ab112ghostscript-gtk-9.07-20.el7_3.3.x86_64.rpm5242edfe69513c55ff590c7b2e910e4a54829e54bca13e602fed31d866bd6b05ghostscript-cups-9.07-20.el7_3.3.x86_64.rpm19aeaf571a025056f7af35f8f90061309a396ed44080c2e698d8eeaa07fd853fghostscript-9.07-20.el7_3.3.i686.rpm69933d1221d934bc84863dc2dc6b26e3dd1ee6e578fc1ddef139171b36630414SLBA-2017:0380-1This update fixes the following bug: * In a case of a successful scan of an incompliant system, the oscap- docker command-line utility incorrectly reported an error. With this update, oscap-docker correctly assesses incompliant systems and prints which rules did not pass the scan to the evaluation results.Scientific LinuxScientific Linux 7openscap-engine-sce-devel-1.2.10-3.el7_3.x86_64.rpm8f28b28437bb0b43e2f7792a7a81cb57121de5c1179108c499c65c8f29dc1531openscap-engine-sce-devel-1.2.10-3.el7_3.i686.rpm6deb604eb37001e09c58d065182854e5ab37262aea3c580ecdcb284c26727d56openscap-extra-probes-1.2.10-3.el7_3.x86_64.rpm8e29ec522b23c47d2a16dbd39435e2b825834820b22f3c935cce2790e8234463openscap-1.2.10-3.el7_3.i686.rpmfcbfd250595a57d65a9254669fd399c302c87c48394de9cadee5219679407ed1openscap-engine-sce-1.2.10-3.el7_3.i686.rpmbc7fed5c2258c373ab4ce3fb0ae2c2ac1a237d8ec1a300fb03bf2a8a564ac94eopenscap-utils-1.2.10-3.el7_3.x86_64.rpm16818ff53684677e25e7c3a28ad393a677932466cc3d930c8ecda06e668c9277openscap-python-1.2.10-3.el7_3.x86_64.rpmcb81d586377047a48ae3e53113e4fcfc1ef38621b3282d8cba78293a07bf570copenscap-scanner-1.2.10-3.el7_3.x86_64.rpm6a82bb6ec1023b78081f7064b5c5703884ce0ac472df9a7fdd552071aea51acfopenscap-devel-1.2.10-3.el7_3.x86_64.rpmf6a169c00f171bc76d3fbf5237926de059f38008333a48dfafd13d7e8a0d4b5dopenscap-1.2.10-3.el7_3.x86_64.rpm89d43c5b88948646008b9aaeb8c9d63aa5a73267eadebb9b5dbc60bfd1907c75openscap-devel-1.2.10-3.el7_3.i686.rpm12062ce6c4e99656b1f38751c6dea0ab11e9df6789391ec5a7cdf72d21e285eaopenscap-engine-sce-1.2.10-3.el7_3.x86_64.rpmd24860a2d616e4a1814fe79dcff7dd3a1b03d7b53709494bdf2a19696bd870a6SLBA-2017:0381-1The motif packages include the Motif shared libraries needed to run applications which are dynamically linked against Motif, as well as MWM, the Motif Window Manager. This update fixes the following bug: * Previously, navigation with arrow keys did not work in drop-down menus. With this update, the underlying source code has been fixed, and using of arrow keys to navigate in drop-down menus now works as expected.Scientific LinuxScientific Linux 7motif-static-2.3.4-8.1.el7_3.x86_64.rpmdbff87c5cd963d299b1df5ee2cd2765658bfb5600e74b7a81aa18e014222b52dmotif-static-2.3.4-8.1.el7_3.i686.rpm6c15061edd53eb39dce39e7569694e0d686c327aaa61c59d05f44c0805ae42f5motif-2.3.4-8.1.el7_3.i686.rpm2a0d1c9ddc0eeca2dedcb841ec70954a5294da282e0a847c8882e9e7a679a065motif-devel-2.3.4-8.1.el7_3.i686.rpm113c341a41212bbdbde05fbb167b48c019f452c13604d19905fb8f936cbed0a9motif-devel-2.3.4-8.1.el7_3.x86_64.rpm7a90dbfe4854a9d18054091de156f73e844e81cb777111e274ae08f899890372motif-2.3.4-8.1.el7_3.x86_64.rpm92aa775b3ffd1cd552eb0ce0962f232c8e88cb42fb0709515e6dbf349f134707SLBA-2017:0382-1This update fixes the following bugs: * Previously, when fencing controllers on Red Hat OpenStack Platform, the RabbitMQ resource terminated unexpectedly with a core dump. This update fixes how the RabbitMQ resource agent handles fencing, and thus avoids the described crash. * Prior to this update, the redis resource agent did not notify the client if a master node was changed into a slave mode. In some cases, this caused temporary unavailability of data on Red Hat OpenStack Platform. This update fixes the underlying code, and the described problem no longer occurs.Scientific LinuxScientific Linux 7resource-agents-3.9.5-82.el7_3.6.x86_64.rpmdbc0150d4ea863ee0f33c95715cde597e16b959b72392d141a043db46bf35306SLBA-2017:0383-1This update fixes the following bugs: * Previously, when fencing a guest node, the Pacemaker resource manager in some cases incorrectly detected that resources on this node's host were stopped. As a consequence, services were sometimes recovered unnecessarily and thus started on multiple nodes. Now, Pacemaker properly determines recovery actions needed when a guest node is fenced, which avoids the described problem. * Prior to this update, if a resource agent used the crm_node command to obtain the node name, the resource agent sometimes received incorrect information if it was running on a Pacemaker remote node. This negatively affected the functionality of resource agents that use the node name. Now, Pacemaker automatically sets an environment variable with the node name, and crm_node uses this variable when it is available. As a result, the described problem no longer occurs.Scientific LinuxScientific Linux 7pacemaker-cli-1.1.15-11.el7_3.4.x86_64.rpm1cbd82d0ac223a32507e4bdb6a74884cdce0b3f5dfe1c1d03a078148052b1969pacemaker-nagios-plugins-metadata-1.1.15-11.el7_3.4.x86_64.rpm8195c48ddf4bbc427141556f0f9a76de20483e6df64e1500961511a1fbe4b7e3pacemaker-1.1.15-11.el7_3.4.x86_64.rpm051f1f98cbe535b4170c5e2031f82043ed5691312dffeae806accf9dfbd24227pacemaker-libs-devel-1.1.15-11.el7_3.4.i686.rpm2dc08de3485d04aca7b1f656ecaf960583760d110b317efa9d34405763afa359pacemaker-remote-1.1.15-11.el7_3.4.x86_64.rpmd3b6d0c1ddd53638edf44618cb53a3b5027da3a5098d9e434290bdc2ff6d05dcpacemaker-libs-devel-1.1.15-11.el7_3.4.x86_64.rpm43ea9396485ec6c8ba9c7238bdbc45ef619e85d3e0ff719a38c019889caf622cpacemaker-cluster-libs-1.1.15-11.el7_3.4.i686.rpmfe75de9e7bea230eec65de9705aef366a1c0cac54972ffbf033dde8db7907539pacemaker-libs-1.1.15-11.el7_3.4.i686.rpmaf417803d93f47e6517cb8cd22978279cde819293b9fc8cd140168ff96a9ca5epacemaker-doc-1.1.15-11.el7_3.4.x86_64.rpm5bf364b12bd01ae6d1b3c57f7d2dc2613cfbbd339e65e130d5119ce0eb0baa0epacemaker-cluster-libs-1.1.15-11.el7_3.4.x86_64.rpmff359401e541773059d7b30cfc74d5c3405d88139c6a3ae8507990e4d428332apacemaker-cts-1.1.15-11.el7_3.4.x86_64.rpm69dc33636149c19993c86562e1255609b1a182abf512c2392615b9b16c1fbb0cpacemaker-libs-1.1.15-11.el7_3.4.x86_64.rpm9f66d9de3d587405bfbfd89c0993ff18cf5928e432b53daf9a915c095baab117SLBA-2017:0384-1This update fixes the following bug: * Previously, Fence agent for Cisco UCS (fence_cisco_ucs) switched off a node without setting the correct power state under certain circumstances. With this update, fence_cisco_ucs sets power states as expected in the described situation.Scientific LinuxScientific Linux 7fence-agents-eps-4.0.11-47.el7_3.3.x86_64.rpm79230affa55c9fe64ca32e383d14ca5c965d059d00f0c1341e4f728308b66af4fence-agents-ifmib-4.0.11-47.el7_3.3.x86_64.rpm70d461b166889b6a076aca9ecd7508a55e693fd0f1a63f0806f7552cc4608314fence-agents-cisco-ucs-4.0.11-47.el7_3.3.x86_64.rpm403aa346e936852cb0b677226d73525a42bb9ad4c0172e856e864fc008abf6c1fence-agents-apc-4.0.11-47.el7_3.3.x86_64.rpm9e2f54a04084933062ffe2439a2ecb6f770ab64d9c7b5e4cd3b74a7be936d70cfence-agents-virsh-4.0.11-47.el7_3.3.x86_64.rpme8bd450034e0895d87848724392aa3d5df1feffda5555c726899f528324b97ecfence-agents-rsb-4.0.11-47.el7_3.3.x86_64.rpmbe69141971037aed99e5adf96491a63c01c9f4c4791fd45615b722f68736bc05fence-agents-ipdu-4.0.11-47.el7_3.3.x86_64.rpm06f9c5c7fca59647434202f967a4104080d29819d24fabafacd7d8a186dc5ecffence-agents-wti-4.0.11-47.el7_3.3.x86_64.rpmc345445f1d5cad07731eb42bcef052102028946966c6078329884aaddf7dc342fence-agents-apc-snmp-4.0.11-47.el7_3.3.x86_64.rpmdb1b2c2978e64e07a2395bf487220554d7659f24602d1d830495db78d76e6675fence-agents-intelmodular-4.0.11-47.el7_3.3.x86_64.rpm7c088421b3135377f8e4e2bcc7c404b91c00a0ccef76a635295db97af22da8c1fence-agents-ilo-mp-4.0.11-47.el7_3.3.x86_64.rpm9b58886d1863ada71bc8b4a77b914b91fc8610364cd8036c738240803cfca5b1fence-agents-rsa-4.0.11-47.el7_3.3.x86_64.rpm765e5fe5a9fc4fbe366c69514d0433bf2abc175009cce79eb4eed0de6335c70ffence-agents-ilo-ssh-4.0.11-47.el7_3.3.x86_64.rpm240c314947fb222742f647bc371a0b5fc182ed9e95226405aad9b9b60702da9ffence-agents-emerson-4.0.11-47.el7_3.3.x86_64.rpm8c8a930ccd2c9c6301a7c765a0ad2a862aa014e1124c58d00ea618f8d87c5bc3fence-agents-rhevm-4.0.11-47.el7_3.3.x86_64.rpm660ea32625e05bb085808eab6f9ea8914f1cb409c5de51c34d7f2d4f2757556efence-agents-ilo2-4.0.11-47.el7_3.3.x86_64.rpmba3a6ba0b7dea026b8282328d7483698604d056194cd51adfc29902fc152bb59fence-agents-ibmblade-4.0.11-47.el7_3.3.x86_64.rpm01db69691ce720e5bc4fa625095bdbcf9ec57ba85025bbadd2f38f18d692a123fence-agents-ipmilan-4.0.11-47.el7_3.3.x86_64.rpmb5762de7de98157b8d1cc3c949713d9cb3310d084e6c9188f991b834db82358bfence-agents-brocade-4.0.11-47.el7_3.3.x86_64.rpm11ca92a1f944221b240e14584c2092e219d3a7cdb9be45bb4bc41ec643af59b5fence-agents-cisco-mds-4.0.11-47.el7_3.3.x86_64.rpm9dd590881c4976746afdb09fc7f654daae28e52f713d259597b60fd105ba77cefence-agents-vmware-soap-4.0.11-47.el7_3.3.x86_64.rpmaf6dfa85a032ba095e40111860a6825c9f54021c6eaa304f96d72d6e2b9a37dbfence-agents-mpath-4.0.11-47.el7_3.3.x86_64.rpmcdc953713b6ef65599a252f49d7d0d6ff87502e9f42ff5e0c1cedb1e5d8e3e47fence-agents-eaton-snmp-4.0.11-47.el7_3.3.x86_64.rpm1bbe70ed98d27a38fb8c5a451588270145a0b72564d9f159df4bbe0baea01f4ffence-agents-all-4.0.11-47.el7_3.3.x86_64.rpm7272b400fb12f72519e9111cf711acff235e2a7dd97f77838572dc7fb5ef32eefence-agents-hpblade-4.0.11-47.el7_3.3.x86_64.rpm7f2483acb3f480e0c70445096101ee9d81205d42086e1825e5056e433460e0a8fence-agents-bladecenter-4.0.11-47.el7_3.3.x86_64.rpm96cfa70d9d087815bfea1c2dfebc84b42f2ad2a2f83a2f7e4e5e4ce2e71e3f81fence-agents-ilo-moonshot-4.0.11-47.el7_3.3.x86_64.rpm5a8965f673f907d048979ac525c558878f13995f880278c442fd6d512662d62efence-agents-scsi-4.0.11-47.el7_3.3.x86_64.rpm14d2df2e3be099b781a698254eb686e8ac0ec9312795f21a06bdf05d5e0464f6fence-agents-common-4.0.11-47.el7_3.3.x86_64.rpm19c4bd42f8e7cb1dc309686db64003ff7c7ca83c93607e7340851dacadb34491fence-agents-drac5-4.0.11-47.el7_3.3.x86_64.rpm21bd59cdd9c6750d6bbbc9d5f4680bdfbb70824616c1e647aef2e94b8aaca359fence-agents-kdump-4.0.11-47.el7_3.3.x86_64.rpm2c6deab1e29cbd06bbcc802915340e502b850591e1e4cff3dec36ef7881edab2fence-agents-compute-4.0.11-47.el7_3.3.x86_64.rpm2e438cbe1fc9803281a8098ae22eeee841882fd45595d1c0fc175b4f80309bb6SLBA-2017:0390-1This update fixes the following bug: * Prior to this update, the OpenSCAP remediation function based on United States Government Configuration Baseline (USGCB) or Security Technical Implementation Guide (STIG) profiles from the SCAP Security Guide incorrectly changed the /etc/ssh/sshd_config file. Consequently, the SSH daemon failed to start and the system was not accessible using the SSH protocol. The remediation function has been fixed and a machine remediated using USGCB or STIG profiles is now accessible by SSH.Scientific LinuxScientific Linux 7scap-security-guide-doc-0.1.30-5.sl7_3.noarch.rpm52729f2676b035b3c0b70e9050b79bcaafae78c78f8a0d2fba9110e062dd2d22scap-security-guide-0.1.30-5.sl7_3.noarch.rpma79bf97a16830ce7332a06636a8e82e7f0a824ef6e312bd14a170707e0ca1680SLBA-2017:0391-1This update fixes the following bugs: * Previously, the vmtoolsd service in some cases entered a deadlock state when taking a snapshot of a Scientific Linux 7 system on the VMWare ESXi hypervisor. Now, vmtoolsd takes into account the dependencies between mount points when taking a snapshot, and the described problem no longer occurs. * Prior to this update, taking a snapshot of a Scientific Linux 7 guest on the VMWare ESXi hypervisor failed if docker images were running on the guest. With this update, the vmtoolsd service properly quiesces the guest file system in the described scenario, which makes it possible for the snapshots to be taken. In addition, this update adds the following enhancement: * A new udev rule for the SCSI timeout increases this timeout from 30 seconds to 180 seconds when using open-vm-tools. This prevents virtualized SCSI devices from becoming offline due to temporary transport problems.Scientific LinuxScientific Linux 7open-vm-tools-10.0.5-4.el7_3.x86_64.rpmbc6aed9d7d65537dd9b1f1665b575a2023636faccb1c3bfb33120f1afbeb5418open-vm-tools-desktop-10.0.5-4.el7_3.x86_64.rpm53ff4f72c35029060a21fbc8900edcc72637e22d90a7db6d6b3370f940170ba2open-vm-tools-devel-10.0.5-4.el7_3.x86_64.rpm236d08621c6b97da191865f730f162defbd8e0760dd74c0279492a73d9bad6c5SLBA-2017:0392-1This update fixes the following bug: * Previously, the polkit daemon (polkitd) was not able to correctly free all memory allocated during normal operation. Consequently, the memory allocated to polkitd continued to grow. When the system ran out of memory, the kernel terminated the process unexpectedly. This bug has been fixed and the polkitd now can free the memory as expected.Scientific LinuxScientific Linux 7polkit-docs-0.112-11.el7_3.noarch.rpmd796e7ef06030b9f5dce68693fbaab6e06fba4d7c22edc94fa32271c503bdc6apolkit-0.112-11.el7_3.i686.rpm51898542ee8cf41731b3bbb0dff39453ccbb75d663130b620a008950a2210e2apolkit-devel-0.112-11.el7_3.i686.rpm15b74234b012ba8447c901ee5ef85e235809dfe18e43ef2e6328588a8fe1a717polkit-devel-0.112-11.el7_3.x86_64.rpm8afb55144423529ca33b7847e0496a4cca7aab599713069f7dc39e6cbca778c0polkit-0.112-11.el7_3.x86_64.rpm397317be838418ad0fc0d494fb60ba7851d71ed2b0bf69ca0278fdad9917a2baSLBA-2017:0393-1This update fixes the following bugs: * Previously, in the auditd.conf configuration file, the audit daemon continued to write logs to the disk even when the "write_logs" option was set to "no". The bug has been fixed, and the audit daemon now respects the value of "write_logs". * Prior to this update, when the "log_format" option was set to "NOLOG", the audit daemon terminated unexpectedly. The bug has been fixed, and the audit daemon now works as expected.Scientific LinuxScientific Linux 7audit-2.6.5-3.el7_3.1.x86_64.rpmfc3fb6539e5c49fc6996297e4fcd486454c5b6229d38b8c7cf33002b6910dba8audit-libs-devel-2.6.5-3.el7_3.1.x86_64.rpm49a266288e24f6027c3ecc56cd0b4dac62fa819bbf3bf16e0425ae43d2eba986audispd-plugins-2.6.5-3.el7_3.1.x86_64.rpmb1de8f5fc13583ea0f3be21d8b37ce5a871572c8ca4a4ef67a3220b74acdd9f1audit-libs-devel-2.6.5-3.el7_3.1.i686.rpm6a33c8a0ae2b8e2c973b65412f479364072e403ba39209855a932f43a2886bd9audit-libs-2.6.5-3.el7_3.1.i686.rpm929523562de498d91871a77c725ac4844a0d432521bd026d8bdb57692afd9b61audit-libs-static-2.6.5-3.el7_3.1.x86_64.rpm3700e6188205de51be463b5429050f5cc284cc322dab3a4d6b6f202373a67c6eaudit-libs-2.6.5-3.el7_3.1.x86_64.rpm766286bddf075d6aa0658e551bb58a499208ded9a3468d99a58d61321a011666audit-libs-static-2.6.5-3.el7_3.1.i686.rpm074e985279920943607804395c766c8307647991cdd05e6d1763bf1fca313beeaudit-libs-python-2.6.5-3.el7_3.1.x86_64.rpm9b24c9899dc56d57ae63d950b039a91c9044e8919b690431d3b39c92eefebc94SLBA-2017:0394-1This update fixes the following bug: * Due to an incorrect parameter passing in an internal function that sends replies to LVM tools, the Metadata Daemon (lvmetad) previously terminated unexpectedly with a segmentation fault when the internal function was called. A patch has been applied to As a result, parameters are now passed correctly in the described situation, and lvmetad no longer crashes.Scientific LinuxScientific Linux 7lvm2-cluster-standalone-2.02.166-1.el7_3.3.x86_64.rpm946d1676836b36c8eaeef3ccc116caf389549e098f49e05e3998330a778c616edevice-mapper-event-devel-1.02.135-1.el7_3.3.x86_64.rpma80c535d467b7e9ce060398453d4456796d51d62e0673318ae85e43402feb459device-mapper-event-1.02.135-1.el7_3.3.x86_64.rpm91d355684ce12e9206090bf1a2e0aa83d8560734d4dec32df29f59f6c4b399fblvm2-cluster-2.02.166-1.el7_3.3.x86_64.rpmd54eae960a709cd3b34755d04633d403b98160c8af4923942e82f03462588b62lvm2-devel-2.02.166-1.el7_3.3.x86_64.rpm9a17cfeac62669c0a700b1c5313f31ee237fcdc8ed5b043bc51646d41215f1ealvm2-python-libs-2.02.166-1.el7_3.3.x86_64.rpm3e52a9fd86a4f0b8e8a0d775ff452c0ab0b5b234d4c4a7df6f3065fe276dbc06lvm2-libs-2.02.166-1.el7_3.3.x86_64.rpmc8809c3769374ff6b0986a1888a9e367ece1bc486c9a278195ee77c5131f1dbedevice-mapper-libs-1.02.135-1.el7_3.3.x86_64.rpm267ed7eadeb3bfa7c55d4f9900cb9793d7a1dd7fc58dfd4e10a511f51cf9abbfcmirror-standalone-2.02.166-1.el7_3.3.x86_64.rpme7384e3686e9ae19194066e261c32035e8bd77fc7bf9dacab5ba5f67591c66b2device-mapper-event-libs-1.02.135-1.el7_3.3.i686.rpm028772848bef33d501d94d53a81679656169ebe2337d3b4994af52523a5b778ecmirror-2.02.166-1.el7_3.3.x86_64.rpm6eb89258e4f8c1a41c7488bb8c55144e099920e8b36d7e56a0cdfcba53c20445lvm2-devel-2.02.166-1.el7_3.3.i686.rpm90e9351c76defde9e6c1d51d93a67d1f5ffc371161c92bad90b89c5fb8a8a3f4device-mapper-devel-1.02.135-1.el7_3.3.x86_64.rpm2dd41c03475d6c7077a6d9a2c7c0ccfbead9fc9f5c4736f12a0fb9f2a55c99d2device-mapper-devel-1.02.135-1.el7_3.3.i686.rpm5ec443533e1696b75a824b8cf6ef00dfe2a98896f2f4e09e6621865a9fa25232lvm2-lockd-2.02.166-1.el7_3.3.x86_64.rpmf6ce00e501549eadead49c521fb520de3980785d6fb94f9e5dd8b191f4f562b7lvm2-sysvinit-2.02.166-1.el7_3.3.x86_64.rpmc1fa88320f1d12cab626eac808dd3d8f1b306d80006902b136360cbafb879363device-mapper-libs-1.02.135-1.el7_3.3.i686.rpm7dc153b98ac09d5d823fedad69e8ec21842b268292b872cccd236a464d94efaddevice-mapper-event-devel-1.02.135-1.el7_3.3.i686.rpmcd7783b9caccd43a35484df2a27b19033f7e9bb6f55ab302633d017e48737caelvm2-2.02.166-1.el7_3.3.x86_64.rpma65b5d8712b47dae55027037c28a9ffdbba8f9647ec0c107fdbfb52711cd824blvm2-libs-2.02.166-1.el7_3.3.i686.rpm6e68dad9e5cbd9b3328240cf1c4130e931af5345d7278dc6c55acc105f75e37adevice-mapper-event-libs-1.02.135-1.el7_3.3.x86_64.rpmfc14e85fd060b328835b242705c9ed727691853afb0cf80ba4977a6a8fa1fc11device-mapper-1.02.135-1.el7_3.3.x86_64.rpm0342bc1a515d94ea4ed47250cdd5cfac8a11c6235a2bed1457457c4cd5b5abfbSLBA-2017:0395-1This update fixes the following bug: * Previously, if the .history file was located on a network file system, such as NFS or Samba, the tcsh command language interpreter sometimes became unresponsive during the login process. With this update, the .history file is not locked if located on a network file system. As a result, tcsh no longer becomes unresponsive in the described situation. Note that having multiple instances of tcsh running can cause the .history file to become corrupted. You can resolve this problem by enabling explicit file-locking mechanism. To do that, add the "lock" parameter to the "savehist" option in the tcsh configuration file. For example: $ cat /etc/csh.cshrc # csh configuration for all shell invocations. set savehist = (1024 merge lock) To force tcsh to use file-locking when .history is located on a network file system, the "lock" parameter must be the third parameter of the "savehist" option. Do this at your own risk, because Red Hat does not guarantee that using the "lock" parameter prevents tcsh from becoming unresponsive during the login process.Scientific LinuxScientific Linux 7tcsh-6.18.01-13.el7_3.1.x86_64.rpm2538075f51bb60b2f5687829dc274dba24dd84918836cfa4b01200df9201a214SLBA-2017:0397-1The libvirt library contains a C API for managing and interacting with the virtualization capabilities of Linux and other operating systems. In addition, libvirt provides tools for remote management of virtualized systems. This update fixes the following bugs: * Previously, the libvirt code assumed that for any domain disk device found to be LUKS encrypted, the device would have a libvirt secret associated with the device to provide the key to unlock the device. As a consequence, when attempting to access the secret libvirt would crash. This update adds a check to ensure that not only is there encryption, but there is a secret, before trying to access the secret object to pass the secret along with the disk. As a result, it is possible to attach a LUKS encrypted without providing a libvirt secret to unlock the LUKS disk. This allows the application to provide the mechanism to unlock the LUKS disk. (BZ# 1411394) * Previously, libvirt did not provide a method for adding a secret for a virtio-scsi device during alterations to support a domain master secret for passing the encrypted secret to qemu. Consequently, it was not possible to hot-plug a virtio-scsi device using cephx authentication. This update adjusts the algorithm to add the authentication object with the encrypted secret for qemu to parse. As a result, libvirt can authenticate a hot-plugged virtio-scsi device. (BZ# 1411398) After installing the updated packages, libvirtd will be restarted automatically.Scientific LinuxScientific Linux 7libvirt-devel-2.0.0-10.el7_3.5.i686.rpmedef83fba21eb17865d0249cb930a5f7e0edc0df2868e3b7db7c7547dc8c7f86libvirt-nss-2.0.0-10.el7_3.5.i686.rpm136e2057d4b429d081c3371d774f39905b43917a2b6761c43bce925e930d3fd4libvirt-daemon-2.0.0-10.el7_3.5.x86_64.rpm6609563499e654e723572472c754c5db7165c4d5d757692c49fccfc2df151c3flibvirt-lock-sanlock-2.0.0-10.el7_3.5.x86_64.rpmcd52f062b4b4537ef92f3a658ce8f5b7f5dc4e7115121b61ef80c8d46883ad82libvirt-nss-2.0.0-10.el7_3.5.x86_64.rpm0c7a7c07b60ca0f4050636fb8db438298eed02a2e43ae56bd146a3b65e9aa591libvirt-client-2.0.0-10.el7_3.5.i686.rpm34595352c3c25af7d5a1f938987cd247b5b69fab4fc5e562e6b61056add9f141libvirt-daemon-config-network-2.0.0-10.el7_3.5.x86_64.rpm08a51443e6aa32ee7dcb804a9b2f3f004c792a23a5904c9b4a82e08b9b7640b9libvirt-devel-2.0.0-10.el7_3.5.x86_64.rpm675f88b60201e04f3ad9aae62b03459cb1f2e61a69878a26f7bfabc5d27ecdc2libvirt-daemon-lxc-2.0.0-10.el7_3.5.x86_64.rpmd0cb45e38213c8fb2a461d670d72de82b33990c798a53723bf65e95ef6c05c55libvirt-login-shell-2.0.0-10.el7_3.5.x86_64.rpm6da932fabf8bc96a0908b35a47c9577b18559295173641bd1911e72a7adcd3d2libvirt-daemon-driver-nwfilter-2.0.0-10.el7_3.5.x86_64.rpm765dc8cf9497765095d8dd6dc7625775f36256df1ad114a2d3c61b67658bdb7alibvirt-client-2.0.0-10.el7_3.5.x86_64.rpm04d673db858cc0ec49b4169fc58fddd3dc862c91aca6ebd744276a983172fca9libvirt-daemon-driver-interface-2.0.0-10.el7_3.5.x86_64.rpm188d9d0823da3603a06f487bd543667f3621c33c8d84cb12d9a4e03f3f5e9cfalibvirt-daemon-driver-storage-2.0.0-10.el7_3.5.x86_64.rpme0904a8cf055e6f9297a91501caf7481b3dadf0d1111d74800e985c2c765b21flibvirt-daemon-driver-qemu-2.0.0-10.el7_3.5.x86_64.rpm2ef312cf056e7ea03ccf732a2f892779af54d14ef40a6a8e814951fbda1c7501libvirt-daemon-kvm-2.0.0-10.el7_3.5.x86_64.rpm504749634a8a4ea88a54d1533f0f898631792ec4eb518949df5047cb3928b544libvirt-docs-2.0.0-10.el7_3.5.x86_64.rpmc4c025d5070a57ce58f053eb9b3d6e29fc108d9232c336be3ecd0197ad307040libvirt-daemon-driver-network-2.0.0-10.el7_3.5.x86_64.rpma3359f6e0dde6c7c6acef78b086e2c344c58217fc0da734d72a46c3fe6676786libvirt-2.0.0-10.el7_3.5.x86_64.rpmefc6e00ac7c1055ca4a81fc6384715b25ebf5d096cf8b49fd164796624da6990libvirt-daemon-driver-lxc-2.0.0-10.el7_3.5.x86_64.rpmee748b14a9edb9b2957e649fa964c5046300d3fa302e1f2a7eca73a40abe4116libvirt-daemon-config-nwfilter-2.0.0-10.el7_3.5.x86_64.rpmb05f53a61e09581687ccabf1326553bfccb2d1ea316205a8ed897ab5b15c16b1libvirt-daemon-driver-secret-2.0.0-10.el7_3.5.x86_64.rpm8d3ff66e4b73ae6769525f0483858f704c001cf8c959cfe872440977a523377flibvirt-daemon-driver-nodedev-2.0.0-10.el7_3.5.x86_64.rpm7deabfc215316a4879b8663e8c889e71fc5d71a067cdbb64a96b3ceec626b551SLBA-2017:0398-1This update fixes the following bug: * Prior to this update, when providing Advanced Configuration and Power Interface (ACPI) tables to SeaBios, it was necessary to use the iasl compiler. The bug has been fixed, and as a result it is no longer required to use the iasl compiler.Scientific LinuxScientific Linux 7seabios-bin-1.9.1-5.el7_3.2.noarch.rpm5f28a87a250020707a116d35b1926a14b07ae2f6de836903a1cbf85577c43191seabios-1.9.1-5.el7_3.2.x86_64.rpm5f4b426db0e80b7821bcca1d29f6cd388c6fbb4af6c0663b6de68594ebafc974seavgabios-bin-1.9.1-5.el7_3.2.noarch.rpm94baf73649ee69cdecc304f3318e272620a50acb97f55057d6bb011f095f13e6SLBA-2017:0399-1This update fixes the following bug: * Previously, the pcs utility did not allow the "scope" configuration option to be used with the "pcs cib-push" command. As a consequence, using "pcs cib-push" with "scope" failed with an error, and the Cluster Information Base (CIB) was not updated. With this update, using "scope" with "pcs cib-push" no longer fails, and CIB is updated as expected.Scientific LinuxScientific Linux 7pcs-0.9.152-10.sl7_3.3.x86_64.rpmce36aec3b0e7d2d0e9858045b7bca911ef829937cdc354449e6460f98215c723SLBA-2017:0400-1This update fixes the following bug: * Previously, when the drop or block zone was used, firewalld placed the logging rules for the LogDenied option after the final DROP or REJECT rule. Consequently, packets matching the DROP or REJECT rules were not logged. The placement of the logging rules has been fixed, and the log rules now works correctly.Scientific LinuxScientific Linux 7firewall-config-0.4.3.2-8.1.el7_3.2.noarch.rpmccd36d7dd986e90948813e6b259b1a406bee220749c8ca821d1fb2ec320fb59dfirewalld-0.4.3.2-8.1.el7_3.2.noarch.rpm72de4c75344a61ce93e769e5dc87f9567761e095129e7843c00fedf7008c83bafirewall-applet-0.4.3.2-8.1.el7_3.2.noarch.rpm5e42ace2df2009d546465f4f59c1928b48bd3977f62bbef1a591dc8301f32145python-firewall-0.4.3.2-8.1.el7_3.2.noarch.rpmc63388cf838ba64cc688727d79163720fab017c7b6afa4380a0efe3bdca3c7fbfirewalld-filesystem-0.4.3.2-8.1.el7_3.2.noarch.rpmf387738ce1c405bbc025b6a0db3f59d25eb9e9ff61a2f790e7bb81fdde4b555fSLBA-2017:0904-1This update fixes the following bug: * Previously, the dmidecode utilities failed to extract hardware information from the BIOS or the Extensible Firmware Interface (EFI). This update fixes the underlying source code, and dmidecode now work as expected.Scientific LinuxScientific Linux 7dmidecode-3.0-2.1.el7_3.x86_64.rpmd12373e7e1a3cb3967edd29436b50ae5652cfcbac4e1f7daed9ae5f0488d2362SLBA-2017:0905-1This update fixes the following bug: * Previously, the default "isolated" and "nohz_full" parameters were not parsed correctly. As a consequence, when these parameters were empty, they were incorrectly applied to CPU 0. This update fixes the bug, and these parameters work as expected.Scientific LinuxScientific Linux 7irqbalance-1.0.7-6.el7_3.1.x86_64.rpm694eec7b2ab7ec58524651cf3ac633861d4688001cb3eb5f3e3fe1e4651ac227SLBA-2017:0908-1This update fixes the following bugs: * When the "default_domain_suffix" option in the /etc/sssd/sssd.conf file configured SSSD to qualify to an automatically discovered trusted domain, the requests to resolve the user's authorized keys were not routed to the appropriate domain. This update fixes the bug, and SSSD now handles the mentioned requests as expected. * When an SSSD process needed to be restarted because it was being blocked by a long-running task, a deadlock sometimes occurred during the restart. For example, this problem occurred when the sssd_be process was enumerating a large domain. This update fixes a bug in the watchdog code, which prevents the deadlock.Scientific LinuxScientific Linux 7sssd-common-pac-1.14.0-43.el7_3.14.x86_64.rpmb678c8164a4d0f9bce802cb1a9468d4b87ac34cbf5a6ca11417548c2ee39beeflibsss_simpleifp-devel-1.14.0-43.el7_3.14.i686.rpma371606e30cda1966981deaf66e7585bf554090baebc80bf5a4da9898f783eacsssd-winbind-idmap-1.14.0-43.el7_3.14.x86_64.rpm51fbc6d6bf470eae1cb5f64e912ce111b67e8fb03e44263819158a240621698asssd-client-1.14.0-43.el7_3.14.x86_64.rpm34170a5e0c3ce76126820aca0cf51581cdca72355ba9f2469f1b96dc6eafd2f8sssd-krb5-1.14.0-43.el7_3.14.x86_64.rpm6ae2e81bb7809d1a1cda29eb2e9cd7492558fb961eb9064533591913abcd0d5bsssd-polkit-rules-1.14.0-43.el7_3.14.x86_64.rpm16b25a57dfcaf79a4240604b9715fa7fe4edc70bffdf252a61a73193f80f56b7sssd-proxy-1.14.0-43.el7_3.14.x86_64.rpm8655a46e664be34656156803e79ef6ba535bae62becd750813c64cb38ecd096flibsss_nss_idmap-1.14.0-43.el7_3.14.x86_64.rpm4bc7e3e17dde4ee8d878dcbdf968b8a16b4322aa719edb42d42df7e040bd1288python-sss-murmur-1.14.0-43.el7_3.14.x86_64.rpmb16dd11e1c55b8f380421156b41579d7cb7bc910e46b84b7a1239dd9494407a9sssd-libwbclient-1.14.0-43.el7_3.14.i686.rpme5c47e29b8fc6627795120b15d7b98693452f86f0bb151e2cffca7e7bc468a30sssd-krb5-common-1.14.0-43.el7_3.14.x86_64.rpmed6c5a48d63a8dd54ee46bb34ee1ff8f7adf28ce782d47d0acd5e9e40183f3c7sssd-1.14.0-43.el7_3.14.x86_64.rpm150b3bd26d04fa578d53ffecc78effc93992c6c44f665dfca08daa9fa803dfc9python-sss-1.14.0-43.el7_3.14.x86_64.rpmf8ca72686b0444f429c060d061fa9f8c7d8857ef113d1bcbacc3b21d655ea99bsssd-ipa-1.14.0-43.el7_3.14.x86_64.rpmb2b49b6d7117b0f7522216bac189898d11d7cac2fd47f1ce1183c3471542346fpython-libsss_nss_idmap-1.14.0-43.el7_3.14.x86_64.rpm712b51599ab8965facc751808e51cb524492f3b3f1922e88055b80ecebadf2falibsss_autofs-1.14.0-43.el7_3.14.i686.rpmeb4276ee1cab1e0fedefea55beaad0ec0db5364c1201f9fd948cdaeffc79511dlibsss_simpleifp-1.14.0-43.el7_3.14.i686.rpme2206f14ff4615f6ca55e293c9de68ea00c6bf1a204f62440ceac5190854b5c9libsss_simpleifp-1.14.0-43.el7_3.14.x86_64.rpm3ce79a327ba108a9e79ecdf8966c97d2bca580d2def2f71544156e61253fe777python-libipa_hbac-1.14.0-43.el7_3.14.x86_64.rpma72f04c152827e48ce73d4c55c2bf9e08973ea6ba9e33cdb143336845367e161sssd-dbus-1.14.0-43.el7_3.14.x86_64.rpm29402bbe6b7630d8bca4e285e7178165fc5bcfbaecdfefff2a23af794424e381sssd-libwbclient-devel-1.14.0-43.el7_3.14.i686.rpmf5da106d9d1c1556fb84713e87241e18c4343a388f726bbeabbe7a0aeb5a3495sssd-tools-1.14.0-43.el7_3.14.x86_64.rpm079a25d3c71b401287bf7ff7318f5080966bd3e53266c5314faa336b9e7cb00csssd-libwbclient-devel-1.14.0-43.el7_3.14.x86_64.rpmd52191f17187a4b503cfdf06e6771f19c8b64249433dbe48a5ac1ab04731d065libipa_hbac-devel-1.14.0-43.el7_3.14.x86_64.rpm2a08e67bba290976a3f1951aaad99518a255ed59713b1e48d562b16fb0c91e2fsssd-libwbclient-1.14.0-43.el7_3.14.x86_64.rpmf1a6c2e77e90a81b523bf5dc6f0fcef9138af551cc765d4fab7e09a95ca03531sssd-ad-1.14.0-43.el7_3.14.x86_64.rpm67756e1cb56aa0e10ba3372ff74341a14f964509e0243dc81e7c21c0531b3173python-sssdconfig-1.14.0-43.el7_3.14.noarch.rpm1e4b4f350480fd6ed6da1b4d26dbbc4df9e91692de509d6fc3a29c48858985bcsssd-krb5-common-1.14.0-43.el7_3.14.i686.rpmcaee253b683b5db261269648b584fed443a06db5d517f98a783923f3486de306libsss_nss_idmap-devel-1.14.0-43.el7_3.14.x86_64.rpm0e574f8939ad4a1423de48d9a4146ac68bdb6e03e1b62bfc8b3c00257b08e369libipa_hbac-1.14.0-43.el7_3.14.x86_64.rpm0c82b68674e39dcd7714da43858b4e67f780712fd08378095f5c59ea19658e20libsss_idmap-1.14.0-43.el7_3.14.i686.rpmd1af5af030a9f85d1613e41443e4ee698def56d02d2db7f433d2030a1d38a7a3libsss_idmap-devel-1.14.0-43.el7_3.14.i686.rpmae3e0952f880fee129d6699eddc10083d29a9b3ac4544bf493507214cd155aa2sssd-common-1.14.0-43.el7_3.14.x86_64.rpma6477a4971b3a4ed71d93562041f295107e28068e921d802049733b80405cdeclibsss_idmap-devel-1.14.0-43.el7_3.14.x86_64.rpm9929f09c6ac1fa46caf8b5ceec6ba07e1fbb37548e380b4db70ca9049d115aa4libsss_idmap-1.14.0-43.el7_3.14.x86_64.rpmf9a9ad5425a6118ae2d4798f1bcffc13ea96b93504f939786235fe8acd70de21libipa_hbac-devel-1.14.0-43.el7_3.14.i686.rpmca0b32dc4b1de5ca7e8ae4bdfb458e207e8f845aa47996eb7f717b58eba7221flibsss_sudo-1.14.0-43.el7_3.14.x86_64.rpm29df2c368072135f22526aff7ecb91e521957d08f21e7ff1ec390dd35c1e2d8bsssd-client-1.14.0-43.el7_3.14.i686.rpmbae7a361cf695885c2a729cb5bbfaf5bdbf5fcf15cf7910eede7876123fcb84flibsss_nss_idmap-1.14.0-43.el7_3.14.i686.rpmcab3e1424a80fb07ea8286246d1adbaefe5db78d73bb0ea21afb4490a41b4801sssd-ldap-1.14.0-43.el7_3.14.x86_64.rpm731f6fc03c5cc7e5a938dc7587919b1aea700b8e48c65a24b348225a4713cde0libsss_simpleifp-devel-1.14.0-43.el7_3.14.x86_64.rpmed3cfd2f1998bfdd485d076c7aea50cd39af3b0f626f45d495f59c1036194d10libipa_hbac-1.14.0-43.el7_3.14.i686.rpm51744200b279efd3d68429907061a7df489225a08cfef3bb2531c23a37308c39libsss_sudo-1.14.0-43.el7_3.14.i686.rpmfccb51b5ae1fe4c2e885454d2e335272c6190d0e718917eb6e3d268f9c74e66blibsss_autofs-1.14.0-43.el7_3.14.x86_64.rpme906205dc99e2357336089dc2ffee2e2bc68b7671253250705d71eea1cedce3fsssd-common-1.14.0-43.el7_3.14.i686.rpm391593e3e83cf8b9d08e18f8dbbc2173866dbbc995f0f11b6a6135500901066flibsss_nss_idmap-devel-1.14.0-43.el7_3.14.i686.rpmff1c6add09608abf03adfb67e1038dd9c8eb6699f6903cc2694460808eeabd3cSLBA-2017:0909-1This update fixes the following bugs: * Previously, there was a bug in the way systemd handles resource limits specification. As a consequence, setting resource limits failed, displaying the error "Failed to parse resource value, ignoring". This bug has been fixed, and systemd no longer fails when setting resource limits. * Previously, there was a bug in the add_random function in systemd. This caused systemd to sometimes terminate unexpectedly when a unit was scheduled to run at a specific time, without any randomized delay. This update fixes the bug, and systemd no longer crashes in the described situation.Scientific LinuxtrueScientific Linux 7systemd-devel-219-30.el7_3.8.x86_64.rpme220f945b96efddb68b1dafe1385c38287f79a608b51c78ecccebc576f2bc1d1systemd-networkd-219-30.el7_3.8.x86_64.rpmc1f234d1ca90afd82d7eed8d9fb56f31613e05f07bef50e3bfb1674e044a6378libgudev1-devel-219-30.el7_3.8.i686.rpm04fce34e9f1ff910fa2adb757bc7eaadbb3fd211abfacc322e85b0871bf15493systemd-python-219-30.el7_3.8.x86_64.rpm99b3ce331e3bb2fe1dc47750b575a98194d6e6083af0e11ecbbe2131d9dff9f1systemd-libs-219-30.el7_3.8.i686.rpmbaee93d8e187cfb53c1580246e8a85e0b5b4385eccdc795cda36a96b628806f5systemd-resolved-219-30.el7_3.8.x86_64.rpma9918b02f390b9f78cba393c7f4b0d26ed460c3c4bd3664786896c8ed19c236fsystemd-sysv-219-30.el7_3.8.x86_64.rpm17fca8fa69ebbe5ab083c3e936edb946db9bacaddca84fe5adc2acc2933fc900systemd-219-30.el7_3.8.x86_64.rpm2fccc8c228ae0f0c6016df9c1b375bba051bf4060a88fb96f83b319ef2a657d7libgudev1-devel-219-30.el7_3.8.x86_64.rpm0bdbbc949daba99b55cf687e655324f03eef21825a8295f55b950a8933d951eelibgudev1-219-30.el7_3.8.i686.rpm5a404229400d0feaf7e04da54c0215abb66137c4f16650084a9d97803f925763systemd-libs-219-30.el7_3.8.x86_64.rpm743cb7074f44bf6b79b34ccc5b222850e9f83898a5c4e5f2cb4748e6ac5d3325systemd-devel-219-30.el7_3.8.i686.rpm37e1d7e0a4a276e1775a387f9762bf6bfd08e784b2e82dfbdfca90c89c42f678libgudev1-219-30.el7_3.8.x86_64.rpmb7cce3f53967bc8b0f69e3af53c7b2bb24c0f6f6ab1cc2dde32367f446439d80systemd-journal-gateway-219-30.el7_3.8.x86_64.rpm665aae4846f95e9e6ea2298b1e2b510b67a287f2dc638162bb6336c2fcf82c65systemd-resolved-219-30.el7_3.8.i686.rpmaac50fe3787cfcead18bd7341a6add236381d264760fdbd098552e57ee8c2605SLBA-2017:0910-1This update fixes the following bug: * Previously, certain calls to the libltdl library provided unclear return values when the process was unable to allocate more memory. As a consequence, these errors could cause segmentation faults or wrong data manipulation. The bug has been fixed, and the libltdl library now provides correct return values.Scientific LinuxScientific Linux 7libtool-ltdl-2.4.2-22.el7_3.x86_64.rpm442e594a99d8ace79216149c47f34ebc6475ac54af4fc3a117b499969e747ae6libtool-ltdl-2.4.2-22.el7_3.i686.rpmf46ddd5dd6b425cad3a1a651f41555557e860cf031ff5cae8c28aa0069125d8flibtool-ltdl-devel-2.4.2-22.el7_3.i686.rpm4e557df70163c030b18642c5eaafe696efca16da650e29329561929d456a3f30libtool-2.4.2-22.el7_3.x86_64.rpm712612e949dbf779be3c724cc332ec67be8a6fcbf48dcdc57cabd8fdd64db1b7libtool-ltdl-devel-2.4.2-22.el7_3.x86_64.rpm1f4466706bf5722217dc19ecf62bb39733ebcc028f08c484cb2af0069441b482SLBA-2017:0911-1This update fixes the following bug: * Previously, the ifup script was very slow when notifying NetworkManager. This particularly affected Red Hat Virtualization network startup times. The bug has been fixed by applying a workaround to initscripts. As a result, ifup no longer slows down when NetworkManager is running.Scientific LinuxScientific Linux 7debugmode-9.49.37-1.el7_3.1.x86_64.rpm7165ce6d37f4658a9881c3b8eee5a7cdeaec840d050c66696da800173ba65304initscripts-9.49.37-1.el7_3.1.x86_64.rpm9a9de299152397335f0c4b3b08f618a4e8c4bdbf89b616c96cff80e3bb4722feSLBA-2017:0912-1This update fixes the following bug: * With this update, RabbitMQ resources are able to correctly run on Pacemaker Remote nodes. In addition, this update adds the following enhancement: * The "SAPHana" and "SAPHanaTopology" resource agents have been updated to upstream version 0.152.17, which improves their reliability and fixes several bugs.Scientific LinuxScientific Linux 7resource-agents-3.9.5-82.el7_3.9.x86_64.rpm42a59e451ebf73f3ac4e0a71b3f7121af01fdb54505ee9cd940906617b4fc079SLBA-2017:0913-1The ca-certificates package has been upgraded to upstream version 2.11, which provides a number of bug fixes and enhancements over the previous version. Notably, the package now contains the following modifications: The certificate store has been upgraded to include the changes contained in version 2.11 of the CA certificate list published by the Mozilla Foundation at the mozilla.org website as part of the Network Security Services (NSS) version 3.28.1. However, for compatibility reasons, several root CA certificates with an RSA key size of 1024 bits have been kept as trusted. Mozilla previously removed trust from several legacy CA certificates containing 1024-bit RSA keys. This version of the ca-certificates package modifies the Mozilla list to keep these legacy CA certificates trusted by default. These modifications have been made to ensure compatibility with existing PKI deployments and with software based on OpenSSL or GnuTLS. The ca-certificates package also includes the "ca-legacy" command, which can be used to disable the mentioned compatibility modifications. Refer to the ca-legacy(8) manual page for more information on how to use the command. Users who intend to disable the legacy modifications are also advised to refer to the following Knowledge Base article, which provides details about these modifications and the potential consequences of disabling them:Scientific LinuxScientific Linux 7ca-certificates-2017.2.11-70.1.el7_3.noarch.rpm0d41b436fc97e1657ad573b094c471915c4e0afa2e16564a146c4f824e3e82c5SLBA-2017:0915-1This update fixes the following bug: * Previously, a race condition between systemd starting the OpenSSH server daemon and sshd writing a PID file could occur. As a consequence, systemd kept the sshd service restarting endlessly. With this update, the sd_notify() function has been added to the sshd code, and systemd is now able to properly detect already running sshd.Scientific LinuxScientific Linux 7openssh-keycat-6.6.1p1-35.el7_3.x86_64.rpm95b3f31e97de1b407c6b585d44acfb35e20439e9ef9a3556240a09229f7e3435openssh-server-6.6.1p1-35.el7_3.x86_64.rpma60b9380b1bd044c948d174ec4c1748034e175ed1f429a78721f93dd7e2a16dcopenssh-server-sysvinit-6.6.1p1-35.el7_3.x86_64.rpmbe9578e86a2f4e076f5183b11c0e628221951a940a7a3e7406c2baf3bb5d4cf1openssh-clients-6.6.1p1-35.el7_3.x86_64.rpma637c0dd56ea0aa27e5e832501e2f4bdc13ba5cf533d612902deea0421cacedbopenssh-ldap-6.6.1p1-35.el7_3.x86_64.rpm9fa6984510f0a7600cfb21f845ab18acd71f37b99c91a4b307a15c8a319df54epam_ssh_agent_auth-0.9.3-9.35.el7_3.i686.rpmf276bf4337da3c07899c1a1af1cd5ae8794fe256eec77d98740f977d17a98fcbopenssh-askpass-6.6.1p1-35.el7_3.x86_64.rpma95259790b7d55ffe0cca661f59421fc49453991280747cacc90a2a9687028fepam_ssh_agent_auth-0.9.3-9.35.el7_3.x86_64.rpmc6c5f0c58bc6b72fcb6b2bdd0bc0095617189a989d863a61fb9778d5ec2397cfopenssh-6.6.1p1-35.el7_3.x86_64.rpme771076d29d83aa8d8581d09c4b243ce6320546e68832025ed3c895c2da6badbSLBA-2017:0916-1This update fixes the following bug: * Previously, executing the "fcoeadm --target" command sometimes caused the fcoeadm utility to terminate unexpectedly with a segmentation fault. With this update, fcoeadm has been modified to ignore sysfs paths for non- FCoE targets, and "fcoeadm --target" no longer causes fcoeadm to crash.Scientific LinuxScientific Linux 7fcoe-utils-1.0.31-1.git5dfd3e4.el7_3.1.x86_64.rpmf7712e02fc6c6dd25f92e8c62feaf17e574474b6b84b0ec033214b8f223e0065SLBA-2017:0918-1This update fixes the following bug: * Prior to this update, the NTP daemon (ntpd) configured as a multicast client was not able to process multicast messages after an association with a multicast server had been created. As a consequence, the multicast client was repeatedly resetting the association with the server and it processed only unicast messages in the initial exchange. With this update, the described bug has been fixed, and the NTP multicast client now works properly in the described scenario.Scientific LinuxScientific Linux 7ntpdate-4.2.6p5-25.el7_3.2.x86_64.rpm201a1b72c63f5d520377eb634a9222f9a905a779ec2a973e65b90d1c7ce8fcfantp-doc-4.2.6p5-25.el7_3.2.noarch.rpme64b11a676aff1ced51fe558a8f2eab637fa7e84c307b425ea1acfc6065745c4sntp-4.2.6p5-25.el7_3.2.x86_64.rpmff86f8fd99d3b389a5a5d4303ea166b7542ebbdf1976d0f514e52a4749bcb940ntp-perl-4.2.6p5-25.el7_3.2.noarch.rpm96b357d7a0067d8bdd9f617c3d40360fd7504b592d638dd2f4a1a4b58a46f4d1ntp-4.2.6p5-25.el7_3.2.x86_64.rpm75fc26645135eb302ffb0ad23566c28d05aa6f2f654612321198813f1b697e27SLBA-2017:0921-1This update fixes the following bug: * Previously, the grubby tool always set the newly added kernel as the default. The new-kernel-pkg tool originally added the debug boot entry and the normal boot entry, respectively. This caused that the debugging arguments were installed into non-debugging boot entries. With this update, the invocations in new-kernel-pkg have been fixed to install the debug entry and the normal entry, respectively. As a result, grubby now does not automatically set the latest added boot entry as the default entry and the order of boot entries is set to "normal kernel" and "with debugging", respectively.Scientific LinuxScientific Linux 7grubby-8.28-21.el7_3.x86_64.rpm1f4346ef26c1fdbda6ab7d81fa29a50c3273eb93f33408c1aad324f6c4ba0953SLBA-2017:0923-1This update fixes the following bug: * Previously, the Squid proxy server terminated unexpectedly with a segmentation fault when it was reconfigured under high load. With this update, the underlying issue has been fixed, and Squid no longer crashes in these circumstances.Scientific LinuxScientific Linux 7squid-sysvinit-3.5.20-2.el7_3.3.x86_64.rpm58bcc1506464870a2952ebf11d1ed61e7cd85aabf65cd387cb30a3569b51231bsquid-3.5.20-2.el7_3.3.x86_64.rpm073f3a25ee30692e54ac30bf4b4760b057054ac05a1149be55b2190fe61ba4a7squid-migration-script-3.5.20-2.el7_3.3.x86_64.rpm8314506a0a488a6f42693c7fae21cacbce2145f0437bea4612efdb143b6f30b7SLBA-2017:0924-1This update fixes the following bug: * Previously, when unloading the module-suspend-on-idle module, suspended devices were not resumed. As a consequence, playing audio on suspended devices failed. This bug has been fixed, and playing audio no longer fails in the mentioned scenario.Scientific LinuxScientific Linux 7pulseaudio-gdm-hooks-6.0-9.el7_3.x86_64.rpm51b7f1704f1d54286f2f329b715780946dcc8ef46fdcef6ae9de9b03ad76df39pulseaudio-module-zeroconf-6.0-9.el7_3.x86_64.rpm821defdfd8d68012c075200ab7346e3743980e1241a00d43c84693eb972b58c1pulseaudio-qpaeq-6.0-9.el7_3.x86_64.rpmc5483ab9cb9318ffcd35d8e47a7c4e56d9800a26eeddac89d738714b2c12ffefpulseaudio-libs-devel-6.0-9.el7_3.i686.rpmc7dcabb8ed61fdd7ad62cbcece0f1d44978cee61d467557cfadae28be7210bd8pulseaudio-module-x11-6.0-9.el7_3.x86_64.rpma0d46fe77929c6f4fe44661dd3f0e449965e497516bc1ef12c78c717f1f528d6pulseaudio-module-bluetooth-6.0-9.el7_3.x86_64.rpmfbb03c752162c283fb777b6329ee5df5e7fa7842111651911924c3447ebc1531pulseaudio-libs-6.0-9.el7_3.i686.rpmf72c4bf7b0aefd493aa1790a937a57a40d8f23f341d51cb1bddd2b28a425ff06pulseaudio-libs-devel-6.0-9.el7_3.x86_64.rpm77480a3f244090fa3bc0c0cbe176ec16a41973c8060fca2a52c9e6734f97a46cpulseaudio-module-gconf-6.0-9.el7_3.x86_64.rpmfb7602c7bde5fa78df6f40f3a2b0ac873b496496139867baf8a02dd824f237e4pulseaudio-utils-6.0-9.el7_3.x86_64.rpmcd8385d6b12c22e68f9e7cf947a63d72f5fb2e677efd2f353d6beb5299ec9a6epulseaudio-6.0-9.el7_3.x86_64.rpmbed13ae6e695338d8695b47656eaddd82be174cd4ba77fdea02c22f56d92d5d5pulseaudio-libs-6.0-9.el7_3.x86_64.rpm0adb76c766cbecfacbc43f23112b8986e5be4e16f8b552e4ba5c0870a77c7d1bpulseaudio-libs-glib2-6.0-9.el7_3.i686.rpm2a94c7f7b2320eb184202b91267c2651cdf21b2940e15f0325be98535ab172d8pulseaudio-esound-compat-6.0-9.el7_3.x86_64.rpm0bae2e4026b1fb203e44e7de2a6c80ce8aa6fab013c46fe13d1c537b93862037pulseaudio-libs-glib2-6.0-9.el7_3.x86_64.rpma02cce341f6d620592606e6a5d1b3f07d768b56e249e60f7dc85b36975c8e7c2SLBA-2017:0925-1This update fixes the following bugs: * Due to a bug, Identity Management (IdM) previously used the system-wide trust store to verify the certificate when opening a new TLS connection to the remote server to use the Custodia API. As a consequence, the "ipa- replica-install" command failed if the certificate of the remote master was not trusted by the system-wide trust store. With this update, IdM uses the IdM trust store in the mentioned situation. As a result, installing a replica no longer fails if the certificate of the remote server is trusted by the IdM but not by the system-wide trust store. * Previously, the batch API command definition used an incorrect data type, which prevented compatibility with previous Identity Management (IdM) versions. Consequently, all batch command calls failed on Scientific Linux (SL) 7.3 clients when they were connected to an IdM server running on SL 7.2 or an earlier version. This patch fixes the problem, and IdM clients now work as expected in the mentioned scenario.Scientific LinuxScientific Linux 7ipa-common-4.4.0-14.sl7_3.7.noarch.rpmc065d947a3f18dd56ac354d8a0784d569fdda268da8edc390f168e38127eae86ipa-server-trust-ad-4.4.0-14.sl7_3.7.x86_64.rpmd61585c91a4dc047a94022007b14044f7a2fc7cabb7b518d00bb738d86262b34python2-ipaclient-4.4.0-14.sl7_3.7.noarch.rpm1bf6a8da1d0c6cba8d290c022b8c123403d457cb2a6983ae3aae706f6546bbe2ipa-admintools-4.4.0-14.sl7_3.7.noarch.rpm9be4a61205c0991f0c85198d7cb96e6dec5703ba65ff282877ff6221851e11f0ipa-python-compat-4.4.0-14.sl7_3.7.noarch.rpmf9480a852dc933c6c71843ccbdef9b9af2bc180a3a059f116de4b326d1e474e6ipa-client-4.4.0-14.sl7_3.7.x86_64.rpm791ef7a223f86b637a1f518dda3d76699d0f49dc2f8ea8acc34f805f25c9176dipa-server-common-4.4.0-14.sl7_3.7.noarch.rpmc66f3332fcfa977eb8d4a2ad549592fb751380e4e12711f906410b65aea50759ipa-server-4.4.0-14.sl7_3.7.x86_64.rpm38cd52b40e9102bda5622d5857b756b6fe785bc605ae869080c6712813d967dbpython2-ipalib-4.4.0-14.sl7_3.7.noarch.rpm96d6ce7d3a61012a0c4ef70477a980afd8529dd2793a599c8081425524b1a220ipa-client-common-4.4.0-14.sl7_3.7.noarch.rpm19142320a7a7de01d4d3adac17f88e65b4ac42c73fccfe17aead46e5faeb4183ipa-server-dns-4.4.0-14.sl7_3.7.noarch.rpm00a6c5ee24cb24ce915ae05e959c6861f88fdd36177ad7729ee532b5b1fde6b5python2-ipaserver-4.4.0-14.sl7_3.7.noarch.rpm0626682e4b3099b3311a463664dc41516aa8b33f8d68d4ca940eb8157d15d3dbSLBA-2017:0926-1This update fixes the following bug: * Due to a bug in error handling of dropped display connections, the GNOME Display Manager (GDM) terminated unexpectedly. Consequently, local users logged out when the X Display Manager Control Protocol (XDMCP) connection dropped. With this update, GDM no longer terminates unexpectedly. GDM must be restarted for this update to take effect.Scientific LinuxtrueScientific Linux 7gdm-devel-3.14.2-20.el7_3.i686.rpm6d290998e94bbb63a4687010291ff40534ac3665a9cb25c70f5d77b1fb9a102agdm-3.14.2-20.el7_3.i686.rpm48f41c8a14b0e1dc216a35763f6121959e5c49a71920271294c65e7a140d9b49gdm-3.14.2-20.el7_3.x86_64.rpmed7aebe3e9cd38e184926bad5a077477009c45f30c3c263e25862bde60f942a5gdm-devel-3.14.2-20.el7_3.x86_64.rpmbbf82b7a02a7264a4166e1aab4f44bd3ecd39c52a833d7c6e6b59313c2ede2dfSLBA-2017:0927-1The compat-sap-c++-6 packages contain the libstdc++ shared library named compat-sap-c++-6.so, which is a runtime compatibility library needed for SAP applications. The compat-sap-c++-6 packages are based on GCC 6. This enhancement update adds the compat-sap-c++-6 packages to Scientific Linux 7. These packages are available both for AMD64 and Intel 64 systems and for IBM POWER, little endian. All users who require compat-sap-c++-6 are advised to install these new packages.Scientific LinuxScientific Linux 7compat-sap-c++-6-6.3.1-1.el7_3.x86_64.rpmfb6939e1e66c2646f1c2bcbfc89d8e1797232b56477f99cb49a028525ee9e58eSLBA-2017:0928-1This update fixes the following bugs: * Prior to this update, NetworkManager would leak memory when new virtual interfaces were added to the system. Consequently, the process continued to consume increasing amounts of memory. The bug has been fixed, and the memory leak no longer occurs. * Previously, NetworkManager in some cases failed to add the default route for VLANs on top of team or bond interfaces. With this update, NetworkManager always adds the default route for such interfaces properly.Scientific LinuxScientific Linux 7NetworkManager-dispatcher-routing-rules-1.4.0-19.el7_3.noarch.rpmee9dad33417ae27d7395fdd9e90dfa03a5fa133e1ab0a2ea6584d7131bcc706eNetworkManager-libnm-1.4.0-19.el7_3.i686.rpm9b23719d6ea8fe91580fa8ee560c0176b4eb303a8069b19113745ed79612b0ebNetworkManager-glib-1.4.0-19.el7_3.x86_64.rpm8be1252e691a6e0f386b2fb1eec8784e83dcf5ee6b152557e141ee015f9e8ef7NetworkManager-glib-1.4.0-19.el7_3.i686.rpm86674348704b9fcaade29f5ddd1f1cd8250dc1fc6dd17508793c3effb7e65b1cNetworkManager-wwan-1.4.0-19.el7_3.x86_64.rpm17f5a4ebb6167b2c40a630333c78744d1333e6b108f2a55ba654136f26954754NetworkManager-config-server-1.4.0-19.el7_3.x86_64.rpm5fc152e2be7d6716718aec119d60162f86b5e899dd07f42d6624c8c7a04acbb4NetworkManager-libnm-devel-1.4.0-19.el7_3.x86_64.rpma809adc01a369ee380e017a0cd65b2058f0062adac7b2390c777324eba8571beNetworkManager-bluetooth-1.4.0-19.el7_3.x86_64.rpm5d5e77aaeab6ec4e0f5246b426390a4f31eb8ed8a99af3984f7fd94c89e98e8fNetworkManager-1.4.0-19.el7_3.i686.rpm6108183ee57f1a003ac36522a0bd616c0dbef50dcd85d2d956c6aaf8bc9badf1NetworkManager-team-1.4.0-19.el7_3.x86_64.rpm16142ac0a23e7ad0dc3464a873f70899d9b932aa4acbdc5bcf592877d843c3eaNetworkManager-glib-devel-1.4.0-19.el7_3.i686.rpmb74e7493663376686a756150c41a94f620d63d29b755c546e628f0437c32e065NetworkManager-tui-1.4.0-19.el7_3.x86_64.rpm96c6dc19e715d67eb59e7116588eb7c8be8c07dec8b9042eb998b48349ea4c46NetworkManager-libnm-1.4.0-19.el7_3.x86_64.rpm5868f2b79ab9744392a46d64e57299d6041fcd15b6a253a24a2e533446e72234NetworkManager-1.4.0-19.el7_3.x86_64.rpmd5e4449fc1ac309c4db9e9f8db45cfd5bf49086dc03640d0ae6335a24d9c60eeNetworkManager-glib-devel-1.4.0-19.el7_3.x86_64.rpm85553e003277a82cb4827b5da2d94f64b9a254da7444f8e1a2f351f4c98f85c5NetworkManager-libnm-devel-1.4.0-19.el7_3.i686.rpm3ddcc8eec087c704f85abf0e00dcdc09d874174eb12c2357d924b261dc1ca3b3NetworkManager-adsl-1.4.0-19.el7_3.x86_64.rpm28e6b0a6326c8d97e41ae2d941976af461c790f4fe4a99c1349f2c013ecff529NetworkManager-wifi-1.4.0-19.el7_3.x86_64.rpm6b0818fc49c3ac1254db0bb861d18a31ed1b263e76ace9a56a50b6850c2a3594SLBA-2017:0929-1This update fixes the following bug: * When an AgentX subagent disconnected from the SNMP daemon (snmpd), the daemon incorrectly accessed the destroyed memory area at that timing. Consequently, snmpd terminated unexpectedly or looped indefinitely. With this update, a check to prevent the destruction of sessions with active requests has been fixed, and snmpd no longer crashes in the described scenario.Scientific LinuxScientific Linux 7net-snmp-devel-5.7.2-24.el7_3.2.x86_64.rpm4816aa9b29c93a2cd806f0d3ff196b8ab9c12c0dc15e2af3b66f698a4eccc349net-snmp-5.7.2-24.el7_3.2.x86_64.rpmda2a37c0a1e691407db31110280daa2453d4d58a7df9b72c3af9b0724c77f3a5net-snmp-sysvinit-5.7.2-24.el7_3.2.x86_64.rpm68ab8f4599c9969fca8b31ce6646318268028e114a270aa087e647671225278anet-snmp-perl-5.7.2-24.el7_3.2.x86_64.rpm8f1906348545f91ead87cd78c986cc8f30b7d32476432ad8135da7b10a1ef68bnet-snmp-libs-5.7.2-24.el7_3.2.x86_64.rpm86aa060610434acb4d90082aa4fc9e8b17d4cb2317714dee47b5bdb6f17acbafnet-snmp-gui-5.7.2-24.el7_3.2.x86_64.rpm8a0f8cec14c9e04855892b62e0ff11ee65805869bb55d8add0198a538955593enet-snmp-python-5.7.2-24.el7_3.2.x86_64.rpmb39b78236ba0860dbc4268066cb25d657b999c5789860336db7109da2d271bd3net-snmp-utils-5.7.2-24.el7_3.2.x86_64.rpmbd267d03cd020601f6e9654ea4779528e266441fbc30c972b75237071088a763net-snmp-agent-libs-5.7.2-24.el7_3.2.i686.rpm20fe72a52dc8e4ccf64dc3b129f31adc6ff17da3b4856fc39b4548510d2b778fnet-snmp-libs-5.7.2-24.el7_3.2.i686.rpm27ee83f62ffa0996ccb60f8abec51aee23fa60dfa8c445f13a48b8ceb0dc3409net-snmp-agent-libs-5.7.2-24.el7_3.2.x86_64.rpme0c42cbebd930e997649a689f8a270b305dafb8d146c96e9792fda7d983c9184net-snmp-devel-5.7.2-24.el7_3.2.i686.rpm095e87b565e6377020f20b85785d05161fae59d1589fa44cfefe868b579035bfSLBA-2017:0930-1This update fixes the following bug: * Due to a switch from positional arguments to named arguments in the Nova python client, creating a Nova connection inside the fence_compute agent previously failed on OpenStack Ocata. As a consequence, the fence_compute stonith device failed to start, and the force-down functionality for the nova-compute service was not available. A patch has been applied to and the described problem no longer occurs.Scientific LinuxScientific Linux 7fence-agents-virsh-4.0.11-47.el7_3.5.x86_64.rpm5ca9b19f86db23c640d854dacd4bcd73eabd648cbd6554f799d96a7414a75732fence-agents-ilo2-4.0.11-47.el7_3.5.x86_64.rpm38588d367e0f0e3d3a56b43be589dfb194d941cd10069be3471a477a0cb6de82fence-agents-apc-4.0.11-47.el7_3.5.x86_64.rpmfe4b4b995399194edf861eaf0a934af20df2281922971cf2290f6633063072fbfence-agents-apc-snmp-4.0.11-47.el7_3.5.x86_64.rpme4f205b2ed42824f2fe8e820de083c71b1ced6528e5541b1a57bdb25cb2165a6fence-agents-eaton-snmp-4.0.11-47.el7_3.5.x86_64.rpm93981b86a2e01925e6d0c97ecd209be508986c73c809eb31d1a78dfbd950452afence-agents-compute-4.0.11-47.el7_3.5.x86_64.rpm4bcb795947a06937c33a72259424e19774fcb2de997da69dbf68e7b5b8e3d330fence-agents-cisco-ucs-4.0.11-47.el7_3.5.x86_64.rpmef5a56073d99389bbfabddecdc4a51a52426274d711fedf46b9311a6c522a136fence-agents-bladecenter-4.0.11-47.el7_3.5.x86_64.rpm02a38fd05f3d6431c5a1cd183c2bdd5b4b8a9db35710b015227537da2b3e8fc8fence-agents-ilo-moonshot-4.0.11-47.el7_3.5.x86_64.rpm6c898e9f261492a995091c0518a80cb19b0d1024757d6ebfd66957ffebae1e54fence-agents-mpath-4.0.11-47.el7_3.5.x86_64.rpm230c2ef05a51504c957fa2f1dc755cd5f632b59d55265469b8e48983dc741340fence-agents-ilo-mp-4.0.11-47.el7_3.5.x86_64.rpmf829a125c13dc57fdbc31c8412362df960b9048c3391755b28d901c7a87a81b0fence-agents-kdump-4.0.11-47.el7_3.5.x86_64.rpm9356cb48eda9bd13894449a07a9486b1dc8742f742a4bd7e728a0e4b0cd5f3fdfence-agents-ipdu-4.0.11-47.el7_3.5.x86_64.rpmd53f06473bec996de92479bf8b49499d3f06f1d9dbe8bec094c2b50c5dd1db29fence-agents-ipmilan-4.0.11-47.el7_3.5.x86_64.rpm1cc02ce95c1ca2eeea7d1e4bb1cb23b0b271e88587631a579d67912f15412077fence-agents-ilo-ssh-4.0.11-47.el7_3.5.x86_64.rpm744ec35fda364fbfaef40f532c96b16ca4a751c74f2da1482ceb4e151c3c5df6fence-agents-vmware-soap-4.0.11-47.el7_3.5.x86_64.rpm5e20c1736ab2bf3557082b40bb7b1e7061feafb9de011c97920402f5b52b3a77fence-agents-brocade-4.0.11-47.el7_3.5.x86_64.rpmafe43e418c433909ca663eb4b3bc5cf8f2df456d4a385e2fc278587cf90b10c8fence-agents-eps-4.0.11-47.el7_3.5.x86_64.rpmc0d7604c4a21d97be95f47cbe8b220f46ab6aa859b3de68b998c1c980b607f6bfence-agents-rsb-4.0.11-47.el7_3.5.x86_64.rpm5f578a9c75f4cfa5038db505c2d5906bfbc494fb05b7d43c1732cee4d4e0b633fence-agents-rhevm-4.0.11-47.el7_3.5.x86_64.rpmc8b2d6702c8ad3a9d9a1473ec7aa24f3c5b764f70ec413ce039cf0baae0a8969fence-agents-cisco-mds-4.0.11-47.el7_3.5.x86_64.rpma74dfd02cca6256eb3fa50873a4c1c6f8b87692cebb411802232842ef6340038fence-agents-drac5-4.0.11-47.el7_3.5.x86_64.rpm344a28fb99b5b43aa72762d22540a96bdb39f317709018d67192e4ff09bbf90bfence-agents-emerson-4.0.11-47.el7_3.5.x86_64.rpm453c467dacb98ef9513997982af87e5c9c74007e798c3673248368b22377e871fence-agents-scsi-4.0.11-47.el7_3.5.x86_64.rpmdccb29e65204f80be737ad9726279be29f81884ea80dd0849ef83ae655e492dbfence-agents-rsa-4.0.11-47.el7_3.5.x86_64.rpm2c4044200df68a0f4c221cb3b662f1a5dd5ef4bec49b961dc0764984466a05d2fence-agents-intelmodular-4.0.11-47.el7_3.5.x86_64.rpmef3cbeac8b574cada672720911682b995a20692feca1cae86a274b922bd2e4a3fence-agents-ibmblade-4.0.11-47.el7_3.5.x86_64.rpm715383fc645cec9dd93ebf291566252d5b5d1977f795afba9c511ec7f3d78ba2fence-agents-wti-4.0.11-47.el7_3.5.x86_64.rpmbf5adf1a43a0d9ab048cdf68ac1a3dfb3176cecb3211a98410f42c793d39f708fence-agents-hpblade-4.0.11-47.el7_3.5.x86_64.rpma27173eda7428c471234d9dd50cd607f1ef8c3e0b92693ce6771cbffba8c48e4fence-agents-common-4.0.11-47.el7_3.5.x86_64.rpm396665c14b945466045cf0c2f7634ff6c014e4960d4e9d90b073b730c4667cbbfence-agents-ifmib-4.0.11-47.el7_3.5.x86_64.rpme7e692cb6197a8bf507550027c327490c8bc6d469b2e9d3e5d7588e2056314e3fence-agents-all-4.0.11-47.el7_3.5.x86_64.rpmfa4a4a020fa0387757153f2425738f08fb6618969b53e1aa98ae2983d4f0286eSLBA-2017:0992-1This update fixes the following bug: * When the clvmd service used the cpg_mcast_joined() call, corruption of the inter-process communication (IPC) ring buffer in some cases occurred. As a consequence, the Corosync engine entered an endless loop, and sometimes caused unavailability of services on a server node managed by Corosync. This update implements a mutual exclusion algorithm to protect cpg_mcast_joined(), which prevents the described problem.Scientific LinuxScientific Linux 7lvm2-lockd-2.02.166-1.el7_3.4.x86_64.rpmf4a677c356c3db8450fac2f29e5558e901a3046b3e578d2efa204821e66fca14cmirror-standalone-2.02.166-1.el7_3.4.x86_64.rpm8870f21acb831720ac0ee5b2e6f6e3ab554fc43892f2c4b74e0feab733d9da26cmirror-2.02.166-1.el7_3.4.x86_64.rpm5e58e7ee1fd3624f058eb19f22488de257622c890a7d9aff551bafc29cc2231elvm2-2.02.166-1.el7_3.4.x86_64.rpm64009d32f5a8b28e5cfc1975df0ad663445af97e13ae4747999e2df1b7d34702lvm2-devel-2.02.166-1.el7_3.4.x86_64.rpmd218410d5a95f5657c01e1d087a59447543877185ac9248d311d79fbe6e1f849lvm2-cluster-standalone-2.02.166-1.el7_3.4.x86_64.rpm6b186907454d3f9f97fce407b474779d05bdf89b517a84f06b96ce8c6a8dc7d9device-mapper-event-1.02.135-1.el7_3.4.x86_64.rpm2ce9b56b1d85135dca8657aa88280d345ceaf5f9e9fc03aa6a77b74b1c899156lvm2-libs-2.02.166-1.el7_3.4.i686.rpm6328f1cef03222bd963ba64e2a4cbbb5093f66ad8caee7baaf55bcb22b84a00elvm2-libs-2.02.166-1.el7_3.4.x86_64.rpm5a6c28e1e22b41a67bb3409f452fc092fbe077c014b7c13a8b2c73ce4a87cfcfdevice-mapper-event-devel-1.02.135-1.el7_3.4.i686.rpmda84db0b155a4bc7855ca836977b6bc86905022177d5098a3812b84b928edbbedevice-mapper-devel-1.02.135-1.el7_3.4.i686.rpmd7750ad06e21c29112f13e6bf4c52a752f6dd6d239f539f55dc626a0b4565a89device-mapper-libs-1.02.135-1.el7_3.4.i686.rpm63fabce7cb1c93e8449018856f2f473a59988b73dfbb88944362a62a60c8fc36lvm2-python-libs-2.02.166-1.el7_3.4.x86_64.rpmb7039eef8ca9a18681b17062fb9ac9ced1de6369214d6364668c7a264dfe3b46device-mapper-devel-1.02.135-1.el7_3.4.x86_64.rpm6ae8037e723cffefe7f119c3c61ee903f871e025c558d9f9d6a3cb6b9833c096device-mapper-event-libs-1.02.135-1.el7_3.4.i686.rpma53d8ac08d0e3b9c44a231493808756df3088c63a8a85eb5a0609afce8634e3fdevice-mapper-1.02.135-1.el7_3.4.x86_64.rpmbf55923d0d12449a4a96af0fd94951898aa93840d9e8ff20fb2f450703797d5fdevice-mapper-libs-1.02.135-1.el7_3.4.x86_64.rpm078c6c604d0730b169d019a7fd925d027596d74527e7ce1b01a7333b654d7278lvm2-devel-2.02.166-1.el7_3.4.i686.rpm1d61f3167245936d278d532185084a332c2387364c716386dfb1cf0c4553f01fdevice-mapper-event-libs-1.02.135-1.el7_3.4.x86_64.rpm3e9b087fa70a229f64d67ea16fc66250341b314e644f5a693538f4e32c4e83aflvm2-cluster-2.02.166-1.el7_3.4.x86_64.rpm03d31949f04f08c05b530f4f154b14942e2052ae340b3189ac3503c153d725d7device-mapper-event-devel-1.02.135-1.el7_3.4.x86_64.rpmb9ed940a0471d6170b1092e79cd440c70b8e0e8935c237433d4911f56d2c2ccelvm2-sysvinit-2.02.166-1.el7_3.4.x86_64.rpm583b3f25baf417bbdce21d761e21633acfe18d645fbbc228ff26ee2c44d56319SLBA-2017:0993-1This update fixes the following bug: * Previously, in certain situations, a corruption occurred in the Inter Process Communication (IPC) buffer. Consequently, the libqb library ran into a spinning loop and caused the application to become unresponsive. This bug has been fixed, and now libqb works as expected.Scientific LinuxScientific Linux 7libqb-1.0-1.el7_3.1.i686.rpm9c6a137f89307ec37b010b180a764d32dbb805edabf293b523e236480536711clibqb-devel-1.0-1.el7_3.1.i686.rpmf401217dcf60ea0bc462464e6c2d3e9e9864ac629ff53c5b09abf2868461b9d2libqb-devel-1.0-1.el7_3.1.x86_64.rpm296efa0ad3436bd09211ab5ebac1d9e4704c049ea43ddaa3d5f65eab52c1f071libqb-1.0-1.el7_3.1.x86_64.rpmb33ccfca6fca44f3922ab36c07f5f369ece1d95892fa1eb1362aeb3a268177d1SLBA-2017:1299-1This update fixes the following bug: * Previously, loading the ocrdma module for Emulex OneConnect cards at boot time, including those that do not support Remote Direct Memory Access (RDMA), caused the kernel to be tainted with the Technology Preview status. With this update, the module is not loaded automatically, which fixes the problem. To re-enable automatic loading of Technology Preview modules for RDMA support on capable hardware, the user can edit the /etc/rdma/rdma.conf configuration file for the RDMA infrastructure.Scientific LinuxScientific Linux 7rdma-7.3_4.7_rc2-6.el7_3.noarch.rpm430f2276a3ec65d9be64f20b3d9324e597efb86d08f4e761e5967079d6c31da8SLBA-2017:1301-1The libnetfilter_conntrack packages have been upgraded to upstream version 1.0.6, which provides a number of bug fixes and enhancements over the previous version. Notably, this update adds support of IPv6 Network Address Translation (NAT) to the libnetfilter_conntrack library. As a result, libnetfilter_conntrack can now create connection tracking for IPv6 NAT entries.Scientific LinuxScientific Linux 7libnetfilter_conntrack-1.0.6-1.el7_3.x86_64.rpmed4f9cfdd64c90262c16273d617caafe0457f6474c778756fba4dfbaaed55b53libnetfilter_conntrack-devel-1.0.6-1.el7_3.x86_64.rpm31a5d5403c7188bb2723de47df6f2ee3c29985e30e851e24a9d457481f03428clibnetfilter_conntrack-devel-1.0.6-1.el7_3.i686.rpm915fc397cb584d276c7a2a3d4c5701b626ae1f98483e91daeba08db44a130447libnetfilter_conntrack-1.0.6-1.el7_3.i686.rpm91b759dd38dfce586f2119899588130b4ed93bf8450610ce880978b2da02a19cSLBA-2017:1302-1This update fixes the following bug: * On systems with the nscd daemon enabled, the getaddrinfo() function in glibc could access uninitialized data and consequently return false address information. This update prevents accessing uninitialized data and ensures that correct addresses are returned.Scientific LinuxtrueScientific Linux 7glibc-headers-2.17-157.el7_3.2.x86_64.rpm7055a27c736cc32a4ff1457428b56a9e2a57bd4ef022d88d8a640ddeda6f2fe7glibc-2.17-157.el7_3.2.x86_64.rpm31af2d4ae141c6da3c3d31282b6bd56a072b210fb19b941174b4aeacf8fee496glibc-devel-2.17-157.el7_3.2.i686.rpmc4138374190c42fc55be1059f527faeff30ce58862113f5d25f958668753f959nscd-2.17-157.el7_3.2.x86_64.rpm6c78df83e22b11b9e0bb6914c22f57b0245296294d3ff06d163a6017e1a1514bglibc-static-2.17-157.el7_3.2.i686.rpmfc2ed728cea914a6fd4560b60361a42394e01d8cfe470b51762e742e1ce2118aglibc-devel-2.17-157.el7_3.2.x86_64.rpm2aa47d4336127ca4e7f949effc52906946b0433483d5daeaad3069749e996aa4glibc-utils-2.17-157.el7_3.2.x86_64.rpm231c296f83364cff4e1212431b2eb63bba5f7cea63945902567b6cc2c2fc9e51glibc-common-2.17-157.el7_3.2.x86_64.rpm94ac525da59151c66da978f69b1602b0bd515e27fb3b5055d2ed5f1b27c99a50glibc-static-2.17-157.el7_3.2.x86_64.rpm4af8e9cdc11a6114b8b7b10cda52e1d3278274e8cf2458c4a7b832a771168931glibc-2.17-157.el7_3.2.i686.rpm4255d60f921b94ed0fa53a687e8ede00f775c84000543eb6174c314c812aedfbSLBA-2017:1303-1This update fixes the following bugs: * Certain storage devices report optimal I/O size values that are not divisible by their reported minimal I/O size value. Previously, the mkfs.gfs2 and gfs2_grow commands attempted to align GFS2 resource groups to unsuitable boundaries. As a consequence, mkfs.gfs2 failed, and gfs2_grow sometimes terminated unexpectedly with a segmentation fault. With this update, mkfs.gfs2 and gfs2_grow no longer attempt to align resource groups to unsuitable boundaries, and the described problems no longer occur.Scientific LinuxScientific Linux 7gfs2-utils-3.1.9-3.el7_3.1.x86_64.rpmac1290c0dea4c896105b5fd0bc825bc5849f274d8ec78ba1690b3a4423e100a0SLBA-2017:1304-1This update fixes the following bugs: * Previously, the libvirt daemon failed when starting a domain where the network interface script path was an empty string. Consequently, this caused the migration of some virtual machines from Scientific Linux release 7.2 to release 7.3 to fail. With this update, libvirt accepts an empty string as a valid script path but does not execute it. As a result, the migration of guest virtual machines from Scientific Linux release 7.2 to release 7.3 succeed. * Prior to this update, when saving and restoring the MAC addresses of Single Root I/O Virtualization (SR-IOV) virtual functions (VFs), multiple problems occurred. These problems occurred when the addresses were used for both hostdev assignment and macvtap passthrough mode. With this update, these problems have been fixed * Previously, on very large installations, libvirt sometimes failed to start some guests and displayed a "Too many open files error". With this update, the default open file handle limits have been substantially increased for the libvirtd, virtlockd, and virtlogd processes, allowing for several thousand guests on a host. The limits can be increased further in the systemd service files for these processes. * Prior to this update, hotplugging user type interfaces was blocked. Consequently, users were unable to hotplug user type interfaces. With this update, the block has been removed. As a result, users can hotplug their interfaces. In addition, this update adds the following enhancement: * In this update, the Level-3 CPU cache can be enabled for virtual CPUs using the <cache level='3' mode='emulate'/> sub-element of the <cpu> element in the domain XML. This can significantly increase performance in some workloads. After installing the updated packages, libvirtd will be restarted automatically.Scientific LinuxScientific Linux 7libvirt-lock-sanlock-2.0.0-10.el7_3.9.x86_64.rpmfb25e9fe2be10dee0c85fe0be90d36af2e07723830a05ea2d316802f40f79656libvirt-daemon-driver-qemu-2.0.0-10.el7_3.9.x86_64.rpme815d44a6baa90ef1f65e183d6ce00047cc3b6b6453ea972fcb8b1084c240a41libvirt-daemon-config-nwfilter-2.0.0-10.el7_3.9.x86_64.rpm46c4e96c243c1656359618b9c68deaf9cabe9631b576f65866668ccea3f38fadlibvirt-2.0.0-10.el7_3.9.x86_64.rpm200523cb4dd90f7204f225ba94443a57c6be7b65e86af2462ec6c9d80a6cdd07libvirt-daemon-driver-lxc-2.0.0-10.el7_3.9.x86_64.rpm0edda2c7793fe985925533c9f55dd9bbaa593e42c642fd3aedae29fc7ccb50d0libvirt-nss-2.0.0-10.el7_3.9.x86_64.rpm311e55ec8165780c703564bdf6e47b3649ac8d6498786819ee70064c5a85eae2libvirt-daemon-lxc-2.0.0-10.el7_3.9.x86_64.rpm8f49e03177cdc8f947e539833913754b206c1da873a41e54868bf2dc106ba4d7libvirt-daemon-config-network-2.0.0-10.el7_3.9.x86_64.rpm9d13296402aaeccd78b191537d772f3e3bafce68b8d5044e456200ead1546faelibvirt-daemon-driver-interface-2.0.0-10.el7_3.9.x86_64.rpm782b3f293b589e3d03a0a2b4ac67e32f865fed21d50f1c699f79257c96f27a62libvirt-devel-2.0.0-10.el7_3.9.i686.rpma3dfea6009f490da70b6d70a57b9d1626a372d5287befca4bf637be627b84635libvirt-client-2.0.0-10.el7_3.9.i686.rpm0f910f0ef4649a469bde0c5c00f1ec2859e8f3faa400a2e95b6f8977b80afb01libvirt-devel-2.0.0-10.el7_3.9.x86_64.rpm35341733c4718ecc9fe97b2582ef2a79d1d049b9f50e7b998015c2a76531cdfclibvirt-daemon-kvm-2.0.0-10.el7_3.9.x86_64.rpm8479dd1d1b682da572dfa99b2f8f4d66d94370833608299b3c9830a2dda47963libvirt-daemon-2.0.0-10.el7_3.9.x86_64.rpm86bd353dcd86b851393759f0befe94a91a276f0c8fa916c997fc04dde69922b6libvirt-daemon-driver-nwfilter-2.0.0-10.el7_3.9.x86_64.rpmf6eebbfe973faf880f7dc6b09396aae8f9b9efd27e8cae2712372619e8dc142flibvirt-docs-2.0.0-10.el7_3.9.x86_64.rpme879627f56d350ae356836921bc7a35928a382836277daeaa6c07f3ef2a892calibvirt-login-shell-2.0.0-10.el7_3.9.x86_64.rpm617be14c6d3e2fe76afa797dd05f9e62fcd72cc9e1e969af80b216d42ed10aa8libvirt-nss-2.0.0-10.el7_3.9.i686.rpm873502c74ca12dbea56403b8c7c52c1d06739b4f9e044d0ae4cd9df7e0bb4e61libvirt-daemon-driver-nodedev-2.0.0-10.el7_3.9.x86_64.rpm791b66a6a82ef003df6ab8081eb90e4e5628023cbd030a6686993b0b9643dd46libvirt-daemon-driver-storage-2.0.0-10.el7_3.9.x86_64.rpm0db4419e118cce331e9a698147cbfae6e8d7d252922b5c6de95ae2287037ea9alibvirt-daemon-driver-secret-2.0.0-10.el7_3.9.x86_64.rpm8cc8fac4b61c6df6fb2456a1ce6bc92480235f15c43262ae87198573891c6e3clibvirt-daemon-driver-network-2.0.0-10.el7_3.9.x86_64.rpm4ee5f7f97eef93cfbe1b43929fa7b24f2294ece6cc5ebcf4b4f16f1aa56229b6libvirt-client-2.0.0-10.el7_3.9.x86_64.rpm66075f2209094e1b6efed0969d063f6541857f07e6f9be6743d85ba195801929SLBA-2017:1305-1This update fixes the following bug: * Previously, the keepalived utility attempted to close a large number of file descriptors each time a notification script was invoked. As a consequence, keepalived generated many unnecessary close() system calls in an attempt to close file descriptors that were not open. This bug has been fixed by using the SOCK_CLOEXEC flag when opening all sockets, and the FD_CLOEXEC flag when opening all file descriptors. As a result, the number of close() system calls is no longer excessive.Scientific LinuxScientific Linux 7keepalived-1.2.13-9.el7_3.x86_64.rpm305e0ec5284fbe2103f4bd1fddfcdf93c7b8aebf4a2e429055c8c98ee14e1321SLBA-2017:1306-1* Previously, the libpolkit-gobject library did not correctly free memory when updating the state of the PolkitPermission object. Consequently, this could lead to unexpected termination of some applications. The bug has been fixed, and libpolkit-gobject now works as expected.Scientific LinuxScientific Linux 7polkit-0.112-12.el7_3.i686.rpm93944446c9e7c8f9e87648342759e12cb061e042f07b0c0190ece468245f5944polkit-devel-0.112-12.el7_3.x86_64.rpm232fd1bd720fc4757d74730e31510c646ff70df813608a439127ba7eeb94fce5polkit-0.112-12.el7_3.x86_64.rpm5590d220b9031e2b6ffab5e6067a8e746888cbbce22811d3cc0c4c0c8de6bdbapolkit-docs-0.112-12.el7_3.noarch.rpm668e19f45d629111846df911b4e2c0cb1a7d064196a08fd5f5235e06acda5494polkit-devel-0.112-12.el7_3.i686.rpm912f01c0c7e5361e313e73146c867d043c9fefd4f225f4ce57a3e5885c820622SLBA-2017:1311-1This update fixes the following bug: * Previously, if there was a require dependency between units (for example, neutron-openvswitch-agent requiring openvswitch), restarting was propagated to the dependent unit even if the dependent unit was not running. For example, restarting openvswitch started also the dependent neutron-openvswitch-agent even when it was in the stopped state. With this update, restarting propagation has been changed to try-restart, and stopped dependent units are no longer started. As a result, neutron- openvswitch-agent remains in the stopped state in the described example.Scientific LinuxtrueScientific Linux 7systemd-resolved-219-30.el7_3.9.x86_64.rpm5674df642e1e3c5c95509232679125f5b2a7945c96423d4d2c1cc985d108d6absystemd-devel-219-30.el7_3.9.i686.rpm804adae4fc12ccb234538d0adbe459abe4b09304c0258bd9101ef7dbdd506f77systemd-libs-219-30.el7_3.9.i686.rpm252424c6e6d85a7be55c5dae1345b3140bca3ad40f476f71da0dbac51a186c96systemd-journal-gateway-219-30.el7_3.9.x86_64.rpmc7ae8d8b95835033f17962f6ed19b3ffa73d18439c94de403951e99af31c8a71systemd-libs-219-30.el7_3.9.x86_64.rpmb7f508c2f6bbd8e8210b49096a1aa24993384668a524ed0df2f9768e088edffcsystemd-sysv-219-30.el7_3.9.x86_64.rpmefa32638b9b4ff743d55601a41bd57e9c2ce061799f528c5f0bbe89f99aef507systemd-resolved-219-30.el7_3.9.i686.rpm7defe7170a5584e3e9d3c7653630081c7ed9b731c0a25470dd9500d5af6a0932systemd-devel-219-30.el7_3.9.x86_64.rpmde442cc834e0e4a4d0d9d44323d021982acf58742865feae586f17f283fbbe40systemd-219-30.el7_3.9.x86_64.rpmf90e3479894075aeac4a77d8c872d80b66c64a3805ac216d5610f9981158f7f4libgudev1-devel-219-30.el7_3.9.i686.rpm1c4c4e5ae9e762e54b0f2fce850b1403ff7a73c5a35637099953a725d494da93libgudev1-219-30.el7_3.9.x86_64.rpm4a6815e4fc70c60293ea764f496e6ea4c44b89d261af976cc056a05b8753c1e2libgudev1-219-30.el7_3.9.i686.rpm9bc9642d2b44eda3690517a89e3fc1c1bf8d14fda99e3a2144ee0d954e7b64ffsystemd-networkd-219-30.el7_3.9.x86_64.rpmb98daf618022a22a6ca99712fc2991d4ccb0fb59949273ed92d0817646c57773systemd-python-219-30.el7_3.9.x86_64.rpme3316e1df6a3bd21652e9a0f1da40b8cb019e11e1a44916d9a490291f672d3e7libgudev1-devel-219-30.el7_3.9.x86_64.rpmd189787fee8a1aa0db37baa03b2dfabd5fa23b4d57868434d72ed98a4cd9df1cSLBA-2017:1312-1This update fixes the following bug: * Previously, GTK+ applications utilizing client-side window decorations were not resizable for users using the Motif window manager. This update fixes the bug and those applications now have resizable borders when managed by Motif as expected. An example application demonstrating the bug fix is the Evince PDF viewer.Scientific LinuxScientific Linux 7gtk3-3.14.13-20.el7_3.1.x86_64.rpm974e2a15b88088d27119b17ba26b5b30d075dc6bd0c6d7399fa61d2b3df57df7gtk3-devel-3.14.13-20.el7_3.1.i686.rpm92707ebf149a96ef6ffdd06bfaa762efd3587544ff522123a7d88d2456fa2f03gtk3-devel-3.14.13-20.el7_3.1.x86_64.rpmad6033c02a7e832963e9955edd841e651def9cf5552c6ece59b1991fe4d15518gtk3-immodules-3.14.13-20.el7_3.1.x86_64.rpm1fca0b083e5fae146574a73bcd981c385d9cc6d3f6ca574b9c5af8c35d299778gtk3-devel-docs-3.14.13-20.el7_3.1.x86_64.rpm24c78fd73efa3fa831d6753bfc4bf605b0b57425fdc861fe106a5c997d3b0b08gtk3-3.14.13-20.el7_3.1.i686.rpm7e239cf9b0406fc7994b1e7fddc9b52a15694e055d941c15de6c2fa5f6421072gtk3-immodule-xim-3.14.13-20.el7_3.1.x86_64.rpmb5dead20202e9754f55bd5c08c887911e11615f97a24931db3681a728e88c213SLBA-2017:1313-1This update fixes the following bugs: * The replica data structure is protected by a lock. Previously, if the first direct update on the server failed, a thread that acquired the lock did not released it. Consequently, the server could no longer use the replica data structure and further read and write requests hung. A patch has been applied to release the lock in the mentioned scenario. As a result, the server now works correctly if the first direct update failed. * Previously, target attributes used in access control lists were processed in a case-sensitive manner. This caused ACLs to behave unexpectedly when entry an entry's attributes used a different case than the attribute in the ACL. This bug has been fixed by ensuring that evaluating target attributes uses case-insensitive comparisons, and ACLs now work as expected regardless of the case of the attribute names. * The retro changelog attribute plug-in (nsslapd-attribute) previously did not allocate enough memory for the attribute list. This caused a crash on shutdown when the plug-in attempted to free memory in use by these attributes. This problem has been fixed by ensuring enough memory is allocated to retro changelog attributes, and the crash at shutdown no longer occurs. * Previously, the FullMachineName parameter was being ignored and overwritten by the server's nsslapd-localhost setting during derver upgrades using a silent install INF file. This caused upgrades to fail on servers which were behind load balancer and required a different host name to be used during the upgrade process. With this update, if the INF file contains a FullMachineName parameter, this parameter is correctly used and not overriden with the nsslapd-localhost setting. As a result, upgrades using silent install INF files work on load-balanced servers. After installing this update, the 389 server service will be restarted automatically.Scientific LinuxScientific Linux 7389-ds-base-snmp-1.3.5.10-21.el7_3.x86_64.rpm584cc041ab683f9af4c2982efeb13256968f154484f7c111c9f61ecd35f5ed50389-ds-base-libs-1.3.5.10-21.el7_3.x86_64.rpme6eab5249233504ce66c4ee64fae0bfb062853cb4851ecb250955b998dc684ec389-ds-base-devel-1.3.5.10-21.el7_3.x86_64.rpm8b39fb296d457a69389aff02b22df52429d56d64579017daedb2e7877f5ce8e2389-ds-base-1.3.5.10-21.el7_3.x86_64.rpm911f0d97a38ca46af176e93dee7ef8ea71d8d0ea7a3c2191c7f8e6321be1f378SLBA-2017:1314-1This update fixes the following bug: * When dynamic host configuration protocol (DHCP) was used, the dracut service previously failed to apply the host name specified by the "ip" kernel command-line argument. This could cause a variety of problems, such as failures to install or boot Scientific Linux. This update ensures that the host name provided on the kernel command line is applied properly, and the described problems no longer occur.Scientific LinuxScientific Linux 7dracut-caps-033-463.el7_3.1.x86_64.rpm25f8e9122cd3adbf470cc7f60a531f4c57129e924ffa0329cce3c17fe6b996efdracut-tools-033-463.el7_3.1.x86_64.rpm3bfc2d197d61fb895eaf909e2fe4f11e5e19cb679edf985e1b16513208341971dracut-fips-aesni-033-463.el7_3.1.x86_64.rpmac4749194ec5163dc31420b776d9e9e7a9405768925349e1b99fd5f2128e69dadracut-network-033-463.el7_3.1.x86_64.rpmf68954be3f30c77b5359f6759e6a615c36dc3f529fac0d04a456137a96b5e37bdracut-config-generic-033-463.el7_3.1.x86_64.rpm85897263e2f929a620506259ab94c48e0066e846daea5b1a424094ffcd1d328cdracut-config-rescue-033-463.el7_3.1.x86_64.rpm9945e05f6d8b81cffb8900b8815f131ee7cd536d7ef8b5a7a1f75df39a7af100dracut-033-463.el7_3.1.x86_64.rpm2bb99549ff66d7047f42c676865566622e34ff5e8f2213dcb43d275a28a43da7dracut-fips-033-463.el7_3.1.x86_64.rpm9833ee9a13ffd9d1ed92d56aa72c9204ef302c397272f9010759364a8cf17a03SLBA-2017:1315-1This update fixes the following bugs: * The IPaddr2 resource agent creates IPv6 virtual IP (VIP) addresses that are used as source addresses for routing by default. Previously, when the VIP was moved, it could cause problems for certain OpenStack services. This update adds the "preferred_lft" parameter to adjust the source IP address. When "preferred_lft" is set to "0", the IP source address remains the same as before starting the VIP. As a result, OpenStack services work as expected. * Previously, if no data was available in a Galera cluster the current node was chosen as the "fallback" node to bootstrap the cluster. As a consequence, every node made a different decision when choosing the "fallback" node, a situation which could lead to single-node clusters of Galera. With this update, the algorithm has been changed to yield coherent results across all the nodes.Scientific LinuxScientific Linux 7resource-agents-3.9.5-82.el7_3.11.x86_64.rpme26d6513ece60978cdbde1d819d402c09262a16cf34f8116bd4a3b654b7397a7SLBA-2017:1316-1This update fixes the following bug: * Previously, rear did not preserve Linux capabilities set on the original system during the backup phase. The recovered system was subsequently missing these capabilities. With this update, Linux capabilities are correctly preserved if the directive "NETFS_RESTORE_CAPABILITIES" is set to "y" in the /usr/share/rear/conf/default.conf configuration file. (BZ##1434519)Scientific LinuxScientific Linux 7rear-1.17.2-9.el7_3.x86_64.rpmc170f1499665f7f69dbd82446aa11677e5a9a344c42b8f00231291851fde28c1SLBA-2017:1317-1This update fixes the following bug: * Previously, NetworkManager in some cases failed to initialize the Maximum Transmission Unit (MTU) of a VLAN device to match the MTU of the parent interface. The bug has been fixed, and now the MTU is inherited properly.Scientific LinuxScientific Linux 7NetworkManager-config-server-1.4.0-20.el7_3.x86_64.rpmff1b399cf3f3f255b18bebee882d81d1bbdd302f7063294e8bf1eb9ae2e893d5NetworkManager-glib-devel-1.4.0-20.el7_3.x86_64.rpm8f63948fb5115606aedeb541fed152dc57f948b8cbb45cd93345c2e3df453b28NetworkManager-glib-1.4.0-20.el7_3.x86_64.rpm5c7c3efb9f16cb9e94b10e85d6318c8d9e3d0e3181ec965e06ff9bab108b19beNetworkManager-bluetooth-1.4.0-20.el7_3.x86_64.rpm0091b00b4b6b49ebba0598f4337c7fd1b18887c8f63347706f1485a22846a529NetworkManager-glib-1.4.0-20.el7_3.i686.rpm16b84e7cd14b821f506267b0be085670b3e672f27414c245bcd7fb4dd88fb747NetworkManager-wwan-1.4.0-20.el7_3.x86_64.rpmc586b2fd2cceb3f64033ec226039b8e7fa548f182988a28d975afb1203c5afe1NetworkManager-libnm-devel-1.4.0-20.el7_3.i686.rpmb927db19f519e9c58214944ab2484854728d4354d0c5d6d89e99b360beacb42fNetworkManager-adsl-1.4.0-20.el7_3.x86_64.rpm49bc9ead42f21fa5460a829740678194e25e63f3029af7998fcd9f5dcd1217e9NetworkManager-1.4.0-20.el7_3.i686.rpma34d218e33a4c258bf76d073dac5685c76ee44471729fc2bf5ac656a49c06324NetworkManager-dispatcher-routing-rules-1.4.0-20.el7_3.noarch.rpma1557475056933edce5719ada5ce99fedcc0732fe626449e957de102edb0289eNetworkManager-tui-1.4.0-20.el7_3.x86_64.rpmc58d91997eab837088816dba8bba181c83c33aa06bd0089ff855b586ea9fb423NetworkManager-team-1.4.0-20.el7_3.x86_64.rpma216bc42e8ae85b1ab70a6354fe1ccfac53ef7cb6c2804ceff993cbd14e2f80eNetworkManager-libnm-1.4.0-20.el7_3.i686.rpm57a23572c5a5a9bfe928e475ce1569bcd5d7747c19266542bc7d2b0d97556d06NetworkManager-glib-devel-1.4.0-20.el7_3.i686.rpm0b6711b6481d4a4110e47a245977ecf64d3081d5f0630981eeeb7f0a5a0c6773NetworkManager-1.4.0-20.el7_3.x86_64.rpm40178266011d2462dc0c5023cd976ec783943f02e1baa9e7e3ad04a9299efae2NetworkManager-libnm-1.4.0-20.el7_3.x86_64.rpmef487d2e6ae4464daff7c8a00d31d6702013a530a480f736f3c7df0290afff8aNetworkManager-libnm-devel-1.4.0-20.el7_3.x86_64.rpm5ff426c1fa3e3feb4606ca09cf59bbfd0a37185b18266fb774587f121095bcceNetworkManager-wifi-1.4.0-20.el7_3.x86_64.rpmd92c5a1504c83f3c65bafbec717261f3b32f7d8a8cb147af46f178dc473e9843SLBA-2017:1318-1This update fixes the following bug: These changes are part of a defense-in-depth fix to the HotSpot virtual machine. All running instances of OpenJDK Java must be restarted for the update to take effect.Scientific LinuxtrueScientific Linux 7java-1.8.0-openjdk-headless-1.8.0.131-3.b12.el7_3.x86_64.rpm5413b933f3ead71584b7a500e01234843ae2f3d7d572331dbf57d4d6e9c9f8d5java-1.8.0-openjdk-devel-debug-1.8.0.131-3.b12.el7_3.x86_64.rpm7c0cde8866aa3df27c37c40bd1af6a01ed03e5f1b8b3da15676cc18f2c3e5d1ejava-1.8.0-openjdk-accessibility-1.8.0.131-3.b12.el7_3.x86_64.rpm58332db2e90e01beda7b67d9c988195d47292483ad8f23a652e2c0572e94b912java-1.8.0-openjdk-javadoc-zip-1.8.0.131-3.b12.el7_3.noarch.rpma4b22c291c634da3eede1aac5de2f92a923b41e468c78daee219a26736d6aef9java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.i686.rpm4bbb057028f842b9318e4c8975347d203818ff48074c5c4d5993851e43acac3djava-1.8.0-openjdk-demo-debug-1.8.0.131-3.b12.el7_3.x86_64.rpmc6b4295960dfc5e3c3dbe9583133cff4426612b383a69ecf810cc2ba220cfc61java-1.8.0-openjdk-demo-1.8.0.131-3.b12.el7_3.x86_64.rpm1c64a5cba4f8ef7458273edb7f7effa26e993d092e11bc09cc4f41eb42dcbfbcjava-1.8.0-openjdk-debug-1.8.0.131-3.b12.el7_3.x86_64.rpm578c639f9f40ee741eb5546c1485d58dcd9c7d703d0a35a70c443e4f5af31745java-1.8.0-openjdk-devel-debug-1.8.0.131-3.b12.el7_3.i686.rpm9e604f15568f02187138ff87c0bca466343a054729498dc2b100c2d50eb783cdjava-1.8.0-openjdk-javadoc-debug-1.8.0.131-3.b12.el7_3.noarch.rpm9db798d42143eb464d7ab5d6ed4723c4bd44de8d6fb24c372550ee81a038a9abjava-1.8.0-openjdk-src-debug-1.8.0.131-3.b12.el7_3.x86_64.rpmd7e12844493c019c6fa894f7d95e64cb9aa9d93e86a1da35e6ccdfa2c86f5ea4java-1.8.0-openjdk-javadoc-zip-debug-1.8.0.131-3.b12.el7_3.noarch.rpme1cba3fcb9fcde17e4807985c9406c8108af3c3ecaf77d2a7f77392387577c52java-1.8.0-openjdk-javadoc-1.8.0.131-3.b12.el7_3.noarch.rpm1b464c579cf17882242c2b57e9138578cb57e83a9670f57e943f18286688fe6ejava-1.8.0-openjdk-headless-debug-1.8.0.131-3.b12.el7_3.x86_64.rpmbb6c0d0aadc00250a4a97f2f9761eb7d340492360ba2b9e56d495daa00788d12java-1.8.0-openjdk-accessibility-debug-1.8.0.131-3.b12.el7_3.x86_64.rpm9b29282c2b56d685b66ca315b24c98cd5dbe1e73156b175b95979213b5692695java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64.rpm19eb998cb2ef158027d01c914b815e2656fc64841768baf283f165fbda5d94d2java-1.8.0-openjdk-devel-1.8.0.131-3.b12.el7_3.i686.rpm0baa58eec8afb0332e672a4b9dd351b743f19a02c66a59775b971db3fc7fb9e0java-1.8.0-openjdk-devel-1.8.0.131-3.b12.el7_3.x86_64.rpm0820ac8e6e5dd850b57ec84855f5564ec4d54fea2d29b38ad3547b4cd746b78djava-1.8.0-openjdk-debug-1.8.0.131-3.b12.el7_3.i686.rpm1a51cd0420ae4f6b2f6318b6ccaa47934d394299925a99d508b833aacdb878a8java-1.8.0-openjdk-headless-debug-1.8.0.131-3.b12.el7_3.i686.rpm0d730f80d564ffccb004b7d9935922e929e7115106966affd2375b66527468fdjava-1.8.0-openjdk-headless-1.8.0.131-3.b12.el7_3.i686.rpmf8db529abd7cdc7d4d7661791b79da042a327d8ceed2f8ded09da4b4386ee37ejava-1.8.0-openjdk-src-1.8.0.131-3.b12.el7_3.x86_64.rpm06393fcde7c713c5bb2164bbfab8ade27acb2587c3e6e9a85fe7b00304a1936bSLBA-2017:1319-1This update fixes the following bug: * Previously, memory corruption in seabios could cause a Scientific Linux release 6 virtual machine guest to become unresponsive when rebooting. This update fixes the reboot procedure. As a result, the virtual machine reboots successfully.Scientific LinuxScientific Linux 7seabios-bin-1.9.1-5.el7_3.3.noarch.rpmc0966e27032c7a74f2c7a77bb10f9521d4a7d0a99c6dc76591e9814f09e4497cseavgabios-bin-1.9.1-5.el7_3.3.noarch.rpm91265ba75b50d6785d6fe19198f6a7a91a28301f5800e5461c69b08923106b25seabios-1.9.1-5.el7_3.3.x86_64.rpm1218bf82529f861f174c2be08230497ec250423d5658e7eb49c3c9d8df362473SLBA-2017:1320-1This update fixes the following bug: * Previously, the gdm-session-worker process terminated unexpectedly under certain circumstances during the initial boot after the installation of the operating system. This termination was caused by a bug in the libaccountsservice library and accountsservice daemon. The bug has been fixed, and the gdm-session-worker process no longer terminates during the initial boot.Scientific LinuxScientific Linux 7accountsservice-libs-0.6.35-14.el7_3.i686.rpm10c9d2afb3f74b160c72127ac3dbdd53a30027fa0c226d761473c443e52568dfaccountsservice-0.6.35-14.el7_3.x86_64.rpm14ed7922795fe95b20d5f3ffd86d4c5c87971a18baf1d60b6b041f5de0185c71accountsservice-devel-0.6.35-14.el7_3.x86_64.rpmc9e1ff42e43003a590445bfde57facade91e6283f9642681a66c2cd9843de668accountsservice-devel-0.6.35-14.el7_3.i686.rpme8eab231210f81a6c46f9147eb75e49ef0ca5a65fce7602f815e52ec80887c05accountsservice-libs-0.6.35-14.el7_3.x86_64.rpmef0349284136cf1041e56968c83ef15d167300cf0d46f066dd475b328879ba9dSLBA-2017:1603-1This update fixes the following bug: * Previously, when XMvn Installer was unable to parse bytecode, for example, new bytecode not yet recognized by the ASM library, it terminated unexpectedly. As a consequence, XMvn Installer was unusable for building RPM packages with Java 8 instructions. With this update, XMvn Installer no longer fails upon encountering unparsable JVM bytecode, and it can be successfully used for building RPM packages with Java 8 instructions.Scientific LinuxScientific Linux 7xmvn-javadoc-1.3.0-6.el7_3.noarch.rpmf0536526c7f80fa74d9c9af91fb9906c3fdb5e51d5bfac3562fde825a4a40ad8xmvn-1.3.0-6.el7_3.noarch.rpm8f601e38ad7a647cd8f69d1ce35a6034fa862a400ce005e466c88b0d4aa51501SLBA-2017:1604-1This update fixes the following bug: * Previously, after downgrading the "alternatives" utility, it was not able to read state files it modified prior to the downgrade. This caused "alternatives" to fail after the downgrade. With this release, downgrading "alternatives" automatically adjusts the state files to ensure that they stay compatible, which prevents the described problem.Scientific LinuxScientific Linux 7chkconfig-1.7.2-1.el7_3.1.x86_64.rpm232344cda1cac53b128b035b711c5be1a9c624cf7c3720f6e6a586944b8da85antsysv-1.7.2-1.el7_3.1.x86_64.rpme09bde7cffbb97e2add6683aa7aa4908a9626a99db3a70580fd1c12476780c5fSLBA-2017:1605-1This update fixes the following bugs: * In environments with a trust relationship between Identity Management (IdM) and Active Directory (AD), AD users with an alternative user principal name (UPN) configured were unable to log in. With this update, AD users with an alternative UPN can log in as expected. * In environments with a trust relationship between Identity Management (IdM) and Active Directory (AD), when listing groups to which a user from the AD domain belongs, IdM incorrectly displayed all group names qualified with the domain name. This problem occurred when the administrator requested the list of groups through the org.freedesktop.sssd.infopipe.GetUserGroups D-Bus interface. With this update, the interface qualifies only group names from the trusted AD domain. * On SSSD clients joined to an Active Directory (AD) domain whose configuration includes the ad_access_filter option in the /etc/sssd/sssd.conf file, authentication sometimes failed with with an error such as this: 10 (User not known to the underlying authentication module) The problem occurred in environments that use nested groups. This update fixes this bug. * In environments with a trust relationship between Identity Management (IdM) and Active Directory (AD), SSSD sometimes failed to map an AD user group with the corresponding IdM POSIX group. Consequently, IdM denied access to members of the AD group due to host-based access control (HBAC) rules. This update modifies SSSD to return correct group information in this situation, which fixes this bug.Scientific LinuxScientific Linux 7libsss_nss_idmap-1.14.0-43.el7_3.18.i686.rpma4932db3e84025888c4aa7d3a832bd10e2ab39d19c397f72e2b4a2fad05bcf01sssd-polkit-rules-1.14.0-43.el7_3.18.x86_64.rpme9cba796c9a34914f60f697c8fb0aebd1083085d8ba06ae5694e5ec0b2a3c6dblibsss_sudo-1.14.0-43.el7_3.18.x86_64.rpm3c7854f15a50cded2a72b41e60fa10b50c31a4ec4a103b3a812b4a56e40f3b2fpython-sss-murmur-1.14.0-43.el7_3.18.x86_64.rpmf3959f227da93ab65c637cf8501eac8ebeff318cd7814feb4bad32ec2dea9e2alibipa_hbac-devel-1.14.0-43.el7_3.18.i686.rpma516fd6f9003c78070027a7b18ddbe628a717f46bbc6ab688cfd24dc2d3a48c9sssd-tools-1.14.0-43.el7_3.18.x86_64.rpm75ef16650ae6938c0f6ba04a491da358a2a92aece829094ddd09739fae9cd6b0sssd-1.14.0-43.el7_3.18.x86_64.rpm77c61c154004f451fc6feb694397a5aac1426610320ce10ead5cdf880a4b195blibsss_idmap-1.14.0-43.el7_3.18.x86_64.rpm0a9aac9e3688396bd4bde51c77136ae7996fb266413bc0c09f938ab0c4df8e83libsss_idmap-devel-1.14.0-43.el7_3.18.i686.rpm83339b2c7225ae5cea1afe22048bf6d0d5d4903ee99524ad5a80e110d8d8022esssd-common-1.14.0-43.el7_3.18.i686.rpm8de19d040c6420a540f80c78337344e928b9a7413ccf371539f1e71c2133fc1elibipa_hbac-1.14.0-43.el7_3.18.i686.rpm38063dfc2be00dda14d5f6bdb7ce3a903d3131a7dda31969d10be9ff9eae4c41libsss_nss_idmap-devel-1.14.0-43.el7_3.18.x86_64.rpmb3a72a8a4b5f7132d3dab17132f217adea1e6e5785a60e442c7564163b231c93libipa_hbac-1.14.0-43.el7_3.18.x86_64.rpm5d2522b2f251edf92ee6c79f6c7790251419f65222143e46fe5ce7ab4ff2502esssd-libwbclient-devel-1.14.0-43.el7_3.18.x86_64.rpmaa08a4a07b6b9561d3182ea7141fc2e70906ba91bc0ddf258774242e48bd1261sssd-libwbclient-1.14.0-43.el7_3.18.x86_64.rpm37ed1d209b1dd253c44273d91b5d03430f290a4257e7c3e6c6ffb0ce19851b4csssd-krb5-common-1.14.0-43.el7_3.18.i686.rpm389250a3dd4c235b34b9c338f6e64ebd2d3e657b85801861259d8c174f8ca06asssd-krb5-common-1.14.0-43.el7_3.18.x86_64.rpm0cd877993dccdc8bd8ccc5a4e8f236b38e6cf13d53a6baa896848db396c82b20libsss_simpleifp-1.14.0-43.el7_3.18.x86_64.rpmd718fbe5cff7466e3d8bc81e9a236fa9920eea73b57c416551a3c2ab4cb0578elibsss_simpleifp-devel-1.14.0-43.el7_3.18.x86_64.rpm0be444062c78575c501c4b71cc54101431520087c7c9492ed477f67e9f2fe3f6libsss_autofs-1.14.0-43.el7_3.18.x86_64.rpmf3cca33121f4e78a65b3e3be9d73684e39966abcff00b1e70756d98b5cfbfdb8python-libsss_nss_idmap-1.14.0-43.el7_3.18.x86_64.rpmd228308462fd8017c0c69fa22f5c9ac407529ea0d0a7b347c16a24cda4e9be63sssd-ldap-1.14.0-43.el7_3.18.x86_64.rpmb55273c7707ad1571198dfd9f30ce0f8405fb799912b8c7517642a307b3942besssd-dbus-1.14.0-43.el7_3.18.x86_64.rpmdc02d06ba60627b812e1bd2b0a04379246fad1d4d8a98007b75c6622b5fbd84alibsss_simpleifp-1.14.0-43.el7_3.18.i686.rpmc24edd310ab36ea3cc56680f5b352fac9444df3fd99eb142adeb478770fc7083python-sssdconfig-1.14.0-43.el7_3.18.noarch.rpm11ffd7f93301c603db9e9fc571d938c50820663c90f1df40b547f732dec8bdf5sssd-proxy-1.14.0-43.el7_3.18.x86_64.rpme1df50fda4cf22983ed2d6de5caab67455497d05344152acb00a0c25def26bc0libsss_sudo-1.14.0-43.el7_3.18.i686.rpm076b2efc2c9c9827e6aea07ca36f4c3af817e24dae684b3e1fe6d07a0da19dfalibsss_autofs-1.14.0-43.el7_3.18.i686.rpmaa17cc7c71705fa1814a6fe256ef2b5d9f84b03e07990fb3c07e223e055809afsssd-common-pac-1.14.0-43.el7_3.18.x86_64.rpm6b0110bda96001471c4f80b3ed167bb1db1a4ce5abab1a26a4df624fbc21553dsssd-client-1.14.0-43.el7_3.18.i686.rpmf745af6c4c2453884baaea5790c5213921e260fd7b4136f0b42877ce86583093sssd-libwbclient-devel-1.14.0-43.el7_3.18.i686.rpm2a046184503b695ca0274b7d10c6283349860dec24b35b7024369c6b1bc3676asssd-common-1.14.0-43.el7_3.18.x86_64.rpm8cbe8084d7af162163395fc4a503906581ad00bff6a731e31d3207f5ff9859dcsssd-libwbclient-1.14.0-43.el7_3.18.i686.rpmeebcec5bde37612427ad39056b9eda8c6cee0b34a25011c5785e642f1c5b25eflibsss_idmap-1.14.0-43.el7_3.18.i686.rpmf7639d8513de8af8e4410a29112ad0e958bb792e44b837aa36a18457e8d2db05libsss_nss_idmap-1.14.0-43.el7_3.18.x86_64.rpm7c99a5d1e6a7ac70d2ae6c24060a858401b04ae4646cc630e18701ff9b1830ffsssd-ad-1.14.0-43.el7_3.18.x86_64.rpm351ef080aaf9071ec182b8145687ac3f9c4c19a99ea928fb90d583d22c8e2d24sssd-client-1.14.0-43.el7_3.18.x86_64.rpm26fa94ce5242f53b9c2d1e357a98b54ca7202adec2e1818de55d60b91479ead5libsss_idmap-devel-1.14.0-43.el7_3.18.x86_64.rpm3fd4d9022f09cf35133420d32026f0dee26f186529f5798e510683aaa4ea2723sssd-winbind-idmap-1.14.0-43.el7_3.18.x86_64.rpm64e4a2ec25a398bda47ef06861c34d43bac31b910d1b3f444e61d493ee3c0f80libsss_nss_idmap-devel-1.14.0-43.el7_3.18.i686.rpmca61ac2b7b80f394afa25fb3f06a9af64a5455b8699434bdd738d5011d410b39sssd-krb5-1.14.0-43.el7_3.18.x86_64.rpm2967298e455ea9e5f266012d2aabb4d6c4dad664061f9790e2c8efa2ea590c4blibipa_hbac-devel-1.14.0-43.el7_3.18.x86_64.rpm6e31aad8c780db0d84d113e8472fc4058f41d759467bd385aef4738cd07bf79bpython-sss-1.14.0-43.el7_3.18.x86_64.rpmea6236c47da355a7028e1084c019fffd36e06dcffb8a4b12b5361f79f75d56f0python-libipa_hbac-1.14.0-43.el7_3.18.x86_64.rpmee80128e539c83dd6f583a1fe1f3a499227f854727cbac01a375c29f0d0111d1sssd-ipa-1.14.0-43.el7_3.18.x86_64.rpmc47c2a6b68f800c089da88b501c9063585203b8856234018a8d01faef06b5425libsss_simpleifp-devel-1.14.0-43.el7_3.18.i686.rpmc9128e5485fdd6e628f3d84686075ec119b013c2f6fa83148bfd26108d620f97SLBA-2017:1606-1This update fixes the following bug: * Due to a missing memory deallocation call, the cmd_append() function previously leaked memory. This bug has been fixed and the described problem no longer occurs.Scientific LinuxScientific Linux 7cyrus-imapd-devel-2.4.17-8.el7_3.1.x86_64.rpm4d2b73d7a00f13f9bc383db0337c0dce69063e9ece521cdc43ab89f0b7e5f439cyrus-imapd-2.4.17-8.el7_3.1.x86_64.rpm3bbb2ad25f4f2ea64c0a445a736df832feacbd16b619a5f34498e795095e3f0acyrus-imapd-utils-2.4.17-8.el7_3.1.x86_64.rpm4af70cb407aa44ea53b37429e99687d3dfa8a084f2df117cb463b6afc01214adcyrus-imapd-devel-2.4.17-8.el7_3.1.i686.rpm03fc7bb7f723f573fa4c20c80adc717a434d8bc936a6c1df2a5a02886e1aacd8SLBA-2017:1607-1This update fixes the following bug: * Previously, using the xfs_copy command to copy a V5 XFS file system to multiple targets in parallel corrupted all but the first copy with an invalid file system UUID. With this update, unique UUIDs are propagated correctly to each copy, and the copies no longer become corrupted in the described situation.Scientific LinuxScientific Linux 7xfsprogs-4.5.0-10.el7_3.x86_64.rpm129d5bc5889a5204224503491f87e037d4580b3e1848c5735453b649c1ba0375xfsprogs-devel-4.5.0-10.el7_3.i686.rpm19c1ca2df98fd5fad7f36e68b223c18e854439dba1198eb46e45d9dd6a49ae40xfsprogs-4.5.0-10.el7_3.i686.rpmc3848fb7b873b85e79d81a163385da9dc541b91e3c633e9b0476483d7110e4aexfsprogs-devel-4.5.0-10.el7_3.x86_64.rpm156afedd192c740c9aedad36e82860eb091e84752d21ced35ae354542fc15043SLBA-2017:1608-1This update fixes the following bug: * Prior to this update, when canceling an operation on a systemd resource, pacemaker's local resource manager daemon (lrmd) did not correctly recognize when the operation was in progress. Consequently, lrmd could terminate unexpectedly with a segmentation fault. With this update, the operation status is correctly detected, and lrmd no longer crashes in the described situation.Scientific LinuxScientific Linux 7pacemaker-doc-1.1.15-11.el7_3.5.x86_64.rpm4c67a558615792830bef1b2f0b04e12246ae401771e19935c5e1ba5bbf83bd8cpacemaker-libs-devel-1.1.15-11.el7_3.5.i686.rpmac854e0298d4d655f27d60c1266b31f0ee705b6638b5797a84aeb053ce1872b5pacemaker-libs-1.1.15-11.el7_3.5.x86_64.rpm21ce441cd1b8a1db1052d3207e698c808187064f62073d9eb9c3e607861f0a35pacemaker-cli-1.1.15-11.el7_3.5.x86_64.rpm31afd3eb0d9132e1495c7ec757cf93e952addde8e6705fb21abac25c5feb5609pacemaker-cluster-libs-1.1.15-11.el7_3.5.x86_64.rpma6db513cfbb5755f4dc03edfc3c2e777bc0ffdf8b77b89f08d7182bc264e0cbfpacemaker-libs-1.1.15-11.el7_3.5.i686.rpma0f6ee0745b9f1af6fbf59847944c33e53a340f135b8596fb3b1e262c6599d30pacemaker-1.1.15-11.el7_3.5.x86_64.rpmbbca113116309729bfe1065d8a5cd4381f6199ef9009d2108f1f1eff363b2e35pacemaker-libs-devel-1.1.15-11.el7_3.5.x86_64.rpm55fc0e2068428c11e85dd7667be56b2e6ba76627c66241f1b5774f4afd5d1a2bpacemaker-cts-1.1.15-11.el7_3.5.x86_64.rpmed27944ce170249f233926facc97a4383d5743801e85299797915a18dbdd0530pacemaker-nagios-plugins-metadata-1.1.15-11.el7_3.5.x86_64.rpm2b68ec612f60e483e700fa14a0a5df9dae74a3aa5146fbc8532414609e77fad1pacemaker-remote-1.1.15-11.el7_3.5.x86_64.rpmc7e1c24f5ca64838f337759ee4c14b2831720ecd5ffb831b2ec3b2c337353182pacemaker-cluster-libs-1.1.15-11.el7_3.5.i686.rpm21d0f209d1afd34507bfe5e507a4e1806bcb07a65b4294398cc33729cc6d7b4bSLBA-2017:1609-1This update fixes the following bug: * Previously, if the Glance command-line client version 1.0.0 or greater was installed on the virt-v2v conversion server, using the virt-v2v utility to convert a guest virtual machine to a Glance image failed. With this release, when exporting images, virt-v2v directly sets all the properties of images. As a result, the conversion to Glance works regardless of the version of Glance client installed on the virt-v2v conversion server.Scientific LinuxScientific Linux 7libguestfs-tools-1.32.7-3.el7_3.3.noarch.rpm0a5a03e36d1bffbd3bce81f4b918773d705c1ffd0a28b0301daf81a7de1f27capython-libguestfs-1.32.7-3.el7_3.3.x86_64.rpmfc23e5270486ca7256c872b05a8dc005cf7566ef8b08e5936e58af01b00d3bcalibguestfs-devel-1.32.7-3.el7_3.3.x86_64.rpm792fdb1b5c0864f258be486bdc915710113c3b4d337f1c1e3bc1a2ff407b5936libguestfs-javadoc-1.32.7-3.el7_3.3.noarch.rpm18e4c659e49baea71eb4e6af307527d75666368b515f970aa79544cd32d1bd64ocaml-libguestfs-1.32.7-3.el7_3.3.x86_64.rpma9cb544792b28814c71839132c7fe80ea1daa048cf62c4c28d89a5789843a5e6ocaml-libguestfs-devel-1.32.7-3.el7_3.3.x86_64.rpm342f01ab173b95778b17fc6d4816556b971f72493ad39845054e5d977d43dc81libguestfs-xfs-1.32.7-3.el7_3.3.x86_64.rpm98e65c0bb7fe24b196fb308c6ada529f62c03b2213562594f9a37095a45f22d8libguestfs-java-1.32.7-3.el7_3.3.x86_64.rpmbe36c7ce1872c7029d1a3fd453a0efabc40f2942f3c67ff57568799186d9ebdclibguestfs-rescue-1.32.7-3.el7_3.3.x86_64.rpm6b524664df4192b78160378f16145e06ece46b40c31ffd1159b561bb2d785735perl-Sys-Guestfs-1.32.7-3.el7_3.3.x86_64.rpmd0b29830756b5d8cd8e84ff38d555948e022ecbda8bd6eda2eca3cc02c38e4cclibguestfs-bash-completion-1.32.7-3.el7_3.3.noarch.rpm0707b74c62c266dac0296b9658de529299c3df63c075d56edc993b6ed4335fafvirt-dib-1.32.7-3.el7_3.3.x86_64.rpm586a0999bc9dfe69606b0ce3424609e5713ea27bfbde0ec49111b76ec10e4650libguestfs-gobject-1.32.7-3.el7_3.3.x86_64.rpmdb8f45e25d2339778d8edc7f2b9344982372ec94da618e2ffeb8902ec7d95a9elibguestfs-gfs2-1.32.7-3.el7_3.3.x86_64.rpm9366a27f7aad444f47641407d19616780d4c552fd463357a9954a5ec94e537eelibguestfs-java-devel-1.32.7-3.el7_3.3.x86_64.rpm728f7dd883669c42e3533ba60c06f5d2e1f393585631d6f4501a055d5659f5a9libguestfs-tools-c-1.32.7-3.el7_3.3.x86_64.rpm223a2314c6a5185f349e5420a25d4ab042cba8168ddb17d077b40e056460831dlibguestfs-gobject-doc-1.32.7-3.el7_3.3.noarch.rpm218de65d34433b6dd3c6cd9f101c19d3fb06b22b0955f57702ca36de58b22cafvirt-v2v-1.32.7-3.el7_3.3.x86_64.rpm657aa30dd2a486dcc2a0aae1e90a5ec283fd20dd78e56994d1c0217463f27a73libguestfs-man-pages-ja-1.32.7-3.el7_3.3.noarch.rpmf526cf632a415ac9102c53791492f62aac3f0b4fbfbfd3efae5170f279be0718lua-guestfs-1.32.7-3.el7_3.3.x86_64.rpm63e5f12ebd9f3b6750e31beffeb228b3ef3aa8eb536e7bdb66500c3a7954f500libguestfs-man-pages-uk-1.32.7-3.el7_3.3.noarch.rpm2414f6b2972d7cd734f39f1192ae337f42ac7ba4c4ce1e1d294d64520a059f24libguestfs-gobject-devel-1.32.7-3.el7_3.3.x86_64.rpm06575851fe345eb1a1a6903dde48a2254b5775dc2d00639622611f7ee2fdbf55libguestfs-inspect-icons-1.32.7-3.el7_3.3.noarch.rpm68fc364ad9d5038c40c33e11d427294e34b2a7b17c6f33b2ab8a949abdeb0a71libguestfs-rsync-1.32.7-3.el7_3.3.x86_64.rpmce4b513dc1487ed24324ca3b670f30903286d1bc6ed291fe91d3dba921fbea2aruby-libguestfs-1.32.7-3.el7_3.3.x86_64.rpm86fba6b09918b9d86c423b77ca532484b26e6daeb03e03617237e48fba3ce7f6libguestfs-1.32.7-3.el7_3.3.x86_64.rpm1f5d093379aff66988e121e30bf4149ef795929654a37b42002cd47c5d912e72SLBA-2017:1610-1This update fixes the following bug: * Previously, the startTime parameter in CA certificate profiles was being parsed as an "int" type, which meant it was limited and could overflow if the startTime was set too far in the future. With this update, the parameter is now being parsed as a "long" type, which has significantly higher maximum value, and the problem no longer occurs.Scientific LinuxScientific Linux 7pki-javadoc-10.3.3-19.el7_3.noarch.rpmff162a0bd739f5d4904163529cc902664b5b91a198c40acb1526791873d6726epki-base-java-10.3.3-19.el7_3.noarch.rpm514db9cfdfc0998dc02e98be802cd85bc70b308c6a8d84ab62a116484ec226f5pki-ca-10.3.3-19.el7_3.noarch.rpmd1cf8428b74bb55e70a4ee77a4759e3b6b764207e40e430a99a92fa2e989a570pki-server-10.3.3-19.el7_3.noarch.rpm33907c9c89d78fb0964b7a65467c540b34c3b2c2da81026301435364c62c48e0pki-kra-10.3.3-19.el7_3.noarch.rpm4750d24278e989f853a466b7dce4bd7e9a7a5e5e83cdc41bfc9decd900e4c15fpki-tools-10.3.3-19.el7_3.x86_64.rpmb33121f4a9a4f8c0be5eda904d46c286336d5a77841d0dcf01d8fe9b27789124pki-symkey-10.3.3-19.el7_3.x86_64.rpm79c692cbf5f2bed9c4a3cf5f532c968adf5dc75b5a062f81800041cea61c53a3pki-base-10.3.3-19.el7_3.noarch.rpm262b19f75a9782ee63c92d5f5b4e9d2c76820b9d73efb2d200df9ee234c9403dSLBA-2017:1611-1This update fixes the following bug: * Previously, the dmidecode Python module did not check for presence of entries in the Desktop Management Interface (DMI) table and was unable to handle malformed data when querying the DMI table. As a consequence, when querying a non-existent or invalid DMI table entry, the dmidecode module terminated unexpectedly with a segmentation fault. This update adds a check for the presence and format of the DMI table entries. As a result, the dmidecode module no longer terminates with a segmentation fault when querying malformed DMI tables, and correctly returns empty data in the described situation.Scientific LinuxScientific Linux 7python-dmidecode-3.10.13-12.el7_3.x86_64.rpmf34f36833722e9488dee5cabdf9df602484e813f5b6c8253fb2800f72a2c8590SLBA-2017:1612-1This update fixes the following bugs: * Due to a bug in the previous version of the ghostscript packages, the Evince document viewer failed to display the content of PostScript files. A patch has been applied to address the problem, and Evince now displays PostScript files properly. * Under certain circumstances, the ghostscript application previously entered an infinite loop, became unresponsive, and caused excessive CPU load. This update fixes the underlying code, which prevents the described problem from occurring.Scientific LinuxScientific Linux 7ghostscript-cups-9.07-20.el7_3.7.x86_64.rpm0ca93d5017221c901924f299035a1a1531f83f96ecc51dac6b151688fe300a34ghostscript-9.07-20.el7_3.7.x86_64.rpm3530b385f5ce07f14ebd6127ad9272f5e45d1d76cbc25047225efa401ea4cf8cghostscript-gtk-9.07-20.el7_3.7.x86_64.rpm90c2bd9dcdeb92a4e01e4db0b97a986ab59671a054a64b7693bbfee4f269f393ghostscript-devel-9.07-20.el7_3.7.i686.rpm3f3f838e9a3a9c83c967a3bb12946afcaa7abf2b777cf2d9ea399f95f8935ba9ghostscript-9.07-20.el7_3.7.i686.rpm2a8868f46601fc0fec0c1b9e901a6f2a732cf5362b0f18e19b6460b454b74478ghostscript-doc-9.07-20.el7_3.7.noarch.rpmecad597c54e250794ca7b07c220362a2a8eff510792baa70eab44c0e22e41a20ghostscript-devel-9.07-20.el7_3.7.x86_64.rpm3734600f9204bc0787435dad2606fe857fd25507cc9d727a67a1b15c75f6ca1fSLBA-2017:1613-1This update fixes the following bug: * Previously, when the team interface was configured and kdump was configured to dump the vmcore over a network, ifup was called recursively. Consequently, kdump generates an Out of Memory (OOM) state and the vmcore is not dumped. With this update, kdump dumps the vmcore over the network even when the team interface is configured.Scientific LinuxScientific Linux 7dracut-network-033-463.el7_3.2.x86_64.rpmce22ea1b824ac87f716a119691b4e97517ab2a0a2ffd6b68c4a3eb37062791fddracut-caps-033-463.el7_3.2.x86_64.rpmaff4105ac2a104c27f0306fd71be0414e2cf1c291bb61bd942bbecc0c3807611dracut-config-generic-033-463.el7_3.2.x86_64.rpm963ef76102567b7fd4db490bd5d209b52c9d957dd73d407d9d72ee42f20be1a5dracut-fips-aesni-033-463.el7_3.2.x86_64.rpm302630f48f91b2d943c64397d1b212e652e3ccca228ef9ab8209637efb8370d4dracut-config-rescue-033-463.el7_3.2.x86_64.rpm3e10465db14f0f5ffbcd558f764c22a797a739c48d760b8104d7ac7fb9004720dracut-033-463.el7_3.2.x86_64.rpma8e766fd46b3ad58013638be381440a8e8b023dbd7f3f54c30709bcd61d02d14dracut-fips-033-463.el7_3.2.x86_64.rpm2e79989b6b1cc7cb0d037cbacdf5bd090c125f953a9738bd589eba03cee8f510dracut-tools-033-463.el7_3.2.x86_64.rpmd2c47bea734bf5d935e319d8e883a28ef2fb98a6f9cf062a4596a7b4c1529ec3SLBA-2017:1614-1This update fixes the following bug: * You can use the "no_proxy" environment variable to specify hosts to be excluded in the virt-who configuration from using the proxy server for a specific host or hosts. Due to a bug, the python-rhsm library previously did not process "no_proxy" environment variables correctly when they were used in certain virt-who configurations. With this update, python-rhsm complies with "no_proxy" in all configurations.Scientific LinuxScientific Linux 7python-rhsm-1.17.10-1.el7_3.x86_64.rpmcceeaff67e539e361c51d5e86ab371276750f2b9b51b94906a93754457d999e9python-rhsm-certificates-1.17.10-1.el7_3.x86_64.rpm0891ad52f49a0c3220699d962f3c62c962e04b7435778b0240c8ee190e6bdeb7SLBA-2017:1617-1This update fixes the following bug: * Previously, a code which added limits to the RAID types used DEFAULT_MIRROR_MAX_IMAGES as a catch-all value without checking if the volume is a mirror. As a consequence, a user could not create logical volumes (LVs) with more than 8 stripes. To the correct condition check now takes place, and volumes with up to 128 stripes can be created.Scientific LinuxScientific Linux 7lvm2-sysvinit-2.02.166-1.el7_3.5.x86_64.rpm653074a6ae905f275570ecb9966824274ac84b9ff0f71b9a5f8dc355c3b9fd31lvm2-libs-2.02.166-1.el7_3.5.x86_64.rpm927ceaa6f4370d63e30520061c675b1601b25b3cb2aeb0d043d63b0a9e49c6aflvm2-2.02.166-1.el7_3.5.x86_64.rpme8bcc98892bf1d1dc49e87d4215667c45153667b3a47331c0b0110a19a5b248adevice-mapper-event-1.02.135-1.el7_3.5.x86_64.rpm3ca3ce145f3859d21a9969469d96282c8d2324622ae7fc52536dfef0568bee43device-mapper-event-libs-1.02.135-1.el7_3.5.i686.rpm04faf4ad4aac7e386cfa76d7f14fbc90848de2afa48dfe5407b6096e486c1f78device-mapper-devel-1.02.135-1.el7_3.5.i686.rpm4928645b0c7f3e663032660e46ceebcae73e96d22ae9c13971a4dc1f34f39a47device-mapper-1.02.135-1.el7_3.5.x86_64.rpm6ff962010abb2e23be02452a6eae5fbc66fda1a21566a9fd7b375e41bbeae69cdevice-mapper-devel-1.02.135-1.el7_3.5.x86_64.rpm0742b752a6a1b6d0e4e4b4af545874372bba23737d8d6c55dd0fb17a44ae1bd6device-mapper-libs-1.02.135-1.el7_3.5.i686.rpmc85131bd59d9fc4231b123bce0a2a551bfccf0ff0e9e97ef41dc3431fb4ffc23device-mapper-event-libs-1.02.135-1.el7_3.5.x86_64.rpmca017be66921e2a7d2c4e84dc1e96d7d85b6435eab6f652a73016c1564dcb4cadevice-mapper-libs-1.02.135-1.el7_3.5.x86_64.rpm1dfbbe50fb6e6c8a6ed34be572c2ecab3fb063823fbfd4eb1bccf1a9965cc3fbcmirror-2.02.166-1.el7_3.5.x86_64.rpm912f1858a7a34e00ed36559092c09530ad99469a454cb1a4b948459446bd50f0lvm2-cluster-standalone-2.02.166-1.el7_3.5.x86_64.rpm8932ccd48b33502013d525f4bcd5631a3d504bb201f42198df490d8451eb246fdevice-mapper-event-devel-1.02.135-1.el7_3.5.i686.rpmc856505e5f6ccf7b17493ae49b496b4ed48f2453e897a4bd6be566a60bab141alvm2-devel-2.02.166-1.el7_3.5.x86_64.rpm1d758b22ad10ddc4f8da89427de3513014cc01bf2d84d5be005b03494bcfd13dlvm2-cluster-2.02.166-1.el7_3.5.x86_64.rpmb324e7cc4d72b8e1980eaa1bc4e35419a34446d88b8106a47b786feb6b3cc82bdevice-mapper-event-devel-1.02.135-1.el7_3.5.x86_64.rpm482b481d9d7daa0cae2c3b73307382e0222c7f60d1d118ce30eeafbafa65e245lvm2-python-libs-2.02.166-1.el7_3.5.x86_64.rpm7afdc8085812ffdf88253ad14d7d3fd1bd2f38d0dafe2447a2941dfa58e20ecelvm2-lockd-2.02.166-1.el7_3.5.x86_64.rpm112825122ae60453877341f8fb0bc7d8a0be2793e491c1a61e28c3570f113eeelvm2-libs-2.02.166-1.el7_3.5.i686.rpm180a517ba8f10c9b073c56bd8c2a02a461e7d641e6e1196b6cff5d57b5abcbd8lvm2-devel-2.02.166-1.el7_3.5.i686.rpm1dedbd70377d87802d8e545107328b5e7637f454514dbdbe91c58c31295a9335cmirror-standalone-2.02.166-1.el7_3.5.x86_64.rpm74a0fcb41ea8595dbcf9272b9d34197edb269ee03c748a1d4bccb6a223cdf596SLBA-2017:1618-1This update fixes the following bug: * Prior to this update, a bug in the gawk utility could sometimes cause it to perform an out of bounds write, which resulted in it being killed by a SIGABRT signal. This bug has been fixed, and gawk is no longer being terminated unexpectedly.Scientific LinuxScientific Linux 7gawk-4.0.2-4.el7_3.1.x86_64.rpm09d50058edfe3858bcf89c9d5aab805c3c77b5cae04e33278304c59253a4e84bSLBA-2017:1674-1* Prior to this update, a bug in the kernel prevented executables from starting if the maximum process stack size (rlimit_stack) was set to a value below approximately 4 MB. This update fixes the search for unmapped address ranges (suitable gap) in unmapped_area() and unmapped_area_topdown() by ensuring that the gap_end is always larger than gap_start. As a result, executables can be started with a limited process stack size as expected. The system must be rebooted for this update to take effect.Scientific LinuxtrueScientific Linux 7perf-3.10.0-514.26.2.el7.x86_64.rpm16992d8ea7197b9ec8b029942e56985ccab5f5340149c7f1be8e036947c8f138kernel-debug-3.10.0-514.26.2.el7.x86_64.rpm9c6b31816390ac3e209edaed714d218951091f4722b932d434f06ee45dd9f0c4python-perf-3.10.0-514.26.2.el7.x86_64.rpmfa1f8896ba79d612fb095ba82ec0422e0ca7aab52a789390383d18d593ff684dkernel-devel-3.10.0-514.26.2.el7.x86_64.rpm644db2c6d58ac993f5508f1b6e47efbc1273bbc7e554af4a325043e6c25bd71bkernel-abi-whitelists-3.10.0-514.26.2.el7.noarch.rpm3ffa202a319c449532b67ceac8364137e8659659128fd2db1328f29a2457bd59kernel-tools-libs-devel-3.10.0-514.26.2.el7.x86_64.rpm330e735f550093f70d46da8733f7b421af5cbdd3f92e93671006173b792b03edkernel-3.10.0-514.26.2.el7.x86_64.rpmde4b4e652d4c7d68d5573fd14e9354560739f897e86cbab6a37e9f0d777c700fkernel-tools-3.10.0-514.26.2.el7.x86_64.rpm12e39a9c49cd6f2c35de74defdfc44c9a2f0650d43fe8e5fad264f7bd10dbe8ekernel-debug-devel-3.10.0-514.26.2.el7.x86_64.rpm72e7dbc82f3a63f8feef0dde743281607fec22bc6109ba684f588390f750a8e7kernel-tools-libs-3.10.0-514.26.2.el7.x86_64.rpmeb3f6a061e21a6960a608aaab3d1f3602a53456847d4cd63c2460aa94cad634ckernel-headers-3.10.0-514.26.2.el7.x86_64.rpm6268d513990cf3fca7aa6acd17739c3e051c04be04463d9b0704231bd6858b58kernel-doc-3.10.0-514.26.2.el7.noarch.rpm8c28c2730bfa9d57fef7269b98e627a8b981118b9ab1c489203bcb556a93ebb6SLBA-2017:1752-1This update fixes the following bug: * Previously, the optimized implementation of the truncl(), ceill(), nearbyintl(), and roundl() functions available in the glibc library could return incorrect results on the IBM Power Systems architecture. As a consequence, any code using these functions performed incorrect calculations for certain inputs. The optimized implementation has been replaced by a generic implementation. As a result, these functions now return the expected results for the affected input values.Scientific LinuxtrueScientific Linux 7glibc-2.17-157.el7_3.5.x86_64.rpmfbeebe1d71fccda434dc601bb33a9a85362dc86020ac9e31cd004683751f9b9aglibc-devel-2.17-157.el7_3.5.i686.rpmb178bc6b1866ef771daba8a5936b10152bef7bb1856ba62a4b2d0cbee36dfde2nscd-2.17-157.el7_3.5.x86_64.rpmdb323656654072dc1c6c0bbd4db2c289f273cfa320a2a000ebcf19e7417177a5glibc-utils-2.17-157.el7_3.5.x86_64.rpmc1c38e1a31da36cbfe0da41810ff024f25a20f466093a16458732aefde4a4f01glibc-headers-2.17-157.el7_3.5.x86_64.rpmf9841bf0dbb9f8c36f7bc577b9f1b287cf98d91cea30349b49f90519bdf7e40dglibc-static-2.17-157.el7_3.5.i686.rpm6d2ceaf65025e8fae4c7949a563e04bb51b16152db3f558f968b1a6eb6470e20glibc-devel-2.17-157.el7_3.5.x86_64.rpma2a3a5d3633fa58b2669be978e96d1d8d2004cac4375df17ac8d06514bcf00eaglibc-static-2.17-157.el7_3.5.x86_64.rpm65578232e2d41612d768a8a4430e7cb12b65ba3a16dae1581a82c09e3d6db52dglibc-common-2.17-157.el7_3.5.x86_64.rpme72f9c1cfff3b076c11791dabdacb1368df04f54108e20b29899e547cd5e6f27glibc-2.17-157.el7_3.5.i686.rpmfdc560bcb7f16f0ffabce97e323b37ea9d20bba542d056103f64d04dd0c2a454SLEA-2017:0458-1The kmod-redhat-mpt3sas package contains the LSI MPT Fusion SAS 3.5 Device Driver kernel module, which adds official support for the new mpt3sas devices, specifically: ThinkSystem 430-16i SAS/SATA 12Gb HBA ThinkSystem 430-16e SAS/SATA 12Gb HBA ThinkSystem 430-8i SAS/SATA 12Gb HBA ThinkSystem 430-8e SAS/SATA 12Gb HBA New PCI IDs supported by this package are: 1000:00AA SAS3508 Fusion-MPT Tri-Mode RAID On Chip (ROC) 1000:00AB SAS3508 Fusion-MPT Tri-Mode RAID On Chip (ROC) 1000:00AC SAS3408 Fusion-MPT Tri-Mode I/O Controller Chip (IOC) 1000:00AD SAS3516 Fusion-MPT Tri-Mode RAID On Chip (ROC) 1000:00AE SAS3516 Fusion-MPT Tri-Mode RAID On Chip (ROC) 1000:00AF SAS3416 Fusion-MPT Tri-Mode I/O Controller Chip (IOC) The kernel modules delivered by this erratum have been made available as part of the Red Hat Driver Update Program, which provides updated kernel modules that add support for selected devices in advance of the next Scientific Linux minor update release. We strongly recommend that these kernel modules be only used when it is necessary to enable the specific hardware mentioned in this erratum. Partners and customers should continue to use the driver that is shipped in the latest Red Hat Enterprise Linux kernel for all other devices that require this driver. All users who require kmod-redhat-mpt3sas are advised to install this new package.Scientific LinuxScientific Linux 7kmod-redhat-mpt3sas-14.101.00.00-1.el7_3.x86_64.rpm175072b2580f6cb1f2e112436a69f73a5ccc422d1e1cd8ff161342141be8f34fSLEA-2017:0518-1The kmod-redhat-megaraid_sas package contains the Avago MegaRAID SAS Driver kernel module, which adds official support for the new SAS3.5 MegaRAID devices, specifically: Dell PERC H740P Dell PERC H745P MX Dell PERC H840 Lenovo ThinkSystem RAID 530-4i Flex Adapter Lenovo ThinkSystem RAID 530-8i Dense Adapter Lenovo ThinkSystem RAID 530-8i PCIe 12Gb Adapter Lenovo ThinkSystem RAID 930-4i 2GB Flash Flex Adapter Lenovo ThinkSystem RAID 930-8e 4GB Flash PCIe 12Gb Adapter Lenovo ThinkSystem RAID 930-8i 2GB Flash PCIe 12Gb Adapter Lenovo ThinkSystem RAID 930-16i 4GB Flash PCIe 12Gb Adapter Lenovo ThinkSystem RAID 930-24i 4GB Flash PCIe 12Gb Adapter New PCI IDs supported by this package are: 1000:0014 MegaRAID Tri-Mode SAS3516 1000:0016 MegaRAID Tri-Mode SAS3508 1000:0017 MegaRAID Tri- Mode SAS3408 1000:001B MegaRAID Tri-Mode SAS3504 1000:001C MegaRAID Tri-Mode SAS3404 The kernel module delivered by this erratum has been made available as part of the Red Hat Driver Update Program, which provides updated kernel modules that add support for selected devices in advance of the next Scientific Linux minor update release. We strongly recommend that this kernel module be only used when it is necessary to enable the specific hardware mentioned in this erratum. Partners and customers should continue to use the driver that is shipped in the latest Scientific Linux kernel for all other devices that require this driver. All users who require kmod-redhat-megaraid_sas are advised to install this new package.Scientific LinuxScientific Linux 7kmod-redhat-megaraid_sas-07.700.00.00-rh1.el7_3.x86_64.rpmdd3976ca362f494f68ddbe5d5d32fb7de701a1698beeef6e8a0fba0211a68ea9SLEA-2017:0922-1This update adds the following enhancement: * Some TLS libraries now warn or refuse to validate DNS names when the DNS name only appears in the Subject Common Name (CN) field, which is a practice that was deprecated by RFC 2818. This update adds the "CommonNameToSANDefault", which copies the Subject Common Name to the Subject Alternative Name (SAN) extension, and ensures that certificates are compliant with current standards.Scientific LinuxScientific Linux 7pki-symkey-10.3.3-18.el7_3.x86_64.rpm9d65a688573bcec21bba9371fb86afa338ed4b083a6f1f7ca92382262bdd4059pki-javadoc-10.3.3-18.el7_3.noarch.rpm92e83d7304741ccfc3a7bc4b225482c39ff768a2b301dfa1321931e0d9aac3f9pki-tools-10.3.3-18.el7_3.x86_64.rpm4e18e2e02b3d3934bf6755038bdb59923cefceb66e3051199cc72ec625e9d048pki-base-java-10.3.3-18.el7_3.noarch.rpm0d87071198228c98aef030b1d675e74f9dce47e22f100a6472565a21b2606f31pki-ca-10.3.3-18.el7_3.noarch.rpmefa316915b40c814f499e0ffbce7308df27792af0554c3b74f749cdfd35bb70cpki-kra-10.3.3-18.el7_3.noarch.rpm32dc216a571d9ff3ef47f8de5498f2c9c7b1dda1988798758a6c65b15d4fced3pki-base-10.3.3-18.el7_3.noarch.rpm7af3ecf026da94d0df9b45e36f863e6c1c15143fa471d9b788fadb4dfca91beapki-server-10.3.3-18.el7_3.noarch.rpm2b3fe72bf77498a396e82075bd7f1b2b6189e08bf54192a6a0a1cbb54e4e9092SLEA-2017:1194-1The kmod-redhat-ixgbe package contains the Intel® 10 Gigabit PCI Express Network Device Driver kernel module, which adds official support for the new ixgbe devices, specifically: Intel Ethernet Connection X553/X557AT 10GBASE-T Intel Ethernet Connection X553 1GbE The new PCI IDs supported by this package are: 8086:15c8 Intel X550EM A 10GBASE-T 8086:15e4 Intel X550EM A 1GBASE-T 8086:15e5 Intel X550EM A 1GBASE-T The kmod-redhat-ixgbevf package contains the Intel® 10 Gigabit PCI Express Virtual Function Network Device Driver kernel module, which adds official support for the new ixgbevf devices, specifically: Intel Ethernet Connection X553 Virtual Function The new PCI IDs supported by this package are: 8086:15c5 Intel X550EM A VF The kernel modules delivered by this erratum have been made available as part of the Red Hat Driver Update Program, which provides updated kernel modules that add support for selected devices in advance of the next Scientific Linux minor update release. We strongly recommend that these kernel modules be only used when it is necessary to enable the specific hardware mentioned in this erratum. Partners and customers should continue to use the driver that is shipped in the latest Scientific Linux kernel for all other devices that require this driver. All users who require kmod-redhat-ixgbe and/or kmod-redhat-ixgbevf are advised to install these new packages.Scientific LinuxScientific Linux 7kmod-redhat-ixgbe-4.4.0_k_rh7.4_z-2.el7_3.x86_64.rpmdeed36de015510fd8ad0eb3323676c1e65512f0d17a5ebf451587b6b633da57fkmod-redhat-ixgbevf-3.2.2_k_rh7.4_z-1.el7_3.x86_64.rpm64f833fc01457816a7a988a2ab66af73c79d306efc49ce3252dee9d403cd27e3SLEA-2017:1300-1This update adds the following enhancement: * With this update, device-mapper-multipath provides a new "max_sectors_kb" parameter in the defaults, devices, and multipaths sections of the multipath.conf file. This parameter allows you to set the "max_sectors_kb" device queue parameter to the specified value on all underlying paths of a multipath device before the multipath device is first activated. When a multipath device is created, the device inherits the "max_sectors_kb" value from the path devices. Manually raising this value for the multipath device or lowering this value for the path devices can cause multipath to create I/O operations larger than the path devices allow. Using the "max_sectors_kb" multipath.conf parameter is an easy way to set these values before a multipath device is created on top of the path devices, and prevent invalid-sized I/O operations from being passed down.Scientific LinuxScientific Linux 7device-mapper-multipath-0.4.9-99.el7_3.3.x86_64.rpm399cdb79504b7bb699bf69f9f7406bb934d2327226be762266e615b47b5f5752device-mapper-multipath-sysvinit-0.4.9-99.el7_3.3.x86_64.rpm3f4b14ab8f5fbff5428332a183b9f16e6809ae04ac947404f51eeb5b63b17e97device-mapper-multipath-libs-0.4.9-99.el7_3.3.i686.rpm43471064e2375442f2f294958962e2c5b19ab9c1f254bd0017a74a4434bd2e95kpartx-0.4.9-99.el7_3.3.x86_64.rpm1ce385945af81726949221ae9c06c01cdb109abe47118e7229a02e1544488fe1device-mapper-multipath-libs-0.4.9-99.el7_3.3.x86_64.rpm2ba9b339892e8d125da608b8a11f87ba62ee9f26da10ba4bd27f3d26da953c14SLEA-2017:1307-1This update adds the following enhancement: * The priority of the "ktimersoftd" and "ksoftirqd" kernel threads has been increased, which improves Real Time kernel performance when using the tuned service.Scientific LinuxScientific Linux 7tuned-profiles-realtime-2.7.1-3.el7_3.2.noarch.rpm8aa5cdf86d43f8d60f8211e1817ef6b04993b7f3c3b3be36ffb09176cdfb91a5tuned-gtk-2.7.1-3.el7_3.2.noarch.rpmbdbb7d414ba343c552bc6ca697cb2475160d52e840fe3e627787f39386ee7422tuned-utils-2.7.1-3.el7_3.2.noarch.rpm3fd7e3fecc545259156d62889e22c91446808360f8cc10d14ddfd96c17338785tuned-2.7.1-3.el7_3.2.noarch.rpm6e9a4a64548128bd11db6423bb57cfac98664c19fee86c994b53ed1549d8e882tuned-profiles-atomic-2.7.1-3.el7_3.2.noarch.rpm04953ae9f18399888838d0860adae0c91e9d22f8d21289912da88f363a0e6566tuned-utils-systemtap-2.7.1-3.el7_3.2.noarch.rpm8ff1bc2aa2906c7b906fd4e50847c50fe9b7067f04d6cbf2d326010d79241118tuned-profiles-compat-2.7.1-3.el7_3.2.noarch.rpma36a76861f9adc06eeef387db4925d2c82aa7c93f155a6c44ada38cacfd1cbeatuned-profiles-oracle-2.7.1-3.el7_3.2.noarch.rpmd19badc65baf3d1987a0808036417645e2af5c2962780edd49494680510f8b00SLEA-2017:1310-1This update adds the following enhancement: * With this update, the firewalld service supports the Stream Control Transmission Protocol (SCTP) and Datagram Congestion Control Protocol (DCCP) protocols in the port and source-port options. Additionally, firewalld now supports SCTP and DCCP in the port, source-port, forward- port, and rich rules options for zones.Scientific LinuxScientific Linux 7firewall-config-0.4.3.2-8.1.el7_3.3.noarch.rpm1dc6310ae944944cca7e7dff948bb959532822d5ce27bd8f5dbb16c913101840python-firewall-0.4.3.2-8.1.el7_3.3.noarch.rpm3ea8b2ce88d394134349f84988d1bd76357084f1b8f844b9b8238e981134dd22firewalld-filesystem-0.4.3.2-8.1.el7_3.3.noarch.rpmf45a455f1f7b3c765a079bc3e35bfe44b473050de9f6b67cf31bb6ed66f83498firewall-applet-0.4.3.2-8.1.el7_3.3.noarch.rpmcb98755fae217ec75a3b7b52f54815d34c033a1b885743f3334600b58208752ffirewalld-0.4.3.2-8.1.el7_3.3.noarch.rpmf670e467359ea253f2fe65fee68fa4eb7dc6aee70d44a7513d77cf171a396baaSLEA-2017:1388-1The kmod-redhat-i40e package contains the Intel® Ethernet Connection XL710 Network Driver kernel module, which adds official support for the new i40e devices, specifically: Intel Ethernet Controller XXV710 for 25GbE backplane Intel Ethernet Controller XXV710 for 25GbE SFP28 The new PCI IDs supported by this package are: 8086:158a Intel Corporation Ethernet Controller XXV710 for 25GbE backplane 8086:158b Intel Corporation Ethernet Controller XXV710 for 25GbE SFP28 The kmod-redhat-i40evf package contains the Intel® XL710 X710 Virtual Function Network Driver kernel module, which adds official support for virtual function of the aforementioned i40e devices. The kernel modules delivered by this erratum have been made available as part of the Red Hat Driver Update Program, which provides updated kernel modules that add support for selected devices in advance of the next Scientific Linux minor update release. We strongly recommend that these kernel modules be only used when it is necessary to enable the specific hardware mentioned in this erratum. Partners and customers should continue to use the driver that is shipped in the latest Scientific Linux kernel for all other devices that require this driver.Scientific LinuxScientific Linux 7kmod-redhat-i40e-1.6.27_k_dup7.3-1.el7_3.x86_64.rpma62d4de580c13c6edb2b23ed03c142e91359eef703b6cce700fbfb2147dac9b7kmod-redhat-i40evf-1.6.27_k_dup7.3-1.el7_3.x86_64.rpmc0efcda65d7e75ac7f60464cd94deb81b33160e3b23b7d35f4b983e14deb950eSLEA-2017:1437-1The ca-certificates package has been upgraded to upstream version 2.14, which provides one enhancement over the previous version. Notably, the package now contains the following modification: * The Certificate Authority (CA) list has been updated to meet the recommendations as published with the latest Mozilla Firefox Extended Support Release (ESR) as part of the Network Security Services (NSS) version 3.28.5. The updated CA list improves compatibility with the certificates that are used in the Internet Public Key Infrastructure (PKI). For compatibility reasons, several root CA certificates with an RSA key size of 1024 bits have been kept as trusted by default to ensure compatibility with existing PKI deployments and with software based on OpenSSL or GnuTLS. To avoid certificate validation refusals, Red Hat recommends installing the updated CA list on June 12, 2017. The ca-certificates package also includes the "ca-legacy" command, which can be used to disable the mentioned compatibility modifications. See the ca-legacy(8) manual page for more information on how to use the command. Users who intend to disable the legacy modifications are also advised to refer to the following Knowledge Base article, which provides details about these modifications and the potential consequences of disabling them: Note that using the unified CA store is required to be able to use the "ca-legacy" command. See the update-ca-trust(8) manual page to learn how to enable the unified CA store.Scientific LinuxScientific Linux 7ca-certificates-2017.2.14-70.1.el7_3.noarch.rpm9a9f681b5630e7397e37a26b0001428528f82fb5a091896ea001c04e550d0b3aSLEA-2017:1602-1This update adds the following enhancement: * With this update, IPv6 Network Address Translation (NAT) support has been added to conntrack-tools. This allows creating failover between firewalls for IPv6 NAT connections.Scientific LinuxScientific Linux 7conntrack-tools-1.4.4-3.el7_3.x86_64.rpm5ee92e5f5e5f519e65ac2f82d2fe45a5db12a2c270f2d631b78330357795058eSLEA-2017:1730-1The kmod-redhat-mgag200 package contains the Matrox MGA G200 device driver kernel module, which adds the official support for the new MGA G200 devices, specifically: Matrox MGA G200eH3 The new PCI ID supported by this package is: 102b:0538 Matrox MGA G200eH3 The kernel modules delivered by this erratum have been made available as part of the Red Hat Driver Update Program, which provides updated kernel modules that add support for selected devices in advance of the next Scientific Linux minor update release. We strongly recommend that these kernel modules be only used when it is necessary to enable the specific hardware mentioned in this erratum. Partners and customers should continue to use the driver that is shipped in the latest Scientific Linux kernel for all other devices that require this driver. All users who require kmod-redhat-mgag200 are advised to install this new package.Scientific LinuxScientific Linux 7kmod-redhat-mgag200-4.11.0_dup7.3-5.el7_3.x86_64.rpmfc96b16a37626d11c8e7a71ea1c455fa87612d19a7e47b2f3e866d6e1d6a0cd2SLEA-2017:1805-1Scientific LinuxScientific Linux 7kmod-redhat-qed-8.10.10.21_dup7.3-2.el7_3.x86_64.rpm35801e08f8b6c814a9e334d37d74e8502c4554501a1b254d93c3223a11a06089kmod-redhat-qedf-8.10.7.0_dup7.3-1.el7_3.x86_64.rpmc5027e6bc0b015e01dbb6cd03e7d14198022fc1e352190f69d9e947061ffb6fekmod-redhat-qed-firmware-8.15.3.0_dup7_3-2.el7_3.x86_64.rpma99daa52c9057862fc845f3a90edcf186f882286fae1b152611cd195df14011akmod-redhat-qed-devel-8.10.10.21_dup7.3-2.el7_3.x86_64.rpm258660abe4d56694855bb32ec9e1a993fbe734a9ff0b0560eaa78418bee61282kmod-redhat-qede-devel-8.10.10.21_dup7.3-1.el7_3.x86_64.rpmec69c87d96391879780b2391a12c51890e94dfaaaa5780b208a16ebb3b8a40c4kmod-redhat-qede-8.10.10.21_dup7.3-1.el7_3.x86_64.rpm058568ceb13f80d3ea3ea5578ffef671a2834bea5fee24d017690d305f1309b6