Keystore is not created with java 22 (password needed)
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
Línea de trabajo
Comienza con los recursos java_ks mostrados en el issue y reproduce la importación con keytool en Java 22. Compara la ejecución no interactiva de Puppet con el comando manual en Rocky 9.5; se considera completado cuando el keystore se crea sin solicitar contraseñas.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the Bug
Running the latest elasticsearch module with elasticsearch 8.15.1 on Rocky 9 throws error:
Error: Execution of 'keytool -importkeystore -srcstoretype PKCS12 -destkeystore /etc/elasticsearch/elasticsearch.ks -srckeystore /tmp/elasticsearch_node.20241023-51377-1njhkrb -alias elasticsearch_node' returned 1: Importing keystore /tmp/elasticsearch_node.20241023-51377-1njhkrb to /etc/elasticsearch/elasticsearch.ks...
Enter destination keystore password: Enter source keystore password:
***************** WARNING WARNING WARNING *****************
* The integrity of the information stored in the srckeystore*
* has NOT been verified! In order to verify its integrity, *
* you must provide the srckeystore password. *
***************** WARNING WARNING WARNING *****************
Enter key password for <elasticsearch_node>Enter key password for <elasticsearch_node>Enter key password for <elasticsearch_node>keytool error: java.lang.Exception: Too many failures - try later
Error: /Stage[main]/Elasticsearch::Config/Java_ks[elasticsearch_node]/ensure: change from 'absent' to 'present' failed: Execution of 'keytool -importkeystore -srcstoretype PKCS12 -destkeystore /etc/elasticsearch/elasticsearch.ks -srckeystore /tmp/elasticsearch_node.20241023-51377-1njhkrb -alias elasticsearch_node' returned 1: Importing keystore /tmp/elasticsearch_node.20241023-51377-1njhkrb to /etc/elasticsearch/elasticsearch.ks...
Enter destination keystore password: Enter source keystore password:
***************** WARNING WARNING WARNING *****************
* The integrity of the information stored in the srckeystore*
* has NOT been verified! In order to verify its integrity, *
* you must provide the srckeystore password. *
***************** WARNING WARNING WARNING *****************
Enter key password for <elasticsearch_node>Enter key password for <elasticsearch_node>Enter key password for <elasticsearch_node>keytool error: java.lang.Exception: Too many failures - try later (corrective)
from elasticsearch module:
# Trust CA Certificate
java_ks { 'elasticsearch_ca':
ensure => present,
certificate => $elasticsearch::ca_certificate,
target => $_keystore_path,
password => $elasticsearch::keystore_password,
trustcacerts => true,
}
# Load node certificate and private key
java_ks { 'elasticsearch_node':
ensure => present,
certificate => $elasticsearch::certificate,
private_key => $elasticsearch::private_key,
private_key_type => $elasticsearch::private_key_type,
target => $_keystore_path,
password => $elasticsearch::keystore_password,
}
The password is not empty in both cases.
Java version used in elasticsearch:
/usr/share/elasticsearch/jdk/bin/java -version
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment (build 22.0.1+8-16)
OpenJDK 64-Bit Server VM (build 22.0.1+8-16, mixed mode, sharing)
This is probably a combination of Java and operation system versions, the same module used on elasticsearch 7.17 works properly.
Expected Behavior
proper keystore should be created.
Steps to Reproduce
I have included code from elasticsearch module.
Environment
- Java version 22.0.1
- Platform: Rocky 9.5
- Puppet version: 7.33.0
Additional Context
When I run commands from above manually (outside puppet run), the keystore is created but I have to provide the password manually on every step.
- Lenguaje dominante
- Ruby
- Estrellas
- 34
- Forks
- 97
- Merge medio
- 1 d 3 h
- PR fusionados (30 d)
- 2
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de puppetlabs/puppetlabs-java_ks
-
bugfix community
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
puppetlabs/puppetlabs-java_ks#476 · 1 comentario ·
-
community
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
puppetlabs/puppetlabs-java_ks#455 · 1 comentario · 1 reacción ·
-
community
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
puppetlabs/puppetlabs-java_ks#445 · 4 comentarios ·
-
community
Dificultad 3/5 1-2 días Aptitud para principiantes 42/100
puppetlabs/puppetlabs-java_ks#434 ·
Todos los issues de puppetlabs/puppetlabs-java_ks
Issues similares
-
Lint/NoReturnInMemoization flags `return` in local variable `||=` and `&&=` assignmentsPosiblemente ocupada @RaphaelFakhri la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Shopify/ruby-style-guide#815 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
zerocracy/judges-action#2849 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
bigbluebutton/bigbluebutton#26166 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
TarteelAI/quranic-universal-library#916 ·
Los mantenedores suelen responder en 1 día
-
good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día