When creating plans from the API, the GUI never refreshes

[Udi Kalifon]

When logging in to a fresh system, where no plans are uploaded yet, you see "No Deployment Plans Available" in the deployment plan page. If you then create a plan from the API:

openstack token issue
curl -X POST -H "x-auth-token:$TOKEN" http://localhost:8585/v1/plans -d plan.json

... The GUI never sees it. Hitting F5 starts a spinner with a message: "Loading Deployments...", and it also never ends.

[Ana Krivokapić (akrivoka)]

The fact that it doesn't auto-detect it is probably by design. But if it doesn't detect it even after refresh, that's a bug that we should fix.

[Jiri Tomasek (jtomasek)]

Pasting a browser console output would be helpful

[Udi Kalifon (ukalifon)]

the refresh works now. However, I saw 2 errors in the console, not sure if they are related to any bug or not:

http://lynx14.qa.lab.tlv.redhat.com:5001/v1/stages/?plan_id= net::ERR_EMPTY_RESPONSE
getRequest @ reqwest.js:240
init @ reqwest.js:380
Reqwest @ reqwest.js:249
reqwest @ reqwest.js:444
getStages @ ValidationsApiService.js:73
(anonymous function) @ ValidationsActions.js:13
(anonymous function) @ index.js:9
fetchValidationStages @ AuthenticatedContent.js:88
componentDidMount @ AuthenticatedContent.js:17
assign.notifyAll @ CallbackQueue.js:65
ON_DOM_READY_QUEUEING.close @ ReactReconcileTransaction.js:81
Mixin.closeAll @ Transaction.js:202
Mixin.perform @ Transaction.js:149
batchedMountComponentIntoNode @ ReactMount.js:282
Mixin.perform @ Transaction.js:136
ReactDefaultBatchingStrategy.batchedUpdates @ ReactDefaultBatchingStrategy.js:62
batchedUpdates @ ReactUpdates.js:94
ReactMount._renderNewRootComponent @ ReactMount.js:476
ReactMount__renderNewRootComponent @ ReactPerf.js:66
ReactMount._renderSubtreeIntoContainer @ ReactMount.js:550
ReactMount.render @ ReactMount.js:570
React_render @ ReactPerf.js:66
(anonymous function) @ index.js:112
tryCatchReject @ makePromise.js:845
runContinuation1 @ makePromise.js:804
Fulfilled.when @ makePromise.js:592
Pending.run @ makePromise.js:483
Scheduler._drain @ Scheduler.js:62
Scheduler.drain @ Scheduler.js:27
run @ env.js:63

ValidationActions.fetchValidationStages
XMLHttpRequest {readyState: 4, timeout: 0, withCredentials: false, upload: XMLHttpRequestUpload, responseURL: ""…}
(anonymous function) @ ValidationsActions.js:17
tryCatchReject @ makePromise.js:845
runContinuation1 @ makePromise.js:804
Rejected.when @ makePromise.js:625
Pending.run @ makePromise.js:483
Scheduler._drain @ Scheduler.js:62
Scheduler.drain @ Scheduler.js:27
run @ env.js:63

[Florian Fuchs (flo-fuchs)]

That traceback seems to be unrelated to plans management: The url mentioned points to the validations api. If the plans refresh works, maybe the 2 console errors could be followed up on in another bug report?