Comments (9)
Thanks @philchristensen - your work around works well for jira versions between 7.1.1 and 7.1.4.
Hopefully this issue gets some love soon :)
from puppet-jira.
Aha! I found a workaround at least:
class { '::jira':
javahome => '/usr/lib/jvm/default-java',
product => 'jira-software-7.1.1-jira',
version => '7.1.1',
This did the trick.
from puppet-jira.
@felipe1982 have you tried modifying $format
to bin
instead of tar.gz?
from puppet-jira.
I get an error when changing format.
class {'jdk_oracle':
version => '8',
version_update => '51',
version_build => '16',
} ->
class {'jira':
# downloadURL => 'https://downloads.atlassian.com/software/jira/downloads/',
format => 'bin',
javahome => '/opt/java_home',
version => '7.0.5',
db => 'oracle',
dbtype => 'oracle10g',
dbserver => 'fred.example.com.au',
dbport => '1521',
dbuser => 'jira',
dbpassword => 'jira',
dbname => 'D11',
proxy => {
scheme => 'http',
proxyName => 'jiratest.example.com.au',
proxyPort => '80'
},
} ->
class {'jira::facts': }
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: staging::extract: unsupported file format atlassian-jira-7.0.5.bin. at /etc/puppet/modules/staging/manifests/extract.pp:102
from puppet-jira.
So i tried to download the Jira tar.gz from https://downloads.atlassian.com/software/jira/downloads/atlassian-jira-software-7.0.5-jira-7.0.5.tar.gz and it works properly. I don't have clear understanding why it is downloading from
http://www.atlassian.com/software/jira/downloads/binary//atlassian-jira-7.0.5.tar.gz in your case above since the only place where I see that download url is on the specs.
from puppet-jira.
I have removed format and downloadURL.
Now module tries to fetch
https://downloads.atlassian.com/software/jira/downloads/atlassian-jira-7.0.5.tar.gz
but should fetch
https://downloads.atlassian.com/software/jira/downloads/atlassian-jira-software-7.0.5-jira-7.0.5.tar.gz
from puppet-jira.
I'm having the same issue. My manifest reads as follows:
class { '::jira':
javahome => '/usr/lib/jvm/default-java',
version => '7.1.1',
installdir => "/opt/jira",
homedir => "/var/lib/jira",
proxy => {
scheme => 'https',
proxyName => 'prod-project.aws.logicworks.net',
proxyPort => '443',
},
dbuser => "jira",
dbpassword => "**********",
dbserver => "prod-jira-db.aws.logicworks.local",
enable_connection_pooling => true,
require => Class['automation::common::java']
}
I've read and re-read the source and I cannot figure out why this is trying to download the link from
http://www.atlassian.com/software/jira/downloads/binary//atlassian-jira-7.1.1.tar.gz
from puppet-jira.
Apparently we need a magic regex for this, this isn't scalable nor maintainable as is. I'll see how far I get with that.
from puppet-jira.
Up issue.
For 7.1.9 we need to change postfix:
diff -ruN install.pp-bak install.pp
--- install.pp-bak 2016-08-08 13:03:34.220422399 +0300
+++ install.pp 2016-08-08 13:10:16.988347547 +0300
@@ -50,7 +50,7 @@
if ((versioncmp($jira::version, '7.0.0') < 0) or ($jira::product_name == 'jira-core')) {
$file = "atlassian-${jira::product_name}-${jira::version}.${jira::format}"
} else {
- $file = "atlassian-${jira::product_name}-${jira::version}-jira-${jira::version}.${jira::format}"
+ $file = "atlassian-${jira::product_name}-${jira::version}.${jira::format}"
}
if ! defined(File[$jira::extractdir]) {
Can anyone fix this problem ?
from puppet-jira.
Related Issues (20)
- Add optional MySQL connection string options HOT 1
- Jira_facts deprecation warnings HOT 1
- jira::java_opts defined as YAML multiline block string generates incorrect JAVA_OPTS string in setenv.sh HOT 2
- server.xml - StuckThreadDetectionValve introduced in 7.6.12
- Drop Ubuntu 16.04, Add 18.04 instead
- 5.0.0 release summary
- Test with Puppet 7 and fresher OSes
- JIRA will not start if the installation directory mode is missing o+x HOT 2
- connection-settings parameter in dbconfig.xml template should be connection-properties instead
- Manage web.xml Config HOT 1
- Release a new Jira version
- Add manage_homedir support
- scheme written twice in server.xml when using tomcat_native_ssl and supplying proxy settings
- cluster node id is too long using fqdn
- AlmaLinux support
- Release v5.2.0 HOT 2
- cluster.properties.epp - soon to be deprecated code by Puppet 8 HOT 1
- JVM_OPENS not set for JIRA Java 17 support
- Optional[Integer[-1]] $pool_max_wait breaks with latest puppet agent (7.29 or 8.5) HOT 3
- Jira cluster and NGINX Plus as the load balancer
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from puppet-jira.