Bug 1192356
Summary: | On updating the content-host limit with long integer under activation-key, UI neither raised any error nor save the changes | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Sachin Ghai <sghai> | ||||||
Component: | Activation Keys | Assignee: | Brad Buckingham <bbuckingham> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Perry Gagne <pgagne> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 6.1.0 | CC: | bbuckingham, rplevka | ||||||
Target Milestone: | Unspecified | Keywords: | Triaged | ||||||
Target Release: | Unused | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2016-07-27 09:13:15 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: | |||||||||
Attachments: |
|
Description
Sachin Ghai
2015-02-13 08:50:14 UTC
Created attachment 991268 [details]
no error raised on UI, on updating content host limit with long integer value
The issue seems to exist on all the numerical id-related attributes and originates from the API. Here's the bug I created to cover the root cause issue: 1252046 I have tested this on a Satellite 6.1.1 GA install and am no longer observing the behavior described. RPMs: ruby193-rubygem-katello-2.2.0.66-1.el7sat.noarch foreman-1.7.2.34-1.el7sat.noarch Attaching updated screenshot. Created attachment 1069118 [details]
Satellite 6.1.1: Activation Key validation error
VERIFIED as Comment#5 states, the issue has been fixed in 6.1.1 and no longer occurs. 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, 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/RHBA-2016:1501 |