Bug 1408438 - Error"No route matches" when editing a host
Summary: Error"No route matches" when editing a host
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.2.4
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: Unspecified
Assignee: Tomer Brisker
QA Contact: Renzo Nuccitelli
URL:
Whiteboard:
Depends On:
Blocks: 1426405
TreeView+ depends on / blocked
 
Reported: 2016-12-23 11:58 UTC by Manikandan Somasundaram
Modified: 2020-06-11 13:10 UTC (History)
10 users (show)

Fixed In Version: foreman-1.11.0.72-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1426405 (view as bug list)
Environment:
Last Closed: 2017-05-01 13:57:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 9531 0 None None None 2017-01-11 15:53:09 UTC
Red Hat Product Errata RHBA-2017:1191 0 normal SHIPPED_LIVE Satellite 6.2.9 Async Bug Release 2017-05-01 17:49:42 UTC

Comment 2 Tomer Brisker 2017-01-11 15:53:06 UTC 
Connecting redmine issue http://projects.theforeman.org/issues/9531 from this bug
Comment 3 Satellite Program 2017-01-12 11:16:05 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/9531 has been resolved.
Comment 7 Daniel Lobato Garcia 2017-01-27 08:43:57 UTC 
Setting as triaged as there's a fix already upstream
Comment 10 Satellite Program 2017-02-23 21:10:39 UTC 
Please add verifications steps for this bug to help QE verify
Comment 11 Tomer Brisker 2017-02-26 08:08:39 UTC 
Verification steps:

1. Edit a host and delete the host name.
2. Attempt to save and verify a validation message is displayed and no ISE occurs.
3. Edit the host name to contain the character "/".
4. Attempt to save again and verify a validation message is displayed and no ISE occurs.
Comment 14 Renzo Nuccitelli 2017-03-31 17:47:26 UTC 
No empty name allowed during host edition on sat 6.2.9 snap 1. No string containing "/" as well. 

Besides that on last case the message could be "no / char allowed" instead of  "is invalid".

But once this is a nitpick I am moving this to VERIFIED.
Comment 16 errata-xmlrpc 2017-05-01 13:57:25 UTC 
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-2017:1191
Note You need to log in before you can comment on or make changes to this bug.