yahoo-eng-team team mailing list archive

[mhg <1822823@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Brief Description 
----------------- 
CLI: system service-parameter-list shows settings of services including panko, which leads users to think CLI 'system service-parameter-modify' is a way to change the settings. 
But changing setting value 'event_time_to_live' for service panko did not work (major alarms Configuration is out-of-date were triggered): 
1 CLI executed without error and returned expected output (as before): 
system service-parameter-modify panko database event_time_to_live=12345 
+-------------+--------------------------------------+ 
| Property | Value | 
+-------------+--------------------------------------+ 
| uuid | 82ccc101-0c90-4af3-a0bb-193843025752 | 
| service | panko | 
| section | database | 
| name | event_time_to_live | 
| value | 12345 | 
| personality | None | 
| resource | None | 
+-------------+--------------------------------------+ 

2 system alarms were triggered as (before): 
 +-------------+--------------------------------------+ 
| Property | Value | 
+-------------+--------------------------------------+ 
| uuid | 82ccc101-0c90-4af3-a0bb-193843025752 | 
| service | panko | 
| section | database | 
| name | event_time_to_live | 
| value | 12345 | 
| personality | None | 
| resource | None | 
+-------------+--------------------------------------+ 

3 but the value '12345' did not populated into config files: 
               /etc/pank/pank.conf on controllers still have the old value (now the file do not exist anymore) 
               /etc/pank/pank.conf on panko-api containers still have the old value 

So here're some issues: 
        1 If it is not supported any more for user to modify 'event_time_to_live' for panko using CLI 'system service-parameter-modify panko database', it might be better to reject the request and return messages telling user so. 
        2 Major type of alarm should not be raised if it changes will not be done. 
        3 Acceptable valid values for users to set should be documented or even better included in the output message in cases user inputs were invalid. 

Severity 
-------- 
Major 


Steps to Reproduce 
------------------ 
system service-parameter-modify panko database event_time_to_live=12345 

Expected Behavior 
------------------ 
1 the CLI executed without errors 
2 'Configuration is out-of-date' alarms were triggered, and cleared after a period of time 
3 new values were populated to persistent storage /etc/panko/panko.conf 
   on controllers (platform) or inside containers of panko-api 

Actual Behavior 
---------------- 
1 the CLI executed without errors 
2 'Configuration is out-of-date' alarms were triggered, and cleared after a period of time 
3 No changes made to /etc/panko/panko.conf 
   on controllers (platform) or inside containers of panko-api 

Reproducibility 
--------------- 
Reproducible 

System Configuration 
-------------------- 
Multi-node system 

Branch/Pull Time/Commit 
----------------------- 
master as of 20190330T013000Z 

Last Pass 
-------------- 
2019-02-15_20-18-00 

Timestamp/Logs 
-------------- 
2019-03-31 15:55:5

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1822823

Title:
  changing 'event_time_to_live' for panko service via service-parameter-
  modify failed

Status in neutron:
  New

Bug description:
  Brief Description 
  ----------------- 
  CLI: system service-parameter-list shows settings of services including panko, which leads users to think CLI 'system service-parameter-modify' is a way to change the settings. 
  But changing setting value 'event_time_to_live' for service panko did not work (major alarms Configuration is out-of-date were triggered): 
  1 CLI executed without error and returned expected output (as before): 
  system service-parameter-modify panko database event_time_to_live=12345 
  +-------------+--------------------------------------+ 
  | Property | Value | 
  +-------------+--------------------------------------+ 
  | uuid | 82ccc101-0c90-4af3-a0bb-193843025752 | 
  | service | panko | 
  | section | database | 
  | name | event_time_to_live | 
  | value | 12345 | 
  | personality | None | 
  | resource | None | 
  +-------------+--------------------------------------+ 

  2 system alarms were triggered as (before): 
   +-------------+--------------------------------------+ 
  | Property | Value | 
  +-------------+--------------------------------------+ 
  | uuid | 82ccc101-0c90-4af3-a0bb-193843025752 | 
  | service | panko | 
  | section | database | 
  | name | event_time_to_live | 
  | value | 12345 | 
  | personality | None | 
  | resource | None | 
  +-------------+--------------------------------------+ 

  3 but the value '12345' did not populated into config files: 
                 /etc/pank/pank.conf on controllers still have the old value (now the file do not exist anymore) 
                 /etc/pank/pank.conf on panko-api containers still have the old value 

  So here're some issues: 
          1 If it is not supported any more for user to modify 'event_time_to_live' for panko using CLI 'system service-parameter-modify panko database', it might be better to reject the request and return messages telling user so. 
          2 Major type of alarm should not be raised if it changes will not be done. 
          3 Acceptable valid values for users to set should be documented or even better included in the output message in cases user inputs were invalid. 

  Severity 
  -------- 
  Major 

  
  Steps to Reproduce 
  ------------------ 
  system service-parameter-modify panko database event_time_to_live=12345 

  Expected Behavior 
  ------------------ 
  1 the CLI executed without errors 
  2 'Configuration is out-of-date' alarms were triggered, and cleared after a period of time 
  3 new values were populated to persistent storage /etc/panko/panko.conf 
     on controllers (platform) or inside containers of panko-api 

  Actual Behavior 
  ---------------- 
  1 the CLI executed without errors 
  2 'Configuration is out-of-date' alarms were triggered, and cleared after a period of time 
  3 No changes made to /etc/panko/panko.conf 
     on controllers (platform) or inside containers of panko-api 

  Reproducibility 
  --------------- 
  Reproducible 

  System Configuration 
  -------------------- 
  Multi-node system 

  Branch/Pull Time/Commit 
  ----------------------- 
  master as of 20190330T013000Z 

  Last Pass 
  -------------- 
  2019-02-15_20-18-00 

  Timestamp/Logs 
  -------------- 
  2019-03-31 15:55:5

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1822823/+subscriptions