hi, thanks to Justin for providing me access to his environment, I managed to debug it live and find 2 issues: - first issue is for web-admin portal which from some reason has timeouts for createStorageDomain command set to 1 minute (where timeout should be 3 minutes and set in the engine-core). - second issue (more disturbing) is a deadlock in super-vdsm (it goes into defunct state) operation which prevents reading\writing storage domain metadata as a part of createStorageDomain thread.
I will file 2 bz for those issues, Haim ----- Original Message ----- > From: "Yaniv Kaul" <[email protected]> > To: "Justin Clift" <[email protected]> > Cc: "users" <[email protected]> > Sent: Thursday, August 9, 2012 9:18:59 AM > Subject: Re: [Users] Status code 500 when adding first storage domain? > > > > Engine log, and possibly VDSM log, would be most helpful. > Y. > > > > > Hi all, > > > Is anyone else experiencing this error, when adding the > first storage domain to a new oVirt 3.1 environment? > > > "Error: A Request to the Server failed with the following Status > Code: 500" > > > Screenshot attached. > > > > > > The environment here has 1 x host server and 1 x engine server. > > > It's using the new oVirt 3.1 ISO, and the rpms's obtained by > following the "Get It" instructions. > > > The storage is NFS, and is known to work. > > > Other useful data points: > > > * Forward and reverse DNS is 100% working for everything. > > > * On some level, the NFS mounting is working. oVirt even > creates its uuid looking data structure inside the mount > point before giving this error. > > > * If I log in to the host remotely, manually mounting the > NFS share from the command line is flawless. Works > immediately. > > > * In the above screenshot, the storage domain is even > shown in the background behind the error message. oVirt > seems to actively remove it after the error message > though. > > > It kind of feels like a timeout thing, as after the initial > mount and creation of UUID on the NFS share, there's a 30-ish > period of inactivity then this error is displayed. > > > Any ideas? > > > Regards and best wishes, > > > Justin Clift > > > > -- > Aeolus Community Manager > http://www.aeolusproject.org > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
