Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-38479 Enhance validation for Hostname Prefix in discovery setting.
  3. SAT-38697

[QE] Enhance validation for Hostname Prefix in discovery setting.

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Discovery Plugin
    • False
    • Hide

      None

      Show
      None
    • False
    • 0
    • sat-rocket
    • Satellite Rocket Sprint 5, Satellite Rocket Sprint 6, Satellite Rocket Sprint 7

      Problem Statement

      Currently, hostname validation logic does not fully comply with RFC 1123 rules. This leads to invalid hostnames being correctly submitted.
      Users expect hostname validation to align with industry standards ensuring compliance eliminates unnecessary errors and improves consistency.

      User Experience & Workflow

      • Go to Administer and then to settings
      • move to Discovery tab
      • click on edit icon for Hostname Prefix

      System validates hostname format:

      • Must start with an alphabetic character (A–Z, a–z).
      • Can contain letters, numbers, and hyphens (A–Z, a–z, 0–9, -).
      • Each label must be 1–62 characters.

      Requirements

      Regex update to allow [A-Za-z][A-Za-z0-9-]{0,62} for RFC 1123 compliance.

      • Validation for maximum 62 characters per label.
      • Clear error messages for invalid input (e.g., "Hostnames cannot exceed 62 characters per label").{}

      Business Impact

      • Increased support tickets from users facing hostname validation issues.
      • Workarounds at customer sites, reducing trust in product compliance.

      QE Tracker for https://issues.redhat.com/browse/SAT-38479

              rh-ee-napathak Nakul Pathak
              satellite-jira-automation@redhat.com Satellite Jira-Automation
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: