2:03 p.m.
The oVirt team is pleased to announce that the 3.3.1 Release is now
available in beta.
Release notes for this update are still being worked on, but information
on the changes can be found on the wiki[1].
A new oVirt Node build will be available soon as well.
Mike
[1] http://www.ovirt.org/OVirt_3.3.1_release_notes
11:48 p.m.
I hit a bump upgrading from 3.3.0.1:
2013-10-18 16:38:14 DEBUG otopi.plugins.ovirt_engine_setup.db.schema
plugin.execute:446 execute-output:
['/usr/share/ovirt-engine/dbscripts/upgrade.sh', '-s',
'localhost',
'-p', '5432', '-u', 'engine', '-d',
'engine', '-l',
'/var/log/ovirt-engine/setup/ovirt-engine-setup-20131018163438.log',
'-g'] stderr:
psql:create_views.sql:400: ERROR: column vm_templates.single_qxl_pci
does not exist
LINE 18: vm_templates.single_qxl_pci as single_qxl_pci,
^
2013-10-18 16:38:14 DEBUG otopi.context context._executeMethod:137
method exception
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/otopi/context.py", line 127, in
_executeMethod
method['method']()
File
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/db/schema.py",
line 261, in _miscUpgrade
osetupcons.DBEnv.PGPASS_FILE
File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in
execute
command=args[0],
RuntimeError: Command '/usr/share/ovirt-engine/dbscripts/upgrade.sh'
failed to execute
2013-10-18 16:38:14 ERROR otopi.context context._executeMethod:146
Failed to execute stage 'Misc configuration': Command
'/usr/share/ovirt-engine/dbscripts/upgrade.sh' failed to execute
----- Original Message -----
From: "Mike Burns" <mburns(a)redhat.com>
To: announce(a)ovirt.org, "users" <users(a)ovirt.org>
Sent: Friday, October 18, 2013 4:03:38 AM
Subject: [Users] oVirt 3.3.1 Beta now available
The oVirt team is pleased to announce that the 3.3.1 Release is now
available in beta.
Release notes for this update are still being worked on, but information
on the changes can be found on the wiki[1].
A new oVirt Node build will be available soon as well.
Mike
[1] http://www.ovirt.org/OVirt_3.3.1_release_notes
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
9:57 p.m.
Some further 3.3.1 beta tests:
Since I wasn't able to upgrade from 3.3.0.1 (seems related to bz1005533)
I did a fresh install of 3.3.1 beta on F19 -- an AIO install. That
worked fine, but I wasn't able to add an additional host, and tried with
F19 and CentOS 6.4. In both cases, engine complained of:
"java.io.IOException: Unexpected connection termination"
I tried installing an 3.3.1 AIO on CentOS 6.4 but hit a dependency
issue:
Error: Package: vdsm-4.13.0-2.gitbae164c.el6.x86_64 (ovirt-beta)
Requires: selinux-policy-targeted >= 3.7.19-213
Installed: selinux-policy-targeted-3.7.19-195.el6_4.12.noarch
(@updates)
I did a clean install of a non-AIO engine on CentOS 6.4, but wasn't able
to add a host due to the selinux issue (w/ CentOS) and the "Unexpected
connection termination" (w/ F19).
So, so far, F19 AIO w/ no additional hosts is the only 3.3.1 config I've
managed to get working.
Jason
On Fri, 2013-10-18 at 13:48 -0700, Jason Brooks wrote:
I hit a bump upgrading from 3.3.0.1:
2013-10-18 16:38:14 DEBUG otopi.plugins.ovirt_engine_setup.db.schema
plugin.execute:446 execute-output:
['/usr/share/ovirt-engine/dbscripts/upgrade.sh', '-s',
'localhost',
'-p', '5432', '-u', 'engine', '-d',
'engine', '-l',
'/var/log/ovirt-engine/setup/ovirt-engine-setup-20131018163438.log',
'-g'] stderr:
psql:create_views.sql:400: ERROR: column vm_templates.single_qxl_pci
does not exist
LINE 18: vm_templates.single_qxl_pci as single_qxl_pci,
^
2013-10-18 16:38:14 DEBUG otopi.context context._executeMethod:137
method exception
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/otopi/context.py", line 127, in
_executeMethod
method['method']()
File
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/db/schema.py",
line 261, in _miscUpgrade
osetupcons.DBEnv.PGPASS_FILE
File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in
execute
command=args[0],
RuntimeError: Command '/usr/share/ovirt-engine/dbscripts/upgrade.sh'
failed to execute
2013-10-18 16:38:14 ERROR otopi.context context._executeMethod:146
Failed to execute stage 'Misc configuration': Command
'/usr/share/ovirt-engine/dbscripts/upgrade.sh' failed to execute
----- Original Message -----
> From: "Mike Burns" <mburns(a)redhat.com>
> To: announce(a)ovirt.org, "users" <users(a)ovirt.org>
> Sent: Friday, October 18, 2013 4:03:38 AM
> Subject: [Users] oVirt 3.3.1 Beta now available
>
> The oVirt team is pleased to announce that the 3.3.1 Release is now
> available in beta.
>
> Release notes for this update are still being worked on, but information
> on the changes can be found on the wiki[1].
>
> A new oVirt Node build will be available soon as well.
>
> Mike
>
>
> [1] http://www.ovirt.org/OVirt_3.3.1_release_notes
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
3:30 a.m.
On 10/19/2013 08:57 PM, Jason Brooks wrote:
Some further 3.3.1 beta tests:
Since I wasn't able to upgrade from 3.3.0.1 (seems related to bz1005533)
I did a fresh install of 3.3.1 beta on F19 -- an AIO install. That
worked fine, but I wasn't able to add an additional host, and tried with
F19 and CentOS 6.4. In both cases, engine complained of:
"java.io.IOException: Unexpected connection termination"
I tried installing an 3.3.1 AIO on CentOS 6.4 but hit a dependency
issue:
Error: Package: vdsm-4.13.0-2.gitbae164c.el6.x86_64 (ovirt-beta)
Requires: selinux-policy-targeted >= 3.7.19-213
Installed: selinux-policy-targeted-3.7.19-195.el6_4.12.noarch
(@updates)
You could try the latest SELinux packages available here:
http://people.redhat.com/dwalsh/SELinux/RHEL6/noarch/
Regards,
Patrick
8:16 a.m.
On Sat, Oct 19, 2013 at 11:57:38AM -0700, Jason Brooks wrote:
Some further 3.3.1 beta tests:
Since I wasn't able to upgrade from 3.3.0.1 (seems related to bz1005533)
I did a fresh install of 3.3.1 beta on F19 -- an AIO install. That
worked fine, but I wasn't able to add an additional host, and tried with
F19 and CentOS 6.4. In both cases, engine complained of:
"java.io.IOException: Unexpected connection termination"
I tried installing an 3.3.1 AIO on CentOS 6.4 but hit a dependency
issue:
Error: Package: vdsm-4.13.0-2.gitbae164c.el6.x86_64 (ovirt-beta)
Requires: selinux-policy-targeted >= 3.7.19-213
Installed: selinux-policy-targeted-3.7.19-195.el6_4.12.noarch
(@updates)
I did a clean install of a non-AIO engine on CentOS 6.4, but wasn't able
to add a host due to the selinux issue (w/ CentOS) and the "Unexpected
connection termination" (w/ F19).
So, so far, F19 AIO w/ no additional hosts is the only 3.3.1 config I've
managed to get working.
Thanks for opening a bug on this
https://bugzilla.redhat.com/show_bug.cgi?id=1021147
It blocks on
Bug 1015068 - Current selinux policy prevents running a VM with
volumes under /var/run/vdsm/storage
which frankly - I do not know what holds.
On the mean time, the only remedy I have is to --force vdsm's
installation before firing AIO and to manually tweak the policy with
sudo semanage fcontext -a -s system_u -t virt_var_run_t -r s0 '/var/run/vdsm(/.*)
6:19 p.m.
----- Original Message -----
From: "Jason Brooks" <jbrooks(a)redhat.com>
To: "users" <users(a)ovirt.org>
Sent: Saturday, October 19, 2013 11:57:38 AM
Subject: Re: [Users] oVirt 3.3.1 Beta now available
Some further 3.3.1 beta tests:
Since I wasn't able to upgrade from 3.3.0.1 (seems related to
bz1005533)
I did a fresh install of 3.3.1 beta on F19 -- an AIO install. That
worked fine, but I wasn't able to add an additional host, and tried
with
F19 and CentOS 6.4. In both cases, engine complained of:
"java.io.IOException: Unexpected connection termination"
Bit of an update:
Adding a host to an F19 engine fails because of
https://bugzilla.redhat.com/show_bug.cgi?id=1021273 and you can work
around it with yum downgrade apache-sshd.
There's no problem adding a new host to a CentOS-based engine. On that
test, I simply forgot to install the ovirt-release package, which pulls
in tar, and the absence of tar is what caused the "Unexpected connection
termination."
I tried installing an 3.3.1 AIO on CentOS 6.4 but hit a dependency
issue:
Error: Package: vdsm-4.13.0-2.gitbae164c.el6.x86_64 (ovirt-beta)
Requires: selinux-policy-targeted >= 3.7.19-213
Installed:
selinux-policy-targeted-3.7.19-195.el6_4.12.noarch
(@updates)
I did a clean install of a non-AIO engine on CentOS 6.4, but wasn't
able
to add a host due to the selinux issue (w/ CentOS) and the
"Unexpected
connection termination" (w/ F19).
So, so far, F19 AIO w/ no additional hosts is the only 3.3.1 config
I've
managed to get working.
Jason
On Fri, 2013-10-18 at 13:48 -0700, Jason Brooks wrote:
> I hit a bump upgrading from 3.3.0.1:
>
> 2013-10-18 16:38:14 DEBUG otopi.plugins.ovirt_engine_setup.db.schema
> plugin.execute:446 execute-output:
> ['/usr/share/ovirt-engine/dbscripts/upgrade.sh', '-s',
'localhost',
> '-p', '5432', '-u', 'engine', '-d',
'engine', '-l',
> '/var/log/ovirt-engine/setup/ovirt-engine-setup-20131018163438.log',
> '-g'] stderr:
> psql:create_views.sql:400: ERROR: column
vm_templates.single_qxl_pci
> does not exist
> LINE 18: vm_templates.single_qxl_pci as single_qxl_pci,
> ^
>
> 2013-10-18 16:38:14 DEBUG otopi.context context._executeMethod:137
> method exception
> Traceback (most recent call last):
> File "/usr/lib/python2.7/site-packages/otopi/context.py", line
127, in
> _executeMethod
> method['method']()
> File
>
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/db/schema.py",
> line 261, in _miscUpgrade
> osetupcons.DBEnv.PGPASS_FILE
> File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451,
in
> execute
> command=args[0],
> RuntimeError: Command '/usr/share/ovirt-engine/dbscripts/upgrade.sh'
> failed to execute
> 2013-10-18 16:38:14 ERROR otopi.context context._executeMethod:146
> Failed to execute stage 'Misc configuration': Command
> '/usr/share/ovirt-engine/dbscripts/upgrade.sh' failed to execute
>
>
>
> ----- Original Message -----
> > From: "Mike Burns" <mburns(a)redhat.com>
> > To: announce(a)ovirt.org, "users" <users(a)ovirt.org>
> > Sent: Friday, October 18, 2013 4:03:38 AM
> > Subject: [Users] oVirt 3.3.1 Beta now available
> >
> > The oVirt team is pleased to announce that the 3.3.1 Release is
now
> > available in beta.
> >
> > Release notes for this update are still being worked on, but
information
> > on the changes can be found on the wiki[1].
> >
> > A new oVirt Node build will be available soon as well.
> >
> > Mike
> >
> >
> > [1] http://www.ovirt.org/OVirt_3.3.1_release_notes
> > _______________________________________________
> > Users mailing list
> > Users(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
11:17 p.m.
Am Freitag, den 18.10.2013, 07:03 -0400 schrieb Mike Burns:
The oVirt team is pleased to announce that the 3.3.1 Release is now
available in beta.
Release notes for this update are still being worked on, but information
on the changes can be found on the wiki[1].
A new oVirt Node build will be available soon as well.
Hey,
the patches for the oVirt Node image are ready. We are currently waiting
for the selinux-policy-targeted >= 3.7.19-213 on EL6 to land.
We will give this a couple of days.
Greetings
fabian
4049
days inactive
4053
days old
6 comments
5 participants
participants (5)
-
Dan Kenigsberg -
Fabian Deutsch -
Jason Brooks -
Mike Burns -
Patrick Lists