[AMBARI-25005] Ambari hides information about cred_store generation failures. Resulting in confusing errors at later stages

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0
• Labels: pull-request-available
• Assignee: Andrew Onischuk
• Reporter: Andrew Onischuk
• Created: 06/Dec/18 11:13
• Updated: 14/May/19 06:08
• Resolved: 14/May/19 06:08

Description

Component was failing to install due to:

Caught an exception while executing custom service command: <type 'exceptions.OSError'>: [Errno 2] No such file or directory: '/var/lib/ambari-agent/cred/conf/dp_profiler_agent/dpprofiler-config.jceks'; [Errno 2] No such file or directory: '/var/lib/ambari-agent/cred/conf/dp_profiler_agent/dpprofiler-config.jceks'

Command failed after 1 tries

The reason was an empty password provided in blueprint. However it took lots
of time to debug this. Since ambari won't show any information regarding
failures during cred_store generation.

The goal is too fail earlier and show output of failed generation command.
So with the patch it looks like this:

Caught an exception while executing custom service command: <class 'resource_management.core.exceptions.ExecutionFailed'>: Execution of '/usr/lib/jvm/java-openjdk/bin/java -cp '/var/lib/ambari-agent/cred/lib/*' org.apache.hadoop.security.alias.CredentialShell create dpprofiler.spnego.signature.secret -value '[PROTECTED]' -provider jceks://file/var/lib/ambari-agent/cred/conf/dp_profiler_agent/dpprofiler-config.jceks' returned 1. SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Dec 06, 2018 11:05:45 AM org.apache.hadoop.util.NativeCodeLoader <clinit>
WARNING: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
java.lang.IllegalArgumentException: Empty key
at javax.crypto.spec.SecretKeySpec.<init>(SecretKeySpec.java:96)
at org.apache.hadoop.security.alias.AbstractJavaKeyStoreProvider.innerSetCredential(AbstractJavaKeyStoreProvider.java:304)
at org.apache.hadoop.security.alias.AbstractJavaKeyStoreProvider.createCredentialEntry(AbstractJavaKeyStoreProvider.java:269)
at org.apache.hadoop.security.alias.CredentialShell$CreateCommand.execute(CredentialShell.java:365)
at org.apache.hadoop.security.alias.CredentialShell.run(CredentialShell.java:68)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.security.alias.CredentialShell.main(CredentialShell.java:442); Execution of '/usr/lib/jvm/java-openjdk/bin/java -cp '/var/lib/ambari-agent/cred/lib/*' org.apache.hadoop.security.alias.CredentialShell create dpprofiler.spnego.signature.secret -value '[PROTECTED]' -provider jceks://file/var/lib/ambari-agent/cred/conf/dp_profiler_agent/dpprofiler-config.jceks' returned 1. SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Dec 06, 2018 11:05:45 AM org.apache.hadoop.util.NativeCodeLoader <clinit>
WARNING: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
java.lang.IllegalArgumentException: Empty key
at javax.crypto.spec.SecretKeySpec.<init>(SecretKeySpec.java:96)
at org.apache.hadoop.security.alias.AbstractJavaKeyStoreProvider.innerSetCredential(AbstractJavaKeyStoreProvider.java:304)
at org.apache.hadoop.security.alias.AbstractJavaKeyStoreProvider.createCredentialEntry(AbstractJavaKeyStoreProvider.java:269)
at org.apache.hadoop.security.alias.CredentialShell$CreateCommand.execute(CredentialShell.java:365)
at org.apache.hadoop.security.alias.CredentialShell.run(CredentialShell.java:68)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.security.alias.CredentialShell.main(CredentialShell.java:442)

Issue Links

• links to: GitHub Pull Request #2697