[Users] Lost our management server.. have DB backup but no /etc/pki/

[St.Keimond]

I will do so and let folks know the URL to check.. I'm working on 
getting a wiki account now :]

--David

On 02/20/2013 08:47 AM, Itamar Heim wrote:
> On 20/02/2013 16:53, Saint Keimond wrote:
>> All,
>>    Thank you for your help! I love the linux community.
>>
>> I actually was able to get my system up 2 days ago. I did a fresh
>> minimal install of F17, and ovirt 3.1.
>> * ran engine-setup trying to use as many of the same variables as I
>> would have around a year ago.
>> * shutdown jboss-as and ovirt-engine
>> * imported the database
>> * started services back up
>> * ran engine-config to reset the password
>> * restarted services
>> * was able to log in
>> * Had to wait roughly 10-15 minutes before ovirt decided that nothing
>> was running and I could finally delete the nodes from my cluster
>> * Re-added the nodes.. they got the new certificates
>> * Networking & Storage (I use ISCSI) came back just fine
>> * SUCCESS !!! (such a great feeling)
>>
>> . . . . and now you IDIOT (me) . . . . back up the certificates too!
>>
>> ---David
>
> please wikify for other who may need this in the future.
> thanks
>
>>
>> On 2/18/13 5:00 AM, Adrian Gibanel wrote:
>>> If it can help I wrote an oVirt engine migration page for oVirt 3.1 on:
>>>
>>> http://www.ovirt.org/User:Adrian15/oVirt_engine_migration
>>>
>>> . I suppose some of the steps might be adapted for your case easily.
>>>
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>>     *De: *"Itamar Heim" <iheim at redhat.com>
>>>     *Para: *"Saint Keimond" <st.keimond at gmail.com>
>>>     *CC: *users at ovirt.org
>>>     *Enviados: *Domingo, 17 de Febrero 2013 9:26:34
>>>     *Asunto: *Re: [Users] Lost our management server.. have DB backup
>>>     but no        /etc/pki/
>>>
>>>     On 17/02/2013 04:17, Saint Keimond wrote:
>>>     > Hello,
>>>     >    We lost our Fedora 17 server with ovirt 3.1 on it. We have 
>>> a good
>>>     > database backup but do not have have any certificates. From what
>>>     I read,
>>>     > it is possible to still do a restore.. we just have to rejoin
>>>     all the
>>>     > nodes so that they get a new certificate.
>>>     >
>>>     > I've tried to bring the database in to a fresh 3.1 install and a
>>>     fresh
>>>     > 3.2 install.. with no success on either. I need some helping
>>>     figuring
>>>     > this out :)
>>>     >
>>>     >
>>>     > Thanks,
>>>     >     David
>>>
>>>     i don't remember the exact process of the top of my head, but it
>>>     should
>>>     be either:
>>>     1. restore db, then install ovirt (exact same version by 
>>> re-using the
>>>         db.
>>>     2. install ovirt, restore the db over it, and fix some config
>>>     entries to
>>>     correctly map the new certificates.
>>>
>>>     then just remove hosts and re-add them to generate new certs for 
>>> them
>>>     (or just move them to maint and re-install them via the link that
>>>     should
>>>     appear in the general subtab)
>>>
>>>
>>>
>>>
>>> -- 
>>> <http://www.btactic.com/>*Adrián Gibanel*
>>> I.T. Manager
>>>
>>> +34 675 683 301
>>> www.btactic.com <http://btactic.com/>
>>>
>>>
>>> *
>>> Ens podeu seguir a/Nos podeis seguir en:
>>>
>>> <http://www.facebook.com/pages/btactic/118651634826400?v=app_9953271133> 
>>>
>>> i <http://twitter.com/btactic>*
>>>
>>> Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi
>>> ambient és cosa de tothom. / Antes de imprimir el mensaje piensa en el
>>> medio ambiente. El medio ambiente es cosa de todos.
>>>
>>> AVIS:
>>> El contingut d'aquest missatge i els seus annexos és confidencial. Si
>>> no en sou el destinatari, us fem saber que està prohibit utilitzar-lo,
>>> divulgar-lo i/o copiar-lo sense tenir l'autorització corresponent. Si
>>> heu rebut aquest missatge per error, us agrairem que ho feu saber
>>> immediatament al remitent i que procediu a destruir el missatge.
>>>
>>> AVISO:
>>> El contenido de este mensaje y de sus anexos es confidencial. Si no es
>>> el destinatario, les hacemos saber que está prohibido utilizarlo,
>>> divulgarlo y/o copiarlo sin tener la autorización correspondiente. Si
>>> han recibido este mensaje por error, les agradeceríamos que lo hagan
>>> saber inmediatamente al remitente y que procedan a destruir el mensaje.
>>>
>>
>>
>
>