Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-22382

Hostname complexity warning remains after a compliant hostname has been supplied

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 6.9.0
    • Host Form
    • Low
    • No

      Description of problem:

      When cloning a host in Satellite 6.9 and 6.10 (I haven't tested older versions), we immediately see this warning for the hostname field:

      can't be blank and hostname can only contain lowercase letters, numbers, dashes and dots according to RFC921, RFC952 and RFC1123

      The warning persists even after entering a hostname that complies with the text. It doesn't prevent the provisioning process from continuing, but at least one customer has observed that for an error message to remain on-screen when it is no longer valid can cause confusion.

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

      Satellite 6.9, 6.10, possibly others

      How reproducible:

      100%

      Steps to Reproduce:
      1. clone a host in Satellite
      2. enter a compliant hostname
      3. observe that the error message remains

      Actual results:

      The error message persists even after entering a valid hostname.

      Expected results:

      The error message should vanish after entering a valid hostname.

              jira-bugzilla-migration RH Bugzilla Integration
              jira-bugzilla-migration RH Bugzilla Integration
              RH Bugzilla Integration RH Bugzilla Integration
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: