Problem: API calls to foreman for provisioning fail with ERF42-2471 code. This might be related to
Bug #33990: Foreman shouldn't reject valid volume attributes with "VM volume attributes are not set properly" - Foreman from my understanding a string vs integer diff in the api vs internal foreman code?
Provisioning internally i.e. foreman UI with a compute profile works, only api call for the Volume fails.
Expected outcome:
To be able to provision via API using a Compute Profiles
which also sets the Disk size.
Foreman and Proxy versions:
foreman-3.8.0-1.el8.noarch
foreman-proxy-3.8.0-1.el8.noarch
Foreman and Proxy plugin versions:
foreman-dynflow-sidekiq-3.8.0-1.el8.noarch
rubygem-foreman-tasks-8.3.3-1.fm3_8.el8.noarch
foreman-3.8.0-1.el8.noarch
foreman-service-3.8.0-1.el8.noarch
rubygem-foreman_maintain-1.3.5-1.el8.noarch
foreman-debug-3.8.0-1.el8.noarch
foreman-installer-3.8.0-2.el8.noarch
foreman-installer-katello-3.8.0-2.el8.noarch
rubygem-hammer_cli_foreman-3.8.0-1.el8.noarch
rubygem-hammer_cli_foreman_remote_execution-0.2.3-1.fm3_7.el8.noarch
rubygem-foreman_puppet-6.2.0-1.fm3_8.el8.noarch
foreman-ovirt-3.8.0-1.el8.noarch
foreman-vmware-3.8.0-1.el8.noarch
foreman-release-3.8.0-1.el8.noarch
foreman-selinux-3.8.0-1.el8.noarch
foreman-cli-3.8.0-1.el8.noarch
rubygem-foreman_remote_execution-11.1.1-1.fm3_8.el8.noarch
foreman-postgresql-3.8.0-1.el8.noarch
rubygem-hammer_cli_foreman_tasks-0.0.19-1.fm3_7.el8.noarch
foreman-proxy-3.8.0-1.el8.noarch
rubygem-hammer_cli_foreman_puppet-0.0.6-1.fm3_4.el8.noarch
Distribution and version:
Red Hat Enterprise Linux release 8.9 (Ootpa)
Other relevant data: