-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tomcat7 deployment won't work on RHEL 6 #9
Comments
Please send me your puppet code.
|
Sure. This is the hiera data:
Then I have a role-profile architecture. Relevant code that has to do with Tomcat:
And:
Profiles rhel and jdk contains EPEL repository and java open-jdk-1.7 respectively. |
I tried your configuration and works fine on my centos6 with branch master and next. Maybe some more input of your errors helps? |
I get no more relevant errors; not even enabling debugging.
I think there is some kind of problem with yum or repos, because tomcat package does not get installed. I think I'll try with a new and blank VM... |
That sounds good. let me know your result of the test.
|
I've tried with a blank Centos 6.5 VM with same results. It seems like puppet is trying to install tomcat package first, no matter what. Since EPEL repository is not installed yet, the tomcat package cannot be installed and the error appears. I've tried all kind of precedence operators, leaving tomcat class for last, but with no success. In fact, these are the lines of code which trigger the tomcat package installation:
This lines are contained in the profile::apache_tomcat class, which is contained in the role::appserver class, this way:
The code contained in rhel and jdk classes is never executed before the tomcat package installation. Have you tried this without EPEL repository installed? I'm running out of ideas... |
I will try to have a look on this problem in the evening.
|
If you declare your repositories with puppet and use before => Class['tomcat'] then the problem is, that I use the anchor behind the install class/define resource, like:
The reason was, I wanna have the directories installed and wanna use i.e. for external file like war files: file { '/var/tomcat/webapp/test.war': I will think about this part of code in the evening. |
What works, use a stage for declaring repos or the collector like |
I've made a dependency graph (file attached) and added some notifications. The result is that Tomcat::Install class depends directly on the main stage, as can be seen in the graph. Perhaps adding a stage for yum repo will work, but order cannot be applied to this module anyway... I'm not sure if this is a desirable behaviour. |
I'm having a new and weird problem with tomcat7 deployment on rhel/centos6. I'm testing a configuration on a pair of rhel machines. This configuration worked before. Now, I've got a lot of errors:
I'm trying a multi-instance configuration with a service called 'data'. Also, no tomcat7 package is installed...
Any ideas?
The text was updated successfully, but these errors were encountered: