Bug 1134315
| Summary: | ovirt-guest-agent installed on Win7-32bit,but SSO not work | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | rainmarks <rainmarks> | ||||
| Component: | ovirt-guest-agent | Assignee: | Vinzenz Feenstra [evilissimo] <vfeenstr> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Belka <jbelka> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.4 | CC: | ecohen, gklein, iheim, oourfali, rbalakri, Rhev-m-bugs, yeylon | ||||
| Target Milestone: | --- | Keywords: | Triaged | ||||
| Target Release: | 3.5.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | virt | ||||||
| Fixed In Version: | ovirt-engine 3.5 rc1 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-10-17 12:29:50 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
rainmarks
2014-08-27 09:39:10 UTC
There's a limitation in the 3.4 engine (which has been changed for 3.5) that it checks for the guest agent application to be installed. However since the naming of the guest agent varies that much upstream, I have posted a patch for this in 3.5 that it does no longer require the application to be present when sending the login info. To me it looks like that this is the cause of the SSO issue, since the engine is not even sending the information at all. ovirt engine 3.5 has fixed this issue and the SSO should work @rainmarks: If you would like to verify this with the ovirt-3.5 rc1, please also beware that there's a known issue on Windows 7 x86 that a policy in the registry has to be set for SSO to work with secure logon. The policy is located at: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System There should be a REG_DWORD value with the name SoftwareSASGeneration and the value 3 If this is not present please set it, and if it is present set the value to either 1 or 3 Thanks. Thanks very mutch. it seems not a hard problem. Is there any simple way to let the ovirt-guest-agent sso work in 3.4 engin? Thanks very mutch. it seems not a hard problem. Is there any simple way to let the ovirt-guest-agent sso work in 3.4 engin? Excuse me again, if it's convenient could you tell me which files modified in voirt-engine src? I want to compare the code have a look what the problem is. Thanks very match。 (In reply to Vinzenz Feenstra [evilissimo] from comment #1) > There's a limitation in the 3.4 engine (which has been changed for 3.5) that > it checks for the guest agent application to be installed. However since the > naming of the guest agent varies that much upstream, I have posted a patch > for this in 3.5 that it does no longer require the application to be present > when sending the login info. > > To me it looks like that this is the cause of the SSO issue, since the > engine is not even sending the information at all. > > ovirt engine 3.5 has fixed this issue and the SSO should work ok # systemctl list-unit-files | egrep "qemu|ovirt" ovirt-guest-agent.service enabled qemu-guest-agent.service static ooops, bad tab :) oVirt 3.5 has been released and should include the fix for this issue. |