SLBA-2015:2543-1This update fixes the following bug: * Previously, a dracut script in the initial RAM file system (initramfs) tried to stop the udev daemon by using the "udevadm control" command. The udev daemon then exited, but the systemd service has a policy to restart the daemon, which could, as a consequence, cause the system not to boot on rare occasions. To this update removes the code that attempted to stop the udev daemon from the dracut script.Scientific LinuxScientific Linux 7dracut-033-360.el7_2.x86_64.rpm269d0f9afaf5af2b285b4cb0dfc3d8f107ad6814b05a4482b2c9c36aee1a127fdracut-config-rescue-033-360.el7_2.x86_64.rpmd4a2edd54676838063c6e50600d19920e516914fc95a3109d2843b7b6c8e8cbfdracut-tools-033-360.el7_2.x86_64.rpm0f5020240b106e278b29b5d2004ce92d9a56fdba7bde90f8cc9445948eea16d7dracut-fips-033-360.el7_2.x86_64.rpm40611cff9094d5267f54c7eb3959a0bf16247ebd3858d4d444cf2c0419f98cf4dracut-network-033-360.el7_2.x86_64.rpmbf88293262cc73a6995ef1ee75753281162f86b96be38b22ba2676ebcc75c90edracut-config-generic-033-360.el7_2.x86_64.rpm9752171bd7fbf1d54623eb87ebc03c8323404e40ed7dc231deb6ad8b10707c2bdracut-caps-033-360.el7_2.x86_64.rpm29075e7707d5a2f53a4b15ac48fcb0f11d4a1547bd322f1e507e3b7d6f614184dracut-fips-aesni-033-360.el7_2.x86_64.rpme403441f58bfa8bcf4a316a4758bf176d5bec7606452752da5de7cb9ff31d66cSLBA-2015:2553-1This update fixes the following bug: * Due to a bug, the crash utility failed to correctly read some firmware memory in sadump vmcore formats. With this update, the crash utility always succeeds in reading memory and obtains correct data in sadump vmcore formats.Scientific LinuxScientific Linux 7crash-devel-7.1.2-3.el7_2.i686.rpmfb84d669773bb9b20f1a183515387a0e000f1abd7cc4b5e5d75c18e0a478e29fcrash-devel-7.1.2-3.el7_2.x86_64.rpm01f6d1bcd779f21001e5cfd607e5ab8311b700c7d0cd7bf828a00a9fdbaef0c8crash-7.1.2-3.el7_2.x86_64.rpm74b688c5ef467958c957780c27a64b885b7325b7919fc42255596cdb5337ef4dSLBA-2015:2563-1This update fixes the following bug: * Previously, Web applications did not correctly handle two-factor authentication, a traditional password and a One-Time Password (OTP), when they used the mod_intercept_form_submit Apache module, and also the Pluggable Authentication Module (PAM) supported pre-auth, for example the pam_sss.so module. As a consequence, the authentication failed. With this update, mod_authnz_pam only provides the concatenated password and the OTP input to the first password PAM response. As a result, authentication no longer fails in the described situation.Scientific LinuxScientific Linux 7mod_authnz_pam-0.9.3-5.el7_2.x86_64.rpm7e05259666f07b000aca1a184bb3ed1b5b6aae2cae755c8f142de9c93bb667e5SLBA-2015:2564-1This update fixes the following bug: * Previously, after using the ipa-winsync-migrate command to migrate users from WinSync to the Identity Management (IdM) trust solution, retrieving an Active Directory (AD) user failed. Also, the SSSD debugging logs contained the following error message: [sysdb_add_user] (0x0400): Error: 17 (File exists) A patch has been applied to address this bug. As a result, AD users are retrieved as expected, and the error no longer occurs in the described situation.Scientific LinuxScientific Linux 7sssd-ipa-1.13.0-40.el7_2.1.x86_64.rpmda639c4f0084ec5813fd48563a20cbf6feaa391d220095b438c8a96cb348d344libsss_nss_idmap-1.13.0-40.el7_2.1.x86_64.rpm20ea2b72cbc7e122c4e4b5a9e551e96eae0249ffe0250d38fd6a1ba3e83af41bsssd-libwbclient-1.13.0-40.el7_2.1.x86_64.rpm7d0ded035d58a4badf9a13415870e8c8f5f256baac35a6c26f3dcfb474d510ffpython-sss-1.13.0-40.el7_2.1.x86_64.rpm2d27a0c4d604e04358c7c97ecdbd34a3827d44af6f4a06f76a7bd85bc498d3b5sssd-krb5-1.13.0-40.el7_2.1.x86_64.rpm9c27faf62db4d8b6c438529dcb744f8babf6880303d2b9aa9bf6704e65ea5bddsssd-1.13.0-40.el7_2.1.x86_64.rpm244be0f967aa7c91a42b8189f2192ee77e57f40284fc9be5ebd083e6325de1e8sssd-libwbclient-devel-1.13.0-40.el7_2.1.i686.rpm68132d9a8efe446f477d555b522e3b1bf096b92258a3191c9998670767c6147dsssd-krb5-common-1.13.0-40.el7_2.1.i686.rpm3e73c7cfb78fb6208f9142cf7008a6651e70b456be24c728dd102728ada5ce4dlibipa_hbac-devel-1.13.0-40.el7_2.1.i686.rpm68c9c78b0ce08d15678f91b2eb5a5bf8f3daae43e61ea3fe3cea58acf74ae9b6python-libipa_hbac-1.13.0-40.el7_2.1.x86_64.rpmfdef81d0d75c07ae557acab7380350e128096626e2d4918c8cfe45e92077798asssd-libwbclient-1.13.0-40.el7_2.1.i686.rpmefff60350f4d4efc5d119cf629c521710ebda77d7c0a9fbba7b7f138888415c1libsss_idmap-1.13.0-40.el7_2.1.i686.rpm849b6b7e93b05cefc786f0fd9d42ea2c2de0d9f146daa8d5f4c3bb8f7e740b7bpython-sssdconfig-1.13.0-40.el7_2.1.noarch.rpmea3c2875ce16b6d2cea3a6ada99f0e653e85a6ed69e0f03010118dba4334ebe4libsss_simpleifp-devel-1.13.0-40.el7_2.1.i686.rpma7985b8f1bf8f36b56238a9be8d29224733522ec65c09364c4262d747e0e8661libsss_nss_idmap-devel-1.13.0-40.el7_2.1.x86_64.rpm9b439fb9464678e896363feda559a4089f8d10096cd600bba4adec42f7088532sssd-tools-1.13.0-40.el7_2.1.x86_64.rpm6993221f571526b1c641bcc18f5f84e836ed10880ecf4e1602b20588279ba969sssd-client-1.13.0-40.el7_2.1.x86_64.rpm8eed193f088ce15083954c3fafb07a90d63dda31f1ae2a8a13d18d55d59ca6f5libsss_idmap-devel-1.13.0-40.el7_2.1.x86_64.rpmb8b17f695d318c9d98e6c6f309f7aed137a2c8697d511be4880c84964f41581alibipa_hbac-devel-1.13.0-40.el7_2.1.x86_64.rpmcdee859a57bc93aec3287f01146a2f55ee2c300085393b0ff68dc9ca876c57basssd-krb5-common-1.13.0-40.el7_2.1.x86_64.rpm75dcedf5f220a05b83f3c51e268da5f1849c16ded59c53478bc128bb0201d4dfpython-sss-murmur-1.13.0-40.el7_2.1.x86_64.rpm7b69622a34e9ac476187bf67ee20dc53bb626b2ebe7a242bf74c7cebf3ad00c9sssd-ad-1.13.0-40.el7_2.1.x86_64.rpmaed7543f3a4951bb39ab5b4d427d6b2e2021f41c9e155f4a332900f331e2603fsssd-proxy-1.13.0-40.el7_2.1.x86_64.rpme616f4243ab3bd28554dd1c77b8f307fa9d4624111fab7650ccd06aff22eb7f1sssd-dbus-1.13.0-40.el7_2.1.x86_64.rpmd1ee8a4b880ab6470fa2d83fc1eb9db0926a93f90a3e21b135904dbcc910f48esssd-client-1.13.0-40.el7_2.1.i686.rpmcc9e56b123f2e0a64d502ae151f7a40f488f1436ef0e06d03ee672e943eac4cdlibsss_nss_idmap-1.13.0-40.el7_2.1.i686.rpma3d5ea7f3adaa2eee1e2d684fd28144e20e2fc2351f52cedad9a9953aabbad28libsss_idmap-devel-1.13.0-40.el7_2.1.i686.rpmc38b76d6d44fc89020446eac9f6122ab55bb664ce9be95d8a1d530489af019aesssd-common-1.13.0-40.el7_2.1.x86_64.rpmb40eb9fc51d460cbfd38d650ccca7db9ebb40293a5fa20c63f705dd7a9240c1csssd-common-pac-1.13.0-40.el7_2.1.x86_64.rpma5f877822fa81bd64e658aba04e3fe6ac2d298f89bad0bf4c84429df7194fe3elibsss_simpleifp-1.13.0-40.el7_2.1.x86_64.rpmca8aa01efbd079891f31ac4fddfc0aab74127f4000101547efae3949789198f0python-libsss_nss_idmap-1.13.0-40.el7_2.1.x86_64.rpmea08b2985e8f0c3cb78ecfaa350a3921df2bd9630cc3bbb91e16c2928ef3b5a8libsss_nss_idmap-devel-1.13.0-40.el7_2.1.i686.rpm648d7e2b4f6b53424a12d484c6f5dff4bc413e5bd5f984af67affbd9663d5907sssd-ldap-1.13.0-40.el7_2.1.x86_64.rpmafdb68ca8eae67f752a4ab577813b63c2ba51fb63e817ba9bdb8359850c6755alibipa_hbac-1.13.0-40.el7_2.1.i686.rpm23492ae39ef27ade66805061b935dd0eabcfa2ae4f63a72b092ec8ff05d279b0libipa_hbac-1.13.0-40.el7_2.1.x86_64.rpmd121a9603c4a037dce47234b7b2215cfaca1cb6c128c33b4a42d8b7581b26663libsss_idmap-1.13.0-40.el7_2.1.x86_64.rpmda01ee664ed09e3f08d242ff68ec6b418a104057a2f03dd1f31e9004891086f1sssd-libwbclient-devel-1.13.0-40.el7_2.1.x86_64.rpm3f6f38347921f67cb42298c3cd40520dd8a3b91101197e14db50b48d769fd2calibsss_simpleifp-devel-1.13.0-40.el7_2.1.x86_64.rpmf7f80d71a8f57ddb308788432ba9462e49ac9929ad263e9dfcf4b5fdaba86d73libsss_simpleifp-1.13.0-40.el7_2.1.i686.rpm91ae414e1a972a3202815f583e3c7cde1c0eb37000ffbe3be3d788a36cae4c6esssd-common-1.13.0-40.el7_2.1.i686.rpm1a0d697f130b6e813070bcc2119d79c23f36b6b280a9cdd3da4af76f380c7dc0SLBA-2015:2565-1This update fixes the following bug: * Previously, the VirtualDomain resource agent (RA) sometimes removed the configuration file, for example if the virtual machine (VM) was added by using the "virsh define /etc/libvirt/qemu/vm.xml" command. As a consequence, the configuration file was sometimes deleted when trying to start the VM again, which caused the VM boot to fail. With this update, a backup file is created and copied back when the configuration file would be otherwise deleted. As a result, the VM starts as expected instead of failing.Scientific LinuxScientific Linux 7resource-agents-3.9.5-54.el7_2.1.x86_64.rpmf04b1b5d83a4187cb00bce1359e1b7b7af7b7062424fc24f3c749daa72e48ff7SLBA-2015:2566-1This update fixes the following bug: * The nuxwdog daemon does not require a GUI to run. As nuxwdog is one of the packages that depended on non-headless java packages, about 300 MB of packages were installed unnecessarily when installing the pki-server and other pki-* packages. As nuxwdog is primarily used by pki-server, which is in Scientific Linux 7 accessed through the CLI by Identity Management (IdM), the nuxwdog packages now require only java-headless instead of java packages because the java graphics classes are not needed. As a result, java packages are not installed because of a removed dependency in nuxwdog. Note that efforts are still underway to remove the dependency on java (as opposed to java headless) in other dependencies of pki-server.Scientific LinuxScientific Linux 7nuxwdog-devel-1.0.3-4.el7_2.x86_64.rpmf4b101c84e458e5e93c469a38aeab200b51ce2d1c1ef99824d88747f797b575dnuxwdog-1.0.3-4.el7_2.x86_64.rpmfc1347e0645b8f2d9cfe191a25163039bc3483e549ee9b50f9ed46e02ba31c03nuxwdog-1.0.3-4.el7_2.i686.rpm68cfe8cb9c1ed387cc4da38237b4ce9e6cd6d92b30751e0000df7f723152bd6fnuxwdog-client-java-1.0.3-4.el7_2.x86_64.rpm37355f3345a5af655d8b2c0e9d6abf29701369dc5e3d28d5e362d07f5da1f767nuxwdog-devel-1.0.3-4.el7_2.i686.rpm41de057e1b77b8be20db34d1c1e2ca83780a2ff1c5e13a65db5e8a72558b46d0SLBA-2015:2567-1This update fixes the following bugs: * Previously, the vhost-multiqueue feature could not be used with QEMU versions earlier than 2.4. With this update, the QEMU version that libvirt searches for has been changed from 2.4 to 2.3, which allows the feature to run with earlier versions of QEMU. * Prior to this update, guest virtual machines with 1 GiB or less allocated memory in some cases failed to start on IBM Power systems. With this update, the memory lock limit is calculated using architecture- specific logic, which allows the affected guests to start as expected. * When using Virtual Function I/O (VFIO) passthrough devices, the memory lock limit failed to be modified during a memory hot-plug operation. As a consequence, the guest virtual machine terminated unexpectedly. Now, the memory lock limit modification is performed before the memory hot-plug, and the described crash no longer occurs. * When performing a guest migration with the memory hot-plug feature enabled, the destination host logged the following untrue error message: "unsupported migration cookie feature memory-hotplug" With this update, the migration cookie is parsed correctly, and the error message is suppressed. After installing the updated packages, libvirtd will be restarted automatically.Scientific LinuxScientific Linux 7libvirt-daemon-driver-interface-1.2.17-13.el7_2.2.x86_64.rpmfe6abbc431f597f81f619fa6843a332f1fc070cea6a4967f0e8f0eafb83e3350libvirt-docs-1.2.17-13.el7_2.2.x86_64.rpm8ec4def3d5fd1ff81ec93438835b1f8bb962720bd9febf7181ae267d51273383libvirt-daemon-1.2.17-13.el7_2.2.x86_64.rpmb0c62dc323d6ebcc3294d3c0667a208b062c7ae05c51308072b1e1f994dd7124libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.2.x86_64.rpm9a7d35c8ba9378fe5b647d68ffa8ff44dad948c2bbb7d10d1302a345a576fcbelibvirt-daemon-config-network-1.2.17-13.el7_2.2.x86_64.rpm23fe28d296f6c605a896e50b25a52cc4e3271f4931671f8461fa2b47e034c128libvirt-client-1.2.17-13.el7_2.2.x86_64.rpma72a4de1fe7333bb5604e3407a5a103cb8fe976cfb50ffa5a8bb633c62156056libvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.2.x86_64.rpm5760f90021ff956561ce8dfd626f7d83a4b263be64a7a83e0089a40a64853db6libvirt-daemon-driver-secret-1.2.17-13.el7_2.2.x86_64.rpm7e9252622797986872a268d51f5de91fa58e4d8a0a4c4a6dfd3a34efa8bf2756libvirt-login-shell-1.2.17-13.el7_2.2.x86_64.rpmf391c94260229e87d4ca86470d2c6364cbb71d4255d10580b498ad62e2a4ab4clibvirt-daemon-lxc-1.2.17-13.el7_2.2.x86_64.rpm91f9488af3ca25fa0ce63337cd7ae171fc32e0d2d888380373de9eaacac2e6b2libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.2.x86_64.rpm14cb1b4a101e64d9e453dc57735ebeab90a0b43f0096fe44a92ec9807191aceblibvirt-devel-1.2.17-13.el7_2.2.x86_64.rpmf2c5ebd8dfcaa9f19f21467d5677ca371fc68b9bfb78f8516fe86c931f5c1704libvirt-daemon-driver-lxc-1.2.17-13.el7_2.2.x86_64.rpm9658ec84147b2a54dd9b9464f38826686ffc213873416dbeeaf1daf12edb06c5libvirt-devel-1.2.17-13.el7_2.2.i686.rpm483a03e4d29fa065ec9ac16f72af9be6dc549b86902207de618b17b595c2a8fflibvirt-daemon-driver-network-1.2.17-13.el7_2.2.x86_64.rpm8966271dfd61df2f003f065857f39708436888c8525cade8704ca266dcc342e6libvirt-daemon-kvm-1.2.17-13.el7_2.2.x86_64.rpm321d3dd8e8c97e91c52a1e7d56e74937344f20b670af85fd0211940bd97006c1libvirt-daemon-driver-qemu-1.2.17-13.el7_2.2.x86_64.rpm3b3d832ff31f3d386aed40566ccfdfb245393026adbb0ce639af5a2b2dc1c789libvirt-client-1.2.17-13.el7_2.2.i686.rpm112e60034f9b4e97e85f6a5d10b5d553d89154bb9bfc4483ed16d20703f6bc00libvirt-daemon-driver-storage-1.2.17-13.el7_2.2.x86_64.rpmadee58a703e82c71bb0b6b5b7dffaa7ef832011e26d2d4d93a4dfe830650fe0dlibvirt-1.2.17-13.el7_2.2.x86_64.rpm2c7349e5a21a63ddbd70520f646f244a02b1bc3e1834f243ad17fa41130b0e34libvirt-lock-sanlock-1.2.17-13.el7_2.2.x86_64.rpm5323d405095c3e0238c7891faa7d856bf900920afcc7c17a43adf2900c416e49SLBA-2015:2568-1This update fixes the following bug: * Previously, when setting up a cluster to use IPv6 multicast transport, the nodes failed to detect each other. As a consequence, multicast routing did not work over IPv6. A patch has been provided to and IPv6 multicast transport works as expected.Scientific LinuxScientific Linux 7corosynclib-devel-2.3.4-7.el7_2.1.i686.rpma6b2fe51cc89a2930a1c0bad05415e9c26d2f317d4ffb708278557981481e8d1corosync-2.3.4-7.el7_2.1.x86_64.rpm3ac16e73f0f7cf1baf406ac3fd7941fb786efe9d99561c65b1e8c2d36ed49378corosynclib-devel-2.3.4-7.el7_2.1.x86_64.rpmc4e3017b4bbdccc8371cff3952123b57ae58ecae6bb02bc0aa8b43fc305855a8corosynclib-2.3.4-7.el7_2.1.x86_64.rpmd8acdd183b53e21b7c2ed0fb047d5695986cde3333a0455d44653812ea1e182fcorosynclib-2.3.4-7.el7_2.1.i686.rpm776f4329278b6e593db4efd9acddf899b24e5e66eb65a7d4086a8447114d41d2SLBA-2015:2569-1This update fixes the following bug: * Previously, configuration properties in the Ceph configuration file could overwrite QEMU command-line properties. This update fixes the order of applying Red Hat Ceph Storage settings so that correct values are used. 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-common-1.5.3-105.el7_2.1.x86_64.rpm5101bca41658e18d074958c869999d9c4a77b30c9ed07cbd1633936c23173a17qemu-img-1.5.3-105.el7_2.1.x86_64.rpm7c1628dfe19ae042641b83870c9645ac94190f4a3703b5c52fcddfc33b846a54qemu-kvm-1.5.3-105.el7_2.1.x86_64.rpm86beac197ade87e6245e3491350103529b2d7608f159108409d37940ee45aec0qemu-kvm-tools-1.5.3-105.el7_2.1.x86_64.rpm9fbdeb78ece6579e78ca5ac45ef26897350692d7450d105618e408ad9c836a13libcacard-devel-1.5.3-105.el7_2.1.i686.rpm2aa63c1dc2a29325b02947b0cd23a72051b731981dca32a6b9f03bc86a9b2849libcacard-1.5.3-105.el7_2.1.i686.rpm1b9f4097cffeb362ab3c0068df541a66ec2c681032e41e4c1580b02418ef90f2libcacard-tools-1.5.3-105.el7_2.1.x86_64.rpm76185630dc8c345b5cfa958c1c977d4c8f64bd0bdbce3f675d2be6c1bf8f0b0blibcacard-1.5.3-105.el7_2.1.x86_64.rpm3d64653110caeaba8d4590f7754642b354767970da5f6a884f665c587f9487f3libcacard-devel-1.5.3-105.el7_2.1.x86_64.rpm3f6e275c757117532433ed61d19ddb61cc3158ea9eeb5738713aa00afec52f4dSLBA-2015:2570-1This update fixes the following bugs: * Previously, the "tuned-adm verify" command, which verifies whether the current system settings match the requested "tuned" profile, evaluated missing sysctl settings as a failure. As a consequence, verification of the realtime profile used together with the realtime kernel could fail. Also, setting sysctl parameters that are not supported on Scientific Linux in a "tuned" profile created by the user could cause the verification of the custom profile to fail. A patch has been applied to address this bug. As a result, the missing unsupported sysctl values are ignored during verification, a warning is logged, and verification no longer fails. Also, the "tuned" output now contains the location of the log file with more detailed information. * The nohz_full boot parameter requires the nohz feature to be enabled, which is not the default for the real-time kernel. As a consequence, nohz_full did not work, and errors could be logged. To fix the "tuned" realtime profile, nohz_full has been removed from it. As a result, nohz_full is now not requested by "tuned" realtime profile. In addition, this update adds the following enhancement: * With this update, the cpumask of unbound workqueueus is set to the list of non-isolated cores in the "tuned" realtime profiles, as Scientific Linux and Real Time kernels now support setting the cpumask of unbound workqueues in sysfs.Scientific LinuxScientific Linux 7tuned-profiles-oracle-2.5.1-4.el7_2.1.noarch.rpmd1a2d1c77202ff1cd74001325b4ad14b4888ca327b722dc906bd42aec74dcc1atuned-profiles-realtime-2.5.1-4.el7_2.1.noarch.rpm5c1da9329c24b1a9230347ac6c3db676755ee01a5da07e7962267743c631fa35tuned-2.5.1-4.el7_2.1.noarch.rpmc3747fc256c0275ef16ab806970f38e6e2a5cd64877315838233e5272bba6bfatuned-gtk-2.5.1-4.el7_2.1.noarch.rpm62cacc7800c9a7848f3e3da507f4ffa5a95a8f18798461777ad6684d810387e7tuned-utils-2.5.1-4.el7_2.1.noarch.rpmfcb565fb2e9e00256f0d34289f54c65002a3c583928aadcabf202f014d4dfde7tuned-utils-systemtap-2.5.1-4.el7_2.1.noarch.rpm0fe5e52b87e3e372e4055790ef9c3970d26dce7bc710f9da69fe2fffa8e7cf04tuned-profiles-atomic-2.5.1-4.el7_2.1.noarch.rpm991a5cb3db7cbc554373a99874669c2b62255240186f1b77024297c2af6e4272tuned-profiles-compat-2.5.1-4.el7_2.1.noarch.rpme3c899f99c2b4958ddba8aa9d0cd6bac7646ba50ed40a829df8eeb191402e38ftuned-profiles-nfv-2.5.1-4.el7_2.1.noarch.rpmbca39d573f3f85d27ec7d394f7db9559d4de6caf2271f492d6f8bf3fbcdd2905SLBA-2015:2571-1This update fixes bugs in the Schema Compatibility plug-in (slapi-nis) to improve stability when integrated with Scientific Linux Identity Management: When slapi-nis responds on an LDAP search query, it holds a read lock for the internal structure called "map cache". The map cache lock can also be taken for write when modification would be required, like responding to DELETE, ADD, or MODIFY operations. As result of the lock semantics, the write lock owner is blocked until all read lock owners release their locks. This is generally not a problem, but when readers send out LDAP query results, they call the SLAPI function that can take a long time to send out the data due to external reasons, such as network latency, clients being blocked, and others. For the duration data sending, the map cache is locked for write operations. When Scientific Linux Identity Management's Kerberos Key Distribution Center (KDC) issues a Ticket-Granting Ticket (TGT), it needs to modify several Kerberos-related attributes in the principal LDAP entry. These updates are generating MOD operations visible by the slapi-nis plug-in, which triggers re-scan of map cache to potentially replace the affected entries. To perform potential replacement, slapi-nis has to take a write lock and be blocked by outstanding readers. Therefore, it is possible to encounter a situation where an LDAP client uses Simple Authentication and Security Layer (SASL) Generic Security Services API (GSSAPI) authentication and existing Kerberos ticket did expire in during an outstanding search request. According to the LDAPv3 protocol specification, an LDAP client must perform re-negotiation before reading any outstanding PDUs. Previously, it asked Kerberos KDC for a new (or renewed) TGT, that would cause MOD updates for the primary tree which is tracked for changes by slapi-nis. These changes would be blocked by a slapi-nis reader as the client cannot finish reading outstanding PDUs yet. Additionally, slapi-nis had several bugs which prevented the use of the ID Views feature of Scientific Linux Identity Management solution when providing legacy clients access to information about users and groups from trusted Active Directory (AD) forests.Scientific LinuxScientific Linux 7slapi-nis-0.54-6.el7_2.x86_64.rpm291c165e7eb05bd6c3c76266f0deb0fb36750ede00a708f4cb01ffda6a259e24SLBA-2015:2572-1This update fixes the following bugs: * Previously, when nunc-stans was enabled, the default thread number was 3, and the thread number was controlled by the MAX_THREADS environment variable. With this update, the value of the nsslapd-threadnumber configuration parameter is used instead of obtaining the thread number from MAX_THREADS. * Prior to this update, the Directory Server could receive an abandon request for a SimplePagedResults request in the source code between the abandon check and the part of source code that sends the search results. Consequently, the abandon request freed the search results that the result-sending code still referred to, and the Directory Server terminated unexpectedly. Now, the source code that sends the search result is protected by a lock, which prevents the abandon request from occurring. As a result, the Directory Server no longer crashes in the described situation. * Previously, when promoting a consumer to a master, the new Replica Update Vector (RUV) element was appended to the RUV. However, when trying to replicate from the newly promoted replica, the remote replica checked the first element in the RUV, which had the same replica ID, and aborted the replication session. As a consequence, the replication between the two servers failed, and other RUVs on other replicas could become corrupted. Now, when promoting a replica to a master, the RUV is reordered to be the first in the list, and replication no longer fails in the described scenario. * Previously, the function acquiring a connection was called in an assert call. As a consequence, the function acquiring a connection was not called if the build was not a debugging build, which caused the connection reference count to become out of sequence. Now, the function acquiring a connection is called regardless of the build type, and connection reference count mismatching no longer occurs. * In the back end deletion, a transaction info was not passed to one of the database helper functions. Consequently, if a plug-in attempted to access data in the area locked by the transaction, a deadlock situation could occur. Now, the transaction info is passed to all the necessary database helper functions, and a deadlock no longer occurs in the described situation. * Previously, in access control evaluation, retrieving a matched value for a macro failed to remove a trailing comma. As a consequence, if the Access Control List (ACL) contained a macro, the correct permission was not provided. To if a trailing comma is found in the matched value, the comma is properly removed. As a result, if the ACL contains a macro, the correct permission is provided. After installing this update, the 389 server service will be restarted automatically.Scientific LinuxScientific Linux 7389-ds-base-1.3.4.0-21.el7_2.x86_64.rpmfaa532722bd7b6920e49d20243e204944923949d1bd906d62383c85771c064b8389-ds-base-devel-1.3.4.0-21.el7_2.x86_64.rpm9c1d8f9f9a7352c44d8c152663c71b481461bbb0477a6eaa2c0ad40cb0ed8c9e389-ds-base-libs-1.3.4.0-21.el7_2.x86_64.rpm527445473b2f855f451607d7db0b43b46cbc1d6339fdc7010eadfe431fa4ced9SLBA-2015:2573-1This update adds the following bug: * Because of unneeded check in logrotate's code, logrotate was not able, when using the "olddir" directive, to rotate the log files that pointed to a directory located on a different physical file system than the one storing the original log file. The check in logrotate's code has been fixed, and logs are now rotated in the mentioned case when the "copytruncate" or "copy" directives are used together with the "olddir" directive.Scientific LinuxScientific Linux 7logrotate-3.8.6-7.el7_2.x86_64.rpm95c6405b08778b1e75e99386f2777047260d19417f1c534dbacadb5166af8cd3SLBA-2016:0002-1This update fixes the following bug: * Due to a regression, the NUMA node was not reported for PCI adapters, which affected every IBM Power system deployed with Scientific Linux 7 and caused significant decrease in the system performance. The underlying source code has been patched, and the system performance no longer suffers in this situation. The system must be rebooted for this update to take effect.Scientific LinuxtrueScientific Linux 7perf-3.10.0-327.4.4.el7.x86_64.rpmc6f616b5985945c3e6955bfae0849998e06401101d2d8b40aa59128c5de8ce6fkernel-abi-whitelists-3.10.0-327.4.4.el7.noarch.rpmf0d84908c9525a8615f018f28c9f2ee98946464def714102916937e7692b6a1dkernel-3.10.0-327.4.4.el7.x86_64.rpm2733a39e077b0676a4a12d5c1de0c14f79bd70e3fa6af480bca6c74b8c0852a4kernel-doc-3.10.0-327.4.4.el7.noarch.rpm1c64efa44db3946f842352ba3dcff45fa64698efbd31303bc7a9e2791f8fee3dpython-perf-3.10.0-327.4.4.el7.x86_64.rpm52ba516e986cf0bd0aa48ab1bfde6d67a14b204e04734a9a4903b41c66ba87ddkernel-devel-3.10.0-327.4.4.el7.x86_64.rpm7ec3dac8e840ebaab8318cb1a8504f7177964c192de2458c7ab0c265ba929ad9kernel-tools-libs-3.10.0-327.4.4.el7.x86_64.rpmfb6feff80958123a2f559c18333b4d0dbf8c3d80f1e80bb94caa6518d1c7199dkernel-debug-devel-3.10.0-327.4.4.el7.x86_64.rpmc59687fd4e6d2e4d1f378bfbd669476223a5ddc5a21e48217b924a2fa88103f8kernel-tools-libs-devel-3.10.0-327.4.4.el7.x86_64.rpm77730b2c372a63c572fa659c5393bcdd9ac1c0d5644836aca08595d6c5ceaf4fkernel-tools-3.10.0-327.4.4.el7.x86_64.rpmdf49410b42bec756a0ed932eeb39ff8ac65e77d09b6889449b9bdcfaf02656a8kernel-headers-3.10.0-327.4.4.el7.x86_64.rpm9501adf014c4cb691cf7c8d741356057820e451888e2b079af28082641d2aedbkernel-debug-3.10.0-327.4.4.el7.x86_64.rpm2842523a54259f0b8575264963cf169499000c5261913680a0744d28e92211c7SLBA-2016:0003-1This update fixes the following bug: * Previously, grub2 builds for EFI systems were not correctly signed for Secure Boot environments. Such packages caused the bootloader to fail. With this update, the packages have been rebuilt with the correct signing set up. As a result, the GRUB2 bootloader receives the correct signatures and can be run as expected.Scientific LinuxScientific Linux 7grub2-efi-2.02-0.34.el7.x86_64.rpm238901fe715b04080000bb9c19e25420a19039af836e4031fae1044e1ae092d2grub2-tools-2.02-0.34.el7.x86_64.rpmba67becffbf61396d9c6fab69335c4fd46ea2bf60d62fa2a9f2f9237847d7e8agrub2-efi-modules-2.02-0.34.el7.x86_64.rpm1debbb7531bbb6a742d23ccf39965e05a9f035ddeca694b42088d0c962b4bb4egrub2-2.02-0.34.el7.x86_64.rpm912e8ce5c3bc636779cb24fa6b7fb96fcfab07003bf8c0c601eb7b6c2a9438c9SLBA-2016:0177-1This update fixes the following bug: * When creating sparse files, the fallocate utility could allocate extents beyond EOF using FALLOC_FL_KEEP_SIZE. As a consequence, when there was a gap (hole) between the extents, and EOF was within that gap, the final hole was not reproduced, which caused silent data corruption in the copied file due to its size being too small. With this update, the cp command ensures that extents beyond the apparent file size are not processed, as such processing and allocating is not currently supported. As a result, silent data corruption in certain type of sparse files no longer occurs.Scientific LinuxScientific Linux 7coreutils-8.22-15.el7_2.1.x86_64.rpm92c6336218078205f5a02994b6bf6c1a21478ef3c88fc15fad2375aee95b95c3SLBA-2016:0178-1This update fixes the following bug: * When using the Cyrus SASL library (cyrus-sasl) Generic Security Services API (GSSAPI) plug-in, all connections shared a single lock for both server and client implementations. As a consequence, a deadlock in the cyrus-sasl GSSAPI plug-in caused the whole Directory Server to become unresponsive when both outgoing replication and incoming client connections used SASL GSSAPI. This update introduces per-thread locks, which minimizes the required synchronization and prevents a deadlock from occurring if some threads are blocked. As a result, the Directory Server is now able to reliably handle concurrent connections that use the cyrus-sasl GSSAPI plug-in.Scientific LinuxScientific Linux 7cyrus-sasl-devel-2.1.26-20.el7_2.x86_64.rpm836327a838307d6a09a582931cc72d5f4993fde10f508adb088ae2d51332596fcyrus-sasl-ldap-2.1.26-20.el7_2.i686.rpmf843baf220fc1f6d55a829a7c31acb1702b70c3493d17a16c26a75c9172ea555cyrus-sasl-gssapi-2.1.26-20.el7_2.x86_64.rpm1cb7d1c059c86de6b08606269603ead8af78aba3ae208d424f1dac689343d319cyrus-sasl-ntlm-2.1.26-20.el7_2.i686.rpm5fa6363ffc9b66d40d8c13fd035879bb27675a4c437c8898c84ef26a7d37ee3acyrus-sasl-plain-2.1.26-20.el7_2.i686.rpm07936c3f2ff7fb8381c08f586b209466bc13858289b57ab6f64f00eb5ab4d4abcyrus-sasl-ldap-2.1.26-20.el7_2.x86_64.rpm0d14fb83971244d64cc8e7469fcf1df0609e6e4eed6cdfb65ce31cc583c87472cyrus-sasl-scram-2.1.26-20.el7_2.i686.rpma6c63d001bc12e41a875466e420fa1d641361854c988a4d37e4b440afd731739cyrus-sasl-lib-2.1.26-20.el7_2.x86_64.rpmd03741b7eea454f719f822d77cd05c09a3f05bc40eced0c9768b59819c899fcecyrus-sasl-scram-2.1.26-20.el7_2.x86_64.rpme42c49d55c5c585b6d038c5e5fd5ea3696f1be87c56a91bf9f88d44c2c5ce9e9cyrus-sasl-lib-2.1.26-20.el7_2.i686.rpm5a3d6e9cb53b4652ad050d2f68d9edf91b548de2206530681d59250edd0715edcyrus-sasl-devel-2.1.26-20.el7_2.i686.rpm6462f5ba77d3f766eda5a84ea3d571e75794408fa68638590b4338912016ae82cyrus-sasl-md5-2.1.26-20.el7_2.x86_64.rpm172662be921ae08990c52e81d347e2e31d598204042e7cfaa9bd5c66b040c35fcyrus-sasl-2.1.26-20.el7_2.i686.rpm2f7c056b092aac4a8175e096366852ca4b10646c9e634607f69aaa440e0c56cdcyrus-sasl-ntlm-2.1.26-20.el7_2.x86_64.rpm62c1a96bd1762580d48d2b0acba5a34b97f6c6978e051cb77888eaf87e5aded6cyrus-sasl-gs2-2.1.26-20.el7_2.x86_64.rpm25d6932d53fc070b41f0586d7ef288941ae52ff59e02cff5788f743a4e4ad305cyrus-sasl-gssapi-2.1.26-20.el7_2.i686.rpm8e3578cc4c76ec6ec0eb73ee6cd90502574f455fbad7b6c0f10fd68b825727fbcyrus-sasl-2.1.26-20.el7_2.x86_64.rpm32776124301e8ded964bddba55bcb2d1b468d5d892b01d55ab224794ca1af9e9cyrus-sasl-sql-2.1.26-20.el7_2.x86_64.rpmc173116dfdf87f61f65eb7fcfe698ac91090284e81ba6f1bff125507143c7c31cyrus-sasl-gs2-2.1.26-20.el7_2.i686.rpm78f9082e8d705d5d2c2f20591c72a1c15637129e42656037c24c216ac43dcb5fcyrus-sasl-plain-2.1.26-20.el7_2.x86_64.rpmb23412d026ae556ad164058af04b99ddbc1e6cebdbf2dfe6717c7873e4cd319ccyrus-sasl-sql-2.1.26-20.el7_2.i686.rpmc8989d6760241e2da6c2577046cb991bca39f8703e7a981a6395e4ba0cefa5abcyrus-sasl-md5-2.1.26-20.el7_2.i686.rpm5e0aceda7f5bc710bd387d7e4c2ebb32a6a53fbc5cb71673b0412166d0c33bfeSLBA-2016:0179-1This update fixes the following bug: * Previously, if an LVM thin pool was filled to capacity while new data was still being written, it was possible to lose some write operations even if the thin pool was being extended at the same time. In some cases, the extended thin pool still could not fit all data waiting to be written, but lvm2 still performed a flush operation, discarding part of the data waiting to be written without logging an error. With this update, lvm2 no longer flushes data when extending thin pools, and data loss is prevented.Scientific LinuxScientific Linux 7device-mapper-event-libs-1.02.107-5.el7_2.1.i686.rpm25d406ba81104d790b1bf69f9156463523cbc1762a75f24518c9ac85dbc967fadevice-mapper-devel-1.02.107-5.el7_2.1.x86_64.rpma29f15665834570d56dbdb26e29874a8c118e2ffb31c9025d63e8956aed90534device-mapper-libs-1.02.107-5.el7_2.1.x86_64.rpm399e2398251a502fd7c00e272a569f94f8641f249567b5e405399249ccb60cbcdevice-mapper-libs-1.02.107-5.el7_2.1.i686.rpmc28f7e8d4549b5d678b0af540ede9ea4b810368070a10760e45be9819ad2d909cmirror-2.02.130-5.el7_2.1.x86_64.rpm75d37cedc52c4c748f521c771b2a2d9dd097b3e42c6ede36a0922edb545c5da6lvm2-devel-2.02.130-5.el7_2.1.x86_64.rpm7fe7c466cea59c6d588127548004dfdb27defabac0d3d76d7fe176926a251e72device-mapper-event-libs-1.02.107-5.el7_2.1.x86_64.rpm7f88b6eae1699fef93862f20c17875df4c2c42d9e25de2e978f2283df0425064lvm2-python-libs-2.02.130-5.el7_2.1.x86_64.rpmcf21f8c9115057a920565ac03db07b6206e776c94d242a22d10bec48cf993543cmirror-standalone-2.02.130-5.el7_2.1.x86_64.rpmf828b31576d11922baf56e9a59592cf011d15731bfa66a7c4d48da6a691b2a4dlvm2-libs-2.02.130-5.el7_2.1.i686.rpm0f1f6a554369d70ec1f839007decdd6fb568e230bc76c1bf0fd8aa83f2be406blvm2-cluster-standalone-2.02.130-5.el7_2.1.x86_64.rpm92d4d5799ef56671e1a6f4bea8f7450b30f5a2ee3431d8f710d78c5a2700ed10lvm2-libs-2.02.130-5.el7_2.1.x86_64.rpm2619f815296d4a7a8b4960574d710c80cf4b73b62e16c9ff878bd658190bb673device-mapper-1.02.107-5.el7_2.1.x86_64.rpmae9e4f56d542c593235578351de7e0b47efd43b46c062d52b89d379d94955e0dlvm2-lockd-2.02.130-5.el7_2.1.x86_64.rpme8c4f51972b9fc2ef63eda5059d20794f0a297722979a7762a7ac6322f7674b0lvm2-2.02.130-5.el7_2.1.x86_64.rpm90842745d870be3174abb61a82fb79d3fa48087e19c261b544a7a4faa3724a96device-mapper-devel-1.02.107-5.el7_2.1.i686.rpmdf8f414925eb859944d1b2325e027c26fe92a417cd9cb612356d896af19add39device-mapper-event-1.02.107-5.el7_2.1.x86_64.rpmc25310353d666504f5762c6d97dc4b859a5af5a896b502f15b90e4c652c10abelvm2-cluster-2.02.130-5.el7_2.1.x86_64.rpmafb792d3035817a900f51bf8fd4c0ac4d38f7cdb4080ac9ce697884505495b77device-mapper-event-devel-1.02.107-5.el7_2.1.i686.rpma08a901a0373fc330d42908496267ab5575894baf425ec965b1f7a2316eff596device-mapper-event-devel-1.02.107-5.el7_2.1.x86_64.rpmcea076bceebe2a84a7f8e1422764af02a90164b29ad2de302685efd5a6317975lvm2-devel-2.02.130-5.el7_2.1.i686.rpma4d3a89d4019d24bd5916fdef1a2477ed928faf30fe5b053c758caebdd8500fblvm2-sysvinit-2.02.130-5.el7_2.1.x86_64.rpm70740854e01675042ef549158b38d8c5ea07c886b6f50f4ba59fed563b106eceSLBA-2016:0180-1This update fixes the following bugs: * With the introduction of VmFlags in the kernel smaps interface, the pmap tool could no longer reliably process the content due to format differences of the VmFlags entry. As a consequence, pmap reported incorrect values of totals to the user. The underlying source code has been patched, and pmap now works as expected. * The above fix indirectly triggered a hidden issue in the "free" utility, where missing initialization of the error status variable used for text string to floating point number conversions caused a failure of the "-s", "--seconds" command-line option processing. Consequently, the following message was returned to the user: "free: seconds argument failed". This bug has been fixed, and using the "-s", "--seconds" option with the "free" command no longer leads to failures.Scientific LinuxScientific Linux 7procps-ng-3.3.10-5.el7_2.i686.rpm9aeb713b9e407d0368b6f83a3bd36ef597760a0ef2b4372594357da62845bc03procps-ng-3.3.10-5.el7_2.x86_64.rpmf6a90572e69c75d5a637f63a71c59b80bd86fe4f50f267fe844adc9b900a3b53procps-ng-i18n-3.3.10-5.el7_2.x86_64.rpm9ff85db540bd4f0a9e670b580b9e8607132aabf805faea18a411423118bac8bfprocps-ng-devel-3.3.10-5.el7_2.x86_64.rpm2818f2591eb8fde91fc26e329c5ddae52cb5ba7313eb85822dbbb30a74c2926eprocps-ng-devel-3.3.10-5.el7_2.i686.rpm0924ff7ef1b219b0943eef1716c690738a42f9234a88d684b50b3c2f2196bdccSLBA-2016:0181-1This update fixes the following bugs: * Previously, if two or more virtual host bus adapters (HBAs) were created on a single physical HBA, only a single link to the device was created in the /dev/disk/by-path/ directory, instead of a link for each path. As a consequence, creating a virsh pool with virtual HBAs by using Fibre Channel N_Port ID Virtualization (NPIV) did not work correctly. With this update, symbolic links in /dev/disk/by-path/ are created correctly and are unique. Note that symbolic links in /dev/disk/by-path/ created by udev for logical unit numbers (LUNs) connected through a physical Fibre Channel N_Port stay the same. * Due to an endianness problem, systemd previously read the device identification bytes in an incorrect order. As a consequence, the /dev/disk/by-id/wwn-* symbolic links generated by the udev device manager were incorrect. A patch has been applied to put the device identification bytes in the correct order. As a result, the mentioned symbolic links are generated correctly. * The device mapper sets the DM_UDEV_DISABLE_OTHER_RULES_FLAG signal to indicate that other rules should not react to the event. However, systemd previously considered the related device not to be ready for use, which is only true for the ADD event. As a consequence, overlaying file systems on the devices were unmounted even if only one path became unavailable, but other paths were still accessible. With this update, the device is marked as unusable only in case of ADD events, and CHANGE events are ignored. As a result, file systems are no longer unmounted if a CHANGE event occurs.Scientific LinuxtrueScientific Linux 7systemd-devel-219-19.el7_2.7.i686.rpm0defe52977e979161163a3d9e77e40a0af0043071dbb038cab5104c6f69627d4systemd-libs-219-19.el7_2.7.i686.rpm4929bec39e3b0c861fd492c7873dcfad9523fbd87f7c92c35eb05b4284b6f9c0systemd-libs-219-19.el7_2.7.x86_64.rpmc373f456226163712e0ae2422440c81e13d00e068b900b52bbc7b9204b9c2967libgudev1-devel-219-19.el7_2.7.i686.rpmcb22fb97b91fd0e5eeec55b0424797fc08fc248af3197989e8c3cc0d010e29cflibgudev1-219-19.el7_2.7.i686.rpm9cd91565476f432351e50807dac7fd116c4bde4d39bbdd89e83d4d0825296585libgudev1-devel-219-19.el7_2.7.x86_64.rpmdba071683f8b0971490dc18b829068f8077bfc5a8d84e93acbbcd9abfc4eb830systemd-devel-219-19.el7_2.7.x86_64.rpm8aa78fb1a975b684dca43bba880d31b7aaa8bd4fd70c73f71a336e834e335dc8systemd-sysv-219-19.el7_2.7.x86_64.rpm00f6fadf430e8c44511b945e7abbfa225f120b16d9f1c7c04e6a787bf238549esystemd-python-219-19.el7_2.7.x86_64.rpmb44dce16d2d566ebbf42508b0834634699a73f59cfda0b65e2a72bfd2cf723f5systemd-networkd-219-19.el7_2.7.x86_64.rpm9016bd742ee5769eb46f06495c3ba6fbd66ddbc326e334e9baf2e0394590f441systemd-resolved-219-19.el7_2.7.x86_64.rpm74e3fabcca2bcd7d25d2c3e5ce36f8f5db7126ab86af004f0ea1dfc27a165917systemd-219-19.el7_2.7.x86_64.rpm106bf82107b585c41db8648ee708fb6d64a1c35b1028347e0a40e9c1be7eaeafsystemd-resolved-219-19.el7_2.7.i686.rpm3374296cc288d037391b270baaaea82118321cf64b00bf3e6dc17b278291455asystemd-journal-gateway-219-19.el7_2.7.x86_64.rpma7a84e0fae48471c593800a340c16be9c3d83a51b4626ebc77b12888a284f2a3libgudev1-219-19.el7_2.7.x86_64.rpmabe5b8571daecea59456650586f9835455ce9389f8677977c72ec35f0e826e10SLBA-2016:0183-1This update fixes the following bug: * Due to invalid packets on the network generated by non-compliant mDNS implementations, avahi created logs about every invalid response packet. A patch has been applied to lower the number of logs created by the avahi daemon with regard to invalid DNS packets, and log files no longer contain the "Invalid response packet from host" log message for each received invalid packet. After installing the update, avahi-daemon will be restarted automatically.Scientific LinuxScientific Linux 7avahi-devel-0.6.31-15.el7_2.1.i686.rpm470024834370df8e4a480587f187fadebdac6fad87f8e13c4c0f2b73e9c9d19cavahi-devel-0.6.31-15.el7_2.1.x86_64.rpm60c441f808d5a30b7fb706933d43a65d45442ce1247890274ce554ac5831fdf2avahi-qt3-devel-0.6.31-15.el7_2.1.x86_64.rpm5b2708e33a345ccdeaf146b7a11c7d2eaf37dc9342f07a711b5599da2abb92deavahi-glib-devel-0.6.31-15.el7_2.1.x86_64.rpm276213d459cf3080608b1f4d68878b50a4fa3db7b30a435ee0244b9e05b9e83bavahi-compat-libdns_sd-0.6.31-15.el7_2.1.x86_64.rpme8328e63313effb2e61d709b08e13bd6365e3a785fd4e5d5c0ff209a985eddb9avahi-glib-0.6.31-15.el7_2.1.x86_64.rpm7d860e3b87500eedbe88a3ca659f000c3bf37c2eb126ba74b0f2fefe466d1221avahi-0.6.31-15.el7_2.1.x86_64.rpmfcce28b67c5c489b7e58d718a80fa9861a698b7818433c09bf4ab221d05c3cd6avahi-ui-gtk3-0.6.31-15.el7_2.1.x86_64.rpma8cc0ab2ca485e935c9eb4ab52baa4d113625aeddcc66320a85d0b3e8e214bd0avahi-gobject-0.6.31-15.el7_2.1.i686.rpmb6efb2f60eb06f6cb6524c3c8888aa627c000d76fd4ca49a42b610385185be55avahi-ui-0.6.31-15.el7_2.1.x86_64.rpm3493f7019895d3994935e44aa123dd91cb657ccd31aaf6dcdade2658b8ef8735avahi-qt3-0.6.31-15.el7_2.1.x86_64.rpm8a032afd1399f9a374babc02465c97d8d18bbfa62cb1c79e6936db309a37ff03avahi-qt4-0.6.31-15.el7_2.1.i686.rpm894e0a44aaa022ba62a6993b35533bb5b4f7924da807a5dd619b1fdfc6addbc7avahi-compat-libdns_sd-devel-0.6.31-15.el7_2.1.i686.rpmaeb71b5c175909864cb9600ae137527b7e78a8fdac963a3823b24b54bcc3e7caavahi-0.6.31-15.el7_2.1.i686.rpm7b6626fba9da124db94a137918e0be31288ca8ed9ceea868b3d037cefb6ca05cavahi-qt4-devel-0.6.31-15.el7_2.1.i686.rpm6adba27482098fb9d53064b217f90f6972b2aa8fb7c57997ce56cba98e9a7155avahi-dnsconfd-0.6.31-15.el7_2.1.x86_64.rpmcbbc1216593ad29ac9e70eee4ff815f06c582e7d0f833a131c0e1fd5ac8b90e8avahi-compat-howl-0.6.31-15.el7_2.1.i686.rpm78452e12d66a6e3a6d95bca7ced092f50fe2ffdff847420c2099db3639e91e5bavahi-gobject-devel-0.6.31-15.el7_2.1.x86_64.rpmd2a819394c5f74e18bc09b7f860f82968ff8ccb6da8b80f65c73dfa1aa0f5dd9avahi-compat-howl-devel-0.6.31-15.el7_2.1.i686.rpm4bea144e851799505aca18c3e07d55045a0e4002400a95e5acfa27fff6f32f21avahi-qt3-devel-0.6.31-15.el7_2.1.i686.rpm0e800bf8a3e7f900d262262d8187982df6183dcc604534463b3d6a44336c6ee1avahi-qt4-0.6.31-15.el7_2.1.x86_64.rpm89bd68526fae3c1ba201764a7a0b5b59a5c53613f9a71f9ceeeed222e8b8cfb2avahi-ui-devel-0.6.31-15.el7_2.1.x86_64.rpm5920aeccc597ef57630050a93d26ecf2e087fd19451762e5fb429f6606c25068avahi-autoipd-0.6.31-15.el7_2.1.x86_64.rpm16bdae351e55828256b52ffb8fcf3c824248f7e7cbed64f7573372f3e81d17e7avahi-gobject-0.6.31-15.el7_2.1.x86_64.rpma1be189934e8a3910e31a6433ab18a14166cd56897a0ed3662df3e7f3b674d7davahi-tools-0.6.31-15.el7_2.1.x86_64.rpmf5b42714c6f5ae277012b3d30a8fe0900461987d064739d17bef3453695f126favahi-libs-0.6.31-15.el7_2.1.x86_64.rpmb3d472f229adc3e5b9667e70689c365ea47ae9e7a84984647948c1f9beb43b9davahi-compat-howl-0.6.31-15.el7_2.1.x86_64.rpm2732d3da416293434b3e65672724d25d02d0e5c7c5b2cbe3a9a41b5fd4c07797avahi-qt3-0.6.31-15.el7_2.1.i686.rpm71894c6f1aded7878f7aa39b40412a3a883c645ee2a58b55eb333c4be67f0402avahi-qt4-devel-0.6.31-15.el7_2.1.x86_64.rpm53de4e424a1bae4610bd9340d714eaa5d70f88f191d41ae47c24d7ef3ff97fa7avahi-compat-howl-devel-0.6.31-15.el7_2.1.x86_64.rpmcf6bc293afccf4771f97aaf732f59845e19e94f6dbe23e7875b7c2edd57fbf4aavahi-glib-devel-0.6.31-15.el7_2.1.i686.rpm34d17aa62204187ff763c666cb40026fe0a72620dd42364acbaadfaf426566faavahi-ui-tools-0.6.31-15.el7_2.1.x86_64.rpmd6ec49ba7e400b96e3128c454fd9ecefa6a9c1ac18b4ccdec17a3445104c7f21avahi-libs-0.6.31-15.el7_2.1.i686.rpm81c4223829908222e398601c06da169d57eeb774e83af5f8a5dfd404752cba9eavahi-compat-libdns_sd-0.6.31-15.el7_2.1.i686.rpma54f2852ad8964648dc32600d16735b03f4c39ee79a3503933c444045e17a97bavahi-ui-gtk3-0.6.31-15.el7_2.1.i686.rpm2053764589df860c4aa106bb02012d77c391c040e541e868ac336bdfe71f6df1avahi-ui-0.6.31-15.el7_2.1.i686.rpm88a7116155ad401995e09b7e0a289af214c0cff28c7c6cc94ed019bb79639ef0avahi-gobject-devel-0.6.31-15.el7_2.1.i686.rpmf876fea0b817603cdf2c3b75b0dc85934688abb2ab73c14fcfd9dbddee4779e3avahi-glib-0.6.31-15.el7_2.1.i686.rpm10ffb65a2c8f39e3c8bf6fef468b7c27d267734095384d7db5df475ac0de4089avahi-ui-devel-0.6.31-15.el7_2.1.i686.rpm217debeb2d77f018e79898f29f1d3772ea5a259bf160a701315c70e088c71af3avahi-compat-libdns_sd-devel-0.6.31-15.el7_2.1.x86_64.rpmd69c12251318a86107c69fbe348e108ee88bed0ca9be8f7d908b5fd7c0ae06c0SLBA-2016:0186-1This update fixes the following bug: * Previously, when the numa_node_to_cpus() function was called on a node which did not have an entry in the sysfs directory, the libnuma library always printed a warning message about an invalid sysfs. Consequently, libnuma printed the confusing warning message also for physically non- existing nodes (for example, for non-contiguous node numbers) and this warning could not be overridden when the function was called using the dlsym interface. With this update, the mentioned warning message is printed just for NUMA nodes that were found during an initial scan but then did not appear in sysfs. As a result, users of libnuma no longer receive the warning message for non-contiguous node numbers.Scientific LinuxScientific Linux 7numactl-libs-2.0.9-6.el7_2.x86_64.rpm44f6efe1aac2958116c6baacfc03d82f7d9813ad07327637b094382de67171aenumactl-libs-2.0.9-6.el7_2.i686.rpm57d760bb8d39ca1fe11fc91ef97752d79c5759e22c7b4e4d13943af19ff0c39anumactl-devel-2.0.9-6.el7_2.x86_64.rpm428090fb310d560875b31e622a2f1cb9ce8ac8c4c6f9ee7fdd55fa26afcbae3dnumactl-devel-2.0.9-6.el7_2.i686.rpm361c83c6c5f88d89af59eccd61c8f7ed40a20751f3eb4369e1a932133a640b31numactl-2.0.9-6.el7_2.x86_64.rpmfd40f0fb303b5f7b06af546bcf74eb5c42b7fae50852dff34bcfb70a32d3a87bSLBA-2016:0190-1This update fixes the following bug: * Previously, when a user successfully unlocked a tty device that was locked by the "screen" utility, no syslog message was recorded of the event. This could cause vulnerability issues as monitoring and recording successful and unsuccessful logins assists in tracking unauthorized access to the system. A patch has been provided to and syslog now records any successful or unsuccessful unlocking events as intended. Users of "screen" are advised to upgrade to these updated packagesScientific LinuxScientific Linux 7screen-4.1.0-0.23.20120314git3c2946.el7_2.x86_64.rpmeb44522e1615d68f63bb98f7c67976e92d667496eee9217488f414f35009bff5SLBA-2016:0191-1This update fixes the following bugs: * Due to insufficient SELinux policy rules, Open vSwitch was not able to read from and write to a hugeTLB file system. With this update, SELinux policy rules have been updated, and Open vSwitch, labeled with the openvswitch_t SELinux type, can read from and write to a hugeTLB file system as expected. * Due to insufficient SELinux policy rules, the smbcontrol tool was not able to send the SIGCHLD signal to the ctdbd process, which was running in the ctdbd_to domain. With this update, SELinux policy rules have been updated, and smbcontrol, labeled with the smbcontrol_t SELinux type, can send SIGCHLD to the ctdbd_t domain as expected.Scientific LinuxScientific Linux 7selinux-policy-3.13.1-60.el7_2.3.noarch.rpm6b768ba7874ef2bed9fc8890f79420ea40bcf59ae9f81ee816c192aa506176ccselinux-policy-sandbox-3.13.1-60.el7_2.3.noarch.rpm26af5ed976b6a5204116a7790472fae61d3c4b8558ab4f6574fda61ae9322e3eselinux-policy-doc-3.13.1-60.el7_2.3.noarch.rpm91a4fd0dfdcb4e449c2485b14a4687d34eb292b9ebc9d4bc3ada0b785d5253b4selinux-policy-minimum-3.13.1-60.el7_2.3.noarch.rpmf9aa0410c24fa0debd98488b0a948ab89492b7fca42028bbbae46499a18f1eceselinux-policy-mls-3.13.1-60.el7_2.3.noarch.rpm8d0930ec9bd54393251e223da3821ca9702ce038ed720aa1d211ce0707517c2bselinux-policy-devel-3.13.1-60.el7_2.3.noarch.rpmb0cbf37e634021d3f696fff92223c2c8d8ed07c2bb28028d32ab0a0ea0dbdeabselinux-policy-targeted-3.13.1-60.el7_2.3.noarch.rpm6d6e4acd67de878d1a4e8e0ccbc088a9358bbee7931dfc8dfca0a20527538f5dSLBA-2016:0198-1The golang-github-cpuguy83-go-md2man package provides the go-md2man tool, which converts markdown documents to manual pages and other formats. This enhancement update adds the golang-github-cpuguy83-go-md2man package to Scientific Linux 7. All users who require golang-github-cpuguy83-go-md2man are advised to install this new package.Scientific LinuxScientific Linux 7golang-github-cpuguy83-go-md2man-1.0.4-2.el7_2.x86_64.rpmc5a35ed209fa54e79952de28ee166f2c1af54e65a74113d4a475c5a47d3a258eSLBA-2016:0199-1This update fixes the following bugs: * Under certain circumstances, by the time PID 1 adds a process to the scope unit, the process can already be ended if the process is short- running, for example an invocation to /bin/true. As a consequence, when the systemd service picked a recycled name for a scope, the following error could occur: 'Failed to start transient scope unit: Unit run-XXXXX.scope already exists.' To systemd-run synchronously waits until the scope unit that is being created is started. * If a mount unit is bound to a device, systemd tries to unmount the mount point if systemd regards the device is no longer connected. Due to the udev event queue (uevent) and the inode notifications (inotify) of /proc/self/mountinfo being two different sources, systemd could not reliably determine the order of events. Consequently, if the uevent queue had ADD, REMOVE, ADD queued and an inode notification from /proc/self/mountinfo was received about the device, or a libmount event occurred, systemd sometimes erroneously unmounted the device in question. To a weaker dependency between mount units and device units is now applied. * A new systemd feature was introduced in Scientific Linux 7.2: cleanup of all allocated inter-process communication (IPC) resources with the last session a user finishes. A session can be an administrative cron job or an interactive session. This behavior can cause daemons running under the same user, and using the same resources, to terminate unexpectedly. With this update, cleanup of all allocated inter-process communication (IPC) resources is disabled by default. * Previously, systemd ignored symbolic links in the /etc/rc.d/init.d/ directory. As a consequence, init scripts with symbolic links included in /etc/rc.d/init.d/ could not be started using systemd. With this update, systemd follows symbolic links included in /etc/rc.d/init.d/ to init scripts. Note that the real location of the init script must be on the partition that is mounted in the initial ramdisk (initrd). * Due to a change in the systemd source code, units with the PrivateTmp directive had a dependency on the tmp.mount unit. As a consequence, a temporary file storage system (tmpfs) was mounted on top of the /tmp/ directory after starting such a unit. This update removes the default dependency on tmp.mount and adds an ordering dependency. As a result, no unwanted tmpfs is mounted on top of /tmp/.Scientific LinuxtrueScientific Linux 7libgudev1-devel-219-19.el7_2.4.i686.rpm4eb66f03b53d578d669e577bcc9ff2521ec722d9d8a820b30443090c708bc957systemd-sysv-219-19.el7_2.4.x86_64.rpmbfe5f32a3f5d22926518db80f2685a148eb2e417bcfae676f09fab777a6f47d7libgudev1-219-19.el7_2.4.i686.rpm488789d7713142ce590db434028d36ff924d3f25e8f7075afe35a3861cdd3f1esystemd-resolved-219-19.el7_2.4.x86_64.rpm24599132fec9817322ea614a454840982ff3c257c1ff8c413d353cb567bf8680systemd-resolved-219-19.el7_2.4.i686.rpmb8869672845058f1f09ba8fa6b08eea071172a63824d772eff7540d335cb6aafsystemd-devel-219-19.el7_2.4.i686.rpma4adf91848faf28a3d0071be771a622eddb84ab77d23917974bc9dfff900fa2bsystemd-journal-gateway-219-19.el7_2.4.x86_64.rpmaa21af2b71082b9623804ac1b672e66f7a57b8403fc27ff998f5812e36538739libgudev1-devel-219-19.el7_2.4.x86_64.rpm18742defcd63ebf32e9a61bce2a7bb1b1b8d303cb707868ca65cfc95a6c44550libgudev1-219-19.el7_2.4.x86_64.rpm2988a116116b37b73a559947065cda419087461440a5effc64dac5d217ea4eccsystemd-219-19.el7_2.4.x86_64.rpm94b7900e23436a85b686babf9ec4c2131750fd61401a79cf77bb0c9805d2a71esystemd-python-219-19.el7_2.4.x86_64.rpm4d3558f8af505c45ead5a178032e06be848390f7d25ac3ff7e4f2a70027b6712systemd-devel-219-19.el7_2.4.x86_64.rpmbed22eb4856192b477347fd23bbda7b3898af5f6c3e473e3345550ddbfc79db9systemd-networkd-219-19.el7_2.4.x86_64.rpm268664507dbd2e3fc611b5cf3d291d600f024e2784ad41d529672b09484d0723systemd-libs-219-19.el7_2.4.i686.rpm0e5d06474f75f3c7e7a3e526bbee99ca8f115a1b6c589d915e2be641d53a47e0systemd-libs-219-19.el7_2.4.x86_64.rpme85acd8583c96a45eeb3f2676c0b47022d8fbbdca97273c0ab49b2200f1a3c85SLBA-2016:0201-1This update fixes the following bugs: * Previously, the createrepo utility did not test file locking correctly. As a consequence, createrepo terminated unexpectedly with a traceback when it was executed in a directory located on a Common Internet File System (CIFS) share provided by a NetApp storage appliance. The test for file locking has been corrected and createrepo now works as expected in the described situation. * Prior to this update, the mergerepo command used only the package name and architecture when merging repositories, and disregarded the package epoch, version, and release. As a consequence, removing duplicate repositories during the merge operation did not work correctly. With this update, mergerepo can merge package versions from multiple repositories, and duplicate repositories are removed as expected.Scientific LinuxScientific Linux 7createrepo-0.9.9-25.el7_2.noarch.rpm1f566292fea81e874b9f5ac31bf2955474420fe7ccefa10582a29f6d2a5b9a66SLBA-2016:0202-1This update fixes the following bug: * Previously, packages that used the /usr/bin/libtool utility could not be built or rebuilt, as the version of the gcc packages with which libtool is built is explicitly stated in the /usr/bin/libtool utility. The libtool packages have been rebuilt to be compatible with the latest version of gcc, and the described problem no longer occurs.Scientific LinuxScientific Linux 7libtool-ltdl-2.4.2-21.el7_2.i686.rpm7969c7c35c842fee8d79596e6ee36251208cf474a58463b9148281891ef0235flibtool-ltdl-2.4.2-21.el7_2.x86_64.rpme82548762d52c5ae838be0c2817c342433c9c6929792f184dd08e88d061fe4f6libtool-ltdl-devel-2.4.2-21.el7_2.x86_64.rpm23562f84e44e035210251b3a6fbc5a0f32eb5b9048de3a8a8453abc1781afbbclibtool-2.4.2-21.el7_2.x86_64.rpmd9c8f725d70762e3c8ce091a33d6baa235ce5b626f0585baf88bad43378795b5libtool-ltdl-devel-2.4.2-21.el7_2.i686.rpmb4332d4c44182e1efcacb7d64f299f8b4c9f2999f5d9358192de682a442a225cSLBA-2016:0203-1This update fixes the following bug: * Because of incorrect release numbering of the libunwind packages, updating libunwind sometimes failed due to a version conflict. With this update, the epoch number of libunwind downloaded from the Scientific Linux repository has been increased to make sure it is always considered a more recent version than libunwind from the Extra Packages repository. As a result, version conflicts are avoided, and the described failure no longer occurs.Scientific LinuxScientific Linux 7libunwind-1.1-5.el7_2.2.x86_64.rpm3cb322cfdd7fd7e68e4126275331414c9ed8bbf998e6499fa7f5d87f370df057libunwind-devel-1.1-5.el7_2.2.x86_64.rpm089b7311e82850061ccc89b215df13a93f49460be083da6e10d48473e8b736e7libunwind-1.1-5.el7_2.2.i686.rpm8a784274bba5c5820a651decff95fb7f66dd0fa0520ecdd162e8c72ba710d9a7libunwind-devel-1.1-5.el7_2.2.i686.rpmbec208e64dd0012309cab816bceac01d885c69a321d28db07c1668486b3bc0afSLBA-2016:0205-1This update fixes the following bug: * Previously, the systemd-libs package was not in the specification file of the python-pyudev package and the build system did not pick it as an implicit dependency because it was a runtime dependency. Consequently, in some cases, for example, during installation, systemd-libs was absent, which caused problems. With this update, the python-pyudev package has been fixed to require systemd-libs, and systemd-libs is installed prior to python-pyudev.Scientific LinuxScientific Linux 7python-pyudev-0.15-7.el7_2.1.noarch.rpmd9fe2aa8b29165af852795fbf79fb2f71f61a6e1fb0716e9f427df66b54a0546SLBA-2016:0206-1This update fixes the following bugs: * Previously, the rpc.gssd service assumed that all machine account names are specified in uppercase letters when searching for a matching keytab entry for the account. Any accounts which contained lowercase letters in their names were therefore ignored as no matching keytab entry could be found. With this update, rpc.gssd first looks for a keytab entry which matches the unmodified account name. If this fails, rpc.gssd converts the name to uppercase and attempts to connect again, ensuring that all accounts are used. * The "exportfs -u" command was previously returning an incorrect exit status due to missing error handling for the getaddrinfo() function. This update adds proper error handling for getaddrinfo() and unexporting directories using "exportfs -u" returns the correct exit status. After installing this update, the nfs service will be restarted automatically.Scientific LinuxScientific Linux 7nfs-utils-1.3.0-0.21.el7_2.x86_64.rpm68ac54457c96e4c96584d057310da90c608387f5ab97fb0b5720d97283397d4dSLBA-2016:0207-1This update fixes the following bugs: * Previously, using the fence_scsi_check.pl watchdog script failed to initiate reboot. Consequently, when Global File System 2 (GFS2) or other file systems were used, file systems could be blocked from unmounting. This update provides a new fence_scsi_check_hardreboot script, which ensures hard reboot. As a result, problems with unmounting no longer occur. * The fence agent for OpenStack has been updated to the latest version, which provides a number of bug fixes over the previous version. * Previously, fence agent for Cisco UCS used an API that was not supposed to work with decommissioned machines. This update provides a call to the correct API endpoint. This allows working with decommissioned machines.Scientific LinuxScientific Linux 7fence-agents-common-4.0.11-27.el7_2.5.x86_64.rpm5eeed908466ef9d40ec117ca0ac32f8c4365210c2827e0fd7cd1ef74afee38ccfence-agents-emerson-4.0.11-27.el7_2.5.x86_64.rpm09e0cbbffebccbffbbd95e757086d71f3883da33a53269116c55224fe2376f2efence-agents-hpblade-4.0.11-27.el7_2.5.x86_64.rpme10601d448108b16cad2cfdbde4390b3b2ca8a006d522da19f9884461a486b06fence-agents-ilo-moonshot-4.0.11-27.el7_2.5.x86_64.rpmafa08ebaa5c4cd16970cd75c83aa25f3471727c54299d3852ed80739a67f1e4bfence-agents-apc-snmp-4.0.11-27.el7_2.5.x86_64.rpm65681253408905fd5b02e54bf33036dcecd07a8d256f2501a723655a1aced2cafence-agents-wti-4.0.11-27.el7_2.5.x86_64.rpm1191493eed4ff85eec75d64114715566380029d815b83bace5a547cf5fa52837fence-agents-bladecenter-4.0.11-27.el7_2.5.x86_64.rpm6e3750979b73582c33d0d2d3ea6a426546ccf8f2a1dd135c8554ec70cd39c393fence-agents-vmware-soap-4.0.11-27.el7_2.5.x86_64.rpmaf14f059028391c149afc5874d94a0b5dc801a82a3fb93e976666d6ab4e66ff1fence-agents-all-4.0.11-27.el7_2.5.x86_64.rpmecffa380c8c05f980c93cbd81cd202b79646b5757643a3c0822dcaad891f95a9fence-agents-cisco-ucs-4.0.11-27.el7_2.5.x86_64.rpma196dc04b28f0d2bd5feafa179847820e63fbdffa8b2184af80c88bbca4eca59fence-agents-ilo-ssh-4.0.11-27.el7_2.5.x86_64.rpm6d327f4c07eb0c29e01f1e2633fbb7b02f6641b00d035291363f269fa03b500dfence-agents-ilo2-4.0.11-27.el7_2.5.x86_64.rpm23fe3e2e024fdd103f4848b5d14624ff60f84d307c2f11ae23237a555924e4e4fence-agents-virsh-4.0.11-27.el7_2.5.x86_64.rpm19694985651b460a924d20970d3b07cb1820b22beef298acc1330ece8498e103fence-agents-apc-4.0.11-27.el7_2.5.x86_64.rpm8ffe3c2f681a610b81d34ce5a834f74ab784f27d94ec677c53d9e695d8940941fence-agents-ilo-mp-4.0.11-27.el7_2.5.x86_64.rpm401f155d2aaf8fec77f1d2a8aef51d8e5f7085a286b3678451f554bf67071bf0fence-agents-drac5-4.0.11-27.el7_2.5.x86_64.rpm780fa802e2065985f448ec255f7170cb3d20e26d5daf367a7e88e3997112ddf9fence-agents-ipdu-4.0.11-27.el7_2.5.x86_64.rpm7deed57f5454586c6f20f89beab47e5485cfc14cc992a8adc34c3585900026a4fence-agents-eps-4.0.11-27.el7_2.5.x86_64.rpma45a12ee20c32fed8c0e98325b17df838e162af9545b684cfce2d94dcaf95719fence-agents-intelmodular-4.0.11-27.el7_2.5.x86_64.rpm15db666cf97f670b38989d856e2dff9164796e08f731cae0fc6c53742c5bac3ffence-agents-eaton-snmp-4.0.11-27.el7_2.5.x86_64.rpm47f9576cf9ee3a78d007fb9859955d603363a1d1ba016d1ce96639d302a9ada2fence-agents-scsi-4.0.11-27.el7_2.5.x86_64.rpm65f8f45733017c7ace5b131661b11e05c4b7ea58e892449d49ebcf82342ec4fffence-agents-brocade-4.0.11-27.el7_2.5.x86_64.rpm0b6a1669c5d992838c4c8f135ea82124792394698605fe279179234891b43ff8fence-agents-kdump-4.0.11-27.el7_2.5.x86_64.rpm4d0339ceed67f417e3588802e1960d2e39a7b2d282830cd1c1c2abc5206a32d5fence-agents-compute-4.0.11-27.el7_2.5.x86_64.rpm8d6946eacd311ad2db1b0a8403bd16c96e5fde7c7e170c860da333b4f3f0e4fdfence-agents-ifmib-4.0.11-27.el7_2.5.x86_64.rpm0feb295c2268e0d8c90415dfa1ffde96949c40505cdebb7995a4532286e6dc32fence-agents-mpath-4.0.11-27.el7_2.5.x86_64.rpmeb5f149b4ed42dd04a5d0ddb950867ebb4e81f3b9ea9940169a057b64c225bd9fence-agents-ibmblade-4.0.11-27.el7_2.5.x86_64.rpmf073f7fc8cd36d920ef3eb3533dde54af7e853ccdc45f69e9ecc4aa494b10e0ffence-agents-rhevm-4.0.11-27.el7_2.5.x86_64.rpm142644b87ba1d62454993c6d26293f1e86533cb1236f1c0f8d97172206ba180bfence-agents-rsa-4.0.11-27.el7_2.5.x86_64.rpm0c2167e306fadb5be909e7a756d03f0496bd76c0783170329a174cbed72970b0fence-agents-ipmilan-4.0.11-27.el7_2.5.x86_64.rpmeb0879f230ddaad972c888790c80b43406a7c305ea740f16ddd498efc7b25eaafence-agents-rsb-4.0.11-27.el7_2.5.x86_64.rpm2311587354b0b5a987f281a5adffd7e1abbfacb2aec648bfb4b4bf571c58c698fence-agents-cisco-mds-4.0.11-27.el7_2.5.x86_64.rpm9aa3f39abfa3fc5cee9bf633fa2fb90f55fc701633d78b3a1b9b7188b816fbf7SLBA-2016:0208-1This update fixes the following bug: * When attempting to isolate some CPUs using tuna, tuna failed to move threads away from the isolated CPUs. As a consequence, only the threads with the same PID/TID had the correct cpumask set. The provided patch adds a function to check the /proc/PID/task/TID/stat file of a thread, which is called to verify the PF_NO_SETAFFINITY flag for threads. As a result, all threads now have the correct cpumask set as expected.Scientific LinuxScientific Linux 7oscilloscope-0.11.1-12.el7_2.noarch.rpmb1146c16727befb4318e603e118eee51b2b6751c94c210d01f11a2466112e95atuna-0.11.1-12.el7_2.noarch.rpm177d511b93a65a8689befb5a1f5ada058a94258350fb2be8f2b2f496c0488398SLBA-2016:0209-1The kpatch package has been upgraded to upstream version 0.3.1, which provides a number of bug fixes and enhancements over the previous version. With this update, the kpatch tool is compatible with Scientific Linux 7.2 live kernel patches.Scientific LinuxScientific Linux 7kpatch-0.3.1-1.el7_2.noarch.rpm835718e5473a293ac773898e80c49d96b1320dfe7dbac23607010870bed4728bSLBA-2016:0210-1This update fixes the following bug: * Incorrect memory handling in cases where multiple ISO domains with the same name were found in REST requests was causing applications using the libgovirt library to crash. This update improves memory handling in such cases and applications using libgovirt no longer crash due to memory corruption.Scientific LinuxScientific Linux 7libgovirt-devel-0.3.3-1.el7_2.1.x86_64.rpmec2ae1ab23e38930d2d9552aec07575f9ad585e3430e82754ffc91ca18b84e76libgovirt-0.3.3-1.el7_2.1.x86_64.rpme04ee502c5bc3837e425b950340a0aadfedeafec52dee8f9a75ea9bfc3269f81libgovirt-devel-0.3.3-1.el7_2.1.i686.rpm7f84d677e81c9ffaae9081962dadf8d37aa46181d56302b7cedd532ed70437bdlibgovirt-0.3.3-1.el7_2.1.i686.rpme32123c34cd3879739335ad31377868c9b18cbc64731c2840e7ba3156b9b3ad4SLBA-2016:0211-1This update fixes the following bugs: * The ipa packages require openssl packages of version 1.0.1e-42 or later. Previously, this requirement was missing from the spec file. As a consequence, upgrade of an IdM server could fail upon creating a SoftHSM database. With this update, the dependency on the correct version of openssl has been added to the spec file. As a result, the SoftHSM database is created and the upgrade is successful. * Prior to this update, an incorrect NIS server configuration container was created during an upgrade. Consequently, using the ipa-nis-manage utility did not create the required NIS maps, which could cause problems to users. The upgrade code has been fixed, the NIS maps are now correctly created, and the enabled NIS server works as expected. * If a umask was set to 077, files in the softhsm directory were created with incorrect permissions. Consequently, the named server was unable to read keys from the SoftHSM database and failed to start. With this update, the correct permissions are set, and the named service starts successfully in this scenario. * The version check during an IdM Server upgrade did not detect Scientific Linux version 7.2.z as a later one. Consequently, it was impossible to upgrade an IdM Server from version 7.2 to 7.2.z. This bug has been fixed, and the upgrade of an IdM Server from version 7.2 to 7.2.z is now successful. * Keys in the sysrestore file were normalized to lowercase values. Previously, the sysrestore utility did not expect that keys had been migrated to lowercase, and did not return the correct state. Consequently, this could cause rewriting of the kasp.db DNSSEC database. With this update, the sysrestore utility is now case-sensitive, the DNSSEC database is no longer accidentally rewritten, and all sysrestore operations work as expected. * The ipa-ods-exporter utility and the ipa-dnskeysyncd daemon did not properly handle DNSSEC key purging, which is automatically done by the OpenDNSSEC Enforcer daemon 14 days after the particular key is no longer in use. Consequently, DNSSEC key synchronization stopped working 14 days after a key rotation. Because Zone Signing Key (ZSK) is rotated every 3 months, the problem typically occurred 3 months and 14 days after DNSSEC was enabled for the first DNS zone. With this update, ipa-ods-exporter and ipa-dnskeysyncd have been fixed to properly handle key purging, and key distribution now works as expected after a key purging event. * The ipa-server-upgrade utility checks for a running certmonger service at the start of the upgrade process and raises an error if the service is not running. Previously, when the Certificate System CA service was not configured, a running certmonger service was not required, and the check always failed. Consequently, this effectively prevented the upgrade of a CA-less IdM master to later versions. With this update, the certmonger service is started also when the CA service is not configured, and the upgrade of a CA-less IdM master works as expected. * If the "skip_version_check" option was enabled, the IdM client identified itself as a client of IdM API version 2.51 to the IdM server. When the IdM API version of the IdM server was earlier than 2.51, the "skip_version_check" option on the client had no effect. Consequently, all API calls failed with an incompatible version error. With this update, if the "skip_version_check" option is enabled, the IdM client is identified as a client of IdM API version 2.0 to the IdM server, and the API calls no longer fail in the described scenario.Scientific LinuxScientific Linux 7ipa-client-4.2.0-15.sl7_2.6.x86_64.rpm67848642d073886910de80e5ae02456da994d62272aa587b645daed618c6f1b8ipa-python-4.2.0-15.sl7_2.6.x86_64.rpmb0dbb14ea4389c593195f03476ef6c35d15da2c070e0816e922d68182b36a676ipa-server-trust-ad-4.2.0-15.sl7_2.6.x86_64.rpmedb33a63b38f3982a926317568f03102cbef47b217467d9a5d9f82bb23a6d8dfipa-server-4.2.0-15.sl7_2.6.x86_64.rpm214e4ed97142b0cd6abb44107cbc7805054b2c106d3a01619d5d56ade73a72c8ipa-server-dns-4.2.0-15.sl7_2.6.x86_64.rpm7deb346e825f724521ad5d29c04f61cf7de93b01010b7f5e378f4b35b4efe551ipa-admintools-4.2.0-15.sl7_2.6.x86_64.rpm3ce227ea787e366aa57b23669b464cf22bf99e8099d6b495a1569a406ad7a40dSLBA-2016:0213-1This update fixes the following bug: * Previously, a race condition in the realtime-virtual-host Tuned profile caused the module's options not to be used and could lead to a latency spike. Tuned code has been amended to and the modprobe configuration file is no longer regenerated during reboot, which removes the race condition.Scientific LinuxScientific Linux 7tuned-gtk-2.5.1-4.el7_2.2.noarch.rpmd0ef936dee31ac96964b612199f23cc440562b5fc038874f632f82dc9e10c9a0tuned-profiles-realtime-2.5.1-4.el7_2.2.noarch.rpm4d220e334eb92e25f2eae5df05dbb6ddead382a008de5dd1cb866392ff8f9cd2tuned-utils-systemtap-2.5.1-4.el7_2.2.noarch.rpmd57ad16a54b806aff7379b321391d1f0977fdd917dc80dc68c1dadff3fdacb1dtuned-utils-2.5.1-4.el7_2.2.noarch.rpma7bdbd20b64bff4222ed959c1171071d79c0961a5525fd9908ae4ff33e853d54tuned-profiles-oracle-2.5.1-4.el7_2.2.noarch.rpm244f313d99a33eb8dfdb6502baa625dc41332f21dd4f8365b4710910f6ffd34dtuned-profiles-compat-2.5.1-4.el7_2.2.noarch.rpm844b89e16352df087f3736e10109c97e3a5b8368b3a92b789bd8b334fa0e0175tuned-profiles-atomic-2.5.1-4.el7_2.2.noarch.rpm824d6c6d84aee510572fbc4ed311aa2f124d70fc5ba4fa82a9d6612984255397tuned-2.5.1-4.el7_2.2.noarch.rpmd75adbb4a90e37177bd4bfd1864ed8c78c5cb40010ddf04c0d2b9f177f2acf68SLBA-2016:0214-1This update fixes the following bug: * Formats of sadump associate each bit in a bitmap with a physical page in reverse order with the kdump-compressed format. However, makedumpfile previously handled a bitmap in sadump formats in the same way as in the kdump-compressed format. As a consequence, makedumpfile attempted to check a physical page corresponding to an incorrect bit. This update reverses the bit to make it consistent with others, thus fixing this bug.Scientific LinuxScientific Linux 7kexec-tools-eppic-2.0.7-38.el7_2.1.x86_64.rpmc27d1781ba923bc493e62bfab24312aa4815c7c741b1aa229955223ae9c05f4ekexec-tools-anaconda-addon-2.0.7-38.el7_2.1.x86_64.rpm8be250a3355fa617b47b9839dc38ae09c915aafdfe4475fe2337eb175a156f7akexec-tools-2.0.7-38.el7_2.1.x86_64.rpm8798808a60994b1527115797a716d296c7eda550ea802eb28e55064937b32ed5SLBA-2016:0215-1This update fixes the following bug: * Previously, pulseaudio structures were not accessed exclusively. As a consequence, the xfreerdp client could terminate unexpectedly when sound redirection using pulseaudio was enabled. A missing lock has been added to ensure exclusive access for pulseaudio structures, and the xfreerdp client no longer crashes in this situation.Scientific LinuxScientific Linux 7freerdp-devel-1.0.2-6.el7_2.1.i686.rpm2134d467252cb25261c75b0b40281a9d492c45b1804e332a015d25ec75babde8freerdp-libs-1.0.2-6.el7_2.1.x86_64.rpm6dfb25ff814db2380c7db558d6c925632227678d21216afeba3448e8d280fce8freerdp-devel-1.0.2-6.el7_2.1.x86_64.rpm987706c88618d6d1b604a6e074143974724a2efd6c85138e9f0463108bdd4596freerdp-libs-1.0.2-6.el7_2.1.i686.rpmb495d853f6d21df86a3d9a94b2cab95d1be3ec0720b3910f52d50f35b181bfa6freerdp-plugins-1.0.2-6.el7_2.1.x86_64.rpm353a79c12afc17c967999769cfdd46755d0caa73099c32bde413338c727ece6dfreerdp-1.0.2-6.el7_2.1.x86_64.rpm73a438ffc17d8020cf4506c60ea2b56eb99dc7434b436f64557581c3efcc84c1SLBA-2016:0216-1This update fixes the following bugs: * Previously, Pacemaker's Local Resource Management Daemon (lrmd) used an invalid format string when logging certain rare systemd errors. As a consequence, lrmd could terminate unexpectedly with a segmentation fault. A patch has been applied to fix the format string. As a result, lrmd no longer crashes and logs the aforementioned rare error messages as intended. * When a Pacemaker cluster was configured with systemd resources, and the cluster was stopped, Pacemaker sometimes regarded a systemd service as stopped while the service was still running. Consequently, services could be stopped out of order, which could lead to stop failures. With this update, Pacemaker interprets systemd responses correctly, and systemd services are now stopped in the proper order at cluster shutdown. * Prior to this update, if a user deleted an attribute from a fence device, Pacemaker's stonithd service sometimes mistakenly removed the entire device. Consequently, the cluster would no longer use the fence device. The underlying source code has been modified to and stonithd now properly distinguishes attribute removals from device removals. As a result, deleting a fence device attribute no longer removes the device itself. * Previously, the ocf:pacemaker:HealthCPU resource parsed the output of the "top" command incorrectly on Scientific Linux 7. As a consequence, the HealthCPU resource did not work. With this update, the resource agent correctly parses the output of later versions of "top". As a result, HealthCPU now correctly measures CPU usage. In addition, this update adds the following enhancement: * The pacemaker_remote service can now be stopped on an active Pacemaker Remote node, and the cluster gracefully migrates resources off the node before stopping the node. Previously, Pacemaker Remote nodes had to be taken out of the cluster before stopping the pacemaker_remote service, either explicitly or implicitly by commands such as "yum update", otherwise the node was fenced. Now, software upgrades and other routine maintenance are significantly easier to perform on Pacemaker Remote nodes. Note that all nodes in the cluster must be upgraded to a version supporting this feature before the feature can be used on any node.Scientific LinuxScientific Linux 7pacemaker-cluster-libs-1.1.13-10.el7_2.2.x86_64.rpme48b59180ab2116c6cd45bc6584ca66b792fee9e5551251629fe36e9729c6b4apacemaker-libs-1.1.13-10.el7_2.2.x86_64.rpm13901c08fc4ad1be1610d59ee818faed07bdee822e3d1df8f217a7e82811d57cpacemaker-nagios-plugins-metadata-1.1.13-10.el7_2.2.x86_64.rpm3bf07685d18e146ec4d59c18320555d9f3462e9318c619cae1c3fc5b7a04c542pacemaker-cts-1.1.13-10.el7_2.2.x86_64.rpmbe63d989866e471d0f5df5dd4017840c6d8ac258426c81f3c650e5dbcf30f827pacemaker-cluster-libs-1.1.13-10.el7_2.2.i686.rpmcad07679e146d852a207ab5e75475c5279ad663dea8b8c1147e074b5d481adb5pacemaker-remote-1.1.13-10.el7_2.2.x86_64.rpm913139ac6fd2dc91844fe0b28644a7ca7b4f9dff341217cdf3966c072e8a3c1bpacemaker-1.1.13-10.el7_2.2.x86_64.rpm0fdfced040f77c15a56fc400498c2f7fd9e8d6499b46d710632f62e1956f842dpacemaker-doc-1.1.13-10.el7_2.2.x86_64.rpm9a7d9bb434bca721cfa2be84d81301552a2ea5bb0dcb3a196f7509cd3eca9cdcpacemaker-libs-devel-1.1.13-10.el7_2.2.i686.rpm181b0b706886be1a0304b517fd7e3e68aad6efb97802ceff7e9567e3ec36cf50pacemaker-libs-1.1.13-10.el7_2.2.i686.rpm1895387c24c6022d9daf2b5400eae242c34962b4a2de91be7613648efa85b6d7pacemaker-libs-devel-1.1.13-10.el7_2.2.x86_64.rpm79027f17e3ebc205db39d7748ac6e671cde248d89fc20cfa8cf2f552622239eepacemaker-cli-1.1.13-10.el7_2.2.x86_64.rpmaef07f4b3548331107c0d0d4b26cbdcc0e9c16ce4e22bb4b853ac21c8dacc036SLBA-2016:0217-1This update fixes the following bugs: * Previously, in the NovaCompute and NovaEvacuate scripts, the "evacuate" argument of the attrd_updater command contained a typo. Consequently, evacuation failed. With this update, the typo in the two scripts has been fixed, and evacuation no longer fails. * The fence_compute agent no longer supports the "reboot" action. Consequently, the "reboot" action cannot be used for evacuations anymore. With this update, the "off" action is used for evacuations instead of "reboot". * Previously, the nfsserver resource agent was unable to monitor all of its daemons, which could lead to incorrect status detection. Consequently, one or more of the required daemons might have stopped without the cluster noticing that the resource had failed. This update introduces further checks, and now the agent will retry once to give the resource an opportunity to resume working. As a result, nfsserver tries once to restart any missing daemons and fails if the process still is not running. * Previously, the galera resource agent was only able to connect to a local MariaDB socket. Consequently, galera could fail due to uncontrolled events, such as when the maximum number of connections was reached or when the connections were slow. With this update, galera now supports custom host and port options to benefit from MariaDB's extra-port and extra-max connections. As a result, galera is now able to connect to other MariaDB resources. * Previously, the NovaCompute resource agent managed the nova-compute process during instance migration. However, for OpenStack Platform director 8, nova-compute must be managed by systemd. With this update, NovaCompute has been replaced with the nova-compute-wait script, which waits for the migration to finish.Scientific LinuxScientific Linux 7resource-agents-3.9.5-54.el7_2.6.x86_64.rpmb05bd4062d6dc3d747e64fe7cd088dc27b7572a27e06ad251b1ee2fd1b0b77faSLBA-2016:0218-1This update fixes the following bug: * Previously, update conflicts occurred due to a different release of the ipxe package for Satellite and for Scientific Linux on RHEV. With this update, the ipxe package has been rebuild, and update conflicts no longer occur.Scientific LinuxScientific Linux 7ipxe-bootimgs-20130517-8.gitc4bce43.el7_2.1.noarch.rpm3c3905bf993316be2e4dac0ae8146b55da3f33e9323b8f0518300974c3340339ipxe-roms-qemu-20130517-8.gitc4bce43.el7_2.1.noarch.rpm754347c01db63f9f94598fbf3660ca3c54a6eaef24bfa8758aea0261da0f488fipxe-roms-20130517-8.gitc4bce43.el7_2.1.noarch.rpmcf6b0a2dc8daf9c8fd3884a4e596ac7b46bbb97c6ee6253f3a510a371bed2a7aSLBA-2016:0219-1This update fixes the following bug: * Previously, the ep11 token incorrectly copied the public key object class to the private key, thus both public and private keys were of the CKO_PUBLIC_KEY key class. The provided patch removes the relevant code and the default attribute functions ensure that the private key now has the correct information.Scientific LinuxScientific Linux 7opencryptoki-devel-3.2-5.el7_2.x86_64.rpme8e0504620989f04d5543fd65ade92d45c5d0d4cb90cafad280e5c43f0c2005eopencryptoki-icsftok-3.2-5.el7_2.i686.rpm569391e2c287c6ae9c6d23c4612cc4718aeedf60ba2256fb087cc6126c7fc434opencryptoki-3.2-5.el7_2.i686.rpm2595893ab9519fe202fe29ec64e0f1fe94def53ee6399143056980b03782b0e3opencryptoki-tpmtok-3.2-5.el7_2.x86_64.rpmcd9781acce1fa25bc8b3410d7228f6e389c9b4439d75e5ec0a10e235471400ecopencryptoki-tpmtok-3.2-5.el7_2.i686.rpmbae2a7420529b4d7e16688319b49239960e78db19a7e77048b7eece4d2e7eaf4opencryptoki-devel-3.2-5.el7_2.i686.rpmf1d1a654e7eee9230be3544ace3d690fbd24d75815c40d8c68b54bd74efb5347opencryptoki-3.2-5.el7_2.x86_64.rpm83253571ffc124bafe1d9c30b2154a910eb230f73d5b04bdb8956ac0293d7d43opencryptoki-swtok-3.2-5.el7_2.x86_64.rpmdcf1a31fe49e2b2db3b0ab237ddea7da6bc88742489258f3c340f840b6d8e58dopencryptoki-swtok-3.2-5.el7_2.i686.rpmde09149f01224a0aaaff3ef3f787a72ba631e398f28e64fb57c62e7296aa73ddopencryptoki-icsftok-3.2-5.el7_2.x86_64.rpm5a34b2869aaf0fbc9fb95b79610c4f4ac733b7a98e399b5b599cd479334fd712opencryptoki-libs-3.2-5.el7_2.x86_64.rpmc7dee2f6271686e9027dfc85b149eaff5816605ecdbd378e6b58e6a446a5a9e4opencryptoki-libs-3.2-5.el7_2.i686.rpmf48df8bbec7a586761d1dc6bb920b2d434ca29986ee4ba293ef0d0a02dcc2bd3SLBA-2016:0220-1This update fixes the following bug: * Previously, when using the libvirt library with the VMWare ESXi hypervisor, loading a guest virtual machine that contained empty CD-ROM images failed with an "internal error" message. With this update, libvirt is able to successfully parse ESXi configuration values for empty CD-ROM images, and the described failure no longer occurs. After installing the updated packages, libvirtd will be restarted automatically.Scientific LinuxScientific Linux 7libvirt-daemon-driver-qemu-1.2.17-13.el7_2.3.x86_64.rpm12799759a8c52ed60cfb79914cd555a2680428cc7889218f218242595ec255e7libvirt-client-1.2.17-13.el7_2.3.x86_64.rpme961cc433ee1e734e520a885e0226d7cfe11ed3e023be2937d9c5a350f76a7cclibvirt-daemon-driver-network-1.2.17-13.el7_2.3.x86_64.rpm1a0d55e5daaae7576ce8bef03a2debfb5266b62b6381fcad33938ceb102e2841libvirt-1.2.17-13.el7_2.3.x86_64.rpm2836f7206e2aae3326b4b985227fc35bef54a6d4e59325de16167ae821697b77libvirt-daemon-driver-secret-1.2.17-13.el7_2.3.x86_64.rpm8d80644fd7c740ed885dc5973da430f665755c0fed8bd05f117d07556c6ecffdlibvirt-daemon-config-network-1.2.17-13.el7_2.3.x86_64.rpmaebf164389477b0dbeb78108bafbccf922f5035aaf5b4070a025b11377365a09libvirt-devel-1.2.17-13.el7_2.3.i686.rpm0d2cfa81e69c2ad5df5933684c14702eb89ee57d64e5a5a604ba56f4194cd93flibvirt-daemon-driver-storage-1.2.17-13.el7_2.3.x86_64.rpm9c36c8aaf87ffd3f1f56705d0aa427526d5487672de3afcbeb2fa4b0165c2e43libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.3.x86_64.rpma4265824f8fe036942e5a07723ac9dc20ae6de76807016fa71e42bc9dc37ea62libvirt-daemon-1.2.17-13.el7_2.3.x86_64.rpm04352659ef93d0892e63dbdac3b6ab6d88b0d9fa71e7a7338fc90a143a883f33libvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.3.x86_64.rpm0498165c82e30afd0b567fa7f0abee66069f999c966fa460064176496411d701libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.3.x86_64.rpmb228937764aa282d0b3136c8b60f6b72a6f96b5188da0cc082a06795820c40e6libvirt-lock-sanlock-1.2.17-13.el7_2.3.x86_64.rpm71aa46bfca8ac0a0bf4465068f65c903667f282f8cc9236e23d121572c0b8f99libvirt-daemon-lxc-1.2.17-13.el7_2.3.x86_64.rpm74cb90a4c150094950f8253c0313f3fddad6f6369c05e86b8c38264a6ac58ce7libvirt-login-shell-1.2.17-13.el7_2.3.x86_64.rpm28ba90ec9dfe6bed50986a3eeb4ab5891a500d7b5da2c360d7b5b516dc938139libvirt-daemon-driver-interface-1.2.17-13.el7_2.3.x86_64.rpmd20179ca6681213aa2d9a76cc9f949da185823395421814fa7cb7159c1848fcdlibvirt-daemon-kvm-1.2.17-13.el7_2.3.x86_64.rpm7c16ab511c5aadceae01390e850bb6ac1217109c818895e4e6d427e619be183clibvirt-devel-1.2.17-13.el7_2.3.x86_64.rpm4fe632bfd9836c3c05546c836861ae70c5003f19df5456a95fdbc0e4a78dc9eflibvirt-client-1.2.17-13.el7_2.3.i686.rpm5ab1ca2a858dd1972a580645f1a45634be7039dd95c27a6a5ef9da67a1e23b64libvirt-docs-1.2.17-13.el7_2.3.x86_64.rpm8a946ffbd7c80fee86204edfce00fa84ddd58b5602e30dfd3f666a4ed3ab19bdlibvirt-daemon-driver-lxc-1.2.17-13.el7_2.3.x86_64.rpmed44c28ccfea1ad9dbc9ecf2d8d280ece750c17e450dfea3adfeeb7dede8644cSLBA-2016:0526-1This update fixes the following bugs: * Previously, after completing the SELinux autorelabel process, the "systemctl --force reboot" command was executed from the rhel-autorelabel script. Consequently, dracut-shutdown.service was not executed, and the rootfs device was not cleanly unmounted. With this update, the dracut- initramfs-restore script is executed before the reboot. As a result, disks are now cleanly unmounted. * Previously, the filesystem quotas were applied before starting the SELinux relabel process. Consequently, the aquota files could not be changed and were not properly relabeled. With this update, the quota are turned off before relabeling. As a result, relabeling works as expected.Scientific LinuxScientific Linux 7initscripts-9.49.30-1.el7_2.2.x86_64.rpmb62ce4944e5fa08d71679e3890a25d814d70d493fddbe48fae68f40c5facc722debugmode-9.49.30-1.el7_2.2.x86_64.rpm2ebd073216218cb7d8ebfee50647bedead1667f8b0f42b20a25fe796c28ecd76SLBA-2016:0529-1This update fixes the following bug: * Previously, multipath did not check correctly for the existence of the libudev() function to compile with support for resizing the uevent socket. The socket could thus overflow, making multipath miss necessary events. As a consequence, multipath failed to add all the path devices correctly. With this update, multipath checks for the proper function and compiles with support for resizing the uevent socket. As a result, multipath no longer misses uevents and adds all appropriate devices as expected.Scientific LinuxScientific Linux 7kpartx-0.4.9-85.el7_2.1.x86_64.rpm38873545cc50ba1e094d543ea2a724a59d474061c2afe4d61f09514633380d8bdevice-mapper-multipath-sysvinit-0.4.9-85.el7_2.1.x86_64.rpm34c666f0abd5d2975ff3863b52f10892eff58e4fe47c47c74b4ffa00ed442c41device-mapper-multipath-libs-0.4.9-85.el7_2.1.i686.rpme2a39c636d8e2e8536dd7534e5a5980ac47978cebb65693fe37b42cbd6af3cf1device-mapper-multipath-0.4.9-85.el7_2.1.x86_64.rpm1ab1844b1d84ac7b3a1071655f68683710c8ebc74f0a8a114b56040aac2d1a1bdevice-mapper-multipath-libs-0.4.9-85.el7_2.1.x86_64.rpm2dc445f61b0bbe27b195093013130e8587d2b69f968a7cdda1e22524e82566f3SLBA-2016:0530-1This update fixes the following bug: * Previously, a race condition in thread initialization code provided by the openldap library could cause programs using this code to crash if multiple processes were connecting to it at the same time using encrypted connections. This update removes the race condition in openldap, and programs using the library no longer crash on multiple concurrent encrypted connections.Scientific LinuxScientific Linux 7openldap-devel-2.4.40-9.el7_2.i686.rpmc0ab0433382b7339485a21295369a1798f15d2999a932d2c3a431e52f986cad6openldap-devel-2.4.40-9.el7_2.x86_64.rpm9ca205cee05a2834322231fa2099e53ffd84b5c4e47893364eaa6cdc8727585dopenldap-2.4.40-9.el7_2.i686.rpmea28149acab5e763255fa61fbf9e15429fb80d43f63f519f05245cbf34851170openldap-servers-sql-2.4.40-9.el7_2.x86_64.rpmb08eda6c681a5a44b6307ca647473aedd9ff7a3b1e748ab9ca19f9653470dae5openldap-clients-2.4.40-9.el7_2.x86_64.rpmce89e36230e83d8500fa0eb3c5fc06fef76005163d6710998409f52a16048d3aopenldap-servers-2.4.40-9.el7_2.x86_64.rpm163d30d77c4756430e5588e0cf97ccb00f8eecffebe411c6caefc1054559dfaaopenldap-2.4.40-9.el7_2.x86_64.rpm67b37f63c17e3bc494e2add737d4c3de94751dd6d4317086cf6ee1143902cfecSLBA-2016:0533-1This update fixes the following bugs: * Previously, the libblkid library did not provide the XFS log signature offset. As a consequence, the wipefs command and LVM tools failed to erase XFS log from block devices. A patch has been applied to fix this bug, and XFS log can now be removed as expected. * Previously, running the lslogins command terminated with a segmentation fault when executed with a non-existing user name or on the IBM Power Systems architecture. A patch has been applied to fix this bug, and lslogins no longer fails in the described situation.Scientific LinuxScientific Linux 7libuuid-2.23.2-26.el7_2.2.i686.rpm002b7d40b9422151fbe89ac7303236c00d08f8ee2c407085fead75802fd565b3util-linux-2.23.2-26.el7_2.2.i686.rpm8928bbc21d9de5378368960bd56361902497b141458840e441050144272a19fclibuuid-devel-2.23.2-26.el7_2.2.x86_64.rpmeb1c884eff837d355734301c9294050bd3e81241296079b494225d3d12e05ccclibblkid-2.23.2-26.el7_2.2.i686.rpmb39e6b52a7445bf82b00a3aceaa7b3dacd0fc8ce3fd4e6035f8ea90793005270libmount-devel-2.23.2-26.el7_2.2.x86_64.rpmcff9111775d199f22ae8c9cd41a5ee5b76e7bc4679cddb871b2c7e292969496alibblkid-devel-2.23.2-26.el7_2.2.i686.rpm5e6cd6b6f3c283053ba0f2a35daf73256fdc9eba906ec7c2589803cc044da198uuidd-2.23.2-26.el7_2.2.x86_64.rpm6bb09d69de9ac233b7a1c531b333282de20dc653ea12de05dd9639b29a6d45d6libuuid-2.23.2-26.el7_2.2.x86_64.rpmedd15bb22372d15ecb6d29fecfd0150bb66583dcaa872d9ed75759766836a89butil-linux-2.23.2-26.el7_2.2.x86_64.rpm0a2504d72112be2774e6ac6e9b4d92ce320c49cf5f7fe31127fa9b8a0eddd90flibmount-devel-2.23.2-26.el7_2.2.i686.rpm747b7ec31b543dcd2aff56ebfb88689f251c3e844ce10632ae9c1f35201a3379libblkid-devel-2.23.2-26.el7_2.2.x86_64.rpmc01e009c71aeca096deb12c013af50873ca250e44636b5d8d1daecda4e0a6a59libmount-2.23.2-26.el7_2.2.i686.rpm313e0f22d787ef023f0079d2685ee991f30d32d94ace391e1a10312a816b3ff4libmount-2.23.2-26.el7_2.2.x86_64.rpm6c623e0340de36aea036affdcc6a9d66f64c54d643627e612571f53b2c21475flibblkid-2.23.2-26.el7_2.2.x86_64.rpma83f50ab33a68c92056c517262dd4d006eb61ef14d0497c0d91264d2e7a3f465libuuid-devel-2.23.2-26.el7_2.2.i686.rpm5c6e11bdebe33f26cb1f474a68587dd28ffd94310367f5c64a3ad6080abad4ddSLBA-2016:0535-1This update fixes the following bug: * The temporary files created by the "crontab -" command were misdetected by the crond service, which incorrectly considered them regular cron job files. Consequently, crond performed unnecessary searches for false user names and reported user lookup failures to the system log. The cron utility is now fixed to use temporary files' names that are ignored by crond as expected, thus fixing this bug.Scientific LinuxScientific Linux 7cronie-anacron-1.4.11-14.el7_2.1.x86_64.rpmf9fa04eac8f65fc77c8955ba4d54d573c9bc3a2063289d4fd1c01c790af28c84cronie-noanacron-1.4.11-14.el7_2.1.x86_64.rpmb66e36fa30880cb0bd8009b18b99a211eb76dbbe8e9707ce9b14f53ad4bf97b5cronie-1.4.11-14.el7_2.1.x86_64.rpmfe04ea126a41cab7677c36585a0a7efb876c92b1a37d9f00bbdbacf93761c1b9SLBA-2016:0541-1This update fixes the following bug: * Due to a bug, when the wdmd service attempted to restart, it disabled the watchdog device on the system, which prevented the watchdog from resetting the system if the wdmd service failed before. With this update, vdmd no longer fails to start in the described situation.Scientific LinuxScientific Linux 7sanlock-python-3.2.4-2.el7_2.x86_64.rpmf8f739908dd3634ffff77642b560a92f13728d9d90621f41b624c5cb374ad3d0sanlock-devel-3.2.4-2.el7_2.x86_64.rpm2037631d49e8af2c8324f185ad5ea0cef98fd592b3f363395950d7805c5557basanlock-3.2.4-2.el7_2.x86_64.rpm3fef958e2bd4f4fe7f259c2f5526fa2eeb004c3dc6bb043d874d88672ed7decasanlock-lib-3.2.4-2.el7_2.x86_64.rpma293c7f8bae0fc741c52ab75e1df1c336bd7a790525bd9b1843c4f9bd40ebb0ffence-sanlock-3.2.4-2.el7_2.x86_64.rpm6bf17e76b651fd6a88ff5d2500611e83ba24703f90b6663290fa6050aa6a7164sanlk-reset-3.2.4-2.el7_2.x86_64.rpm5673299944b4e547680f82ee4d2cacc56f04c9bc8d64c3f49f5bef425afaa718SLBA-2016:0542-1This update fixes the following bug: * When building a package using the %kde_runtime_requires macro from the macros.kdelibs4 file, the required version of kde-runtime was higher than the version of kde-runtime available in Scientific Linux 7. This update sets the required version of kde-runtime to the latest available in Scientific Linux 7, and %kde_runtime_requires can now be used safely in spec files to have a dependency on kde-runtime. The desktop must be restarted (log out, then log back in) for this update to take effect.Scientific LinuxtruetrueScientific Linux 7kdelibs-ktexteditor-4.14.8-5.el7_2.x86_64.rpmb2cbb5a978c61f2ad3657cb508130e7febda0ee30efe65a81bb1e1d6fa12d278kdelibs-ktexteditor-4.14.8-5.el7_2.i686.rpmd646090295ceb2b4b6eff4b417b3d89be7810eafb156815cbe96622cb17947f4kdelibs-apidocs-4.14.8-5.el7_2.noarch.rpm722d837905481a94d0e4a938c0351e4d3dfa56c35a3d27d11ff82af7afce2e14kdelibs-4.14.8-5.el7_2.i686.rpm2caa6ca10e34f5784bc85559b215ec071ecb9c37c0dc344ea33769c8ff05f5e3kdelibs-4.14.8-5.el7_2.x86_64.rpm17df4d45df37d8f463699fad726236b098cdd9d3018ec80e80dbbfa66a6e6847kdelibs-devel-4.14.8-5.el7_2.i686.rpm8b9c8fe5998fbfcce489b4cd5254c5aee0687b3ee472942bfb1587c8b4c67d32kdelibs-devel-4.14.8-5.el7_2.x86_64.rpm7979d7758394e161f8eda612246ecb1347b332841cc1e0ab39157408da0249e8kdelibs-common-4.14.8-5.el7_2.x86_64.rpmbef128dc92cb63ebfebe5d386a8d3ec7df33495b6358668c57252b22626cd35bSLBA-2016:0543-1This update fixes the following bug: * Prior to this update, using the "-inetd" option caused the tigervnc tool to terminate unexpectedly. A patch has been applied to fix this bug, and tigervnc no longer crashes in the described situation.Scientific LinuxScientific Linux 7tigervnc-server-1.3.1-4.el7_2.x86_64.rpm2b67cad88848534992e678c39a99d60b66f52067a1c7131d2487ac278e23a02ftigervnc-server-applet-1.3.1-4.el7_2.noarch.rpmeea9c2df5e0dbcd9f97de561a790ce48958b62e7c7c11bbf2685edf4d447c555tigervnc-server-minimal-1.3.1-4.el7_2.x86_64.rpm957967492688163166dccbaa28beec26d95a51c6fa776eefd5e219de408bf427tigervnc-server-module-1.3.1-4.el7_2.x86_64.rpmc4180ece84bca5e3db474ed1611e08636ada6c3ccd8a5e78b1e70a7f7d88fd5btigervnc-license-1.3.1-4.el7_2.noarch.rpm4ad6ac76bfbde8ab4d9d41d115458586f4b030cdcf41ffed3f71794d48957a36tigervnc-icons-1.3.1-4.el7_2.noarch.rpm7d9cebc8382d02c44d11a73c4c6a356d7d1f45af0cbf664939c6013bc7ce273etigervnc-1.3.1-4.el7_2.x86_64.rpmd3efdce65dd775befa678cd9999f645ac6b27a0b2afaeea09f89da7e5d8c6effSLBA-2016:0544-1This update fixes the following bug: * Previously, switching ports at some enabled switches with Virtual Chassis Port (VCP) led to a failure with the "misconfiguration on client" message returned. With this update, the libteam packages have been patched to fix a bug in sending multiple LACP packets at the start of establishing a logical channel. Now, the LACP device is enabled as expected, and the aforementioned error message is no longer returned.Scientific LinuxScientific Linux 7python-libteam-1.17-6.el7_2.x86_64.rpm1d73e4daa9f08da59f2ff3e3ff611deab97fc03e65b8c6de764a7f2ae549534flibteam-1.17-6.el7_2.i686.rpmdda02f5ee32a9ca77b24a9859b77ea91e538ba3bc09521776ef1be7f37464941teamd-1.17-6.el7_2.i686.rpmadcfdd7d2a1361348a6e50f9ce8c4db3915ab3f036d293924ae1f7bf0d810d63libteam-devel-1.17-6.el7_2.x86_64.rpm091c496c616ad427bb4f015c4b069270591c76ad7cb7071e83bfebac4ad50218libteam-doc-1.17-6.el7_2.x86_64.rpm25058c0688efbb0779e48734b4abdf803101564827816757057159ccfbe884a6libteam-1.17-6.el7_2.x86_64.rpm96e28b679a4ca94b5837dbfbb6fd83c45a06428caef69c8cc8822861d329d69ateamd-1.17-6.el7_2.x86_64.rpm098da981318fd5d615f0407a3b476f43bdfa2d0f4fe85f3163de7f6def42e454teamd-devel-1.17-6.el7_2.x86_64.rpmd22be5b6b280647dfe235dd5d1a9a2f53d6cc2c50126779c4b3a823c48e1b0f5libteam-devel-1.17-6.el7_2.i686.rpm53117ce04e11c3b0d77667b83e624593e81ecf52c83c28c15938f121ec6699b8teamd-devel-1.17-6.el7_2.i686.rpmde7407d485cefaef4e699ff391cd3a8e560488da5e09ca1eb87530e7dfbf3902SLBA-2016:0545-1This update fixes the following bug: * Due to a bug, if the tuned-adm command was issued while the tuned service was not running, an attempt to automatically restart the tuned service failed with a traceback. The underlying source code has been patched to handle automatic restarting of the daemon correctly. As a result, restarting the tuned service no longer fails in the described situation.Scientific LinuxScientific Linux 7tuned-profiles-compat-2.5.1-4.el7_2.3.noarch.rpmca4785be6a76695a1c6d6231cfeeb191f05a1ea4815c1fbcb14c82930cc4e5b5tuned-profiles-nfv-2.5.1-4.el7_2.3.noarch.rpm83eff710f3d7bae46cd26f432129f2046bb82e74f62d3b961bce9cd49455207atuned-profiles-atomic-2.5.1-4.el7_2.3.noarch.rpm10d26820a74f6d64578704cbc305399a5e2c506596d3cb18dfa39f5b582d196ctuned-2.5.1-4.el7_2.3.noarch.rpm4dbfda704df14429265cc4b4a8a60691c89ea186b221486da4693f697292558atuned-utils-2.5.1-4.el7_2.3.noarch.rpmdfc8de729d1a0f7f0449ed8b250d613d65331da7a97da4efcfafdf18d9b521bdtuned-utils-systemtap-2.5.1-4.el7_2.3.noarch.rpmb51b38e80d191dc29ce1d2449a93978525f162df75a70f257ecf004d01357175tuned-profiles-realtime-2.5.1-4.el7_2.3.noarch.rpmf145c9d3355f28f14269d4f4d343c443cde286e545e72250354a3563446583d8tuned-gtk-2.5.1-4.el7_2.3.noarch.rpm9ea434fc5597df65e2078c0c0c0c94fd92840b015ea5161499dd19f6cae0d681tuned-profiles-oracle-2.5.1-4.el7_2.3.noarch.rpm0ad6c67d7f51a121634cf5deb08e0559f259bd5e07ce049331db855e8ed068b0SLBA-2016:0546-1This update fixes the following bug: * When converting some .exr files by ImageMagick, the process previously failed, which led to an unexpected termination of ImageMagick. This update reverts the changes in the code causing this bug, and converting .exr files now proceeds successfully.Scientific LinuxScientific Linux 7ImageMagick-c++-6.7.8.9-12.el7_2.x86_64.rpmd26089f1d5a999f1e718b97d78dbae22c49353513e3c0339e7cc8200800cdea3ImageMagick-devel-6.7.8.9-12.el7_2.i686.rpm15b7d31378f91acfb24af6f076927b09aa60bf32ddccdeb0e06e92084e3e0dc6ImageMagick-perl-6.7.8.9-12.el7_2.x86_64.rpm26f04e9ab78ea53783dfa11b58c5392a7b49a2c530f7e6a28b2ccf5774dc5e47ImageMagick-doc-6.7.8.9-12.el7_2.x86_64.rpmad5f259a88fb2eedb32cb28399ce1949aa0e629907e0dc2c2d7ef911c6df5283ImageMagick-c++-devel-6.7.8.9-12.el7_2.i686.rpm0eb4cc8438dfd626b80a560756086917d6568d2673cf543dd06187a26f434cb6ImageMagick-6.7.8.9-12.el7_2.x86_64.rpm0748dc703cc04511b8d60d845d79c6f8ec1b34eb2bb01b18d8295d60eb87bd39ImageMagick-devel-6.7.8.9-12.el7_2.x86_64.rpm880ab1e52740791bda27f6d94b0a4264ed5658b77b00464c32ae0956e2a1df24ImageMagick-c++-6.7.8.9-12.el7_2.i686.rpma1e3b0477af682ed2eb6f33dddf23305dad05921ea6af6d4afea818024a7ba5eImageMagick-6.7.8.9-12.el7_2.i686.rpm2ec1c6449ec0a69e4c69d8d4b2e67c0dba0ba2594825a0688702c8a07967ff1dImageMagick-c++-devel-6.7.8.9-12.el7_2.x86_64.rpm3c385a62d4dc36d593be7bc734dcf0e1a73fc061e39d7e6d5517ecbf3664a785SLBA-2016:0547-1This update fixes the following bugs: * Due to invalid handling of BSSID (basic service set identification) of an access point, NetworkManager could previously encounter an assertion. As a consequence, NetworkManager terminated unexpectedly. A patch has been provided to fix this bug, and NetworkManager now works as expected. * NetworkManager could previously fail the automatic activation of certain types of virtual Ethernet devices because the activation was started before the interface had a valid MAC address. This bug has been fixed, and NetworkManager now waits for a valid MAC address before proceeding.Scientific LinuxScientific Linux 7NetworkManager-devel-1.0.6-29.el7_2.x86_64.rpm8bf4bf50730c8d645fa85d0692cc8be5889f0d01047c3bb6fb64386b230d3d57NetworkManager-libnm-devel-1.0.6-29.el7_2.i686.rpm3405ac3397b2ba627106c7d199c493d3830e876998fea6722be9c2e63acf22ddNetworkManager-libnm-devel-1.0.6-29.el7_2.x86_64.rpm6268a163187fe32fef42476c5f6e7b48187b0dff1f4d6a53dd1726714bb40f53NetworkManager-devel-1.0.6-29.el7_2.i686.rpmc5a20b5d03efbfda8f3ed59f3c1ab9f72adbf7c80bec9b8bdc9404ef95e5637aNetworkManager-libnm-1.0.6-29.el7_2.x86_64.rpm183a3002ddd8c2cb068d68d2abe54a3234430633f2e2688ce42f0069f08567dfNetworkManager-libnm-1.0.6-29.el7_2.i686.rpm8f43fe2d5e5a92eea6fb8207b50ca7d16301ef0ae5b207ce020d23fe504525adNetworkManager-tui-1.0.6-29.el7_2.x86_64.rpma82f2da8b1b9cee61ec6e32ca5f896ccc6a47d17f0e4293c60c01719d4690e9bNetworkManager-glib-1.0.6-29.el7_2.i686.rpm972a39ee9c737b6956af52a05fddb5a1450ec92d5939224c09f2f9cc13989273NetworkManager-glib-devel-1.0.6-29.el7_2.i686.rpmfd83994bddee586813bc7a7cfac6818dfd4d9d48a1a7d22539d845bcc2bc7ad4NetworkManager-glib-1.0.6-29.el7_2.x86_64.rpmf59a3eaa7d76cdf605bb99f00df02b596c23c17a99219bd39a38e253154ef679NetworkManager-wwan-1.0.6-29.el7_2.x86_64.rpm66b6c0a3131839e7b9af3dc9abbedd65a41a936ed7ac89f112156b9659954e5fNetworkManager-config-routing-rules-1.0.6-29.el7_2.x86_64.rpm45582dbe8829eed647c27fe609815a840cb818c79775ec6286e21afbc2abad87NetworkManager-adsl-1.0.6-29.el7_2.x86_64.rpm5b55420f59cc6fc9509e9f0dd6ba1b16811ab8b4194a05c515de3da67278cefcNetworkManager-wifi-1.0.6-29.el7_2.x86_64.rpm5ffe1a7b2ae1e2b19cb71e76ab94e030c0a7417a9054d31e079d5f7a74dc0462NetworkManager-1.0.6-29.el7_2.i686.rpmaa748c77ba71f80f79e469f040e418aa78b2666814b7628dee29bf597eda00c1NetworkManager-bluetooth-1.0.6-29.el7_2.x86_64.rpm4d668feaa65e0eda2911c332fffd6babcad9c54c296816e3a4209ae48ae0504fNetworkManager-1.0.6-29.el7_2.x86_64.rpm0a6fe17a06bfa54e6e7c934ecf6fd0daa46bb3ee95f937778c79746b6f8ad5eeNetworkManager-glib-devel-1.0.6-29.el7_2.x86_64.rpmdc0b8f189b2c30f52efcdaa248ec310d7b4a165cc4a962e000800545c212768dNetworkManager-team-1.0.6-29.el7_2.x86_64.rpmfd3154338ad0ce95f010d99a2398764d7ce8a480e05bd14a02fd83774de9dccdNetworkManager-config-server-1.0.6-29.el7_2.x86_64.rpmedde4c361378fc436d4886143b3382e2c67142f90391e41e8e8e31581544952dSLBA-2016:0548-1This update fixes the following bug: * Due to a bug, the "closefrom_override" sudo option did not work correctly. With this update, "closefrom_override", as expected, overrides the default starting point at which sudo begins closing open file descriptors.Scientific LinuxScientific Linux 7sudo-devel-1.8.6p7-17.el7_2.x86_64.rpm8c3219c9dfea7d363f6acab7e540951e324b807abacc2c11384e62e59661018bsudo-devel-1.8.6p7-17.el7_2.i686.rpmb602705189933fdac9e377e0370f7873e2686096fc9258a26513221b198e0535sudo-1.8.6p7-17.el7_2.x86_64.rpmc7aa9c5a3dd35208b0b66a507ae32469a93ff7bebe41cad5748bc1d11dc8a46fSLBA-2016:0550-1This update fixes the following bugs: * Previously, a keep alive entry was being created at too many opportunities during replication, potentially causing a race condition when adding the entry to the replica changelog and resulting in operations being dropped from the replication. With this update, unnecessary keep alive entry creation has been eliminated, and missing replication no longer occurs. * When a persistent search (psearch) was launched by a bind user without sufficient permissions, the access permissions object in cache previously failed to reset to point the initial pblock structure to the permanent structure. As a consequence, the ACL plug-in could crash the server due to a missing pblock object. This update ensures that the initial pblock object is reset to the permanent pblock and prevents the server from crashing in this situation. * Keep alive entries are used to prevent skipped updates from being evaluated several times in a fractional replication. If a large number of updates is skipped, these entries can be updated very frequently. Before the keep alive entries are updated, it is tested that they exist. Previously, the test was being logged at a "Fatal" log level, so it was always logged no matter which log level had been set. As a consequence, error logs were filled with unnecessary messages. With this update, the log level for keep alive entry creation has been changed from "Fatal" to "Replication debugging" (8192), and the error log file is no longer filled with "Fatal" messages. * The LICENSE file contains the correct license information, which is GPLv3+. Previously, the output of the "rpm -qi 389-ds-base" command displayed an incorrect License field with an earlier license, GPLv2 with exceptions. The License field in RPM now contains the correct information. After installing this update, the 389 server service will be restarted automatically.Scientific LinuxScientific Linux 7389-ds-base-1.3.4.0-29.el7_2.x86_64.rpm41a7785f618f3f1748f686fb7a8d28c5dd6f8ebc7e4fc7d53f2e80f3e2014f60389-ds-base-devel-1.3.4.0-29.el7_2.x86_64.rpm67d91e7017b3e7c23fec59ab36d75dbbe5fdf263af0cd16496ab912a785d3fcb389-ds-base-libs-1.3.4.0-29.el7_2.x86_64.rpm7e50219b6791da0f4e3e332f949edd7c3dc50e0683246306d662153ef2e553f3SLBA-2016:0551-1This update fixes the following bugs: * Previously, the iscsi-initiator became unresponsive intermittently due to be2iscsi driver errors. This update assures data transfer on the iSCSI connection works as expected. * After a USB device removal, a problem in synchronization occurred, which could lead to a race condition. This update makes sure the timer is initialized early enough, thus fixing this bug. * Due to races and duplicate frees in dst_release() and ipv4_dst_destroy() functions, a kernel panic could previously occur. The provided set of patches fixes the aforementioned races and duplicate frees, and the kernel no longer panics. * Previously, as more kernel network namespaces were created, the average CPU load was increasing too fast. As a consequence, the system performance dropped significantly. This change moves accesses to nsproxy under task_lock protection, thus removing the need for the very costly synchronize_rcu call. * TCP resets previously did not honor the SO_BINDTODEVICE option even if the socket was still available. This update makes sure the outdevice ifindex is set and TCP resets are thus sent via the interface specified with SO_BINDTODEVICE. * Previously, if a receiving system had two IPv6 multicast addresses bound to the same UDP port, incoming traffic was only delivered to the most recently-started listener. This bug has been fixed, and both receivers now receive, as they are on different IPv6 mcast addresses. * In the hpsa driver, non-zero LUNs of multi-lun devices could no longer be presented via SAS-based SmartArray. The hpsa driver has been patched to address this bug. * Under heavy TCP stream test using mlx4_en, the mlx4_en_recover_from_oom() function could be invoked and could cause a BUG_ON assert to occur. As a consequence, the operating system crashed. The provided patch fixes this bug, and the system no longer crashes in the aforementioned situation. * Previously, the discard operation for thin volumes was not enabled and it was thus impossible to free the space unused by the file system. In addition, mounting the file system with the discard option had no effect, and the fstrim utility returned an error. The provided set of patches fixes this bug, and fstrim now works as expected. * Previously, the veth interface was replacing CHECKSUM_NONE with CHECKSUM_UNNECESSARY, which caused corrupt packets routed from hardware to a veth device to be delivered to the application. Consequently, some applications received corrupted data, because the network stack did not verify the packet's checksum. This update makes sure the checksum is verified, thus preventing this bug. In addition, this update adds the following enhancements: * With this update, new device IDs for the iwlwifi driver have been added, making sure iwlwifi modules are loaded properly when the system detects wifi devices with new IDs. * This update incorporates the fw_ldst_cmd structure change for new firmware and also updates version string of the cxgb4 driver. The system must be rebooted for this update to take effect.Scientific LinuxtrueScientific Linux 7kernel-doc-3.10.0-327.13.1.el7.noarch.rpm6cbd1e4b5bd1efaf4f1b6483a81a3ebb3c3bdb72b03a693b8b8cc9e6c99b22c0kernel-3.10.0-327.13.1.el7.x86_64.rpm42795b9273006872af694b8b3bbbc5a198da85d747cf7dd85671e0ff407ff564kernel-headers-3.10.0-327.13.1.el7.x86_64.rpm4eb60b8791cbc36336830067a49b9629d019b79c95042223141ab30adfc03016perf-3.10.0-327.13.1.el7.x86_64.rpm0de475fe2c63c550d08391a28290155b0741bd05f9bda79062ea1abb07e8079fkernel-devel-3.10.0-327.13.1.el7.x86_64.rpmc823fbb910b2018e598488afd879155c4d6082edc163b3cfc3015be926ed27a0python-perf-3.10.0-327.13.1.el7.x86_64.rpm797ff4f306d69d211104c658e0bc594f2478753950e700513bf4521b65f8f2d8kernel-tools-3.10.0-327.13.1.el7.x86_64.rpm4ea8706fb678cfbbb126455dd6bece1ecb5ce9e2a8bdc094f17c6dee5f631a87kernel-tools-libs-devel-3.10.0-327.13.1.el7.x86_64.rpmcb8a319843b0037b2b8e0b0e6f426521ec47bc30836d2fc79c82cf4ff561f6c7kernel-abi-whitelists-3.10.0-327.13.1.el7.noarch.rpme67395ea79163dfc8718e1bf375868afcd992f03859bfdaab19edaffeb656908kernel-debug-devel-3.10.0-327.13.1.el7.x86_64.rpmf0643c45cd07eeec0f104937d185c8826d2c0f1fbd69784f93e9e65b832b8947kernel-debug-3.10.0-327.13.1.el7.x86_64.rpm57e6455b842a80b529ed36d77cc3bc8dbc37b702c705d784abf83c195e17defbkernel-tools-libs-3.10.0-327.13.1.el7.x86_64.rpma3312515267995827b0aac374a37853c263362f7851a17ec056eccedde283928SLBA-2016:0552-1This update fixes the following bug: * Previously, when an Active Directory (AD) user or group was added to an Identity Management (IdM) group using an external IdM group, IdM was unable to resolve the AD user or group before they logged into IdM. With this update, IdM retrieves AD users and groups during group lookups as expected. Additionally, AD members of IdM groups are now successfully resolved. Note that this update allows the slapi-nis Directory Server (DS) plug-in to populate AD group members of IdM groups in the compatibility tree, thus enabling functionality such as group-based sudo rules assignment on legacy clients.Scientific LinuxScientific Linux 7sssd-libwbclient-1.13.0-40.el7_2.2.x86_64.rpm450bc36169b2e771b9cc533be2703c9a41d97c483bb9002369b8b254750d3990libsss_nss_idmap-devel-1.13.0-40.el7_2.2.i686.rpm94abbe2750bbc614a723ce108054bbba3834f5ccb0e3eaec535c1fcff4aef58blibsss_idmap-devel-1.13.0-40.el7_2.2.x86_64.rpm035d749cf359143b602d1a91f7868c0fa589513d3d099510f1cfcd7d016554fdsssd-libwbclient-devel-1.13.0-40.el7_2.2.i686.rpm4a4d8eea04085a34248bb3adc58afb8eb50fe4bae5a7618e22e94f2aaf3d2ba6libsss_idmap-1.13.0-40.el7_2.2.i686.rpm8ccb4bcc8e4bccb50289c553db4e9ee12c76d2d79d7135c2c614de7e28fecca7libipa_hbac-1.13.0-40.el7_2.2.i686.rpm3492ecc5fa9a0295c3e487d44ef1b4dfa1dc72c577281138cb810479fc0d7ad2sssd-ipa-1.13.0-40.el7_2.2.x86_64.rpm532e2a82e12f4efa5bb954ef758c2d6587eb306f8849e674ee73e40fc1045c27python-libsss_nss_idmap-1.13.0-40.el7_2.2.x86_64.rpm5a348187a01695ea5d3390219fcb8f0fe5ee39842eceba8f7790e380bba6a0c1sssd-1.13.0-40.el7_2.2.x86_64.rpme1034d57f21d2d9e96b16ca79119c8da0056a3276ac9c02f8ce648feb6baaab8sssd-common-pac-1.13.0-40.el7_2.2.x86_64.rpm7137e5cad8becabac9a3453178a3fca0f79d971fbe4b6c6646130b24f595ad0clibipa_hbac-devel-1.13.0-40.el7_2.2.i686.rpmacfd19834ac6b67479e091982815b9e7ccea0defe432f8c68d47b1789b4f4e7asssd-ldap-1.13.0-40.el7_2.2.x86_64.rpmd6fb0a7572410e66bc2005fec6eca4798b2dce4078b340de91fd038ed22b9211libsss_nss_idmap-devel-1.13.0-40.el7_2.2.x86_64.rpm811be072feb376de1a14d512a7789500471c9de9f933ceed6d190c58150df312libipa_hbac-1.13.0-40.el7_2.2.x86_64.rpm9217552bb10dcd21265bc05500100348485b096c626d035df80499a8db076a5dpython-sss-murmur-1.13.0-40.el7_2.2.x86_64.rpm19a0823e268b9c21deccb52162325da08db27ff3a0d6befe1a153fa6530999e7libsss_simpleifp-1.13.0-40.el7_2.2.x86_64.rpm2f267a09685be4e0d2447c0fe4ab4e70ce464d82888262053f968145b8516400sssd-common-1.13.0-40.el7_2.2.i686.rpm2709360e876c4f93e57c671b30a35e3b199bc4d6d4349932f6ece72ead7df5a8sssd-dbus-1.13.0-40.el7_2.2.x86_64.rpme66abd149f99f74a04c078234fe73a7b70098f2f24f3eed50bf92a21a4a58e2blibsss_simpleifp-devel-1.13.0-40.el7_2.2.x86_64.rpmb9d2c5dd3fdd3b8d29d11460a916f826cc2b523a1bd105053eeb88f9c7b3e93bsssd-proxy-1.13.0-40.el7_2.2.x86_64.rpmf433202184da9f7b5035a696b1680645b4c18c02603269b6ef5d691b74a19901libsss_idmap-1.13.0-40.el7_2.2.x86_64.rpme67b1d3d5f030fdace66b88fd3564d7a7cfe2683e4d1eb165f67855df30b1b7fsssd-krb5-common-1.13.0-40.el7_2.2.i686.rpm19ee978ff6472ac23f33d4be69123c2a9de8078b9eb994cfbc6500905b5d3222sssd-krb5-1.13.0-40.el7_2.2.x86_64.rpm3715a0d16132c70e4757892fdd6c4e04ec54d766e6d335b5a0979b1ad332d6d8sssd-krb5-common-1.13.0-40.el7_2.2.x86_64.rpmb6f185ee1d069aab3df919030b88e78257767f06f21fb8db927fd13b663ffeb4libsss_idmap-devel-1.13.0-40.el7_2.2.i686.rpmc7e10ee94bec07b9869946abcc918c8fcdcc1d596a2941cf4eb92005e22430d4libsss_nss_idmap-1.13.0-40.el7_2.2.x86_64.rpm3fb5097db193d0fb34d8fab5da712fd0c6904ecde1da04239ccf480bb25013b4libsss_simpleifp-1.13.0-40.el7_2.2.i686.rpm2f3836618d0c34e48d8f676ced74d0b8ef1836d264b6e58f0d6101e18b15ef7bpython-sss-1.13.0-40.el7_2.2.x86_64.rpmdb4d0565d7ab461a940f6df50a6f6db9a074b2598710cb60174165aed70a6e17python-sssdconfig-1.13.0-40.el7_2.2.noarch.rpm2d48d251bb53606424200bf5aa9e409e2ce3b052b945d2b95a494b9927cc3a57sssd-tools-1.13.0-40.el7_2.2.x86_64.rpmae2b85007fdbecbb22c9bfce155cb39763e25f0a9bccda105eb05c7ca5f35ed1sssd-libwbclient-devel-1.13.0-40.el7_2.2.x86_64.rpma58c9c8b8c7e458dfd5c74cd111d6944d5d6e11fa03436595e68273b5650a1ffsssd-client-1.13.0-40.el7_2.2.x86_64.rpme75be59dd27b59668e89d7eb6013ffea908ab1b70d0c2188c69025356350246dlibsss_simpleifp-devel-1.13.0-40.el7_2.2.i686.rpm4217dca351cfb85e8eb551129d082602de64ca537a6116ba37e686e2afd12d11libipa_hbac-devel-1.13.0-40.el7_2.2.x86_64.rpmc59d5cfc990502b117c79440d9392f3b835254239ca5ff184b81be420ab1dd9dsssd-client-1.13.0-40.el7_2.2.i686.rpm6404c2574770f54d3f187452e774354487bf3607f0e2d0d6bde647f32de425eepython-libipa_hbac-1.13.0-40.el7_2.2.x86_64.rpm06ff47222f6135ba985a69b5a799e73ef6c8fa42e1d9e3347e564ec0789f0293sssd-ad-1.13.0-40.el7_2.2.x86_64.rpmfba514caffb1f2f07da85526aa54ecd50633e08ab0150102bfe3ecefcdfbf7c6libsss_nss_idmap-1.13.0-40.el7_2.2.i686.rpma8287775dfc950dd777cc03208440890af022ff753bc7fcd9f9b7f90cb6478d1sssd-common-1.13.0-40.el7_2.2.x86_64.rpmc4a069f5ae69ffc88aebd0a07d4b13422e72a2553fb2a4ba8cf0d40f295d2ec9sssd-libwbclient-1.13.0-40.el7_2.2.i686.rpm993a469d6397bcc3747e707c5f046e780311a9c7c213db0dbcc946f3164ecd21SLBA-2016:0553-1This update fixes the following bug: * Previously, the vsftpd service did not handle the question mark character "?" correctly when used in file names. As a result, the service sent incorrect responses to clients using question marks in this way. This has been fixed and vsftpd now responds correctly in this situation. The vsftpd daemon must be restarted for this update to take effect.Scientific LinuxtrueScientific Linux 7vsftpd-3.0.2-11.el7_2.x86_64.rpm1dbc4bc9ec48e0ffa17da48a8ee7f6a5fcb8b852ad793505c384c46c0072e6e8vsftpd-sysvinit-3.0.2-11.el7_2.x86_64.rpm2f2a4d4af187a9b814cc1cb2df8ae3a9fadeb9674ebf2a0ffa5d53dc0ef0eeadSLBA-2016:0555-1This update fixes the following bug: * In a prior update, systemd introduced strict requirements for machine names. As an unintended effect, this caused starting virtual domains with non-ASCII characters in their name or with a long name to fail. With this update, libvirt introduces an escaping mechanism that allows such virtual machines to start as expected. In addition, this update adds the following enhancement: * The virt-v2v utility now processes the "<vmware:datacenterpath>" tag, newly added to the domain XML file by the libvirt library, and maps the paths to the disk image on a VMware vCenter server. This feature enables accessing disk images on the VMware vCenter server without the need for the "--dcpath" command-line option. After installing the updated packages, libvirtd will be restarted automatically.Scientific LinuxScientific Linux 7libvirt-daemon-config-network-1.2.17-13.el7_2.4.x86_64.rpm8d31dfe2812de202f6d7462500fc40ab60ff09c6dca87568cddc4f60beabd192libvirt-devel-1.2.17-13.el7_2.4.i686.rpm0c7ead28acc20f86d17d6418bdc3eb34dda26d2c67006dd66c39d1df6cb786e5libvirt-daemon-kvm-1.2.17-13.el7_2.4.x86_64.rpm88f987ab668d622082ca7cbfac18959ce163fec5c5b6d6cbfd7cabde0047b48clibvirt-daemon-driver-lxc-1.2.17-13.el7_2.4.x86_64.rpm85b230ea62304285e273d90b1f68078a9a676f4e51fdf76d087afcd323fbebablibvirt-client-1.2.17-13.el7_2.4.i686.rpm72432d86e214f95c5c31b99b74549fbd0129a0a31964f9d4d3a823cf1c318d22libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.4.x86_64.rpmf0de8a1f9a7dec42b583bac84f2a3598a329b3bf35802e75aca2b087cd9dc94flibvirt-daemon-driver-network-1.2.17-13.el7_2.4.x86_64.rpma5fc6e57bdc9a9acc53717065b484a2fe3dcd9201f2d7c92d88847af29079238libvirt-daemon-driver-interface-1.2.17-13.el7_2.4.x86_64.rpmbc6cee3a37fd2c0dafa2c570e0cf63b5415c3216688d4ab97522fda47cb95794libvirt-login-shell-1.2.17-13.el7_2.4.x86_64.rpme0d03228c92efa8991535031753a73f2efc56410da7b99245442de72ff87bce5libvirt-1.2.17-13.el7_2.4.x86_64.rpm2c0fbdc66056b1bfa522b38063c643b09fd86d3fabc7dc2c5dad82d9467eed1elibvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.4.x86_64.rpm38b3ffa5a9d82d874132e7bd93b1f780f306216ef73209596787fd446fc60778libvirt-daemon-1.2.17-13.el7_2.4.x86_64.rpm13a67f87c0074de96997264d28719b79b17e3dc7653027ade32b24754c6f29delibvirt-daemon-lxc-1.2.17-13.el7_2.4.x86_64.rpm7f21965536e4c613b7a32d86d9320b3e9b9ec2f561c23db2b448af16f1992064libvirt-docs-1.2.17-13.el7_2.4.x86_64.rpm2d1123ee9c24584a0b09f85ce4a6ad84ab7858c7c2a2eda5f6a89738ca8a6c83libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.4.x86_64.rpm8f5db331ce17fe3f490e851e8029c837fe7182dd657ddb3780d054cb5a813015libvirt-daemon-driver-storage-1.2.17-13.el7_2.4.x86_64.rpm33f438e64e46ac84530aee4e0b0f0816d093a46848fe556727c350bbfab8d2a8libvirt-devel-1.2.17-13.el7_2.4.x86_64.rpm4e2dbe5af836bb60403d49acda6e82090cb7ff0ee6f1e2f053083712bef97126libvirt-client-1.2.17-13.el7_2.4.x86_64.rpm199281179d85715ffb89eaa0572008f0ac84535e78e6920f893ccf928e8870cflibvirt-daemon-driver-qemu-1.2.17-13.el7_2.4.x86_64.rpmfa49b19c24eb314c0bf6cd6c8ec197fb64846bca8cee0efffb4fc8712876e301libvirt-daemon-driver-secret-1.2.17-13.el7_2.4.x86_64.rpm0eb75a4d572d886fdbe758e68cc0161398be30792d4966e353b7340a8f507ec7libvirt-lock-sanlock-1.2.17-13.el7_2.4.x86_64.rpmfbfa51154fd48355815066b960704e21991c11f4215ef4da9636c9d4afe2ca0cSLBA-2016:0556-1This update fixes the following bugs: * Previously, the rabbitmq message broker kept track of members even after they left the cluster. Consequently, after fencing, a rabbitmq-cluster resource instance sometimes was not able to rejoin the rabbitmq cluster. With this update, the "rabbitmqctl forget_cluster_node &lt;node&gt;" action is used when a node is fenced. As a result, the node is removed from cluster and can join again. * Previously, resource-agents deleted too much data on recovery. Consequently, users were lost. With this update, users are backed up on resource-agents stop and restored on start. As a result, the users are available after recovery.Scientific LinuxScientific Linux 7resource-agents-3.9.5-54.el7_2.8.x86_64.rpm451bda78d625e2ab8fba41158b4be1ab82551ffc053220c70fcee8357abd1d07SLBA-2016:0557-1This update fixes the following bug: * After upgrading the nfs-utils packages, the nfs-rquotad.service systemd service was previously unavailable on the system after starting the quota remote procedure call (RPC) service. With this update, the quota packages include a new rpc-rquotad.service systemd service, which allows querying and setting disk quotas over a network. Now, rpc-rquotad.service can be configured in the /etc/sysconfig/rpc-rquotad file. The nfs-rquotad service alias is also provided for compatibility with earlier versions. As a result, the quota RPC service is now available on Scientific Linux 7.Scientific LinuxScientific Linux 7quota-warnquota-4.01-11.el7_2.1.x86_64.rpm224d0c332ac09021a25dc0584ee73b4a86a360db5d3258c9da4b9d92a205959cquota-doc-4.01-11.el7_2.1.noarch.rpm2bf26c549f8d672f8be47a97e7c83a07d22572808a91a89d4b435244e00b9a43quota-nls-4.01-11.el7_2.1.noarch.rpmfe4473ed54dfce181c56a91a38874630c52761e3c05b49bb9e5b3a32a80b4c66quota-4.01-11.el7_2.1.x86_64.rpm1915cc3d22fb786749cbd45f31c2815b1ec75d524b2f7c2dcd0c5531da152fa7quota-devel-4.01-11.el7_2.1.i686.rpmf3a1d5787bec21d7126d8ecb80b01bf282cb56d925384100ae8f42963fb1c270quota-devel-4.01-11.el7_2.1.x86_64.rpme5bc58d6aced6654195edae3d7b43dac6da2e65c70111163162ba65ac9a2b017quota-nld-4.01-11.el7_2.1.x86_64.rpmc1c945538e556baa409431e4817edd45480fdc038ab0709c6db8c6eed59314b1SLBA-2016:0633-1This update fixes the following bug: * Previously, if a Galera node was unexpectedly terminated while a replication process was in progress, the MariaDB database could not be restarted on the node afterwards. With this update, the resource agent passes proper recovery arguments to MariaDB, which ensures that in the described circumstances, MariaDB can restart and synchronize to the Galera cluster as expected.Scientific LinuxScientific Linux 7resource-agents-3.9.5-54.el7_2.9.x86_64.rpmd95fcf800fbcf026d89e11dac4e56d3317da72ce98495648203f95b8312b4502SLBA-2016:0634-1This update fixes the following bug: * Previously, the fence_compute agent searched only for compute instances created by admin users. As a consequence, instances created by non-admin users were not evacuated when a compute instance was turned off. This update makes sure that fence_compute searches for instances run as any user, and compute instances are evacuated to new compute nodes as expected.Scientific LinuxScientific Linux 7fence-agents-common-4.0.11-27.el7_2.7.x86_64.rpm4437c8b054ae5c5f4fbd433702c744e2638f97b43ced2da1b4ec8aa89577c2a3fence-agents-hpblade-4.0.11-27.el7_2.7.x86_64.rpmc581ceb2abdfe515adb75a2cfdb27c551f4b77104ceffff6044ec73f81a6e4eafence-agents-rsb-4.0.11-27.el7_2.7.x86_64.rpm5c15a5ce63553a423764b3618c86cb8700b6e8f2b6156b72cf2b9775c0581755fence-agents-emerson-4.0.11-27.el7_2.7.x86_64.rpm035b85fbf646b291bcafc00d6b80a6fc4d38bd410890ad3cf46f3026cadf6a05fence-agents-brocade-4.0.11-27.el7_2.7.x86_64.rpm90637a80313b0d49e2bfd776c0d0cbf40fb614d4da72ac7654694e6c70ceb058fence-agents-eaton-snmp-4.0.11-27.el7_2.7.x86_64.rpmb5266e7f962debd88a8308ae4473b6cc43430f3eaa511fbb57b8beef3f5ea998fence-agents-cisco-ucs-4.0.11-27.el7_2.7.x86_64.rpm8b374a9a0c08473c9bc7c29b4e2320479eb406fe10236f11fdca7bff6839014dfence-agents-vmware-soap-4.0.11-27.el7_2.7.x86_64.rpmbb5c86cc85a41bff40f4768c45c74150b6965c24bf1e5f097a2425ba752e5c84fence-agents-all-4.0.11-27.el7_2.7.x86_64.rpmb590977da077cc2bf7a8e84dbb9b3756991e76d6a28a2f703a4be3f976881575fence-agents-drac5-4.0.11-27.el7_2.7.x86_64.rpm0c20ff0e10e51021930cb9842fb1eb17b673320e5cc593eda0db0e8f8437117efence-agents-eps-4.0.11-27.el7_2.7.x86_64.rpm6ba2d00144beb526aea234e0615b66ffe52f6aea3530589cee75b91fb889801bfence-agents-compute-4.0.11-27.el7_2.7.x86_64.rpm006f73942bdb6954781d2662abe28464f0d689d807b7922fb9f9a4a808199c26fence-agents-bladecenter-4.0.11-27.el7_2.7.x86_64.rpm1b1740db106d874be27dbb59cb1c39271abaeec5481a2c4d61fb96d5c1807d16fence-agents-mpath-4.0.11-27.el7_2.7.x86_64.rpm6819ce18c08339bdb87697085624ff5cb438b2ee68d9d81ebec73ab72df38af0fence-agents-ifmib-4.0.11-27.el7_2.7.x86_64.rpm572e378d7439492291c1a8f005def575fb4d525f7730868155ca368946d33869fence-agents-rsa-4.0.11-27.el7_2.7.x86_64.rpm2a4b2e651afe4a089bb6c42cc09dd41ed45a3c3f39d09abb24140cc5d7b3450bfence-agents-ipdu-4.0.11-27.el7_2.7.x86_64.rpm00841eae4e91d4b3f5a8100baa27c53c3c2947b29fc27f83870a3170d7e0b780fence-agents-ilo-mp-4.0.11-27.el7_2.7.x86_64.rpm163931a500643b05f308bba8282da64e920607d9465a6889b5f41856ea9581fffence-agents-ipmilan-4.0.11-27.el7_2.7.x86_64.rpmed4acfb45146afc3b994ee2803e7bf6d41a00e1b0fc57d4c6e5ec75b56c26f99fence-agents-cisco-mds-4.0.11-27.el7_2.7.x86_64.rpmd3be5aff07cb9f2d44bc45f8bc086166a8dedaf3eb0d7b9931147af4f55c078dfence-agents-apc-4.0.11-27.el7_2.7.x86_64.rpm0147d4c7eab19e275df5d5290fd15912a1dff312bd62a5e8f4eaa071ba36652efence-agents-ilo2-4.0.11-27.el7_2.7.x86_64.rpm8a6b9c0313d697e944132f4977bc349b370a7d65577a43c7d702cd60673133f4fence-agents-virsh-4.0.11-27.el7_2.7.x86_64.rpm2a8271e2a1eca94c14acbe202d667699d791c1b0480196ebf44a0f662b6fe06ffence-agents-ilo-moonshot-4.0.11-27.el7_2.7.x86_64.rpm6ba56b3487e1ac1bbc765a90c370134d64e480e00e9e569107b67162c2d55f50fence-agents-intelmodular-4.0.11-27.el7_2.7.x86_64.rpme677a2bf5cffd981bf664e724ebba9e3adec55bdcf11d7cec4a19dac65d1a649fence-agents-wti-4.0.11-27.el7_2.7.x86_64.rpmbbc7c0b16d63c68e68c57da320caed9334bac14eb1db13c59f9cea79c47f4bf1fence-agents-kdump-4.0.11-27.el7_2.7.x86_64.rpm68a4ad68c8711b1e28d73f4550fee808fabe4d9c9f5cf72873504e25a1a7d9b1fence-agents-scsi-4.0.11-27.el7_2.7.x86_64.rpme2d55da0f649ec71758c50c794345b25e326814652b537e4ff39e5d4e4343aaefence-agents-ilo-ssh-4.0.11-27.el7_2.7.x86_64.rpm4c11da28c3f82ec94fbe58c6e8dca75b25c85b8441dc9e0ca165f4cc7b15c0d7fence-agents-rhevm-4.0.11-27.el7_2.7.x86_64.rpm609cb7fa8f598fadbd540926f35dd8b501c92671c80bfff14b01805e2030825ffence-agents-ibmblade-4.0.11-27.el7_2.7.x86_64.rpmff7765e5f7f498d1a02dd21fa66e9a076856d6d83674a1809d0ef350ec3f99bafence-agents-apc-snmp-4.0.11-27.el7_2.7.x86_64.rpm0d06c5f8836037f590d920156b3a4aa411666062caec25995910db93e4c3006dSLBA-2016:1026-1This update fixes the following bugs: * In an earlier version, the default value of the ForwardToSyslog parameter was changed and was by default set to "no". Consequently, the rsyslog utility was by default reading data from journal through the imjournal plug-in, in which case forwarding to traditional syslog daemons was not affected. However, if the syslog daemon read messages through the /run/systemd/journal/syslog file, forwarding to traditional syslog daemons was turned off. This update sets the default value of ForwardToSyslog to "yes" to prevent the described behavior from occurring. * Due to a bug in handling errors when compressing journal objects, the journald service could stop working under certain circumstances, and error messages were logged. With this update, compression errors are handled properly. As a result, the described problem no longer occurs, and logs are available as expected.Scientific LinuxtrueScientific Linux 7systemd-sysv-219-19.el7_2.9.x86_64.rpm3953a8937244989c9201d6273d17e1f4202be4e6793adfd1863e6ad5d8dcd46dlibgudev1-devel-219-19.el7_2.9.i686.rpm45cff704cb8d4ede654524a303684affbcc11c3e4ff623e3e67e3fbc8c6238a6systemd-libs-219-19.el7_2.9.i686.rpm5d71fa4b60b24ced530af67a95e91a506fcd520c293b01172ebe511b0954a919systemd-resolved-219-19.el7_2.9.x86_64.rpm273e251a9f14551df47ac9bb9c44d60229078afa3d880d8b5caa0fe39caacab7systemd-devel-219-19.el7_2.9.i686.rpma0e16b568cf12417c4b4bd4c4401d8a1f3973cf2f2135e210d676caea20c4522systemd-devel-219-19.el7_2.9.x86_64.rpm96e03ee7a4eb20e02540021018a6d98e84c9e6aad3991c32deeafcf0c579ed32libgudev1-219-19.el7_2.9.i686.rpm12fe5fb46ee65684e40ebbaa8f25606559801519218c499cf96814e4208401ecsystemd-libs-219-19.el7_2.9.x86_64.rpm777cde2cbc9b897db9f4e9bfbdb37ce1e9f59c97432e63818d5dab2173e9a12bsystemd-journal-gateway-219-19.el7_2.9.x86_64.rpm35bb874087c480d5b4823bcdf2dd9711e4b27a13ae65f9e84671171da31255d9libgudev1-219-19.el7_2.9.x86_64.rpm441e9697ca811999eb875bf974da493434ff4f64ae7fab56c07a66bf1bdbac1dsystemd-219-19.el7_2.9.x86_64.rpmdd0ce660049cc7d29aaaeee231615190ef264c9edcccc8c311c0105f4caa15fbsystemd-networkd-219-19.el7_2.9.x86_64.rpme9d9c4b0afe0528dd6ffeffdcde1dce5d2953948dedeb043a313874c95af1ea0systemd-python-219-19.el7_2.9.x86_64.rpmf7bc699bc9874bb00a1aa939810c39178b4833caaf132cbdfba4f14e64c1b5f9systemd-resolved-219-19.el7_2.9.i686.rpm589f0739eebdeffe30b77f391432af401d265445d04ba14bb5584a3adb451806libgudev1-devel-219-19.el7_2.9.x86_64.rpm32b83fc31cc7b766b8add27362c92ea2be2f1f59fabf065207d56b6be6b0d79eSLBA-2016:1027-1This update fixes the following bug: * Previously, the kpartx tool was by default returning without waiting for devices to be created. As a consequence, the devices did not exist immediately after kpartx returned, which was unexpected. With this update, kpartx by default waits until the devices are created before returning, and the described problem no longer occurs.Scientific LinuxScientific Linux 7device-mapper-multipath-libs-0.4.9-85.el7_2.4.i686.rpm9950ace2f9059430ab7bddacb7d0c35c613830c8eeecdfc20dff951658609943device-mapper-multipath-libs-0.4.9-85.el7_2.4.x86_64.rpmb9a5c5bbaba41cf0dd4ce31cc00bbb69013a6e4b8808bfc6f3e094731c40c51bdevice-mapper-multipath-0.4.9-85.el7_2.4.x86_64.rpmc323eb2b941feaee45e58e6c5dbdf33544f7e26c5087e1eeedaebd1f1773cc02device-mapper-multipath-sysvinit-0.4.9-85.el7_2.4.x86_64.rpm3513a47b28349a2655cd7441f958d9fca924e2e277ac072e2c0a39f4a2cd5351kpartx-0.4.9-85.el7_2.4.x86_64.rpme173705e1d76540c7e7b379fc9c76c2c9be9ffdd6518e1ccc7abc9c5e002a2edSLBA-2016:1028-1This update fixes the following bug: * Due to timing problems, when processing udev events for multipathed Physical Volumes (PVs), lvmetad and LVM commands previously failed to detect the PVs on reboot. This update fixes the aforementioned timing bug, and the system now finds and activates all LVM volume groups while scanning and activating PVs.Scientific LinuxScientific Linux 7device-mapper-libs-1.02.107-5.el7_2.2.x86_64.rpm4eb2343d1277a76c1116d4d1ea84b0c1458c9bc015c9aae21de231ab6ccf7727lvm2-python-libs-2.02.130-5.el7_2.2.x86_64.rpmd067df87ecc2616845f70e7021b0e9b4a90dda2d1a6c165148cc4fa7ce20cf10device-mapper-event-1.02.107-5.el7_2.2.x86_64.rpm68883462b3d8ff34302b9aa877121def3c04f85149a3d6c36a383609e1b42121lvm2-devel-2.02.130-5.el7_2.2.i686.rpmd1f088479c56df19695ddc2453f4c23a2b5c73509dec6e94af8614ab23e49889lvm2-lockd-2.02.130-5.el7_2.2.x86_64.rpm9fc0c9381d1948b006339d9fe1cb602c860ae46290023858068ba0407d516bbalvm2-sysvinit-2.02.130-5.el7_2.2.x86_64.rpma075de116278ef25a5a588b204ce0c5393746e4a16e52c64854abac2612fe25adevice-mapper-event-libs-1.02.107-5.el7_2.2.x86_64.rpmfbbdd7d12b81581ffd7758e8e460101e3082218cd5abbc5fcfbd18a798dab853device-mapper-libs-1.02.107-5.el7_2.2.i686.rpm1a7ca02eb24660853938a8316a937b6e2a68f2ca3b62398eea0f932a8d8f0a9fdevice-mapper-devel-1.02.107-5.el7_2.2.x86_64.rpma54f89704cb6abefc2066508e5220eec31194e7fe71cf0d6d1ca74c20369e385lvm2-libs-2.02.130-5.el7_2.2.x86_64.rpm9064e69360f50179b45047e3f9552d4c1902edafe77105c347a56cbd10d3e288device-mapper-event-devel-1.02.107-5.el7_2.2.x86_64.rpmb16b4fc50d205c3b8392f00ee91795befbac6ec7a03afe7438594cc6019da803lvm2-libs-2.02.130-5.el7_2.2.i686.rpmb9c35f89d55e7a998e29dcba8265c454b712782bf3bae4bf05434145b6179beclvm2-2.02.130-5.el7_2.2.x86_64.rpm7f07855134dc118047ed0ded9aa679995dd18b29a4e0517c230e60ccd4ca1b3edevice-mapper-event-devel-1.02.107-5.el7_2.2.i686.rpm26d9b9b127b20c46dad773c2a83bad628bd11494c76fb87a84698d04422c58d8cmirror-2.02.130-5.el7_2.2.x86_64.rpm99e02f3a765161b8737d7bb104781afff1d5a92f16a30c7215775bf53a8f5f3acmirror-standalone-2.02.130-5.el7_2.2.x86_64.rpm8537060ac26a6c5d69df2cb07162070bd4418f04d36c42ce19b42f256690c7afdevice-mapper-event-libs-1.02.107-5.el7_2.2.i686.rpm7899ee5a982d0514e7fe69d765f1de9c5fc3855752b3402256d752e1531d37d0lvm2-devel-2.02.130-5.el7_2.2.x86_64.rpmee442da77548ce07fbd63d404430819312b21be37987fa1af2c00697d5194fa1lvm2-cluster-2.02.130-5.el7_2.2.x86_64.rpm3b4e8fc3acbf5b4fc1e033e019c82c0ea65e57f394b515f728f3f7fff40c1775device-mapper-devel-1.02.107-5.el7_2.2.i686.rpm9881f085c8aea5be61874e432df1cc3cb14974fda6fa055e32862bcfb0bacb2alvm2-cluster-standalone-2.02.130-5.el7_2.2.x86_64.rpmb7e9079dd676557b393079f57acb0ce898b96933e83606a9632633f0185b6c10device-mapper-1.02.107-5.el7_2.2.x86_64.rpm019ed74214b925674f2b7131941d1c7b246044d9c94ab09759e3744c3cccb49fSLBA-2016:1029-1This update fixes the following bug: * Previously, when chkconfig checked the status of a service handled by the xinetd Internet daemon, it only checked whether xinetd's initscript is enabled. However, because xinetd is now run by the systemd service, the check always reported that every service handled by xinetd was not enabled. With this update, xinetd status in systemd is checked, and chkconfig reports the status of services handled by xinetd correctly.Scientific LinuxScientific Linux 7chkconfig-1.3.61-5.el7_2.1.x86_64.rpm294b48647f174bd2493aa394acb3bd2a2564e105454dbec705611fce91587635ntsysv-1.3.61-5.el7_2.1.x86_64.rpm7a0cdcb941007b9b73af03a259e32af3aefbb50f78587b94dd828b63b1430a2fSLBA-2016:1030-1This update fixes the following bugs: * Previously, certain code paths used by the C library's memory allocator "fastbins" feature, which were enabled by default, were not thread-safe. When the non-safe code paths executed, the code paths could cause corruption in the allocator, which cause the application terminate unexpectedly with a segmentation fault. The thread-unsafe code paths have been made thread-safe, and the described problem no longer occurs. * Previously, when writing content to a file, the do_ftell_wide() function could spend some time on processing data in a file buffer before the write operation took place. As a consequence, a memory leak occurred when do_ftell_wide() was called against a file content in the buffer that was not flushed. A patch has been applied to fix this bug, and memory leaks no longer occur in the described situation. * Prior to this update, if the /etc/resolv.conf file contained addresses that caused the connect system call to fail immediately, queries which triggered the search along the search path caused a segmentation fault to occur. This bug has been fixed, and segmentation faults no longer occur in the described scenario.Scientific LinuxtrueScientific Linux 7glibc-utils-2.17-106.el7_2.6.x86_64.rpmd4ec4b0c5a005b0edd1c0cfc7428b2442aefd2d8773af19dabb9dcc12b5bc54eglibc-2.17-106.el7_2.6.x86_64.rpm5c6a1af6f89f4ebfb0853d5c239c2f596647996894320cfcd49c84ac27c3659fglibc-devel-2.17-106.el7_2.6.i686.rpm2ed6aea7e5e4d372be0bc745d4c83ab6640d7bc4d27e9e19eeae8b730aaaf0a8glibc-2.17-106.el7_2.6.i686.rpm6eb68df3364664c676e088dbac57f8249c46a9e386a56f4cccde605d7434a286nscd-2.17-106.el7_2.6.x86_64.rpm1e9b2ab7bbd48f071c1b32d26c98679a952666ee18b7a9bc0b724168d8d0fc72glibc-headers-2.17-106.el7_2.6.x86_64.rpm06603977add68c834640c9ab412fe59ba26721a081983f68e198e5ad498eaa83glibc-static-2.17-106.el7_2.6.i686.rpmfc78e19d354c6e0eaefe3c9beb7d136c8a3090c9f8ad2858419b86d58b1b7de6glibc-devel-2.17-106.el7_2.6.x86_64.rpm3710e0c1735086fc33050d8ba442391d1e8cd5b630c8e771b513b08dac7077a2glibc-static-2.17-106.el7_2.6.x86_64.rpmabddf8a689f3668ca4e37fcb41de17d2dd5ad70bde62e0003a96755c0ecba1edglibc-common-2.17-106.el7_2.6.x86_64.rpm6e4575d8547757197aed3ed02f87933fe210a680f0bbc249768377a9476315dbSLBA-2016:1031-1This update fixes the following bug: * Due to a bug, the crash utility failed to read excluded pages by default on sadump-related formats. A sadump-specific patch has been applied. As a result, when an excluded page is requested, a zero-filled page is returned, which is the desired behavior.Scientific LinuxScientific Linux 7crash-devel-7.1.2-3.el7_2.1.x86_64.rpm4fef576f07c0cf186442eb96b54ca6839e0cc768740e949b334ab4037b8b93d4crash-devel-7.1.2-3.el7_2.1.i686.rpm91a07156377ccb4a05c5828ab0cc70bd06773c3ede37de30ba9b1914658d240bcrash-7.1.2-3.el7_2.1.x86_64.rpm2db09e705a8c6e23a814f8226fe6afb6d05c763fb1ccfb06dbbcfc4dc371808bSLBA-2016:1035-1This update fixes the following bug: * Previously, when a group member was removed from the System Security Services Daemon (SSSD) internal cache, the SSSD "memberof" plug-in leaked memory. This could cause an increase in memory usage of the sssd_be process. With this update, the memory leak no longer occurs.Scientific LinuxScientific Linux 7sssd-libwbclient-1.13.0-40.el7_2.4.x86_64.rpm9fbdbfbdc844d977ac226d417854a50efc67f82ef1e45ee9d66ea3a3e5d8b5bfsssd-1.13.0-40.el7_2.4.x86_64.rpma98d3a4adde5303b60cbeaaddce38b3f10623939634d5a14f68094ca89a5be45libipa_hbac-devel-1.13.0-40.el7_2.4.i686.rpme7f0c33299120aa535f574081338b6bcaa07efd9d316b505d3958ec3619b9651sssd-dbus-1.13.0-40.el7_2.4.x86_64.rpmcdd5ffba680164d838aed7c4829b83ee99665ff4eebae5dc6d350dc128ac59b9libsss_idmap-1.13.0-40.el7_2.4.x86_64.rpm1e2c4b51e2708681741fef13c69c0d7e2e2152906bebcdc9594ef1cf356b7e69libsss_nss_idmap-1.13.0-40.el7_2.4.x86_64.rpma0bd4cccec27e6631addd1d1027bfdc269799369f8563e5e3ed3764a1a79e7aasssd-ad-1.13.0-40.el7_2.4.x86_64.rpm4e246ce20d666a807c3cedb1e64b2fe20f6ca75809490a9c99a7895708f19f2dsssd-proxy-1.13.0-40.el7_2.4.x86_64.rpm70a45c7246398780c0c3294de89d7fd8acc7b866133b351021cb50363c456f32python-sssdconfig-1.13.0-40.el7_2.4.noarch.rpmbe63110e4ca595c5ba9ee38151504e09a97d47e3aa7af220606a2b486f60f48esssd-common-1.13.0-40.el7_2.4.i686.rpm5514449e76f468992286f10c88ea25545f01d5d448806b37203f28e0c1c0562alibsss_nss_idmap-devel-1.13.0-40.el7_2.4.x86_64.rpm2c16b7ba504ceba12822204380ddd40fb53385dcc6af3e227d1add5b91fd2364libsss_idmap-devel-1.13.0-40.el7_2.4.x86_64.rpme83321e5053df081da9b6c608f7a5e00248f3853e88c01f66c07706d1d2243cepython-libipa_hbac-1.13.0-40.el7_2.4.x86_64.rpm3c57bbb48c37a12a91eecb6527f15b5301346444ab792d2f626746e7bbe86a52sssd-common-1.13.0-40.el7_2.4.x86_64.rpm662c0db5a5755cdb15d50f1a6e0cb3b4263199cac02d3e0b7284263d473fead6libsss_nss_idmap-1.13.0-40.el7_2.4.i686.rpmcd5062fccfe08e04bf55d53551152bab04d4a7ff79f67da605fcbd396d772c46sssd-ipa-1.13.0-40.el7_2.4.x86_64.rpm1585fb3915bbe21958c1388c7984ada488267e20529ae80061cc94ffec1ca446sssd-libwbclient-devel-1.13.0-40.el7_2.4.i686.rpme345b0e9313a36e22bf20d80e796ba2dbabac72b9489405188cc394d978b1315libsss_simpleifp-1.13.0-40.el7_2.4.i686.rpm330ff1ef2bc17349f8f3ca65bbd9a56a52e1ac8c8feb6ca49d52e2ec78ddfd56libsss_nss_idmap-devel-1.13.0-40.el7_2.4.i686.rpmb438d3bd8e78c0a8cbb30af4fb0d1a4f5a57c142139934497b237d2de5a81a26libsss_idmap-1.13.0-40.el7_2.4.i686.rpm5c55729a0b28eb9a6db34f97c499f4e75b131ba67f5126fc6207a80571e6025dlibipa_hbac-1.13.0-40.el7_2.4.i686.rpm2c83d5511d2b1e0814b67fc0d45a44a7e7a921198407542ca93b370bf669ff01sssd-common-pac-1.13.0-40.el7_2.4.x86_64.rpm1cc77b7d1ad2e91f470e8e75e4dcf28409ffc9add4ad79134367b6fd2ae00125sssd-client-1.13.0-40.el7_2.4.i686.rpm47c8d6bf3144d1f4444ae30fa2a8ac52db6fbe05cd1bcfb3242cb5220424aa80sssd-libwbclient-1.13.0-40.el7_2.4.i686.rpm323d04464bdfbeeb61ac20c65ed83aba1eb5bb880a7fd3b9662bb751c71d5f25sssd-krb5-common-1.13.0-40.el7_2.4.x86_64.rpm8f1158bd4e79d450953737d92d8e0feee173427ff7bcc285654a71c356736743python-libsss_nss_idmap-1.13.0-40.el7_2.4.x86_64.rpmcf8798452ec5a2c7643a8e039159832818f932a522ff610d398be34a5b187f79sssd-client-1.13.0-40.el7_2.4.x86_64.rpm27653a2f089be5d5699e30c3f00fc66104c5b862fde6cb0609f0a331447e3d7esssd-tools-1.13.0-40.el7_2.4.x86_64.rpmd393548ec37c7ed1f309ff7a011f58ebf8b43e06eb206d5590ea5b4bfd579287libipa_hbac-1.13.0-40.el7_2.4.x86_64.rpm9d67fb6ff7b6b7135627de68040c1e7a3fcfee558b12ee5aa39ff9a16dc116eflibsss_simpleifp-1.13.0-40.el7_2.4.x86_64.rpm5bf119cb48a81c22a5b64988cdd85fc6498c5086ba58bb9d916942b24d0ea1fflibipa_hbac-devel-1.13.0-40.el7_2.4.x86_64.rpmb86f23ef7bd101282d0ac659791928cec6b111bfa05e34a2d950408c081443c2sssd-ldap-1.13.0-40.el7_2.4.x86_64.rpm228300400438752791c65177e78e1565eb45a26c754ff32cf2e773194563797bsssd-libwbclient-devel-1.13.0-40.el7_2.4.x86_64.rpm867d69314ec1bb43614256e9d170b581409f446e74d070c905b20b2e2c173ebdlibsss_idmap-devel-1.13.0-40.el7_2.4.i686.rpm5521f36efbd84aea2e7773288997a2e4832e2f4ff256f691b7b254dd4303e196libsss_simpleifp-devel-1.13.0-40.el7_2.4.i686.rpm2539fb1c8916117c479495b72453a67943671db2ef5326a26c3ea47c29e08bc7sssd-krb5-common-1.13.0-40.el7_2.4.i686.rpm1d53ab707c418ad560f248f6a6d9b9e929f5ee451d6198a97aaf6209f680222cpython-sss-murmur-1.13.0-40.el7_2.4.x86_64.rpm34c6c02bcf520dda9e712d1f0cd1f635dc2a526fd0a81138503134eb93cc3b85libsss_simpleifp-devel-1.13.0-40.el7_2.4.x86_64.rpm5e386eb298d98c8b8562fb0b59ec7cd78d8b8b4d927e0b957f6c4dba16a35fa9sssd-krb5-1.13.0-40.el7_2.4.x86_64.rpm21dbad33ff1dbf1750c47d60bb8076fe0ef9db8ba42b04fe0318cec7b0421195python-sss-1.13.0-40.el7_2.4.x86_64.rpm7c8dda225d3ad36dab9f1fad70ce63bcb8ba0d8d26c2c27d7d1ea1a9e93fdd68SLBA-2016:1036-1Bug fixes: * The encoding used by Apache Tomcat for the HTTP reason phrase is not compatible with UTF-8 in some locales. IdM attempted to decode certain HTTP reason phrases in non-English locales as UTF-8, which caused the ipa- server-install utility to fail. Now, IdM ignores the HTTP reason phrases, which fixes the bug. * When installing a server with an externally signed CA certificate, the "ipa-server-install --setup-dns" command did not install the integrated DNS services with the server. The command now installs the DNS services as expected in this situation. * The "id [ad_user]" command did not show all IdM groups the AD user belonged to. Now, all IdM groups that an AD user belongs to are added to the Privilege Attribute Certificate (PAC), which fixes this bug. * After the user entered an incorrect old password when resetting the password in the IdM web UI, the password was not changed but IdM did not inform the user about the failure. Now, IdM displays an error message. * The ipa-replica-install and ipa-ca-install utilities failed when installing a replica of a Scientific Linux 6 master with a self-signed CA certificate. This updates fixes the bug. Note that after running ipa-ca- install, you must run the ipa-certupdate utility. Also, it is not possible to install a replica with a CA certificate against a master that uses a third-party certificate for the httpd service. To work around this problem, issue a temporary IdM certificate for httpd on the master before installing the replica: # certutil -d /etc/httpd/alias -L -n [NICKNAME] -r >backup.crt.der # ipa service-mod HTTP/[HOSTNAME] --certificate= # ipa-getcert start- tracking -d /etc/httpd/alias -n [NICKNAME] -p /etc/httpd/alias/pwdfile.txt -C /usr/lib64/ipa/certmonger/restart_httpd # ipa-getcert resubmit -d /etc/httpd/alias -n [NICKNAME] -K HTTP/[HOSTNAME] After installing the replica, revert to the original certificate: # ipa-getcert stop-tracking -d /etc/httpd/alias -n [NICKNAME] # certutil -d /etc/httpd/alias -D -n [NICKNAME] # certutil -d /etc/httpd/alias -A -n [NICKNAME] -t ,, -i backup.crt.der # systemctl restart httpd * During server upgrade, the migration of certificate profiles into the LDAP back end sometimes failed, which left the server without functional certificate profiles. Consequently, certificate requests failed with an error. The LDAP profile migration code has been updated and re-adds any missing profiles to the database at every upgrade. The certificate requests work as expected. * When upgrading an IdM server to version 4.2 or installing the 4.2 version, AD trusts created on the server did not work, even though the server reported the trust status as established and verified. This update fixes the configuration of the sidgen and extdom plug-ins, thus eliminating the problem. If you experienced this problem, recreate all trusts using the ipa trust-add utility. * The Schema Compatibility plug-in did not expose users from a trusted Active Directory (AD) forest as part of IdM groups even if the group membership was defined in IdM. This prevented legacy clients from subjecting AD users to sudo rules and group-restricting access rules. External members of IdM groups are now resolved and their information exported to the plug-in, thus improving compatibility with legacy clients. * Server or replica installation sometimes failed when multiple versions of the same certificate, such as before and after renewal, were available to the installer. The installation no longer fails in this situation.Scientific LinuxScientific Linux 7ipa-server-trust-ad-4.2.0-15.sl7_2.15.x86_64.rpm59126c95b129aea8da9b85a683fa412b71afa061a293b29e94b16a3c56ff9ce9ipa-python-4.2.0-15.sl7_2.15.x86_64.rpmc9d14798f9f5e309c5c1829f2488685e8422641c1f6ef8503eb1e7e7363f557cipa-server-dns-4.2.0-15.sl7_2.15.x86_64.rpm89c18c79cc58550998820fac64c276cd5f96314189d7263ec40def65a4185a11ipa-server-4.2.0-15.sl7_2.15.x86_64.rpm458378115b49bc3cd00b2995119e787e007f564feaecaf7ce77ee53b10098427ipa-client-4.2.0-15.sl7_2.15.x86_64.rpm3d9f142f57e787c67cecf48ccb3718f1eed0f1401a8b36a8f933b445ce83a818ipa-admintools-4.2.0-15.sl7_2.15.x86_64.rpm1af5bd026785663516074a0f98a04b73dfac37c6833dc401aa6877c1a1a91780SLBA-2016:1037-1* Previously, the libtevent package suffered from a memory leak in signal handling. This bug has been fixed and memory leaks no longer occur in libtevent.Scientific LinuxScientific Linux 7libtevent-0.9.26-1.el7_2.1.x86_64.rpm173af8603b67e32b50b19c3154ac22341de6e10a064786428867ab1776db9b02libtevent-devel-0.9.26-1.el7_2.1.i686.rpmf812dcaf800d30d4b0a1ab0f1d8d3fd4bb33f45c5e8aa35ee09305d4a04cf092python-tevent-0.9.26-1.el7_2.1.x86_64.rpmf436029674c36429945fbe9a3efec7c838e255bcac2960bac6c9bead620760calibtevent-devel-0.9.26-1.el7_2.1.x86_64.rpm88839be926df6fd319a9faf3a8571401a6e7015509b21821ce45056ef695bd95libtevent-0.9.26-1.el7_2.1.i686.rpm1fe89a3380037060262596e0749fdbc27b0784cec4e904b85648ec2a9ea9ef7eSLBA-2016:1042-1This update fixes the following bugs: * The certificate validity was calculated incorrectly when a daylight saving time change occurred in the validity period. Consequently, the "ipa-cacert-manage renew" command failed with a validity error. With this update, the CA Validity Default has been modified to use Calendar API, which calculates the certificate validity range consistently with the Validity Constraint and Validity Default. As a result, a CA certificate is successfully renewed in this scenario. * Previously, the PKI server relied on a fixed list of certificates to import from the PKCS #12 file during cloning. If the PKCS #12 file contained third-party CA certificates that were not part of the certificate chain, they were not imported, which caused the installation to fail due to trust problems. The code has been fixed to import all CA certificates in the PKCS #12 file with the proper trust flags before the server is started during installation. This ensures the installation completes successfully in the described scenario. * Previously, installing an IdM replica failed if the password supplied to the ipa-replica-prepare utility included a special symbol, such as the percent sign (%). The problem occurred because the PKI configuration parser unexpectedly interpolated the pki_client_pkcs12_password variable. This update adds pki_client_pkcs12_password to the no_interpolation list. As a result, users can now include special symbols when specifying the password. In addition, this update adds the following enhancements: * The deployment procedure for external CA has been modified to generate the CA Certificate Signing Request (CSR) before starting the server. This allows the same procedure to be used for importing a CA certificate from an existing server. In addition, it is no longer required to keep the server running while waiting to get the CSR signed by an external CA. The "pki ca-cert-request-submit" command now provides options to specify the profile name and the CSR, which is then used to create and populate the request object. As a result, it is no longer necessary to download the request template and insert the CSR manually. A new "pki-server subsystem-cert-export" command exports a system certificate, the CSR, and the key. This command can be used to migrate a system certificate into another instance. The manual pages have been updated to reflect these changes. The installation code for installing an Identity Management (IdM) server with an external CA has been fixed so that IdM can detect whether step 1 of the installation process was completed properly. The code that handles certificate data conversion has been fixed to reformat base-64 data for Privacy Enhanced Mail (PEM) output correctly.Scientific LinuxScientific Linux 7pki-ocsp-10.2.5-10.el7_2.noarch.rpmc37f9eef20b9acd6b4ecaa75c3197082e21395a5c4a3058b01530ec4a561c927pki-symkey-10.2.5-10.el7_2.x86_64.rpm5fd19ccb52eed51eb0755df96f26953f49f300d4e31a1c4d1043f6f6966d2ed4pki-tools-10.2.5-10.el7_2.x86_64.rpm0e9296a4d5073707e0206b5852771433aea38143324fb1c6c11e2816352d1a1bpki-server-10.2.5-10.el7_2.noarch.rpm5f7190606b17d53cddec3186434d040f4952b55f60dbe10fa763440704f2d0abpki-tks-10.2.5-10.el7_2.noarch.rpmdb643403f3aa291cda16de6b6421fb921ff7a4488db65a290415f2d2427594e6pki-kra-10.2.5-10.el7_2.noarch.rpm6295411b66d00a6b50b004857620d9981df98b3feb903ab0944095b233e16b8cpki-javadoc-10.2.5-10.el7_2.noarch.rpm8df3263ed218b6bc94f1f2f7d9a5d038c267d6104b2c1bbc93a2ec4a5e1a6d63pki-ca-10.2.5-10.el7_2.noarch.rpmd16ca978a9e8a38169dd92855f9623ef935e0c83f27ae975b5d992a32b1456c1pki-tps-10.2.5-10.el7_2.x86_64.rpm4bc08ebcb8a8da4cad20dde7e66e303d573b1489c89a01e8ae5b66e92f4adb27pki-base-10.2.5-10.el7_2.noarch.rpmc324a3a484546977e912223ed52527eea52c34200cad00e615e5f874e10e665cSLBA-2016:1043-1This update fixes the following bugs: * Previously, NIS server support in Scientific Linux Identity Management did not properly propagate information about lockout status of a user to NIS clients. This caused users which were locked out by an IdM administrator to still be able to log in via NIS if the NIS shadow map was enabled in addition to the passwd map. With this update, the NIS server is updated to correctly propagate lockout status information to clients, and systems using both NIS passwd and shadow maps correctly deny access to users which are locked out from IdM. * The Schema Compatibility plug-in supports exposing users and groups from trusted Active Directory forests with the help of SSSD running on the IdM master server. Previously, the plug-in did not expose these users as part of IdM groups even if the group membership is defined in IdM, which prevented legacy clients from subjecting Active Directory users to sudo rules and group-restricting access rules. This update enables support for resolving external members of IdM groups and exporting their information to the Schema Compatibility plug-in, improving compatibility with legacy clients. * The Schema Compatibility plug-in supports overriding POSIX attributes of users and groups exposed to legacy clients with ID views. Due to a bug, when a legacy client was binding to a LDAP server using a Distinguished Name (DN) pointing to an overriden user from a non-default ID view, the plug-in was not accepting the DN unless the "uid" attribute was overriden in the ID view as well. For this reason, it was impossible to authenticate to the LDAP server using ID overrides unless the server included an explicit override to the original user ID, which was inconvenient in cases where only a shell or the "uidNumber" or "gidNumber" attributes needed to be overriden. This update provides a fix which allows for detecting situations where the "uid" attribute is not overriden in the ID view and to fall back to the original user name for authentication purposes. Therefore, it is now possible to use customized ID views without creating explicit overrides for the "uid" attribute in Scientific Linux Identity Management for legacy clients.Scientific LinuxScientific Linux 7slapi-nis-0.54-9.el7_2.x86_64.rpm76cbb48ee240a4aac74937c356cf49f1c571b0806f803f21f60d340bba7dcd67SLBA-2016:1044-1This update fixes the following bug: * Previously, a memory leak occurred when the snmpd service was used for monitoring certain network devices. As a consequence, the memory usage of snmpd used continually increased. This bug has been fixed, and snmpd no longer uses more memory than necessary in this situation.Scientific LinuxScientific Linux 7net-snmp-agent-libs-5.7.2-24.el7_2.1.x86_64.rpmf7a74b4d71fd982106044e00d590e401ada5bbf2026e934ba4529a013511ffbcnet-snmp-devel-5.7.2-24.el7_2.1.x86_64.rpm95682fc793a02d45765f5c97abb20a7ddd4f3b17e4ecaefb7bd99cc91704449enet-snmp-utils-5.7.2-24.el7_2.1.x86_64.rpmf2a8dbee648da28b0e7211ca410d7a02f90c63a7a0844551d0a86793d8c558ecnet-snmp-libs-5.7.2-24.el7_2.1.x86_64.rpmedf76f176b9239d3aaa5fb2ab4ec046fe726959835a2d7a0d82da458e8bdb02enet-snmp-python-5.7.2-24.el7_2.1.x86_64.rpmd7c60a62592ca1b779c996e2252b42db10d9125bedc767767411096ffb7b2ab9net-snmp-perl-5.7.2-24.el7_2.1.x86_64.rpm92676047ddb2fd31bc9019be18226dd81593d31e97fa2358d0c4e405b77b1f8cnet-snmp-agent-libs-5.7.2-24.el7_2.1.i686.rpm2171139c4be2544a3c00b83a12de5d45e64438f53e840a0ec4388de0c7cce408net-snmp-sysvinit-5.7.2-24.el7_2.1.x86_64.rpma240c1be92d41fc275a272c27ab9b0da8d1c313619cc719a0e5e2254f270d52anet-snmp-5.7.2-24.el7_2.1.x86_64.rpmf1b7f8a37cbfa87cd699eb6797f0767ac01350a46a7ba48e8b83f46d19b98fd2net-snmp-gui-5.7.2-24.el7_2.1.x86_64.rpm35e49451b8d0f0e7a78bf9470d9fa1eee6d71d13987a2c716d51ad685bc1ae6anet-snmp-libs-5.7.2-24.el7_2.1.i686.rpm4ae5c2c9595dc56f29f21e4a53eb98790ea80a3f2a6f2dfe154a5f4c84fb56d2net-snmp-devel-5.7.2-24.el7_2.1.i686.rpme804d308f7d67e3d2e78e00daa49b17058b98f3de5307f55261a80b7168eea82SLBA-2016:1045-1This update fixes the following bug: * The httpd package installation script tried to create both the "apache" user and group in a single "useradd" command. Consequently, when the "apache" group had already been created on the system, the command failed, and the "apache" user was not created. To fix this bug, the "apache" group is now created by a separate command, and the "apache" user is correctly created during httpd installation even when the "apache" group exists. After installing the updated packages, the httpd daemon will be restarted automatically.Scientific LinuxScientific Linux 7httpd-2.4.6-40.sl7.1.x86_64.rpm9cab9e5de7cb7379d7e240abc5104560db1758690643e081347675d44d95e43dhttpd-tools-2.4.6-40.sl7.1.x86_64.rpmcb26595885a2c6bcaf7eaf850b601bd8537466107e037b0d3065984d2c6efbfdmod_ssl-2.4.6-40.sl7.1.x86_64.rpm19473820d2655ebaca44ce786b2f566cd541868e7ed8094e34d3ff8baa542902mod_session-2.4.6-40.sl7.1.x86_64.rpm914d0f7656620e481bf44b40344e96d3917feb9da82f9daa8e4c177f267d652fmod_proxy_html-2.4.6-40.sl7.1.x86_64.rpm3825796422f132a4190a108ab11cb1e38c55daf5f65434de7c5152feea983ae8httpd-manual-2.4.6-40.sl7.1.noarch.rpm342f46638d40f98f1db42590a58747c23601ccbe72e5f38520bea574333fe594mod_ldap-2.4.6-40.sl7.1.x86_64.rpm9392eb4914fede071d112a0cc92ab4fe77a026ee76987e96b069e9f4939282c3httpd-devel-2.4.6-40.sl7.1.x86_64.rpm037b3c9775e9b6cb941cb05bd7e2d56e34c8d28e82c29f9f97bcd92470eac275SLBA-2016:1046-1This update fixes the following bug: * LVM udev rules do not allow processing a device that is currently suspended, which happens during a reload. Previously, the multipathd service could be reloading a device when the creation uevent for the device arrived. As a consequence, LVM sometimes failed to recognize multipath physical volumes (PVs). With this update, multipathd delays device reloads until after multipathd has received the creation uevent. As a result, multipath devices are now correctly identified as PVs.Scientific LinuxScientific Linux 7kpartx-0.4.9-85.el7_2.2.x86_64.rpm7d95a049fd45d65c084cade486bab0c562ec32feabb8e814ab914f36c7815bb5device-mapper-multipath-libs-0.4.9-85.el7_2.2.i686.rpm2e9431d3cacd798bc440ed3f51f594b6f0e4e145ffab09b7e014adfe530314bbdevice-mapper-multipath-sysvinit-0.4.9-85.el7_2.2.x86_64.rpm0daef33ee3b25fbfea49de22c7402598dd0e3735744a01768f910f082115a373device-mapper-multipath-libs-0.4.9-85.el7_2.2.x86_64.rpm03b35d52b10b027d8268fcb3a4dc94575687ccb2e14e9a1ac76e77ceccdd6e34device-mapper-multipath-0.4.9-85.el7_2.2.x86_64.rpmdd3bcb6f23b274e607b2a38ef779a967d6d96842601da1436afcc8f2e066ff6cSLBA-2016:1047-1This update fixes the following bug: * Previously, changing the keyboard layout in an X Window environment caused custom keyboard shortcuts to stop working. This update fixes the underlying source code and thus ensures that keyboard shortcuts work as expected in the described situation.Scientific LinuxScientific Linux 7qt-postgresql-4.8.5-12.el7_2.i686.rpmc4ee0d0e7c681373b3ff91126c9b9d3dba734a1076ee2152f8749e57d69e782aqt-devel-4.8.5-12.el7_2.i686.rpm4fed03332a4391e3a1ef3e7f6d9c2e83b6be1ec67de01c3599b95fb86073483fqt-4.8.5-12.el7_2.i686.rpm0dcd882be77558e2a02adbdcbc16ffab23838f09289c8a37445c144686c5f1ebqt-devel-private-4.8.5-12.el7_2.noarch.rpmf9867b59c8508f07be0042f5393e9f5abc0c4f2c4eb3b0549dd22f2b64c0dca0qt-qdbusviewer-4.8.5-12.el7_2.x86_64.rpm4dda00a9c8dd8a4ba4165e3ff7e01441a68b0854b5ffdb0d38813fba0d111f88qt-config-4.8.5-12.el7_2.x86_64.rpma527753f61090c2272fa40b431de512375717d50fc0e5f899342827e84a3a22dqt-devel-4.8.5-12.el7_2.x86_64.rpmf1156e8a0d09a11a4615ba1eb9697e890eb4f0f6238a52ca23ef1ee2853ac2cfqt-assistant-4.8.5-12.el7_2.x86_64.rpmc958ea3a3ee1bdd2f553ea41f2cb07701832e374f1bd513eb02de5e2a1f2ccdaqt-doc-4.8.5-12.el7_2.noarch.rpm931233c49e3e1d4e2188860246f19712e06985eabff4ebaa1c4664e53404715dqt-4.8.5-12.el7_2.x86_64.rpm6c71cb710fef4644706aebbdf2c41b693229ac6552407bc78dac7c7474573cbfqt-x11-4.8.5-12.el7_2.i686.rpm52a0c5d3882111fbd1ccc8f5dd2f38a88b8f2e31b828a2ab016b46bc659b97afqt-odbc-4.8.5-12.el7_2.i686.rpm7de895777dfab525fb05f939bbdf0b0c4e0b20ea8a0eacea88c332c67ac92615qt-demos-4.8.5-12.el7_2.x86_64.rpm478eec056e6b9c8a3f962642f63fae6e6b5b8188a457856668e0ce0b59fe79e8qt-examples-4.8.5-12.el7_2.x86_64.rpm92805eab04cd6c3e8b6a3d0c55aef546ba194bd0f639407d1063993888cfc482qt-odbc-4.8.5-12.el7_2.x86_64.rpm23d402509555249322ee0c2d8739bd771caf39b6fcfb0884dd6ebb51a5611b22qt-qvfb-4.8.5-12.el7_2.x86_64.rpm52ca479441101bf8244e499fcab93cc39f343de7b21e5843c2e71d813893c975qt-mysql-4.8.5-12.el7_2.i686.rpme5f9ea96fbc4aeaedb2d259c0e8cdb1b21891f598eabd158164b417bbc7b20c7qt-mysql-4.8.5-12.el7_2.x86_64.rpm245f328df0f641533a574725f77d8736772670bb709886d52429cf9341676c34qt-postgresql-4.8.5-12.el7_2.x86_64.rpmdbf7fee852e9dae7c163ce4d283f840da946894db2042dd34bec85ccf778a695qt-x11-4.8.5-12.el7_2.x86_64.rpm5fb3747d36a5f14303523461a041089a55503f107a4264ac642871947a5e9d8dSLBA-2016:1048-1This update fixes the following bug: * During upgrade from Scientific Linux 7.1 to 7.2, the encryption algorithm used by the Reversible Password Plug-in was changed from DES to AES, and 389-ds-base automatically converted all passwords to the new algorithm. However, if any defined backend was missing the top entry, password conversion failed with an "error 32". Additionally, even if the conversion failed, 389-ds-base still disabled the DES plug-in, which caused existing passwords to fail to decode. This bug has been fixed, 389 -ds-base now ignores errors when searching backends for passwords to convert, and the DES plug-in is now only disabled after all passwords using the DES algorithm were successfully converted to AES. After installing this update, the 389 server service will be restarted automatically.Scientific LinuxScientific Linux 7389-ds-base-devel-1.3.4.0-30.el7_2.x86_64.rpm2ce2e732edb5be357b9efe6c308d44c81ec683b000f53e3ed7258dcd582fc9e5389-ds-base-libs-1.3.4.0-30.el7_2.x86_64.rpmd11510ac178c63ded7c2df25ecf0794dfce468a7f26c7234f40e0c07f2e09d1c389-ds-base-1.3.4.0-30.el7_2.x86_64.rpmf3d54a92cc03c04df25ef75d872049276b22fea195250346ff4f0c8e36dbd1f0SLBA-2016:1049-1This update fixes the following bug: * Previously, the "session" extension source code contained a bug in the handling of HTML form upload progress callback. As a consequence, if the "session" extension was configured alongside certain third-party extensions, the PHP interpreter could terminate unexpectedly. This update fixes the form upload progress callback, and the PHP interpreter no longer crashes in the described scenario. After installing the updated packages, the httpd daemon must be restarted for the update to take effect.Scientific LinuxtrueScientific Linux 7php-gd-5.4.16-36.1.el7_2.1.x86_64.rpm934b4b6ffc17d6e49c5bbfecd48ec7c35058cb3368bc20ec3fbede4e1390f354php-snmp-5.4.16-36.1.el7_2.1.x86_64.rpm3d658c57357b25a4a6001c9c2dd09579a6d85f6fa5d2f2d6d5d596772dce4da2php-odbc-5.4.16-36.1.el7_2.1.x86_64.rpm92420fc659c6a4a8222bfc244e18a69ce736840548fcd09066f3c6fb38e90a85php-cli-5.4.16-36.1.el7_2.1.x86_64.rpmc76c149502e4eeb855df46a0b72970c1455641572d7e82f90a90c67df2beb3cbphp-devel-5.4.16-36.1.el7_2.1.x86_64.rpm01f876d5cd68b7316aff630b60e00ffc4110748b27a5e26acd31619b94cd13d3php-mbstring-5.4.16-36.1.el7_2.1.x86_64.rpm26da115f7b598940c9c50fe116d9ac017c6dccdc2861e0701e1e99a91cc5456ephp-intl-5.4.16-36.1.el7_2.1.x86_64.rpm022723a412a95f9320b3c82af47d6126d6ea1c1f2f4ae0cbd2aeaf369ac91850php-recode-5.4.16-36.1.el7_2.1.x86_64.rpmb98ded14bde01ae7d1ce6d0b00cff466dd91e3f0ee6e0bb665e253d1f26bbbb6php-pspell-5.4.16-36.1.el7_2.1.x86_64.rpm15545a7d01c0fdbc4234a6eeb0164cc275140adb144ca0de12677ecda56cbb5aphp-5.4.16-36.1.el7_2.1.x86_64.rpm15e58df91b8b54ff9335165c21309991902a192403946afcf3b0b774b6ed3be1php-pgsql-5.4.16-36.1.el7_2.1.x86_64.rpmef4fd2cc64ffebf2156c3092bd477ed0fd7d9ae5bdbc7293146fdbbbfbffe664php-mysqlnd-5.4.16-36.1.el7_2.1.x86_64.rpmd139d6012fa7141b450936386f38eb95bb9ff13e9915e106dc32de6ecba2b0ffphp-xmlrpc-5.4.16-36.1.el7_2.1.x86_64.rpm0731409f4ccb25985fcc44a4f865889d75260f8727cc4682c236e0438782058fphp-soap-5.4.16-36.1.el7_2.1.x86_64.rpm17188b58b9cfe491d2dd52742302576fa4e22ef85d643c7a291465baf8193560php-common-5.4.16-36.1.el7_2.1.x86_64.rpmcf11ccf0d80ba3eb9e06a10b1eac0072ad2080bb1867ee14f567c6f4e2f9363cphp-xml-5.4.16-36.1.el7_2.1.x86_64.rpmab3e7791f66c246d2bfc6e7fe61ac7fd3b01a933ae9b03f71ff9e31763992d9ephp-dba-5.4.16-36.1.el7_2.1.x86_64.rpm8dc10c287d5ff8d54f283efb14663236dfeeed8188db43d925afeb4980535083php-mysql-5.4.16-36.1.el7_2.1.x86_64.rpmbb1f1dcad3346087db858d07db0dc5defe29af3572bd3d71d0e4dd20dab23088php-ldap-5.4.16-36.1.el7_2.1.x86_64.rpmb12b23348159ac53b2ff4ee86a926be128be884a518cc8e60fcb421b852b72e2php-pdo-5.4.16-36.1.el7_2.1.x86_64.rpm0959abc0706ce23912f9d7a1527cf3b612fd9d7ff860f5b256487248711d4984php-enchant-5.4.16-36.1.el7_2.1.x86_64.rpm9ba0274abf9f90e876a8cecb9b56fb3c17f22f8b844ef98aac08c249a53fc788php-bcmath-5.4.16-36.1.el7_2.1.x86_64.rpm3292a53734379fd63c3086f1403f99c07e5561d2cea386de2d4606005cecaea1php-fpm-5.4.16-36.1.el7_2.1.x86_64.rpme2fe99616483ce909781c1b9cb15708783576e8518d801c7e1bb2a57801e970aphp-process-5.4.16-36.1.el7_2.1.x86_64.rpm46591c00a33d1833129370e72be8cba11846918baf44aa1d37f6ac1cd3a8a3ebphp-embedded-5.4.16-36.1.el7_2.1.x86_64.rpm7155a6e94ddf83750fb26436da0353dcc2ef894bce23c7044a365605f9bf9062SLBA-2016:1050-1This update fixes the following bug: * Previously, gnome-terminal failed to start if global locale was set to ISO 8859. With this update, the support for non-UTF-8 locales has been restored, and gnome-terminal starts successfully.Scientific LinuxScientific Linux 7gnome-terminal-nautilus-3.14.3-3.el7_2.1.x86_64.rpm7ff1d1a958f76625b1c420857e3ed83d4e03b2934451c9ee46534ab3e23bcc0dgnome-terminal-3.14.3-3.el7_2.1.x86_64.rpm7c0c92f945095d3ec0efa754e634397cea81dc33fe4a488c631b6a268a485b05SLBA-2016:1052-1This update fixes the following bug: * Prior to this update, the multipath command quit early if it failed to get information on any of the devices it was trying to use. As a consequence, multipath could fail to set up working devices because of failures on unrelated ones. With this update, multipath no longer quits early if it fails to get information on some of the devices. As a result, failures on some devices no longer prevent multipath from creating others.Scientific LinuxScientific Linux 7device-mapper-multipath-libs-0.4.9-85.el7_2.3.i686.rpmd13d4a4194f7fefe793587f0a0170f623374c7d500364c93d1217c45ecf577ffdevice-mapper-multipath-0.4.9-85.el7_2.3.x86_64.rpmee690d3892ebce87bd51ce9c8281fb853895896fe6dcee27d029f67b9c2a7d30device-mapper-multipath-sysvinit-0.4.9-85.el7_2.3.x86_64.rpm0736d8217447e039fbe52e982038e7746fa3786ada01d2351053c227ac0c93f8device-mapper-multipath-libs-0.4.9-85.el7_2.3.x86_64.rpm6d34bc47c0f56444dad8cfaff85de67437b1fa92d65fc7a9d29ea8f7978f4988kpartx-0.4.9-85.el7_2.3.x86_64.rpm25246f1900a36cc8da4c9c9c90601bd78215c17a7fd76d6df67395e2035b3f27SLBA-2016:1053-1This update fixes the following bug: * Previously, when the virt-sysprep tool was run on a guest, an incorrect SELinux context was set on the /etc/machine-id file inside the guest. This bug has been fixed, and the correct SELinux context is now set on /etc /machine-id in the described situation.Scientific LinuxScientific Linux 7libguestfs-rsync-1.28.1-1.55.el7_2.4.x86_64.rpmfeffabc9f73874b30c80f91fdd83da9183953eeaa9b2102339d57e361dfef033perl-Sys-Guestfs-1.28.1-1.55.el7_2.4.x86_64.rpm164cc4c3e44374ab1e590f43e35cd9421379547a16c38fde59517e09c30539edlibguestfs-man-pages-uk-1.28.1-1.55.el7_2.4.noarch.rpm744ab786fd12d1bf3316d06522b10ddb6340a5fc5377cb4250b0806b9734b8f3libguestfs-javadoc-1.28.1-1.55.el7_2.4.noarch.rpmb652a9c01d82a2832225b5a55e227198c30e280768cdc3655f4f0e8a67c71b09python-libguestfs-1.28.1-1.55.el7_2.4.x86_64.rpm9fc27062907cc459a8a7d767b9529bc63d4bf29dee22be7c0cac7b80f3a82a31libguestfs-bash-completion-1.28.1-1.55.el7_2.4.noarch.rpm1739f1cbb4c9285187c3f972f9b68d0863ffd9277d6fad7ec64b9d9d747faf26libguestfs-tools-1.28.1-1.55.el7_2.4.noarch.rpmafb48f8df9b5a88f84188e60d4613eaac82e63d91ad2bfca49c6c3f3e68c96e5libguestfs-xfs-1.28.1-1.55.el7_2.4.x86_64.rpmc4faa023cecc698db68eba5bde447b66f34ea04817cbdec8caaf6e13891f5ad5libguestfs-gobject-1.28.1-1.55.el7_2.4.x86_64.rpm441f4ecc06d20dad4fbdaa2ffae905a36915075cf5ec48752c667265e6b90bfblua-guestfs-1.28.1-1.55.el7_2.4.x86_64.rpmb6151accf33aa19d8ed6709d17dfc79dca419488e2b01037aa827297641eb008libguestfs-man-pages-ja-1.28.1-1.55.el7_2.4.noarch.rpmfe3ffd21bdbac17a5338f46451b3f92e5176f1ca615c33e3aaac47246a33a8d1libguestfs-tools-c-1.28.1-1.55.el7_2.4.x86_64.rpm4d2386721a780beda75c9d7f606b3404e7f216df7b900e34ee1bd0e55f2fbcdfocaml-libguestfs-devel-1.28.1-1.55.el7_2.4.x86_64.rpm9a3efd16e3f3642a5450dc88e7d731429e7d01b646723955875daf45f5f750d4libguestfs-java-devel-1.28.1-1.55.el7_2.4.x86_64.rpm2c4a4d9ce20b40861972f5c809e6b489a6c3edc82e779184d30e1838b8f450c5ruby-libguestfs-1.28.1-1.55.el7_2.4.x86_64.rpm9407940cfcc3b15979899051865fa7635059f5439720749287c341c2607335c4libguestfs-java-1.28.1-1.55.el7_2.4.x86_64.rpm74a0add200d47c4d03ab216825fad7cb7bc32b9b6d4d2613535e53a2785966eblibguestfs-1.28.1-1.55.el7_2.4.x86_64.rpm79b28aedf24074f152c3eec33ed92eb14ef6c0599d02110aff53bef051dabe56ocaml-libguestfs-1.28.1-1.55.el7_2.4.x86_64.rpm25117bf8143fe6171f45a5e22f179656d179f8b9e778fe22c411bf028ec4831elibguestfs-gobject-doc-1.28.1-1.55.el7_2.4.noarch.rpm7fc4ef7131777c9c6397fb34a0bfd3d5a29d8eb31090fbb9db1aebbfb57be60clibguestfs-gfs2-1.28.1-1.55.el7_2.4.x86_64.rpm460645a1a024bd3cf4c1f613d4a074c54eb9895dafb01d73ab473b445d46c96clibguestfs-rescue-1.28.1-1.55.el7_2.4.x86_64.rpm0a608423d9bd41c66cae1cdf29e031c8514312aa90c41489c2c2045c054d2205virt-v2v-1.28.1-1.55.el7_2.4.x86_64.rpm0db897a320f2037b394c07dc2d8e29faf009a1208f3cf8952718572de21fbfe6libguestfs-gobject-devel-1.28.1-1.55.el7_2.4.x86_64.rpm677d811ff1fb8f0659653f4d042fcf5612690c0666b99975568222e442c5f339libguestfs-devel-1.28.1-1.55.el7_2.4.x86_64.rpma9a2def117d43b8e4ad146c301a95d5f598ea3baa5e6d2d7d76a53bbc6b6266aSLBA-2016:1054-1This update fixes the following bug: * The nfs-idmapd service fails to start when the var-lib-nfs- rpc_pipefs.mount process is active. The process is active by default. Consequently, starting the nfsserver resource failed. With this update, var-lib-nfs-rpc_pipefs.mount stops in this situation and does not prevent nfs-idmapd from starting. As a result, nfsserver starts as expected.Scientific LinuxScientific Linux 7resource-agents-3.9.5-54.el7_2.10.x86_64.rpma8ced7158839a898c4c4f103b9b09d81619c27fa87e2ba61e701674cd009fef5SLBA-2016:1090-1This update fixes the following bug: * Previously, due to an expired Firefox Add-on certificate, add-ons were disabled and the user could not activate them. This update provides an exception which no longer verifies the sign-off timestamp, so that an add- on signed off by the Firefox certificate is a sufficient condition. As a result, add-ons are no longer disabled due to certificate expiration. After installing the update, Firefox must be restarted for the changes to take effect.Scientific LinuxtrueScientific Linux 7firefox-45.1.1-1.el7_2.x86_64.rpmd7170334940f9d04b414d24af88214c5b6fa5b2175f54fd3cda7e351dc26f3b7firefox-45.1.1-1.el7_2.i686.rpmf611ed17154a81037dce231e8351970c8d9df753b7e2db54222b2e70d560b5e7SLBA-2016:1251-1This update fixes the following bugs: * Prior to this update, snapshot merge on Logical Volume Manager (LVM2) autoactivation when booting did not work correctly. A patch has has been applied to fix this problem, and LVM2 snapshots are now deleted after merging as expected. * Previously, LVM2 failed to handle a failure in mirrors that were not synchronized yet. As a consequence, file systems on top of such mirrors could shut down prematurely. The underlying source code has been modified to and LVM2 now handles mirror repairs correctly. As a result, premature file system shutdowns no longer occur in the described situation.Scientific LinuxScientific Linux 7device-mapper-libs-1.02.107-5.el7_2.4.x86_64.rpm706f6df2a20d4ba19e3b7227674ab514323589552977ef8adb31b4a515bc7a3ddevice-mapper-event-devel-1.02.107-5.el7_2.4.x86_64.rpmc0c94384e4e8296071215d58208a63c4c0348b8a7b58b6aee58d4adcfa8ac477device-mapper-event-libs-1.02.107-5.el7_2.4.x86_64.rpma67f256da3a1cc60101bed875c1a56ffa2c692ddff172b71bfa81ba5b83dacd3lvm2-2.02.130-5.el7_2.4.x86_64.rpm9a27592e98e7f0be77c950ab1a9c17d27ac5560e37b8bb54827f9efc9ca60198lvm2-cluster-2.02.130-5.el7_2.4.x86_64.rpmb297f17455d52135dede93d2b3e1d515463d11ff165d630c5da4e95da7e9d8e6device-mapper-1.02.107-5.el7_2.4.x86_64.rpm837dfa17bfb627927ce19ab949d447b0c3354e5b93b4cac43c7d7dc01f6bdda4lvm2-sysvinit-2.02.130-5.el7_2.4.x86_64.rpm7e7195495e9c40ca291d173fcca177c4e79abcdb0744564e418454e0e95c9167lvm2-lockd-2.02.130-5.el7_2.4.x86_64.rpmb4b1b9ce6221878c32ee44b8444a5ba2a3b60a046a900fc02ee85e060757a828device-mapper-event-libs-1.02.107-5.el7_2.4.i686.rpm8ee9ff38bc1e89c9ff936db05dd65270b1767ead6fc43535cb4e241063d36157cmirror-standalone-2.02.130-5.el7_2.4.x86_64.rpmcae31985ceeb8e0501ab60a70bd9d38c267412d772412c570b6a579b8a6c5976lvm2-libs-2.02.130-5.el7_2.4.i686.rpm27e570cfca6cb008e610925056202c345061be184653b49b09514820b180eddfcmirror-2.02.130-5.el7_2.4.x86_64.rpm00d4b4c7729a2070aca0c231f2d663f6b7cf2be52892ce7df8e4a99b6e2d5a84lvm2-python-libs-2.02.130-5.el7_2.4.x86_64.rpm9dac0ec7d94c3ec966eef429850a5f9760e68267684e7b903da3a81d6a566ed6lvm2-devel-2.02.130-5.el7_2.4.i686.rpmccb71c752a13431e70621859beaad6f1245d6ec48f4bc4d709535cf5bf24ced2lvm2-cluster-standalone-2.02.130-5.el7_2.4.x86_64.rpm3d0c24a1b4e59bd2fa8327374d4f57c0ddf4b348feb73151bcb07a1154b4c076device-mapper-event-1.02.107-5.el7_2.4.x86_64.rpm33fa8e54a49eab776b6a165fb96c58f14400d494581c077c26df776c34c8e91cdevice-mapper-devel-1.02.107-5.el7_2.4.i686.rpmb28a921755f26734bbf62f7ecef456658b9eed0988b8b5bfce263d11746cab6edevice-mapper-event-devel-1.02.107-5.el7_2.4.i686.rpm8fb977142356763ad8ef6a69876fe98e977e6f8b0409d1273e53ab418fd0cbf9device-mapper-libs-1.02.107-5.el7_2.4.i686.rpm0fe8345b88018735c9680dd028a0953fc3af26df68bf858fb34dfdd1486852cclvm2-libs-2.02.130-5.el7_2.4.x86_64.rpma112cf09cac1677b658a80e4d2ae9802f9c9724ab6e6a0d3a84e8185c6c0e777lvm2-devel-2.02.130-5.el7_2.4.x86_64.rpm6080c664d4a952f66721a23eb9bcd68f50d45bcab77cdecdde6e0cfad3f41207device-mapper-devel-1.02.107-5.el7_2.4.x86_64.rpmc0d7af57d5864b6d2389f54d5efeba0c9946d38be325a318735b8e92b5418e10SLBA-2016:1252-1This update fixes the following bug: * Previously, if a mount point resided in /run on shutdown and could not be unmounted, systemd mounted this mount point read-only. This caused the whole /run directory to be read-only too. Consequently, when the dracut shutdown procedure ran in the root in /run to disassemble and unmount the old real root in /, it failed, because it requires a writable /run. With this update, if dracut encounters a read-only /run on shutdown, it mounts it again with write permissions. As a result, the dracut shutdown procedure to disassemble and unmount the old real root in / now succeeds.Scientific LinuxScientific Linux 7dracut-033-360.el7_2.1.x86_64.rpm0b7deef533079a81a22bec5b63c2f9347a5a70ef1cbece7392f9f307a2b96857dracut-network-033-360.el7_2.1.x86_64.rpm0c9c8b2e6e759fbe6fa32c1335cd67130dd466875f10b4dbfa50ca3cf4bbefcedracut-config-rescue-033-360.el7_2.1.x86_64.rpma8e624973bda37abc045fe74a1ca586ac6add94b2e82cc004c5bb7a55474b45fdracut-fips-aesni-033-360.el7_2.1.x86_64.rpm65e2003fc2954e858569b627a3b8907ab0395d16e9a91d335b8be84824f1332fdracut-caps-033-360.el7_2.1.x86_64.rpm5065c1141c11199a5690c29401453c00bc0a3bb89867d774e93648eb8131548adracut-config-generic-033-360.el7_2.1.x86_64.rpmbbd685907273130b7a5aabc53002d95579fb1beb43820fa02b403ed36d3a634bdracut-fips-033-360.el7_2.1.x86_64.rpm35a63758fb49d14582cc66210b601a18d4ab72d7b409b0286b4fa6bb181d27eedracut-tools-033-360.el7_2.1.x86_64.rpm13b8879a7d0b7f1be8f818dda1991382b250a8246bbb870b958989c391422d91SLBA-2016:1253-1This update fixes the following bug: * Previously, if the multipathd service detected that a path was down before calling the path checker, multipathd did not clear the last path checker message. As a consequence, multipathd printed that the path status was up when it was actually down. With this update, multipathd clears the path checker message if a path is determined to be down before running the path checker. As a result, multipathd no longer outputs incorrect path status messages in the described situation.Scientific LinuxScientific Linux 7device-mapper-multipath-libs-0.4.9-85.el7_2.5.x86_64.rpma494963ae28f84dc6383eb73bbd0103e2b09f2342d326b6d5d00347707d9512adevice-mapper-multipath-0.4.9-85.el7_2.5.x86_64.rpmfa85a9d785f2aa41f5abbb05f5d27074bea9a63e7e968332b1abc25ea4425c3dkpartx-0.4.9-85.el7_2.5.x86_64.rpm2e5ec8e7520594857610b5b94c993a2696a8b1d71ab9bb363cae89a9c1fb6046device-mapper-multipath-sysvinit-0.4.9-85.el7_2.5.x86_64.rpm2c5b9c5f3d4dbee7477cc2310857f10a8924654c0375d482d683f7cfd52edaa2device-mapper-multipath-libs-0.4.9-85.el7_2.5.i686.rpmcd18f53e000a8318aa102c34d745a4cc52777367412ad958bbc9f9946a50d3feSLBA-2016:1254-1This update fixes the following bugs: * Scientific Linux 7.2 introduced ldconfig.service, which is run during early boot stages before non-root file systems are mounted. As a consequence, links in the /lib/ and /lib64/ directories could be broken if remote file systems were not mounted yet, and the "ldconfig -X" command that was executed by ldconfig.service removed those symbolic links. To the ldconfig.service unit file has been removed from the systemd packages. As a result, the mentioned symbolic links are no longer removed. * Previously, systemd incorrectly handled the "LABEL=/" option in the initial RAM disk (initrd). As a consequence, the label was not found, and the system failed to boot when the root partition LABEL included the "/" character. With this update, "/" is escaped correctly in the described situation, and the system no longer fails to boot.Scientific LinuxtrueScientific Linux 7libgudev1-219-19.el7_2.11.x86_64.rpme954d7cb1d27e2c2a2f70cf355e847fcdd96b1f2bbe457bd4c4a0e12fd89e42dsystemd-libs-219-19.el7_2.11.i686.rpmbf35c662663b73e468e866ea0bbcd0e0fee258b81ee1c558479f524c827a3304libgudev1-devel-219-19.el7_2.11.i686.rpm06e3180ed8349843fa6c30c3c4a02331e5033490770c6cae74ceba2379077a56systemd-python-219-19.el7_2.11.x86_64.rpm96fb3e6f60648fe3be6d83dd0106fbfcd945c3bf96e85edef8fec47ad96f1348systemd-journal-gateway-219-19.el7_2.11.x86_64.rpmf657b6d432f36303cc25bb2e4be3435669df356eebfd59c6827e0e667bf56b18systemd-networkd-219-19.el7_2.11.x86_64.rpm80faa4d60d84d6438235646d2954dfb144b3a11ecdd70ad37e4b928d42533a0elibgudev1-devel-219-19.el7_2.11.x86_64.rpmd57126207acfa6c01dee632d8578482346c021a058d059d7ed93d4174683fbc2systemd-sysv-219-19.el7_2.11.x86_64.rpmadc903934a10d5a61339e7360ea840a52fe452cf4a1b624f1a0cf9456af5bd9bsystemd-devel-219-19.el7_2.11.i686.rpm6edd5171604e5fce5d88f0e1026e321aeae60d65db0048ab447e792372f085d4systemd-resolved-219-19.el7_2.11.x86_64.rpm253c9963f1672310495edd92de3844d75c939507debb90480737ce2a5190bde2systemd-libs-219-19.el7_2.11.x86_64.rpma23fb35519bb14d6ca58462eb5f5f551aad5dca781d5febce04a8735888ff0desystemd-devel-219-19.el7_2.11.x86_64.rpmc0793bb55451951dd34c7ccf03ea1e87a47b3623efad15e0b2d8a757f7601d9fsystemd-resolved-219-19.el7_2.11.i686.rpmf830931c83a72af43c6e55c7a54a720f58b67cc552ba1f60268558804873551csystemd-219-19.el7_2.11.x86_64.rpm2430a2f1f99e961b5ab4b286ebb21fbbe7c75d7130090667a2edbe4be99eec7alibgudev1-219-19.el7_2.11.i686.rpm43e6081a8877e6f383da43c42a10550d2ef847e22bf131feb1b3c8b0f53cfb8fSLBA-2016:1255-1This update fixes the following bugs: * The System Security Services Daemons (SSSD) ipa provider handled requests for netgroups and accounts from trusted domains asymmetrically. As a consequence, incorrect data types were accessed and SSSD failed when a netgroup for a trusted domain was requested. The requests have been synchronized and as a result, requesting a netgroup for a trusted domain no longer fails. * Previously, when a user that was disabled in Active Directory (AD) logged in and bypassed the SSSD authentication, the AD lockout attribute was not checked and the user was allowed to access. With the updated packages, the attribute is checked during the access phase, and disabled AD user accounts can not log in any more using SSH keys. * Previously, when a non-existing netgroup was requested from SSSD, the sssd_nss process allocated memory without freeing it. In consequence, sssd_nss consumed an excessive amount of memory. A patch has been applied to free the allocated memory, and sssd_nss no longer leaks memory when non-existing netgroups are requested. * Prior to this update, accounts from a trusted Active Directory (AD) did not use the default entry cache timeout value. A fix has been applied to honor the entry_cache_timeout parameter from a trusted AD as well. As a result, the parameter is now used to set the cache validity for users in all domains. * Previously, SSSD used the domain name instead of the forest name to discover services in an IdM-AD trust environment. As a consequence, the discovery in some cases failed when looking up the service DNS entries. A patch has been applied, and now the automatic server discovery works correctly in a trust environment.Scientific LinuxScientific Linux 7libsss_idmap-1.13.0-40.el7_2.9.i686.rpm463900a946756917f730ed1ce18ad155a64ba31a4ac0441db33338023e10d018libsss_nss_idmap-devel-1.13.0-40.el7_2.9.i686.rpmbd48fa297a81a9f4ea6f184b3f8ecf0895408ddf200b93657605e9d4b5684c77sssd-proxy-1.13.0-40.el7_2.9.x86_64.rpm9be19ae072205b72215c61248bf35eb3b3543f4c4584ea72007f478c014b0bc2libipa_hbac-1.13.0-40.el7_2.9.i686.rpmd1e7d8547b506e3169dbe854b803b4cdc355e27eb794215ebe6f967d4325b14fsssd-krb5-common-1.13.0-40.el7_2.9.i686.rpm58af4ac086b5c3adabf74f0523db479fd57d039fb8713bc77ee2817cbbc7aa4dlibsss_simpleifp-1.13.0-40.el7_2.9.x86_64.rpmdd3d94173261e050abf5afafc61be692d5ed889dad0d0163161992c35f8ec9bdsssd-tools-1.13.0-40.el7_2.9.x86_64.rpm14268b2986c72b79f612c95387a29aa56f9773f6958c14892dcb06421c6b678dpython-sssdconfig-1.13.0-40.el7_2.9.noarch.rpm5cc9f2bd7e0e523d25eb909fba1d687f13647e4b15634a40d9681a6f2871da6asssd-common-1.13.0-40.el7_2.9.i686.rpm09b5eb20b93e2873147980fe2972fcdf78ed696e107421ba89ecf2c171a7213esssd-libwbclient-devel-1.13.0-40.el7_2.9.i686.rpm763d30cf38b30d8be267f85953e40887353fa37717b29662384e363c6e467b94python-sss-1.13.0-40.el7_2.9.x86_64.rpm72953cab7baa4ae88dd27a1ca7c756d2eac48dff8ab174c981bdb716c19d4beesssd-ad-1.13.0-40.el7_2.9.x86_64.rpmab85db171667dea017eee651f4fa40dc8f36d5d89a770eae489fadf39092da08libsss_idmap-devel-1.13.0-40.el7_2.9.x86_64.rpm1ab82718a8fb6995d993913009c462a84fe28f3b2b7d7a78f959a131bef7d8bdlibsss_nss_idmap-1.13.0-40.el7_2.9.x86_64.rpm37aeb2ebb1968ae3c4548e4f8b7968c0902c32b8f459231ca89d83c03daae195sssd-libwbclient-devel-1.13.0-40.el7_2.9.x86_64.rpm16d42749db36a52dcf4a96cf7c3daee812e14b1ffbae3eea16892ada71d62dfasssd-client-1.13.0-40.el7_2.9.x86_64.rpm3082dd6d53ff7a9d99127a9b00f3ee4031e127a9d525f8c91987b21b7d7a2a78sssd-1.13.0-40.el7_2.9.x86_64.rpm484bc018c3d372113b590feaf999740bebf3775c6693b29cef3c68494617efe2sssd-common-1.13.0-40.el7_2.9.x86_64.rpm4c2a79464efcba847dffac499805a795bb8587829ff75da52c0edae81d0df64cpython-libsss_nss_idmap-1.13.0-40.el7_2.9.x86_64.rpm0106a1bf2253bf4dae7340376560c6d21287bd0f7339dd1ffb9c8d995bca8420sssd-krb5-common-1.13.0-40.el7_2.9.x86_64.rpm7f8da8dd08d8e837042e2d868ae7f4169b29e1a97934fb8d55e040039520a62elibsss_simpleifp-devel-1.13.0-40.el7_2.9.i686.rpmc349f8dd25d725e3d4ffb593c7262d173884f4191213a58e7791e861fc8192c2sssd-ipa-1.13.0-40.el7_2.9.x86_64.rpm5e270665a18fca882c967ec7830f19867133c0b5999c241745896dc0e183388esssd-libwbclient-1.13.0-40.el7_2.9.x86_64.rpm863a46aa96c0d9084380f572c83b8f202ee5091b886a61f1eed75161bb5d37balibsss_simpleifp-1.13.0-40.el7_2.9.i686.rpm17495f3c11043cd70ad8445bf11818b03aa6607759218ebbcafa1b356cfa3787sssd-common-pac-1.13.0-40.el7_2.9.x86_64.rpme5560f1cac16a29b441f4ff1087c35a45b843200890185ecbd3a7a28dfbbecdasssd-client-1.13.0-40.el7_2.9.i686.rpmc02eccc8b24ea9c9cda37b3a7aa7f75091246613fef4ae6f1d2e43f6a236f8dalibsss_idmap-devel-1.13.0-40.el7_2.9.i686.rpm47f2353b442fae2f002fab49a410da6e8713289c980aff2026cc7d36c68eadealibsss_simpleifp-devel-1.13.0-40.el7_2.9.x86_64.rpm407338bd5810b2a3a20bacda61d329fa4930a40e99291b162da06f18f003ed0flibipa_hbac-devel-1.13.0-40.el7_2.9.x86_64.rpm854c04ae6cde7a062764f66e52f9b6c8cbb472198cfe4a4a288c5c7123d5ef48libipa_hbac-1.13.0-40.el7_2.9.x86_64.rpmfef8a2bd494f99ec1a90ad0349ed69d22b4d8b2171ad8458fd609d9e19ffd9c8python-sss-murmur-1.13.0-40.el7_2.9.x86_64.rpma9236e52d9c9ab3aec3862a2d0f4b2daecc9b592d2cc15a387530e92ddfd896cpython-libipa_hbac-1.13.0-40.el7_2.9.x86_64.rpma073cadee0db3ee33c111b067db770d63cc5e1145a023996db8a9b523b5236f4libsss_idmap-1.13.0-40.el7_2.9.x86_64.rpm699196a8585369d2df73c2e096381966c0fcf6fe4fb9a64e8adb447360a46754libipa_hbac-devel-1.13.0-40.el7_2.9.i686.rpmd89c4cb176450b20125fa7dcffe129209394527e0b838da0f9535dc928baa4ccsssd-krb5-1.13.0-40.el7_2.9.x86_64.rpmbd21ca51f3b4bc552d33e6da403e01ccb35294ee1aadc3aca4297233c1a414fcsssd-dbus-1.13.0-40.el7_2.9.x86_64.rpm188452c8196e6ae26ddaf7ff3e2758fbe374e0a07f269a7448bb523cc5388209sssd-ldap-1.13.0-40.el7_2.9.x86_64.rpm470dc801782fd06b7866644029759d8b3207b6c53ba94eae50fac7f312790db2libsss_nss_idmap-devel-1.13.0-40.el7_2.9.x86_64.rpmbfad87c392a6fb025a5415fbed82b998fa7e66eef949a0ce702a34f173799871libsss_nss_idmap-1.13.0-40.el7_2.9.i686.rpm0a345da080277d063b4249bdb1ccd0434b22d1eb6f1692a8f0ef6c473c988af2sssd-libwbclient-1.13.0-40.el7_2.9.i686.rpma41e19d318217f53d56d1c46aebeccb7defccbdf2edb6a186d401520e01c533aSLBA-2016:1256-1This update fixes the following bugs: * Previously, the caIPAserviceCert profile was replaced with an incorrect version during replica installation. The profile import procedure, which is executed during every replica installation, has been modified to never replace existing profiles. Now, replica installation no longer replaces caIPAserviceCert with an incorrect version of the certificate profile. * When installing a clone certificate authority (CA) on a replica, the LDAP entry representing the replica was marked with the "caRenewalMaster" flag, even though another server already served as the CA renewal master. However, Identity Management (IdM) supports only one CA renewal master. Consequently, generating a new CA subsystem certificate could potentially cause the certificate to be generated multiple times, and CA operations, such as certificate renewal, could stop working on some servers. Now, the replica is no longer marked as "caRenewalMaster" in the described situation. Also, IdM removes any surplus "caRenewalMaster" flags to ensure only one CA renewal master is available. As a result, generating a CA subsystem certificate does not cause the CA operations to fail.Scientific LinuxScientific Linux 7ipa-server-trust-ad-4.2.0-15.sl7_2.17.x86_64.rpma1c228bcac0b62d8a13896222ad33b2f9afa33019d6c7d5cc726f2b853a510cbipa-python-4.2.0-15.sl7_2.17.x86_64.rpma361621be61cf997f7846648260f645898e0e27930d5d4341ccfe0b1d19191f4ipa-client-4.2.0-15.sl7_2.17.x86_64.rpmd13a55f6abff712a7c25b9b8b526d695babba536d9b1ab16fffed801b2824d04ipa-server-4.2.0-15.sl7_2.17.x86_64.rpma6559e3013fcb78795d765766c38076d3fc373f4d1a83b91ff0a4628c1ac6f17ipa-admintools-4.2.0-15.sl7_2.17.x86_64.rpm980520d7c4a56bdd19a7ddb41791b6ddf289fd81c99fe8071c74ff5176f2587cipa-server-dns-4.2.0-15.sl7_2.17.x86_64.rpm8e188933f9055b9a372fff9854eedee274654772fb2859faf653cf73e3e2398eSLBA-2016:1257-1This update fixes the following bug: * Prior to this update, Samba fixes for Badlock vulnerability generated several regressions: - inability of a domain member in an Active Directory (AD) domain to authenticate as an AD user against Samba without running of the winbindd daemon - inability of Mac OS X operating system users to access the Samba shares - inability of Samba to join an AD domain with the /bin/net utility - inability to list AD users if winbindd is running when Samba is used as a domain member in an AD domain With this update, the underlying code has been fixed and the aforementioned regressions no longer occur. As a result, users are now able to connect to the network drives mapped with the use of Samba. After installing this update, the smb service will be restarted automatically.Scientific LinuxScientific Linux 7libsmbclient-devel-4.2.10-6.2.el7_2.x86_64.rpm708b2b1939cfba1eceedf9d98da64f6c136a1e2f7410ad67fdc9b4474965e46cctdb-4.2.10-6.2.el7_2.x86_64.rpm4ecb12cea02bd8af3704aa547e292cd7a587e5d17b1b5886fe761fc09ef17feesamba-dc-4.2.10-6.2.el7_2.x86_64.rpm9220a169da934ed44ea10a1cd1065614abd263cc7266765fb186c5d78daf5c75samba-python-4.2.10-6.2.el7_2.x86_64.rpm2016da84acf5a4113c9d9983a62a8bb8fdde51e5aa2d19affe3fa8c640ec161esamba-winbind-4.2.10-6.2.el7_2.x86_64.rpm3d3ffcc0b47a8601a6f5b90b975cfd8ebacdf0de2ef8726331c52bc5d49728b3samba-test-4.2.10-6.2.el7_2.x86_64.rpm0960710f2af807ea9d99d88ec91c4a16b09b473c622998cda436ab5db59b9fdasamba-client-4.2.10-6.2.el7_2.x86_64.rpm0b0ae6fb54465491bfcc477da33e490405ac36d7ff0993f6c7d46752277c7088samba-client-libs-4.2.10-6.2.el7_2.x86_64.rpm54e51c625e3ae8fdab71c801766abab5331358af8300a8258d31a45320403284samba-pidl-4.2.10-6.2.el7_2.noarch.rpme5873d1e4b7b1d5ac57201ce098a0ec65bcb56b1076ec9eea52cd77d923176e0samba-devel-4.2.10-6.2.el7_2.x86_64.rpmebcbd264fe12e6b145799d316058530327081990c7f87681ae20bfc8eb96da25samba-vfs-glusterfs-4.2.10-6.2.el7_2.x86_64.rpmfd465ea197fd892a99dad9729d4ccfd180c1d4061d1e15a6f543a9a005de2bc0samba-test-devel-4.2.10-6.2.el7_2.x86_64.rpm5364bd1c5fc55ca46e362ef73c4eba9812acf69ea2f2a170dae23650e5279f9clibwbclient-devel-4.2.10-6.2.el7_2.i686.rpmf593a330b8838bf09d89064c26f254eb313b7af6a28b17422c17eb80f19f5129samba-libs-4.2.10-6.2.el7_2.i686.rpmfe454a108436c1ac5001d97105794adfe83d04ff7cb5ec2e54bc7610c3a94203samba-libs-4.2.10-6.2.el7_2.x86_64.rpmee10d340f113cee95d7c26694923f637d808884473d70491552eef9348feebeectdb-devel-4.2.10-6.2.el7_2.x86_64.rpm9c7bfab0c7e760e45cc20ba98d5a062daeacdcbf76d1842cdca42f14e5f8e960samba-client-libs-4.2.10-6.2.el7_2.i686.rpm16631ed4eb0bb38bc86f6aaee8fafbc9a9f69f819e6076104411bf82dfb3421cctdb-devel-4.2.10-6.2.el7_2.i686.rpm7426f480c1bbd2a69cdcf34ca0369ae91cb58232a1a841483f87eab419e96492samba-common-libs-4.2.10-6.2.el7_2.x86_64.rpmf19160ff3d48755a684ff6b5eace7d0260dffaa67adb6eefc7a99d259aff98c5samba-devel-4.2.10-6.2.el7_2.i686.rpmd6ff11a47bfe52a3b9b79e07978b787745b61b3ebaf15ea3eeef11b84aee5cc6ctdb-tests-4.2.10-6.2.el7_2.x86_64.rpma65efeeef10c68084ee546d29417f7a3b6ea21d980a26a91c4f9e9a057a546a7samba-winbind-clients-4.2.10-6.2.el7_2.x86_64.rpmf0c738e5bd476e653df0fb32907101aaa5ac9b91576a2a10ccde90bba8b84e61libwbclient-4.2.10-6.2.el7_2.x86_64.rpm02de025a6d72d55b79009e0d4dcd83db2ae99cb855c62c1b35671888a83061ealibwbclient-4.2.10-6.2.el7_2.i686.rpm80196532aa94d2a32eb254b2499e2b8474f9b9e286f963d3059ef59e56d5332fsamba-winbind-modules-4.2.10-6.2.el7_2.x86_64.rpm69d400b58cb22bc4f4b0b2f3c067d07037a83493ec0991f92e6989f6021a802blibsmbclient-4.2.10-6.2.el7_2.x86_64.rpm0bbc94dbeb3b51071708a32d08a1bf17d3c11e6227ecfb1126f22efa65d2ed7dlibsmbclient-devel-4.2.10-6.2.el7_2.i686.rpm7b658ed37bf82ee79437cabab3ea28deed69172d79727ab02c2110da93d53f07samba-4.2.10-6.2.el7_2.x86_64.rpm40ed136c629104c70fdf6a27aa8595d73b155762770c11a8daa150831aff569esamba-common-tools-4.2.10-6.2.el7_2.x86_64.rpm40330c9b2c842852cb6734d8e0b3904b61db6fd1b092b6ca4b415dabc2826dcdsamba-test-libs-4.2.10-6.2.el7_2.x86_64.rpma7212f86326fac4d671b41ca5243c3c2cf8fdb4f017f62b5ed0c0bf356f75c17samba-winbind-modules-4.2.10-6.2.el7_2.i686.rpm4a0bd9f400c0eb797bdc0f12f8081b8bcf0e068c32f0f869e04ebbdfedf69b58libwbclient-devel-4.2.10-6.2.el7_2.x86_64.rpm7b1a28abead5353c9df266a04e88aa581b6eb593abc249eea0e0dd830647fe8esamba-winbind-krb5-locator-4.2.10-6.2.el7_2.x86_64.rpme528e9ffdf55ada0c18c27fec2596ff00845d7b24dee4b7dc9bf5bbd36deac0flibsmbclient-4.2.10-6.2.el7_2.i686.rpm3d31f4617b64c1145960dcbae0f91212687a6a6806de11f3cebaaf0960c117afsamba-test-libs-4.2.10-6.2.el7_2.i686.rpmd75c86f85a3391c23830396f69caf1357b1ca7d6918584f371f0c16e0f119829samba-dc-libs-4.2.10-6.2.el7_2.x86_64.rpm4aa5375ca97e1d0e8a36d9d569757173bd761bcd7aa814c3fd1f123240fddff7samba-common-4.2.10-6.2.el7_2.noarch.rpm8897fb6a30715b16f2f02891fc39abd9d67f07b8070384332fbd6d79057365baSLBA-2016:1258-1This update fixes the following bug: * The update of the nfs-utils packages in Scientific Linux 7.2 added support for NFSv4.1 features which was incomplete. Consequently, the NFSv4 client-tracking callout program (nfsdcltrack) created incorrect schema for the clients table, and the clients using NFSv4 were not able to connect to the server. With this update, the underlying source code has been fixed, and the NFSv4 clients can now connect as expected. After installing this update, the nfs service will be restarted automatically.Scientific LinuxScientific Linux 7nfs-utils-1.3.0-0.21.el7_2.1.x86_64.rpmf4439ef5ff61fa75fd4dc894a643fc35175ead327a2db5396e6a76580299a2c3SLBA-2016:1259-1Previously, the polkit client library did not correctly free memory when listing available actions, which could cause programs to terminate. With this update, the library frees the memory correctly.Scientific LinuxScientific Linux 7polkit-0.112-7.el7_2.x86_64.rpm813c55abc8658eb3266871c75deb152706f6f3401c435698d9d49e73f059a510polkit-0.112-7.el7_2.i686.rpmb9f421ecbdb2d8208a2224b1161799b86e3a9ccc5183f993e47b0aa17e749a3apolkit-devel-0.112-7.el7_2.i686.rpm48e8c4cd50fe075356173a2596dd3de106676c2d89e1c8da26edcb029feb2b50polkit-devel-0.112-7.el7_2.x86_64.rpmb1d0b50f3a0e7e70013eb42d8dda59712a3f9787848070b4b5e451638e5e560dpolkit-docs-0.112-7.el7_2.noarch.rpm0ad32a67318e547b2c62e402972e6edd028cdbe7a89fe855450e3e0bcd28d19cSLBA-2016:1266-1This update fixes the following bugs: * In 2015, Egypt did not observe Daylight Savings Time (DST). However, in 2016, Egypt observes DST from July 7 at 24:00 to October 27 at 24:00. As a consequence of this change, the tzdata package had incorrect data regarding DST in Egypt in 2016. This has been fixed, and tzdata now has the correct data.Scientific LinuxScientific Linux 7tzdata-java-2016e-1.el7.noarch.rpm2fa33ca5ada8f71ada0d6dedcfd23ae558be750664accb2c020cbeec4fd18bc7tzdata-2016e-1.el7.noarch.rpm86dc188cd6e79d30ed85756f75c628e1c3b7172030f1db2d2a52fb314caafd89SLBA-2016:1276-1Scientific LinuxScientific Linux 7iproute-devel-3.10.0-54.el7_2.1.i686.rpmc98bad28054b5fe98916328d9d6190fc3803a9b834ece974c84e012ffdebba46iproute-doc-3.10.0-54.el7_2.1.x86_64.rpmf78e0cd4d6d88cbca3e6cd18db8fba8603fb886f8a2628a925a79283ae7b8973iproute-devel-3.10.0-54.el7_2.1.x86_64.rpmc5bab2d181f1297fee29e73af03c066015fd9954539ef08b4ee26d09ae14a6a7iproute-3.10.0-54.el7_2.1.x86_64.rpm31766245af84db6ff334522c74edcf69022b91928b5b6597377b179f75fbc405SLBA-2016:1279-1This update fixes the following bugs: * Due to missing rules in the Gluster SELinux policy, the nfs-ganesha service failed to connect to the rpc.statd daemon after a node reboot in the situation where the nfs-ganesha server was installed on four nodes. The underlying code has been fixed, and nfs-ganesha no longer fails in the described scenario. * When the nfs-ganesha server was set up on four nodes with 2X2 volume, the volume was not exported after the nfs-ganesha service was enabled. With this update, a workaround has been provided which ensures that the volume is exported as expected in the described scenario. * Due to the denial of the Access Vectore Cache (AVC), refresh of the configuration file for the dbus message daemon failed in the situation where the nfs-ganesha server was installed on four nodes and volume was created. With this update, a workaround has been provided which ensures that the configuration file now refreshes as expected. * When the nfs-ganesha server was set up with a volume, and an attempt to mount this volume on a client within the Kerberos network was made, SELinux denied this Kerberos mount. This update ensures that the Gluster SELinux domain can read the Kerberos keytab files. As a result, the Kerberos mount is successful in the described scenario.Scientific LinuxScientific Linux 7selinux-policy-sandbox-3.13.1-60.el7_2.7.noarch.rpm91aa1c574b2a15118a15a54d4fe89e1189944d71699b911d6f3dd85704c19712selinux-policy-mls-3.13.1-60.el7_2.7.noarch.rpmb0f36ff56f6c671d84660a00909fb96ebad51f161139e7519c8eaac54836e17cselinux-policy-3.13.1-60.el7_2.7.noarch.rpmdfca0d2bd2e47c9ff362b1a520f03c9c8dd6dabb7da34f8cec5613757aae38c4selinux-policy-devel-3.13.1-60.el7_2.7.noarch.rpm2f6d99e33151df8cb637648237bbe7ecc507a9713ae839fc9e6da1003ac36a6bselinux-policy-minimum-3.13.1-60.el7_2.7.noarch.rpm616049878f8a1e83a059a9fb6fd214a19273c01532d8f3449c5013834c293b32selinux-policy-targeted-3.13.1-60.el7_2.7.noarch.rpm91cdba7135d673e9f2a7e0e48c330948b43b4d45bb57b2bafb22736252338f11selinux-policy-doc-3.13.1-60.el7_2.7.noarch.rpmd7fdbfa6028662afc800fe727528932b9652c5735c9c60805e021179e7408069SLBA-2016:1283-1This update fixes the following bug: * After an upgrage of the rpcbind packages, the automounted file systems became inaccessible, which also caused an unexpected termination of running applications dependant on these file systems. The provided patch ensures that the rpcbind.socket is restarted. As a result, rpcinfo is able to connect to rpcbind locally, and automounted file systems are accessible as expected.Scientific LinuxScientific Linux 7rpcbind-0.2.0-33.el7_2.1.x86_64.rpmc63f24f17156fa09581b9e93f1a871d8908fe01835344b88b995d33277164406SLBA-2016:1284-1This update fixes the following bug: * Due to incorrect handling of Multi Function mode when dealing with the bnx2x driver, booting iSCSI from Storage Area Network (SAN) did not work correctly for some Host Bus Adapters (HBAs). The underlying source code has been fixed, and iSCSI boot now works correctly in Multi Function mode.Scientific LinuxScientific Linux 7iscsi-initiator-utils-devel-6.2.0.873-33.el7_2.1.i686.rpm9146071427578a1d061e5f3d1c62154ce6b6a6afc5ab6de93d8f0a18abb68d54iscsi-initiator-utils-devel-6.2.0.873-33.el7_2.1.x86_64.rpmdc36cfa2c4ad5e15b7aa666efa0b7875252b47b6189dc664107abb1426964fbfiscsi-initiator-utils-6.2.0.873-33.el7_2.1.x86_64.rpm2e840d73942da8280656e6e840005031a2ea9482adec022ed33443d1f22d9888iscsi-initiator-utils-6.2.0.873-33.el7_2.1.i686.rpm670a724fec9ed68495cb5183ba6f62552fd6372fb177cdee2b7c7052247aa1f2iscsi-initiator-utils-iscsiuio-6.2.0.873-33.el7_2.1.x86_64.rpm2c2fa9a717717242b014d9a9f89a9a2ab7fbdc0ec4cc641460ae964f903cc52bSLBA-2016:1285-1This update fixes the following bug: * Previously, the NetworkManager service could fail to configure routes or IP addresses because it incorrectly handled the change of the maximum transmission unit (MTU) of a device. As a consequence, activating a device with a changed MTU could result in a non-working device configuration. A patch has been applied that fixes the problem in the described scenario..Scientific LinuxScientific Linux 7NetworkManager-1.0.6-30.el7_2.i686.rpmdd4754dbc0af8cb41e2d3288610ca554a2a3bce3c9098e5750eff6b50e2b7917NetworkManager-team-1.0.6-30.el7_2.x86_64.rpm12dc684ba7a0ac97c08c3136b0af22b574f59a6191e375c68dd8a25d842add36NetworkManager-config-server-1.0.6-30.el7_2.x86_64.rpm94bc315e0e4e4a760d8213b0133d5c1c96bff793f13a4dd8cd5a0f9240d4d034NetworkManager-devel-1.0.6-30.el7_2.x86_64.rpm0f80b7573ab81eca263229dd66806ae9f49b1177e1b2575da2d5d4b26013f4b1NetworkManager-wwan-1.0.6-30.el7_2.x86_64.rpm59649c636f2257e00141a50aefd46bea9fb885316a9baa0abd62eecdcb4d85cfNetworkManager-tui-1.0.6-30.el7_2.x86_64.rpma2ccc00b94b88a74302a8b29224b7ab73535d287342ad36255b6a7a9afe8217fNetworkManager-1.0.6-30.el7_2.x86_64.rpm84ab046ae555233296fdb3e78d338775bbcf24a701a1cbe383e2c7e5575d011aNetworkManager-bluetooth-1.0.6-30.el7_2.x86_64.rpmd49ccd7ef4bd1b99131227c2c6dd3b6a8de9cfa353084c499744fdb7b66168a0NetworkManager-libnm-devel-1.0.6-30.el7_2.x86_64.rpm6945bac80eee097d9e338ecb77406e29bcf7566c09a5b1d0bc9a449788b98d6cNetworkManager-glib-devel-1.0.6-30.el7_2.x86_64.rpm03d6ab9d0d5e73b15d0035ad276d5b7fe13d12f8d8a161e573b516b845bda8d1NetworkManager-libnm-1.0.6-30.el7_2.i686.rpmd06fa4ffa381caa906782129851413399eec3094cbfa2568cc4af8c1440c909eNetworkManager-config-routing-rules-1.0.6-30.el7_2.x86_64.rpmce2784ca73e224dee0c4fd230420aa8580ce9c0edce90ea2ca53426337f18337NetworkManager-devel-1.0.6-30.el7_2.i686.rpmc7a8f2a0dd688ce4796114600d0cd8ab989d787d73fc5316d4c44f50800fe912NetworkManager-glib-1.0.6-30.el7_2.x86_64.rpm3386490ce22202a1bdfb47e83fac3c018e62b1e2eda932156094dfe5ce6a8775NetworkManager-libnm-1.0.6-30.el7_2.x86_64.rpm1072f5d7f10d11a02e238eea67aa7129c2b6f9731a29d8b9509c13bc5e546ac7NetworkManager-glib-1.0.6-30.el7_2.i686.rpm74c91f899213c8d98d24ac4090e66b1c1b4185e3b9a465c98094fd74663b0688NetworkManager-wifi-1.0.6-30.el7_2.x86_64.rpmb49c7614421bea44cf257f967086f6badac23faf2567fe1546777a6d9eff200bNetworkManager-libnm-devel-1.0.6-30.el7_2.i686.rpm2dce8bbf5fb886cf3e2659a73312ddf998c51fbdcea20dcccb7e9a7701607407NetworkManager-adsl-1.0.6-30.el7_2.x86_64.rpm41c23e004fb39ea7c6ebceb69c2b0b15766a136cc73c09aa957b839a8871b2b4NetworkManager-glib-devel-1.0.6-30.el7_2.i686.rpm1495d6a0d07f43abae599a9c715c157b4404b5ece4560b73d562a77488eb861aSLBA-2016:1290-1This update fixes the following bugs: * Previously, the node device XML did not contain the PCI header type, which caused guest PCI devices to be unavailable for passthrough assignment. With this update, the libvirt service reports the PCI header type properly, and guest PCI devices can be assigned for passthrough as expected. * When the libvirt service attempted to access a file on a blocked or unreachable NFS storage device on a remote guest virtual machine, the APIs running on the guest became unresponsive. With this update, if the remote guest is online, libvirt collects data from the guest's monitor utility and does not access its NFS storage. As a result, the described problem occurs significantly less frequently. After installing the updated packages, libvirtd will be restarted automatically.Scientific LinuxScientific Linux 7libvirt-daemon-driver-storage-1.2.17-13.el7_2.5.x86_64.rpm07a94bd63bd7484d45b4ca9740c31987f4eb180c355f1f1713a8b1c511641e6dlibvirt-1.2.17-13.el7_2.5.x86_64.rpmbea07d3c5842bd5483066dde34dfa624243e9dc369d88ca6292d32ab4dcd1234libvirt-client-1.2.17-13.el7_2.5.x86_64.rpme546c84c0587cc09dbfd9df628ce865c126df00ccb54e19a63baaacc085a61a7libvirt-daemon-config-network-1.2.17-13.el7_2.5.x86_64.rpme51a3ba0333b05b4fe1302845cf9c8af87b5a19cea81b8851153b82d7fbaef31libvirt-daemon-lxc-1.2.17-13.el7_2.5.x86_64.rpma5c2bfcd24d9fe0d282e68c8c0a7364e18e8865daa584ab9be83bdfa515c8daalibvirt-devel-1.2.17-13.el7_2.5.x86_64.rpmf2b5149f42be6b144a73313c57297f89a7d1f4f4d73de2049215dde508dae95blibvirt-daemon-1.2.17-13.el7_2.5.x86_64.rpme8198521585f008beebf153e0533afeb555b6dd77ce3b6553ef05b62a138c5balibvirt-daemon-driver-qemu-1.2.17-13.el7_2.5.x86_64.rpmb7ff10f83f9a8ebdaaf2ae22fe669af0cafba7562ee7cf299c2d5ecc7ad10eedlibvirt-daemon-driver-network-1.2.17-13.el7_2.5.x86_64.rpm3e8564a101532fb86ce6e789d0125cb5346e7ff4f3c3edf5100e5ab5ecf28766libvirt-client-1.2.17-13.el7_2.5.i686.rpm32d532f30efdef51e5b77145ec0053764732fd40cca0d6e898b58913fa25a5eflibvirt-daemon-driver-interface-1.2.17-13.el7_2.5.x86_64.rpm1249cef01817a8997a494112a0423a5256a0b16b2645a5e9fd2c764d7a63962alibvirt-lock-sanlock-1.2.17-13.el7_2.5.x86_64.rpmde66405da105391cd8ca4bf4ae1faed6bb599ada3daf0c3057f69829d97abe2blibvirt-devel-1.2.17-13.el7_2.5.i686.rpm43266991028caaf4b66ab50b6a83cd0588f04be7d016885015c4a47c847477e6libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.5.x86_64.rpma3b3b3afc8ead0dbc130ed68a319d8bb9d7ef1a290185d43e40b79b34d4e9bd6libvirt-daemon-kvm-1.2.17-13.el7_2.5.x86_64.rpmc9635ec6ef9e3fc857acba8d992a0b56a715a4ecaee1d7df70c0959cfd4e405alibvirt-daemon-driver-nodedev-1.2.17-13.el7_2.5.x86_64.rpmf8a19f505d30433d433effbe5c6803de3bd94ad5d14bdcaabd0dad1cd14c2893libvirt-daemon-driver-lxc-1.2.17-13.el7_2.5.x86_64.rpm9eb7f363b09611f38e7dd56bad2be24e05140008a8517139b0f7bc83ced6d49alibvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.5.x86_64.rpm15d2027470efe514518fedc60a065e22b615b27b2c29aa19631b0ffe9dd0b5e2libvirt-login-shell-1.2.17-13.el7_2.5.x86_64.rpm6f53a8fd099a1619c59ce19d9ce755bc3aac5c8b8a7c04dd8338551f86a230f6libvirt-daemon-driver-secret-1.2.17-13.el7_2.5.x86_64.rpm448c3ac345cd0818eecf8bf3c2731f31472a6375e52f6e07b438149584704d2clibvirt-docs-1.2.17-13.el7_2.5.x86_64.rpmf1837e500052a88ba887016ae3991b03e330ce132612342d0325f200ff6d3c90SLBA-2016:1291-1This update fixes the following bugs: * Previously, the corosync configuration file was generated with nodes using a hostname instead of an IP address and using the Internet Protocol version 4 (IPv4). However, the DNS server was set to return both IPv4 and IPv6 addresses. As a consequence, the corosync utility failed on start. With this update, if the corosync parser is configured to use IPv4, it uses only IPv4. As a result, corosync starts in the described circumstances as expected. * Previously, the corosync-cmapctl utility did not handle corosync errors in the print_key() function correctly. Consequently, corosync-cmapctl could enter an infinite loop if the corosync utility was killed. The provided fix makes sure all errors returned when corosync exits are handled correctly. As a result, corosync-cmapctl leaves the loop and displays a relevant error message in this scenario.Scientific LinuxScientific Linux 7corosynclib-devel-2.3.4-7.el7_2.3.i686.rpm71ddc7363f811471ea127dd7c2c0c6da01a186e821049b077d1f31dc3d71e223corosynclib-2.3.4-7.el7_2.3.i686.rpm7b89d59365a6c0809307cf7e4e3e09250f60976526429d8e511c535ab13bf268corosynclib-devel-2.3.4-7.el7_2.3.x86_64.rpmcf3a6ce1dbfd7adccd50bec0c6047812f5bade09c44f1647524740713fafab8acorosync-2.3.4-7.el7_2.3.x86_64.rpm2b4399e244187dd6f6a848e3bddefeee55026b1038c857c5590a27ec6595f494corosynclib-2.3.4-7.el7_2.3.x86_64.rpm2a4319f8548d39c17b4259eea0503cf9e09696a1f58a80ef4107dd0f9bf241cbSLBA-2016:1298-1This update fixes the following bugs: * Previously, when a simple paged results slot in a connection was discarded due to an error such as "SIZELIMIT_EXCEEDED", the discarded slot was not cleaned up properly. Subsequent searches which reused this slot then returned 0 instead of the actual search result. With this update, discarded simple paged results slots are cleaned up correctly, and searches return correct results even with reused slots. * When 389 Directory Server starts, all present DES-encrypted passwords are automatically converted to AES. DES passwords were previously being detected using an internal unindexed search, which was too slow for very large user databases, and could potentially cause the startup process to time out and prevent Directory Server from starting. With this update, only the configuration suffix "cn=config" is checked for DES passwords, and a new slapi task "des2aes" is now available which can be run after starting the server to convert DES passwords to AES on a specific database if needed. The server therefore starts up regardless of the database size. * 389-ds-base versions 1.3.2 and later are compliant with the schema definition described in RFC 4512, which may not allow the schema to be used by the older versions. To ease migration from earlier versions, the "nsslapd-enquote-sup-oc" was introduced. However, this parameter contained a bug which prevented handling old schema styles such as 'SYNTAX oid' in single quotes. This update fixes that bug, and you can now use single quotes with older schema styles. Additionally, this update introduces the "LDAP_SCHEMA_ALLOW_QUOTES" environment variable which adds support for older style schema in the schema directory. To enable this functionality, set LDAP_SCHEMA_ALLOW_QUOTED="on" in the /etc/sysconfig/dirsrv-INSTANCE configuration file. After installing this update, the 389 server service will be restarted automatically.Scientific LinuxScientific Linux 7389-ds-base-1.3.4.0-32.el7_2.x86_64.rpme474ec2f40c66af5cb11149aa8a83f0ef3689a1ce6a9ee5fc2685f5750154f47389-ds-base-devel-1.3.4.0-32.el7_2.x86_64.rpmfc3ffa53b22963f435620b93204c518fd4ad37c9963d235364b81bf62bf59f39389-ds-base-libs-1.3.4.0-32.el7_2.x86_64.rpmd6c8d7cc0bcd6096daf29f1d2540d36fe70592d4f37b5f2c7f24882d368dec54SLBA-2016:1302-1This update fixes the following bugs: * Previously, if the zsh process received a signal during the execution of a memory allocation function and the signal handler attempted to allocate or free memory, zsh entered a deadlock and became unresponsive. With this update, signal handlers are no longer enabled while handling the global state of zsh or while using the heap memory allocator. This ensures that the described deadlock no longer occurs. * Previously, the zsh parser state was insufficiently initialized. Consequently, zsh failed to parse unescaped exclamation mark ("!") characters in a text string. An upstream patch has been applied that fixes zsh to initialize the parser state properly. As a result, unescaped exclamation marks do not cause parsing problems to zsh anymore.Scientific LinuxScientific Linux 7zsh-html-5.0.2-14.el7_2.2.x86_64.rpm72893cc0e3a694430e90f7d03a4b506f76f083fb02cff69383752801315feaf9zsh-5.0.2-14.el7_2.2.x86_64.rpmd9af244b06250cfd99a1a81bbafe96e73591b37343116cec121e76c11f47b6feSLBA-2016:1303-1This update fixes the following bug: * Prior to this update, the virt-who agent failed to connect to VDSM using a secured connection. As a consequence, when in VDSM mode, virt-who was not able to send updates about virtual guests to the Subscription Asset Manager (SAM) and Red Hat Satellite. With this update, virt-who sends the list of guests in the VDSM mode correctly and reports to SAM and Satellite as expected.Scientific LinuxScientific Linux 7virt-who-0.14-9.el7_2.1.noarch.rpmb36396f3f9227e5538d77de49c8a56f03cbf8452921acc4cbcb49e55b55e93f5SLBA-2016:1305-1This update fixes the following bug: * When booting with the "nousb" kernel parameter, the hp and hpfax back ends previously terminated unexpectedly with a segmentation fault. The upstream patch fixing the aforementioned segmentation fault has been applied, and hp and hpfax no longer crash in this scenario.Scientific LinuxScientific Linux 7hplip-common-3.13.7-6.el7_2.1.i686.rpm4e4d0b5fb091889e42bfc2d801574df19168ea176d3c3a638a6a348b3edaf79fhplip-libs-3.13.7-6.el7_2.1.x86_64.rpmc669aa6b6645a65a756277359ee6db4b03b39bf1404501452f144250c09531ffhplip-libs-3.13.7-6.el7_2.1.i686.rpm8b1a98f19b4089789f7580ab4d71a069655fe0e0b7f280e55e8e832879cfb28chplip-gui-3.13.7-6.el7_2.1.x86_64.rpmc4c796c0191a7a4065e721b94564a84a2b28683cbb6660bac56930336a98e4d8hplip-common-3.13.7-6.el7_2.1.x86_64.rpm739149b74de5cf3c727af5f67f22e4f6e9d7299bf4162330fc65bebefb7b1b6flibsane-hpaio-3.13.7-6.el7_2.1.i686.rpmdb061597c48fd3779d6d49bed2f08c60872a9e89002c88dd31dd1ef9c31859f3libsane-hpaio-3.13.7-6.el7_2.1.x86_64.rpmdf2cf69b601bcd36288516e4a4c1609ea43e745d5e51bc3b671f89c1341cf448hplip-3.13.7-6.el7_2.1.x86_64.rpmc91526ffb506ab602442324cb8b0010f1e2dfe01739867d7d8203d16377d84d4hpijs-3.13.7-6.el7_2.1.x86_64.rpmd6f0e0d2a3990fe6811697f66908f6ec63ff5d837c0d4f923362d458a5c4e279SLBA-2016:1306-1This update fixes the following bug: * Prior to this update, the output of a PKCS#10 certificate request from the keytool application always used CRLF line endings. This update adds an option to keytool, "-systemlineendings", so that lines can instead be terminated using system line endings (LF on Scientific Linux), same as in OpenJDK 7. All running instances of OpenJDK Java must be restarted for the update to take effect.Scientific LinuxtrueScientific Linux 7java-1.8.0-openjdk-demo-debug-1.8.0.91-1.b14.el7_2.x86_64.rpm0c3a6654079bb762a2874fa545f7041ed0bc147e955252cb1306adbf71fabe18java-1.8.0-openjdk-javadoc-1.8.0.91-1.b14.el7_2.noarch.rpmacb781eed3a7c531889a019cd1a5c1aa2e053f348eecd372b646cfeb588dfbddjava-1.8.0-openjdk-accessibility-1.8.0.91-1.b14.el7_2.x86_64.rpm550ee6810f84f8bb702215678841aef08173ea83bc7a13ea8308ed1f4728d280java-1.8.0-openjdk-1.8.0.91-1.b14.el7_2.x86_64.rpm27d9bbda575e6d68e88735bf5f669f5e6c66f2a1101feb6ec503676af60f9ae3java-1.8.0-openjdk-demo-1.8.0.91-1.b14.el7_2.x86_64.rpmf42f3f9f69a57d50be6d8e841f9681ffef873c16a910a5884598c6a00b5f4a07java-1.8.0-openjdk-javadoc-debug-1.8.0.91-1.b14.el7_2.noarch.rpm7603b2a61877629019f28ae2d8237d4afb4ad1f80be7bef89ca60748f06d5705java-1.8.0-openjdk-src-debug-1.8.0.91-1.b14.el7_2.x86_64.rpm23f053662e74803c25b6f424c44b36981a5eff33e4243be28cd9dc2c6c3e600ajava-1.8.0-openjdk-debug-1.8.0.91-1.b14.el7_2.x86_64.rpmc43148f1a6212085d8b41e9ac4dc29a4385d49d409593cbee9b1dd88e7655a71java-1.8.0-openjdk-src-1.8.0.91-1.b14.el7_2.x86_64.rpm8cb0cd109d0f9fd3349081c02429006b1813675333a106c22fbb6b74af078b9fjava-1.8.0-openjdk-devel-debug-1.8.0.91-1.b14.el7_2.x86_64.rpmedf0d89eaa0d42af28e3d19eb366c064b68f7997f2aa4f3a2120af935c6bf20bjava-1.8.0-openjdk-accessibility-debug-1.8.0.91-1.b14.el7_2.x86_64.rpmec68f2738051cc4f85bd5bd2f727c41cde51d6bd951bc427f6b67a6d000d858djava-1.8.0-openjdk-devel-1.8.0.91-1.b14.el7_2.x86_64.rpm9b913ba6f315516729fe59f35cc15b925b807a7d5f613cf1058b22ebc2c297efjava-1.8.0-openjdk-headless-debug-1.8.0.91-1.b14.el7_2.x86_64.rpmb49264d2a743c4f6e2f1e51445134599211d20fbc206228b17add6a8e824c4e5java-1.8.0-openjdk-headless-1.8.0.91-1.b14.el7_2.x86_64.rpm0bc1cea6d6c50450669c4c1d982a9f9164e82f5e447de95c3bcc6bee98cb7b0eSLBA-2016:1307-1This update fixes the following bug: * Previously, the "max_filedescriptors" configuration directive in the squid.conf file of the Squid proxy server was ignored. The underlying source code has been fixed, and the "max_filedescriptors" configuration directive now works as expected. After installing this update, the squid service will be restarted automatically.Scientific LinuxScientific Linux 7squid-3.3.8-26.el7_2.4.x86_64.rpm7fcd2f3c137af582386a730201518cd656fd7b7e451bc4f5e1d8a8fb52448309squid-sysvinit-3.3.8-26.el7_2.4.x86_64.rpm88a9364e57ec22a3c914e1525f6c787862cc5fd9506e021d29079d9ccb8ada8dSLBA-2016:1349-1This update fixes the following bug: * Previously, the regular expressions filter was incorrectly positioned within other filters. As a consequence, running certain LVM2 commands, such as vgck and pvs, caused all block devices to be open for scanning, even though the settings in the lvm.conf file specified only devices that were allowed for scanning, while all other devices were supposed to be rejected. With this update, the regular expressions filter is evaluated first, before any other filters that need to open a device. As a result, only the desired devices are opened for scanning in the described situation.Scientific LinuxScientific Linux 7lvm2-libs-2.02.130-5.el7_2.5.i686.rpmab61bbc521dc165b173b16b49efda74f9382ae4559bb4793420659a5a65b768edevice-mapper-event-devel-1.02.107-5.el7_2.5.x86_64.rpm2f8ef89962aeb461a0d46660cc241f5626cf0614b7b053059afa8d6e630a3069lvm2-sysvinit-2.02.130-5.el7_2.5.x86_64.rpmb330b01a2782372b3a9b443480cfc8cabbc985da3286da2d24b861bb9ab97e45device-mapper-1.02.107-5.el7_2.5.x86_64.rpm0f9f8c1cd3dedb692a71c38a67c3ee793d003b037bb4b0e9eb9d40c05033dd98device-mapper-event-devel-1.02.107-5.el7_2.5.i686.rpm0175f875ae9153fc57c46e8c1e5248fb0f379a1baab8d8f1c22ca6992a35be59lvm2-devel-2.02.130-5.el7_2.5.x86_64.rpm489d2e84cfb4c088d718e12216d5078e9e46691b638c34e24eea67c976ab68c9lvm2-lockd-2.02.130-5.el7_2.5.x86_64.rpmea5b982a48e5d2d4889535d423307744cc2740e61bf9105ff2c6bbecd8daa6fbdevice-mapper-devel-1.02.107-5.el7_2.5.i686.rpme84ea79b0db60929da09f5f2f72caf99cf7f4be967b3fed5723309c11500e9facmirror-standalone-2.02.130-5.el7_2.5.x86_64.rpm8e2613e5faba8203893abb497f5026666099dc85a80ff74dc5f1438bc4deded2lvm2-python-libs-2.02.130-5.el7_2.5.x86_64.rpmc6de0381cf3f70b9a9e5c3c687fb60fba717aa50b86c7907e95b174777e68e9alvm2-devel-2.02.130-5.el7_2.5.i686.rpmd59fcffbaaab2468b9fd0cde2ef8a9f93274d5c05d2dcb94483441c708f2c5ddlvm2-cluster-standalone-2.02.130-5.el7_2.5.x86_64.rpm79fc64ad21a59ce671e738eb3eccd58db1b4e96d5fd46d46c765657a6c6df3b6device-mapper-event-libs-1.02.107-5.el7_2.5.x86_64.rpm91154dc2b488d5b1eb60843f659426508c6dad54a462e9ae7b230a62820d42a0cmirror-2.02.130-5.el7_2.5.x86_64.rpmba05a51882a1bfb4a9713e5f616e8a78cc97ed5c7f70c1d40ddbffd51cdb5d44lvm2-cluster-2.02.130-5.el7_2.5.x86_64.rpmb9f6cd76bfe507aa4c29ffa6f6a305c120e3269d570f6ab0bae1617fecb309e9device-mapper-devel-1.02.107-5.el7_2.5.x86_64.rpm55f776f62cae68c26832ca9c5fa419a26212c729eb1dd51ca31c9dac7bdf52d4device-mapper-libs-1.02.107-5.el7_2.5.i686.rpmb1bb8b17ddcfc2c7aac9ea20d6077b5278040c98f3fce998344ed9bd0738e5a2device-mapper-libs-1.02.107-5.el7_2.5.x86_64.rpmd96471e3712b9221f218575094b33c3eae60079850f40c84f07016ee35d51cf3device-mapper-event-1.02.107-5.el7_2.5.x86_64.rpm6d926f02ee85d468f512b47b9f4c796c6967103b3d7116595d942c234956809adevice-mapper-event-libs-1.02.107-5.el7_2.5.i686.rpm218a1dbbf6093b2e965674d228cad41bf68b64241c8a5f741c9d604bb3e08cc5lvm2-2.02.130-5.el7_2.5.x86_64.rpm238956c433468ca5f18c3a4b0b1fcda78920e1669251c28ce87a56a72d649ec2lvm2-libs-2.02.130-5.el7_2.5.x86_64.rpmceffc9da1583b9d381094b32a447a28ff06d7bb5d6f77a0df9c5eb5de4e21228SLBA-2016:1444-1This update fixes the following bug: * Previously, the dbus-daemon service incorrectly handled multiple messages containing file descriptors if they were received in a short time period. As a consequence, dbus-daemon leaked file descriptors and became unresponsive. A patch has been applied to correctly handle multiple file descriptors from different messages inside dbus-daemon. As a result, dbus- daemon closes and passes file descriptors correctly and no longer becomes unresponsive in the described situation. For the update to take effect, all running instances of dbus-daemon and all running applications using the libdbus library must be restarted, or the system rebooted.Scientific LinuxtrueScientific Linux 7dbus-x11-1.6.12-14.el7_2.x86_64.rpm86e9dfa678f1d76af5745e8743bc2f79a4c9cee585e5f7ef04060d630ad6922ddbus-doc-1.6.12-14.el7_2.noarch.rpm5cb3dc437ebe73ffcdd89bc85fffc9a733cf85b83190c8c9db893942b4257eb7dbus-libs-1.6.12-14.el7_2.x86_64.rpm58454246f05d6a3fff3e9548f3bf0463527efbaec369e7b0138375dcc38e58d8dbus-devel-1.6.12-14.el7_2.i686.rpm78c83ca51021535660b478d39efd1f798af7b3fc3ed0c8985d4bd8bae9eafc2adbus-1.6.12-14.el7_2.x86_64.rpmfde0eb0f27c8887f3f4416985d080c2972cf5ac8a3f9e70a2d57db64d83f385cdbus-devel-1.6.12-14.el7_2.x86_64.rpm1f778feed7e492b04d495d5bf89184063ce60aa66e396cfb8c4283cef22d71a1dbus-libs-1.6.12-14.el7_2.i686.rpme9f89875b186f69f1a414a3942f95f552c8582f5cc2bfe0dcff8cc6671cacb69SLBA-2016:1449-1This update fixes the following bug: * The glibc headers and linux headers share certain definitions of key structures that are required to be defined in kernel and in user space. In certain cases both user space and sanitized kernel headers have to be included in order to get the structure definitions required by the user program. However, the glibc and linux headers previously did not coordinate their behavior, which could lead to compilation errors. With this update, the glibc headers have been fixed to coordinate with kernel UAPI-based headers, and the header coordination compilation errors thus no longer occur.Scientific LinuxtrueScientific Linux 7nscd-2.17-106.el7_2.8.x86_64.rpm49a6f79d7e7f6993d93787c6a1237f6db5037882c70b4f9702f1bd752a6fe256glibc-static-2.17-106.el7_2.8.i686.rpmb535f193654bbf579618498914b692d0b78dbcc1d002c8938f1e601e96d1880dglibc-static-2.17-106.el7_2.8.x86_64.rpm2c73935d0fae60431e29777187349640f5056ea280c1bb5eb0334002e8bd13e4glibc-utils-2.17-106.el7_2.8.x86_64.rpmf6d367a4b4a0926a9009fa2edb9ec5e3023bc55e2faacacba1082c34cd026c95glibc-headers-2.17-106.el7_2.8.x86_64.rpm44fb1fd9a08f25330066125b982bff617ac0ec2028ba7a3be6d8fabec7574a82glibc-devel-2.17-106.el7_2.8.i686.rpm52391fdb38a3c0b58d5115880153e4b22ee18df41543cebf2f2235e5ea9921e0glibc-2.17-106.el7_2.8.i686.rpm6f4069d7589b030a830cee1ee6382694c904a7a6154bce73a793eb4e22dafebeglibc-devel-2.17-106.el7_2.8.x86_64.rpm5b1378157e44dc2befdffa910cf104a1def5714197bec855b2926ca5cbd54abbglibc-common-2.17-106.el7_2.8.x86_64.rpmd8cca660873a9683545b0514278aec3047ed4bb62c23e4f6a82e9c781630dce9glibc-2.17-106.el7_2.8.x86_64.rpmbfe0a6b4ec513aa18fb9b020fafc14693368bf3984674ee32f2d02624fa242b1SLBA-2016:1522-1This update fixes the following bug: * Previously, in some cases, bash terminated unexpectedly when the shopt command was used with the lastpipe option. This update fixes the bug.Scientific LinuxScientific Linux 7bash-4.2.46-20.el7_2.x86_64.rpm0e6549b0b91c4582111dd7309acc52ca97c43c350f0778070838165a80b6acd3bash-doc-4.2.46-20.el7_2.x86_64.rpm2a2bde85862bdd960d70d48f7376299e4642759ae04f1235a8f718e0d3b84353SLBA-2016:1523-1This update fixes the following bug: * Previously, when running the ifup command on a network interface whose configuration file contained "NM_CONTROLLED=no", initscripts did not reload the ifcfg file, and NetworkManager did not stop managing the device. Consequently, NetworkManager still managed the interface in parallel with initscripts. With this update, initscripts reload ifcfg files even if NM_CONTROLLED=no is set. As a result, NetworkManager stops managing the device successfully when running ifup on a network interface with NM_CONTROLLED=no set.Scientific LinuxScientific Linux 7initscripts-9.49.30-1.el7_2.3.x86_64.rpmc71694a4ab5af5a80388f8470aba7505105cc56c0bd0233791f8739ff4b4d8b3debugmode-9.49.30-1.el7_2.3.x86_64.rpm3b5423eb4d9939ce8145d65ba82851293dec386b225ec6fc498ca3e94714c0b3SLBA-2016:1524-1This update fixes the following bug: * Previously, the garbage collector inside systemd had N! (factorial of N) worst-case complexity, where N is the number of units. Consequently, the system hung during shutdown if a lot of units were stopped. The algorithm has been changed to have N^2 (square of N) worst-case complexity, and the system no longer hangs in the described scenario.Scientific LinuxtrueScientific Linux 7systemd-python-219-19.el7_2.12.x86_64.rpm5ac9f84dd86fd2d0728e7f88f1cdb21f788708379ffaabdf2ea3c9422dd67385systemd-devel-219-19.el7_2.12.i686.rpm5258fe78a4cb99665b6fe5f028c4ab2c7ac3e2cb81836779ab2ad59e2bb0f340systemd-networkd-219-19.el7_2.12.x86_64.rpmdec4d0f0d4b7da2da5163ebb17b1d6fdcd7bf0aec1306e464d2273f3f8a5f128systemd-devel-219-19.el7_2.12.x86_64.rpm7e5ec1e36b3c0625da0d47b5a27cd3067cf1fd70c2139185ddde08983062db1alibgudev1-devel-219-19.el7_2.12.i686.rpme515bf36ae447ceccbb399f9830bbad7a7c590062bcb47d959bd423d3754fe86systemd-libs-219-19.el7_2.12.i686.rpmfe1c851a535cd6a163a7955f94cc94f71d071eeb9a624db682473d598f7f9407systemd-libs-219-19.el7_2.12.x86_64.rpm9ae3c153382118f64967b8cb255ee4384b1d210d87a7c48dcf462bbc9ebba164libgudev1-219-19.el7_2.12.i686.rpmea5b3443025f5379d31c5fbba1804d445864edaa8cd9a5d325ed786ecfa76123systemd-219-19.el7_2.12.x86_64.rpm5baa7f4394dcf8f1d7dc978fa6e9b84e67cd7d574bcbfae7f6437941ead24077libgudev1-devel-219-19.el7_2.12.x86_64.rpmc7c9c65f7e48494645408322836dde8ce891991f3901efa46cebee3a1f052208systemd-journal-gateway-219-19.el7_2.12.x86_64.rpm7aa1f9a98f283bf4517a9f6f4f5d092f37f481be1de21243568c37eb54e8697csystemd-resolved-219-19.el7_2.12.i686.rpm0c4a90588d1642ce801d6dad333fd6172ed6071f2003ef8a771a62dc1749a453systemd-sysv-219-19.el7_2.12.x86_64.rpm15946a500a80153079daadfa378a0f9e2467df5d51368814f27afb63212139c9libgudev1-219-19.el7_2.12.x86_64.rpma5a64ff0e8f522aca7f019dd5d14b2ce237eeb2eed7d6291ce5524daf06741e2systemd-resolved-219-19.el7_2.12.x86_64.rpma68cd03538730b24fe5c57824a4a1147600e7cbc6a1c6d3ea23a6f4a5b33ea91SLBA-2016:1525-1This update fixes the following bug: * Previously, the "fdisk f" subcommand did not re-order logical partitions correctly by the starting offset. Consequently, a broken partition table and a loss of data could occur. The "fdisk f" subcommand has been fixed, it now creates a proper chain of logical partitions and no longer causes data corruption.Scientific LinuxScientific Linux 7libuuid-2.23.2-26.el7_2.3.x86_64.rpmbbab7dfc82464ac471e99f7d5f3abaaccb5ffab3a01cf04a5fd63df7f8585440util-linux-2.23.2-26.el7_2.3.i686.rpmf129d51dc18a2fbf0260faaf6da7c0be0f347bc8ee8c96bc634150d3849a304butil-linux-2.23.2-26.el7_2.3.x86_64.rpme0e7623a33c52fd23c6377b2b19ff5b581a64fbc38ffd98234ccd5e096c49993libmount-2.23.2-26.el7_2.3.i686.rpm0c15325a238143dd6fcf7dfc3d7d6b41b590ce5691424e6302b07b9fa50495b2libuuid-devel-2.23.2-26.el7_2.3.x86_64.rpm3ad9ca3f4b11f2d1f58278c806e319e69bbb110ede0eb9e7105c9722b57b39eflibblkid-devel-2.23.2-26.el7_2.3.x86_64.rpm7ee220b681a3f14f231d01f280ded0c96ee9913365b1c49512616aa63f5ab3b5libuuid-devel-2.23.2-26.el7_2.3.i686.rpmbe5ebd6feaae4014aee254ced6d62154e3bb7fcb2bea2d1d475e00a2bfdd52bclibuuid-2.23.2-26.el7_2.3.i686.rpmc1585b34e4b75987460444e4576cab6784e6dea400740c330ee82aabd3cbe686libmount-devel-2.23.2-26.el7_2.3.i686.rpmc9a1b1072a47be9d5bc233eaec2424427a6759aad51b14020e8ceb9c6c9e3f2dlibblkid-devel-2.23.2-26.el7_2.3.i686.rpm6602df8f2f9e9c95a304ba17d8cc5cbdb7870fd15422cf9cdf58bd4ec1b0d5delibblkid-2.23.2-26.el7_2.3.i686.rpmeea2e366f8dfadbdf0b4ae980a21f68a79e922b2a3a935a529731bbb9e9dcefalibblkid-2.23.2-26.el7_2.3.x86_64.rpmb10201661b19c1c891dbaf263421463e84b7b9cee258cae89c5d2b65da3984b0libmount-2.23.2-26.el7_2.3.x86_64.rpm86df2cbaa7403bd0cf2d8ee38f59dc3973c664b5968c0ca3969d049ab7064e07libmount-devel-2.23.2-26.el7_2.3.x86_64.rpmf6548a79d2899412d31b0802e0061868b315eba1df027271793f35807f4a2011uuidd-2.23.2-26.el7_2.3.x86_64.rpmf7f3d1c9e6e15e63077a06275d199cf9009b7ff7fddfa0747dcb4987b53485fdSLBA-2016:1527-1This update fixes the following bug: * Previously, the mechglue layer of GSS-Proxy cached file descriptors indefinitely. As a consequence, daemons that often change the UID or GID, such as as autofs, can behave unexpectedly. A patch has been applied to close and reopen the connection to GSS-Proxy when an ID changes. As a result, GSS-Proxy cache file descriptors less frequently and daemons that change the UID or GID often work as expected.Scientific LinuxScientific Linux 7gssproxy-0.4.1-8.el7_2.x86_64.rpm587b8459e30effabd98e165954d2c6d3cfbeffd5a6c4d3812db8f6c041951909SLBA-2016:1530-1This update fixes the following bug: * When an iSCSI multipath network connection was disrupted and then restored within a certain time window, data corruption in some cases occurred on the system. The handling of errors in the TCP connection shutdown during an iSCSI session has been updated to abort the connection and prevent further retransmission. As a result, TCP retransmission delays no longer cause data corruption in the described scenario.Scientific LinuxScientific Linux 7iscsi-initiator-utils-devel-6.2.0.873-33.el7_2.2.i686.rpm80846f34fc06c1743303532e05b8c6ed7bae4c523e2e492393bc22c50df3a921iscsi-initiator-utils-6.2.0.873-33.el7_2.2.x86_64.rpmdbca02147255e7391835a13b88717e0eedfcef63be1274610d8ce681a89f3e4aiscsi-initiator-utils-iscsiuio-6.2.0.873-33.el7_2.2.x86_64.rpme2f8f442a55af911597d11cdbc2e87f9a5a83e86c3f4caa83fabf2fa08f721aciscsi-initiator-utils-devel-6.2.0.873-33.el7_2.2.x86_64.rpmcd2323c128b2e07fcc61ec8f873fc8cba75b1ae04a21b66dabc06cac925b2bfaiscsi-initiator-utils-6.2.0.873-33.el7_2.2.i686.rpm8f6b3327b4b3982e3f58227065238126901a97697e27ee53cf0e5cbab19d3814SLBA-2016:1531-1This update fixes the following bug: * Due to a bug, attempts to stop an Intel Matrix Storage Manager (IMSM) RAID array during a reshape previously failed. The underlying source code has been modified to and the mdadm utility now stops the array correctly in the described situation.Scientific LinuxScientific Linux 7mdadm-3.3.2-7.el7_2.1.x86_64.rpm35a30612140cad10653b3a56f2e5816d970a2a30c128c7ae5424e9fe68674183SLBA-2016:1533-1This update fixes the following bug: * When using the vmtoolsd service to take a snapshot of a guest system autofs-mounted NFS shares, the guest previously became unresponsive. With this update, the underlying code has been fixed, and the described problem no longer occurs.Scientific LinuxScientific Linux 7open-vm-tools-9.10.2-5.el7_2.x86_64.rpmdb595de79086575d03bef3006e1824b147adc919103f871abf5e536f89914370open-vm-tools-devel-9.10.2-5.el7_2.x86_64.rpm119f7357b716762280a47c1e8680f72de57ab5f6361bed60f6280f98965fd6f4open-vm-tools-desktop-9.10.2-5.el7_2.x86_64.rpmed164dff239d5a00751f467332d2fef54e5857a6e3ae008bdb2f87ca751f03d8SLBA-2016:1534-1This update fixes the following bug: * Due to a bug, a postinstall scriptlet rebuilt initial RAM file system (initramfs) only for the running kernel, and not for the installed kernel. A patch has been applied to and initramfs is now rebuilt as expected. Note: a system reboot is necessary for this update to take effect.Scientific LinuxScientific Linux 7microcode_ctl-2.1-12.el7_2.1.x86_64.rpm0ff8f613cf6f9c0a927dafabad5c25bbf09098607c545abf6b7d75273f64e492SLBA-2016:1535-1This update fixes the following bug: * The API used to manage SAP HANA System Replication has changed in the SAP HANA SPS11 release. Previous versions of resource-agents did not support the changed API, resulting in compatibility problems and unavailability of new SAP HANA features such as Multiple Components in One Database (MCOD). This update adds support for updated API, and the resource-agents packages are now fully compatible with SAP HANA System Replication SPS11. In addition, this update adds the following enhancement: * This update adds the Galera arbitrator, "garbd", as a new resource agent. It can be used in Galera clusters with an even number of nodes, where it can act as an odd node and a quorum arbitrator, preventing split- brain situations. Use Pacemaker to set up "garbd" on a node.Scientific LinuxScientific Linux 7resource-agents-3.9.5-54.el7_2.16.x86_64.rpm2ef143bbf8fc214675da355fe1b3ad56fcfcb48d1cffc9a4ba7354c3a133d80cSLBA-2016:1536-1The libgovirt packages contain a library that allows applications to use the oVirt Representational State Transfer (REST) API to list virtual machines (VMs) managed by an oVirt instance. The library is also used to get the connection parameters needed to establish a connection to the VMs using Simple Protocol For Independent Computing Environments (SPICE) or Virtual Network Computing (VNC). This update fixes the following bugs: * Prior to this update, closing a virt-viewer console by using the checkbox in the View -&gt; Displays menu in some cases caused virt-viewer to terminate unexpectedly. This update fixes the underlying code, and thus prevents the described problem from occurring. * Using the remote-viewer console to connect to a remote guest machine on RHEV 4.0 in some cases failed because the state of the guest was not detected accurately. This update corrects a syntax error in the REST API that was causing this problem, and remote-viewer now opens the described guests more reliably. * Previously, opening a remote guest console with the remote-viewer utility in the RHEV Manager caused the event log to be flooded with the "Refresh image list succeeded for domain(s)" message. This update significantly lowers the frequency of displaying messages about refreshing image list, so that they no longer flood the guest event log. In addition, this update adds the following enhancement: * The virt-viewer and libgovirt packages have been updated to adjust to authentication changes in RHEV 4.0. This ensures that the foreign menu continues working correctly on RHEV 4.0 when starting the remote-viewer utility using the web portal interface. Note, however, that the menu does not work when starting remote-viewer from the command line.Scientific LinuxScientific Linux 7libgovirt-0.3.3-1.el7_2.4.i686.rpmc16509cffae035aa57e24f37ad887acb544f3126f38b29b944d8b5d630fc5181libgovirt-devel-0.3.3-1.el7_2.4.i686.rpm2e6aeb3f2a34c92ce37893cacee000ac4b8918f0ce99e8a48c8508cd80d4d604libgovirt-0.3.3-1.el7_2.4.x86_64.rpm54d3b08ff3c9622c6053a189496da11e8e92f6af5ccdf5335ed3998d9fe4a28alibgovirt-devel-0.3.3-1.el7_2.4.x86_64.rpmf31ddb8a623b926d24177f821899de8e78b2c269ecd8cdbe0d516fd10a4b47c1virt-viewer-2.0-6.el7_2.2.x86_64.rpm22074984e8e42d4d4db1767cdc2db03d2588e7af4d9cbfa0e5ed1674943e92a3SLBA-2016:1537-1This update fixes the following bug: * Previously, Pacemaker's node attribute manager removed attribute values from its memory but not the attributes themselves when purging a node removed from the cluster. As a consequence, if a new node was later added to the cluster with the same node ID, attributes that existed on the original node could not be set for the new node. With this update, Pacemaker purges the attributes themselves when removing a node. As a result, attributes can be set as expected on a node with the same ID as an older node. * When restarting a service, Pacemaker's crm_resource tool sometimes failed to properly determine when affected resources successfully started. As a consequence, running the "pcs resource restart" command could fail to restart a resource that was a member of a group, or the command could enter an infinite loop if the restarted resource depended on a cloned resource that moved to another node. With this update, crm_resource properly determines expected results for resources that are in a group or depend on a clone. As a result, running "pcs resource restart" and "crm_resource --restart" works as expected, and the desired service is restarted. * Previously, Pacemaker could schedule actions that depended on an unrunnable action on a cloned resource. As a consequence, log files became unnecessarily verbose, and the "crm_resource --wait" command never returned due to the scheduled actions. There was no significant effect on the cluster itself, as the cluster did not proceed beyond the unrunnable action. Now, Pacemaker no longer schedules actions that depend on an unrunnable clone action. As a result, log files are cleaner, and running "crm_resource --wait" or a pcs command with the "--wait" option returns as expected when the cluster stabilizes.Scientific LinuxScientific Linux 7pacemaker-doc-1.1.13-10.el7_2.4.x86_64.rpm37f572993ff3cc8d6e0c68faa44f82ad6529513b6f3274b020b6782ea0f6ae32pacemaker-cluster-libs-1.1.13-10.el7_2.4.i686.rpm398c9f4985f6115d9a1d0b6367adfe34a32aa47fd8184016e28d5dfd71f8dde7pacemaker-cli-1.1.13-10.el7_2.4.x86_64.rpme645f96fe37e3e2dcc052dc02978aa5a890072c2107f926b2c31ee8afbbb92fepacemaker-cts-1.1.13-10.el7_2.4.x86_64.rpm2e313302befcfd858376b78e770697aa244e270f57f890657884a6cbce2a79eapacemaker-cluster-libs-1.1.13-10.el7_2.4.x86_64.rpmd134cae1738988fe2412e9df6ff55547478c8dd527f424bc7a3bf1c814e1e286pacemaker-1.1.13-10.el7_2.4.x86_64.rpmabe5ae4f5afed7e910f7afb13da099b36bb8d7f4c15c8bf6f5bee016bd965accpacemaker-libs-devel-1.1.13-10.el7_2.4.i686.rpmea202d603573da384c53b25a0318d584ad925a951ea47fbffe76b2959615a2a3pacemaker-libs-1.1.13-10.el7_2.4.x86_64.rpmff17ea582c80cdc419d1d600c9534faf0a5cf0ece874107bd973d2545adccf37pacemaker-libs-1.1.13-10.el7_2.4.i686.rpm57ceeeb0829fa4340ea0d785a575751fc4cf7485e05d4bed25401125c59e8bc0pacemaker-libs-devel-1.1.13-10.el7_2.4.x86_64.rpm87900c7bffe3903c70f93e83bf079c74676f931910f32c7999eba8af1ab65c7bpacemaker-nagios-plugins-metadata-1.1.13-10.el7_2.4.x86_64.rpmc1a2571bfd619005fe3bb1b71a20f62e925e5fd989e98cdef512359e9ffa9f21pacemaker-remote-1.1.13-10.el7_2.4.x86_64.rpme98e1faf687be223be845bbbfbff7277287d4bb7bb5f81b407d249386cb2466aSLBA-2016:1544-1This update fixes the following bugs: * Previously, a bug in the changelog iterator buffer caused it to point to an incorrect position when reloading the buffer. This caused replication to skip parts of the changelog, and consequently some changes were not replicated. This bug has been fixed, and replication data loss due to an incorrectly reloaded changelog buffer no longer occurs. * If a replica update failed on the consumer side and was followed by another update that succeeded, the consumer's replication status was updated by the successful update, which caused the consumer to look like it was caught up. Consequently, the failed update was never retried, leading to data loss. With this update, a replication failure closes the connection and stops the replication session. This prevents further updates from changing the consumer's replication status, and allows the supplier to retry the failed operation in the next session, avoiding data loss. In addition, this update adds the following enhancement: * In a multi-master replication environment where multiple masters receive updates at the same time, it was previously possible for a single master to obtain exclusive access to a replica and hold it for a very long time due to problems such as a slow network connection. During this time, other masters were blocked from accessing the same replica, which considerably slowed down the replication process. This update adds a new configuration attribute, "nsds5ReplicaReleaseTimeout", which can be used to specify a timeout in seconds. After the specified timeout period passes, the master releases the replica, allowing other masters to access it and send their updates. After installing this update, the 389 server service will be restarted automatically.Scientific LinuxScientific Linux 7389-ds-base-libs-1.3.4.0-33.el7_2.x86_64.rpmbbb859c62b362c4131daf8a6e11efb2a85ebe64bea0b9e7075324931502b16b7389-ds-base-devel-1.3.4.0-33.el7_2.x86_64.rpm5347d939bb27f379a06615b0d2857c15db2b5d99715c1082676fc3d55cc0b421389-ds-base-1.3.4.0-33.el7_2.x86_64.rpm258502509ef998838ade2f1b54570b79be648d711ddd279d644032e49b6ee930SLBA-2016:1545-1The device-mapper-persistent-data packages have been upgraded to upstream version 0.6.2, which provides a number of bug fixes and enhancements over the previous version. Notably, the thin_ls tool, which lists thin volumes within a pool, is now available.Scientific LinuxScientific Linux 7device-mapper-persistent-data-0.6.2-1.el7_2.x86_64.rpm16e644082e0db8d86a9a5c78c89bcc61e718289c9ff3d373c2e464d61dac0f31SLBA-2016:1832-1This update fixes the following bug: * Previously, the weak-modules script was not able to handle a period (.) in names of symbols. Consequently, the device drivers were not migrated after a kernel update, because the script determined them incompatible due to a missing "TOC." symbol. With this update, the weak-modules script handles a period in symbol names. As a result, the device drivers are migrated as expected after a kernel update.Scientific LinuxScientific Linux 7kmod-libs-20-8.el7_2.x86_64.rpmb2688ec715f93b191e4f16d764d473248c62495afd99294a2f142869683bb072kmod-devel-20-8.el7_2.x86_64.rpm7ab94471e1f35a3bf5a0a1304700691707fc1fe264c2a30523d98da875dd697akmod-20-8.el7_2.x86_64.rpm2c920c9689c468f7fef7b4fc14ca23c603c0f1c9fea8cb1544bfe59d7350e34ekmod-devel-20-8.el7_2.i686.rpmfdc5e541faf7df578f6be0dc7198bd4da73726646a69659af845791ac0779a7bkmod-libs-20-8.el7_2.i686.rpm1417351e3f8e0871597bea391fecc896db8faf2a7917105aa4493987936b5b98SLBA-2016:1833-1This update fixes the following bug: * Previously, Logical Volume Manager (LVM) devices on a multipath mapper were in some cases not properly activated during the boot process, which prevented file systems from being mounted using the /etc/fstab file. With this update, the multipathd service always starts after the systemd-udev- trigger service. This ensures that using /etc/fstab to mount file systems is more reliable.Scientific LinuxScientific Linux 7device-mapper-multipath-sysvinit-0.4.9-85.el7_2.6.x86_64.rpmf91fb1258109f8de752e066c3a78f3c999cf5db4ec94c651f733f593c6b6e315device-mapper-multipath-0.4.9-85.el7_2.6.x86_64.rpm3527f008e4aa0f40fd53fcbe77960f682f3b4562eba5d3385edf429747f446a7device-mapper-multipath-libs-0.4.9-85.el7_2.6.i686.rpm8830082d9d71b45430127d44745d24a6aa7602166627d2b64a36fab32b687813kpartx-0.4.9-85.el7_2.6.x86_64.rpme6dd45db01a4368d35623a50442d105aa52b82210ee3cb8de62f6bce970d3befdevice-mapper-multipath-libs-0.4.9-85.el7_2.6.x86_64.rpme576c905e32205dde359abc203fcc887b8c21edd9bec6372e8ddd8c771832ba3SLBA-2016:1834-1This update fixes the following bug: * Previously, the OpenSSL_add_all_digests function in the hashlib library was not initialized. Consequently, some hashlib algorithms did not work. With this update, the function is properly initialized, and hashlib algorithms work as expected.Scientific LinuxScientific Linux 7python-devel-2.7.5-39.el7_2.x86_64.rpmcb3be6a797e286d46a9ffd1ddc9d3db470d670249e76d2ed06c8a826b9e42633python-debug-2.7.5-39.el7_2.x86_64.rpmd29318744d366932bd3d4cc0a9d0d74cecf4d9905e5b3c97123c72a7f2f80e1epython-libs-2.7.5-39.el7_2.i686.rpm6dfaa92cdce9dfe5272e53cc7f67a77ce602ad58c1c91d45fe244ee678ec7889tkinter-2.7.5-39.el7_2.x86_64.rpm696030b8575ffbd53e70e95ddc6e4f2918038caa50330cb1e3ed0a38f3f96708python-2.7.5-39.el7_2.x86_64.rpmb0431e0aedd529b662bc0247eba2574c6f0cb0d910dd1fddbbb34e6e3d9a3616python-test-2.7.5-39.el7_2.x86_64.rpm33c90ad175692b69aa2cac4ed363df323dbd9aaa6892ef94d5721cd4f6257802python-tools-2.7.5-39.el7_2.x86_64.rpm4dd8beef59acba8c5d36c92dc606e0f11fb12c9ec6d653389570a53d90d59f0apython-libs-2.7.5-39.el7_2.x86_64.rpm2ea906ecc269f7fa35005d6e520782cb28ac4a499258a74a43867842da7b8398SLBA-2016:1835-1This update fixes the following bugs: * Previously, the cgroups-agent program used D-Bus for its messaging. Because the dbus-daemon used a backlog of 30 connections on its D-bus system bus socket, reaching the limit of 30 queued connections could consequently result in losing cgroup empty messages from further connections. This update adds a separate cgroup agent socket of the AF_UNIX/SOCK_DGRAM type, which needs no connection set up and for no listen() backlog applies. Now, if the cgroups-agent binary file cannot queue datagram messages, it does not attempt for re-connection but instead blocks the datagram messages. As a result, cgroup empty messages are no longer lost, the session scopes for an SSH connection no longer trigger a memory leak, and the load increases. * Previously, an inefficient algorithm for reaping processes caused that the systemd service became unresponsive when a large number of processes terminated in a short interval. The algorithm has been improved, and systemd is now able to reap the processes more quickly, which prevents the described hang from occurring.Scientific LinuxtrueScientific Linux 7systemd-libs-219-19.el7_2.13.x86_64.rpmb37ecafe09767f19fc610dc3f651a7375a59261b5bf137b4bde58634007d0785systemd-resolved-219-19.el7_2.13.i686.rpmf40b67c401b4abfcf3cc092202136a685a8cdd0966d890ff01ce076b4fe9ed3fsystemd-sysv-219-19.el7_2.13.x86_64.rpma5ef4a5fae49b7c92816064ff2e83ab84b6ab955f7ee1518144878a6900a20f3libgudev1-devel-219-19.el7_2.13.x86_64.rpm2694b87ea6fe3c1191364790badf7dd9442baf2ca8947e15251a3c129ceacc6bsystemd-networkd-219-19.el7_2.13.x86_64.rpm26535bbb641e1c7379e5e5931f9a5250dc70d0fdae40862acec30af0f2df6e65systemd-python-219-19.el7_2.13.x86_64.rpm4c55103bccd36e4ae8e7575b820cafd43988d866aef3e91da5f6ecec451cde13systemd-journal-gateway-219-19.el7_2.13.x86_64.rpm8fcc8a2d4f5696693b48a1176661eef500982b6565a2b61bb802f001e64a6e88systemd-219-19.el7_2.13.x86_64.rpm54697678c52bac2565f396d555673459aa8212c7b16abee898ba29701cfefc54systemd-devel-219-19.el7_2.13.x86_64.rpme7aac0ae9ae858ceb8a28bcb815d1e80f9e99060aa5e074baf1ad24c54414c78libgudev1-219-19.el7_2.13.i686.rpmf506d4d4aa2cddc1114aed29c87e2feeb60eea3c40b894649001e9a5dd215519systemd-devel-219-19.el7_2.13.i686.rpm26d7d1467849ae8588323c1a51a1dd86e3928ae7f4fb861baf0bfdd43614697blibgudev1-219-19.el7_2.13.x86_64.rpm7c594d2e78a7e6b9ca75e3e5ddade8fa1cf4a39f982971888dd82bbcee684d9asystemd-libs-219-19.el7_2.13.i686.rpm7851aa502505f8b1747f5fd9f1c59c414350b81fd77ecc48964d4753d8da50ffsystemd-resolved-219-19.el7_2.13.x86_64.rpm4f997087b0b3987ab24538ffb930313510eb16c62f690249af40df79aa4cde92libgudev1-devel-219-19.el7_2.13.i686.rpm14f1350ae9927d42b81995ca8215be0fce926be25ec5d1f4a0f5bed2d99fee90SLBA-2016:1843-1This update fixes the following bug: * Previously, NetworkManager always sent only the host part of a machine host name in a DHCP request. As a consequence, it was not possible to force sending a Fully Qualified Domain Name (FQDN). After this update, the user can configure the FQDN to be sent in a DHCP request by using nmcli and setting ipv4.dhcp-fqdn to the desired FQDN and ensuring that ipv4 .dhcp-send-hostname is enabled. In configuration files, the FQDN can be specified with the DHCP_FQDN variable..Scientific LinuxScientific Linux 7NetworkManager-wwan-1.0.6-31.el7_2.x86_64.rpm519b8ea3e9f7c9cc0aeca790f8aafaa1c033c0c59b7b1e725e0da2e988cb2f22NetworkManager-glib-devel-1.0.6-31.el7_2.i686.rpm66d188fe3000bd916f4a20388affc3bb8845986f38564572e1d8135b6ae23ebbNetworkManager-devel-1.0.6-31.el7_2.x86_64.rpm693306c97a267284d0fd3e45f38e7ab85c138f62b0c5add3c316ef345070e287NetworkManager-config-routing-rules-1.0.6-31.el7_2.x86_64.rpm0f01a2e3247d2b87f4e75fc9017f5a81df78c5450e23a51bec45e0498e40bfbbNetworkManager-adsl-1.0.6-31.el7_2.x86_64.rpma07182bc5dfae53d6b7afffe206c3e6e0f6fb329840df5fe1253cb9d99a14b77NetworkManager-glib-devel-1.0.6-31.el7_2.x86_64.rpma8c88ef853f0faf83db1824c1d0395005b3b67eca9c75f133262cde9aa65d289NetworkManager-libnm-devel-1.0.6-31.el7_2.i686.rpm3294502a9bb4e8bf9962006b2c986a9a91ba208e5c468d9f4c2e59a305922c45NetworkManager-tui-1.0.6-31.el7_2.x86_64.rpm84f154c2eaf4f5e9283dbbd1c6ddf66e4fca6681073ba2b7fa48cf2150807c8fNetworkManager-glib-1.0.6-31.el7_2.i686.rpm73531992b8b71ca1368d323ba662fc67cf3bbd393a305bf1cab2e7a594786bbbNetworkManager-config-server-1.0.6-31.el7_2.x86_64.rpmd7b55dd059b43304602a2ff3ddddf63c4a0c5afbdfbe4c1be0789df39faa562fNetworkManager-devel-1.0.6-31.el7_2.i686.rpmacfd515826a8e604b73ea7973d2aba14734deea79394fae198e45aca23f4af25NetworkManager-libnm-1.0.6-31.el7_2.i686.rpm218528a80223239f28a7059ae6465cf8c971ae1f383e7e9f6dc5930edd8a2580NetworkManager-bluetooth-1.0.6-31.el7_2.x86_64.rpm5e687cc21464d132b165b7396e19a62e57ef17e1470008a69c32e302bd582c9fNetworkManager-team-1.0.6-31.el7_2.x86_64.rpmb5d5d99d0f247c13207770d31b1a673f482f09560272b69a0944d7570ceaa3c1NetworkManager-1.0.6-31.el7_2.i686.rpm404a2d42417432b789d8ee825c86921df15b0c8433b31fb44e90207c456f912cNetworkManager-wifi-1.0.6-31.el7_2.x86_64.rpm8d6dd7388bec031b8d204d855b0ed92407ff52a932e2f23e217f5cd5bcc9ecd4NetworkManager-libnm-devel-1.0.6-31.el7_2.x86_64.rpmeebbeb76ebda5e2c684d1f9e75f336819bd6ed9e52d36e3f2cf1ff97998f9a0aNetworkManager-libnm-1.0.6-31.el7_2.x86_64.rpm307fbf3fd5c8e031f1e4515c524baa5945e5a2f6f0f7cf89500519f78bb11aaeNetworkManager-glib-1.0.6-31.el7_2.x86_64.rpm60b4866be5516d12d32f7a1f25a68be4bf6e6ec0b981bc42014293bf76e7e9b8NetworkManager-1.0.6-31.el7_2.x86_64.rpm4a9b7582bc85654fb5014822d72a1d5e8e7acd30dc12776ee4f34e693a41d754SLBA-2016:1846-1This update fixes the following bug: * Previously, dnsmasq incorrectly read host names using the "--dhcp- hostsfile" and "--dhcp-host" options that began with numbers. As a consequence, hosts with numbers at the beginning of the host name did not receive a lease, and dnsmasq logged the "no address available" error. With this update, dnsmasq reads host names correctly, and DHCP errors with host names that begin with numbers no longer occur.Scientific LinuxScientific Linux 7dnsmasq-2.66-14.el7_2.1.x86_64.rpmbd95c5229e1a414bd56786a51e09c30cca279638f7420fc132ac62edc9b3dea7dnsmasq-utils-2.66-14.el7_2.1.x86_64.rpma5e696aa9ca84ce628833a6c934c42a98613e5fed097e8b0a0bde92788f4dc1fSLBA-2016:1848-1This update fixes the following bugs: * Previously, the realtime tuned profile that is included in the tuned- profiles-realtime package set the value of the kernel.timer_migration variable to 1. As a consequence, realtime applications could be negatively affected. This update disables the timer migration in the realtime profile. * Due to a missing condition in the _process_assignment_modifiers() function, the tuned utility sometimes failed to start, and the following error message was displayed: ValueError: invalid literal for int() with base 10: '&gt;4096' A patch has been applied to and tuned no longer fails to start. * Previously, with the realtime-virtual-host and realtime-virtual-guest tuned profiles, the rcu_nocbs kernel parameter was missing from the /proc/cmdline file. With this update, rcu-nocbs is included as expected. * Prior to this update, the tuned utility profile configuration for the kernel.sched_rt_runtime_us sysctl variable in the realtime profile included in the tuned-profiles-realtime package was incorrect. As a consequence, spawning a VM instance led to an error due to an incorrect scheduling time. Now, the value of kernel.sched_rt_runtime_us is set to "-1", and the described problem no longer occurs.Scientific LinuxScientific Linux 7tuned-profiles-realtime-2.5.1-4.el7_2.6.noarch.rpm1a3d7453232bfc41d9be6900d73d3323aa90a55e4e5332aa022e668eb76a75d4tuned-profiles-nfv-2.5.1-4.el7_2.6.noarch.rpm45c19e978c3f9f2d79fd86bc7759ddcd082418fc0ff6ab9a73467a283cf1c555tuned-utils-2.5.1-4.el7_2.6.noarch.rpm5c0d65e813fc21ab501760ad5a8f04916b6a87630ae2af3c9901084fb5a82bcctuned-gtk-2.5.1-4.el7_2.6.noarch.rpm29afaa32a88d28f052ec85781d9940fc1ae15077a778bc5064ce73a5a870f0cbtuned-profiles-compat-2.5.1-4.el7_2.6.noarch.rpm5818ddea1d01636b8d0984cbf9cbd64111166d1881b73c80c15bb2574a085d33tuned-profiles-oracle-2.5.1-4.el7_2.6.noarch.rpmed5819e489605c9c7697f4c4135ef7ca0b2132a8ac9b43ee2fe57cc5e127be6etuned-utils-systemtap-2.5.1-4.el7_2.6.noarch.rpm69c788c12c90a0d06776bde907045a142392c708e331f268cddb5d1429e7543ctuned-profiles-atomic-2.5.1-4.el7_2.6.noarch.rpm9e2953ed946e4c785c094f6dc2eb1903fab388b04a5751455520eb7edebfd9a1tuned-2.5.1-4.el7_2.6.noarch.rpmea307d004de1956a2759bfaf88326b6e351ebee0cf94f6e25d9abe20170578a9SLBA-2016:1863-1This update fixes the following bugs: * Due to insufficient SELinux policy rules, sanlock domain was previously not able to access a CEPH file system. As a consequence, sanlock failed to acquire a lock for a CEPH device. The SELinux policy rules have been updated. As a result, the CEPH file system is now correctly labeled as cephfs_t and accessible by the sanlock domain. * Previously, AVC denials messages were observed while running Red Hat Gluster Storage (RHGS) Geo-replication. The "dontaudit" rules for the Geo- replication has been added, and the AVC denials messages no longer appear. * Previously, with SELinux in enforcing mode, it was not possible to create a UNIX Domain Socket on a Red Hat Gluster Storage (RHGS) volume. As a consequence, the user could not store containers on an RHGS volume. The relevant policy module has been updated, and the user is now able to store containers on a Gluster volume.Scientific LinuxScientific Linux 7selinux-policy-sandbox-3.13.1-60.el7_2.9.noarch.rpma9aa13e3fb3aa32730bf4f6aaa91d8ee0d5f21e65725279154255c1a34342700selinux-policy-doc-3.13.1-60.el7_2.9.noarch.rpm6a18147e82d8305f5c2981cfb1334390f24d24b5f3197b44cdf40d74f99e635dselinux-policy-minimum-3.13.1-60.el7_2.9.noarch.rpm0ef279ba1f2757ac884dd090439981941bca5ecb5fa8dfba8d431042d29603c7selinux-policy-targeted-3.13.1-60.el7_2.9.noarch.rpmd5f2fbf04fd6facb5a316d6933f132d599e718d3eba7dd3d7f941b2a95d7bd75selinux-policy-mls-3.13.1-60.el7_2.9.noarch.rpmf610c3cd25f956ab7aac3177c126ba91f2e4fea74f6aafc4d72e1a2ee238f17cselinux-policy-3.13.1-60.el7_2.9.noarch.rpm475650025cf995f25ca77b42e42bf6a1ffb3245cd91e623105a81ae120660c10selinux-policy-devel-3.13.1-60.el7_2.9.noarch.rpmfe2d2e03d29c0786345e2cf1adf5d39e00312b007ee4f838ec7398021e07a583SLBA-2016:1873-1This update fixes the following bug: * Previously, the Link Aggregation Control Protocol (LACP) runner in the teamd service did not set the INFO_STATE_AGGREGATION bit when there was only one slave in a team, and the team did not negotiate. As a consequence, communication over libteam LCAP failed. A patch has been applied to and communication over libteam LCAP no longer fails in the described situation.Scientific LinuxScientific Linux 7libteam-1.17-7.el7_2.i686.rpmc36257a32016b1c3b3930b49da0b0cb25594192dda341206b27c9177c0980481python-libteam-1.17-7.el7_2.x86_64.rpme04450e90f4e911586ea2bf45df17db40d4c04495af6e300bdfcfed94cb0487eteamd-devel-1.17-7.el7_2.x86_64.rpm50a1b528f57d0490aa15346a3433bf60e4955c4fe655bed12cd0d6a467dafb45libteam-1.17-7.el7_2.x86_64.rpm5cf2a4037a6b1e0eede2cc418c39845973d2856324d73d8e408e0cdf828ec728teamd-1.17-7.el7_2.x86_64.rpmf1468cd19513747d02ce15291c6b84d8055674550b6319e23e6d216224e8ae65libteam-devel-1.17-7.el7_2.x86_64.rpm844dc411de5214cbc32f9d335df5ffdadec77336a7ec50cc01c8ba988a46f32dteamd-devel-1.17-7.el7_2.i686.rpme09011f61623ac140b56f4fd8fb71db106edb735d82a21d8ec55c4426ba6319dlibteam-devel-1.17-7.el7_2.i686.rpm21ef2df3ca5bf737eb78c803f93e5264b7d9df6e0e5e916abb4502a4aec5dc13libteam-doc-1.17-7.el7_2.x86_64.rpm5208d3bb8157f01f5dd1903491a49c177211cee12fca8710a9639ccf505a9e5dteamd-1.17-7.el7_2.i686.rpm054ef796dabcd3dc7885f4ef63e756f28bcaa5af2057c7a26f1b105cf3d19840SLBA-2016:1874-1This update fixes the following bug: * Due to a race condition, using the SPICE console to view video from certain sources, such as YouTube pages, and stretching the video over multiple monitors caused SPICE to terminate unexpectedly. This update ensures that thread-safe reference counting is used in the described scenario, which avoids the race condition and thus prevents the crashes from occurring.Scientific LinuxScientific Linux 7spice-server-0.12.4-15.el7_2.2.x86_64.rpmc67c4f4221decf76de0f46522b02ad1aa60179a2fe610ced7722f095e8fc4f6cspice-server-devel-0.12.4-15.el7_2.2.x86_64.rpm45a0b7d320ffb480870ce0ebab0aa2f8fd95fcbe329d7c07cb3755c35180ff37SLBA-2016:1876-1This update fixes the following bug: * Previously, the dmraid packages were compiled with an incorrect testing option. As a consequence, the dmraid tool inadvertently scanned all devices, including any other device-mapper subsystems like LVM, which could interfere with those other subsystems and cause various failures while booting. With this update, testing mode is disabled in dmraid, and all devices are not scanned at boot. As a result, interferences between dmraid and other device-mapper subsystems no longer occur.Scientific LinuxScientific Linux 7dmraid-1.0.0.rc16-26.el7_2.1.i686.rpm9ba1b7827ed03aaf48d02f2c74a399188913a0c2507f4e671e40e10bba7765eddmraid-1.0.0.rc16-26.el7_2.1.x86_64.rpm68602a883788625b9f0e0d89c0ccac1b13bfede4fd070eaa25008e4c9e8ef85edmraid-devel-1.0.0.rc16-26.el7_2.1.x86_64.rpm2abcc468649cc99adf95a9c4834cf74f43a676dcdb8108782c6029f920891f14dmraid-events-1.0.0.rc16-26.el7_2.1.x86_64.rpmabd6ed05fad7b2fc93d3b71d5049a9516eb3c2b6f29e526c3f1441b6b15f7b9admraid-events-logwatch-1.0.0.rc16-26.el7_2.1.x86_64.rpm0cf2e2f8d11df61379ff620c74fa6198cfcc8df787a147dd15f248f7c25562a9SLBA-2016:1877-1The java-1.8.0-openjdk packages have been upgraded to upstream version 1.8.0.102, which provides a number of bug fixes over the previous version. This update also fixes the following bugs: * Previously, Java programs failed with a NoSuchAlgorithmException when attempting to debug SSL connections in which information on supported elliptic curves was received from the client. With this update, the debug code supports cases in which an elliptic curve cryptography provider is unavailable, and they no longer cause Java programs to fail. * Previously, due to a bug in the Java Virtual Machine, Java programs running on the 64-bit ARM architecture failed with false NullPointerExceptions. With this update, the bug is fixed, and the described problems no longer occur. All running instances of OpenJDK Java must be restarted for the update to take effect.Scientific LinuxtrueScientific Linux 7java-1.8.0-openjdk-debug-1.8.0.102-1.b14.el7_2.x86_64.rpm133f4301246f5236ef04f6dba3f6bf47e81b886e4453d65bdd89e01c3237c2efjava-1.8.0-openjdk-devel-1.8.0.102-1.b14.el7_2.x86_64.rpm5b6585f1aeacd8195bb597a9248121869daa7f284bda53ceaf2116bb17275508java-1.8.0-openjdk-accessibility-debug-1.8.0.102-1.b14.el7_2.x86_64.rpm59095049c8d4db0b70099058e077d5ac4bd1a0d5db4332c11accca4c9c4bdb7ajava-1.8.0-openjdk-demo-1.8.0.102-1.b14.el7_2.x86_64.rpm89c6745600acf2f58602f5c61c9b4f7e7b4c170bedbdba4ae0d2ab26464cbc97java-1.8.0-openjdk-devel-debug-1.8.0.102-1.b14.el7_2.x86_64.rpm8a8fb9df3b97171d10fbfe910565180a4aa630a58130c1e59b55d3abc91e578djava-1.8.0-openjdk-headless-1.8.0.102-1.b14.el7_2.x86_64.rpm064df04078bf33a896ff52a23e107327b3ed8dda6fbde40c40b9393d03c085b2java-1.8.0-openjdk-javadoc-1.8.0.102-1.b14.el7_2.noarch.rpm41c0c22883f88820144119c2e5a9e6a29e4d9c0f73270c7cb857e22851c27150java-1.8.0-openjdk-accessibility-1.8.0.102-1.b14.el7_2.x86_64.rpm8d75f0027ef84bb300cf6d404f17408e89ab22c57f22403ad2b94c1c50d54043java-1.8.0-openjdk-headless-debug-1.8.0.102-1.b14.el7_2.x86_64.rpmb48d8504e0528e43c57e39849bca865925cebfcb4dec8100e89d533c8076ca68java-1.8.0-openjdk-src-debug-1.8.0.102-1.b14.el7_2.x86_64.rpme72861f7745c49332b55d494594e056a5c2e4d096699b14a113bb7a0c5749588java-1.8.0-openjdk-src-1.8.0.102-1.b14.el7_2.x86_64.rpmf4d91c3a33179d464138694af0981c1d7371372dc5eedd0b3eb34dd58e15cd8fjava-1.8.0-openjdk-1.8.0.102-1.b14.el7_2.x86_64.rpm1a32e765e1123ba60b08c85806bf8649f42104fbb8634a25751c2c3904f8d691java-1.8.0-openjdk-demo-debug-1.8.0.102-1.b14.el7_2.x86_64.rpm96fe173014495ed3a794c6ee703dfae4c161fb1f7b0b97e1deb692742752b82fjava-1.8.0-openjdk-javadoc-debug-1.8.0.102-1.b14.el7_2.noarch.rpm4f8ce55e9be1732964835e9079baaf67f1a24861c1e4dc4a6b4aa1dcb0da7915SLBA-2016:1878-1This update fixes the following bug: * The memcached daemon now correctly starts in an IPv6 environment.Scientific LinuxScientific Linux 7memcached-devel-1.4.15-9.el7_2.1.x86_64.rpmc7b1070dac76dc71731013a82e66069ae4e2a8a81a79e0a5ceb52f217c1f3019memcached-1.4.15-9.el7_2.1.x86_64.rpm649240e917de4111c025a1048937ec72f207357229c6887136bcdd7ec3f0a5bbmemcached-devel-1.4.15-9.el7_2.1.i686.rpm6bce340772a39bf94829a50665881b44bc03f4c2d81b2a5ed03e933970f2433bSLBA-2016:1879-1This update fixes the following bug: * Previously, ipmitool could not recognize DDR4 memory modules and terminated unexpectedly on such systems. This update adds support for DDR4 reporting. As a result, ipmitool no longer crashes on DDR4 systems when running the Field Replacement Unit (FRU) inventory listing. After installing this update, the IPMI event daemon (ipmievd) will be restarted automatically.Scientific LinuxScientific Linux 7ipmitool-1.8.13-9.el7_2.x86_64.rpmd5ed99eb5ec6b5a90bb6f85ea714a57e5b838d10c173bce45d8fd82c8427d010exchange-bmc-os-info-1.8.13-9.el7_2.noarch.rpmb6bb7de1505e2a10c90dbbf4efac7be107053456a23cf3aedf66ddf6ead54aa4bmc-snmp-proxy-1.8.13-9.el7_2.noarch.rpma58c1580fdbc56c39f8c7fd1ab00af863e3f265a7b1abc7bafd122c1d823df00SLBA-2016:1880-1This update fixes the following bug: * Previously, the fence agent for Cisco UCS, fence_cisco_ucs, did not obtain the power state status correctly when a blade was pulled out from the blade enclosure. As a consequence, the stack in use became inoperative. With this update, the correct power state status is obtained, and fencing works as expected in the described situation.Scientific LinuxScientific Linux 7fence-agents-apc-snmp-4.0.11-27.el7_2.9.x86_64.rpm12f051d33913761edc64a172da85878d266f57e30f3af08a258e32f137c630d2fence-agents-intelmodular-4.0.11-27.el7_2.9.x86_64.rpm579aa74a6a6c82baec277d1c3f7ed5e2db7dafbd3e3dbe372d647baf5af3414dfence-agents-rhevm-4.0.11-27.el7_2.9.x86_64.rpm1a24f6242031c658b82ebb02457f7b8d22bdb138f1cbc47276923af7ed635739fence-agents-cisco-ucs-4.0.11-27.el7_2.9.x86_64.rpmf830d752c2d5cdf193e42bd99e5c652135c08c9e991870e239b8675e348278f9fence-agents-ifmib-4.0.11-27.el7_2.9.x86_64.rpmf5faab25eb7dd37e019174f04b6766e218c4f27c02e01c55aabde33cffab9ba7fence-agents-ipmilan-4.0.11-27.el7_2.9.x86_64.rpm6a2b5bbdf899305fd38ea5b18b5b8c1dd06a1ad014d8492ae512ae7b122ca835fence-agents-rsb-4.0.11-27.el7_2.9.x86_64.rpm26cf40a2d9de0310a942081681a2903b8854ac7188ab4bf03cd50788f9f4f2fafence-agents-compute-4.0.11-27.el7_2.9.x86_64.rpm7f691ca6f6a6e0242a4182176d2343241280db96b02cc9a72bd61f83e62dc49afence-agents-eaton-snmp-4.0.11-27.el7_2.9.x86_64.rpm227565e71714dffc21cbb56f0b22f6095163b1c57eb9749a0465e2a137327869fence-agents-vmware-soap-4.0.11-27.el7_2.9.x86_64.rpm4aa5f747d72ad0de64608c6ec717ddf585b54f1abe3a1d3a695ea3f2292db414fence-agents-hpblade-4.0.11-27.el7_2.9.x86_64.rpm9f8b7ffa4df031603ebd6a101d2ee7da3809f44a7818ebfb93a067209c3913e2fence-agents-ilo-mp-4.0.11-27.el7_2.9.x86_64.rpma79b1ff0b85a483992164e00c8a73cde26e481085abdc12293ea1741054cffaefence-agents-cisco-mds-4.0.11-27.el7_2.9.x86_64.rpmf0181d6231afe1fee4ad11e5449ab69e7822948bc8d61c171c9e6d71578662abfence-agents-ilo2-4.0.11-27.el7_2.9.x86_64.rpmfb187c5d3c61022a71404b8ffa57c46daf94eacec385e67adafce589fd292fb8fence-agents-virsh-4.0.11-27.el7_2.9.x86_64.rpm36fe648e217277b409ef55ad45069555c874bdab20d08fdd3b6e57de4425deaefence-agents-apc-4.0.11-27.el7_2.9.x86_64.rpm7c58e8853b18a5ce82329a29ef7124bdd18fa9d6c25481e03f6f3f0a6dfd4e99fence-agents-ipdu-4.0.11-27.el7_2.9.x86_64.rpmfc09be6e44b837cd2efe1de9066ebda3618eed146c24f34c27a73097279b8edcfence-agents-eps-4.0.11-27.el7_2.9.x86_64.rpm2f81c6dfbf309e97d3d0018052d0dca9cd56fa1415f36e57e47beaf11d59f96ffence-agents-brocade-4.0.11-27.el7_2.9.x86_64.rpm52087c91440fb799e05b9b25403c1e223f302a15932babbafd21ed54e388eecafence-agents-emerson-4.0.11-27.el7_2.9.x86_64.rpm2660a8723e861aa594ecdc1fbd7892e6dac15bee9c8aec3a2e7ab4c3ba8be1e3fence-agents-common-4.0.11-27.el7_2.9.x86_64.rpm4425e37213f3eb13d53753ddcd7c8ed0744ef702e8de2a9fa2f5f15002fbfa7efence-agents-mpath-4.0.11-27.el7_2.9.x86_64.rpm4cdd5befeea4625b3a3f4ede22027a7e428a8b2a7816613a0ed45e52a7209633fence-agents-bladecenter-4.0.11-27.el7_2.9.x86_64.rpm6871cc77838beb555577913f9665665459117be0d08ca288839d0daa9cc2b591fence-agents-ilo-ssh-4.0.11-27.el7_2.9.x86_64.rpm6b5378b90cb540ca8596f3541db41c578f1394f0a4da61f80ff90cdfe1e69679fence-agents-scsi-4.0.11-27.el7_2.9.x86_64.rpm46944653dfae707fcc56396249110538b74fb5f967edc1400c85d29f322daba9fence-agents-rsa-4.0.11-27.el7_2.9.x86_64.rpm4601172dbc8b3c162517aeaab3f8ed2692e3dc2db1d1c19203fe497716e1cc57fence-agents-all-4.0.11-27.el7_2.9.x86_64.rpmccecba91db565806e0ef5ffe00736a381acfe2e40865d5304ace6d4b3f7696e4fence-agents-ilo-moonshot-4.0.11-27.el7_2.9.x86_64.rpmbcb1f5ea7baa63e59e5b45801640ef9601320fd1ddd71812080ae0da4a8d71ecfence-agents-drac5-4.0.11-27.el7_2.9.x86_64.rpm9bd98180ea49600617a3df505b1601cd0fe57d5d69439082d89a3aa779111b72fence-agents-kdump-4.0.11-27.el7_2.9.x86_64.rpm09c64fab85ec56fb64126b4a0d692995af67a883f191bd55a54a216f8071cc4bfence-agents-ibmblade-4.0.11-27.el7_2.9.x86_64.rpmaa3c8f18c6237a4e685ec55117358975c8f05f8f488de64dde940d98a76475d7fence-agents-wti-4.0.11-27.el7_2.9.x86_64.rpm61a68ca2c6857710c65bae773293f30b904e9f7f288a8f5f346dd34d50124c6fSLBA-2016:1881-1This update fixes the following bug: * A previous update caused Pacemaker to start NFS services during monitor actions such as "pcs resource debug-monitor". This update fixes the nfsserver resource agent, and monitor actions in Pacemaker no longer automatically start these services.Scientific LinuxScientific Linux 7resource-agents-3.9.5-54.el7_2.17.x86_64.rpmfb042ff2560c1c2dfe43d641fed79398491cca260b28f8aa6e618d2977813128SLBA-2016:2551-1Libtasn1 is a library that provides Abstract Syntax Notation One (ASN.1, as specified by the X.680 ITU-T recommendation) parsing and structures management, and Distinguished Encoding Rules (DER, as per X.690) encoding and decoding functions.Scientific LinuxScientific Linux 7libtasn1-devel-3.8-3.el7.i686.rpm423e2d5401e60a414f46224d373275a2fb411c2eb0e85bb74fb0359456021ad7libtasn1-3.8-3.el7.x86_64.rpm0d4426d22b11fa82c3ad47899a21e52fc39f2715d25ee3261427ef43af20bd1alibtasn1-3.8-3.el7.i686.rpm2a16b37f63d3ea365050884ceb4290ceebbf1b93a467dd9dd441b5f9de60fb68libtasn1-devel-3.8-3.el7.x86_64.rpme9954da150ff81d845cab045d9f13e3c16177aca479d5ee4944057c8152f2caclibtasn1-tools-3.8-3.el7.x86_64.rpm795b8ee81c6bd583299dcf1cd2d2a5e82b6d0d101add3f83a9fef6228116e9d7SLEA-2016:0026-1The kmod-ahci packages contain the Advanced Host Controller Interface (AHCI) kernel module. This enhancement update adds the kmod-ahci packages to Scientific Linux 7.Scientific LinuxScientific Linux 7kmod-ahci-327_RH1-1.el7_2.x86_64.rpm545ac12344260e4349f659a804994d10e585c1a4556396d65303495667ebaef7SLEA-2016:0027-1The kmod-igb packages contain the Intel I354 NIC (i354 with Marvell 1512 PHY) kernel module. This enhancement update adds the kmod-igb packages to Scientific Linux 7.Scientific LinuxScientific Linux 7kmod-igb-5.2.15_k-1.el7_2.x86_64.rpmbea75f20c592b9987356af6efbdfbe473d66ad7bc89bae3f7f587fe2c60c22deSLEA-2016:0182-1The ca-certificates package has been upgraded to upstream version 2.6, 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.6 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.21. 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-2015.2.6-70.1.el7_2.noarch.rpm6f8ce4edf67cf6da2d30cf6bf281a6d426f17b800bf864c1f72d9eb529fc06a8SLEA-2016:0464-1* This enhancement update adds the kmod-i40e packages to Scientific Linux 7. 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 these kernel modules are 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-i40e-1.3.21_k-1.el7_2.x86_64.rpme625d7b8c6318a77b6809d06a5493afdb0ef7dfd86305258162d6268b826af6bSLEA-2016:0593-1This update adds the following enhancements: * The virt-v2v utility now processes the "<vmware:datacenterpath>" tag, newly added to the domain XML file by the libvirt library, and maps the paths to the disk image on a VMware vCenter server. This allows for accessing disk images on the VMware vCenter server without the need for the "--dcpath" command-line option. * With this update, virt-v2v is capable of exporting guests with more than one disk to the OpenStack Glance service, while previously, only guests with a single disk could be exported. This makes it possible for larger virtual deployments to be converted to OpenStack Glance using virt-v2v.Scientific LinuxScientific Linux 7ocaml-libguestfs-devel-1.28.1-1.55.el7_2.2.x86_64.rpma2eeb23238c08ef71a749c36f418e195a8d2d02d7bb7e253a525a968c2260a61libguestfs-javadoc-1.28.1-1.55.el7_2.2.noarch.rpm294fe90cbebc9871cf257ebf588328593ebf378a94cdb580b81c941517322d2elibguestfs-man-pages-uk-1.28.1-1.55.el7_2.2.noarch.rpm835a717893a23e5741aa1adeee8d21ba5a9b2af2d5553a3fa63473b98f6dbefepython-libguestfs-1.28.1-1.55.el7_2.2.x86_64.rpm980460de7449d8785085081a2628b70a1074d2c6efa4020b51b5be39752048f2libguestfs-1.28.1-1.55.el7_2.2.x86_64.rpm39d0a6af598506811d2d3367ab840af590746cb8c665af9bbbfd20a55b8c3c93libguestfs-xfs-1.28.1-1.55.el7_2.2.x86_64.rpm7b71bacf579b23ec3a6fe7535edf515cd5310d9745df8317cf70bbb4da5fa02alibguestfs-gobject-doc-1.28.1-1.55.el7_2.2.noarch.rpm9b013e31c028db5e1685767e03347ac6809735a746b54a8d4760f36a8294f350perl-Sys-Guestfs-1.28.1-1.55.el7_2.2.x86_64.rpm4b2453a9aef5343e176bcba148c710a33946c59829f2464e4f6fdf4fa48d5a2alibguestfs-rescue-1.28.1-1.55.el7_2.2.x86_64.rpm5c11d87418d179dec56b7c863c9c0be156a26e08e1ba508a4318328050f1a538libguestfs-devel-1.28.1-1.55.el7_2.2.x86_64.rpm6a18dbd5e2c0d934d6e84fa3ae35504173c02e840b89d46695460a059e9e8231libguestfs-man-pages-ja-1.28.1-1.55.el7_2.2.noarch.rpm5c3e287cb73ca0f42ba280d206e364b55c794f0b07602a483d9daf02182ba3b1libguestfs-gobject-devel-1.28.1-1.55.el7_2.2.x86_64.rpm355db5f89ae52d96735a419d1bee6c2a5c39a56d1a84dec41474ad7eebf1cc70libguestfs-java-1.28.1-1.55.el7_2.2.x86_64.rpm67c845e99d44054eeec00dfe65ae854eb0996f0186ff770ffac6cb1b3c4a08d6ruby-libguestfs-1.28.1-1.55.el7_2.2.x86_64.rpm5bf40d1cc7a77a04f42ba3b47859a5ba4585b2196569a3770ed5df699cff7cf0libguestfs-java-devel-1.28.1-1.55.el7_2.2.x86_64.rpmc37141f78a0639fc4cc65ae1a1a30c3ac9fe8d442afe5abfeffd04b3e4dd48e7libguestfs-rsync-1.28.1-1.55.el7_2.2.x86_64.rpm4757af3c2959c19426928759e26bb51bd47e2781dbd2b14f59bc90d3b3c252delibguestfs-bash-completion-1.28.1-1.55.el7_2.2.noarch.rpm939b4c4982abb923b39f1d992b4c17bdbc5484d651f7b78937552bd5ac9b61c4libguestfs-gfs2-1.28.1-1.55.el7_2.2.x86_64.rpm109cbe0e2acc4bba08259976c2ff852a100fdd61cb4f554d4aea71905f6f4325libguestfs-gobject-1.28.1-1.55.el7_2.2.x86_64.rpm9458994c7b6a7d938175f6688a3b05b079780c571171ca6640fbde4eaeb8bc7dlibguestfs-tools-1.28.1-1.55.el7_2.2.noarch.rpm434bd2c53dde1d2a67f83a9b1b8402fc3cc6cdaa1557a6715c7f2f956b1f41bbvirt-v2v-1.28.1-1.55.el7_2.2.x86_64.rpmf8b0ca4bb2fa79f0b15329bb34bcafadabbffbfb027b6f16e300b234e1e0acc7lua-guestfs-1.28.1-1.55.el7_2.2.x86_64.rpme1049bfa008416d3042b295e75c264b6559408f90eb3769065470ceb4f86d369libguestfs-tools-c-1.28.1-1.55.el7_2.2.x86_64.rpm68523304c4c1538c2e28b7ffab9c13515e96ce5403817b75a27a6d5dc8d5f3e5ocaml-libguestfs-1.28.1-1.55.el7_2.2.x86_64.rpm68c5c84d70331a24b135d9c230b36564dad4f7265f15b74e3143e692896d0675SLEA-2016:1297-1The openscap packages have been upgraded to upstream version 1.2.9, which provides a number of bug fixes and enhancements over the previous version. Most notably, this update adds support for scanning containers using the "atomic scan" command. In addition, this update includes the following enhancements: - the oscap-vm utility for offline scanning of virtual machines - the oscap-chroot utility for offline scanning of file systems mounted at arbitrary paths - full support for the Open Vulnerability and Assessment Language (OVAL) security language, version OVAL 5.11.1 - native support for remote.xml.bz2 files - grouping results in HTML reports according to various criteria - HTML report improvements - verbose mode for debugging OVAL evaluationScientific LinuxScientific Linux 7openscap-python-1.2.9-5.el7_2.x86_64.rpm6c7414b98935507ee0e209de3392df3048c0b77a6ba583f274953a7d9c463fe0openscap-devel-1.2.9-5.el7_2.i686.rpm815f475d39b593eda37f2f41c7a1b345c3c57413d0736f21f00bddd0300bcde6openscap-engine-sce-1.2.9-5.el7_2.x86_64.rpmef5a39d1a83a4267a9ce235beb9e1414e7a3846aa87d19147ba555b54a913682openscap-scanner-1.2.9-5.el7_2.x86_64.rpmf13babcb92e74d7380c473e79534dfad62fdfbd36d62df6c5323c0d80555ced0openscap-1.2.9-5.el7_2.x86_64.rpm0dcc7da7c6d316627511d84921cd9c5a823481e92be9b6862f0a63c54e1827e8openscap-devel-1.2.9-5.el7_2.x86_64.rpmbde29015148c319574dfabf8364b960994174a405197d6a252418b11c2d78699openscap-engine-sce-1.2.9-5.el7_2.i686.rpm649584f0e859bb009a143fb9ee982b6ccbc4cb2f88815ba65fcb0ff80bff77b2openscap-extra-probes-1.2.9-5.el7_2.x86_64.rpmaf08f7cea9e1acb95d3f7647a4d328e6f9066c5afdcff169515ec672a86cfd8copenscap-engine-sce-devel-1.2.9-5.el7_2.i686.rpma7227f06ee9cfdef8a48f52a098980183a657d9456ca5b2918d8c59f6571e66copenscap-utils-1.2.9-5.el7_2.x86_64.rpm8b536ac99fe9cf7a61b464eb4efd7390c003db15c9a558c50352842bd3087f6bopenscap-engine-sce-devel-1.2.9-5.el7_2.x86_64.rpm2dc8a9245c45542845c180bc063063699ce82f24438f462e865eb74ae949d8f3openscap-1.2.9-5.el7_2.i686.rpm420f74d57b9d3006cad0af7647762e89d5386a4a9087942d67913d4903ec682bSLEA-2016:1375-1The kmod-qla2xxx package contain the QLogic Fibre Channel HBA driver kernel module. Following is the list of PCI IDs supported by this package: 1077:2261 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-qla2xxx-8.07.00.33.07.3_k-1.el7_2.x86_64.rpm809ede0e9d5b91f20c8bddd43c2a330487d03da5928f75396951ed7df620ae93SLEA-2016:1388-1Prior to this update, the data files provided by the tzdata package reflected the Egyptian government's plan to transition to daylight saving time (DST) on July 7, but the Egyptian government canceled the planned transition. This update provides tzdata data files that reflect the change of plans, and will thus provide correct time zone information. This update also includes a time zone transition for Asia/Novosibirsk from +06 to +07 on 2016-07-24 at 02:00.Scientific LinuxScientific Linux 7tzdata-java-2016f-1.el7.noarch.rpm331c5af0e224468774885fd7c0b074f5b6ccb763bdbfbfb74579d04f5900206dtzdata-2016f-1.el7.noarch.rpm26fb8ceed93c90e7b1e1947b63308fce727f57374f92582c9d777fdc04972e78SLEA-2016:1390-1The kmod-rtsx_usb and kmod-rtsx_usb_sdmmc packages contain the Realtek USB card reader RTS5129/5179 driver kernel module. These packages add support for the Realtek RTS5129/5179 card reader. Following is the list of USB IDs supported by this package: -0BDA:0140d -0BDA:0139d -0BDA:0129d 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.Scientific LinuxScientific Linux 7kmod-rtsx_usb-0.1_rh1-1.el7_2.x86_64.rpm024522fb5a9972322057919a5a5b843285b841f4626db5d1492c7842070dd2a9kmod-rtsx_usb_sdmmc-0.1_rh1-1.el7_2.x86_64.rpmf3715bd5822871ebeda601d4e057af43dc2ed21e9d755fbf1f0a68cb5841049cSLEA-2016:1394-1The kmod-i40e, kmod-i40evf packages contain the update for the Intel Fortville NIC (i40e) core driver kernel module, which adds official support for the i40e LAN adapter. The PCI IDs supported by this package are 8086:1572, 8086:1584, and 8086:1581. * This enhancement update adds the kmod-i40e, kmod-i40evf packages to Scientific Linux 7. 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 these kernel modules are 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-i40evf-1.5.10_k-1.el7_2.x86_64.rpmd3398aa242c83362621af5ec958749c9432e39c6ec494c0dbe1ce936e6607a0dkmod-i40e-1.5.10_k-1.el7_2.x86_64.rpm60202b7fd97947e225c7e483f3b26b4b95cc23358d6f23a05210db2368903488SLEA-2016:1558-1The kmod-ixgbe packages contain a local area network (LAN) driver for the Ethernet X552 and X557 controllers on Intel Xeon v4 architectures, which provides support for the ixgbe LAN adapter. The PCI IDs supported by this package are: 8086:15AC 8086:15C2 8086:15C3 8086:15C4 8086:15C6 8086:15C7 8086:15CE 8086:15D1 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.Scientific LinuxScientific Linux 7kmod-ixgbe-4.4.0_k-1.el7_2.x86_64.rpm95f1f2fb6210dd9dd5bdeef661a768e6cac06b248e90dcbc89921c8d5febf1abSLEA-2016:1559-1The kmod-bnx2x packages contain the QLogic NetXtreme II 10GbE Networking core driver kernel module, which adds official support for the bnx2x LAN adapter. The PCI IDs supported by this package are 1077:16A1, 1077:16A4, and 1077:16AD. 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.Scientific LinuxScientific Linux 7kmod-bnx2x-firmware-1.712.30-1.el7_2.x86_64.rpmc8db79282a5228f025ea36e2fce426adf1306605215aa0dbd317c2eca9da8581kmod-bnx2x-1.712.30-1.el7_2.x86_64.rpm253ce7c73d6938cea177013dca8d732e9ca5e495c227b01a839e9f28e1af877eSLEA-2016:1780-1The kmod-megaraid_sas packages contain the Avago MegaRAID SAS Driver kernel module, which adds official support for the megaraid_sas devices.The PCI IDs supported by this package are 1000:0052, 1000:0053, 1000:00CE, 1000:00CF. 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.Scientific LinuxScientific Linux 7kmod-megaraid_sas-06.811.02.00-1.el7_2.x86_64.rpme6f76bb6459fa386586f153d4ce85aa33c683686d3fb25fac94f6e61253a073cSLEA-2016:1902-1The kmod-i40e and kmod-i40evf packages contain an update for the Intel ethernet connection XL710 network driver kernel module, which adds official support for the i40e LAN adapter and the i40evf driver that provides virtual functions for this adapter. The PCI IDs supported by these packages are 8086:1572, 8086:1584, and 8086:1581. * This enhancement update adds the kmod-i40e and kmod-i40evf packages to Scientific Linux 7. 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 these kernel modules are 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-i40evf-1.5.10_k-2.el7_2.x86_64.rpm6e0067b63a5d7abf395d054cd1c9765333c39001bee20a0942b3e0b220aaf925kmod-i40e-1.5.10_k-2.el7_2.x86_64.rpm8501f2e94892353fbe247e0b5bcc79afaf9d0d288c7490035690d5eccf10f2c4SLEA-2016:1975-1The kmod-lpfc packages contain the Emulex LightPulse Fibre Channel SCSI driver kernel module, which adds official support for the lpfc devices. The PCI ID supported by this package is 10DF:E300. 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.Scientific LinuxScientific Linux 7kmod-lpfc-11.1.0.2-1.el7_2.x86_64.rpm69a0f655547bc11fe72c652c5a703628ebedf4de01f3dd6fedc13044f95c0783SLEA-2016:1976-1The kmod-bnxt_en packages contain the Broadcom BCM573xx network driver kernel module, which adds official support for the bnxt_en devices. The PCI IDs supported by this package are: 14E4:16C8 14E4:16C9 14E4:16CA 14E4:16CE 14E4:16CF 14E4:16D0 14E4:16D1 14E4:16D2 14E4:16D4 14E4:16D6 14E4:16D7 14E4:16D8 14E4:16D9 14E4:16DE 14E4:16DF 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.Scientific LinuxScientific Linux 7kmod-bnxt_en-1.2.0-2.el7_2.x86_64.rpm7d7c1559301bcb7a701e851f5347a532713916e07c4b1a82571293b1b9c0be79SLEA-2016:1977-1The kmod-sfc packages contain the Solarflare network driver kernel module, which adds official support for the sfc devices. The PCI IDs supported by this package are 1924:0A03, 1924:1923, 1924:1A03. 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.Scientific LinuxScientific Linux 7kmod-sfc-4.0-1.el7_2.x86_64.rpmfc40be075a83612bcf4721d3cd42e6f32be16e144ed9dca20d20fd8dd817958a