[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453847#comment-13453847
 ] 

Hiroaki Kawai commented on CLOUDSTACK-78:
-----------------------------------------

Please try typing:
yum install jsvc
and/or
yum install jakarta-commons-daemon-jsvc
                
> Cloudstack Agent installation failed with jsvc package dependancy error 
> ------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-78
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-78
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Install and Setup
>    Affects Versions: pre-4.0.0
>            Reporter: Sailaja Mada
>            Assignee: David Nalley
>            Priority: Critical
>             Fix For: pre-4.0.0
>
>
> Steps:
> 1. Tried installing Agent with KVM host .  
> Observation : Cloudstack Agent installation failed with jsvc package 
> dependancy error 
> Details : 
>     M) Install the Management Server
>     A) Install the Agent
>     B) Install BareMetal Agent
>     S) Install the Usage Monitor
>     D) Install the database server
>     Q) Quit
>     > A
> Installing the Agent...
> Loaded plugins: product-id, security, subscription-manager
> Updating certificate-based repositories.
> cloud-temp                                                                    
>                                                                               
>                   | 2.6 kB     00:00 ...
> cloud-temp/primary_db                                                         
>                                                                               
>                   |  10 kB     00:00 ...
> rhel                                                                          
>                                                                               
>                   | 4.0 kB     00:00 ...
> Setting up Install Process
> No package cloud-premium available.
> Resolving Dependencies
> --> Running transaction check
> ---> Package cloud-agent.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
> --> Processing Dependency: cloud-utils = 4.0.59 for package: 
> cloud-agent-4.0.59-0.59.el6.4.0.x86_64
> --> Processing Dependency: cloud-python = 4.0.59 for package: 
> cloud-agent-4.0.59-0.59.el6.4.0.x86_64
> --> Processing Dependency: cloud-deps = 4.0.59 for package: 
> cloud-agent-4.0.59-0.59.el6.4.0.x86_64
> --> Processing Dependency: cloud-core = 4.0.59 for package: 
> cloud-agent-4.0.59-0.59.el6.4.0.x86_64
> --> Processing Dependency: cloud-agent-scripts = 4.0.59 for package: 
> cloud-agent-4.0.59-0.59.el6.4.0.x86_64
> --> Processing Dependency: cloud-agent-libs = 4.0.59 for package: 
> cloud-agent-4.0.59-0.59.el6.4.0.x86_64
> --> Processing Dependency: jsvc for package: 
> cloud-agent-4.0.59-0.59.el6.4.0.x86_64
> --> Processing Dependency: jna for package: 
> cloud-agent-4.0.59-0.59.el6.4.0.x86_64
> --> Running transaction check
> ---> Package cloud-agent.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
> --> Processing Dependency: jsvc for package: 
> cloud-agent-4.0.59-0.59.el6.4.0.x86_64
> ---> Package cloud-agent-libs.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
> ---> Package cloud-agent-scripts.x86_64 0:4.0.59-0.59.el6.4.0 will be 
> installed
> ---> Package cloud-core.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
> ---> Package cloud-deps.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
> ---> Package cloud-python.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
> ---> Package cloud-utils.x86_64 0:4.0.59-0.59.el6.4.0 will be installed
> ---> Package jna.x86_64 0:3.2.4-2.el6 will be installed
> --> Finished Dependency Resolution
> Error: Package: cloud-agent-4.0.59-0.59.el6.4.0.x86_64 (cloud-temp)
>            Requires: jsvc
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest
> Done
> Expected Results :  Installation should go thru with out any issues. 

--
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

Reply via email to