Aptomi / k8s-app-engine

Application delivery engine for k8s
Apache License 2.0
163 stars 19 forks source link

Client doesn't print understandable error message when creating components which are being deleted #286

Closed romangithub1024 closed 6 years ago

romangithub1024 commented 6 years ago
  1. Deploy example

  2. Delete namespaces

  3. Apply example again:

    Gen 5 -> 6      [+] cluster-us-east#platform#analytics_pipeline#platform
                     -> hdfs, kafka, spark
                [+] cluster-us-east#platform#hdfs#platform
                     -> hdfs
                [+] cluster-us-east#platform#kafka#platform
                     -> kafka, zookeeper
                [+] cluster-us-east#platform#spark#platform
                     -> spark, zookeeper
                [+] cluster-us-east#platform#zookeeper#platform
                     -> zookeeper
                [+] cluster-us-east#social#twitter_stats#realtime
                     -> analytics_pipeline, tweepub, tweetics, tweeviz
    Waiting for changes to be applied....
    [Applying changes]
    [59/59] [====================================================================] 100%   Time: 19s
    Error! Revision 5 failed with an error and has not been fully applied
    FATA[0019] error
  4. Client exits with empty error message

  5. Server log has:

    ERRO[0076] (enforce-5-apply) error while applying action 'action-component-create/cluster-us-east#platform#zookeeper#platform#zookeeper': unable to deploy component instance 'cluster-us-east#platform#zookeeper#platform#zookeeper': rpc error: code = Unknown desc = failed to create resource: configmaps "zk-a-8ap5vlrdbpc00" is forbidden: unable to create new content in namespace east because it is being terminated.
Frostman commented 6 years ago

The error is clear - namespace is terminated. You should wait till it'll be terminated completely.

Frostman commented 6 years ago

Oh, I see, it's not propagated to the client.

romangithub1024 commented 6 years ago

related to the fact that apply logs are not propagated to the client. will create another issue for it. client won't need to display logs directly, it will need to display CMD + HTTP LINK to show logs