# SuseManager Ansible does not recognize Inventory

**URL:** <https://forums.suse.com/t/susemanager-ansible-does-not-recognize-inventory/41983>\
**Category:** SUSE Multi Linux Manager\
**Created:** [November 22, 2023, 9:21am UTC](https://forums.suse.com/t/susemanager-ansible-does-not-recognize-inventory/41983 "2023-11-22T09:21:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Haensel](https://avatars.discourse-cdn.com/v4/letter/h/59ef9b/32.png) [@Haensel](https://forums.suse.com/u/Haensel)\
**Post date:** [November 22, 2023, 9:21am UTC](https://forums.suse.com/t/susemanager-ansible-does-not-recognize-inventory/41983/1 "2023-11-22T09:21:08Z")

</div>

![Unbenannt](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/4/464b31476b5d2067f50a9646617243a9682906d1.png)

Hello to all,  
Have any of you ever had this problem?  
Somehow the Suse Manager does not recognize the servers that are definitely managed by it.  
Is there a setting in the SuseManager that still needs to be activated?

---

<div class="post-metadata">

**Author:** ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)\
**Post date:** [November 22, 2023, 6:29pm UTC](https://forums.suse.com/t/susemanager-ansible-does-not-recognize-inventory/41983/2 "2023-11-22T18:29:29Z")

</div>

My reading of [Setup Ansible control node | SUSE Manager 4.3 Documentation](https://documentation.suse.com/suma/4.3/en/suse-manager/administration/ansible-setup-control-node.html#configure-ansible-inventory-files) suggests that you need to create and add your hosts to /etc/ansible/hosts - I don’t think it uses SUSE Manager’s own “inventory”

---

<div class="post-metadata">

**Author:** ![Haensel](https://avatars.discourse-cdn.com/v4/letter/h/59ef9b/32.png) [@Haensel](https://forums.suse.com/u/Haensel)\
**Post date:** [November 23, 2023, 9:26am UTC](https://forums.suse.com/t/susemanager-ansible-does-not-recognize-inventory/41983/3 "2023-11-23T09:26:08Z")

</div>

Exactly. SUSE Manager does not do this either.  
It only manages the devices. It also knows the devices that it manages. As shown in the picture, there is the item: “Registered Systems”. Unfortunately, my devices are missing here.

The file /etc/ansible/hosts only contains host names and SUSE should compare this machine with its own managed (Registered Systems). Alternatively, the devices should be listed under “Unknown Hostnames”. Which it does not do either

---

<div class="post-metadata">

**Author:** ![Haensel](https://avatars.discourse-cdn.com/v4/letter/h/59ef9b/32.png) [@Haensel](https://forums.suse.com/u/Haensel)\
**Post date:** [December 1, 2023, 8:27am UTC](https://forums.suse.com/t/susemanager-ansible-does-not-recognize-inventory/41983/4 "2023-12-01T08:27:54Z")

</div>

![AnsibleInventory](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/8/8a0365da2a5207cc8edcd3b2e3e82f379293340d.png)  
I have found something in the official Suse document about the new features in Suse Mananger 4.3. In this document there are also no registered machines listed.

I have already found an answer to the problem. I simply added the necessary SSH key to the inventory of the Ansibles with the parameter “ansible\_ssh\_private\_key\_file”

For example:  
\_meta:  
hostvars:  
server.local: {ansible\_ssh\_private\_key\_file: /root/.ssh/sshkey}