Hide Forgot
Description of problem: After I created an application without adding any cartridges, click the Details link and click the Add link on details page, the /cartridge_types page does not match the details of applications sometimes, it will show that some cartridges are already installed.If I cleared my cookies and sign in again, sometimes the page will return normal, sometimes it will not. Version-Release number of selected component (if applicable): How reproducible:randomly Steps to Reproduce: 1.Go to openshift website and log in 2.Create an application and go the the details page of this application 3.Try to add a cartridge of this application. Actual results: The /cartridge_types page does not match the details of applications sometimes. Expected results: The /cartridge_types page should match the details of applications sometimes. Additional info: This issue did not exist on devenv-stage_146.
Not sure what code causes this regression, since it can not always reproduced, give it medium priority, but we do hope you could check what happened to it before push to production. Thanks
Is this still happening? I can't recreate it locally in my devenv.
Fixed.
(In reply to comment #3) Tested this bug on devenv-stage_154, does not have this issue now, thanks.
(In reply to comment #3) hi Fabiano, need to re-open this bug for I met this issue on stage again, still randomly, could you please check this again?
It's so strange that it seems this bug only occurs on stage, it works well on all the devenv build and production (since it's failed on stage-2.0.7, but it works on production-2.0.7), could you please check what's different between devenv and stage about this? Since it's not always, let me reduce its severity to low.
It occurs again on stage-2.0.10, but it works on devenv-stage_183.
This looks like a two node issue, as if the broker is out of sync between the nodes, or there is a cache issue at play.
I found an problem in stage, when I am trying to add the mysql to an app, it failed, and the error message is "You must create a Jenkins application as a server before you can add the Jenkins cartridge to an application". But it occurred just once.I can't reproduce it again. And I took the snapshot(badge6.png), and can refer to it.
Created attachment 584266 [details] The snapshot of adding mysql.
When we fixed this, my understanding was that the error code from the server would be a specific code to correspond to jenkins failing to be added. However, what we are getting is 143, which is the generic "could not add cartridge due to node failure, retry". We need a more specific error code to be set by the node on this failure (not 143) and then the UI needs to change to react specifically to that code. Medium severity because we are displaying the wrong message to end users in error scenarios Krishna, is this your code or the runtime teams?
This is probably in broker code.
https://github.com/openshift/crankcase/pull/37
I've gotta make a change first.
Have to fix this in bug 821915. Closing this story out. The REST API should return an exit code to the client that is 0
Fixed on my end
It is not fixed on current stage. I still can reproduce it. The step of reproduce. 1.Log on the openshift website. 2.create two applications. 3.Add some cartridge to the first application, such as mysql,cron,monogdb. 4.Go to the second application's detail page, and go to cartridge type page. 5.If you saw the page is regular, you just refresh the page, it will reproduce this problem.
I will test it again,after the new stage pushed.
It still exists on int.openshift.redhat.com. The step of reproduce(must follow this step): 1.create a jboss app 2.embed the mysql ,mectrics, monodb,rockmongo to the jboss app 3.create a php app 4.click the php app detail page 5.click the add cartridge page. 6.If the page is normal , please re refresh it again and again till the problem page is presented.
Can you get a screenshot and a copy of both site/development.log and broker/development.log when you reproduce this?
(In reply to comment #20) Did not meet this issue on devenv_1806, I will test it again on stage.
Tested on stage, did not meet this issue, verify this bug.