How to check where are the bugs when the execution status is error

Bug #1643840 reported by jzx
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mistral
Invalid
Undecided
Unassigned

Bug Description

I want to execute a workflow,the workflow definition as follows:

---

version: '2.1.1'

send_tenant_stat:
 type: direct

 input:
  - to_email
  - from_email
  - smtp_server
  - smtp_password

 output:
  vm_count: $.vm_count
  active_vm_count: $.active_vm_count
  net_count: $.net_count

 tasks:
  get_vm_count:
   action: nova.servers_list
   publish:
    vm_count: $.length()
    active_vm_count: $[$.status = 'ACTIVE'].length()
   on-complete:
    - get_net_count
  get_net_count:
   action: neutron.list_networks
   publish:
    net_count: $.length()
   on-complete:
    - send_stat
  send_stat:
   action: std.email
   input:
    params:
     to: [$.to_email]
     suject: Tenant Statistics
     body: |
      Statistics for tenant '{$.openstack.project_name}'
      Number of VMs: {$.vm_count}
      Number of active VMs: {$.active_vm_count}
      Number of networks: {$.net_count}

    settings:
     from: $.from_email
     smtp_server: $.smtp_server
     password: $.smtp_password

and,my input is:
 {"to_email":"<email address hidden>","from_email":"<email address hidden>","smtp_server":"smtp.gmail.com","smtp_password":"my email's password"},and store it in Tenant_Statistics.json

then,I run the following command to execute the workflow:
mistral execute-create XXX(workflow's name) Tenant_Statistics.json

but the status is error ,and the output is None.

Revision history for this message
Vijendra Soni (vijendra-soni) wrote :

Try checking in /var/log/mistral/ <-- Check actual log dir in conf file. That should give info on error.

Revision history for this message
jzx (xuange) wrote :

Vijendra,

Thank you. But in my dir : /var/log/,I don't have 'mistral' directory.

Revision history for this message
Renat Akhmerov (rakhmerov) wrote :

Why did you specify version "2.1.1"?

On your question: we are now working on several ideas that will help debug workflow executions. One of the blueprints is https://blueprints.launchpad.net/mistral/+spec/mistral-debug. Stay tuned.

Revision history for this message
Renat Akhmerov (rakhmerov) wrote :

One more note: analyzing logs is not what a user should do to analyze problems, all required info should be accessible through API. Currently, you can do "mistral task-list <workflow execution id>" and see what tasks are in ERROR and 'state_info' of those tasks should contain information about the error.

Revision history for this message
Dougal Matthews (d0ugal) wrote :

Closing this bug as there is work happening here to improve this problem. https://blueprints.launchpad.net/mistral/+spec/mistral-error-analysis

Changed in mistral:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.