[Users] Update of oVirt 3.1
by Karli Sjöberg
--_000_ACA540572C9145638511F5CBF3D34773sluse_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
----- Original Message -----
> Good evening,
>
> I had installed the 3.1 beta version. After an update of Fedora
> 17,
> the portal does not show any links. I reckon that ovirt-engine
> version
> has been upgraded to 3.1.0-1.fc17.
>
> Have I lost all the information in the database? Is there a way
> to
> bring back the datacenters and the nodes info?
I'm pretty sure the DB is still there.
you should take a look into the log files under /var/log/ovirt-engine (serv=
er.log and engine.log) and look for exceptions.
also, you might want to make sure that postgrsql, httpd and ovirt-engine se=
rvices are up and running.
Just tried reinstalling from beta repo. Install goes OK but web is blank
server.log says:
2012-07-25 09:20:17,150 ERROR [org.jboss.msc.service.fail] (MSC service thr=
ead 1-1) MSC000001: Failed to start service
jboss.module.service."deployment.engine.ear.ovirtengineweb.war".m=
ain: org.jboss.msc.service.StartException in service jboss.module.service."=
deployment.engine.ear.ovirtengineweb.war".main: Failed to load module: depl=
oyment.engine.ear.ovirtengineweb.war:main
It goes on saying this for all modules.
All services are up and running.
>
> Regards,
> Jose Garcia
> _______________________________________________
> Users mailing list
> Users at ovirt.org<http://lists.ovirt.org/mailman/listinfo/users>
> http://lists.ovirt.org/mailman/listinfo/users
>
--_000_ACA540572C9145638511F5CBF3D34773sluse_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1"></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -=
webkit-line-break: after-white-space; "><div><span class=3D"Apple-style-spa=
n" style=3D"font-family: monospace; white-space: pre; ">----- Original Mess=
age -----</span></div><div><pre>><i> Good evening,
</i>><i>=20
</i>><i> I had installed the 3.1 beta version. After an update of F=
edora
</i>><i> 17,
</i>><i> the portal does not show any links. I reckon that ovirt-engine
</i>><i> version
</i>><i> has been upgraded to 3.1.0-1.fc17.
</i>><i>=20
</i>><i> Have I lost all the information in the database? Is there =
a way
</i>><i> to
</i>><i> bring back the datacenters and the nodes info?
</i>
I'm pretty sure the DB is still there.
you should take a look into the log files under /var/log/ovirt-engine (serv=
er.log and engine.log) and look for exceptions.
also, you might want to make sure that postgrsql, httpd and ovirt-engine se=
rvices are up and running.</pre><pre><br></pre><pre><div style=3D"font-fami=
ly: Helvetica; white-space: normal; ">Just tried reinstalling from beta rep=
o. Install goes OK but web is blank</div><div style=3D"font-family: Helveti=
ca; white-space: normal; "><br></div><div style=3D"font-family: Helvetica; =
white-space: normal; ">server.log says:</div><div style=3D"font-family: Hel=
vetica; white-space: normal; ">2012-07-25 09:20:17,150 ERROR [org.jboss.msc=
.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service<=
/div><div style=3D"font-family: Helvetica; white-space: normal; "> &n=
bsp; jboss.module.service."deployment.engine.ear.=
ovirtengineweb.war".main: org.jboss.msc.service.StartException in serv=
ice jboss.module.service."deployment.engine.ear.ovirtengineweb.war&quo=
t;.main: Failed to load module: deployment.engine.ear.ovirtengineweb.war:ma=
in</div><div style=3D"font-family: Helvetica; white-space: normal; "><br></=
div><div style=3D"font-family: Helvetica; white-space: normal; ">It goes on=
saying this for all modules.</div><div style=3D"font-family: Helvetica; wh=
ite-space: normal; "><br></div><div style=3D"font-family: Helvetica; white-=
space: normal; ">All services are up and running.</div>
><i>=20
</i>><i> Regards,
</i>><i> Jose Garcia
</i>><i> _______________________________________________
</i>><i> Users mailing list
</i>><i> <a href=3D"http://lists.ovirt.org/mailman/listinfo/users">Users=
at ovirt.org</a>
</i>><i> <a href=3D"http://lists.ovirt.org/mailman/listinfo/users">http:=
//lists.ovirt.org/mailman/listinfo/users</a>
</i>><i> </i></pre><div><br></div></div></body></html>=
--_000_ACA540572C9145638511F5CBF3D34773sluse_--
11 years, 9 months
[Users] Call for Agenda -- oVirt Weekly Sync 2012-07-25
by Mike Burns
Meeting Time and Place
oVirt Weekly Sync
* Wednesdays @ 15:00 UTC (may change during DST changes) - always
at 7:00am US Pacific, 10:00am US Eastern.
* To see in your timezone date -d 'WEDNESDAY 1000 EDT'
* On IRC: #ovirt on irc.oftc.net
This is the agenda for the 2012-07-25 meeting:
* Status of Next Release
* Sub-project reports (engine, vdsm, node, infra)
* Upcoming workshops
If you have other topics, please reply to me and I will add them to the
agenda. If you propose a topic, please be prepared to lead the
discussion during the meeting.
Thanks
Mike
11 years, 9 months
[Users] release date Ovirt 3.1
by Winfried de Heiden
Hi all,
Any new about the Ovirt 3.1 release date? Will it be available this week...?
Can't wait!
Winfried
11 years, 9 months
[Users] VDSM and RHEL problem
by Jonathan Cox
Hello,
I am running Ovirt 3.1 and everything was running well but then I
decided to upgrade to a system with more memory for the engine and now the
VDSM version dropped to 3.1 and the RHEL is complaining that there is no
compatible pc. This wasnt a problem before and I tried to go back to the
old system but now both of them are giving the same error. Anyone have any
ideas what I should be looking to fix here? I am not sure if the 2 problems
are related, I am running CentOS 6.3, Ovirt 3.1 and using the dreyou
builds. Thanks
--
Jonathan H Cox
11 years, 9 months
[Users] oVirt and AWS
by Jamie Pow
Hi Guys,
Hope you are all well.
I am currently putting together a test rig to use this software in my
company for VM maanagement.
I am using AWS to host this at the moment. I am having trouble adding a
new host.
When I enter the details and click ok I recieved an error telling me I
cannot add host. Failed to create SSH......
If anybody has managed to succesfully configure this on AWS and/or provide
some pointers would be much appreciated.
Many thanks folks!
Jamie
11 years, 9 months
Re: [Users] ovirt-engine upgrade 3.0 to 3.1 issue
by Dead Horse
Forgot reply-all sending to ovirt-users as well.
-DHC
On Wed, Jul 18, 2012 at 6:03 PM, Dead Horse
<deadhorseconsulting(a)gmail.com>wrote:
> 3.0 engine database dump attached as: "engine.sql.tar.gz"
> - DHC
>
>
> On Wed, Jul 18, 2012 at 1:05 PM, Eli Mesika <emesika(a)redhat.com> wrote:
>
>>
>>
>> ----- Original Message -----
>> > From: "Dead Horse" <deadhorseconsulting(a)gmail.com>
>> > To: Users(a)ovirt.org
>> > Sent: Wednesday, July 18, 2012 9:08:55 AM
>> > Subject: [Users] ovirt-engine upgrade 3.0 to 3.1 issue
>> >
>> >
>> > Steps taken:
>> >
>> > Load up bare metal or a VM with FC16
>> > Install 3.0 from http://www.ovirt.org/releases/stable/fedora/16/
>> > Setup up something minimal (EG: engine-setup then setup a basic
>> > datacenter/cluster/etc)
>> > Add a FC16 or EL based node for fun as well and some VM's if feeling
>> > ambitious.
>> >
>> > Back up database:
>> > systemctl stop jboss-as.service
>> > pg_dump -C -E UTF8 --column-inserts --disable-dollar-quoting
>> > --disable-triggers -U postgres --format=p -f "/temp/engine.sql"
>> > engine
>> >
>> > Back up the following files within /etc/pki/ovirt-engine from a 3.0
>> > install (preserve owner/group).
>> > /etc/pki/ovirt-engine/cacert.conf
>> > /etc/pki/ovirt-engine/ca.pem
>> > /etc/pki/ovirt-engine/cert.conf
>> > /etc/pki/ovirt-engine/certs/01.pem
>> > /etc/pki/ovirt-engine/certs/02.pem
>> > /etc/pki/ovirt-engine/certs/ca.der
>> > /etc/pki/ovirt-engine/certs/engine.cer
>> > /etc/pki/ovirt-engine/certs/engine.der
>> > /etc/pki/ovirt-engine/database.txt
>> > /etc/pki/ovirt-engine/database.txt.attr
>> > /etc/pki/ovirt-engine/database.txt.attr.old
>> > /etc/pki/ovirt-engine/database.txt.old
>> > /etc/pki/ovirt-engine/keys/engine_id_rsa
>> > /etc/pki/ovirt-engine/keys/engine.ssh.key.txt
>> > /etc/pki/ovirt-engine/private/ca.pem
>> > /etc/pki/ovirt-engine/requests/ca.csr
>> > /etc/pki/ovirt-engine/requests/engine.req
>> >
>> > Load up bare metal or a VM with FC17 (Upgrade from FC16 --> FC17 is
>> > still rather messy)
>> > Install 3.1 from http://www.ovirt.org/releases/beta/fedora/17/
>> >
>> > Run engine-setup to get an initial setup.
>> > stop ovirt-engine (systemctl stop ovirt-engine.service)
>> >
>> > Copy the previously backed up /etc/pki/ovirt-engine files from above
>> > over top of the ones just generated (be sure to preserve owner/group
>> > EG: cp -a)
>> >
>> > Drop the existing engine database: dropdb -U postgres engine
>> > Create a new blank database: createdb -U postgres engine
>> > Populate with with the backup of the above 3.0 database:
>> > psql -U postgres -d engine -w < "/temp/engine.sql"
>>
>> Can you please attach the engine.sql file so I will be able to reproduce
>> , thanks
>>
>>
>> >
>> > Attempt to upgrade the DBschema via
>> > /usr/share/ovirt-engine/dbscripts/upgrade.sh
>> > upgrade.sh -u postgres
>> >
>> > The DB schema upgrade will fail like so:
>> >
>> > Running upgrade script upgrade/03_01_0260_add_job_table.sql
>> > psql:upgrade/03_01_0260_add_job_table.sql:29: NOTICE: CREATE TABLE /
>> > PRIMARY KEY will create implicit index "pk_jobs" for table "job"
>> > CONTEXT: SQL statement "CREATE TABLE job
>> > (
>> > job_id UUID NOT NULL,
>> > action_type VARCHAR(50) NOT NULL,
>> > description TEXT NOT NULL,
>> > status VARCHAR(32) NOT NULL,
>> > owner_id UUID,
>> > visible BOOLEAN NOT NULL DEFAULT true,
>> > start_time TIMESTAMP WITH TIME ZONE NOT NULL,
>> > end_time TIMESTAMP WITH TIME ZONE default NULL,
>> > last_update_time TIMESTAMP WITH TIME ZONE default NULL,
>> > correlation_id VARCHAR(50) NOT NULL,
>> > CONSTRAINT pk_jobs PRIMARY KEY(job_id)
>> > )
>> > WITH OIDS"
>> > PL/pgSQL function "__temp_upgrade_add_job_table" line 6 at SQL
>> > statement
>> > psql:/tmp/tmp.mXz8U4xpWr:3: ERROR: column "comment" of relation
>> > "schema_version" does not exist
>> > LINE 1:
>> > ...ksum,installed_by,started_at,ended_at,state,current,comment)
>> >
>> > My assumption here is that if the DB schema upgrade would work, that
>> > this should be the cleanest way to upgrade from 3.0 to 3.1.
>> >
>> > - DHC
>> >
>> > _______________________________________________
>> > Users mailing list
>> > Users(a)ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/users
>> >
>>
>
>
11 years, 9 months
Re: [Users] "Error: Cannot attach Storage. Storage Domain doesn't exist."
by Johan Kragsterman
Hmm, I'm going to do some research here...
Story is that the first LUN I attached was 30 Gb. Since the LUN's are attached by the same Fc HBA and same port, it is most likely that they get the same device name, even if I change the LUN behind, in the SAN controller. Do someone know something about this?
Is it likely that the HV system save some LUN/device information in it's system LUN? So that it reports the same size of the LUN that it was originally?
I am going to remove the LUN again, and take away the LUN mapping, so the HV can't see it. Then I will make a new LUN of different size again, and check if it has the same device name, and also check what size it reports.
I would appreciate if someone with deeper knowledge than me about these things could shed some light here...
Rgrds Johan
-----Johan Kragsterman/Capvert skrev: -----
Till: Jakub Libosvar <libosvar(a)redhat.com>
Från: Johan Kragsterman/Capvert
Datum: 2012.07.20 14:59
Ärende: Re: [Users] "Error: Cannot attach Storage. Storage Domain doesn't exist."
Hi again!
Hmm, very strange, the size LVM reports on the LUN is actually 30 Gb...??? So why doesn't it allow me to create on it?
PV VG Fmt Attr PSize PFree
/dev/mapper/3600144f09aa1800000004fd87a300001p4 HostVG lvm2 a-- 288.00m 0
/dev/mapper/3600144f09aa180000000500788c20002p1 HostVG lvm2 a-- 30.00g 0
[root@node1 admin]#
rgrds Johan
-----Jakub Libosvar <libosvar(a)redhat.com> skrev: -----
Till: Johan Kragsterman <johan.kragsterman(a)capvert.se>
Från: Jakub Libosvar <libosvar(a)redhat.com>
Datum: 2012.07.20 12:42
Ärende: Re: [Users] "Error: Cannot attach Storage. Storage Domain doesn't exist."
On 07/20/2012 12:13 PM, Johan Kragsterman wrote:
> Hi!
>
> Ahaa, I can shed some light here...
>
> This is a part of the log in engine:
>
> 2012-07-15 13:46:51,837 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (http--0.0.0.0-8080-3) Vds: node1.hemma.home
> 2012-07-15 13:46:51,837 ERROR [org.ovirt.engine.core.vdsbroker.VDSCommandBase] (http--0.0.0.0-8080-3) Command CreateVGVDS execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed in vdscommand to CreateVGVDS, error = Volume Group not big enough: ('VG size must be more than 10240 MiB',)
> 2012-07-15 13:46:51,837 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVGVDSCommand] (http--0.0.0.0-8080-3) FINISH, CreateVGVDSCommand, log id: da915ec
> 2012-07-15 13:46:51,838 ERROR [org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand] (http--0.0.0.0-8080-3) Command org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand throw Vdc Bll exception. With error message VdcBLLException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed in vdscommand to CreateVGVDS, error = Volume Group not big enough: ('VG size must be more than 10240 MiB',)
> 2012-07-15 13:46:51,859 INFO [org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand] (http--0.0.0.0-8080-3) Command [id=db9901fd-9f2d-4298-88d9-70dd898fa4bd]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.storage_domain_dynamic; snapshot: ae76ccdb-e920-436c-b623-09d5e3db3acd.
> 2012-07-15 13:46:51,869 INFO [org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand] (http--0.0.0.0-8080-3) Command [id=db9901fd-9f2d-4298-88d9-70dd898fa4bd]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.storage_domain_static; snapshot: ae76ccdb-e920-436c-b623-09d5e3db3acd.
> 2012-07-15 13:46:51,890 ERROR [org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand] (http--0.0.0.0-8080-3) Transaction rolled-back for command: org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand.
> 2012-07-15 13:46:52,049 WARN [org.ovirt.engine.core.bll.storage.AttachStorageDomainToPoolCommand] (http--0.0.0.0-8080-3) CanDoAction of action AttachStorageDomainToPool failed. Reasons:VAR__TYPE__STORAGE__DOMAIN,VAR__ACTION__ATTACH,ACTION_TYPE_FAILED_STORAGE_DOMAIN_NOT_EXIST
>
> And the important part is that it say`s that "error = Volume Group not big enough: ('VG size must be more than 10240 MiB',)"
>
> The LUN I created is a qcow2-LUN of 50 Gb size, which of coarse doesn't have the size of 50 Gb, because it is a thin provisioned LUN.
>
> So question is then: Doesn't oVirt support thin provisioned LUN's? If not, it is not very good, because most SAN's provide thin provisioned LUN's nowaday's...
It does but the limitation is at least 10GB for block storage device.
Can you check please with 'pvs' command how large does lvm reports
connected lun?
Thanks,
Kuba
> This is perhaps a limitation of LVM2? It would be a real setback to not be able to use qcow2, though....
>
> Regards Johan
>
> -----Jakub Libosvar <libosvar(a)redhat.com> skrev: -----
> Till: Johan Kragsterman <johan.kragsterman(a)capvert.se>
> Från: Jakub Libosvar <libosvar(a)redhat.com>
> Datum: 2012.07.20 10:37
> Ärende: Re: [Users] "Error: Cannot attach Storage. Storage Domain doesn't exist."
>
> On 07/20/2012 10:27 AM, Johan Kragsterman wrote:
>> Thanks for you respons, Kuba!
>>
>> But I didn't attach any log, I was refering to the log attached by Trey Dockendorf in his post: "iSCSI discovery not showing all LUNs - oVirt 3.1", where he is describing an error with the same message as in my post.
>>
>> I don't have a log, since I run only a small hypervisor and haven't enabled external logging...
> There should be logging by default, you can find it at
> /var/log/vdsm/vdsm.log on your hypervisor.
>
>> Or is there logging on the engine as well, in this matter...?
> On machine where oVirt is installed you can find one in
> /var/log/ovirt-engine/engine.log
>
> Kuba
>> Rgrds Johan
>>
>> -----users-bounces(a)ovirt.org skrev: -----
>> Till: Johan Kragsterman <johan.kragsterman(a)capvert.se>
>> Från: Jakub Libosvar
>> Sänt av: users-bounces(a)ovirt.org
>> Datum: 2012.07.20 10:17
>> Kopia: users(a)ovirt.org
>> Ärende: Re: [Users] "Error: Cannot attach Storage. Storage Domain doesn't exist."
>>
>> On 07/19/2012 07:35 PM, Johan Kragsterman wrote:
>>> Hi all!
>>>
>>> This is my first post to this list.
>>>
>>> I set up a fedora16 HV, and an oVirt engine on fedora 16, both booted and installed on fibre channel storage.
>>>
>>> Everything works fine, shows up in web gui on engine, host discovered and active, until that I try to attach storage.
>>>
>>> Then I get this message: "Error: Cannot attach Storage. Storage Domain doesn't exist."
>>>
>>> Same as in the post: "iSCSI discovery not showing all LUNs - oVirt 3.14", also this month.
>>>
>>> In that post discuss if LUN's are dirty or not. My LUN's are not dirty.
>>>
>>> I checked that by removing the data LUN, removing the LUN mapping creating a new LUN I didn't use(so the new LUN I will use didn't use something of the old one), and finally creating a new LUN of different size.
>>>
>>> Same result with that LUN when I try to use it as storage domain: "Error: Cannot attach Storage. Storage Domain doesn't exist."
>>>
>>> I was reading the enclosed vdsm-log of the message: "iSCSI discovery not showing all LUNs - oVirt 3.14"
>> Hi Johan,
>>
>> could you please try to attach the vdsm log again? I don't have it
>> attached in this mail.
>>
>> Thanks,
>> Kuba
>>> The log was a lot about MPIO, if I understood right. Could it be that the MPIO driver isn't discover a dual path, only a single path? Right now I don't have an fc switch, so I am unable to test if that would solve the problem.
>>>
>>> Anyone have any suggestions?
>>>
>>> Regards Johan
>>> _______________________________________________
>>> 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 years, 9 months
[Users] Error: Cannot attach Storage. Storage Domain doesn't exist.
by Johan Kragsterman
Hi again!
Hmm, very strange, the size LVM reports on the LUN is actually 30 Gb...??? So why doesn't it allow me to create on it?
PV VG Fmt Attr PSize PFree
/dev/mapper/3600144f09aa1800000004fd87a300001p4 HostVG lvm2 a-- 288.00m 0
/dev/mapper/3600144f09aa180000000500788c20002p1 HostVG lvm2 a-- 30.00g 0
[root@node1 admin]#
rgrds Johan
11 years, 9 months
[Users] Error: Cannot attach Storage. Storage Domain doesn't exist.
by Johan Kragsterman
Ohh, I see that I haven't sent to the list, so I do that now....
Hi!
Ahaa, I can shed some light here...
This is a part of the log in engine:
2012-07-15 13:46:51,837 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (http--0.0.0.0-8080-3) Vds: node1.hemma.home
2012-07-15 13:46:51,837 ERROR [org.ovirt.engine.core.vdsbroker.VDSCommandBase] (http--0.0.0.0-8080-3) Command CreateVGVDS execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed in vdscommand to CreateVGVDS, error = Volume Group not big enough: ('VG size must be more than 10240 MiB',)
2012-07-15 13:46:51,837 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVGVDSCommand] (http--0.0.0.0-8080-3) FINISH, CreateVGVDSCommand, log id: da915ec
2012-07-15 13:46:51,838 ERROR [org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand] (http--0.0.0.0-8080-3) Command org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand throw Vdc Bll exception. With error message VdcBLLException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed in vdscommand to CreateVGVDS, error = Volume Group not big enough: ('VG size must be more than 10240 MiB',)
2012-07-15 13:46:51,859 INFO [org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand] (http--0.0.0.0-8080-3) Command [id=db9901fd-9f2d-4298-88d9-70dd898fa4bd]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.storage_domain_dynamic; snapshot: ae76ccdb-e920-436c-b623-09d5e3db3acd.
2012-07-15 13:46:51,869 INFO [org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand] (http--0.0.0.0-8080-3) Command [id=db9901fd-9f2d-4298-88d9-70dd898fa4bd]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.storage_domain_static; snapshot: ae76ccdb-e920-436c-b623-09d5e3db3acd.
2012-07-15 13:46:51,890 ERROR [org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand] (http--0.0.0.0-8080-3) Transaction rolled-back for command: org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand.
2012-07-15 13:46:52,049 WARN [org.ovirt.engine.core.bll.storage.AttachStorageDomainToPoolCommand] (http--0.0.0.0-8080-3) CanDoAction of action AttachStorageDomainToPool failed. Reasons:VAR__TYPE__STORAGE__DOMAIN,VAR__ACTION__ATTACH,ACTION_TYPE_FAILED_STORAGE_DOMAIN_NOT_EXIST
And the important part is that it say`s that "error = Volume Group not big enough: ('VG size must be more than 10240 MiB',)"
The LUN I created is a qcow2-LUN of 50 Gb size, which of coarse doesn't have the size of 50 Gb, because it is a thin provisioned LUN.
So question is then: Doesn't oVirt support thin provisioned LUN's? If not, it is not very good, because most SAN's provide thin provisioned LUN's nowaday's...
This is perhaps a limitation of LVM2? It would be a real setback to not be able to use qcow2, though....
Regards Johan
11 years, 9 months
