-
Notifications
You must be signed in to change notification settings - Fork 92
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
Validation failed: ManageIQ::providers::openstack::cloudmanager::template cannot be a descendant of itself. #862
Comments
That is an interesting one @SanthoshRam-03 , what version is this and did it start happening e.g. after an upgrade or just randomly? |
Hi @agrare Thanks for quick response, We are using Petrosian-1 version. When we connect with default domain it works as expected. When we try to connect with different domain (other than the default openstack domain) it's not working as expected and gives us errors. |
Hi @agrare , Is there any update on the same. We are facing the same issue in our manageiq environment too |
@remo233 is it also failing for you in non-default domains? Did this start happening on an upgrade to a specific version? |
Hi @agrare , Yes, its failing for non-default domains. Also its happening in najdrof, oparin and petrosian. I think it is happening in particular snapshots. So, can we please provide me the commands or steps to check the exact errored template from manageiq. |
Okay I'm surprised we haven't seen this before if it is failing all the way back in najdorf. Okay let me create another domain in my local openstack environment and see if I can reproduce it. |
Hi @agrare any update for this above issue? |
Hi | @agrare , any update on this ? |
Hi @remo233 FILE PATH: manageiq/providers/inventory/persister/builder/cloud_manager.rb In the above file, I commented out the particular lines in the source code, and it worked. def vm_and_miq_template_ancestry_save_block
If the "vm_and_miq_template_ancestry_save_block" references the non-existent genealogy_parent column and you've ensured that this column is not required for the refresh functionality to work, then these changes should not negatively affect the refresh process. Hi @agrare Is this correct? |
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on |
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on |
1 similar comment
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on |
Hi @Fryguy @agrare
I am facing this issue when we connecting with provider openstack it is showing the validation failed error.
I shared the screenshot below,
evm.log
Can you suggest me any solution for this issue.
The text was updated successfully, but these errors were encountered: