- 27 Apr, 2020 1 commit
-
-
Guillaume Abrioux authored
This commit moves the dummy container creation task right before the cephx keys creation task so it can't be run out of time. Also, this commit makes the dummy container running for ever. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1828105 Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com>
-
- 23 Apr, 2020 2 commits
-
-
ianwatsonrh authored
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1827271 Signed-off-by:
ianwatsonrh <ianwatson@redhat.com> (cherry picked from commit ccf6a7f1)
-
Guillaume Abrioux authored
This commit is the first of a serie in order to describe all day-2 operations that are possible via ceph-ansible using a set of playbook provided in `infrastructure-playbooks` directory. Fixes: #5061 Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit 7e800303)
-
- 20 Apr, 2020 1 commit
-
-
Rishabh Dave authored
Error message were moved to from stdout in stderr here - https://github.com/ceph/ceph/commit/b8d6dcbe9f803c96c0af68da54f1262e9b6a9e77#diff-20f7c578a4e69ec61a5869d706567a24R137. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1793542 Signed-off-by:
Rishabh Dave <ridave@redhat.com> (cherry picked from commit 4249d1e0)
-
- 14 Apr, 2020 1 commit
-
-
Dimitri Savineau authored
We were not testing the right ansible_distribution fact value for RHEL distribution. This commit also updates the minial RHEL version supported by RHCS. Signed-off-by:
Dimitri Savineau <dsavinea@redhat.com> (cherry picked from commit 5de74fe5)
-
- 07 Apr, 2020 3 commits
-
-
Guillaume Abrioux authored
There's no need to have two plays anymore since we now set/unset osd flags in `ceph-osd` role. Also, this commit makes the role `ceph-facts` to be called after `ceph-defaults` Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com>
-
Guillaume Abrioux authored
This commit makes this playbook gathering facts from all other nodes but clients. When collocating OSDs on other nodes it can fail like following: ``` fatal: [vm252-11]: FAILED! => { "msg": "'ansible.vars.hostvars.HostVarsVars object' has no attribute 'ansible_hostname'" } ``` In that case, a fact from a RGW node is called when rendering the `ceph.conf.j2` but it fails because facts are gathered only from mon and osd nodes. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1806765 Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com>
-
Guillaume Abrioux authored
this commit fixes a bug when using `add-osd.yml` playbook. `noup` flag is set early but it never got unset before the "wait for pgs clean" check, so the playbook always fails because OSDs aren't never seen UP. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1816023 Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com>
-
- 03 Apr, 2020 3 commits
-
-
Guillaume Abrioux authored
Fetch the key when it is present in the cluster but not on the node. Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit ccfa2499)
-
Guillaume Abrioux authored
553584cb introduced a regression when no secret is passed, it overwrites the secret each time the task is run. Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit 003defec)
-
Guillaume Abrioux authored
With this change, the state `present` is enough to update a keyring. If the keyring already exist, it will be updated if caps or secret passed to the module are different. If the keyring doen't exist, it will be created. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1808367 Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit 553584cb)
-
- 02 Apr, 2020 1 commit
-
-
Dimitri Savineau authored
Since 306ce823 we explicitly fail when there's no mgr node preent in the inventory. fatal: [mon0]: FAILED! => { "changed": false } MSG: Please add a mgr host to your inventory. Signed-off-by:
Dimitri Savineau <dsavinea@redhat.com>
-
- 31 Mar, 2020 2 commits
-
-
Guillaume Abrioux authored
Creating crush rules even with no crush hierarchy configuration is a valid scenario so we shouldn't be bound to the first task result (which configure crush hierarchy) to be able to add new crush rules. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1816989 Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit 5b047638)
-
Dimitri Savineau authored
This adds a symlink to the site-docker.yml.sample playbook. Signed-off-by:
Dimitri Savineau <dsavinea@redhat.com>
-
- 30 Mar, 2020 3 commits
-
-
Guillaume Abrioux authored
just like site.yml and rolling_update, let's exclude clients node from the fact gathering. Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit 332c3937) (cherry picked from commit 5c3ba078)
-
Guillaume Abrioux authored
This commit excludes client nodes from facts gathering, they are not needed and can speed up this task. Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit 865d2eac)
-
John Fulton authored
Client configuration with --limit fails without this patch because certain tasks are only done to the first host in the _filtered_clients list and it's likely that first host will not be included in what's sepcified with --limit. To fix this the _filtered_clients list should be built from all clients in the inventory that are also in the running play. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1798781 Signed-off-by:
John Fulton <fulton@redhat.com> (cherry picked from commit e4bf4857)
-
- 26 Mar, 2020 1 commit
-
-
Guillaume Abrioux authored
This is no longer true, let's remove this comment given that this option is not ignored in containerized deployments. Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit e551b5ba)
-
- 25 Mar, 2020 1 commit
-
-
Guillaume Abrioux authored
Those tasks aren't needed in docker-common since the introduction of `ceph-infra` role. They are duplicated tasks. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1810376 Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit cd0195c5)
-
- 04 Mar, 2020 1 commit
-
-
Guillaume Abrioux authored
This inventory is intended to be used in the upgrade scenario in stable-4.0 branch. Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com>
-
- 03 Mar, 2020 1 commit
-
-
Guillaume Abrioux authored
This commit modifies the way we test add-osd scenario given that the playbook add-osd.yml is broken at the moment. As a workaround we can use main playbook with `--limit` to achieve this operation. Note: This commit is intended to be reverted once we get a fix. Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com>
-
- 17 Feb, 2020 4 commits
-
-
Dimitri Savineau authored
This patch changes the pg_num value of the rgw pools foo and bar to be a power of two number. Signed-off-by:
Dimitri Savineau <dsavinea@redhat.com>
-
Benoît Knecht authored
In 3c31b19a , I fixed the `customize pool size` task by replacing `item.size` with `item.value.size`. However, I missed the same issue in the `when` condition. Signed-off-by:
Benoît Knecht <bknecht@protonmail.ch> (cherry picked from commit 3842aa1a)
-
Benoît Knecht authored
RadosGW pools can be created by setting ```yaml rgw_create_pools: .rgw.root: pg_num: 512 size: 2 ``` for instance. However, doing so would create pools of size `osd_pool_default_size` regardless of the `size` value. This was due to the fact that the Ansible task used ``` {{ item.size | default(osd_pool_default_size) }} ``` as the pool size value, but `item.size` is always undefined; the correct variable is `item.value.size`. Signed-off-by:
Benoît Knecht <bknecht@protonmail.ch> (cherry picked from commit 3c31b19a)
-
Dimitri Savineau authored
Since ed36a11e we move the crush rules creation code from the ceph-mon to the ceph-osd role. To keep the backward compatibility we kept the possibility to set the crush variables on the mons side but we didn't move the default values. As a result, when using crush_rule_config set to true and wanted to use the default values for crush_rules then the crush rule ansible task creation will fail. "msg": "'ansible.vars.hostvars.HostVarsVars object' has no attribute 'crush_rules'" This patch move the default crush variables from ceph-mon to ceph-osd role but also use those default values when nothing is defined on the mons side. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1798864 Signed-off-by:
Dimitri Savineau <dsavinea@redhat.com> (cherry picked from commit 1fc6b337)
-
- 11 Feb, 2020 1 commit
-
-
Dimitri Savineau authored
We already stop the upgrade playbook (rolling_update.yml) if there's no mgr node present so we should also do the same for initial deployment. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1788644 Signed-off-by:
Dimitri Savineau <dsavinea@redhat.com>
-
- 05 Feb, 2020 1 commit
-
-
Dimitri Savineau authored
When using ceph aliases with commands that require manual intervention to stop then the command will keep running inside the container (like using Ctrl+c). For handling this, we should use the interactive session option (-it) with the docker commands. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1797874 Signed-off-by:
Dimitri Savineau <dsavinea@redhat.com>
-
- 03 Feb, 2020 4 commits
-
-
Mike Christie authored
During a rolling update we will run the ceph iscsigw tasks that start the daemons then run the configure_iscsi.yml tasks which can create iscsi objects like targets, disks, clients, etc. The problem is that once the daemons are started they will accept confifguration requests, or may want to update the system themself. Those operations can then conflict with the configure_iscsi.yml tasks that setup objects and we can end up in crashes due to the kernel being in a unsupported state. This could also happen during creation, but is less likely due to no objects being setup yet, so there are no watchers or users accessing the gws yet. The fix in this patch works for both update and initial setup. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1795806 Signed-off-by:
Mike Christie <mchristi@redhat.com> (cherry picked from commit 77f3b5d5)
-
Guillaume Abrioux authored
Add a script to retry several times to fire up VMs to avoid vagrant failures. Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> Co-authored-by:
Andrew Schoen <aschoen@redhat.com> (cherry picked from commit 1ecb3a93)
-
Guillaume Abrioux authored
When no monitor group is present in the inventory, this task fails. This affects only non-containerized deployments. Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit e7bc0794)
-
Guillaume Abrioux authored
This commit adds a new 'external ceph clients' scenario. Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit 64172935)
-
- 31 Jan, 2020 2 commits
-
-
Guillaume Abrioux authored
This commit allows ceph-ansible 3.2 to be run against ansible 2.7 However, note that running stable-3.2 against ansible 2.7 doesn't get any testing upstream this might break the playbook, only ansible 2.6 is officially supported. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1781635 Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com>
-
Guillaume Abrioux authored
Add new scenario 'all_in_one' in order to catch more collocated related issues. Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit 3e7dbb4b)
-
- 29 Jan, 2020 2 commits
-
-
Guillaume Abrioux authored
These tasks should have been removed with backport #4756 Note: This should have been backported from master but it's not possible because of too many change between master and stable-3.2 Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1740463 Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com>
-
Dimitri Savineau authored
The [rgw] section in the ceph.conf file or via the ceph_conf_overrides variable doesn't exist and has no effect. To apply overrides to all radosgw instances we should use either the [global] or [client] sections. Overrides per radosgw instance should still use the [client.rgw.{instance-name}] section. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1794552 Signed-off-by:
Dimitri Savineau <dsavinea@redhat.com> (cherry picked from commit 2f07b851)
-
- 14 Jan, 2020 1 commit
-
-
Guillaume Abrioux authored
To avoid confusion, let's change the default value from `0.0.0.0` to `x.x.x.x`. Users might think setting `0.0.0.0` will make the daemon binding on all interfaces. Fixes: #4827 Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit fc02fc98)
-
- 13 Jan, 2020 4 commits
-
-
Dimitri Savineau authored
This is enabled in the group_vars/clients file but it's overrided in extra vars by tox. Let's do it like that for now. Signed-off-by:
Dimitri Savineau <dsavinea@redhat.com>
-
Guillaume Abrioux authored
This commit adds a playbook to be played before we run purge playbook, it first creates an rbd image then map an rbd device on client0 so the purge playbook will try to unmap it. Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit db77fbda)
-
Guillaume Abrioux authored
in containerized context, using the binary provided in atomic os won't work because it's an old version provided by ceph-common based on 10.2.5. Using a container could be an idea but for large cluster with hundreds of client nodes, that would require to pull the image of each of them just to unmap the rbd devices. Let's use the sysfs method in order to avoid any issue related to ceph version that is shipped on the host. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1766064 Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit 3cfcc7a1)
-
Guillaume Abrioux authored
There is no need to run these tasks n times from each monitor. Signed-off-by:
Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit c878e995)
-