1. 29 Oct, 2019 1 commit
  2. 08 Oct, 2019 1 commit
  3. 07 Oct, 2019 5 commits
  4. 04 Oct, 2019 5 commits
  5. 01 Oct, 2019 2 commits
  6. 30 Sep, 2019 1 commit
  7. 25 Sep, 2019 3 commits
  8. 10 Sep, 2019 3 commits
  9. 09 Sep, 2019 2 commits
  10. 30 Aug, 2019 2 commits
  11. 28 Aug, 2019 2 commits
  12. 27 Aug, 2019 1 commit
  13. 22 Aug, 2019 2 commits
  14. 20 Aug, 2019 2 commits
  15. 13 Aug, 2019 1 commit
  16. 12 Aug, 2019 1 commit
    • Guillaume Abrioux's avatar
      osd: copy systemd-device-to-id.sh on all osd nodes before running it · 81906344
      Guillaume Abrioux authored
      Otherwise it will fail when running rolling_update.yml playbook because
      of `serial: 1` usage.
      The task which copies the script is run against the current node being
      played only whereas the task which runs the script is run against all
      nodes in a loop, it ends up with the typical error:
      
      ```
      2019-08-08 17:47:05,115 p=14905 u=ubuntu |  failed: [magna023 -> magna030] (item=magna030) => {
          "changed": true,
          "cmd": [
              "/usr/bin/env",
              "bash",
              "/tmp/systemd-device-to-id.sh"
          ],
          "delta": "0:00:00.004339",
          "end": "2019-08-08 17:46:59.059670",
          "invocation": {
              "module_args": {
                  "_raw_params": "/usr/bin/env bash /tmp/systemd-device-to-id.sh",
                  "_uses_shell": false,
                  "argv": null,
                  "chdir": null,
                  "creates": null,
                  "executable": null,
                  "removes": null,
                  "stdin": null,
                  "warn": true
              }
          },
          "item": "magna030",
          "msg": "non-zero return code",
          "rc": 127,
          "start": "2019-08-08 17:46:59.055331",
          "stderr": "bash: /tmp/systemd-device-to-id.sh: No such file or directory",
          "stderr_lines": [
              "bash: /tmp/systemd-device-to-id.sh: No such file or directory"
          ],
          "stdout": "",
          "stdout_lines": []
      }
      ```
      
      Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1739209
      
      Signed-off-by: default avatarGuillaume Abrioux <gabrioux@redhat.com>
      81906344
  17. 08 Aug, 2019 1 commit
  18. 07 Aug, 2019 1 commit
  19. 06 Aug, 2019 1 commit
    • Dimitri Savineau's avatar
      shrink-osd: Stop ceph-disk container based on ID · 343eec7a
      Dimitri Savineau authored
      Since bedc0ab6
      
       we now manage ceph-osd systemd unit scripts based on ID
      instead of device name but it was not present in the shrink-osd
      playbook (ceph-disk version).
      To keep backward compatibility on deployment that didn't do yet the
      transition on OSD id then we should stop unit scripts for both device
      and ID.
      This commit adds the ulimit nofile container option to get better
      performance on ceph-disk commands.
      It also fixes an issue when the OSD id matches multiple OSD ids with
      the same first digit.
      
      $ ceph-disk list | grep osd.1
       /dev/sdb1 ceph data, prepared, cluster ceph, osd.1, block /dev/sdb2
       /dev/sdg1 ceph data, prepared, cluster ceph, osd.12, block /dev/sdg2
      
      Finally removing the shrinked OSD directory.
      Signed-off-by: default avatarDimitri Savineau <dsavinea@redhat.com>
      343eec7a
  20. 01 Aug, 2019 1 commit
  21. 31 Jul, 2019 1 commit
    • Dimitri Savineau's avatar
      ceph-osd: check container engine rc for pools · 4dffcfb4
      Dimitri Savineau authored
      When creating OpenStack pools, we only check if the return code from
      the pool list command isn't 0 (ie: if it doesn't exist). In that case,
      the return code will be 2. That's why the next condition is rc != 0 for
      the pool creation.
      But in containerized deployment, the return code could be different if
      there's a failure on the container engine command (like container not
      running). In that case, the return code could but either 1 (docker) or
      125 (podman) so we should fail at this point and not in the next tasks.
      
      Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1732157
      
      Signed-off-by: default avatarDimitri Savineau <dsavinea@redhat.com>
      (cherry picked from commit d549fffd)
      4dffcfb4
  22. 30 Jul, 2019 1 commit
    • Dimitri Savineau's avatar
      tests: Update ooo-collocation scenario · bf8bd4c0
      Dimitri Savineau authored
      The ooo-collocation scenario was still using an old container image and
      doesn't match the requirement on latest stable-3.2 code. We need to use
      at least the container image v3.2.5.
      Also updating the OSD tests to reflect the changes introduced by the
      commit bedc0ab6
      
       because we don't have the OSD systemd unit script using
      device name anymore.
      Signed-off-by: default avatarDimitri Savineau <dsavinea@redhat.com>
      bf8bd4c0