Re: [ceph-users] Re: octopus v15.2.17 QE Validation status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fr, 2022-07-29 at 08:01 +0000, Sven Kieske wrote:
> On Fr, 2022-07-29 at 08:13 +1000, Brad Hubbard wrote:
> > For octopus you should be using stable_5.0 as per
> > https://docs.ceph.com/projects/ceph-ansible/en/latest/#releases
> > 
> > What error are you referring to?
> 
> 
> I'm currently getting this error[1] on stable-5.0 branch, deploying
> octopus to our virtual dev environment (wrapped via terraform).
> 
> I was until now unable to pinpoint the exact error condition, it seems
> like ansible thinks the `mon_group_name` group is empty, but it's definitely not!
> 
> This is running on commit 18064032a93e04fe1aebfa2493bd9601df89a01f (stable-5.0)
> with ansible 2.9.27, that being said, I didn't check if a newer ansible version
> helps or is required, but the requirements file doesn't indicate this.
> 
> this is currently being run on ubuntu 18.04 VMs.
> 
> the same virtual environment deploys fine with the stable-4.0 branch and the EOL nautilus release.
> 
> 
> [1]:
> 
> TASK [ceph-facts : get current default crush rule details] *********************
> Monday 25 July 2022  13:17:19 +0000 (0:00:00.038)       0:05:23.227 *********** 
> fatal: [10.60.0.153 -> {{ delegated_node | default(groups[mon_group_name][0]) }}]: FAILED! => 
>   msg: |-
>     The conditional check 'inventory_hostname == groups.get('_filtered_clients', []) | first' failed. The error was: error while evaluating conditional (inventory_hostname ==
> groups.get('_filtered_clients', []) | first): No first item, sequence was empty.
>   
>     The error appears to be in '/ceph-ansible/roles/ceph-facts/tasks/get_def_crush_rule_name.yml': line 2, column 3, but may
>     be elsewhere in the file depending on the exact syntax problem.
>   
>     The offending line appears to be:
>   
>     ---
>     - name: get current default crush rule details
>       ^ here

I found the error:

we didn't check for changes in our custom site.yml versus upstreams
site.yml.sample

turns out that in this commit:
https://github.com/ceph/ceph-ansible/commit/d6fcd78e72186aa748b00f3b840472f464ebcbba

the generation of the group `_filtered_clients` was moved from

`roles/ceph-client/tasks/create_users_keys.yml` into `site.yml.sample`

thus the group was empty in our deployment and threw an error.

I'm not sure if maybe the documentation regarding site.yml could get improved:

https://docs.ceph.com/projects/ceph-ansible/en/stable-5.0/index.html#playbook

it could maybe mention that you should diff your custom site.yml versus upstreams yaml.

another solution would be to not put critical tasks inside a sample file. ;)

have a nice weekend all!

-- 
Mit freundlichen Grüßen / Regards

Sven Kieske
Systementwickler / systems engineer
 
 
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 4-6
32339 Espelkamp
 
Tel.: 05772 / 293-900
Fax: 05772 / 293-333
 
https://www.mittwald.de
 
Geschäftsführer: Robert Meyer, Florian Jürgens
 
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen

Informationen zur Datenverarbeitung im Rahmen unserer Geschäftstätigkeit 
gemäß Art. 13-14 DSGVO sind unter www.mittwald.de/ds abrufbar.

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx

[Index of Archives]     [CEPH Users]     [Ceph Devel]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux