Successfull installation - Plugin not present

Problem:

I already succeeded to install thoses plugins :

foreman-installer --enable-foreman-plugin-ansible --enable-foreman-proxy-plugin-ansible --enable-foreman-cli-ansible

I see them into the API into the plugin tab “about”, they are working

When i try to add the vmware module, i have no error, but i cannot see it into my API

foreman-installer --enable-foreman-plugin-ansible --enable-foreman-proxy-plugin-ansible --enable-foreman-cli-ansible --enable-foreman-compute-vmware 2024-03-22 08:47:25 [NOTICE] [root] Loading installer configuration. This will take some time.
2024-03-22 08:47:27 [NOTICE] [root] Running installer with log based terminal output at level NOTICE.
2024-03-22 08:47:27 [NOTICE] [root] Use -l to set the terminal output log level to ERROR, WARN, NOTICE, INFO, or DEBUG. See --full-help for definitions.
2024-03-22 08:47:32 [NOTICE] [configure] Starting system configuration.
2024-03-22 08:47:42 [NOTICE] [configure] 250 configuration steps out of 1366 steps complete.
2024-03-22 08:47:42 [NOTICE] [configure] 500 configuration steps out of 1368 steps complete.
2024-03-22 08:47:43 [NOTICE] [configure] 750 configuration steps out of 1375 steps complete.
2024-03-22 08:47:43 [NOTICE] [configure] 1000 configuration steps out of 1375 steps complete.
2024-03-22 08:47:43 [NOTICE] [configure] 1250 configuration steps out of 1375 steps complete.
2024-03-22 08:48:01 [NOTICE] [configure] System configuration has finished.
Executing: foreman-rake upgrade:run
Success!

Any idea ? am i missing something ?

Distribution and version:

Version 3.9.1
Red Hat Enterprise Linux release 8.9 (Ootpa)

Compute Resource providers like vmware are technically not plugins to Foreman, so you won’t find that feature in the plugin API.
Why is it you need to check via the API if it is there if the installer succeeded? If you just generically want to know if it is installed, easiest would be to check the installed packages for foreman-vmware or rubygem-fog-vsphere.

Thanks for your comment, i was looking into the API because of this documentation :
https://theforeman.org/2020/12/how-to-start-with-foreman.html
with the topic “Importing VMs from compute resource”

Navigate to Infrastructure → Compute resources and click Create Compute Resource button. Give it some name and select a provider type. If you don’t see any provider, you need to install some. While some providers are part of Foreman core, we ship them in separate RPM packages, so users can install only those, that are interesting in their environment. In order to see, what providers you have installed, navigate to Administer → About → Available Providers .

I wanted to connect my vmware server to Foreman, is it not the way to do ?

While that article is a bit dated (over 3 years by now), the section you quoted should generally still be correct, though I currently do not have a recent Foreman instance at hand to check for myself.
Are you able to create a VMWare compute resource?
You might want to take a look at the current docs for some more help.
While the new docs at docs.theforeman.org currently are mainly aimed at Katello, the section about VMWare integration is generic enough to also be applicable to plain Foreman as well.

Thanks for your answer, actually i cannot creation compute resource because i have nothing available to select into “Provider” field

here’s one grep of vmware into the log :

grep -i vmware /var/log/foreman-installer/foreman.log

