Hide Forgot
Description of problem: phpmyadmin should be removed when mysql was being removed less resource occupation, better UE Version-Release number of selected component (if applicable): devenv_1575 How reproducible: Steps to Reproduce: 1. create app 2. embed mysql and phpmyadmin, confirming them working well 3. remove mysql 5. check phpmyadmin Actual results: phpmyadmin still exists, and showing error in web page Expected results: phpmyadmin removed as well Additional info: [root@intel-q8200novt-8-6 bin]# rhc-ctl-app -e remove-mysql-5.1 -a java Password: Contacting https://ec2-107-22-47-30.compute-1.amazonaws.com Response from server: DEBUG: Exit Code: 0 api_c: placeholder broker_c: namespacerhloginsshapp_uuiddebugaltercartridgecart_typeactionapp_nameapi API version: 1.1.2 Broker version: 1.1.1 RESULT: Success [root@intel-q8200novt-8-6 bin]# rhc domain Password: User Info ========= Namespace: lilu8 RHLogin: lilu+8 Application Info ================ java Framework: jbossas-7.0 Creation: 2012-02-01T03:15:05-05:00 UUID: 73b0115682e246d6b8b0a82a87fd29b2 Git URL: ssh://73b0115682e246d6b8b0a82a87fd29b2.rhcloud.com/~/git/java.git/ Public URL: http://java-lilu8.dev.rhcloud.com/ Embedded: rockmongo-1.1 - URL: https://java-lilu8.dev.rhcloud.com/rockmongo/ mongodb-2.0 - Connection URL: mongodb://127.0.251.1:27017/ phpmyadmin-3.4 - URL: https://java-lilu8.dev.rhcloud.com/phpmyadmin/
This isn't any different for mongo and rock mongo is it? We might change our minds about this later but for now I am hestitant to do this automatically. The user might be removing mysql just to add it back. And changing phpmyadmin would make them setup their pw for that again.
(In reply to comment #1) > This isn't any different for mongo and rock mongo is it? > > We might change our minds about this later but for now I am hestitant to do > this automatically. The user might be removing mysql just to add it back. And > changing phpmyadmin would make them setup their pw for that again. I'm not sure whether the pw here you mentioned indicates the admin password of phpmyadmin. This password will be changed when user remove mysql then add it back, no matter phpmyadmin is the old one or new. And so is rockmongo, right?
I was referring the the pw of phpmyadmin. Are you saying that's changed when you remove and add mysql?
(In reply to comment #3) > I was referring the the pw of phpmyadmin. Are you saying that's changed when > you remove and add mysql? Yes, user/pw of phpmyadmin is actually the user/pw of mysql database. If pw of mysql changed, it changes too.
Geez... I haven't noticed that before. Since it is output when you add phpmyadmin I thought it was from phpmyadmin. That makes sense though. So I think my only reason left not to do it is just to avoid the act of re-adding phpmyadmin if you are going to readd mysql. I'm going to stick with that for now but this decision may change in the near future. Thanks for setting me straight :)
Glad I can help :) Actually you gave me another thought about this. Currently, nobody tells users that re-adding mysql will cause the change of phpmyadmin pw, so they may hit "wrong password" after re-adding mysql. If we are not going to do this auto-removing thing, maybe we should give users a notice about that when re-adding mysql, or tell them both pw are identical when embedding phpmyadmin instead of giving a pw like it's individual. So does mongo.
I like the making it more clear when adding phpmyadmin. Feel free to reopen this defect with that request or open a new one.