Since it also exist on RHEL-6.9-20161216.1, clone it to track it on RHEL6.9

+++ This bug was initially created as a clone of Bug #1368341 +++

Description of problem:
When system registered to stage candlepin, run virt-who with --sam/satellite6 in CLI,virt-who still can send mapping info to stage candlepin.

Version-Release number of selected component (if applicable):
virt-who-0.17-7.el7.noarch
subscription-manager-1.17.10-1.el7.x86_64
python-rhsm-1.17.6-1.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Register system to stage candlepin
2. Run virt-who in CLI with --sam/--satellite6
[root@cloud-qe-16-vm-03 ~]# virt-who --hyperv --hyperv-owner=8036391 --hyperv-env=Library --hyperv-server=10.73.5.203 --hyperv-username=administrator --hyperv-password=Welcome1 -o -d --sam
or 
[root@cloud-qe-16-vm-03 ~]# virt-who --hyperv --hyperv-owner=8036391 --hyperv-env=Library --hyperv-server=10.73.5.203 --hyperv-username=administrator --hyperv-password=Welcome1 -o -d --satellite6
2016-08-19 02:19:54,065 [virtwho.init INFO] MainProcess(15478):MainThread @main.py:main:160 - Using configuration "env/cmdline" ("hyperv" mode)
2016-08-19 02:19:54,066 [virtwho.init INFO] MainProcess(15478):MainThread @main.py:main:162 - Using reporter_id='cloud-qe-16-vm-03.idmqe.lab.eng.bos.redhat.com-41e2151a02208a886d33766e1c88c11e'
2016-08-19 02:19:54,109 [virtwho.env_cmdline DEBUG] MainProcess(15478):MainThread @hyperv.py:__init__:472 - Hyper-V url: http://10.73.5.203:5985/wsman
2016-08-19 02:19:54,115 [virtwho.env_cmdline DEBUG] HyperV-1(15485):MainThread @virt.py:run:364 - Virt backend 'env/cmdline' started
2016-08-19 02:19:54,761 [virtwho.env_cmdline DEBUG] HyperV-1(15485):MainThread @hyperv.py:retry_ntlm_negotitate:64 - Using NTLM authentication
2016-08-19 02:19:55,382 [virtwho.env_cmdline DEBUG] HyperV-1(15485):MainThread @hyperv.py:retry_ntlm_authenticate:77 - Sending NTLM authentication data
2016-08-19 02:19:55,706 [virtwho.env_cmdline DEBUG] HyperV-1(15485):MainThread @hyperv.py:retry_ntlm_authenticate:100 - NTLM authentication successful
2016-08-19 02:19:55,715 [virtwho.env_cmdline DEBUG] HyperV-1(15485):MainThread @hyperv.py:getHostGuestMapping:520 - Unable to enumerate using root/virtualization namespace, trying root/virtualization/v2 namespace
2016-08-19 02:20:02,162 [virtwho.env_cmdline DEBUG] HyperV-1(15485):MainThread @virt.py:enqueue:357 - Report for config "env/cmdline" gathered, putting to queue for sending
2016-08-19 02:20:02,166 [virtwho.env_cmdline DEBUG] HyperV-1(15485):MainThread @virt.py:run:385 - Virt backend 'env/cmdline' stopped after sending one report
2016-08-19 02:20:02,193 [virtwho.main DEBUG] MainProcess(15478):MainThread @subscriptionmanager.py:_connect:123 - Authenticating with certificate: /etc/pki/consumer/cert.pem
2016-08-19 02:20:02,737 [virtwho.main DEBUG] MainProcess(15478):MainThread @subscriptionmanager.py:hypervisorCheckIn:171 - Checking if server has capability 'hypervisor_async'
2016-08-19 02:20:03,279 [virtwho.main DEBUG] MainProcess(15478):MainThread @subscriptionmanager.py:hypervisorCheckIn:183 - Server does not have 'hypervisors_async' capability
2016-08-19 02:20:03,280 [virtwho.main INFO] MainProcess(15478):MainThread @subscriptionmanager.py:hypervisorCheckIn:194 - Sending update in hosts-to-guests mapping for config "env/cmdline": 1 hypervisors and 2 guests found
2016-08-19 02:20:03,281 [virtwho.main DEBUG] MainProcess(15478):MainThread @subscriptionmanager.py:hypervisorCheckIn:195 - Host-to-guest mapping: {
    "564D900A-2E82-672D-2CB7-C17F0B3FF876": [
        {
            "guestId": "EBBF4A99-85AD-0947-AB31-45DD18FE96E5", 
            "state": 1, 
            "attributes": {
                "active": 1, 
                "virtWhoType": "hyperv"
            }
        }, 
        {
            "guestId": "3A830D1F-AC88-EA45-94D2-9AF69CCEAE6D", 
            "state": 1, 
            "attributes": {
                "active": 1, 
                "virtWhoType": "hyperv"
            }
        }
    ]
}
2016-08-19 02:20:03,873 [virtwho.main DEBUG] MainProcess(15478):MainThread @executor.py:send_report:101 - Report for config "env/cmdline" sent
2016-08-19 02:20:03,875 [virtwho.main DEBUG] MainProcess(15478):MainThread @__main__.py:main:19 - virt-who terminated
2016-08-19 02:20:03,876 [virtwho.main DEBUG] MainProcess(15478):MainThread @executor.py:terminate:303 - virt-who is shutting down

