{"id":1281,"date":"2021-05-09T18:39:54","date_gmt":"2021-05-09T18:39:54","guid":{"rendered":"https:\/\/www.nicktailor.com\/?p=1281"},"modified":"2024-04-30T05:49:56","modified_gmt":"2024-04-30T05:49:56","slug":"how-to-create-a-new-host-in-foreman-with-ansible","status":"publish","type":"post","link":"https:\/\/nicktailor.com\/tech-blog\/how-to-create-a-new-host-in-foreman-with-ansible\/","title":{"rendered":"How to Create a New Host in Foreman with Ansible"},"content":{"rendered":"

Okay\u2026this one was quite difficult to find online<\/strong>. Seems like the ansible documentation for the foreman module was seriously lacking or not kept up to date by anyone. I searched for awhile to see if anyone had an actual working model of it.
\nNot<\/strong> even in the ansible chat rooms<\/strong> did anyone know….which was weak.<\/p>\n

So I spent some time getting this to work smoothly, and you will probably not find anywhere else on the web on how to do this. If you do show me\u2026.so I can kick myself.<\/strong><\/p>\n

Lets get dangerous then. \ud83d\ude0a<\/p>\n

Step by step:<\/p>\n

Foreman \u2013 Already setup and your \u201ccomputer resource<\/span>\u201d is hooked in (VMware<\/span>)<\/strong>
\nNote: The compute<\/em><\/span> profile<\/em><\/span>(<\/em><\/span>vmware<\/em><\/span>) when<\/em><\/span> hooked in<\/em><\/span>,<\/em><\/span> will<\/em><\/span> also<\/em><\/span> trigger a new <\/em><\/span>vm<\/em><\/span> creation in <\/em><\/span>vsphere<\/em><\/span> prepped to do DHCP. <\/em><\/span>You can combine variables from <\/em><\/span>vmware_guest<\/em><\/span> module and this module as they require similar variables to be passed. To setup a one stop <\/em><\/span>shop<\/em><\/span> to deploy in foreman and <\/em><\/span>vmware<\/em><\/span> with just using ansible. <\/em><\/span>Iv<\/em><\/span> done this already<\/em><\/span>\u2026..<\/em><\/span><\/strong>
\n
\nSpecial notes: The foreman I had setup did not have organisation or location configured. This caused the module to not function properly and I had to contact one of the developers who helped me patch the code so I didn\u2019t require them to be configured or defined. Which I will show you all how to do.<\/em><\/span><\/strong><\/p>\n

Ansible \u2013 Assuming you have it setup and working with python 2.7 not sure this module will work with python 3. <\/span>Havent<\/span> tried that yet<\/span>\u2026..<\/span><\/strong><\/p>\n

Module \u2013 TheForeman Collection<\/strong><\/p>\n

\n
\n
1.<\/span>To install it<\/strong><\/div>\n
\n
\n
a.<\/span>ansible-galaxy collection install <\/span>theforeman.foreman<\/span><\/strong><\/div>\n<\/div>\n
\n
b.<\/span>edit ansible.cfg file and add the following lines.<\/strong><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

Note: You can find the locations of these certs on foreman server. You will to copy them over to ansible for the <\/span>callback<\/span> to work properly. However, it is not needed to complete the host creation, you likely just see an error at the end of the play.<\/span><\/strong><\/p>\n

[<\/span>callback_foreman<\/span>]<\/span><\/strong><\/p>\n

url<\/span> = ‘http:\/\/foreman-1.tdr.corp-apps.com’<\/span><\/strong><\/p>\n

ssl_cert<\/span> = \/etc\/foreman-proxy\/<\/span>ssl-cert.pem<\/span><\/strong><\/p>\n

ssl_key<\/span> = \/etc\/foreman-proxy\/<\/span>ssl-pvt.pem<\/span><\/strong><\/p>\n

verify_certs<\/span> = \/etc\/foreman-proxy\/<\/span>ssl<\/span>-ca<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

Okay once installed you. If you look at the ansible documentation on how to manage hosts using this module\u2026from redhat.<\/p>\n

It utterly useless\u2026and will not work if you try to use the examples below.<\/span><\/p>\n

https:\/\/people.redhat.com\/evgeni\/fam-antsibull\/plugins\/host_module.html<\/a><\/p>\n

             – <\/span>name<\/span><\/strong>: <\/span>“Create<\/span> a<\/span> host”<\/span><\/p>\n

    <\/span>host<\/span><\/strong>:<\/span><\/p>\n

        <\/span>username<\/span><\/strong>: <\/span>“admin”<\/span><\/p>\n

        <\/span>password<\/span><\/strong>: <\/span>“<\/span>changeme<\/span>“<\/span><\/p>\n

        <\/span>server_url<\/span><\/strong>: <\/span>“https:\/\/foreman.example.com”<\/span><\/p>\n

        <\/span>name<\/span><\/strong>: <\/span>“<\/span>new_host<\/span>“<\/span><\/p>\n

        <\/span>hostgroup<\/span><\/strong>: <\/span>my_hostgroup<\/span><\/p>\n

        <\/span>state<\/span><\/strong>: present<\/span><\/p>\n

.<\/span><\/span><\/p>\n

\n
\n
2.<\/span>Okay now since my foreman is not configured with Organisation and Locations. <\/span>I had to patch the python code with the help of one of contributing authors of the module.<\/span><\/strong><\/div>\n<\/div>\n<\/div>\n

.<\/span><\/span><\/p>\n

\n
\n
3.<\/span>Apply the following patch.<\/span><\/strong><\/div>\n

.<\/span><\/span>The fix was to avoid trying to touch a specific resource that is only available when you have Org\/<\/span>Loc<\/span> enabled.<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

diff –git plugins\/module_utils\/<\/span>foreman_helper.py<\/span> plugins\/module_utils\/foreman_helper.py<\/span><\/strong><\/p>\n

index 432c76<\/span>df..<\/span>c9a3abda 100644<\/span><\/strong><\/p>\n

— plugins\/module_utils\/foreman_helper.py<\/span><\/strong><\/p>\n

+++ plugins\/module_utils\/foreman_helper.py<\/span><\/strong><\/p>\n

@@ -396,8 +396,9 @@ class <\/span>ForemanAnsibleModule<\/span>(<\/span>AnsibleModule<\/span>):<\/span><\/strong><\/p>\n

_<\/span>host_update<\/span> = <\/span>next(<\/span>x for x in _<\/span>host_methods<\/span> if x[‘name’] == ‘update’)<\/span><\/strong><\/p>\n

for param in [‘<\/span>location_id<\/span>‘, ‘<\/span>organization_id<\/span>‘]:<\/span><\/strong><\/p>\n

– _<\/span>host_update_taxonomy_param<\/span> = <\/span>next(<\/span>x for x in _<\/span>host_update<\/span>[‘params’] if x[‘name’] == param)<\/span><\/strong><\/p>\n

– _<\/span>host_update<\/span>[‘params’<\/span>].remove<\/span>(_<\/span>host_update_taxonomy_param<\/span>)<\/span><\/strong><\/p>\n

+ _<\/span>host_update_taxonomy_param<\/span> = <\/span>next(<\/span>(x for x in _<\/span>host_update<\/span>[‘params’] if x[‘name’] == param), None)<\/span><\/strong><\/p>\n

+ if _<\/span>host_update_taxonomy_param<\/span> is not None:<\/span><\/strong><\/p>\n

+ _<\/span>host_update<\/span>[‘params’<\/span>].remove<\/span>(_<\/span>host_update_taxonomy_param<\/span>)<\/span><\/strong><\/p>\n

@_<\/span>check_patch_needed<\/span>(<\/span>fixed_version<\/span>=’2.0.0′)<\/span><\/strong><\/p>\n

def _<\/span>patch_templates_resource_name<\/span>(self):<\/span><\/strong><\/p>\n<\/div>\n<\/div>\n

.<\/span><\/span><\/p>\n

\n
\n
4.<\/span>Once this patch is implemented. You will need a role that has all the correct variables to pass to your foreman in order for it to be able create a host without erroring.<\/span><\/strong><\/div>\n<\/div>\n<\/div>\n

.<\/span><\/span><\/p>\n

Trick<\/span>: with ansible you can write some of the code and run the playbook and if there are missing variables it will tell you what they are.<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

fatal: [testnick1]: FAILED! => {<\/span><\/strong><\/p>\n

“changed”: false, <\/span><\/strong><\/p>\n

“invocation”: {<\/span><\/strong><\/p>\n

“<\/span>module_args<\/span>“: {<\/span><\/strong><\/p>\n

“<\/span>activation_keys<\/span>“: null, <\/span><\/strong><\/p>\n

“architecture”: null, <\/span><\/strong><\/p>\n

“build”: null, <\/span><\/strong><\/p>\n

“comment”: null, <\/span><\/strong><\/p>\n

“<\/span>compute_attributes<\/span>“: null, <\/span><\/strong><\/p>\n

“<\/span>compute_profile<\/span>“: null, <\/span><\/strong><\/p>\n

“<\/span>compute_resource<\/span>“: null, <\/span><\/strong><\/p>\n

“<\/span>config_groups<\/span>“: null, <\/span><\/strong><\/p>\n

“<\/span>content_source<\/span>“: null, <\/span><\/strong><\/p>\n

“<\/span>content_view<\/span>“: null, <\/span><\/strong><\/p>\n

“domain”: null, <\/span><\/strong><\/p>\n

“enabled”: null, <\/span><\/strong><\/p>\n

“environment”: null, <\/span><\/strong><\/p>\n

“<\/span>hostgroup<\/span>“: “<\/span>my_hostgroup<\/span>“, <\/span><\/strong><\/p>\n

“image”: null, <\/span><\/strong><\/p>\n

“<\/span>interfaces_attributes<\/span>“: null, <\/span><\/strong><\/p>\n

“<\/span>ip<\/span>“: null, <\/span><\/strong><\/p>\n

“<\/span>kickstart_repository<\/span>“: null, <\/span><\/strong><\/p>\n

“<\/span>lifecycle_environment<\/span>“: null, <\/span><\/strong><\/p>\n

“location”: null, <\/span><\/strong><\/p>\n

“mac”: null, <\/span><\/strong><\/p>\n

“managed”: null, <\/span><\/strong><\/p>\n

“medium”: null, <\/span><\/strong><\/p>\n

“name”: “testnick1”, <\/span><\/strong><\/p>\n

“<\/span>openscap_proxy<\/span>“: null, <\/span><\/strong><\/p>\n

“<\/span>operatingsystem<\/span>“: null, <\/span><\/strong><\/p>\n

“organization”: null, <\/span><\/strong><\/p>\n

“owner”: null, <\/span><\/strong><\/p>\n

“<\/span>owner_group<\/span>“: null, <\/span><\/strong><\/p>\n

“parameters”: null, <\/span><\/strong><\/p>\n

“password”: “VALUE_SPECIFIED_IN_NO_LOG_PARAMETER”, <\/span><\/strong><\/p>\n

“<\/span>provision_method<\/span>“: null, <\/span><\/strong><\/p>\n

“<\/span>ptable<\/span>“: null, <\/span><\/strong><\/p>\n

“<\/span>puppet_ca_proxy<\/span>“: null, <\/span><\/strong><\/p>\n

“<\/span>puppet_proxy<\/span>“: null, <\/span><\/strong><\/p>\n

“<\/span>puppetclasses<\/span>“: null, <\/span><\/strong><\/p>\n

“<\/span>pxe_loader<\/span>“: null, <\/span><\/strong><\/p>\n

“realm”: null, <\/span><\/strong><\/p>\n

“<\/span>root_pass<\/span>“: null, <\/span><\/strong><\/p>\n

“<\/span>server_url<\/span>“: “http:\/\/foreman-1.<\/span>nictailor.com<\/span>\/”, <\/span><\/strong><\/p>\n

“state”: “present”, <\/span><\/strong><\/p>\n

“subnet”: null, <\/span><\/strong><\/p>\n

“subnet6”: null, <\/span><\/strong><\/p>\n

“username”: “<\/span>ntailor<\/span>“, <\/span><\/strong><\/p>\n

“<\/span>validate_certs<\/span>“: true<\/span><\/strong><\/p>\n

}<\/span><\/strong><\/p>\n

}, <\/span><\/strong><\/p>\n

“<\/span>msg<\/span>“: “The hostname must be FQDN”<\/span><\/strong><\/p>\n

}<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

PLAY RECAP ************************************************************************************************************************************************************************<\/span><\/strong><\/p>\n

testnick1 <\/span> :<\/span> ok=0 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 <\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

.<\/span><\/span><\/p>\n

\n
\n
5.<\/span>Okay so once you get all the variables. Its just a matter of playing around until you\u2019re able to get to work.<\/div>\n
\n
\n
c.<\/span>Mkdir a directory inside \/etc\/ansible\/roles<\/div>\n
\n
\n
i.<\/span>m<\/span>kdir<\/span> ansible-provision-foreman<\/span><\/em><\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
d.<\/span>Inside the directory create two directories (defaults & tasks)<\/span><\/div>\n
\n
\n
ii.<\/span>Mkdir<\/span> defaults && <\/span>mkdir<\/span> tasks<\/span><\/em><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

.<\/span><\/span><\/p>\n

\n
\n
6.<\/span>Now inside the <\/span>tasks<\/span> directory, create a file called <\/span>main.yml<\/span> and insert the code below<\/span><\/div>\n
\n
\n
e.<\/span>vi main.yml<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

Create a Host: This code is what you need for this module to work.<\/h2>\n

– name: “Create a host”<\/h2>\n

  theforeman.foreman.host:<\/h2>\n

username: “{{ foreman_user }}”<\/h2>\n

password: “{{ vcenter_password }}”<\/h2>\n

    server_url: “{{ server_url }}”<\/h2>\n

name: “{{ inventory_hostname }}”<\/h2>\n

    hostgroup: “{{ host_group }}”<\/h2>\n

managed: no<\/h2>\n

build: no<\/h2>\n

    compute_profile: “{{ compute_profile }}”<\/h2>\n

    compute_resource: “{{ computer_resource }}”<\/h2>\n

    compute_attributes:<\/h2>\n

      cpus: “{{ vm_cpu_count }}”<\/h2>\n

      memory_mb: “{{ vm_memory }}”<\/h2>\n

    interfaces_attributes:<\/h2>\n

– type: “interface”<\/h2>\n

primary: true<\/h2>\n

      compute_attributes:<\/h2>\n

name: nic1<\/h2>\n

network: “{{ vm_vlan_name }}”<\/h2>\n

interface: “{{ vm_interface }}”<\/h2>\n

subnet: “{{ vm_subnet }}”<\/h2>\n

        ip: “{{ vm_ip }}”<\/h2>\n

domain: “{{ domain }}”<\/h2>\n

provision: yes<\/h2>\n

    operatingsystem: “{{ operating_system }}”<\/h2>\n

medium: “{{ medium }}”<\/h2>\n

architecture: x86_64<\/h2>\n

    pxe_loader: PXELinux BIOS<\/h2>\n

    puppet_ca_proxy: “{{ puppet_ca_proxy }}”<\/h2>\n

    puppet_proxy: “{{ puppet_proxy }}”<\/h2>\n

    root_pass: “{{ root_pass }}”<\/h2>\n

environment: tdr<\/h2>\n

# ptable: Centos – LVM – \/ , swap<\/h2>\n

    ptable: “{{ ptable }}”<\/h2>\n

# owner: unix<\/h2>\n

state: present<\/h2>\n

    validate_certs: false<\/h2>\n

  delegate_to: localhost<\/h2>\n

– name: “Switch host on”<\/h2>\n

  theforeman.foreman.host_power:<\/h2>\n

username: “{{ foreman_user }}”<\/h2>\n

password: “{{ foreman_password }}”<\/h2>\n

    server_url: “{{ server_url  }}”<\/h2>\n

hostname: “{{ inventory_hostname }}”<\/h2>\n

state: on<\/h2>\n

    validate_certs: false<\/h2>\n

  delegate_to: localhost<\/h2>\n

.<\/span><\/span><\/p>\n

\n
\n
f.<\/span>save file.<\/div>\n<\/div>\n<\/div>\n

.<\/span><\/span><\/p>\n

\n
\n
7.<\/span>Okay so next want now want to pass the basic defaults for new host creating. How we do that is define what those are under defaults. These variables wont change<\/div>\n
\n
\n
g.<\/span>Cd<\/span> ..<\/span>\/defaults<\/span><\/em><\/div>\n<\/div>\n
\n
h.<\/span>Vi <\/span>main.yml<\/span><\/em><\/div>\n<\/div>\n<\/div>\n

Note: <\/span>You can find all these variables <\/span>inside foreman GUI with a bit of digging.<\/span><\/p>\n

foreman_user<\/span>: <\/span>Reptilianfilth<\/span><\/strong>
\nforeman_password<\/span>: <\/span>{ generally<\/span> want a ansible vault password }<\/span><\/strong>
\ncompute_profile<\/span>: <\/span>vmware<\/span><\/strong>
\ncomputer_resource<\/span>: <\/span>vcenter.<\/span>nic<\/span>.internal<\/span><\/strong>
\ndomain: <\/span>nic<\/span>.internal<\/span><\/strong>
\nmedium: 7.8-CentOS<\/span><\/strong>
\npuppet_ca_proxy<\/span>: puppet-2.<\/span>nic<\/span>.internal<\/span><\/strong>
\npuppet_proxy<\/span>: puppet-2.<\/span>nic.<\/span>internal<\/span><\/strong><\/p>\n

\n
\n
i.<\/span>Save file<\/span><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

.<\/span><\/span><\/p>\n

\n
\n
8.<\/span>Okay now we want to pass the host specific variables for new host creations and or <\/span>vm<\/span> deployments.<\/span><\/div>\n
\n
\n
j.<\/span>Move into to your \/etc\/ansible\/inventory\/{{environment}}\/<\/span>host_vars<\/span> directory<\/span><\/div>\n
\n
\n
iii.<\/span>CD <\/span>\/etc\/ansible\/inventory\/{{environment}}\/<\/span>host_vars<\/span><\/div>\n<\/div>\n
\n
iv.<\/span>Create a file called <\/span>testserver<\/span><\/div>\n<\/div>\n
\n
v.<\/span>Vi <\/span>testserver<\/span><\/div>\n<\/div>\n<\/div>\n

#VM creation variables<\/span><\/strong><\/p>\n

vm_network<\/span>: <\/span>nic<\/span>corp-<\/span>192<\/span>.1<\/span>68<\/span>.65_corp<\/span><\/strong><\/p>\n

vm_interface<\/span>: VMXNET3<\/span><\/strong><\/p>\n

vm_subnet<\/span>: 192.168.65.0<\/span><\/strong><\/p>\n

vm_ip<\/span>: 192.168.65.103<\/span><\/strong><\/p>\n

domain: <\/span>nic<\/span>.internal<\/span><\/strong><\/p>\n

managed: no<\/span><\/strong><\/p>\n

host_group<\/span>: Base-Server\/Centos-7.8.2003<\/span><\/strong><\/p>\n

operating_system<\/span>: Centos 7.8.2003<\/span><\/strong><\/p>\n

ptable<\/span>: Centos – LVM – <\/span>\/ ,<\/span> swap<\/span><\/strong><\/p>\n

root_pass<\/span>: <\/span>changeme<\/span>twiceaday<\/span><\/strong><\/p>\n

medium: 7.8-CentOS<\/span><\/strong><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

.<\/span><\/span><\/p>\n

\n
\n
k.<\/span>Past the above and save the file<\/span><\/div>\n<\/div>\n<\/div>\n

Special <\/span>Note: Now if you wanted to <\/span>have it so you can use <\/span>foreman module <\/span>or <\/span>vmware_guest<\/span> module combining the variables names between the modules. <\/span><\/strong><\/p>\n

You can do <\/span>as below. You will need to ensure the variables match but it works. You can get around having to <\/span>rely on<\/span> DHCP with this<\/span>.<\/span><\/strong><\/p>\n

#VM creation variables foreman and <\/span>v<\/span>mware<\/span> together<\/span><\/strong><\/p>\n

vm_vlan_name<\/span>: <\/span>nic<\/span>_<\/span>192<\/span>.<\/span>168<\/span>.44_db_stor2<\/span><\/strong><\/p>\n

vm_datastore<\/span>: <\/span>esx_<\/span>nic<\/span>rc<\/span>orp<\/span><\/strong><\/p>\n

vm_dvswitch<\/span>: VDS-<\/span>nic<\/span>-Corporate<\/span><\/strong><\/p>\n

vm_interface<\/span>: VMXNET3<\/span><\/strong><\/p>\n

vm_subnet<\/span>: <\/span>192<\/span>.1<\/span>268<\/span>.44.0<\/span><\/strong><\/p>\n

vm_ip<\/span>: <\/span>192<\/span>.1<\/span>68<\/span>.44.14<\/span><\/strong><\/p>\n

vm_netmask<\/span>: 255.255.255.0<\/span><\/strong><\/p>\n

vm_gateway<\/span>: <\/span>192<\/span>.<\/span>168<\/span>.<\/span>44<\/span>.254<\/span><\/strong><\/p>\n

vm_dns_servers<\/span>: [<\/span>192<\/span>.<\/span>168<\/span>.<\/span>1<\/span>.<\/span>1<\/span>]<\/span><\/strong><\/p>\n

vm_dns_suffix<\/span>: <\/span>nic<\/span>.internal<\/span><\/strong><\/p>\n

vm_cpu_count<\/span>: 4<\/span><\/strong><\/p>\n

vm_memory<\/span>: 16384<\/span><\/strong><\/p>\n

vm_state<\/span>: <\/span>poweredon<\/span><\/strong><\/p>\n

vm_connected<\/span>: true<\/span><\/strong><\/p>\n

domain: <\/span>tdr.internal<\/span><\/strong><\/p>\n

managed: no<\/span><\/strong><\/p>\n

host_group<\/span>: Base-Server\/Centos-7.8.2003<\/span><\/strong><\/p>\n

operating_system<\/span>: Centos 7.8.2003<\/span><\/strong><\/p>\n

ptable<\/span>: Centos – LVM – <\/span>\/ ,<\/span> swap<\/span><\/strong><\/p>\n

root_pass<\/span>: <\/span>changeme<\/span>twiceaday<\/span><\/strong><\/p>\n

medium: 7.8-CentOS<\/span><\/strong><\/p>\n

\n
\n
9.<\/span>Next you need to ensure your host are listed in your inventory host file<\/span><\/div>\n
\n
\n
l.<\/span>vi<\/span> ..<\/span>\/hosts<\/span><\/em><\/div>\n<\/div>\n
\n
m.<\/span>testnick3.<\/span>nic<\/span>.internal<\/span><\/em><\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
10.<\/span>save file<\/span><\/div>\n<\/div>\n<\/div>\n

.<\/span><\/span><\/p>\n

Before you to start one last thing. If you remember in the defaults we outlined <\/span><\/p>\n

compute_profile<\/span>: <\/span>vmware<\/span><\/strong>
\n (this is the foreman profile it will use, so whatever defaults you have set for network and <\/span>disksize<\/span> here is what will be used to trigger foreman to create a host in <\/span>vcenter<\/span>, so it good to go check this in foreman first.)<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

.<\/span><\/span>Run playbook: from \/etc\/ansible<\/span><\/p>\n

[<\/span>root@nick<\/span> ansible]#<\/span> ansible-playbook –<\/span>i<\/span> inventory\/TDR\/hosts <\/span>foremancreatehost.yml<\/span> –ask-vault-pass –limit ‘testnick3.<\/span>tdr<\/span>.internal’<\/span><\/strong><\/p>\n

Vault password: <\/span><\/strong><\/p>\n

.<\/span><\/span><\/strong><\/p>\n

PLAY [all] **********************************************************************************************************************************************<\/span><\/strong><\/p>\n

.<\/span><\/span><\/strong><\/p>\n

TASK [ansible-provision-<\/span>foreman :<\/span> Create a host] ********************************************************************************************************<\/span><\/strong><\/p>\n

changed: [testnick3.tdr.internal]<\/span><\/strong><\/p>\n

.<\/span><\/span><\/strong><\/p>\n

PLAY RECAP *******************************************************************************************************************************************************************************<\/span><\/strong><\/p>\n

testnick3.tdr.internal <\/span> :<\/span> ok=1 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 <\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

403 Client Error: Forbidden for url: http:\/\/foreman-1.nic.corp.com\/api\/v2\/reports (<\/span>if you see this, just ignore it<\/span><\/span>) Its just callback report.<\/span><\/strong><\/p>\n

.<\/span><\/span><\/p>\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

Okay\u2026this one was quite difficult to find online. Seems like the ansible documentation for the foreman module was seriously lacking or not kept up to date by anyone. I searched for awhile to see if anyone had an actual working model of it. Not even in the ansible chat rooms did anyone know….which was weak. So I spent some timeRead More …<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":true,"template":"","format":"standard","meta":{"footnotes":""},"categories":[51,26],"tags":[],"class_list":["post-1281","post","type-post","status-publish","format-standard","hentry","category-ansible","category-red-hat-satellite"],"_links":{"self":[{"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/posts\/1281","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/comments?post=1281"}],"version-history":[{"count":13,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/posts\/1281\/revisions"}],"predecessor-version":[{"id":1582,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/posts\/1281\/revisions\/1582"}],"wp:attachment":[{"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/media?parent=1281"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/categories?post=1281"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/tags?post=1281"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}