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

ASF GitHub Bot commented on CLOUDSTACK-9049:
--------------------------------------------

Github user wilderrodrigues commented on the pull request:

    https://github.com/apache/cloudstack/pull/1052#issuecomment-155161579
  
    This PR needs fixes, I cannot even build the RPMs.
    
    I did:
    
    * git fetch origin pull/1052/head:pr/1052
    * git checkout pr/1052
    * cd packaging
    * ./packaging -d centos7
    
    Result below:
    
    ```
    7-nonssl.conf 
/data/git/cs1/cloudstack/dist/rpmbuild/BUILDROOT/cloudstack-4.6.0-SNAPSHOT.el7.centos.x86_64/etc/cloudstack/management/tomcat7-nonssl.conf
    mv: cannot stat 
'/data/git/cs1/cloudstack/dist/rpmbuild/BUILDROOT/cloudstack-4.6.0-SNAPSHOT.el7.centos.x86_64/usr/share/cloudstack-management/webapps/client/WEB-INF/classes/tomcat7-nonssl.conf':
 No such file or directory
    error: Bad exit status from /var/tmp/rpm-tmp.YrDgHw (%install)
    
    
    RPM build errors:
        Bad exit status from /var/tmp/rpm-tmp.YrDgHw (%install)
    RPM Build Failed 
    [root@cs1 packaging]#
    ```
    
    Cheers,
    Wilder


> Fix deployment in CentOS 7 with Tomcat 7
> ----------------------------------------
>
>                 Key: CLOUDSTACK-9049
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9049
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.6.0
>            Reporter: David Amorim Faria
>            Assignee: David Amorim Faria
>
> The centos 7 packaging is using custom config files instead of the files 
> sourced from the webapp. Also, the library used by 
> cloudstack-setup-management expects to find tomcat6 files in the config 
> directory, and they are not valid for tomcat7 which comes as default in 
> centos7.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to