Actual results:
virt-who can report host/guest associations to stage candlepin.

Expected results:
Virt-who shouldn't report host/guest associations to stage candlepin since virt-who run with --sam/--satellite6, it should show some remind info. such as:
"--sam/--satellite6 is not supported on stage candlepin, exiting"

Additional info:

--- Additional comment from Radek Novacek on 2016-08-23 07:23:33 EDT ---

I don't understand why virt-who should threat stage candlepin differently. It uses the same API.

Is there any reason why should virt-who behave differently with stage candlepin?

--- Additional comment from Liushihui on 2016-08-30 02:21:09 EDT ---

Radek, As I noticed that "--satellite6/--sam" option hasn't taken any effect, virt-who can send mapping info to the registered server no matter what server options has been specified in the CLI command. Meanwhile, these two options' functions are different from it on the virt-who man page.

please see the instances as the following:
1. Register to stage candlepin, run virt-who with "--satellite6/--sam", virt-who can send mapping info to stage candlepin.
# virt-who --sam -o -d 
# virt-who --satellite6 -o -d 
2. Register to SAM, run virt-who with "--satellite6/--sam", virt-who can send mapping info to SAM.
# virt-who --sam -o -d 
# virt-who --satellite6 -o -d 
3. Register to Satellite6, run virt-who with "--satellite6/--sam", virt-who can send mapping info to Satellite6.

However, in the virt-who man page ,I notice these two options explanation as the following, There are two differences.
1. It hasn't reminded with "--satellite6/--sam" can reported mapping to stage candlepin. 
2. It hasn't reminded with "--satellite6" can reported to SAM.
# man virt-who
--satellite6 Report host/guest associations to the Satellite 6 server
--sam  Report host/guest associations to the Subscription Asset Manager or Satellite 6 [default]

Therefore, I suggest two types of updating.
1. Update the virt-who man page to make it the same as the actual result
--satellite6 Report host/guest associations to the SAM, Satellite 6 server or Stage Candlepin.
--sam  Report host/guest associations to the SAM,Satellite 6 server or Stage Candlepin.[default]
2. Remove --sam/satellite6 since it hasn't taken any effect.

--- Additional comment from Chris Snyder on 2016-12-22 11:33:42 EST ---

I believe the fix for this is to do one of the following:
1) Remove those options (as the APIs are the same either way)
2) Improve them to be useful.

My preference would be option 1.

Some brief investigation leads me to believe not much (aside from some config validation) is done with those options (--sam/--satellite6).