Playbook skips the debug for no reason

Archives Ansible Project
1

Hi,

I am not sure why the playbook skips the debug to print the output.
Am i missing some thing ?

  • name: Collect the JDK version of the updated package
    shell: “/apps/jdk1.8.0_351/bin/java -version”
    register: jdkstat

  • debug:
    var: jdkstat.stdout
    verbosity: 2

However the log shows the logs are registered under jdkstat.err .

changed: [server1] => {
“changed”: true,
“cmd”: “/apps/jdk1.8.0_351/bin/java -version”,
“delta”: “0:00:00.066018”,
“end”: “2022-11-15 12:45:45.676558”,
“invocation”: {
“module_args”: {
“_raw_params”: “/apps/jdk1.8.0_351/bin/java -version”,
“_uses_shell”: true,
“argv”: null,
“chdir”: null,
“creates”: null,
“executable”: null,
“removes”: null,
“stdin”: null,
“stdin_add_newline”: true,
“strip_empty_ends”: true,
“warn”: true
}
},
“rc”: 0,
“start”: “2022-11-15 12:45:45.610540”,
“stderr”: “java version "1.8.0_351"\nJava™ SE Runtime Environment (build 1.8.0_351-b10)\nJava HotSpot™ 64-Bit Server VM (build 25.351-b10, mixed mode)”,
“stderr_lines”: [
“java version "1.8.0_351"”,
“Java™ SE Runtime Environment (build 1.8.0_351-b10)”,
“Java HotSpot™ 64-Bit Server VM (build 25.351-b10, mixed mode)”
],
“stdout”: “”,
“stdout_lines”:
}

TASK [debug] *****************************************************************************************************************
task path: /home/veera/myplay.yml:34
skipping: [server1] => {
“skipped_reason”: “Verbosity threshold not met.”

Even i change the debug module content to below:, still no output in debug

  • debug:
    var: jdkstat.err
    verbosity: 2
2

Debug looks like it is indented too far? Needs to properly line up.

  • name: Collect the JDK version of the updated package
    shell: “/apps/jdk1.8.0_351/bin/java -version”
    register: jdkstat

  • debug:
    var: jdkstat.stdout
    verbosity: 2

Walter

3

I think you misunderstand what the “verbosity: 2” does on a ansible.builtin.debug task:

verbosity

integer

added in 2.1 of ansible.builtin

A number that controls when the debug is run, if you set to 3 it will only run debug when -vvv or above.

Default: 0

If you run ansible-playbook with only zero or one "-v"s, then that step will be silently skipped.

4

Hate to be “that guy,” but it is incredibly annoying how terrible the Google Groups interface is for communicating technical info, especially where indentation actually matters. I’ve tried the web interface and various plugins for markdown formatting in email, only to be rudely surprised by the results: weird indentation, crazy highlighting, spurious blank lines, hit-n-miss fixed-width vs “creative” font interpretations… I have my own private google group just for formatting experiments for posts destined eventually to this group, and it still bites me. My inner cynic says I shouldn’t expect better because there’s no money in it for \G{oogle}.

Sorry. This post didn’t make the world better. Please forgive this indulgence. I shall try harder tomorrow.

5

@Todd Lewis why I favor gist/pastebin for showing the code, both in
groups and/or irc/matrix

A 2nd best is using 'text format' and monospaced fonts.

6

Thanks … I have set the indent right and it was working .
Actucally i tried various verbosity level and indent in the debug module , which was not helping .

However , in future I will avoid bringing in atleast indent releated issues here …

7

We all have the indent challenge from time to time. Tools like vscode or turning on language aware settings in VIM can help. This is my .vimrc file. It turns on syntax highlighting and filetype / language aware features. This is on macOS but should work on Linux too. I also set F7 to toggle syntax on and off highlighting.

:filetype on
:filetype plugin on
:filetype indent on
:syntax on
:map :if exists(“syntax_on”) syntax off else syntax on endif

I used to use Atom for code editing. Development ceased and I have switched to VSCode.

Walter