X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C88EA2.205C4270@onstor-exch02.onstor.net>; Tue, 25 Mar 2008 11:00:35 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Cougar FTI + bobcat Migration code ready for in-branch testing
Date: Tue, 25 Mar 2008 11:00:35 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E056C94E4@onstor-exch02.onstor.net>
In-Reply-To: <20080325094018.58c46d72@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cougar FTI + bobcat Migration code ready for in-branch testing
Thread-Index: AciOlulVAKbykIxRQHqOkNRhixSr0gACtdXg
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

With a message "invald configuration" I think... The FTI code just
printed a failure message.

-----Original Message-----
From: Andy Sharp=20
Sent: Tuesday, March 25, 2008 9:40 AM
To: Larry Scheer
Subject: Re: Cougar FTI + bobcat Migration code ready for in-branch
testing

On Sat, 22 Mar 2008 15:05:48 -0700 "Larry Scheer"
<larry.scheer@onstor.com> wrote:

> I used system upgrade -s to install the cougar debug image on g4r5 to
> test the basic installation. I discovered the following issues with
> this build:
>=20
> 1. The cg_fti branch was not updated with all of the changes from the
> dev branch the descr-$(PROD) files are not the latest. This
> introduced a regression with ypbind fails to start if your root file
> system was previously configured to run with ypbind on the SSC (many
> defects filed agains this)
>=20
> 2. Although I had a fully configured system when I started nfxsh
> after the installion and reboot I encountered the FTI screen in the
> CLI.=20
>=20
> 3. Selecting the option to copy the configuration from the secondary
> flash failed.

Failed how?
