[IGNITE-15408] CLI: 'ignite node start' command produces NPE when optional config path is not passed

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Labels: ignite-3
• Assignee: Unassigned
• Reporter: Andrey N. Gura
• Created: 31/Aug/21 14:50
• Updated: 06/Oct/21 10:49
• Resolved: 06/Oct/21 10:49

Description

CLI command ignite node start produces NullPointerException in case when optional --config=<configPath> parameter is not passed.

Steps to reproduce:

1. ignite init
2. ignite node start prb-node

Result:

Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8 -Djava.net.preferIPv4Stack=true
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.
Starting a new Ignite node...
Can't start the node. Read logs for details: <path-to-log>/ignite-log/prb-node.log

Log:

Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8 -Djava.net.preferIPv4Stack=true
Exception in thread "main" java.lang.NullPointerException
        at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)

Expected behavior:

Node should be started with some defaults or --config parameter must be mandatory.

Issue Links

• duplicates: IGNITE-15538 Starting node via CLI can lead to NullPointerException