2024-03-25 09:28:29 [DEBUG ] [root] checking presence of /usr/share/foreman-installer/modules/foreman/manifests/compute/vmware/params.pp
2024-03-25 09:28:32 [DEBUG ] [root] Running installer with args [[“–enable-foreman-compute-vmware”]]
2024-03-25 09:28:37 [DEBUG ] [configure] Facter: Detected product name: VMware7,1
2024-03-25 09:28:37 [DEBUG ] [configure] Facter: Detected hypervisor vmware
2024-03-25 09:28:37 [DEBUG ] [configure] Facter: Detected product name: VMware7,1
2024-03-25 09:28:37 [DEBUG ] [configure] Facter: Detected bios vendor: VMware, Inc.
2024-03-25 09:28:37 [DEBUG ] [configure] Facter: Vmware hypervisor detected
2024-03-25 09:28:38 [DEBUG ] [configure] Facter: Fact value is: vmware
2024-03-25 09:28:38 [DEBUG ] [configure] Facter: fact “dmi.manufacturer” has resolved to: VMware, Inc.
2024-03-25 09:28:38 [DEBUG ] [configure] Facter: fact “manufacturer” has resolved to: VMware, Inc.
2024-03-25 09:28:38 [DEBUG ] [configure] Facter: fact “dmi.bios.vendor” has resolved to: VMware, Inc.
2024-03-25 09:28:38 [DEBUG ] [configure] Facter: fact “bios_vendor” has resolved to: VMware, Inc.
2024-03-25 09:28:38 [DEBUG ] [configure] Facter: fact “dmi.product.name” has resolved to: VMware7,1
2024-03-25 09:28:38 [DEBUG ] [configure] Facter: fact “productname” has resolved to: VMware7,1
2024-03-25 09:28:38 [DEBUG ] [configure] Facter: fact “dmi.product.serial_number” has resolved to: VMware-42 28 40 c4 cc 3f 6b de-93 a8 fb ae 81 2d 6e 55
2024-03-25 09:28:38 [DEBUG ] [configure] Facter: fact “serialnumber” has resolved to: VMware-42 28 40 c4 cc 3f 6b de-93 a8 fb ae 81 2d 6e 55
2024-03-25 09:28:38 [DEBUG ] [configure] Facter: fact “disks” has resolved to: {“sr0”=>{“model”=>“VMware SATA CD00”, “size_bytes”=>1073741312, “size”=>“1.00 GiB”, “vendor”=>“NECVMWar”, “type”=>“hdd”, “serial”=>“00000000000000000001”}, “sda”=>{“model”=>“Virtual disk”, “size_bytes”=>107374182400, “size”=>“100.00 GiB”, “vendor”=>“VMware”, “type”=>“ssd”}}
2024-03-25 09:28:38 [DEBUG ] [configure] Facter: fact “blockdevice_sr0_model” has resolved to: VMware SATA CD00
2024-03-25 09:28:38 [DEBUG ] [configure] Facter: fact “blockdevice_sda_vendor” has resolved to: VMware
2024-03-25 09:28:38 [DEBUG ] [configure] Facter: fact “hypervisors.vmware” has resolved to: {}
2024-03-25 09:28:38 [DEBUG ] [configure] Facter: fact “virtual” has resolved to: vmware
2024-03-25 09:28:38 [DEBUG ] [configure] “foreman::compute::vmware”,
2024-03-25 09:28:38 [DEBUG ] [configure] “foreman::compute::vmware”,
2024-03-25 09:28:38 [DEBUG ] [configure] importing ‘/usr/share/foreman-installer/modules/foreman/manifests/compute/vmware.pp’ in environment production
2024-03-25 09:28:38 [DEBUG ] [configure] Automatically imported foreman::compute::vmware from foreman/compute/vmware into production
2024-03-25 09:28:39 [DEBUG ] [configure] Automatic Parameter Lookup of ‘foreman::compute::vmware::version’
2024-03-25 09:28:39 [DEBUG ] [configure] Searching for “foreman::compute::vmware::version”
2024-03-25 09:28:39 [DEBUG ] [configure] No such key: “foreman::compute::vmware::version”
2024-03-25 09:28:39 [DEBUG ] [configure] Found key: “foreman::compute::vmware::version” value: “installed”
2024-03-25 09:28:40 [DEBUG ] [configure] Adding relationship from Class[Foreman::Install] to Package[foreman-vmware] with ‘notify’
2024-03-25 09:28:40 [DEBUG ] [configure] Adding relationship from Package[foreman-vmware] to Class[Foreman::Service] with ‘notify’
2024-03-25 09:28:40 [DEBUG ] [configure] /Package[foreman-vmware]: Provider dnf does not support features targetable; not managing attribute command
2024-03-25 09:28:41 [DEBUG ] [configure] /Stage[main]/Foreman::Install/notify: notify to Package[foreman-vmware]
2024-03-25 09:28:41 [DEBUG ] [configure] /Stage[main]/Foreman::Compute::Vmware/Package[foreman-vmware]/notify: notify to Class[Foreman::Service]
2024-03-25 09:28:41 [DEBUG ] [configure] Class[Foreman::Compute::Vmware]: Starting to evaluate the resource (81 of 1366)
2024-03-25 09:28:41 [DEBUG ] [configure] Class[Foreman::Compute::Vmware]: Evaluated in 0.00 seconds
2024-03-25 09:28:46 [DEBUG ] [configure] /Package[foreman-vmware]: Starting to evaluate the resource (311 of 1366)
2024-03-25 09:28:46 [DEBUG ] [configure] /Package[foreman-vmware]: Evaluated in 0.00 seconds
2024-03-25 09:28:46 [DEBUG ] [configure] Class[Foreman::Compute::Vmware]: Starting to evaluate the resource (312 of 1366)
2024-03-25 09:28:46 [DEBUG ] [configure] Class[Foreman::Compute::Vmware]: Evaluated in 0.00 seconds

I find the solution →

yum install foreman-ovirt

after restarting the service i was available to see “vmware” into the compute resource

Huh, interesting, still don’t understand why foreman-ovirt affects the VMware.