linux Upgrade fails on clusters from 181 to 2.0 or 2.0 to 2.0.1 ( node referenced using hostnames)

Centos 5.7

• Update 181 nodes w/ hostnames
• create 181 3 node cluster, 2 buckets ( default and sasl)
• Load 100k items on both the buckets.

Take a backup of the data.

Do an offline upgrade on master node
rpm -U

Do an offline upgrade on non-master node
rpm -U

No data/buckets after upgrade

Seeing this error on upgrade
[root@grape-008 jenkins]# rpm -U couchbase-server-community_x86_64_2.0.0-1956-rel.rpm
Stopping couchbase-server ...
Stopping couchbase-server
Upgrading couchbase-server ...
/opt/couchbase/bin/install/cbupgrade -c /opt/couchbase/var/lib/couchbase/config -a yes
Automatic mode: running without interactive questions or confirmations.
Upgrading your Couchbase Server to 2.0.0-1956-rel.
The upgrade process might take awhile.
Analysing...
Previous config.dat file is /opt/couchbase/var/lib/couchbase/config/config.dat
Target node: ns_1@127.0.0.1
Done: previous node configuration is empty.
Starting couchbase-server[ OK ]

You have successfully installed Couchbase Server.
Please browse to http://grape-008:8091/ to configure your server.
Please refer to http://couchbase.com for additional resources.

The upgrade is unable to pickup older node w/ hostname and wrongly identifies it w/ ip address inplace of hostname here.
Resulting in this being treated as an install instead of upgrade