-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
storage_pod can not be set #1247
Comments
Can you post the output of |
After creating the profile:
I tried with group-p666 as a storage pod name, but I got the same results. |
Thanks! Another request (sorry!) Can you select the right pod in the UI, save it, and then again run the playbook with Background: the output you posted implies the API did accept the pod, but if the UI disagrees, we might be using a wrong identifier or something? |
I think, the problem is, the plugin uses the pod id "group-p666" by creating or checking the pod parameter, that does not match with katello API, I think katello wants the pod name not the pod id, does it? Have a look please at the network name and compare it with the pod, the plugin uses the network id dvportgroup-257 by creating and checking which suits katello API. |
Interesting, thanks! |
Out of curiosity, did you try deploying a host with the "broken" (the one using the id, not name) compute profile? I have a feeling this should work and the UI is just displaying it wrongly, but don't have a VMware to test on :( |
Your feeling is right :) I used the name as pod name
The UI does not display the pod under the profile, but while creating a virtual machine, I can see the pod under the vm configurations. In addition, the creating of new vm works. |
"nice" We'll try get access to an VMware to test this and other parameters properly and issue a fix afterwards. cc @ezr-ondrej for "how broken is this intergration?!" |
I've experienced the same problem with FAM 2.2.0. I can assist in debugging FAM (and Foreman) if you need someone with access to VMware. |
Hello, |
same here, changing storage_pod['id'] to storage_pod['name'] did the trick. I've tested with collection 3.8 and foreman-3.4.1-1 |
Hello, I'm facing the same issue. I've a fresh installation of RH Satellite 6.14.0 (i.e. foreman-3.7.0.9-1.el8sat.noarch) and collection 3.10.0. There is any fix for this situation? |
I've tried the fix suggested by @s-reimann and implemented a pull request #1686. |
SUMMARY
I am using compute_profile plugin to create configuration on katello. However, this plugin let the storage_pod parameter empty after problem free Ansible run
ISSUE TYPE
ANSIBLE VERSION
COLLECTION VERSION
KATELLO/FOREMAN VERSION
STEPS TO REPRODUCE
EXPECTED RESULTS
Set the storage-pod parameter in my Small compute profile
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: