Primary storage was, indeed, still attached to the xenserver host
when I tried to add primary storage on Tuesday.
So, I did unmount that primary storage this morning.
Then, I tried as fresh an install as possible using 3.0.2.1.
However, I am still getting a similar error when I try to
add primary storage using CSMS GUI (no longer in Basic
Setup Wizard).
Here is what is mounted on the xenserver:
[root@xenserver1-cs 10efe737-fa96-d72c-433e-c0239787af0d]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 4127440 1949348 1968428 50% /
none 158208 0 158208 0% /dev/shm
/opt/xensource/packages/iso/XenCenter.iso
51240 51240 0 100% /var/xen/xc-install
sunshine.eng.citrite.net:/exports/data
5716045824 1973301248 3452385280 37% /nfs/data
10.217.5.19:/exports/data/cs/primary
5716045824 1973301248 3452385280 37%
/var/run/sr-mount/10efe737-fa96-d72c-433e-c0239787af0d
[root@xenserver1-cs 10efe737-fa96-d72c-433e-c0239787af0d]# pwd
/var/run/sr-mount/10efe737-fa96-d72c-433e-c0239787af0d
[root@xenserver1-cs 10efe737-fa96-d72c-433e-c0239787af0d]# ll
total 8
drwxrwxr-x 2 root root 4096 Jul 5 12:23 .
drwxr-xr-x 5 root root 4096 Jul 5 12:25 ..
[root@xenserver1-cs 10efe737-fa96-d72c-433e-c0239787af0d]#
Here is the error I get even after I clear the nfs mounted
primary partition from the host xenserver:
Can not create storage pool through host 1 due to Catch Exception
com.cloud.utils.exception.CloudRuntimeException, create StoragePool failed due
to com.cloud.utils.exception.CloudRuntimeException: There is a SR using the
same configuration server:10.217.5.192, serverpath:/home/export/primary for
pool c9c0319f-33f0-3494-9ada-4d7a2f1dafd4on
host:09b3515e-447e-406f-869a-239386d5fe90 on
host:09b3515e-447e-406f-869a-239386d5fe90 pool: 10.217.5.192/home/export/primary
The, trying a different nfs partition from a completely different host,
I get:
Can not create storage pool through host 1 due to Catch Exception
com.cloud.utils.exception.CloudRuntimeException, create StoragePool failed due
to com.cloud.utils.exception.CloudRuntimeException: There is a SR using the
same configuration server:10.217.5.19, serverpath:/exports/data/cs/primary for
pool f3660f4e-2a6b-30ab-899d-75cdc16b368eon
host:09b3515e-447e-406f-869a-239386d5fe90 on
host:09b3515e-447e-406f-869a-239386d5fe90 pool:
10.217.5.19/exports/data/cs/primary
What's going on?
Need help getting past this error, since the zone is disabled and CSMS is
unusable.
BTW, Secondary storage was added successfully.
Regards,
Evan
-----Original Message-----
From: Nitin Mehta [mailto:[email protected]]
Sent: Thursday, July 05, 2012 12:21 PM
To: [email protected]; Alena Prokharchyk
Subject: RE: Need help installing Basic Setup for CSMS v3.0.2.1 - Stuck with
same error as before
Did you clean up the host you were using ? I think the primary storage wasn't
detached from the host and so CS won't create a SR out of it saying it already
exists.
-----Original Message-----
From: Evan Miller [mailto:[email protected]]
Sent: Friday, July 06, 2012 12:47 AM
To: [email protected]; Alena Prokharchyk
Subject: Need help installing Basic Setup for CSMS v3.0.2.1 - Stuck with same
error as before
Tried to go back and install CSMS 3.0.1.1.
However, the install.sh script wouldn't allow it.
install.sh persisted in trying to install the 3.0.2.1 libraries.
So, I continued with that install. I, initially, deleted as much as possible
using install.sh.
However, I got the same blocking error as before:
Something went wrong; you may go back and correct any errors:
Cannot create storage pool through host 1 due to Catch Exception
com.cloud.utils.exception.CloudRuntimeException, create StoragePool failed due
to com.cloud.utils.exception.CloudRuntimeException: There is a SR using the
same configuration server:cumulus.eng.citrite.net,
serverpath:/home/export/primary for pool 9b759fa1-414c-3680-9204-9da3fe549136on
host:09b3515e-447e-406f-869a-239386d5fe90 on
host:09b3515e-447e-406f-869a-239386d5fe90 pool:
cumulus.eng.citrite.net/home/export/primary
How do I get past this error in CSMS 3.0.2.1 that didn't occur with 3.0.1.1?
Need help please, since CSMS is unusable unless I get past this error.
Regards,
Evan
-----Original Message-----
From: Evan Miller [mailto:[email protected]]
Sent: Thursday, July 05, 2012 9:29 AM
To: [email protected]; Alena Prokharchyk
Subject: RE: Unable to create a deployment for VM[User|i-2-23-VM]
I am going to re-install CloudStack 3.0.1, since I am dead in the water with my
installation of CloudStack 3.0.2.
Regards,
Evan
-----Original Message-----
From: Evan Miller
Sent: Tuesday, July 03, 2012 8:34 PM
To: [email protected]; Alena Prokharchyk
Cc: Evan Miller
Subject: RE: Unable to create a deployment for VM[User|i-2-23-VM]
Hi Alena:
Terminated the Basic Installation of 3.02.
Then, fired up the GUI.
Was able to setup Secondary Storage.
Still getting the same error when trying to setup Primary Storage.
Please see the attached third snapshot.
I'll send u a detailed log of several failed attempts to add primary storage.
Does CSMS think the primary storage device is already being used?
NOTE: The exported filesystem disk for secondary and primary is the same,
however the mount points are named differently.
This worked fine in CSMS 3.0.1.
Regards,
Evan
-----Original Message-----
From: Evan Miller [mailto:[email protected]]
Sent: Tuesday, July 03, 2012 7:58 PM
To: [email protected]; Alena Prokharchyk
Subject: RE: Unable to create a deployment for VM[User|i-2-23-VM]
In an Basic Setup Installation Loop now ...
Please see the second attachment after merely changing the hostname to its
equivalent ip address.
Only option appears to be to kill the GUI install. Any ideas?
Regards,
Evan
-----Original Message-----
From: Evan Miller [mailto:[email protected]]
Sent: Tuesday, July 03, 2012 7:48 PM
To: Alena Prokharchyk; [email protected]
Subject: RE: Unable to create a deployment for VM[User|i-2-23-VM]
The upgrade to 3.0.2 has been disappointing so far.
Here were my steps:
service cloud-management stop
tar xvzf CloudStack-oss-3.0.2-1-rhel6.2.tar.gz
cd CloudStack-oss-3.0.2-1-rhel6.2
./install
Select U for upgrade existing libraries.
cloud-setup-management
cloud-setup-databases cloud:c1tr1x=@localhost --deploy-as=root:c1tr1x=
Checked my database configuration in /etc/cloud/management/db.properties.
service cloud-management restart
In a browser: http://10.217.5.192:8080/client/
Enter "password" as the default password.
DONE getting the GUI going.
What should I have done differently to preserve the previous metadata related
to CloudStack? I couldn't believe that the upgrade caused a reset of the CSMS
from the beginning, and I had to re-type all of the ip, xenserver, pod, etc.
data in again.
My steps started me over from scratch with the CSMS.
After entering everything in the various text boxes, please see the snapshot.
How should I resolve this?
I want to use the same host (the CSMS) for serving both the primary and
secondary filesystems.
While waiting for your response, I'll go back and see if I can see what is
wrong with primary and secondary filesystem setup in CSMS.
Regards,
Evan
-----Original Message-----
From: Alena Prokharchyk
Sent: Tuesday, July 03, 2012 6:19 PM
To: [email protected]
Cc: Evan Miller
Subject: Re: Unable to create a deployment for VM[User|i-2-23-VM]
I fixed exactly this issue. It existed in 3.0.x branch only, should work fine
in asf/master build.
-Alena.
On 7/3/12 6:13 PM, "Evan Miller" <[email protected]> wrote:
>Yes. I'm using: v3.0.1.1
>
>I'll go get the latest build and try it out.
>
>Adding a new VM just won't work in my current, Basic Setup.
>There are no instances at all. A previous VM was deleted using the API.
>
>
>Regards,
>Evan
>
>
>
>-----Original Message-----
>From: Alena Prokharchyk [mailto:[email protected]]
>Sent: Tuesday, July 03, 2012 6:09 PM
>To: [email protected]
>Subject: Re: Unable to create a deployment for VM[User|i-2-23-VM]
>
>Is it 3.0.x build?
>If so, I've put a couple of fixed to Vm deployment in Basic zone in
>3.0.x branch one hour ago, please get the latest build and try again.
>
>
>-Alena.
>
>On 7/3/12 5:46 PM, "Prachi Damle" <[email protected]> wrote:
>
>>If you try to create a new VM using the network you have, a router
>>should be started by CS as part of the new user VM start.
>>
>>-Prachi
>>
>>-----Original Message-----
>>From: Evan Miller [mailto:[email protected]]
>>Sent: Tuesday, July 03, 2012 5:42 PM
>>To: [email protected]
>>Subject: RE: Unable to create a deployment for VM[User|i-2-23-VM]
>>
>>As ROOT Admin, listRouters API produced the following:
>>
>>{ "listroutersresponse" : { } }
>>
>>Fyi, under the Networks tab, I show one Network only:
>>
>>guestNetworkForBasicZone using
>>DefaultSharedNetworkOfferingWithSGService
>>
>>I restarted that network, but that didn't help.
>>
>>What are the steps to create the router, if it doesn't exist?
>>
>>
>>Regards,
>>Evan
>>
>>-----Original Message-----
>>From: Ahmad Emneina [mailto:[email protected]]
>>Sent: Tuesday, July 03, 2012 3:41 PM
>>To: [email protected]
>>Subject: Re: Unable to create a deployment for VM[User|i-2-23-VM]
>>
>>On 7/3/12 3:27 PM, "Evan Miller"
>><[email protected]<mailto:[email protected]>> wrote:
>>
>>
>>Running CloudStack Management Server:
>>
>> v3.0.1.1
>>
>>
>>
>>OS:
>>
>> [root@cumulus management]# uname -a
>>
>> Linux cumulus.eng.citrite.net 2.6.32-220.el6.x86_64 #1 SMP Tue Dec 6
>>19:48:22 GMT 2011 x86_64 x86_64 x86_64 GNU/Linux
>>
>> [root@cumulus management]#
>>
>>Hi:
>>
>>I am trying to deploy the simplest of VMs from the GUI.
>>
>>Attached the csms failing job's log output in job-53.txt.
>>
>>How do I fix these two problems reported in the attached log file?
>>
>>
>>1) Unable to apply dhcp entry on disconnected router r-4-VM(4)
>>
>>2) Host name: xenserver1-cs, hostId: 12 is in avoid set
>>
>>Is #1 an important error, since I am using well-defined ip address
>>ranges?
>>
>>In #2, how do I get xenserver1-cs out of the avoid set?
>>
>>
>>Regards,
>>
>>Evan Miller
>>
>>Citrix Systems. Inc.
>>Desktop and Cloud Engineering Infrastructure
>>4988 Great America Parkway
>>Santa Clara, CA 95054
>>
>>
>>
>>
>>What state is your router in? It seems to be unreachable, I'd attempt
>>to restart it... Maybe even destroy it. The avoid sets' scope doesn't
>>go beyond the vm deployment. Every time you deploy a vm the avoid set
>>is empty.
>>--
>>Æ
>>
>
>
>
