Il 13/05/2014 20:29, Dan Kenigsberg ha scritto:
On Tue, May 13, 2014 at 12:07:09PM +0200, Sandro Bonazzola wrote:
Il 12/05/2014 23:53, Bob Doolittle ha scritto:
On 05/12/2014 02:49 PM, Bob Doolittle wrote:
Hi,
I'm trying to set up a fresh system on F19, using oVirt 3.4.
Hi Bob, can you
On Wed, May 14, 2014 at 08:49:06AM +0200, Sandro Bonazzola wrote:
Il 13/05/2014 20:29, Dan Kenigsberg ha scritto:
On Tue, May 13, 2014 at 12:07:09PM +0200, Sandro Bonazzola wrote:
Il 12/05/2014 23:53, Bob Doolittle ha scritto:
On 05/12/2014 02:49 PM, Bob Doolittle wrote:
Hi,
I'm
Il 13/05/2014 00:33, Bob Doolittle ha scritto:
On 05/12/2014 06:21 PM, Dan Kenigsberg wrote:
On Mon, May 12, 2014 at 05:53:10PM -0400, Bob Doolittle wrote:
On 05/12/2014 02:49 PM, Bob Doolittle wrote:
Hi,
I'm trying to set up a fresh system on F19, using oVirt 3.4.
When running
On 13/05/14 00:35, Bob Doolittle wrote:
Also - is there a bugID for this new issue?
The one I quoted is supposed to only affect non-existent device names.
Why is this affecting valid device names as well, and only in the VDSM
context?
Antonio may correct me here, but I believe it's caused
- Original Message -
From: David Sommerseth dav...@redhat.com
To: Bob Doolittle b...@doolittle.us.com, Dan Kenigsberg
dan...@redhat.com, asegu...@redhat.com
Cc: users users@ovirt.org
Sent: Tuesday, May 13, 2014 10:59:47 AM
Subject: Re: Failure during self-hosted deployment:
On Tue, May 13, 2014 at 10:27:12AM +0200, Sandro Bonazzola wrote:
Il 13/05/2014 00:33, Bob Doolittle ha scritto:
On 05/12/2014 06:21 PM, Dan Kenigsberg wrote:
On Mon, May 12, 2014 at 05:53:10PM -0400, Bob Doolittle wrote:
On 05/12/2014 02:49 PM, Bob Doolittle wrote:
Hi,
I'm trying to
Il 13/05/2014 11:50, Dan Kenigsberg ha scritto:
On Tue, May 13, 2014 at 10:27:12AM +0200, Sandro Bonazzola wrote:
Il 13/05/2014 00:33, Bob Doolittle ha scritto:
On 05/12/2014 06:21 PM, Dan Kenigsberg wrote:
On Mon, May 12, 2014 at 05:53:10PM -0400, Bob Doolittle wrote:
On 05/12/2014 02:49 PM,
Il 12/05/2014 23:53, Bob Doolittle ha scritto:
On 05/12/2014 02:49 PM, Bob Doolittle wrote:
Hi,
I'm trying to set up a fresh system on F19, using oVirt 3.4.
Hi Bob, can you check you're using right repositories in order to get 3.4.1?
See http://www.ovirt.org/OVirt_3.4.1_release_notes
Thanks,
On Tue, May 13, 2014 at 12:03:28PM +0200, Sandro Bonazzola wrote:
Il 13/05/2014 11:50, Dan Kenigsberg ha scritto:
On Tue, May 13, 2014 at 10:27:12AM +0200, Sandro Bonazzola wrote:
Il 13/05/2014 00:33, Bob Doolittle ha scritto:
I am using the vdsm from ovirt-stable (and ovirt-3.4-stable):
I think I did in fact start with the wrong ovirt-release RPM, and
consequently the wrong repos.
I have started over as specified in the 3.4.1 release notes (fresh
Fedora 19 install, yum localinstall
http://resources.ovirt.org/pub/yum-repo/ovirt-release34.rpm).
Now I am encountering a
Also - is there a bugID for this new issue?
The one I quoted is supposed to only affect non-existent device names.
Why is this affecting valid device names as well, and only in the VDSM
context?
Thanks,
Bob
On 05/12/2014 06:21 PM, Dan Kenigsberg wrote:
On Mon, May 12, 2014 at
What is my best workaround? I need to get going again ASAP.
Make the bridge by hand. I seem to have had the same problem last weekend and
ended up doing the bridge myself and then let engine do the rest.
Had to downgrade the sos package first.
Joop
12 matches
Mail list logo
