This repository has been archived by the owner on Oct 8, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 17
Installing 9.0.3.0 IF0002 #5
Comments
I have been using the fixpack with v9.0.3 IF#2 with no issues. I agree the handler may need to be fixed to wait for the appliance to finish rebooting. I am not following the comment about playbook will go to next host - that should not matter. Are you trying to do something after the fixpack installs in the same playbook? |
as a work around for this I am pausing my ansible execution using below play...
|
I’m trying to perform the fixpack upgrade in a specific order. Primary, secondary, federation (one at a time), reverse proxies (one at a time).
So I created a playbook that has a play for each group.
So the primary will be rebooting and it starts on the secondary without waiting for the primary to be back on line.
Thanks
Bill
From: Ram Sreerangam [mailto:notifications@github.com]
Sent: Thursday, September 14, 2017 9:53 PM
To: IBM-Security/isam-ansible-playbook-sample
Cc: Willett II, William D W1CIP; Author
Subject: Re: [IBM-Security/isam-ansible-playbook-sample] Installing 9.0.3.0 IF0002 (#5)
I have been using the fixpack with v9.0.3 IF#2 with no issues. I agree the handler may need to be fixed to wait for the appliance to finish rebooting. I am not following the comment about playbook will go to next host - that should not matter. Are you trying to do something after the fixpack installs in the same playbook?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_IBM-2DSecurity_isam-2Dansible-2Dplaybook-2Dsample_issues_5-23issuecomment-2D329655802&d=DwMFaQ&c=WlnXFIBCT3pmNh_w8hYeLw&r=dw2ntgsgilP2mX2ahyxWsOxR0JGpXcOU1-F7caKwf6c&m=gEQwCvxkdCYLLvXoLbH84rnRND7rV1TB7e1q9lwHa10&s=zKW1PQ6daiHRxrPIPIzzvsJwCSuKcxAhlKuGm3TmKsQ&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AajJgyMRFMrZkdHVkQ6Tex0U-2DL7x5NFRks5sidiSgaJpZM4PYS-5FW&d=DwMFaQ&c=WlnXFIBCT3pmNh_w8hYeLw&r=dw2ntgsgilP2mX2ahyxWsOxR0JGpXcOU1-F7caKwf6c&m=gEQwCvxkdCYLLvXoLbH84rnRND7rV1TB7e1q9lwHa10&s=KbcbqpkM2K58T4zyrRYmOIFllaC669NVTyi2fCXjQNU&e=>.
------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: If you have received this email in error,
please immediately notify the sender by e-mail at the address shown.
This email transmission may contain confidential information. This
information is intended only for the use of the individual(s) or entity to
whom it is intended even if addressed incorrectly. Please delete it from
your files if you are not the intended recipient. Thank you for your
compliance. Copyright (c) 2017 Cigna
==============================================================================
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using playbook install_fixpack.yml with IF0002, this fixpack involves a reboot. The playbook handlers don't seem to support this. I am using the serial: 1 parameter to perform the upgrade in a serial manner. The play book will go onto the next host before first host has rebooted and is back on line.
Also when i run this against PS/FED appliances it works, but when run against RP appliances it installs the fixpack but errors out after the first host and stops execution after the commit changes task.
Note: I've used this playbook to install the 9.0.3.0 "restash" fixpack with no issues.
The text was updated successfully, but these errors were encountered: