Forgot reply-all sending to ovirt-users as well.<br>-DHC<br><br><div class="gmail_quote">On Wed, Jul 18, 2012 at 6:03 PM, Dead Horse <span dir="ltr">&lt;<a href="mailto:deadhorseconsulting@gmail.com" target="_blank">deadhorseconsulting@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">3.0 engine database dump attached as: &quot;engine.sql.tar.gz&quot;<br>- DHC<div><div><br><br>
<div class="gmail_quote">On Wed, Jul 18, 2012 at 1:05 PM, Eli Mesika <span dir="ltr">&lt;<a href="mailto:emesika@redhat.com" target="_blank">emesika@redhat.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><br>
<br>
----- Original Message -----<br>
&gt; From: &quot;Dead Horse&quot; &lt;<a href="mailto:deadhorseconsulting@gmail.com" target="_blank">deadhorseconsulting@gmail.com</a>&gt;<br>
&gt; To: <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
&gt; Sent: Wednesday, July 18, 2012 9:08:55 AM<br>
&gt; Subject: [Users] ovirt-engine upgrade 3.0 to 3.1 issue<br>
&gt;<br>
&gt;<br>
&gt; Steps taken:<br>
&gt;<br>
&gt; Load up bare metal or a VM with FC16<br>
&gt; Install 3.0 from <a href="http://www.ovirt.org/releases/stable/fedora/16/" target="_blank">http://www.ovirt.org/releases/stable/fedora/16/</a><br>
&gt; Setup up something minimal (EG: engine-setup then setup a basic<br>
&gt; datacenter/cluster/etc)<br>
&gt; Add a FC16 or EL based node for fun as well and some VM&#39;s if feeling<br>
&gt; ambitious.<br>
&gt;<br>
&gt; Back up database:<br>
&gt; systemctl stop jboss-as.service<br>
&gt; pg_dump -C -E UTF8 --column-inserts --disable-dollar-quoting<br>
&gt; --disable-triggers -U postgres --format=p -f &quot;/temp/engine.sql&quot;<br>
&gt; engine<br>
&gt;<br>
&gt; Back up the following files within /etc/pki/ovirt-engine from a 3.0<br>
&gt; install (preserve owner/group).<br>
&gt; /etc/pki/ovirt-engine/cacert.conf<br>
&gt; /etc/pki/ovirt-engine/ca.pem<br>
&gt; /etc/pki/ovirt-engine/cert.conf<br>
&gt; /etc/pki/ovirt-engine/certs/01.pem<br>
&gt; /etc/pki/ovirt-engine/certs/02.pem<br>
&gt; /etc/pki/ovirt-engine/certs/ca.der<br>
&gt; /etc/pki/ovirt-engine/certs/engine.cer<br>
&gt; /etc/pki/ovirt-engine/certs/engine.der<br>
&gt; /etc/pki/ovirt-engine/database.txt<br>
&gt; /etc/pki/ovirt-engine/database.txt.attr<br>
&gt; /etc/pki/ovirt-engine/database.txt.attr.old<br>
&gt; /etc/pki/ovirt-engine/database.txt.old<br>
&gt; /etc/pki/ovirt-engine/keys/engine_id_rsa<br>
&gt; /etc/pki/ovirt-engine/keys/engine.ssh.key.txt<br>
&gt; /etc/pki/ovirt-engine/private/ca.pem<br>
&gt; /etc/pki/ovirt-engine/requests/ca.csr<br>
&gt; /etc/pki/ovirt-engine/requests/engine.req<br>
&gt;<br>
&gt; Load up bare metal or a VM with FC17 (Upgrade from FC16 --&gt; FC17 is<br>
&gt; still rather messy)<br>
&gt; Install 3.1 from <a href="http://www.ovirt.org/releases/beta/fedora/17/" target="_blank">http://www.ovirt.org/releases/beta/fedora/17/</a><br>
&gt;<br>
&gt; Run engine-setup to get an initial setup.<br>
&gt; stop ovirt-engine (systemctl stop ovirt-engine.service)<br>
&gt;<br>
&gt; Copy the previously backed up /etc/pki/ovirt-engine files from above<br>
&gt; over top of the ones just generated (be sure to preserve owner/group<br>
&gt; EG: cp -a)<br>
&gt;<br>
&gt; Drop the existing engine database: dropdb -U postgres engine<br>
&gt; Create a new blank database: createdb -U postgres engine<br>
&gt; Populate with with the backup of the above 3.0 database:<br>
&gt; psql -U postgres -d engine -w &lt; &quot;/temp/engine.sql&quot;<br>
<br>
</div></div>Can you please attach the engine.sql file so I will be able to reproduce , thanks<br>
<div><div><br>
<br>
&gt;<br>
&gt; Attempt to upgrade the DBschema via<br>
&gt; /usr/share/ovirt-engine/dbscripts/upgrade.sh<br>
&gt; upgrade.sh -u postgres<br>
&gt;<br>
&gt; The DB schema upgrade will fail like so:<br>
&gt;<br>
&gt; Running upgrade script upgrade/03_01_0260_add_job_table.sql<br>
&gt; psql:upgrade/03_01_0260_add_job_table.sql:29: NOTICE: CREATE TABLE /<br>
&gt; PRIMARY KEY will create implicit index &quot;pk_jobs&quot; for table &quot;job&quot;<br>
&gt; CONTEXT: SQL statement &quot;CREATE TABLE job<br>
&gt; (<br>
&gt; job_id UUID NOT NULL,<br>
&gt; action_type VARCHAR(50) NOT NULL,<br>
&gt; description TEXT NOT NULL,<br>
&gt; status VARCHAR(32) NOT NULL,<br>
&gt; owner_id UUID,<br>
&gt; visible BOOLEAN NOT NULL DEFAULT true,<br>
&gt; start_time TIMESTAMP WITH TIME ZONE NOT NULL,<br>
&gt; end_time TIMESTAMP WITH TIME ZONE default NULL,<br>
&gt; last_update_time TIMESTAMP WITH TIME ZONE default NULL,<br>
&gt; correlation_id VARCHAR(50) NOT NULL,<br>
&gt; CONSTRAINT pk_jobs PRIMARY KEY(job_id)<br>
&gt; )<br>
&gt; WITH OIDS&quot;<br>
&gt; PL/pgSQL function &quot;__temp_upgrade_add_job_table&quot; line 6 at SQL<br>
&gt; statement<br>
&gt; psql:/tmp/tmp.mXz8U4xpWr:3: ERROR: column &quot;comment&quot; of relation<br>
&gt; &quot;schema_version&quot; does not exist<br>
&gt; LINE 1:<br>
&gt; ...ksum,installed_by,started_at,ended_at,state,current,comment)<br>
&gt;<br>
&gt; My assumption here is that if the DB schema upgrade would work, that<br>
&gt; this should be the cleanest way to upgrade from 3.0 to 3.1.<br>
&gt;<br>
&gt; - DHC<br>
&gt;<br>
</div></div>&gt; _______________________________________________<br>
&gt; Users mailing list<br>
&gt; <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
&gt; <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
&gt;<br>
</blockquote></div><br>
</div></div></blockquote></div><br>