Description of problem: While new kernel for namespace is needed in rhel 6.4 followed by hosts reboot, in rhel 6.5 it is not needed since kernel support namespace. We need to remove the following message from packstack when using rhel 6.5 "Kernel package with netns support has been installed on host 10.35.160.19. Because of the kernel update the host mentioned above requires reboot " Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.install neutron with packstack on rhel 6.5 2. 3. Actual results: Expected results: Additional info:
According to Martin this was fixed already. Now the message is only displayed when the new kernel has been installed.
Auto adding >= MODIFIED bugs to beta
Ofer, could you please reproduce it again and provide us the packstack and puppet logs to make sure the kernel wasn't actually installed. If it were installed, this wouldn't actually be a bug.
Ofer, note that the reboot message is not still there for one use-case: Kernel was updated but was not loaded, eg. uname -a shows old kernel, but rpm -qa shows newer package. This is exactly your case, citation: root@puma04 ~]# rpm -qa | grep kernel kernel-2.6.32-431.el6.x86_64 libreport-plugin-kerneloops-2.0.9-19.el6.x86_64 kernel-2.6.32-420.el6.x86_64 .... [root@puma04 ~]# uname -a Linux puma04.scl.lab.tlv.redhat.com 2.6.32-420.el6.x86_64 #1 SMP Mon Sep 23 11:00:49 ... "It seems the message is there, also we have two kernels installed why ?" Answer: When new kernel package is installed, usually old stays as fallback in case the new one will fail to boot. Setting back to ON_QA. First update kernel (with all necessary repos installed first), reboot and then run packstack. If rpm -qa shows the same newest kernel package as uname do, then this bug fails qa ... otherwise set to verified.
... and just to be sure: also if the reboot message is shown
You are correct, i have updated the kernel rebooted the hosts and installed packstack , no message appear
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-1859.html