1. 09 Sep, 2019 1 commit
  2. 05 Sep, 2019 1 commit
  3. 11 Jul, 2019 1 commit
  4. 24 Jun, 2019 1 commit
  5. 17 Jun, 2019 2 commits
  6. 26 Mar, 2019 1 commit
  7. 11 Mar, 2019 1 commit
  8. 05 Mar, 2019 1 commit
  9. 21 Jan, 2019 1 commit
  10. 10 Jan, 2019 1 commit
  11. 07 Jan, 2019 1 commit
  12. 20 Dec, 2018 1 commit
  13. 07 Dec, 2018 1 commit
  14. 03 Dec, 2018 1 commit
  15. 14 Nov, 2018 2 commits
  16. 13 Nov, 2018 1 commit
  17. 26 Oct, 2018 1 commit
  18. 24 Oct, 2018 2 commits
  19. 12 Oct, 2018 1 commit
    • slaprunner: correctly patch software release path on import · f5eee79f
      usually, the software release path is :
      in a web runner : /srv/slapgrid/slappartXX/srv/runner/project/buildout.cfg
      in a test node : /srv/slapgrid/slappartX/srv/testnode/xx/inst/test0-XX/srv/runner/project/buldout.cfg
      
      the previous regex was replacing in all slappartX and test0-X by the new test0-Y
      which of course would make an existing path : /srv/slapgrid/test0-Y/.../test0-Y/...
      
      This commit only replace the latest occurence in order to have
      compatible code in the "normal" case, and in the test nodes
      Nicolas Wavrant committed
  20. 05 Oct, 2018 2 commits
    • slaprunner: exclude backup.signature while checking if file changed during export · 746d98d9
      Runner exporter failed with this message while checking if file changed during backup of instances files:
      
          < 3226bab4cd318d30cfbde18e6530435dcae3205f94103384ce266c3c73d1afeb  ./runner/instance/slappart2/srv/backup/pbs/slaprunner-slappart1-runner-1/backup.signature
          < 3226bab4cd318d30cfbde18e6530435dcae3205f94103384ce266c3c73d1afeb  ./runner/instance/slappart3/srv/backup/runner/backup.signature
          < 3226bab4cd318d30cfbde18e6530435dcae3205f94103384ce266c3c73d1afeb  ./runner/instance/slappart5/srv/backup/runner/backup.signature
          5248d5244
          < bb3d96876d1d6cecee9878d835e7515215fc5d2a6ae6b647d0e7915c36700b54  ./runner/instance/slappart4/srv/backup/runner/backup.signature
          ERROR: Some backups are not consistent, exporter should be re-run.
      
      This is because instance in webrunner has also backup.signature the file is excluded while doing sha256sum on backup file:
      
          find -type f ! -name backup.signature -print0 | xargs -0 sha256sum | sort -k 66 > backup.signature
      
      A fix is to exclude backup.signature in `find`.
      Alain Takoudjou committed
    • slaprunner: do not try to chdir if not a directory while building exclude list · 220411a0
      If instance/slappartXX is not a folder but file, skip chdir else import/export fail with a message like:
      
          /srv/slapgrid/slappart18/bin/runner-exporter run at : Thu Oct  4 04:30:03 CEST 2018
          Traceback (most recent call last):
            File "<stdin>", line 17, in <module>
          OSError: [Errno 20] Not a directory: '/srv/slapgrid/slappart18/srv//runner/instance/slappart5-mariadb.dump.sql.gz'
      Alain Takoudjou committed
  21. 03 Oct, 2018 2 commits
  22. 28 Sep, 2018 1 commit
  23. 21 Sep, 2018 1 commit
  24. 13 Sep, 2018 1 commit
  25. 03 Sep, 2018 1 commit
  26. 30 Aug, 2018 1 commit
  27. 29 Aug, 2018 2 commits
  28. 17 Aug, 2018 1 commit
  29. 13 Aug, 2018 1 commit
  30. 03 Aug, 2018 1 commit
    • correctly propagate password to requested instances · 8d4b5445
      the recipe slapos.cookbook:generate.password will install the password only after the [request-xx] was called for the first time. Then the second run of buildout the password can change as it was not stored yet. We use publish-early to make it persistent on master and avoid inconsistency between published password and stored one.
      
      /reviewed-on !370
      Alain Takoudjou committed
  31. 31 Jul, 2018 1 commit
  32. 30 Jul, 2018 2 commits
  33. 25 Jul, 2018 1 commit