Content-Type: text/plain; charset="utf-8"
I'm not able to add a EXPORT Domain to the system. The web does not show any EXPORT domains, but engine.log tells me about
AddStorageServerConnection failed. Reasons:VAR__ACTION__ADD,VAR__TYPE__STORAGE__CONNECTION,ACTION_TYPE_FAILED_STORAGE_CONNECTION_ALREADY_EXISTS
and indeed, there is an entry in storage_server_connections.
Is it save to delete this entry?
Content-Type: text/html; charset="utf-8"
<span style=3D'font-family:Verdana'><span style=3D'font-size:12px'>Hello,<b=
r /><br />I'm not able to add a EXPORT Domain to the system. The web does n=
ot show any EXPORT domains, but engine.log tells me about<br /><br /> =
AddStorageServerConnection failed. Reasons:VAR__ACTION__ADD,VAR__TYPE__STOR=
br />and indeed, there is an entry in storage_server_connections.<br /><br =
/>Is it save to delete this entry?<br /><br />Thanks,<br /><br />Hans-Joach=
Foreman guys say this is probably an oVirt side issue..
I was successfully able to hook up my foreman server to the oVirt
datacenter using the compute resources section. It detected the available
datacenters and logged in fine. Logs showed code 200, I can view the VMs
available, power them on and shut them down from the foreman UI.
But when I go to hosts->New Host and select oVirt I get the error:
Error loading virtual machine information: Internal Server Error
Logs are showing:
Operation FAILED: statementcallback; bad sql grammar select * from (select
* from vds groups view where ( vds group id in (select vds groups storage
domain.vds group id from vds groups storage domain left outer join
storage pool with storage domain on vds groups storage domain.storage pool
id=storage pool with storage domain.id where ( storage pool with
storage domain.name like '%dc_01%' or storage pool with storage
domain.description like '%dc_01%' or storage pool with storage
domain.comment like '%dc_01%' ) )) order by name asc ) as t1 offset (1 -1)
limit 100; nested exception is org.postgresql.util.psqlexception: error:
column storage pool with storage domain.comment does not exist
Rendered common/500.html.erb (5.2ms)
Completed 500 Internal Server Error in 150ms (Views: 6.0ms | ActiveRecord:
CentOS 6.4 - Foreman 1.2
CentOS 6.4 - oVirt 3.3 Nightly
my all-in-one host is stuck in unresponsive state, no matter what I try.
Found this error in my engine.log:
2013-08-31 23:53:59,325 ERROR
(DefaultQuartzScheduler_Worker-54) Command GetCapabilitiesVDS execution
failed. Exception: VDSNetworkException: java.net.ConnectException:
This message starts to appear when I try to activate the host (from
Any idea how to activate the host?
Running oVirt 3.3 RC2 on Fedora 19, all-in-one Setup.
On Fri, Aug 30, 2013 at 9:03 AM, Ofer Schreiber wrote:
> (Sorry for the format, sent from my cell)
> I don't remember any work on that issue.
> I really wonder now whether the el6 build work fine.
For sure it would be impossible to have the new feature "Gluster
Storage Domain" in both plain el6 servers configured as ovirt nodes
and in ovirt-node iso for EL6.
I'm now following this blocker for 3.3 that is strictly connected with
Latest post I read is from yesterday:
I was wondering if it is possible to include correct version of qemu
into ovirt 3.3 repository as it is required for one of ovirt's main
new features - Gluster Storage Domain.
Is there any release plan for RHEL 6.5? It seems that it will be a
long time for having this feature in CentOS (supported by ovirt as I
Tracker bug for libgfapi backport in RHEL 6.5, currently in QA (this
means in the best scenario end of 2013... donna if usable on 6.4
related thread I found on ovirt-devel list:
I'm using oVirt 3.2 on a single hosts with only one NIC. Currently
there is only the ovirtmgmt network configured. But I need to add
more networks, especially some internal networks like 192.168.x.y/24
need to be usable for VMs.
From the oVirt Admin Portal this does not seem to be possible. It
seems I cannot reuse the ovirtmgmt interface for any other network.
Is this true? How am I supposed to add several networks in oVirt if
I have just one NIC?
i am a newbie in ovirt . i installed ovirt 3.2 on centos6.4. i ran VM's on
node manager but i cant connect to them. i installed ovirt in a network
that doesnt access to internet. i have only one active interface on host
(host and ovirt node manager on a server). should i run dhcp or there is
any other solution?thanks in advance
I've got a scenario:
Router->Node (vlan tag 100, vlan tag 101)->VM
Does the node take care of the tagging or will the VM's interface also need
to be tagged. Right now the VM's interface is not in a VLAN and it can't
connect to the router.
I'm looking for some opinions on our current topology and how a disaster
recovery plan would shake out in the real world on an ovirt/gluster
Please ignore the RH references in the attached diagram, we're still on the
fence if we're going with support or not.
[image: Inline image 1]
At HQ site:
Two Gluster nodes running as replica's.
~4 Virt notes
1 Manager node (likely running on as separate kvm HA VM)
1 Gluster node acting as a geo-replication target
1 Virt node
1 Manager in standby (waiting to recover db backup)
*Even better would be using both nodes at this site as one striped gluster
volume, standby Manager, and Virt nodes to eliminate the standby Manager
box, decrease costs and increase virt resources, but I'm not sure this is
doable quite yet.*
During regular operations we're replicating our gluster storage offsite
In the event of a disaster (for simplicity we'll say the server room
becomes unusable) I would want to recover the Manager at the offsite
location from a backup, add the geo-replicated gluster storage domain as
the normal domain, then start spinning up the business critical VM's. With
a router in-place and some external DNS changes we should be able to keep
our VPN accessible and all our internal resources available to mobile/home
workers, or in this simple case even from our normal office location
(already have the site-to-site VPN active).
I'm planning on using a vpls solution to extend the VM subnet and
storage/virt subnet across both sites so we don't need to worry about
dns/IP changes in the middle of recovery.
I think the biggest question so far is can we smoothly replace the normal
storage domain on ovirt with the geo-replicated storage domain in the DR
I've tried to layout most of the high level stuff here so if anyone sees
any flaws or potential gotcha's feel free to chime in. I can provide more
detail if necessary.