Re: [ovirt-users] Network & local disk on same host, live storage migration

2016-04-07 Thread Matthew Bohnsack
Thanks for your responses.

Is gaining the ability to have local and shared storage domains in the same
datacenter (and therefore host) on the roadmap? It's most certainly
functionality we require in our virtual environment.

On Thu, Apr 7, 2016 at 8:44 AM, Alexander Wels <aw...@redhat.com> wrote:

> On Thursday, April 07, 2016 07:47:59 AM Matthew Bohnsack wrote:
> > Hello.
> >
> > I've been doing some experimentation with oVirt 3.6 and CentOS 7.2 hosts,
> > and I have a few high level questions, related to what I've seen in my
> > testing:
> >
> > 1/ It seems that for a given host, it's impossible to have both a local
> > storage domain and a shared storage domain such as NFS.  Is this correct?
> > If so, is adding this capability on the roadmap somewhere?  I would
> really
> > like to have the ability for a single host to simultaneously support both
> > local and network disks.
> >
>
> Storage is defined on a data center level, not on a host level, so you are
> correct you cannot have local storage and shared storage in the same data
> center.
>
> > 2/ Does oVirt support any sort of live storage migration functionality?
> >
>
> Yes, if you go to the disks main tab, you can select the disk you want to
> migrate and click 'move'. This will give you a dialog that allows you to
> select the target storage domain and profile.
>
> >   2.A/ For example, say I have one host (host#1) with two separate NFS
> > storage domains (NFS#1 and NFS#2).  In this case,  can a VM on host#1
> > associated with NFS#1 be live migrated to NFS#2 storage?  Or can this
> sort
> > of storage movement only be accomplished by a shutdown of the VM and an
> > export/import/restart workflow?
> >
> >   2.B/ Is the scenario described in 2.A possible across two different
> hosts
> > that share both NFS storage domains?  That is, can a VM guest on
> > host#1/NFS#1 be live migrated to host#2/NFS#2?
> >
>
> See above answer, you can live migrate between storage domains, and since
> storage domains are at a data center level if both hosts are in the same
> data
> center, and both storage domains are in the same data center, you can live
> migrate the storage as well as the VMs. It will be 2 separate operations
> though.
>
> > 3/ Let's says that you setup a host (host#1) with a shared storage domain
> > (NFS#1) and a second host (host#2) with a local storage domain (local#2).
> > If you wanted to move a VM from host#1/NFS#1 to host#2/local#2, how would
> > you most easily accomplish this?  All I could come up with is: Add NFS
> > export domain to host#1, turn VM on host#1 off, export VM, add NFS import
> > domain to host#2, import VM, on host#2 onto local#2, turn VM on on
> host#2?
> >
>
> Since these hosts cannot be in the same data center (cannot mix shared and
> local storage) that is the only option I know of for this particular
> scenario.
>
> > Thanks for your help,
> >
> > -Matthew
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Network & local disk on same host, live storage migration

2016-04-07 Thread Matthew Bohnsack
Hello.

I've been doing some experimentation with oVirt 3.6 and CentOS 7.2 hosts,
and I have a few high level questions, related to what I've seen in my
testing:

1/ It seems that for a given host, it's impossible to have both a local
storage domain and a shared storage domain such as NFS.  Is this correct?
If so, is adding this capability on the roadmap somewhere?  I would really
like to have the ability for a single host to simultaneously support both
local and network disks.

2/ Does oVirt support any sort of live storage migration functionality?

  2.A/ For example, say I have one host (host#1) with two separate NFS
storage domains (NFS#1 and NFS#2).  In this case,  can a VM on host#1
associated with NFS#1 be live migrated to NFS#2 storage?  Or can this sort
of storage movement only be accomplished by a shutdown of the VM and an
export/import/restart workflow?

  2.B/ Is the scenario described in 2.A possible across two different hosts
that share both NFS storage domains?  That is, can a VM guest on
host#1/NFS#1 be live migrated to host#2/NFS#2?

3/ Let's says that you setup a host (host#1) with a shared storage domain
(NFS#1) and a second host (host#2) with a local storage domain (local#2).
If you wanted to move a VM from host#1/NFS#1 to host#2/local#2, how would
you most easily accomplish this?  All I could come up with is: Add NFS
export domain to host#1, turn VM on host#1 off, export VM, add NFS import
domain to host#2, import VM, on host#2 onto local#2, turn VM on on host#2?

Thanks for your help,

-Matthew
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] capture all serial output of all vms?

2016-01-29 Thread Matthew Bohnsack
You may be able to wire up conman, conserver, or a similar application to
accomplish this:

https://github.com/dun/conman
http://www.conserver.com

-Matthew
On Jan 29, 2016 7:17 AM, "Ernest Beinrohr" 
wrote:

> Hi, is it possible to capture all serial output
> and still have access to the serial console?
>
> Our serial is made with the vdsm hook:
> http://www.ovirt.org/Features/Serial_Console_in_CLI
>
> and this is how we access it:
> virsh -c qemu+tls://$HOST/system console $VM
>
> --
> Ernest Beinrohr, AXON PRO
> Ing , RHCE
> , RHCVA ,
> LPIC , VCA
> ,
> +421-2-62410360 +421-903-482603
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt 3.6.1 ISO storage domain with all-in-one local disk install not working as expected

2015-12-30 Thread Matthew Bohnsack
Thanks.  I will be also testing NFS, as you used in the howto you
reference, but for this phase of my testing, I want to stick with local
disk.  As such, there appears to be a bug with all-in-one engine setup and
a local disk ISO domain.  Should I report a bug for this?  What's the right
way to do that?

I was able to work around the issue by creating a new ISO domain via the
web GUI (see the local-iso-on-host.jpg attachment) and then copying an ISO
into the right place by hand with something like this (your exact path may
vary):

[host ~]# cp CentOS-7-x86_64-Minimal-1511.iso
/home/ovirt-localdisk/iso2/d61c0b87-25cd-4da0-9704-f453143daa6c/images/----/

After taking the two above-mentioned steps, I was able to successfully
attach ISOs to my VMs.

-Matthew

On Tue, Dec 29, 2015 at 8:48 PM, Taste-Of-IT <kont...@taste-of-it.de> wrote:

> Hello Matthew,
>
> i got similar problem, but this howto works for me :
> http://taste-of-it.de/ovirt-all-in-one-installation-auf-centos-7/
>
> Hope it works for you too.
> Taste
>
>
> Am 2015-12-29 23:02, schrieb Matthew Bohnsack:
>
>> Hello,
>>
>> I installed an all-in-one oVirt 3.6.1 system on CentOS 7.2 with local
>> disk configured for images and ISOs.  However, the engine web GUI
>> doesn't mention the ISO_DOMAIN, and I can't seem to select an uploaded
>> ISO and attach it to a VM.  Any idea what I'm doing wrong here?
>>
>> Thanks,
>>
>> -Matthew
>>
>> Additional detail...
>>
>> I did engine setup with this where all paths are on local disk:
>>
>> OVESETUP_CONFIG/isoDomainName=str:ISO_DOMAIN
>> OVESETUP_CONFIG/isoDomainACL=str:*(rw)
>> OVESETUP_CONFIG/isoDomainMountPoint=str:/home/ovirt-localdisk/iso
>> OVESETUP_AIO/storageDomainDir=str:/home/ovirt-localdisk/images/
>>
>> With this, I was able to upload an image like so:
>>
>> [root@host ~]#  engine-iso-uploader upload -i ISO_DOMAIN
>> ./CentOS-7-x86_64-Minimal-1511.iso
>> Please provide the REST API password for the admin@internal oVirt
>> Engine user (CTRL+D to abort):
>> Uploading, please wait...
>> INFO: Start uploading ./CentOS-7-x86_64-Minimal-1511.iso
>> Uploading: [] 100%
>>
>> INFO: ./CentOS-7-x86_64-Minimal-1511.iso uploaded successfully
>>
>> After this, the local filesystem had my image:
>>
>> [root@host ~]# find /home/ovirt-localdisk/iso/ -iname *.iso
>>
>> /home/ovirt-localdisk/iso/d33449b5-f660-4e90-abd4-5d55f9c27b85/images/----/CentOS-7-x86_64-Minimal-1511.iso
>>
>> But this seems to say something's wrong:
>>
>> [root@host ~]# engine-iso-uploader list
>> Please provide the REST API password for the admin@internal oVirt
>> Engine user (CTRL+D to abort):
>> ERROR: There are no ISO storage domains.
>>
>> Further, the engine web gui has no mention of the ISO storage domain
>> nor does CentOS-7-x86_64-Minimal-1511.iso show up as an option to
>> attach as a CDROM to guests.
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ovirt 3.6 centos7.2 all-in-one install: The VDSM host was found in a failed state.

2015-12-29 Thread Matthew Bohnsack
Progress: I managed to get a host setup and then a vm setup on the host,
but the VM won't start.  I'm looking for some help getting the VM to
start.  Details...

I was able to work around the VDSM host in a failed state issue (I think),
by doing a host reinstall from the engine web GUI, after specifying the the
root password for the host.  That is, I changed to password authentication,
instead of what was originally set to SSH PublicKey authentication.   After
the host reinstall completed, I was left with what appears to be an
all-in-one setup with the engine and a host running on the same server.
Maybe this would have worked automatically, without the re-install step, if
I had ovirt SSH keys setup for root as expected?

Question: Any hints on to how to debug this in terms of host install SSH
PublicKey auth not working?  What user is attempting to SSH from the engine
to the host with what private key to complete the setup?  I see an
ovirt-engine public key that was added to /root/.ssh/authorized_keys.  Is
this the public key that's expected to work with the automated all-in-one
host setup?  If so, where's the corresponding private key so I might
attempt to debug further?

After adding a virtual local disk to the new host and setting up a new VM
through the web interface, I tried to attempt to start the VM but got this
permission denied error in engine.log:

2015-12-29 12:01:47,814 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(ForkJoinPool-1-worker-3) [] Correlation ID: null, Call Stack: null, Custom
Event ID: -1, Message: VM nycovirttest1 is down with error. Exit message:
internal error: process exited while connecting to monitor:
2015-12-29T17:01:45.424728Z qemu-kvm: -drive
file=/rhev/data-center/62bbbc20-00c6-46b3-8ac9-2677a4da69e4/954ebee1-521b-454d-b54c-db9516f36cff/images/e87e1633-7afc-4835-931e-c444e1cf72f5/f6dc9f53-b373-4c96-9015-25b316dcbf0a,if=none,id=drive-virtio-disk0,format=raw,serial=e87e1633-7afc-4835-931e-c444e1cf72f5,cache=none,werror=stop,rerror=stop,aio=threads:
Could not open
'/rhev/data-center/62bbbc20-00c6-46b3-8ac9-2677a4da69e4/954ebee1-521b-454d-b54c-db9516f36cff/images/e87e1633-7afc-4835-931e-c444e1cf72f5/f6dc9f53-b373-4c96-9015-25b316dcbf0a':
Permission denied

Question: How can I debug this VM startup permission denied error further?
Is there a command line I can issue that's similar to what ovirt engine is
attempting that can give me more detail?  Something I can strace?

The vdsm user can read the above referenced image just fine, so it's
something more than just simple filesystem permissions I think?:

$ id
uid=36(vdsm) gid=36(kvm) groups=36(kvm),107(qemu),179(sanlock)

$ file
/rhev/data-center/62bbbc20-00c6-46b3-8ac9-2677a4da69e4/954ebee1-521b-454d-b54c-db9516f36cff/images/e87e1633-7afc-4835-931e-c444e1cf72f5/f6dc9f53-b373-4c96-9015-25b316dcbf0a
/rhev/data-center/62bbbc20-00c6-46b3-8ac9-2677a4da69e4/954ebee1-521b-454d-b54c-db9516f36cff/images/e87e1633-7afc-4835-931e-c444e1cf72f5/f6dc9f53-b373-4c96-9015-25b316dcbf0a:
data

Thanks for your help,

-Matthew

On Mon, Dec 28, 2015 at 12:46 PM, Matthew Bohnsack <bohns...@gmail.com>
wrote:

> Hello,
>
> I am attempting to build a fairly basic proof of concept ovirt 3.6 machine
> with the engine, host and guests all on a single physical CentOS 7.2 box
> with local storage (to start), but am running into issues where
> engine-install produces the following error:
>
> [ ERROR ] The VDSM host was found in a failed state. Please check engine
> and bootstrap installation logs.
>
>
> The engine webconsole seems to be working fine after this - I can login
> and click around - but there's no host CPU/storage resources available, as
> expected.  From the logs shown below, there seems to be an issue with the
> vdsm installation process being unable to contact the engine host during
> installation.  Any ideas what's going wrong and/or what I can do to debug
> things further so I can move beyond this issue?
>
> Thanks,
>
> -Matthew
>
>
> Steps I took to install and diagnose the problem:
>
> 1. Installed system with our configuration management system.
>
> 2. Deleted users using UID=36 (needed by vdsm user) and UID=108 (needed by
> ovirt user).
>
> 3. Ensured that /etc/sudoers contained the line "#includedir
> /etc/sudoers.d" so that /etc/sudoers.d/50_vdsm will take effect.
>
> 4. Made directories for isos and images:
>
> # mkdir /state/partition1/images/; chmod 777 /state/partition1/images/
> # mkdir /state/partition1/iso/; chmod 777 /state/partition1/iso/
>
>
> 5. Ensured selinux was disabled and no firewall rules were installed.
>
> 6. Installed RPMs:
>
> # yum -y install
> http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm
>
> # yum -y install ovirt-engine ovirt-engine-setup-plugin-allinone
> # rpm -qa | grep ovirt-release36
> ovirt-releas

[ovirt-users] oVirt 3.6.1 ISO storage domain with all-in-one local disk install not working as expected

2015-12-29 Thread Matthew Bohnsack
Hello,

I installed an all-in-one oVirt 3.6.1 system on CentOS 7.2 with local disk
configured for images and ISOs.  However, the engine web GUI doesn't
mention the ISO_DOMAIN, and I can't seem to select an uploaded ISO and
attach it to a VM.  Any idea what I'm doing wrong here?

Thanks,

-Matthew

Additional detail...

I did engine setup with this where all paths are on local disk:
OVESETUP_CONFIG/isoDomainName=str:ISO_DOMAIN
OVESETUP_CONFIG/isoDomainACL=str:*(rw)
OVESETUP_CONFIG/isoDomainMountPoint=str:/home/ovirt-localdisk/iso
OVESETUP_AIO/storageDomainDir=str:/home/ovirt-localdisk/images/

With this, I was able to upload an image like so:

[root@host ~]#  engine-iso-uploader upload -i ISO_DOMAIN
./CentOS-7-x86_64-Minimal-1511.iso
Please provide the REST API password for the admin@internal oVirt Engine
user (CTRL+D to abort):
Uploading, please wait...
INFO: Start uploading ./CentOS-7-x86_64-Minimal-1511.iso
Uploading: [] 100%
INFO: ./CentOS-7-x86_64-Minimal-1511.iso uploaded successfully

After this, the local filesystem had my image:

[root@host ~]# find /home/ovirt-localdisk/iso/ -iname \*.iso
/home/ovirt-localdisk/iso/d33449b5-f660-4e90-abd4-5d55f9c27b85/images/----/CentOS-7-x86_64-Minimal-1511.iso

But this seems to say something's wrong:

[root@host ~]# engine-iso-uploader list
Please provide the REST API password for the admin@internal oVirt Engine
user (CTRL+D to abort):
ERROR: There are no ISO storage domains.

Further, the engine web gui has no mention of the ISO storage domain nor
does CentOS-7-x86_64-Minimal-1511.iso show up as an option to attach as a
CDROM to guests.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ovirt 3.6 centos7.2 all-in-one install: The VDSM host was found in a failed state.

2015-12-29 Thread Matthew Bohnsack
I temporarily moved beyond both my issues with the VDSM host needing to be
reinstalled from the engine GUI and VMs not starting by doing a fresh
all-in-one install without any of our configuration management stuff.
I.e., it worked fine when I installed on top of a fresh CentOS 7.2 ISO
install.  I'll still need to get things working with our configuration
management system, but for now I'm making progress.  Any help with my
previous questions about how to debug the issues would still be very much
appreciated.

-Matthew

On Tue, Dec 29, 2015 at 12:40 PM, Matthew Bohnsack <bohns...@gmail.com>
wrote:

> Progress: I managed to get a host setup and then a vm setup on the host,
> but the VM won't start.  I'm looking for some help getting the VM to
> start.  Details...
>
> I was able to work around the VDSM host in a failed state issue (I think),
> by doing a host reinstall from the engine web GUI, after specifying the the
> root password for the host.  That is, I changed to password authentication,
> instead of what was originally set to SSH PublicKey authentication.   After
> the host reinstall completed, I was left with what appears to be an
> all-in-one setup with the engine and a host running on the same server.
> Maybe this would have worked automatically, without the re-install step, if
> I had ovirt SSH keys setup for root as expected?
>
> Question: Any hints on to how to debug this in terms of host install SSH
> PublicKey auth not working?  What user is attempting to SSH from the engine
> to the host with what private key to complete the setup?  I see an
> ovirt-engine public key that was added to /root/.ssh/authorized_keys.  Is
> this the public key that's expected to work with the automated all-in-one
> host setup?  If so, where's the corresponding private key so I might
> attempt to debug further?
>
> After adding a virtual local disk to the new host and setting up a new VM
> through the web interface, I tried to attempt to start the VM but got this
> permission denied error in engine.log:
>
> 2015-12-29 12:01:47,814 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (ForkJoinPool-1-worker-3) [] Correlation ID: null, Call Stack: null, Custom
> Event ID: -1, Message: VM nycovirttest1 is down with error. Exit message:
> internal error: process exited while connecting to monitor:
> 2015-12-29T17:01:45.424728Z qemu-kvm: -drive
> file=/rhev/data-center/62bbbc20-00c6-46b3-8ac9-2677a4da69e4/954ebee1-521b-454d-b54c-db9516f36cff/images/e87e1633-7afc-4835-931e-c444e1cf72f5/f6dc9f53-b373-4c96-9015-25b316dcbf0a,if=none,id=drive-virtio-disk0,format=raw,serial=e87e1633-7afc-4835-931e-c444e1cf72f5,cache=none,werror=stop,rerror=stop,aio=threads:
> Could not open
> '/rhev/data-center/62bbbc20-00c6-46b3-8ac9-2677a4da69e4/954ebee1-521b-454d-b54c-db9516f36cff/images/e87e1633-7afc-4835-931e-c444e1cf72f5/f6dc9f53-b373-4c96-9015-25b316dcbf0a':
> Permission denied
>
> Question: How can I debug this VM startup permission denied error
> further?  Is there a command line I can issue that's similar to what ovirt
> engine is attempting that can give me more detail?  Something I can strace?
>
> The vdsm user can read the above referenced image just fine, so it's
> something more than just simple filesystem permissions I think?:
>
> $ id
> uid=36(vdsm) gid=36(kvm) groups=36(kvm),107(qemu),179(sanlock)
>
> $ file
> /rhev/data-center/62bbbc20-00c6-46b3-8ac9-2677a4da69e4/954ebee1-521b-454d-b54c-db9516f36cff/images/e87e1633-7afc-4835-931e-c444e1cf72f5/f6dc9f53-b373-4c96-9015-25b316dcbf0a
> /rhev/data-center/62bbbc20-00c6-46b3-8ac9-2677a4da69e4/954ebee1-521b-454d-b54c-db9516f36cff/images/e87e1633-7afc-4835-931e-c444e1cf72f5/f6dc9f53-b373-4c96-9015-25b316dcbf0a:
> data
>
> Thanks for your help,
>
> -Matthew
>
> On Mon, Dec 28, 2015 at 12:46 PM, Matthew Bohnsack <bohns...@gmail.com>
> wrote:
>
>> Hello,
>>
>> I am attempting to build a fairly basic proof of concept ovirt 3.6
>> machine with the engine, host and guests all on a single physical CentOS
>> 7.2 box with local storage (to start), but am running into issues where
>> engine-install produces the following error:
>>
>> [ ERROR ] The VDSM host was found in a failed state. Please check engine
>> and bootstrap installation logs.
>>
>>
>> The engine webconsole seems to be working fine after this - I can login
>> and click around - but there's no host CPU/storage resources available, as
>> expected.  From the logs shown below, there seems to be an issue with the
>> vdsm installation process being unable to contact the engine host during
>> installation.  Any ideas what's going wrong and/or what I can do to debug
>> things further so I can move beyond this issue?
>>

[ovirt-users] ovirt 3.6 centos7.2 all-in-one install: The VDSM host was found in a failed state.

2015-12-28 Thread Matthew Bohnsack
Hello,

I am attempting to build a fairly basic proof of concept ovirt 3.6 machine
with the engine, host and guests all on a single physical CentOS 7.2 box
with local storage (to start), but am running into issues where
engine-install produces the following error:

[ ERROR ] The VDSM host was found in a failed state. Please check engine
and bootstrap installation logs.


The engine webconsole seems to be working fine after this - I can login and
click around - but there's no host CPU/storage resources available, as
expected.  From the logs shown below, there seems to be an issue with the
vdsm installation process being unable to contact the engine host during
installation.  Any ideas what's going wrong and/or what I can do to debug
things further so I can move beyond this issue?

Thanks,

-Matthew


Steps I took to install and diagnose the problem:

1. Installed system with our configuration management system.

2. Deleted users using UID=36 (needed by vdsm user) and UID=108 (needed by
ovirt user).

3. Ensured that /etc/sudoers contained the line "#includedir
/etc/sudoers.d" so that /etc/sudoers.d/50_vdsm will take effect.

4. Made directories for isos and images:

# mkdir /state/partition1/images/; chmod 777 /state/partition1/images/
# mkdir /state/partition1/iso/; chmod 777 /state/partition1/iso/


5. Ensured selinux was disabled and no firewall rules were installed.

6. Installed RPMs:

# yum -y install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm

# yum -y install ovirt-engine ovirt-engine-setup-plugin-allinone
# rpm -qa | grep ovirt-release36
ovirt-release36-002-2.noarch


7. Installed engine with an all-in-one configuration (Configure VDSM on
this host? Yes):

# cat /root/ovirt-engine.ans
# action=setup
[environment:default]
OVESETUP_DIALOG/confirmSettings=bool:True
OVESETUP_CONFIG/applicationMode=str:virt
OVESETUP_CONFIG/remoteEngineSetupStyle=none:None
OVESETUP_CONFIG/sanWipeAfterDelete=bool:False
OVESETUP_CONFIG/storageIsLocal=bool:False
OVESETUP_CONFIG/firewallManager=none:None
OVESETUP_CONFIG/remoteEngineHostRootPassword=none:None
OVESETUP_CONFIG/firewallChangesReview=none:None
OVESETUP_CONFIG/updateFirewall=bool:False
OVESETUP_CONFIG/remoteEngineHostSshPort=none:None
OVESETUP_CONFIG/fqdn=<...host.fqdn...>
OVESETUP_CONFIG/storageType=none:None
OSETUP_RPMDISTRO/requireRollback=none:None
OSETUP_RPMDISTRO/enableUpgrade=none:None
OVESETUP_DB/secured=bool:False
OVESETUP_DB/host=str:localhost
OVESETUP_DB/user=str:engine
OVESETUP_DB/dumper=str:pg_custom
OVESETUP_DB/database=str:engine
OVESETUP_DB/fixDbViolations=none:None
OVESETUP_DB/port=int:5432
OVESETUP_DB/filter=none:None
OVESETUP_DB/restoreJobs=int:2
OVESETUP_DB/securedHostValidation=bool:False
OVESETUP_ENGINE_CORE/enable=bool:True
OVESETUP_CORE/engineStop=none:None
OVESETUP_SYSTEM/memCheckEnabled=bool:True
OVESETUP_SYSTEM/nfsConfigEnabled=bool:True
OVESETUP_PKI/organization=str:<...dn...>
OVESETUP_PKI/renew=none:None
OVESETUP_CONFIG/isoDomainName=str:ISO_DOMAIN
OVESETUP_CONFIG/engineHeapMax=str:7975M
OVESETUP_CONFIG/adminPassword=str:<...password...>
OVESETUP_CONFIG/isoDomainACL=str:*(rw)
OVESETUP_CONFIG/isoDomainMountPoint=str:/state/partition1/iso
OVESETUP_CONFIG/engineDbBackupDir=str:/var/lib/ovirt-engine/backups
OVESETUP_CONFIG/engineHeapMin=str:7975M
OVESETUP_AIO/configure=bool:True
OVESETUP_AIO/storageDomainName=str:local_storage
OVESETUP_AIO/storageDomainDir=str:/state/partition1/images/
OVESETUP_PROVISIONING/postgresProvisioningEnabled=bool:True
OVESETUP_APACHE/configureRootRedirection=bool:True
OVESETUP_APACHE/configureSsl=bool:True
OVESETUP_VMCONSOLE_PROXY_CONFIG/vmconsoleProxyConfig=bool:True
OVESETUP_ENGINE_CONFIG/fqdn=str:<...fqdn...>
OVESETUP_CONFIG/websocketProxyConfig=bool:True

# engine-setup --config-append=/root/ovirt-engine.ans

...
[ INFO  ] Starting engine service
[ INFO  ] Restarting httpd
[ INFO  ] Waiting for VDSM host to become operational. This may take
several minutes...
[ ERROR ] The VDSM host was found in a failed state. Please check engine
and bootstrap installation logs.
[WARNING] Local storage domain not added because the VDSM host was not up.
Please add it manually.
[ INFO  ] Restarting ovirt-vmconsole proxy service
[ INFO  ] Stage: Clean up
  Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20151228112813-iksxhe.log
[ INFO  ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20151228113003-setup.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ INFO  ] Execution of setup completed successfully

8. Examined 
/var/log/ovirt-engine/setup/ovirt-engine-setup-20151228112813-iksxhe.log
and found this error message which seems to indicate that the vdsm
installation process was unable to contact the engine:

2015-12-28 11:29:29 DEBUG otopi.plugins.otopi.services.systemd
plugin.execute:941 execute-output: ('/bin/systemctl', 'start',
'httpd.service') stderr:


2015-12-28 11:29:29 DEBUG otopi.context context._executeMethod:142 Stage
closeup METHOD

[ovirt-users] patternfly missing during CentOS7.1 installs of oVirt v3.5 and v3.6

2015-12-07 Thread Matthew Bohnsack
Hello,

I am attempting to install oVirt v3.6 on CentOS.7.1 via:


# yum install
http://plain.resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm
# yum -y install ovirt-engine

When I do this, I get an error about
patternfly1-1.3.0-1.el7.centos.noarch.rpm not existing.  Sure enough that
file is missing from the referenced repository:


# yum -y install ovirt-engine
...
patternfly1-1.3.0-1.el7.centos FAILED

http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64/patternfly1-1.3.0-1.fc20/patternfly1-1.3.0-1.el7.centos.noarch.rpm:
[Errno 14] curl#18 - "transfer closed with 2165640 bytes remaining to read"
Trying other mirror.

Error downloading packages:
  patternfly1-1.3.0-1.el7.centos.noarch: [Errno 256] No more mirrors to try.


A very similar error occurs when attempting to install oVirt v3.5.

Any suggestions?

Thanks,

-Matthew
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users