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.
--
Todd

On 11/15/22 2:36 PM, 'Rowe, Walter P. (Fed)' via Ansible Project wrote:
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
--
Walter Rowe, Division Chief
Infrastructure Services, OISM
Mobile: 202.355.4123

On Nov 15, 2022, at 2:04 PM, Veera <[email protected]> wrote:

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(TM) SE Runtime Environment (build 1.8.0_351-b10)\nJava HotSpot(TM) 64-Bit Server VM (build 25.351-b10, mixed mode)",
    "stderr_lines": [
        "java version \"1.8.0_351\"",
        "Java(TM) SE Runtime Environment (build 1.8.0_351-b10)",
        "Java HotSpot(TM) 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

--
You received this message because you are subscribed to the Google Groups "Ansible 
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/163b1493-9f43-4b83-4a35-3f338f65affa%40gmail.com.

Reply via email to