Hide Forgot
Created attachment 810917 [details] cpu details info Description of problem: Can't show cpu details info after upgrade from 6.4 to 6.5 Version-Release number of selected component (if applicable): rhev-hypervisor6-6.5-20130930.0.auto665 rhev-hypervisor6-6.4-20131003.0.el6_4 How reproducible: 100% Steps to Reproduce: 1. Install rhev-hypervisor6-6.4-20131003.0.el6_4 2. Upgrade to 6.5 via TUI. 3. login 6.5 and enter "view cpu details" menu. Actual results: "Failed to Establish Libvirt Connection" pop-up. Expected results: Hypervisor can show the correct cpu details info after upgrade from 6.4 to 6.5 Additional info:
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
Can't reproduce. Can I get details on your environment, please?
Add keyword "Regression" due to no such issue in RHEV-H 6.4.
Is this working in permissive mode? It could be something blocked by dontaudit rules. semodule -DB Will disable them. semodule -B Will enable them.
Daniel: Not sure if it works in permissive mode or not. It appears to only fail during a very brief window, and both networking and libvirtd worked as expected (after starting libvirtd). I'll see about dontaudiot cshao: I'm still not able to reproduce this, but I think I have a better idea of what's happening. What steps did you take to get here? Install 6.4 ???? Configure Networking ????? Upgrade Doesn't work I'm hoping to get closer to your workflow so I can reproduce in an environment where I debug init at the point where name resolution fails.
(In reply to Ryan Barry from comment #11) > Daniel: > > Not sure if it works in permissive mode or not. It appears to only fail > during a very brief window, and both networking and libvirtd worked as > expected (after starting libvirtd). I'll see about dontaudiot > > cshao: > > I'm still not able to reproduce this, but I think I have a better idea of > what's happening. What steps did you take to get here? > > Install 6.4 > ???? > Configure Networking > ????? > Upgrade > Doesn't work > > I'm hoping to get closer to your workflow so I can reproduce in an > environment where I debug init at the point where name resolution fails. Test step: 1. Install 6.4 and set password as "r" 2. configure network. 3. reboot 4. TUI upgrade to 6.5 5. Set password as "123qweP!@#" 6. reboot 7. login 6.5 and check cpu details info
*** Bug 1017132 has been marked as a duplicate of this bug. ***