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

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

Github user remibergsma commented on the pull request:

    https://github.com/apache/cloudstack/pull/1052#issuecomment-155204305
  
    @davidamorimfaria Here's another glitch you may want to look at:
    
    ```
    [root@cs2 x86_64]# cloudstack-setup-management
      File "/usr/bin/cloudstack-setup-management", line 36
        if options.tomcat7
                         ^
    SyntaxError: invalid syntax
    ```
    
    You mis a `:` after `if options.tomcat7`.
    
    I edit it locally, then run: `cloudstack-setup-management --tomcat7` 
(suppose I need that option when I look at the code?)
    
    Now I get:
    ```
    Starting to configure CloudStack Management Server:
    Configure Firewall ...        [OK]
    Configure CloudStack Management Server ...Configure CloudStack Management 
Server failed, Please check the /var/log/cloudstack/setupManagement.log for 
detail, due to:globalEnv instance has no attribute 'srvConf'
    Try to restore your system:
    Restore Firewall ...          [OK]
    ```


> 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