This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2265142 - asterisk symbol is missing for required field
Summary: asterisk symbol is missing for required field
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Credentials
Version: 6.15.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: stream
Assignee: Ian Ballou
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-02-20 16:42 UTC by amolpati
Modified: 2024-06-06 17:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:03:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
reference image for - missing asterisk symbol (26.96 KB, image/png)
2024-02-20 16:42 UTC, amolpati
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 37482 0 Normal Closed asterisk symbol is missing for required field 2024-05-20 14:29:35 UTC
Red Hat Issue Tracker   SAT-23426 0 None Migrated None 2024-06-06 17:03:44 UTC

Description amolpati 2024-02-20 16:42:12 UTC
Created attachment 2017825 [details]
reference image for - missing asterisk symbol

Created attachment 2017825 [details]
reference image for - missing asterisk symbol

Description of problem:

when we click on save it gives "An error occurred while creating the Content Credential: Validation failed: Content can't be blank". It shows it is required field and w/o that we can move forward. Also there is no content validation on content type.

Version-Release number of selected component (if applicable):

6.15

How reproducible:

always

Steps to Reproduce:
1. Content -> Content Credential -> click on create
2. w/o adding any content in "Content Credential Contents" click on save, it will throw error 
3. and for name field "save" option remains blur until we put any name

Actual results:

asterisk symbol is missing for required fields like name, Content Credential Contents

Expected results:

asterisk symbol should be there for required fields

Comment 1 Ian Ballou 2024-05-16 17:46:14 UTC
Created redmine issue https://projects.theforeman.org/issues/37482 from this bug

Comment 2 Ian Ballou 2024-05-20 16:46:54 UTC
Moving to POST since the upstream PR is merged.

Comment 3 Eric Helms 2024-06-06 17:03:45 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.


Note You need to log in before you can comment on or make changes to this bug.