Closed saffer58 closed 6 months ago
I Would like to know which shutdown option you are choosing from HMC UI when it's working, because in powervm_lpar_instance module by default we use 'Delayed' shutdown option.
In ansible_power_hmc-1.8 we have introduced new parameter called shutdown_option
which allows user to choose different options(Delayed, Immediate, OperatingSystem, OSImmediate
)
If you are not using Delayed option from HMC UI, could you try to run the playbook with same option as UI.
Hi
We are doing an immediate shutdown that is specifically required for this project and forms part of a disaster fail over test. Delayed shutdown has never been used.
Regards
Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: Navinakumar Kandakur @.> Sent: Thursday, April 20, 2023 8:03:09 AM To: IBM/ansible-power-hmc @.> Cc: Paul Clayton @.>; Author @.> Subject: Re: [IBM/ansible-power-hmc] powervm_lpar_instance generates a "EPOW_SUS_CHRP" environmental error in the error log and fails to shut the LPAR down (Issue #99)
I Would like to know which shutdown option you are choosing from HMC UI when it's working, because in powervm_lpar_instance module by default we use 'Delayed' shutdown option. In ansible_power_hmc-1.8 we have introduced new parameter called shutdown_option which allows user to choose different options(Delayed, Immediate, OperatingSystem, OSImmediate) If you are not using Delayed option from HMC UI, could you try to run the playbook with same option as UI.
— Reply to this email directly, view it on GitHubhttps://github.com/IBM/ansible-power-hmc/issues/99#issuecomment-1515760137, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A7AJSXV3IRJG64A6EVH62ATXCDGR3ANCNFSM6AAAAAAXDZWN5U. You are receiving this because you authored the thread.Message ID: @.***>
Disclaimer: https://www.shopriteholdings.co.za/email-disclaimer.html
Disclaimer: https://www.shopriteholdings.co.za/email-disclaimer.html
Looking at the playbook mentioned in the issue, you are not specifying shutdown_option
so by default its taking shutdown_option:Delayed
, Can you use the ansible_power_hmc-1.8
content and run your playbook by adding shutdown_option in it as below.
name: Shutdown a logical partition.
powervm_lpar_instance:
hmc_host: '{{ inventory_hostname }}'
hmc_auth: "{{ curr_hmc_auth }}"
system_name: SAPPRD
vm_name: goldaix72
shutdown_option: Immediate
action: shutdown
Since there is no response, Assuming issue is resolved, hence closing the issues, if you encounter the issue again feel free to reopen the issue.
powervm_lpar_instance generates a "EPOW_SUS_CHRP" environmental error in the error log and fails to shut the LPAR down To Reproduce
Using the YAML playbook below, the LPAR fails to shutdown and the HMC displays a D200A200 reference code. On invocation of the playbook, the following error is noted in the error log and timeout occurs. HMC GUI lpar shutdown works without any issues. There are no applications running on the test lpar
ErrorLog `LABEL: EPOW_SUS_CHRP IDENTIFIER: BE0A03E5
Date/Time: Wed Apr 19 11:22:12 2023 Sequence Number: 8331 Machine Id: 00FADCA74C00 Node Id: goldaix72 Class: H Type: PERM WPAR: Global Resource Name: sysplanar0 Resource Class: planar Resource Type: sysplanar_rspc Location:
Description ENVIRONMENTAL PROBLEM
Probable Causes Power Turned Off Without a Shutdown POWER OR FAN COMPONENT
Detail Data POWER STATUS REGISTER 0000 0003 PROBLEM DATA 0624 0040 0000 00BC 8600 8E00 0000 0000 0000 0000 4942 4D00 5048 0030 0100 A207 2023 0419 0922 1200 0000 0000 0000 0000 4C00 0004 0000 0000 0000 0000 0000 0000 83B8 CD1A 0000 0000 5548 0018 0100 A207 8303 0001 0000 0000 0000 0000 0000 0000 4548 0050 0100 A207 3832 3836 2D34 3241 3231 4443 4137 5700 0000 0000 5356 3836 305F 3234 3300 0000 0000 0000 5046 3231 3131 3034 2E70 6677 3836 3000 0000 0000 0000 0000 0000 0000 0000 0004 0000 0000 4550 0014 0200 A207 0301 0100 0420 0000 0000 0000
Diagnostic Analysis Diagnostic Log sequence number: 31 Resource tested: sysplanar0 Menu Number: 651303 Description:
The following informational event was reported by Platform Firmware.
Platform Firmware Miscellaneous, Information Only.
Normal system shutdown with no additional delay.
---
name: HMC LPAR poweroff hosts: HMC collections:
vars: curr_hmc_auth: username: hscroot password: !vault | $ANSIBLE_VAULT;1.1;AES256 66363164363561646239316636653832373263316437323132643436383835376631626161303166 3463306561313462663765616162396236623539373233320a636631663935616537656635396432 39643461313763386134303439643461396666386431323565633464663265393861363337323265 6339653837366361350a363535373933333230306633306630333464646637633637346662323631 3532
tasks:
name: list managed system details power_system: hmc_host: '{{ inventory_hostname }}' hmc_auth: "{{ curr_hmc_auth }}" system_name: SAPPRD state: facts register: testout
name: Stdout the managed system details debug: msg: '{{ testout }}'
name: Shutdown a logical partition. powervm_lpar_instance: hmc_host: '{{ inventory_hostname }}' hmc_auth: "{{ curr_hmc_auth }}" system_name: SAPPRD vm_name: goldaix72 action: shutdown
ansible-playbook [core 2.13.3] config file = /home/ansibleaix/.ansible.cfg configured module search path = ['/usr/share/ansible/fos/library'] ansible python module location = /usr/lib/python3.9/site-packages/ansible ansible collection location = /home/ansibleaix/.ansible/collections:/usr/share/ansible/collections executable location = /usr/bin/ansible-playbook python version = 3.9.13 (main, Nov 9 2022, 13:16:24) [GCC 8.5.0 20210514 (Red Hat 8.5.0-15)] jinja version = 3.1.2 libyaml = True Using /home/ansibleaix/.ansible.cfg as config file Vault password: host_list declined parsing /home/ansibleaix/etc/hosts as it did not pass its verify_file() method script declined parsing /home/ansibleaix/etc/hosts as it did not pass its verify_file() method auto declined parsing /home/ansibleaix/etc/hosts as it did not pass its verify_file() method Parsed /home/ansibleaix/etc/hosts inventory source with ini plugin Skipping callback 'default', as we already have a stdout callback. Skipping callback 'minimal', as we already have a stdout callback. Skipping callback 'oneline', as we already have a stdout callback.
PLAYBOOK: testoff.yml **** 1 plays in testoff.yml
PLAY [HMC poweroff] **
TASK [Gathering Facts] *** task path: /home/ansibleaix/Power/AIX/HOHAFAIL/roles/testoff.yml:2