You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/11/23 00:51:21 UTC

[GitHub] [airflow] dimberman commented on issue #12264: Better Statuses Kubernetes Executor

dimberman commented on issue #12264:
URL: https://github.com/apache/airflow/issues/12264#issuecomment-731879113


   So when I look at the events that are generated on an unschedule-able pod I see that the failure here is actually reported during the "ADDED" phase. So I THINK we can add a check there and that might help with some of these use-cases. I'm not sure about all though...
   
   ```
   >>> e
   {'type': 'ADDED', 'object': {'api_version': 'v1',
    'kind': 'Pod',
   ...
    'status': {'conditions': [{'last_probe_time': None,
                               'last_transition_time': datetime.datetime(2020, 11, 23, 0, 47, 12, tzinfo=tzutc()),
                               'message': 'persistentvolumeclaim "test-volume" '
                                          'not found',
                               'reason': 'Unschedulable',
                               'status': 'False',
                               'type': 'PodScheduled'}],
               'container_statuses': None,
               'host_ip': None,
               'init_container_statuses': None,
               'message': None,
               'nominated_node_name': None,
               'phase': 'Pending',
               'pod_ip': None,
               'qos_class': 'BestEffort',
               'reason': None,
               'start_time': None}},
   ```


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org