Bug 1076457
| Summary: | SSO not functional with or without guest agent | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Lukas Svaty <lsvaty> | ||||||
| Component: | ovirt-engine | Assignee: | Nobody <nobody> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Lukas Svaty <lsvaty> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 3.4.0 | CC: | acathrow, cpelland, gklein, iheim, lpeer, lsvaty, michal.skrivanek, ofrenkel, Rhev-m-bugs, vfeenstr, yeylon | ||||||
| Target Milestone: | --- | Keywords: | TestBlocker, Triaged | ||||||
| Target Release: | 3.4.0 | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | virt | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-03-20 13:47:14 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 758946 | ||||||||
| Attachments: |
|
||||||||
|
Description
Lukas Svaty
2014-03-14 11:40:27 UTC
please attach engine and vdsm log guest agent logs as well. and details about the guest setup Created attachment 876363 [details]
vdsm log of host
Created attachment 876365 [details]
engine log
Nothing was logged into /var/log/ovirt-guest-agent/ovirt-guest-agent.log Added vdsm and engine log of actions: Log to user portal with admin@internal StartVM Wait for VM status UP Open Spice console restart GA in VM Close Spice console Open Spice console (In reply to Lukas Svaty from comment #6) "Nothing was logged into /var/log/ovirt-guest-agent/ovirt-guest-agent.log " nothing? so...was the agent running at all? My last log around time I was testing it on engine: /var/log/ovirt-guest-agent/ovirt-guest-agent.log MainThread::INFO::2014-03-13 17:12:39,089::ovirt-guest-agent::55::root::oVirt guest agent is down. <- 6 days ago (nothing from todays tests) in VM service ovirt-guest-agent status: running After some configuration (no gdm installed previously) I got to this result: VmLoggon is called, however user is not logged to VM engine: 2014-03-20 13:26:22,464 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp-/127.0.0.1:8702-4) [6756e574] START, SetVmTicketVDSCommand(HostName = blue, HostId = 4118c061-331f-4983-9199-6bd269faae9b, vmId=e6b03061-7a3b-46f4-9fff-a786b9d501d9, ticket=4ENIygOvv+Zv, validTime=120,m userName=vdcadmin2, userId=8fb38dc7-6cc3-4678-bffe-bf9fbefbf839), log id: 6f9ad185 2014-03-20 13:26:22,521 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp-/127.0.0.1:8702-4) [6756e574] FINISH, SetVmTicketVDSCommand, log id: 6f9ad185 2014-03-20 13:26:22,541 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp-/127.0.0.1:8702-4) [6756e574] Correlation ID: 6756e574, Call Stack: null, Custom Event ID: -1, Message: user vdcadmin2 initiated console session for VM a 2014-03-20 13:26:22,577 WARN [org.ovirt.engine.core.dal.job.ExecutionMessageDirector] (ajp-/127.0.0.1:8702-7) [1beaf8be] The message key VmLogon is missing from bundles/ExecutionMessages 2014-03-20 13:26:22,633 INFO [org.ovirt.engine.core.bll.VmLogonCommand] (ajp-/127.0.0.1:8702-7) [1beaf8be] Running command: VmLogonCommand internal: false. Entities affected : ID: e6b03061-7a3b-46f4-9fff-a786b9d501d9 Type: VM 2014-03-20 13:26:22,637 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.VmLogonVDSCommand] (ajp-/127.0.0.1:8702-7) [1beaf8be] START, VmLogonVDSCommand(HostName = blue, HostId = 4118c061-331f-4983-9199-6bd269faae9b, vmId=e6b03061-7a3b-46f4-9fff-a786b9d501d9, domain=ad2.rhev.lab.eng.brq.redhat.com, password=******, userName=vdcadmin2), log id: 6427ebd8 2014-03-20 13:26:22,642 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.VmLogonVDSCommand] (ajp-/127.0.0.1:8702-7) [1beaf8be] FINISH, VmLogonVDSCommand, log id: 6427ebd8 guest-agent in vm: Dummy-1::INFO::2014-03-20 13:26:22,640::OVirtAgentLogic::169::root::Received an external command: login... Dummy-1::INFO::2014-03-20 13:26:22,640::CredServer::207::root::The following users are allowed to connect: [0] Dummy-1::INFO::2014-03-20 13:26:22,640::CredServer::273::root::Opening credentials channel... Dummy-1::INFO::2014-03-20 13:26:22,640::CredServer::132::root::Emitting user authenticated signal (718271). CredChannel::INFO::2014-03-20 13:26:27,646::CredServer::241::root::Credentials channel timed out. Dummy-1::INFO::2014-03-20 13:26:27,646::CredServer::277::root::Credentials channel was closed. You have not being logged in because you did not start gdm correctly and SELINUX blocked you. Once on runlevel5 and gdm is started the right way the SSO works on your setup. Verified this with suggested config. CLOSED -> NOTABUG |