Ohara: StreamApp can't be used in manager's pipeline

[HarryChiang143]

Describe the bug
使用v0.6.0 的ohara-quickstart-vm，在Pipeline中無法添加已上傳的streamApp

To Reproduce
Steps to reproduce the behavior:

1. 匯入ohara-quickstart-vm
2. 啟動configurator、manager
3. 建立node、workspace，創建topic及上傳streamapp
4. 建立pipeline，添加streamapp，跳出streamapp doesn't exist錯誤
   
5. 砍掉pipeline，嘗試從workspace清除已上傳streamapp失敗
   

Expected behavior

1. streamapp上傳後應可在pipeline中正常使用。
2. 沒有pipeline使用該streamapp時應可正常刪除。

Screenshots
reference logs from ohara-configurator:
First Error msg:

Second Error msg:

刪除失敗的log msg:

Operation System (please complete the following information):

• Backend OS & Version: CentOS 7.3
• Frontend OS & Version: CentOS 7.3
  
• Browser & Version : Google Chrome , 版本 75.0.3770.100 (正式版本) (64 位元)

[saivirtue]

thanks for reporting, I will take a look later.

[saivirtue]

It is due to the error message response from api cannot be parsed in manager when streamApp is not starting yet.
Since we are going to release 0.7, is it urgent for you to fix it in 0.6?

[HarryChiang143]

I think this issue fix in later version is ok , plz fix it before 1.0 release.

[vitojeng]

@saivirtue Can we fix this issue in v0.7 ?

[saivirtue]

@saivirtue Can we fix this issue in v0.7 ?

Sure :)

[saivirtue]

@HarryChiang143
This should be fixed in 0.7. Could you help me to verify if resolved?

[HarryChiang143]

@saivirtue I think this bug already fixed in 0.7

[HarryChiang143]

@saivirtue

我發現第二個預期的behavior仍然未能運作。

• [ ]沒有pipeline使用該streamapp時應可正常刪除。

[chia7712]

我發現第二個預期的behavior仍然未能運作。

你是指streamapp "jar"嗎

[saivirtue]

你是指streamapp "jar"嗎

@HarryChiang143 的意思應該是streamApp jar 即使在pipeline刪除後依然不能delete

[chia7712]

的意思應該是streamApp jar 即使在pipeline刪除後依然不能delete

我記得0.7在刪除pipeline時"不會"清除底下的物件(例如streamapp, connector)，所以該jar無法刪除是合理的，因為"仍然"有streamapp在使用該jar

FYI @konekoya @wu87988622

[HarryChiang143]

As discussion before, i will check this scenario on v0.8

[konekoya]

0.7在刪除pipeline時"不會"清除底下的物件(例如streamapp, connector)，所以該jar無法刪除是合理的，因為"仍然"有streamapp在使用該jar

Yep. This issue will be addressed in 0.8. Please follow the issue here #2321

[chia7712]

@HarryChiang143 Could we close this issue?

[HarryChiang143]

@chia7712 Sure, i will track last issue on #2321