| Summary: | phpmyadmin should be removed when mysql was being removed | ||
|---|---|---|---|
| Product: | OKD | Reporter: | Linqing Lu <lilu> |
| Component: | Containers | Assignee: | Dan McPherson <dmcphers> |
| Status: | CLOSED WONTFIX | QA Contact: | libra bugs <libra-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1.x | CC: | gshipley |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-02-01 17:03:53 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Linqing Lu
2012-02-01 10:42:17 UTC
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. |