Bug 1417752
Summary: | Satellite Capsule syncs error out when there are more than a certain amount of characters in the content view name | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Sam Yangsao <syangsao> |
Component: | Content Management | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED ERRATA | QA Contact: | Lai <ltran> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2.7 | CC: | aladke, avroy, bbuckingham, ehelms, heiko.hemmerling, juwatts, mmccune, sraut |
Target Milestone: | 6.10.0 | Keywords: | Reopened, Triaged |
Target Release: | Unused | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-11-16 14:08:26 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
Sam Yangsao
2017-01-30 21:40:38 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you. I have the same problem with Satellite 6.8. To me it looks like the generated data name, which causes problems here, has a length of 287 characters. That is obviously 32 characters too many. The part of this file name that I am responsible for is 56 characters. Assuming that the organization, lifecycle and content view are represented in these 56 characters, that is by no means too much. I find the far too long repo names that RedHat is responsible for much more difficult here. Now these repos are called that and it is difficult to change that afterwards. So the only acceptable solution is to remove or extend the 255 character limit! Otherwise the capsule cannot be used by us, which I would have to escalate accordingly. We are going to re-open this bug as it will be resolved in Satellite 6.10 with our move to Pulp 3 as the content storage backend for Satellite. Pulp 3 uses an entirely different database and filesystem layout for storing content and repositories that will not face the 255 character limitation as outlined in this bug. We will add this to our verification and test cycle of Satellite 6.10 to ensure that this issue does not effect our customers and users. Steps to retest: 1. Register a capsule to a sat via an ak 2. Ensure subscriptions and repos are present by running "subscription-manager repos" or "yum repolist" 3. Create a cv with over 255 characters in the name 4. Create a cv with exactly 255 characters in the name 5. Add necessary a sample repo to the cv created in 4 and publish 6. Check tasks page Expected: 3. Should be an error that says only have a 255 character limit 4. Should be able to create cv successfully 6. Actions::Katello::ContentView::CapsuleGenerateAndSync should be successful Actual: 3. There's an error that says only have a 255 character limit 4. Able to create cv successfully 6. Actions::Katello::ContentView::CapsuleGenerateAndSync is successful Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Satellite 6.10 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:4702 |