| Summary: | [ovirt] [vdsm] change storage exception to suit upstream (error: 613,614) | ||
|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Haim <hateya> |
| Component: | vdsm | Assignee: | Dan Kenigsberg <danken> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | abaron, acathrow, amureini, bazulay, hateya, iheim, jbrier, mgoldboi, yeylon, ykaul |
| Target Milestone: | --- | ||
| Target Release: | 3.3.4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | storage | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-03-12 09:37:21 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Since the bug causing this is in RHEV-2.2.0 only, and was never in upstream Vdsm, the exception would never appear for non-customers. I would have closed this bug as wontfix, but "Redhat" is misspelled, so we should fix that. We also refer to a "GSS knowledge base" instead of providing a link to it. Vladik can you help with that? *** Bug 766837 has been marked as a duplicate of this bug. *** (In reply to comment #1) > Since the bug causing this is in RHEV-2.2.0 only, and was never in upstream > Vdsm, the exception would never appear for non-customers. > > I would have closed this bug as wontfix, but "Redhat" is misspelled, so we > should fix that. for 613 I have some additional suggestions (from #766837) "Redhat" should be Red Hat [1] It should be Global Support Services, not just "Global Support." Regardless I would use just "Red Hat Support" instead of Global Support Services since GSS is mostly an internal reference, if you go to our website most of the references these days just say "Red Hat Support" In addition it would save us calls if you could just give a link to creating a ticket instead of suggesting a phone call. It will be faster for everyone: https://access.redhat.com/support/cases/new If you still want to suggest calling you could give the URL to phone number: https://access.redhat.com/support/contact/technicalSupport.html > > We also refer to a "GSS knowledge base" instead of providing a link to it. > Vladik can you help with that? Here is the link https://access.redhat.com/kb/knowledgebase for 614 here are my comments (from #766837) Customers may not be familiar with GSS as an acronym for Global Support Services. Here I suggest "Red Hat Support" or at least "Global Support Services," but definitely not the acronym. Additionally I would suggest you should refer to the "Knowledgebase on the Red Hat Customer Portal" instead of "GSS/Support knowledgebase." This will help in finding the knowledgebase from our site as that's how it's listed from the main page. FWIW, there was no public kbase on this issue when I encountered a customer opening a case on this exact error message. In the future it would be best if you could coordinate with GSS to ensure that if RHEV references the knowledgebase for a specific issue it is already in there so that customers can find it. 1) https://home.corp.redhat.com/sites/default/files/shared_files/DesignThinkingBrandBook.pdf Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug. |
Description of problem: from storage exception, we have the following alerts stating there is a problem with vg suggesting user to call Redhat support; class VgMetadataCriticallyFull(StorageException): def __init__(self, vgname, mdasize, mdafree): self.value = "vgname=%s mdasize=%s mdafree=%s" % (vgname, mdasize, mdafree) code = 613 message = """Error - The system has reached the high watermark on the VG metadata area size. This is due high number of Vdisks or large Vdisks size allocated on this specific VG. Please call Redhat Global Support to address the issue""" class SmallVgMetadata(StorageException): def __init__(self, vgname, mdasize, mdafree): self.value = "vgname=%s mdasize=%s mdafree=%s" % (vgname, mdasize, mdafree) code = 614 message = """Warning - The allocated VG metadata area size is too small, which might limit its capacity (the number of Vdisks and/or their size). Refer to GSS knowledge base to understand the issue and how to resolve it""" please change description to fit upstream as it ***should*** run over Fedora and we don't have support for it. git; d5c8ceb6964c44f7a6ff2781a0f8591b60625729