Created attachment 1513911 [details] Demo Description of problem: Version-Release number of selected component (if applicable): Version 5.10.0.29.20181211195209_fd990a9 How reproducible: 100% Steps to Reproduce: 1.Create a Service catalog item and add Reconfigure Entry Point. 2.Order the service 3.Go to My Services 4.Go to created My Services details page Actual results: Provisioned Services doesn't show the date in service name and in service title when we select Reconfigure Entry Point. Expected results: It should show the Date. Additional info:
Niyaz, Please share your appliance setup on which this issue is reproducible.
@Niyaz this should be listed as UI - Ops
The service naming is applied from the CatalogItemInitialize entry-point if the service name is not being overridden from the dialog. See https://github.com/ManageIQ/manageiq-content/blob/master/content/automate/ManageIQ/Service/Provisioning/StateMachines/Methods.class/__methods__/catalogiteminitialization.rb#L43 Can you confirm that: 1) You are using CatalogIteminItialization as the create entry-point 2) You are not overriding the Service name from the dialog
@Greg, answers to your questions, 1.I am using following entry points Provisioning Entry Point - /Service/Provisioning/StateMachines/ServiceProvision_Template/CatalogItemInitialization Reconfigure Entry Point - /System/Event/StateMachines/Refresh/default (this is diff) Retirement Entry Point - /Service/Retirement/StateMachines/ServiceRetirement/Default 2. Not overriding name from service dialog but the problem is, I am not able to differentiate between active services since all names are same
Hi Niyaz, Service reconfigure is only available for Cloud Orchestration. The reconfigure entry point would be: /Cloud/Orchestration/Reconfiguration/StateMachines/Reconfigure/Default. The reconfigure entrypoint specified is not a valid entry point: /System/Event/StateMachines/Refresh/default (this is diff) I don't believe this is an issue. Can we close this ticket? Let me know if you have any questions. Thanks, Tina
Created attachment 1515083 [details] with cloud provider I tried with correct entry points as you mentioned in above comments with azure provider. I am still seeing the issue. -> /Cloud/Orchestration/Reconfiguration/StateMachines/Reconfigure/Default.
Do you have a reproducer ? I looked at appliance in Comment3 and it doesn't match the screenshot. Please advise
Hi Niyaz, Service reconfigure is only available for Cloud Orchestration stacks. You will need to provision a service from an orchestration template. That template needs to be reconfigurable and then try to run the service reconfiguration. Please disable your OpenStack domain when testing this. Thanks Billy
Created attachment 1515911 [details] Service Reconfiguration with date
Niyaz, I tried to reconfigure the service and its showing the date now. I included the screenshot. Can you try now and verify its working now? Thanks Billy
Yes I can see the date on service details page.I have mentioned in comment12. But there is another issue when you navigate Configuration->Reconfigure this service page the date is not present with service name.
Can you provide screenshots showing the service detail page and the service page showing the difference in naming?
In comment #13 I have uploaded the image. you can see the date is not present with service name
Transferring to UI - OPS
Tina talked to Dan about this issue and they decided to transfer this ticket to UI
Hi Harpreet, Yes, the code should use the 'Service' name for the right cell header, instead of the 'Service Template' name. Let me know if you have any questions. Thanks, Tina
https://github.com/ManageIQ/manageiq-ui-classic/pull/5124
The issue is still present in Version 5.10.4.2.20190508174256_282f74e Hence failing this BZ.
Niyaz, this is fixed only in 5.11, not in 5.10.z. Can you retest with 5.11.0.1 or later build?
Thanks Satoe for correcting me. I will test in 5.11
Now date is present in service name for reconfigure services Verified in Version 5.11.0.8.20190611155126_01e077e
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:4199