| 
      
        2019-05-03
      
      §
     | 
  
    
  | 09:39 | 
  <arturo> | 
  puppet should be now fine across toolforge (except tools-puppetdb-01 which is WIP I think) | 
  [tools] | 
            
  | 09:37 | 
  <arturo> | 
  fix puppet in tools-elastic-03, archived jessie repos, weird rsyslog-kafka package situation | 
  [tools] | 
            
  | 09:33 | 
  <arturo> | 
  fix puppet in tools-elastic-02, archived jessie repos, weird rsyslog-kafka package situation | 
  [tools] | 
            
  | 09:24 | 
  <arturo> | 
  fix puppet in tools-elastic-01, archived jessie repos, weird rsyslog-kafka package situation | 
  [tools] | 
            
  | 09:18 | 
  <arturo> | 
  solve a weird apt situation in tools-puppetmaster-01 regarding the rsyslog-kafka package (puppet agent was failing) | 
  [tools] | 
            
  | 09:16 | 
  <arturo> | 
  solve a weird apt situation in tools-worker-1028 regarding the rsyslog-kafka package | 
  [tools] | 
            
  
    | 
      
        2019-04-23
      
      §
     | 
  
    
  | 15:26 | 
  <arturo> | 
  T221225 rebooting tools-sgebastion-08 to cleanup sssd | 
  [tools] | 
            
  | 15:19 | 
  <arturo> | 
  T221225 creating tools-sgebastion-09 for testing sssd stuff | 
  [tools] | 
            
  | 13:06 | 
  <arturo> | 
  T221225 use `profile::ldap::client::labs::client_stack: classic` in the puppet bastion prefix, again. Rollback again. | 
  [tools] | 
            
  | 12:57 | 
  <arturo> | 
  T221225 use `profile::ldap::client::labs::client_stack: sssd` in the puppet bastion prefix, try again with sssd in the bastions, reboot them | 
  [tools] | 
            
  | 10:28 | 
  <arturo> | 
  T221225 use `profile::ldap::client::labs::client_stack: classic` in the puppet bastion prefix | 
  [tools] | 
            
  | 10:27 | 
  <arturo> | 
  T221225 rebooting tools-sgebastion-07 to clean sssd confiuration | 
  [tools] | 
            
  | 10:16 | 
  <arturo> | 
  T221225 disable puppet in tools-sgebastion-08 for sssd testing | 
  [tools] | 
            
  | 09:49 | 
  <arturo> | 
  T221225 run puppet agent in the bastions and reboot them with sssd | 
  [tools] | 
            
  | 09:43 | 
  <arturo> | 
  T221225 use `profile::ldap::client::labs::client_stack: sssd` in the puppet bastion prefix | 
  [tools] | 
            
  | 09:41 | 
  <arturo> | 
  T221225 disable puppet agent in the bastions | 
  [tools] | 
            
  
    | 
      
        2019-04-17
      
      §
     | 
  
    
  | 12:08 | 
  <arturo> | 
  T221225 rebooting bastions to clean sssd. We are back to nscd/nslcd until we figure out what's wrong here | 
  [tools] | 
            
  | 11:58 | 
  <arturo> | 
  T221205 sssd was deployed successfully into all webgrid nodes | 
  [tools] | 
            
  | 11:39 | 
  <arturo> | 
  deploy sssd to tools-sge-services-03/04 (includes reboot) | 
  [tools] | 
            
  | 11:31 | 
  <arturo> | 
  reboot bastions for sssd deployment | 
  [tools] | 
            
  | 11:30 | 
  <arturo> | 
  deploy sssd to bastions | 
  [tools] | 
            
  | 11:24 | 
  <arturo> | 
  disable puppet in bastions to deploy sssd | 
  [tools] | 
            
  | 09:52 | 
  <arturo> | 
  T221205 tools-sgewebgrid-lighttpd-0915 requires some manual intervention because issues in the dpkg database prevents deleting nscd/nslcd packages | 
  [tools] | 
            
  | 09:45 | 
  <arturo> | 
  T221205 tools-sgewebgrid-lighttpd-0913 requires some manual intervention because unconfigured packages prevents a clean puppet agent run | 
  [tools] | 
            
  | 09:12 | 
  <arturo> | 
  T221205 start deploying sssd to sgewebgrid nodes | 
  [tools] | 
            
  | 09:00 | 
  <arturo> | 
  T221205 add `profile::ldap::client::labs::client_stack: sssd` in horizon for the puppet prefixes `tools-sgewebgrid-lighttpd` and `tools-sgewebgrid-generic` | 
  [tools] | 
            
  | 08:56 | 
  <arturo> | 
  T221205 disable puppet in all tools-sgewebgrid-* nodes | 
  [tools] |