Hide Forgot
Description of problem: Automate service objects do not list all VMs associated with the service. Version-Release number of selected component (if applicable): CFME 5.6.0.13.20160624114606_13a9153 CF 4.1 How reproducible: 1. Create a catalog bundle consisting of several catalog items, each of which provisions a VM/ instance 2. Request the service, and wait for the VMs to provision 3. Record the name of the service 4. Start the interactive ruby shell on the Cloudforms appliance (See "Rails console" - https://pemcg.gitbooks.io/introduction-to-cloudforms-automation/content/chapter9/investigative_debugging.html) 5. Get a handle to the service (service = $evm.vmdb(:service).find_by_name("service-name") 6. List out the number of VMs for the service (service.v_total_vms) 7. List out the VMs for the service (service.vms) Actual results: The number and description of VMs reported from IRB different to that reported in the UI Expected results: The number and description of VMs reported from IRB is the same as that reported in the UI Additional info: This has yet to be tested on CFME 5.6.1
Shane - Please provide an example of the counts you getting back so we can validate that our results match yours. For example, is v_total_vms returning more or less then the number of VMs returned from service.vms?
I'll take the QE on this to start but may reassign.
I promised Shane I would follow up, but I need your help Shveta. Let me know if you can reproduce it or send it back to me. Thanks.
I recreated the use case . I don't see any bug . I have a service named "bundle" which has 5 catalog items and hence 5 Vm's were provisioned. (service.v_total_vms) PostgreSQLAdapter#log_after_checkout, connection_pool: size: 5, connections: 1, in use: 1, waiting_in_queue: 0 PostgreSQLAdapter#log_after_checkin, connection_pool: size: 5, connections: 1, in use: 0, waiting_in_queue: 0 PostgreSQLAdapter#log_after_checkout, connection_pool: size: 5, connections: 1, in use: 1, waiting_in_queue: 0 PostgreSQLAdapter#log_after_checkin, connection_pool: size: 5, connections: 1, in use: 0, waiting_in_queue: 0 => 5 Rails Console shell command also returned 5 VM's. Please let me know if there was some other issue .
Hi Shveta, Thanks very much for your assistance. I've tried to replicate this issue multiple times at the site today, unfortunately without success. I suspect I introduced this in a post-provision automation, and if I can reproduce the behaviour I'll update you. Greg, Thanks for following up on this. I was seeing the number of VMs reported less than the UI. I have the original service which still shows this behaviour; v_total_vms reports 1, and 3 are shown in the UI, however, I'm unable to replicate it.