[
https://issues.apache.org/jira/browse/CLOUDSTACK-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608492#comment-13608492
]
angeline shen commented on CLOUDSTACK-1736:
-------------------------------------------
Another issue involves how to setup APT repo in one server and have another
server configured to use the APT repository.
Per the ASF 4.1 cloudstack installation guide page 18 section 3.5.1
I setup MS1 repo at MS1:/var/www/cloudstack/repo/binary with the Ubuntu
*.deb packages & Packages:
cloudstack-agent_4.1.0-incubating-0.0.snapshot_all.deb
cloudstack-management_4.1.0-incubating-0.0.snapshot_all.deb
cloudstack-awsapi_4.1.0-incubating-0.0.snapshot_all.deb
cloudstack-usage_4.1.0-incubating-0.0.snapshot_all.deb
cloudstack-cli_4.1.0-incubating-0.0.snapshot_all.deb
cloudstack-common_4.1.0-incubating-0.0.snapshot_all.deb
cloudstack-docs_4.1.0-incubating-0.0.snapshot_all.deb
Packages
Packages.gz
Then configured a management server MS2 to use the APT repository per section
3.5.2:
/etc/apt/sources.list.d/cloudstack.list contains :
deb http://10.223.133.51/cloudstack/repo binary ./
When executed apt-get update, got following error:
root@angie:/etc/apt/sources.list.d# apt-get update
W: Failed to fetch
http://10.223.133.51/cloudstack/repo/dists/binary/.//binary-amd64/Packages 404
Not Found
W: Failed to fetch
http://10.223.133.51/cloudstack/repo/dists/binary/.//binary-i386/Packages 404
Not Found
E: Some index files failed to download. They have been ignored, or old ones
used instead.
So it was expecting the Packages file to be located at:
http://10.223.133.51/cloudstack/repo/dists/binary/.//binary-amd64/ instead
of
http://10.223.133.51/cloudstack/repo/binary
So on 10.223.133.51 I created
/var/www/cloudstack/repo/dists/binary/.//binary-amd64/ & placed binaries.
But when I execute apt-get install cloudstack-managment, it emits error &
expects binaries & Packages
to be at 10.223.133.51:/var/www/cloudstack/repo .
I had to manually put another set of binaries and Packages files in
/var/www/cloudstack/repo.
> Ubuntu 12.04 cloud-setup-management Failed to configure CloudStack
> Management Server
> --------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1736
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1736
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Environment: MS ubuntu 12.04
> Reporter: angeline shen
> Assignee: Prasanna Santhanam
> Priority: Blocker
> Fix For: 4.1.0
>
> Attachments: asf4.1cloud_centos63_release.doc,
> asf4.1cloud_ubuntu1204_release.doc, ip1.doc, iptables_13324.doc,
> setupManagement.doc.log
>
>
> 1. http://jenkins.cloudstack.org/job/package-deb-4.1/ contains cloudstack
> debian packages to be installed for Ubuntu 12.04 OS based management server.
> 2. MS1: setup up APT repository containing above packges in
> MS1:/var/www/cloudstack/repo/binary
> 3. MS2: To configure MS2 to make use of MS1's APT repository for installation,
> in MS2 create /etc/apt/sources.list.d/cloudstack.list with following
> content:
> deb http://MS1 IP address/cloudstack/repo binary ./
> 4. MS2:
> apt-get install cloud-management
> apt-get install cloudstack-awsapi
> apt-get install cloudstack-cli
> apt-get install cloudstack-usage
> root@angie:/var/log/cloudstack/management# dpkg -l | grep cloudstack
> ii cloudstack-awsapi 4.1.0-incubating-0.0.snapshot
> CloudStack Amazon EC2 API
> ii cloudstack-cli 4.1.0-incubating-0.0.snapshot
> The CloudStack CLI called CloudMonkey
> ii cloudstack-common 4.1.0-incubating-0.0.snapshot
> A common package which contains files which are shared by several
> CloudStack packages
> ii cloudstack-management 4.1.0-incubating-0.0.snapshot
> CloudStack server library
> ii cloudstack-usage 4.1.0-incubating-0.0.snapshot
> CloudStack usage monitor
> root@angie:/# cd /
> root@angie:/# find . -name 'cloud*' -print
> ....
> ./usr/bin/cloud-update-xenserver-licenses
> ./usr/bin/cloud-setup-databases
> ./usr/bin/cloud-set-guest-sshkey
> ./usr/bin/cloud-set-guest-password
> ./usr/bin/cloud-migrate-databases
> ./usr/bin/cloud-setup-management
> ......
> 5. root@angie:/usr/bin# cloud-setup-databases cloud@localhost --deploy-as=root
> Mysql user name:cloud
> [ OK ]
> Mysql user password:
> [ OK ]
> Mysql server ip:localhost
> [ OK ]
> Mysql server port:3306
> [ OK ]
> Mysql root user name:root
> [ OK ]
> Mysql root user password:
> [ OK ]
> Checking Cloud database files ...
> [ OK ]
> Checking local machine hostname ...
> [ OK ]
> Checking SELinux setup ...
> [ OK ]
> Detected local IP address as 10.223.133.24, will use as cluster management
> server node IP[ OK ]
> Preparing /etc/cloudstack/management/db.properties
> [ OK ]
> Applying /usr/share/cloudstack-management/setup/create-database.sql
> [ OK ]
> Applying /usr/share/cloudstack-management/setup/create-schema.sql
> [ OK ]
> Applying /usr/share/cloudstack-management/setup/create-database-premium.sql
> [ OK ]
> Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql
> [ OK ]
> Applying /usr/share/cloudstack-management/setup/server-setup.sql
> [ OK ]
> Applying /usr/share/cloudstack-management/setup/templates.sql
> [ OK ]
> Processing encryption ...
> [ OK ]
> Finalizing setup ...
> [ OK ]
> CloudStack has successfully initialized database, you can check your database
> configuration in /etc/cloudstack/management/db.properties
> 6. root@angie:/var/log/cloudstack/management# cloud-setup-management
> Starting to configure CloudStack Management Server:
> Configure sudoers ... [OK]
> Configure Firewall ... [OK]
> Configure CloudStack Management Server ...[Failed]
> Failed to configure CloudStack Management Server, please see the
> /var/log/cloudstack/setupManagement.log for detail
> Try to restore your system:
> Restore sudoers ... [OK]
> Restore Firewall ... [OK]
> Restore CloudStack Management Server ...[OK]
> Problems:
> 1. cloud-setup-managment FAILed
> 2. no managment-server.log generated in /var/log/cloudstack/management
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
