Show Table of Contents
Chapter 3. Known Issues
This chapter describes known issues in Red Hat Satellite 6.1 and, where possible, suitable workarounds.
3.1. API Issues
This section describes known issues with the Satellite 6.1 API.
- Issue
If you create a docker repository that has tags and then synchronize it in one organization, and then view the Docker Tags page for another organization, you can see all the tags for the first organization.
WorkaroundNone at this time.
- BZ 1111574: Content Host API Calls Time Out
- Red Hat Satellite 6 APIs that call the "GET /katello/api/systems (DEPRECATED) List content hosts" method may experience performance issues when there are over 300 hosts registered on the Satellite Server.
- BZ 1239077: Cannot rename product to original name after importing a manifest
Issue
If you create a product in a new organization, import a manifest, and then rename the product, you cannot rename the product to its original name. For example, in the following scenario:- Create a product "MyProduct" in a new organization.
- Import a manifest.
- Rename the product to "YourProduct".
- Attempt to rename the product to "MyProduct".
This results in the following error message:Error: Validation failed: Name Product with name 'MyProduct' already exists in this organization.
Workaround
You can run the following command to work around this issue:# foreman-rake console > Katello::MarketingProduct.find_by_name('MyProduct').destroyThis allows you to rename the product.Note
This issue might return as soon as you import or refresh a manifest.- BZ 1241077: API settings unquoted integer provided gives error
- Issue
If you provide a numeric value to an API element which requires a numeric value, you may see the following error message.
Value is invalid: must be integer
The cause of this issue is that the value is tested with a regular expression and the numeric value fails the test.WorkaroundEnclose the numeric value in quote characters (").
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.