Bug 1538988
Summary: | Need restart master service for non-ha ocp to let the aggregate clusterrole take effective | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Chuan Yu <chuyu> |
Component: | apiserver-auth | Assignee: | Matt Rogers <mrogers> |
Status: | CLOSED ERRATA | QA Contact: | Chuan Yu <chuyu> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.9.0 | CC: | aos-bugs, chuyu, jokerman, mkhan, mmccomas, mrogers, wmeng |
Target Milestone: | --- | ||
Target Release: | 3.9.0 | ||
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: | 2018-03-28 14:23:11 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
Chuan Yu
2018-01-26 10:29:34 UTC
This may be related to https://bugzilla.redhat.com/show_bug.cgi?id=1537426 which should be fixed by https://github.com/openshift/origin/pull/18311 Verified failed. When non-ha OCP cluster upgrade to OCP 3.9.0-0.36.0 from v3.7.27, still need restart master service to let the aggregate clusterrole take effective. > 2.upgrade cluster to OCP3.9, v3.9.0-0.24.0
Does this step restart the master? i.e. a master reboot is _always_ required after an upgrade.
(In reply to Mo from comment #5) > > 2.upgrade cluster to OCP3.9, v3.9.0-0.24.0 > > Does this step restart the master? i.e. a master reboot is _always_ > required after an upgrade. Chuan, can you clarify the exact steps for #2? Matt, the steps is restart master service, atomic-openshift-master-api.service and atomic-openshift-master-controllers.service. Chuan, I meant to ask for details (commands run, verbose outputs, etc.) on the steps you are taking for the whole upgrade process. The upgrade steps that I see in the docs mention that you need to the restart manually, or reboot the master after an automated upgrade, so I don't think the restart is intended to be an integrated part of the upgrade. The master logs throughout the upgrade process will also be helpful here (so pre-, during, and post- logs). 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-2018:0489 |