Bug 1421867
| Summary: | rpm-ostree daemon does not start when system is unsubscribed | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Micah Abbott <miabbott> |
| Component: | rpm-ostree-client | Assignee: | Colin Walters <walters> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | CC: | lfriedma, mjenner |
| Target Milestone: | rc | Keywords: | Extras |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-02 22:39:44 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: | |||
|
Description
Micah Abbott
2017-02-13 22:16:05 UTC
$ rpm -q rpm-ostree-client ostree rpm-ostree-client-2017.1-3.atomic.el7.x86_64 ostree-2017.1-2.atomic.el7.x86_64 Ug. Yes, this is likely to be due to changes in the daemon for parsing the sysroot state. Two things to improve: - The autobrew stream being broken for ENOSPC for a while and us not consistently watching the results - Upstream tests don't currently have coverage of this special unsubscribed state I'll work on this tonight. (In reply to Colin Walters from comment #4) > Two things to improve: > > - The autobrew stream being broken for ENOSPC for a while and us not > consistently watching the results Agreed. Need a better way of getting nagged when the builds fail. > - Upstream tests don't currently have coverage of this special unsubscribed > state https://trello.com/c/6o9me2xB/654-3-add-test-for-running-rpm-ostreed-on-unsubscribed-system This is fixed with rpm-ostree-client-2017.1-6.atomic.el7.x86_64 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/RHSA-2017:0444 |