Re: [Users] Problems Starting Engine After Borked FC17-18 Upgrade

18 Apr 2013


      This is a multi-part message in MIME format.
--------------090803060302020202030609
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Il 18/04/2013 11:34, Chris Steinle ha scritto:
...
Hi all,
Wanting to upgrade to oVirt 3.2 for a number of the new features, I
upgraded to FC18 from FC17 in preparation. This upgrade failed rather
nastily, leaving me with both fc17 and fc18 versions installed for a
number of RPMs. Having unpicked this and resolved a number of issues,
including a rather nasty networking issue and having to manually
upgrade the oVirt DB from PostgreSQL 9.1 to 9.2, I'm now trying to get
oVirt itself back up and running.
Hi Chris, the upgrading from Fedora 17 with oVirt 3.1 to Fedora 18 with
oVirt 3.2 still has some issues open.
I'm assuming you haven't disabled the ovirt repo during the upgrade of
Fedora, so ovirt was upgraded by fedup.
...
I'm running a single server in "all-in-one" mode.
Initially the engine.log and server.log files were reporting that they
could not connect to PostgreSQL, with PostgreSQL complaining about
unauthorized access attempts. I managed to get psql connecting to the
engine DB with what I believed was the correct password I set up on
first install, but the error persisted. I've now set pg_hba.conf to
"trust" everywhere just to get around this, which while not really an
issue given the security actually required on this server, does
concern me that there may be further issues with the DB.
I'm assuming you've already fixed your installed rpms with yum
distro-sync and upgraded the posgresql database using postgresql-setup
upgrade.
But if you've not run engine-upgrade the DB schema was not updated.
The only way I can suggest you for having it running again is to try to
downgrade your rpms to oVirt 3.1 taking them from oVirt repo for Fedora 17.
Once ovirt is running again, I think you should be able to do a backup
(http://www.ovirt.org/User_talk:Stkeimond/Backing_Up_And_Restoring_OVirt),
export your VMs, install oVirt from Fedora 18 oVirt repository and
re-import your VMs on a fresh install.
...
Now that the connection is being established, however, I am getting
other errors. If have included what I believe are the relevant log
file entries. I am now somewhat stumped -- it looks like the DB
contents may not have been upgraded to 3.2, judging by what looks like
missing stored procedures. However, I am not sure that this is the
problem, and even if it is I am unsure how to resolve this without
destroying the current system and starting again. In fact, given the
inherent instability in using Fedora, I am tempted to move to CentOS6
and the EL6 oVirt repos that now exist, so if there was an alternative
get-out that would enable me to export the VMs and import them in to a
new system.
In short -- HELP! J
Cheers,
Chris
[cut]
...
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com


--------------090803060302020202030609
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Il 18/04/2013 11:34, Chris Steinle ha
      scritto:<br>
    </div>
    <blockquote
      cite="mid:A8D21FE1200A3A4DA3453AF5D3396F180E0F5A81@EUEXMB02.ds.jdsu.net"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal">Hi all,<o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">Wanting to upgrade to oVirt 3.2 for a
          number of the new features, I upgraded to FC18 from FC17 in
          preparation. This upgrade failed rather nastily, leaving me
          with both fc17 and fc18 versions installed for a number of
          RPMs. Having unpicked this and resolved a number of issues,
          including a rather nasty networking issue and having to
          manually upgrade the oVirt DB from PostgreSQL 9.1 to 9.2, I’m
          now trying to get oVirt itself back up and running.</p>
      </div>
    </blockquote>
    <br>
    Hi Chris, the upgrading from Fedora 17 with oVirt 3.1 to Fedora 18
    with oVirt 3.2 still has some issues open.<br>
    I'm assuming you haven't disabled the ovirt repo during the upgrade
    of Fedora, so ovirt was upgraded by fedup.<br>
    <br>
    <blockquote
      cite="mid:A8D21FE1200A3A4DA3453AF5D3396F180E0F5A81@EUEXMB02.ds.jdsu.net"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">I’m running a single server in “all-in-one”
          mode.<o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">Initially the engine.log and server.log
          files were reporting that they could not connect to
          PostgreSQL, with PostgreSQL complaining about unauthorized
          access attempts. I managed to get psql connecting to the
          engine DB with what I believed was the correct password I set
          up on first install, but the error persisted. I’ve now set
          pg_hba.conf to “trust” everywhere just to get around this,
          which while not really an issue given the security actually
          required on this server, does concern me that there may be
          further issues with the DB.</p>
      </div>
    </blockquote>
    <br>
    I'm assuming you've already fixed your installed rpms with yum
    distro-sync and upgraded the posgresql database using
    postgresql-setup upgrade.<br>
    But if you've not run engine-upgrade the DB schema was not updated.<br>
    The only way I can suggest you for having it running again is to try
    to downgrade your rpms to oVirt 3.1 taking them from oVirt repo for
    Fedora 17.<br>
    Once ovirt is running again, I think you should be able to do a
    backup
(<a class="moz-txt-link-freetext" href="http://www.ovirt.org/User_talk:Stkeimond/Backing_Up_And_Restoring_OVirt">http://www.ovirt.org/User_talk:Stkeimond/Backing_Up_And_Restoring_OVirt</a>),<br>
    export your VMs, install oVirt from Fedora 18 oVirt repository and
    re-import your VMs on a fresh install. <br>
    <br>
    <blockquote
      cite="mid:A8D21FE1200A3A4DA3453AF5D3396F180E0F5A81@EUEXMB02.ds.jdsu.net"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">Now that the connection is being
          established, however, I am getting other errors. If have
          included what I believe are the relevant log file entries. I
          am now somewhat stumped – it looks like the DB contents may
          not have been upgraded to 3.2, judging by what looks like
          missing stored procedures. However, I am not sure that this is
          the problem, and even if it is I am unsure how to resolve this
          without destroying the current system and starting again. In
          fact, given the inherent instability in using Fedora, I am
          tempted to move to CentOS6 and the EL6 oVirt repos that now
          exist, so if there was an alternative get-out that would
          enable me to export the VMs and import them in to a new
          system.<o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">In short – HELP! <span
            style="font-family:Wingdings">J</span><o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">Cheers,<o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">Chris<o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
      </div>
    </blockquote>
    [cut]<br>
    <br>
    <blockquote
      cite="mid:A8D21FE1200A3A4DA3453AF5D3396F180E0F5A81@EUEXMB02.ds.jdsu.net"
      type="cite">
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a>
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com</pre>
  </body>
</html>

--------------090803060302020202030609--