Bug 1445204
| Summary: | 'Next System Certificate Check' and 'Next System Auto Attach' in About window are not accurate. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | qianzhan | ||||||
| Component: | subscription-manager | Assignee: | Jiri Hnidek <jhnidek> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | John Sefler <jsefler> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 7.4 | CC: | csnyder, jhnidek, jstavel, redakkan, skallesh | ||||||
| Target Milestone: | rc | Keywords: | Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | subscription-manager-1.19.13-1 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-08-01 19:23:41 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
qianzhan
2017-04-25 09:08:43 UTC
Created attachment 1273862 [details]
Next_checks_time_is_not_right.png
Agreed! I can also reproduce this failure (testing with rhsmcertd.splay=0). I suspect these errors which are written to rhsm.log at exactly the time of the first check-in are blocking rhsmcertd-worker from writing new /var/run/rhsm/next_* files. 2017-04-25 14:42:52,499 [WARNING] rhsmcertd-worker:23859:MainThread @dmiinfo.py:86 - Error reading system DMI information: coercing to Unicode: need string or buffer, NoneType found 2017-04-25 14:42:52,618 [WARNING] rhsmcertd-worker:23859:MainThread @dmiinfo.py:86 - Error reading system DMI information: coercing to Unicode: need string or buffer, NoneType found [root@jsefler-rhel7 ~]# ls -l /var/run/rhsm/* -rw-r--r--. 1 root root 10 Apr 25 14:40 /var/run/rhsm/next_auto_attach_update -rw-r--r--. 1 root root 10 Apr 25 14:40 /var/run/rhsm/next_cert_check_update Notice that the timestamp of the /var/run/rhsm/next_* files remains unchanged from the time rhsmcertd is restarted and the hard 2 minute wait begins. This bug might be a consequence of Bug 1444714. Additional Info: This bug is reproducible with both selinux Enforcing and Permissive. I can confirm this failure too. John, why do you think this bug might be a consequence of https://bugzilla.redhat.com/show_bug.cgi?id=1444714 ? This bug was addressed in this PR: https://github.com/candlepin/subscription-manager/pull/1607. BTW: This bug fix is already present in subscription-manager-1.19.10-1. (In reply to Jiri Hnidek from comment #4) > John, why do you think this bug might be a consequence of > https://bugzilla.redhat.com/show_bug.cgi?id=1444714 ? I changed my mind. I do not think this bug is a consequence of bug 1444714. Instead... I think this bug depends on the fix for selinux-policy Bug 1445494. Will verify this bug when next RHEL7.4 build comes out. Created attachment 1279961 [details]
No mismatch in next system update
[root@dhcp71-112 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.9.51.23-1
subscription management rules: 5.15.1
subscription-manager: 1.19.14-1.el7
python-rhsm: 1.19.6-1.el7
marking bug as verified as I dont see any mismatch between rhsmcertd log and next system check values in the about window of gui 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:2083 |