Bug 851285
Summary: | mysql cartridge added, but no info given | ||
---|---|---|---|
Product: | OKD | Reporter: | Amit Shah <amit.shah> |
Component: | Pod | Assignee: | Rajat Chopra <rchopra> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.x | CC: | bmeng, dmcphers, rmillner |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-09-17 21:29:51 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Amit Shah
2012-08-23 16:51:58 UTC
What version of the client do you have? Amit, something is wrong with this apps setup. We are looking to figure out what went wrong. But you'll probably want to delete the app and recreate it. We might have to delete parts of it manually. Let me know if you want to go this route and we can work out the details. (In reply to comment #1) > What version of the client do you have? rubygem-rhc-0.92.11-1.fc16.noarch The other apps (which are working perfectly fine) were created on a different system, which has a different version of the 'rhc' package: rhc-0.96.9-1.el6_3.noarch. Both run F16. (In reply to comment #2) > Amit, something is wrong with this apps setup. We are looking to figure out > what went wrong. But you'll probably want to delete the app and recreate > it. We might have to delete parts of it manually. Let me know if you want > to go this route and we can work out the details. I can destroy and re-create the app, this time from the other machine, to check if things work OK. Do you want me to preserve some parts of the app for your troubleshooting? Do you want me to keep the app around till some time for you to poke at it? Lets keep the app for a while to debug. I assume you can still create similar app successully using the same client tool without issues, so its not a consistent problem. (In reply to comment #4) > Lets keep the app for a while to debug. > I assume you can still create similar app successully using the same client > tool without issues, so its not a consistent problem. Dunno; I've reached my limit of maximum apps, so can't confirm things till I destroy this one and re-create another one. Ok. I think you can destroy and re-create the app. The existing app in its current form will be difficult to restore. Debugged this and found that there was an apparent server restart that happened at the same time as the app was being created. This resulted in runaway gear. There are known issues with database consistency that we are addressing in forthcoming releases. The DNS should get fixed with the new app as well. Please let it be known if there are issues in deleting the old app. Amit, could you please help mark this bug as VERIFIED if your problem has gone since the comment#6. And we cannot know that if your account's issue has been resolved. Thanks. (In reply to comment #6) > Ok. I think you can destroy and re-create the app. The existing app in its > current form will be difficult to restore. > > Debugged this and found that there was an apparent server restart that > happened at the same time as the app was being created. This resulted in > runaway gear. There are known issues with database consistency that we are > addressing in forthcoming releases. > > The DNS should get fixed with the new app as well. Please let it be known if > there are issues in deleting the old app. I re-created the app, and everything's working fine now. Thanks. (In reply to comment #7) > Amit, could you please help mark this bug as VERIFIED if your problem has > gone since the comment#6. I can, but as I understand from comment 6, the fix is supposed to be rolled out in the future. Do you want to wait for the fix to be rolled out and use this bug for tracking? Lets treat this bug as production issue arising from known limitations. We are tracking the inconsistency problems as part of planned feature work. Based on comment #8, marking this bug as verified. |