Bug 1702239

I wasn't able to reproduce this issue.  Let me get a little more information from you.

* I was running my test on Centos7.  What distro were you using?
* Is that the full stack trace?  It looks like it but it seems curious that it doesn't reference any lines from subscription-manager
* Since the stacktrace is referencing the logging library, can you paste the last few lines of log output?  Maybe that would help narrow down the search space.

Hi Al,
I'm sorry. I missed the important information in bug report. I'm able to reproduce the bug, when the system is NOT registered. I'm not able to reproduce the bug, when system is registered.

* I was using CentOS 7 distro too.
* The stack trace is full. It is really strange that there is no reference from subscription-manager.
* There is log (rhsm.log) output:

2019-05-03 07:22:35,495 [DEBUG] syspurpose:4370:MainThread @cli.py:296 - Running the syspurpose utility...
2019-05-03 07:22:35,505 [DEBUG] syspurpose:4370:MainThread @identity.py:138 - Loading consumer info from identity certificates.
2019-05-03 07:22:35,506 [DEBUG] syspurpose:4370:MainThread @connection.py:924 - Connection built: host=svice port=8443 handler=/candlepin auth=identity_cert ca_dir=/etc/rhsm/ca/ insecure=True
2019-05-03 07:22:35,507 [DEBUG] syspurpose:4370:MainThread @files.py:319 - Successfully read local syspurpose contents.
2019-05-03 07:22:35,507 [DEBUG] syspurpose:4370:MainThread @files.py:356 - Successfully read cached syspurpose contents.
2019-05-03 07:22:35,507 [DEBUG] syspurpose:4370:MainThread @files.py:273 - Attempting to sync syspurpose content...
2019-05-03 07:22:35,508 [DEBUG] syspurpose:4370:MainThread @connection.py:591 - Making request: GET /candlepin/status
2019-05-03 07:22:35,520 [DEBUG] syspurpose:4370:MainThread @connection.py:638 - Response: status=200, requestUuid=695b6015-05a1-4e70-8751-cd3eddc6c5d8, request="GET /candlepin/status"
2019-05-03 07:22:35,521 [DEBUG] syspurpose:4370:MainThread @connection.py:977 - Server has the following capabilities: [u'instance_multiplier', u'derived_product', u'vcpu', u'cert_v3', u'remove_by_pool_id', u'syspurpose', u'storage_band', u'cores', u'hypervisors_async', u'org_level_content_access', u'guest_limit', u'ram', u'batch_bind']
2019-05-03 07:22:35,522 [DEBUG] syspurpose:4370:MainThread @files.py:334 - Failed to read remote syspurpose from server: no available connection, or the consumer is not registered.
2019-05-03 07:22:35,526 [DEBUG] syspurpose:4370:MainThread @files.py:552 - Attempting a three-way merge...
2019-05-03 07:22:35,527 [DEBUG] syspurpose:4370:MainThread @files.py:373 - Failed to update remote syspurpose on the server: no available connection, or the consumer is not registered.
2019-05-03 07:22:35,533 [DEBUG] syspurpose:4370:MainThread @files.py:506 - Successfully updated syspurpose values at '/etc/rhsm/syspurpose/syspurpose.json'.
2019-05-03 07:22:35,537 [DEBUG] syspurpose:4370:MainThread @files.py:506 - Successfully updated syspurpose values at '/var/lib/rhsm/cache/syspurpose.json'.
2019-05-03 07:22:35,538 [DEBUG] syspurpose:4370:MainThread @files.py:296 - Successfully synced system purpose.

I forgot to mention the last important detail. The option default_log_level has to be set to "DEBUG" in rhsm.conf.

Reproducer:

[root@kvm-01-guest10 ~]# subscription-manager version
server type: This system is currently not registered.
subscription management server: 2.3.17-1
subscription management rules: 5.35
subscription-manager: 1.25.1-1.git.78.8ae61ee.el7


[root@kvm-01-guest10 ~]# LANG=cs_CZ.utf8 syspurpose show
Traceback (most recent call last):
  File "/usr/lib64/python2.7/logging/__init__.py", line 851, in emit
    msg = self.format(record)
  File "/usr/lib64/python2.7/logging/__init__.py", line 724, in format
    return fmt.format(record)
  File "/usr/lib64/python2.7/logging/__init__.py", line 467, in format
    s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 105: ordinal not in range(128)
Logged from file identity.py, line 149

This was added by mistake to the errata. The latest build of subscription-manager does not include this bug fix. Moving back to POST (as the fix has been completed upstream but not downstream).

reproducer:

[root@hpe-dl360egen8-01 ~]# subscription-manager version
server type: This system is currently not registered.
subscription management server: 2.7.5-1
subscription management rules: 5.37
subscription-manager: 1.24.13-1.el7


[root@hpe-dl360egen8-01 ~]# syspurpose set-usage foo
usage set to foo
Unable to send system purpose to subscription management server
[root@hpe-dl360egen8-01 ~]# vi /etc/rhsm/rhsm.conf 
[root@hpe-dl360egen8-01 ~]# export LANG=cs_CZ.utf8
[root@hpe-dl360egen8-01 ~]# syspurpose show
Traceback (most recent call last):
  File "/usr/lib64/python2.7/logging/__init__.py", line 851, in emit
    msg = self.format(record)
  File "/usr/lib64/python2.7/logging/__init__.py", line 724, in format
    return fmt.format(record)
  File "/usr/lib64/python2.7/logging/__init__.py", line 467, in format
    s = self._fmt % record.__dict__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 105: ordinal not in range(128)
Logged from file identity.py, line 149

{
  "usage": "foo"
}
Unable to send system purpose to subscription management server

[root@hpe-dl360gen8-01 ~]# subscription-manager version
server type: This system is currently not registered.
subscription management server: 2.7.5-1
subscription management rules: 5.37
subscription-manager: 1.24.17-1.el7


Verification:

[root@hpe-dl360gen8-01 ~]# subscription-manager unregister
Unregistering from: subscription.rhsm.stage.redhat.com:443/subscription
System has been unregistered.


[root@hpe-dl360gen8-01 ~]# cat /etc/rhsm/rhsm.conf | grep log
[logging]
default_log_level = DEBUG


[root@hpe-dl360gen8-01 ~]# export LANG=cs_CZ.utf8
[root@hpe-dl360gen8-01 ~]# syspurpose show
{
  "role": "dsadsa"
}

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-2020:1028