You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Set a 'variables' entry to mark an ongoing DB update and have connect_to_db() check and, if set, loop until the variable is released (with a sane timeout).
…sable triggers. Normal users can't set the 'session_replication_role' and I will need some time to understand the effects of allowing a user to disable the triggers (ideally find a way to restrict the trigger disable to just the scancore DB). See issue #76. This also fixes a bug where ScanCore would not sync.
* Added 'timout 15' to all calls in 'AN::Tools::Striker->_gather_node_details()' that might hang with a failed or pending fence so that the Striker UI won't hang. Still need to make sure that the display is sane in a hung case though.
* Removed the old email section of the default striker.conf.
* Added 'sys::install_manifest::default::update_os = [0,1]' to allow the user to control if Anvil! nodes get updated by controlling the install manifest '<update os="true" />' element's attribute.
* Added '--no-os-updates' to striker-installer to prevent OS updates during the dashboard stage-2 as well.
* Updated 'anvil-generate-iso' to support RHEL 6.7 and made the 6.x set by the OS name.
Signed-off-by: Digimer <[email protected]>
Set a 'variables' entry to mark an ongoing DB update and have connect_to_db() check and, if set, loop until the variable is released (with a sane timeout).
Then setup the ScanCore schema to allow the Striker user to set/release 'session_replication_role'. See C. Keane's reply in this thread: https://forums.aws.amazon.com/thread.jspa?messageID=561509.
The text was updated successfully, but these errors were encountered: