-
Notifications
You must be signed in to change notification settings - Fork 899
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
Child service link does not work on parent service details page #23060
Comments
@jeffbonson Can you please take a look at this one. |
hey @eggoide , if possible, could you please give us the steps on how to replicate this issue in petrosian so that it makes it easier for us to debugg. a few scrrenshots or a screen recording would do. |
Findings - I checked out I didn't have a child service configured in my local env. Probably thats why it went unnoticed during the conversion process. Earlier, this was an explorer page, and the click event is supposed to be loading the right hand side of the explorer page. However, @eggoide , if you still have the steps on how to do it, please do share it over here. |
@jeffbonson Thank you for the fix. Will the commit be also included in the Petrosian docker image - possible rebuild? |
cc @Fryguy |
@jeffbonson Hi, I checked the fix however, I dont think it works. Correct me please if I am doing something wrong. After restart of ManageIQ , the child link does nothing, no activity in debug console. |
Hey @eggoide , thats weird. I can see you have applied the changes and the new react component is being rendered. Here is what is see in my local env I am clicking on the the child row and it redirects me to a new service summary page Screen.Recording.2024-06-14.at.4.42.44.PM.mov |
@jeffbonson I tried it on two different environments. One clean just to test the fix and one that servers as our main environment. Both behave the same. If I can test anything else for you, I will do it. |
Found the issue. A lot of code refactoring happend after could you try changing this line below in the
|
@jeffbonson This modification works! Thank you |
|
@eggoide Unfortunately the Petrosian branch is no longer supported and we do not release any updates for it so the Petrosian pr can not be merged. If you want this fix it would have to be done locally |
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 |
Hello,
we are experiencing the following problem after upgrading from Najdorf to petrosian-1.20230912222549_a07cb46
If there is a service, that has its child service, the link to the child service does not work. On the parent service detail page, if you click on the child service to see the details, the link is just wrong.
The example link to the child service looks like this:
https://<miq_instance>/service/tree_select/?id=s-50115
(here is the log from apache access log file: 10.92.245.92 - - [07/Jun/2024:08:30:00 +0200] "GET /service/tree_select/?id=s-50115 HTTP/1.1" 404 728 )
The standard link to the child service works fine - https://<miq_instance>/service/show/50115#/
Is this a known bug or is there any workaround? Thank you
The environment is petrosian-1.20230912222549_a07cb46 running in Docker container connected to PostreSQL DB.
The text was updated successfully, but these errors were encountered: