[Users] [Engine-devel] oVirt 3.4.0 beta is now available

[Sandro Bonazzola]

Il 23/01/2014 03:19, Douglas Schilling Landgraf ha scritto:
> On 01/22/2014 03:00 PM, Eli Mesika wrote:
>>
>>
>> ----- Original Message -----
>>> From: "Eli Mesika" <emesika at redhat.com>
>>> To: dougsland at redhat.com
>>> Cc: "engine-devel" <engine-devel at ovirt.org>, Users at ovirt.org
>>> Sent: Wednesday, January 22, 2014 9:48:54 PM
>>> Subject: Re: [Users] [Engine-devel] oVirt 3.4.0 beta is now available
>>>
>>>
>>>
>>> ----- Original Message -----
>>>> From: "Douglas Schilling Landgraf" <dougsland at redhat.com>
>>>> To: "Eli Mesika" <emesika at redhat.com>, "Sandro Bonazzola"
>>>> <sbonazzo at redhat.com>
>>>> Cc: "engine-devel" <engine-devel at ovirt.org>, Users at ovirt.org
>>>> Sent: Wednesday, January 22, 2014 9:31:59 PM
>>>> Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available
>>>>
>>>> Hi Eli,
>>>>
>>>> On 01/22/2014 01:10 PM, Eli Mesika wrote:
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>>> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
>>>>>> To: "Martin Perina" <mperina at redhat.com>
>>>>>> Cc: "engine-devel" <engine-devel at ovirt.org>, Users at ovirt.org
>>>>>> Sent: Wednesday, January 22, 2014 5:01:55 PM
>>>>>> Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available
>>>>>>
>>>>>> Il 22/01/2014 15:49, Martin Perina ha scritto:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I tried to install on F19, but openstack* packages >= 3.0.2 are
>>>>>>> missing:
>>>>>>
>>>>>> thanks, updated release page, it needs updates-testing
>>>>>
>>>>> I had enabled ovirt-updates-testing and still got this :
>>>>
>>>> Here it worked, without looking your 'yum repolist' output I do guess
>>>> you need to enable the repo from:
>>>> /etc/yum.repos.d/fedora-updates-testing.repo
>>>
>>>
>>> Thanks, I enabled ovirt-updates-testing in ovirt repo ..... :-(
>>
>> engine-setup fails with the following error
>>
>> Failed to execute stage 'Misc configuration': Command '/bin/systemctl' failed to execute
>>
>> any ideas ?
>>
> Hi Eli,
> 
> Would be nice too see your engine-setup log file to determine which error happened. Should be available here:  /var/log/ovirt-engine/setup/
> 
> Anyway, I could reproduce a similar output during a setup (below the log) and in my case was postgresql with error: "FATAL:  could not create shared
> memory segment: Invalid argument"
> 
> Resolved with wiki:
> http://www.ovirt.org/Troubleshooting#Installation
> 
> In session:
> "I am having trouble connecting to the database. In the system log, I get the following message from Postgres"
> 
> @Sandro, should or maybe installer detect this kind of situation?

Seems like http://www.ovirt.org/OVirt_3.4.0_release_notes#Known_issues

On Fedora 19 with recent versions of PostgreSQL it may be necessary to manually change kernel.shmmax settings (BZ 1039616)

Please try:

# engine-setup --otopi-environment="OVESETUP_SYSTEM/shmmax=int:68719476736"



> 
> =========================
> 
> 2014-01-22 17:37:52 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:446 execute-output: ('/bin/systemctl', 'start', 'postgresql.service')
> stderr:
> Job for postgresql.service failed. See 'systemctl status postgresql.service' and 'journalctl -xn' for details.
> 
> 2014-01-22 17:37:52 DEBUG otopi.context context._executeMethod:152 method exception
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in _executeMethod
>     method['method']()
>   File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/provisioning/postgres.py", line 182, in _misc
>     self._provisioning.provision()
>   File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/postgres.py", line 552, in provision
>     self._restart()
>   File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/postgres.py", line 407, in _restart
>     state=state,
>   File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 138, in state
>     'start' if state else 'stop'
>   File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 77, in _executeServiceCommand
>     raiseOnError=raiseOnError
>   File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in execute
>     command=args[0],
> RuntimeError: Command '/bin/systemctl' failed to execute
> 2014-01-22 17:37:52 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Misc configuration': Command '/bin/systemctl' failed to
> execute
> 2014-01-22 17:37:52 DEBUG otopi.transaction transaction.abort:131 aborting 'Yum Transaction'
> 2014-01-22 17:37:52 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:92 Yum Performing yum transaction rollback
> Loaded plugins: versionlock
> 
> 


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com