-
Bug
-
Resolution: Done-Errata
-
Normal
-
6.14.1
-
0
-
False
-
-
False
-
VERIFIED
-
900
-
Platform
-
-
-
Moderate
-
No
Description of problem:
The compute profile created through Satellite Ansible collection will set the storage pod to its id instead of name. This is causing Web UI showing empty storage pod and the image base host provisioning to fail with Storage pod doesn't exist error.
~~~
error (Foreman::WrappedException): ERF50-1679 [Foreman::WrappedException]: Satellite could not find a required vSphere resource. Check if Satellite has the required permissions and the resource exists. Reason: Storage Pod group-XXXXX Doesn't Exist! ([Fog::Vsphere::Compute::NotFound]: Storage Pod group-XXXXX Doesn't Exist!)
~~~
How reproducible:
Always
Additional info:
This is a known issue and has been fixed upstream:
Upstream issue:
https://github.com/theforeman/foreman-ansible-modules/issues/1247
Upstream PR:
https://github.com/theforeman/foreman-ansible-modules/pull/1686
- external trackers
- links to
-
RHBA-2024:140284 Important: Satellite 6.16.0 release