** Description changed:

  Bionic: cloud-init 18.2-14-g6d48d265-0ubuntu1
  
+ It also might we worth looking at using systemctl instead of service X
+ restart while looking at this bug.
  
- It might be some sort of race condition as cloud-init.log shows key files 
being written to /etc/salt/pki, a minute earlier than the directory's timestamp 
on /etc/salt/pki.
- 
+ It might be some sort of race condition as cloud-init.log shows key
+ files being written to /etc/salt/pki, a minute earlier than the
+ directory's timestamp on /etc/salt/pki.
  
  Additional log attempts:
  2018-05-07 21:07:47,811 - util.py[DEBUG]: Writing to /etc/salt/pki/minion.pub 
- wb: [644] 69 bytes
  2018-05-07 21:07:47,812 - util.py[DEBUG]: Writing to /etc/salt/pki/minion.pem 
- wb: [644] 70 bytes
  2018-05-07 21:07:47,813 - util.py[DEBUG]: Running command ['service', 
'salt-minion', 'restart'] with allowed return codes [0] (shell=False, 
capture=False)
  
  $ ls -ltr /etc/salt/ --full-time
  
  drwxr-xr-x 2 root root  2 2018-03-05 14:36:11.000000000 +0000 minion.d
  -rw-r--r-- 1 root root 67 2018-05-07 21:07:45.232367690 +0000 minion_id
  -rw-r--r-- 1 root root 34 2018-05-07 21:07:47.804370487 +0000 minion
  -rw-r--r-- 1 root root 18 2018-05-07 21:07:47.804370487 +0000 grains
  drwx------ 2 root root  2 2018-05-07 21:07:48.8403:71611 +0000 pki
  
  root@cloud-test-ubuntu-bionic-modules-salt-minion-4k9oerogscbsq9bqs3:~# ls 
/etc/salt/pki/
  root@cloud-test-ubuntu-bionic-modules-salt-minion-4k9oerogscbsq9bqs3:~#
  
- 
- 
- I'm wondering if service salt_minion restart is cleaning /etc/salt/pki? Can't 
find salt logs that claim to have removed these files.
+ I'm wondering if service salt_minion restart is cleaning /etc/salt/pki?
+ Can't find salt logs that claim to have removed these files.
  
  From /var/log/salt/minion log: the service restart might be responsible for 
this clean
  2018-05-07 21:07:47,828 [salt.utils.parsers:1048][WARNING ][1252] Minion 
received a SIGTERM. Exiting.
- 
  
  Subsequent apt-get remove --purge salt-minion; cloud-init clean --logs
  --reboot on the affected container doesn't reproduce this issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cloud-init 18.2-14-g6d48d265-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CloudName: LXD
  Date: Mon May  7 20:57:47 2018
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=C.UTF-8
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769754

Title:
  salt-minion: public/private keys not preserved in /etc/salt/pki

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1769754/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to