Problem Note 70556: The SAS® Orchestration Command Line Interface (CLI) reports “SLF4J: No SLF4J providers were found”
 |  |  |  |
When you create a playbook with the SAS Orchestration CLI and the build command is reported as completing successfully, you can safely ignore any SLF4J messages similar to the following:
[sasinstall@sasviya test]$ ./sas-orchestration build --input /sas/install/SAS_Viya_deployment_data.zip --platform redhat --architecture x64 --repository-warehouse file:///sasshare/mirror_repo/
The build command started
SLF4J: No SLF4J providers were found.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details.
SLF4J: Class path contains SLF4J bindings targeting slf4j-api versions 1.7.x or earlier.
SLF4J: Ignoring binding found at [jar:file:/tmp/manifest-tool-spring.jar.24599!/BOOT-INF/lib/logback-classic-1.2.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See https://www.slf4j.org/codes.html#ignoredBindings for an explanation.
Examining entitled repositories:
0%.........10%.........20%.........30%.........40%.........50%.........60%.........70%.........80%.........90%.........100%
Loading deployment definition data:
0%.........10%.........20%.........30%.........40%.........50%.........60%.........70%.........80%.........90%.........100%
Loading application data:
0%.........10%.........20%.........30%.........40%.........50%.........60%.........70%.........80%.........90%.........100%
[2023-12-05, 16:08:44.897] ILocationGroupDeclaration: Location group name "sas-casserver-primary" has been converted to "sas_casserver_primary".
[2023-12-05, 16:08:44.898] ILocationGroupDeclaration: Location group name "sas-casserver-secondary" has been converted to "sas_casserver_secondary".
[2023-12-05, 16:08:44.898] ILocationGroupDeclaration: Location group name "sas-casserver-worker" has been converted to "sas_casserver_worker".
The build command completed successfully
The build command started
SLF4J: No SLF4J providers were found.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details.
SLF4J: Class path contains SLF4J bindings targeting slf4j-api versions 1.7.x or earlier.
SLF4J: Ignoring binding found at [jar:file:/tmp/manifest-tool-spring.jar.24599!/BOOT-INF/lib/logback-classic-1.2.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See https://www.slf4j.org/codes.html#ignoredBindings for an explanation.
Examining entitled repositories:
0%.........10%.........20%.........30%.........40%.........50%.........60%.........70%.........80%.........90%.........100%
Loading deployment definition data:
0%.........10%.........20%.........30%.........40%.........50%.........60%.........70%.........80%.........90%.........100%
Loading application data:
0%.........10%.........20%.........30%.........40%.........50%.........60%.........70%.........80%.........90%.........100%
[2023-12-05, 16:08:44.897] ILocationGroupDeclaration: Location group name "sas-casserver-primary" has been converted to "sas_casserver_primary".
[2023-12-05, 16:08:44.898] ILocationGroupDeclaration: Location group name "sas-casserver-secondary" has been converted to "sas_casserver_secondary".
[2023-12-05, 16:08:44.898] ILocationGroupDeclaration: Location group name "sas-casserver-worker" has been converted to "sas_casserver_worker".
The build command completed successfully
A fix for this issue is planned for a future software release.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Viya 3.x | Microsoft® Windows® for x64 | 3.5 | Viya 3.5 | ||
| Linux for x64 | 3.5 | Viya 3.5 | ||||
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2023-12-11 14:38:20 |
| Date Created: | 2023-12-05 16:00:30 |