Closed fgoebel closed 4 years ago
This looks like an issue with your installation and not with the Ansible modules. I would expect you can't create a compute resource in the WebUI either.
I just ran this playbook again today and it just works again. So yes I think you are right this i more a problem with my installation.
Thank you for your feedback and providing these modules!
SUMMARY
After an update of Foreman-apt-packages, the module compute_resource leads to Foreman internal server error, see verbose output below. This is the second time that I have these Issues after an update.
At the first time i just added another new compute-resource with the same settings but different name, migrated the tied virtual machines to the new one, deleted the old and renamed the compute-resource. As i do not want to go through this step every time I update some foreman-packages i want to check what is going on here
Foreman is installed on Ubuntu 18.04 with provided apt packages. To better understand how Foreman works we installed Foreman "on our own" with ansible and we did not use the foreman-installer.
I am not sure if this is even a problem with the ansible-module at the first place, but this is where I start... If you have some comments or ideas what this is causing and what i can do about it i would be quite happy!
What is striking to me is the line
"message": "uninitialized constant Fog::Vsphere::Compute::ResourcePool"
in the verbose output below, but i have not that much knowledge in ruby that i know what i should do about it.Thank you very much for the foreman-ansible-modules as i really use them a lot and the work quite well. I have completely automated our foreman-setup and configuration with ansible with only compute-profiles and host-groups left to do.
My Background is mainly sys-admin stuff and I have not done that much development in my life..
I have redacted some information, so maybe some org-names may not match..
ISSUE TYPE
ANSIBLE VERSION
KATELLO/FOREMAN VERSION
katello is not installed
APYPIE VERSION
STEPS TO REPRODUCE
I am not quite sure what caused this issue, so it is difficult to tell the steps to reproduce this. Instead i will show what I have done before this happend.
I updated the apt packages for foreman from 2.1.2 to 2.1.3 with apt upgrade and ran the commands mentioned in the manual at Point 3 A like this:
Snipped from playbook with regarding task:
Playbook example:
excerpt from ansible-role-foreman-config tasks.yml
snipped from defaults/main.yml from the role
EXPECTED RESULTS
Module runs successfully with "changed"
ACTUAL RESULTS