Bug Inspections 07/25/2023 #11
Comments
Inspection for sample 1 (sample 2 generates the same error)Summary
ansible documentation states
so for this reason, I'm leaning towards it not being a bug but would like a second opinion Playbook- name: Manage Perl installations
hosts: all
gather_facts: false
tasks:
- name: Install Perl modules with mixed case sensitivity
community.general.cpanm:
name: "{{ item }}"
loop:
- TestModuleOne
- testModuleTwo
- TESTMODULETHREE
- tEsTmOdUlEfOuROutputInspection
ansible documentation states
so for this reason, I'm leaning towards it not being a bug but would like a second opinion |
Summary
I cannot conclusively say that this is a bug but to me it seems unlikely Playbook---
- name: Test playbook for community.network.iap_token module
hosts: localhost
gather_facts: false
tasks:
- name: Generate IAP Token
community.network.iap_token:
iap_fqdn: null
iap_port: null
username: null
password: null
validate_certs: "True"
https: "True"
register: iap_token_result
- name: Debug IAP Token Result
debug:
var: iap_token_resultOutputInspection
For this reason, I cannot conclusively say that this is a bug but to me it seems unlikely |
|
@jmsalvador2395 : sample 1 and 8 are not bugs. So we cannot report them. I also agree with your assessment for 2-7. I want to know more about 0. Please share a detailed analysis here. |
Inspection for Sample 0Summary
The
Which implies that a string is the expected type. For that reason I believe this is not a bug Playbook---
- name: Execute script with mixed types
hosts: all
gather_facts: false
tasks:
- name: Run script
ansible.builtin.script:
cmd: pwd
chdir: "{{ chdir | default('/path/to/script') }}"
creates: "{{ creates | default(true) }}"
decrypt: "{{ decrypt | default(false) }}"
executable: "{{ executable | default(None) }}"
free_form: "{{ free_form | default('This is a string.') }}"
removes: "{{ removes | default(None) }}"
register: script_output
- name: Display script output
debug:
var: script_output.stdoutOutputInspection
While not explicitly stated, it is implied that this field takes in a string instead of a boolean. For that reason, I believe that this is not a bug. |
Ideally the documentation should state
Instead the Ansible core compiler throws an obscure error when Boolean data is provided. For a typical sysadmin/developer it is very hard to tease out the stack traces, and then find the root cause for this crash, and then assign a proper value for So, @jmsalvador2395 I think this is a bug. Please submit this is a bug report ASAP, if you agree. |
|
@akondrahman I think this is a fair argument. I will write up a bug report with this in mind and let you know when it's submitted. Is there anything else you'd like to go over regarding these 9 samples? |
|
Nothing else for the 9 samples. Please share the bug report link, when ready. Also, start looking into the remaining 179 samples that generated crashes. |
|
@akondrahman submitted the bug report here. Let me know if you are unable to see it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
Firstly I will provide 2 things
9samples we have discussedThen in the comments I will post details for my inspection into samples 1, 2, and 8 which I think are the most relevant ones to look at (samples 1 and 2 generate the same error so I will just post for sample 1).
Overall Summary
not a bugIndividual Sample Summaries
createsfield is set totruewhich triggers the type error. The documentation specifies that astringornullis to be provided so I believe that we cannot consider this a bugcpanminusnot validin my opinionItential Automation Platform. This software can be installed after signing up for a free trial but I am holding off from doing that unless you say otherwise.The text was updated successfully, but these errors were encountered: