Dne 30.7.2013 00:19, Eli Mesika napsal(a):
Hi
Attached please find the presentation slides
This session was recorded. To view the recording, please click the link below:
https://sas.elluminate.com/p.jnlp?psid=2013-07-29.0638.M.0095240B0C736D2B11BF860A1F0376.vcrsid=819
Hi Eduardo,
Can u please also add the engine log and the full VDSM log (if you have
other hosts then please add their vdsm.log as well)
Thanks.
Maor
On 07/29/2013 11:10 PM, Eduardo Ramos wrote:
Hi all!
My SPM has logging such a strange message on vdsm.log. I tries to get
information from a
On 07/29/2013 06:06 PM, Nicholas Kesick wrote:
Date: Mon, 29 Jul 2013 09:56:30 +0200
From: mklet...@redhat.com
To: dan...@redhat.com
CC: cybertimber2...@hotmail.com; users@ovirt.org
Subject: Re: [Users] oVirt 3.2 - Migration failed due to error: migrateerr
On 07/27/2013 09:50 PM, Dan
Thanks.
So this leads me further to the upgrade procedure
which may have fail, thus not completing the DB upgrade.
Can you please check the upgrade logs to see if something
matches this flow?
- Original Message -
| From: Dead Horse deadhorseconsult...@gmail.com
| To: Doron Fediuck
Hi,
we currently run F18 based nodes as oVirt 3.2.1 HVs.
For installation it was necessary to have internet access for the nodes during
the triggered setup from engine server.
Which repo does the engine/HV need to make an offline installation possible:
Hi All,
Because of discussion on IRC I'll make a RFE for the following:
When you have lots (25) ISCSI LUN's where your ovirt hosts have
access to then the selection window gets really messy because there
is no apparent sorting on LUN ids or a searching possibility
Hello,
I have an ovirt cluster which runs CentOS VM. I have a template to
create VM. On this template, there are two interfaces, eth0 and eth1.
When I create a VM using this template, the new interfaces are named
eth2 and eth3. It can be pretty annoying and I would like to know if it
would be
Hi
You have toremove HWADDR value from theifcfg-ethX and rules string
from /etc/udev/rules.d/70-persistent-net.rules files.
It'll work fine if you have only one NIC per machine.
--
Best regards, Pavel Zhukov
Software Maintenance Engineer
RHCE, RHCVA
Tel: +420.532294671
Hello All,
Starting the discussion again...
I would like to receive feedback regarding how we should cope with a state
presented to use by Fedora.
Fedora-19 minimal setup does not install tar utility which is required to
deploy files during the host-deploy process (Hosts-Add Host).
I guess
Hi,
The easiest way is to remove 70-persistent-net.rules in your master-vm,
remove HWADDR-strings from ifcfg-eth* friles, shut it down and create
the template.
Btw, also remove your ssh-keys in your template to create unique ones
for each vm...
Regards,
René
On Tue, 2013-07-30 at 14:59
On Tue, 2013-07-30 at 08:01 -0400, Sven Knohsalla wrote:
Hi,
we currently run F18 based nodes as oVirt 3.2.1 HVs.
For installation it was necessary to have internet access for the
nodes during the triggered setup from engine server.
Which repo does the engine/HV need to make an
Hi Joop, sounds great.
Can u please just send an update of the BZ number which was opened,just
to have it scrubbed more quickly.
Thanks,
Maor
On 07/30/2013 03:00 PM, noc wrote:
Hi All,
Because of discussion on IRC I'll make a RFE for the following:
When you have lots (25) ISCSI LUN's where
Hi,
there's already an RFE for supporting column sorting in main/sub tab grids:
https://bugzilla.redhat.com/893999
The above mentioned RFE could be generalized to support all grids, including
the ones found in dialogs, such as Add Virtual Disk dialog. However, we need
to distinguish between
Hi
AFAIK This is more a CentOS- than an oVirt-issue. CentOS behaves identically on
vSphere.
If I remember correctly, this is due to the fact that the MAC-address of the
virtual NIC has to change, when you create a VM from a template.
CentOS however keeps the MAC address of the template and
Good afternoon,
In attachment the result of vdsClient -s 0 getVdsCaps during problem and
after problem resolved.
Best regards,
Ricardo Esteves.
-Original Message-
From: Mike Kolesnik mkole...@redhat.com
To: Ricardo Esteves maverick...@gmail.com
Cc: Users@ovirt.org, Itamar Heim
I would advocate for option 2.
- Original Message -
From: Michal Skrivanek michal.skriva...@redhat.com
To: Alon Bar-Lev alo...@redhat.com
Cc: Juan Hernandez jhern...@redhat.com, engine-devel
engine-de...@ovirt.org, arch a...@ovirt.org, users
users@ovirt.org
Sent: Tuesday, July 30,
Hi René,
thanks for the information and the URL!
Will have a look at this :)
Cheers,
Sven.
Sven Knohsalla | System Administration | Netbiscuits
Office +49 631 68036 433 | Fax +49 631 68036 111 |E-Mail
s.knohsa...@netbiscuits.com | Skype: netbiscuits.admin
Netbiscuits GmbH | Europaallee 10
You need to delete the udev created files under /etc/udev.d
I believe persistent-net-70-* or something (can't check).
And then create your template
Vincent
Connected by Motorola
Sven M. Geschke ov...@nebulaone.com wrote:
Hi
AFAIK This is more a CentOS- than an oVirt-issue. CentOS behaves
Il 30/07/2013 15:12, Alon Bar-Lev ha scritto:
Hello All,
Starting the discussion again...
I would like to receive feedback regarding how we should cope with a state
presented to use by Fedora.
Fedora-19 minimal setup does not install tar utility which is required to
deploy files during
- Original Message -
| From: Dead Horse deadhorseconsult...@gmail.com
| To: Doron Fediuck dfedi...@redhat.com
| Cc: Alon Bar-Lev alo...@redhat.com, users users@ovirt.org, Dave
Chen wei.d.c...@intel.com, Eli Mesika
| emes...@redhat.com
| Sent: Tuesday, July 30, 2013 6:55:18 PM
| Subject:
Hi Ayal,
On Mon, 2013-07-29 at 10:13 -0400, Ayal Baron wrote:
I have found a similar issue here:
https://www.redhat.com/archives/lvm-devel/2011-February/msg00127.html
After discussing this with Peter Rajnoha, it looks like the specific issue in
the above thread has been resolved and
Hi Ricardo,
Thanks a lot for the extra and very relevant info. Could you please create a
bug in bugzilla so we can better track it?
Best,
Toni
- Original Message -
From: Ricardo Esteves gmail.com
To: Users@ovirt.org
Sent: Tuesday, July 30, 2013 5:58:44 PM
Subject: Re: [Users]
On Tue, 30 Jul 2013 16:40:16 +0200
Vincent Van der Kussrn vinc...@vanderkussen.org wrote:
I hadn't looked at the history below which already explains it.
you can also add a .reconfigure file in your root that allows you
to provide a new root pwd on boot.
- Vincent
You need to delete the udev
On Tue, Jul 30, 2013 at 06:05:46PM +0300, Moran Goldboim wrote:
We would like to go a head on oVirt 3.3 release process and issue an RC
for tomorrow meeting:
Maintainers/ Package owners
==
-branch your git repo (master) with 3.3 branch (making master ready for 3.4)
-for
On 07/30/2013 04:13 PM, René Koch (ovido) wrote:
Hi,
The easiest way is to remove 70-persistent-net.rules in your master-vm,
remove HWADDR-strings from ifcfg-eth* friles, shut it down and create
the template.
Btw, also remove your ssh-keys in your template to create unique ones
for each vm...
On 07/30/2013 06:05 PM, Moran Goldboim wrote:
We would like to go a head on oVirt 3.3 release process and issue an RC
how can we do this before folks review all the bugs with target release
of 3.3 and either suggest them as blockers or move them from 3.3?
there are currently 59 NEW, 7
On 07/30/2013 09:56 PM, Itamar Heim wrote:
On 07/30/2013 06:05 PM, Moran Goldboim wrote:
We would like to go a head on oVirt 3.3 release process and issue an RC
how can we do this before folks review all the bugs with target
release of 3.3 and either suggest them as blockers or move them
- Original Message -
From: Dead Horse deadhorseconsult...@gmail.com
To: Doron Fediuck dfedi...@redhat.com
Cc: Alon Bar-Lev alo...@redhat.com, users users@ovirt.org, Dave
Chen wei.d.c...@intel.com, Eli Mesika
emes...@redhat.com
Sent: Tuesday, July 30, 2013 11:20:01 PM
Subject: Re:
Big thanks DHC for your time and efforts.
Since neither of us managed to reproduce the issue
I suggest we drop it for now. If someone else will hit
into it, we should try and get more info on a possible
failure which will not complete the db upgrade.
Thanks again,
Doron
- Original Message
Agreed,
I did revert my victim VM back the pre-upgrade snapshot and retry the
upgrade with the same results with yesterdays packages.I had watch on the
logs but I did not see any DB upgrade failures.
Given that I figured for the heck of it I would just rebuild with this
mornings latest commits to
On 07/30/2013 09:25 AM, Michal Skrivanek wrote:
On Jul 30, 2013, at 15:12 , Alon Bar-Lev alo...@redhat.com wrote:
Hello All,
Starting the discussion again...
I would like to receive feedback regarding how we should cope with a state
presented to use by Fedora.
Fedora-19 minimal setup does
On Tue, Jul 30, 2013 at 10:09:47AM -0400, Antoni Segura Puimedon wrote:
I would advocate for option 2.
- Original Message -
From: Michal Skrivanek michal.skriva...@redhat.com
To: Alon Bar-Lev alo...@redhat.com
Cc: Juan Hernandez jhern...@redhat.com, engine-devel
On Tue, Jul 30, 2013 at 06:05:46PM +0300, Moran Goldboim wrote:
We would like to go a head on oVirt 3.3 release process and issue an RC
for tomorrow meeting:
Maintainers/ Package owners
==
-branch your git repo (master) with 3.3 branch (making master ready for 3.4)
-for
33 matches
Mail list logo
