Bug 1414618 - Hypervisor host can't register to satellite web UI when hypervisor hostname using special character
Summary: Hypervisor host can't register to satellite web UI when hypervisor hostname u...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscriptions - virt-who
Version: 6.2.7
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Tom McKay
Tom McKay
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-19 03:08 UTC by yanpliu
Modified: 2017-06-27 14:10 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-01 13:32:23 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description yanpliu 2017-01-19 03:08:19 UTC
Description of problem:
Hypervisor host can't register to satellite WEB UI when using special character. but virt-who can send json information successfully.


Version-Release number of selected component (if applicable):
Satellite6.2.7-snap2.0
virt-who-0.17-10.el6sat.noarch
Hypervisor: libvirt

How reproducible:
Always

Steps to Reproduce:

1. Register virt-who to satellite6.2.7 
2. Register Hypervisor guest to satellite6.2.7 on Organization:Default_Organization
3. change Hypervisor short hostname using special characters ,such as "hp-z220-06a!#$%^&*"
# hostname
hp-z220-06a!#$%^&*
# hostname -s
hp-z220-06a!#$%^&*
4. vim /etc/virt-who.d/libvirt.conf
[test-libvirt]
type=libvirt
server=10.66.144.4
username=root
password=XXXXX
owner=Default_Organization
env=Library
rhsm_username=admin
rhsm_password=XXXXX
hypervisor_id=hostname
rhsm_password=XXXXXXXXX
 
5. restart virt-who service
# service virt-who restart
Stopping virt-who: [  OK  ]
Starting virt-who: [  OK  ]

6. hypervisor host and guest json info sent successfully, and the json info should be print with hypervisor's hostname with special characters.

MainProcess(10816):MainThread @subscriptionmanager.py:hypervisorCheckIn:194 - Sending update in hosts-to-guests mapping for config "test-libvirt": 1 hypervisors and 2 guests found
2017-01-18 21:41:52,011 [virtwho.main DEBUG] MainProcess(10816):MainThread @subscriptionmanager.py:hypervisorCheckIn:195 - Host-to-guest mapping: {
    "hp-z220-06a!#$%^&*": [
        {
            "guestId": "1f994abe-2df4-9cbd-9b60-d7a07a8d6f67", 
            "state": 5, 
            "attributes": {
                "active": 0, 
                "virtWhoType": "libvirt"
            }
        }, 
        {
            "guestId": "65681fef-4d66-a804-9825-66a4a22b053d", 
            "state": 5, 
            "attributes": {
                "active": 0, 
                "virtWhoType": "libvirt"
            }
        }
    ]
}
2017-01-18 21:41:55,968 [virtwho.main DEBUG] MainProcess(10816):MainThread @executor.py:send_report:101 - Report for config "test-libvirt" sent
2017-01-18 21:42:48,045 [virtwho.test-libvirt DEBUG] Libvirtd-1(10820):MainThread @libvirtd.py:_listDomains:245 - Libvirt domains found: 1f994abe-2df4-9cbd-9b60-d7a07a8d6f67, 65681fef-4d66-a804-9825-66a4a22b053d
7. check Default_Organization->Hosts->Content Hosts
Hypervisor host can not register to satellite in web ui.

Actual results:
Hypervisor host can not register to satellite in web ui.


Expected results:
Hypervisor host should be registered to satellite in web ui.

Additional info:

Comment 4 yanpliu 2017-03-28 08:36:38 UTC
Yes, it is a real hostname.

Comment 5 Brad Buckingham 2017-06-01 13:32:23 UTC
Based on discussion in triage involving PM, ENG, QE and CEE, this is not a bug, since hostnames within Satellite must be RFC compliant.  If you have any concerns about this, please feel free to contact Rich Jerrido. Thank you.


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