Activity log for bug #1615983

Date Who What changed Old value New value Message
2016-08-23 08:40:14 Michele Baldessari bug added bug
2016-08-23 08:41:56 Michele Baldessari summary boostrap_node if checks are fragile if $:::hostname == boostrap_node checks are fragile
2016-08-23 08:42:03 Michele Baldessari summary if $:::hostname == boostrap_node checks are fragile if $::hostname == boostrap_node checks are fragile
2016-08-23 08:42:52 Michele Baldessari description We currently litter our code with the following if checks: if $::hostname == downcase($bootstrap_node) { $sync_db = true } else { $sync_db = false } We do so for a bunch of reasons, but mainly for: 1) Creating pacemaker resources only from a single node 2) Call sync_db commands to create sql tables and fixup sql data in general When we merged commit b345dbea16ad3edd600c62848d8ee116f4df16ee "Combine BootstrapNodeDeployment with AllNodesDeployment" we added a bootstrap node id not not only for controller nodes but for each type of nodes. This is problematic. Imagine the following scenario as an example: - Both Controllers and Compute nodes are configured with service aodh-api - Both controllers and computes will include the following snippet: """ if $::hostname == downcase($bootstrap_node) { $sync_db = true } else { $sync_db = false } if $step >= 3 and $sync_db { include ::aodh::db::mysql } """ - The if statement will hold true for both the controller 0 *and* compute 0, which means that they can be called at the same time, thereby opening up a race condition We currently litter our code with the following if checks: if $::hostname == downcase($bootstrap_node) {   $sync_db = true } else {   $sync_db = false } We do so for a bunch of reasons, but mainly for: 1) Creating pacemaker resources only from a single node 2) Call sync_db commands to create sql tables and fixup sql data in general When we merged commit b345dbea16ad3edd600c62848d8ee116f4df16ee "Combine BootstrapNodeDeployment with AllNodesDeployment" we added a bootstrap node id not not only for controller nodes but for each type of nodes. This is problematic. Imagine the following scenario as an example: - Both Controllers and Compute nodes are configured with service aodh-api - Both controllers and computes will include the following snippet: """   if $::hostname == downcase($bootstrap_node) {     $sync_db = true   } else {     $sync_db = false   }   if $step >= 3 and $sync_db {     include ::aodh::db::mysql   } """ - The if statement will hold true for both the controller 0 *and* compute 0, which means that they can be called at the same time, thereby opening up a race condition
2016-08-23 08:44:21 Michele Baldessari description We currently litter our code with the following if checks: if $::hostname == downcase($bootstrap_node) {   $sync_db = true } else {   $sync_db = false } We do so for a bunch of reasons, but mainly for: 1) Creating pacemaker resources only from a single node 2) Call sync_db commands to create sql tables and fixup sql data in general When we merged commit b345dbea16ad3edd600c62848d8ee116f4df16ee "Combine BootstrapNodeDeployment with AllNodesDeployment" we added a bootstrap node id not not only for controller nodes but for each type of nodes. This is problematic. Imagine the following scenario as an example: - Both Controllers and Compute nodes are configured with service aodh-api - Both controllers and computes will include the following snippet: """   if $::hostname == downcase($bootstrap_node) {     $sync_db = true   } else {     $sync_db = false   }   if $step >= 3 and $sync_db {     include ::aodh::db::mysql   } """ - The if statement will hold true for both the controller 0 *and* compute 0, which means that they can be called at the same time, thereby opening up a race condition We currently litter our code with the following if checks: if $::hostname == downcase($bootstrap_node) {   $sync_db = true } else {   $sync_db = false } We do so for a bunch of reasons, but mainly for: 1) Creating pacemaker resources only from a single node 2) Call sync_db commands to create sql tables and fixup sql data in general When we merged commit b345dbea16ad3edd600c62848d8ee116f4df16ee "Combine BootstrapNodeDeployment with AllNodesDeployment" we added a bootstrap node id not not only for controller nodes but for each type of nodes. This is problematic. Imagine the following scenario as an example: - Both Controllers and Compute nodes are configured to include aodh-api - Both controllers and computes will include the following snippet: """   if $::hostname == downcase($bootstrap_node) {     $sync_db = true   } else {     $sync_db = false   }   if $step >= 3 and $sync_db {     include ::aodh::db::mysql   } """ - The if statement will hold true for both controller 0 *and* compute 0,   which means that they can be called at the same time, thereby opening up   a race condition
2016-08-23 13:17:12 Emilien Macchi tripleo: status New Confirmed
2016-08-23 13:17:14 Emilien Macchi tripleo: importance Undecided High
2016-08-23 13:17:16 Emilien Macchi tripleo: milestone newton-3
2016-08-26 10:33:56 Steven Hardy tripleo: milestone newton-3 newton-rc1
2016-09-16 18:47:04 Emilien Macchi tripleo: milestone newton-rc1 newton-rc2
2016-09-19 21:33:07 Emilien Macchi tripleo: status Confirmed Triaged
2016-09-21 21:17:08 Steven Hardy tripleo: milestone newton-rc2 ocata-1
2016-11-11 16:15:28 Steven Hardy tripleo: milestone ocata-1 ocata-2
2016-12-08 17:14:52 OpenStack Infra tripleo: status Triaged In Progress
2016-12-08 17:14:52 OpenStack Infra tripleo: assignee Michele Baldessari (michele)
2016-12-14 22:01:44 Emilien Macchi tripleo: milestone ocata-2 ocata-3
2017-01-31 13:39:12 Emilien Macchi tripleo: milestone ocata-3 ocata-rc1
2017-02-16 15:27:54 Emilien Macchi tripleo: milestone ocata-rc1 ocata-rc2
2017-03-06 15:16:40 Emilien Macchi tripleo: milestone ocata-rc2 pike-1
2017-04-11 10:54:20 Emilien Macchi tripleo: milestone pike-1 pike-2
2017-06-08 20:31:06 Emilien Macchi tripleo: milestone pike-2 pike-3
2017-07-30 04:36:02 Emilien Macchi tripleo: milestone pike-3 pike-rc1
2017-08-25 13:40:09 Emilien Macchi tripleo: milestone pike-rc1 pike-rc2
2017-09-05 18:31:50 Emilien Macchi tripleo: milestone pike-rc2 queens-1
2017-10-23 16:07:10 Emilien Macchi tripleo: milestone queens-1 queens-2
2017-12-05 00:16:36 Alex Schultz tripleo: milestone queens-2 queens-3
2018-01-26 00:50:29 Emilien Macchi tripleo: milestone queens-3 queens-rc1
2018-03-02 20:15:02 Alex Schultz tripleo: milestone queens-rc1 rocky-1
2018-04-20 17:02:29 Alex Schultz tripleo: milestone rocky-1 rocky-2
2018-06-05 19:03:19 Emilien Macchi tripleo: milestone rocky-2 rocky-3
2018-07-26 13:41:29 Emilien Macchi tripleo: milestone rocky-3 rocky-rc1
2018-08-14 14:57:46 Alex Schultz tripleo: milestone rocky-rc1 stein-1
2018-10-30 16:12:43 Juan Antonio Osorio Robles tripleo: milestone stein-1 stein-2
2019-01-13 22:35:22 Emilien Macchi tripleo: milestone stein-2 stein-3
2019-03-14 02:30:24 Alex Schultz tripleo: milestone stein-3 stein-rc1
2019-04-15 18:46:10 Alex Schultz tripleo: milestone stein-rc1 train-1
2019-06-07 19:54:55 Alex Schultz tripleo: milestone train-1 train-2
2019-07-29 14:14:39 Alex Schultz tripleo: milestone train-2 train-3
2019-09-11 21:13:33 Alex Schultz tripleo: milestone train-3 ussuri-1
2019-12-19 14:48:34 Emilien Macchi tripleo: milestone ussuri-1 ussuri-2
2020-02-10 20:29:59 wes hayutin tripleo: milestone ussuri-2 ussuri-3
2020-04-13 17:19:05 wes hayutin tripleo: milestone ussuri-3 ussuri-rc3
2020-05-26 20:35:20 wes hayutin tripleo: milestone ussuri-rc3 victoria-1
2020-07-28 12:30:46 Emilien Macchi tripleo: milestone victoria-1 victoria-3
2020-11-03 11:47:54 Marios Andreou tripleo: milestone victoria-3 wallaby-1
2020-12-08 11:22:05 Marios Andreou tripleo: milestone wallaby-1 wallaby-2
2021-01-29 15:08:12 Marios Andreou tripleo: milestone wallaby-2 wallaby-3
2021-02-19 15:51:26 Marios Andreou tripleo: status In Progress Incomplete
2021-02-19 15:51:26 Marios Andreou tripleo: milestone wallaby-3