-
Notifications
You must be signed in to change notification settings - Fork 45
[Role][2168] support_mode role to gather all facts #2392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
fernandofloresg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Requested few changes, codewise and tests are looking good.
rexemin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thank you for working on this, it will be really useful for our technical support. Besides the comments I've already left, I would say to:
- make sure you update copyright years to the correct ones (that is, 2025 in all of them, as they are new files)
- probably rename
Docs/todocs/to keep naming consistent inside the role directory - and also add checking of the SSH config files inside the managed node playbook (this would include getting the contents of
~/.ssh/rc,/etc/ssh/sshrcand/etc/ssh/ssh_config). I will leave it up to you to decide whether this information should be a toggle just like other parts of the playbook that are optional
| @@ -0,0 +1,26 @@ | |||
| # Copyright (c) IBM Corporation 2020, 2025 | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leave the copyright year as just 2025
| --- | ||
| # Operator PCON command | ||
| gather_diagnostics_gather_syslog: true | ||
| # Wether to get the controller node logs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| # Wether to get the controller node logs | |
| # Whether to get controller logs |
| gather_diagnostics_gather_syslog: true | ||
| # Wether to get the controller node logs | ||
| controller_node: true | ||
| # Wether to create the managed node logs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| # Wether to create the managed node logs | |
| # Whether to create the managed node logs |
| controller_node: true | ||
| # Wether to create the managed node logs | ||
| managed_node: true | ||
| # Set to true to create the YAML report files. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| # Set to true to create the YAML report files. | |
| # If set to true, it will create YAML report files. |
| # Set to true to create the YAML report files. | ||
| # If set to false, no report will be created, all sensitive data will be printed to the console. | ||
| managed_node_log_file: true | ||
| # Creates separate file for control node logs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| # Creates separate file for control node logs | |
| # Creates a separate file for controller logs |
| managed_node_log_file: true | ||
| # Creates separate file for control node logs | ||
| controller_node_log_file: true | ||
| # NEW: Directory to write reports to. Defaults to controller's home dir. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| # NEW: Directory to write reports to. Defaults to controller's home dir. | |
| # Directory to write reports to. Defaults to controller's home dir. |
| """ | ||
|
|
||
| Note = r""" | ||
| 1. If C(environment- '{{ environment_vars }}') is defined in the main playbook before the controller node execution. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 1. If C(environment- '{{ environment_vars }}') is defined in the main playbook before the controller node execution. | |
| 1. If C(environment- '{{ environment_vars }}') is defined in the main playbook before controller execution, |
|
|
||
| Note = r""" | ||
| 1. If C(environment- '{{ environment_vars }}') is defined in the main playbook before the controller node execution. | ||
| it will fail as the controller node tasks will assume them as local environment variables. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| it will fail as the controller node tasks will assume them as local environment variables. | |
| the role will fail as the controller tasks will assume them as local environment variables, when they are meant for the managed node running z/OS. |


SUMMARY
Create a role that executes on the managed node and collect all the required parameters for the support.
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION