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.

Description of problem:
HW model names starting with number are wrongly treated as IDs. 
Accessing HW model with name starting with number (name=1foo) turns wrongly into accessing completely different HW model with id derived from the name (id=1)

Version-Release number of selected component (if applicable):
@satellite-6.2.8-4.0.el7sat.noarch

How reproducible:
Have HW model with name that converts into existing id

Steps to Reproduce:
1. Have at least one HW model defined.
2. Crete HW model with the name '1foo'
3. Try to Access/Edit the HW model '1foo'

>>> you see details for HW model with id=1


Actual results:
editing completely different HW model

Expected results:
editing correct HW model

Although not completely identical in symptoms, this is caused by the same root cause as bz1265150 which has already been fixed upstream. Closing as dup.

*** This bug has been marked as a duplicate of bug 1265150 ***