Bug 1774366
| Summary: | "oc logs --selector k8s-app=machine-config-daemon -n openshift-machine-config-operator -c machine-config-daemon" command returned error message | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | xiyuan |
| Component: | oc | Assignee: | Maciej Szulik <maszulik> |
| Status: | CLOSED ERRATA | QA Contact: | xiyuan |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.3.0 | CC: | aos-bugs, jokerman, josiah.ritchie, mfojtik |
| Target Milestone: | --- | ||
| Target Release: | 4.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
We have an internal code that recognized which resources it's working with and that was missing newer versions of API.
Consequence:
Logs were not working correctly for some resources.
Fix:
Support all known types and versions.
Result:
oc logs is working against any possible resource.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-13 21:53:06 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
xiyuan
2019-11-20 06:58:34 UTC
We should try re-use upstream version instead of maintaining our own version. bug verification passed. $ oc version Client Version: v4.4.0 Server Version: 4.4.0-0.nightly-2020-02-13-212616 Kubernetes Version: v1.17.1 $ oc logs --selector k8s-app=machine-config-daemon -n openshift-machine-config-operator error: a container name must be specified for pod machine-config-daemon-4vpgm, choose one of: [machine-config-daemon oauth-proxy] $ oc logs --selector k8s-app=machine-config-daemon -n openshift-machine-config-operator -c machine-config-daemon I0214 02:38:09.447000 14698 node.go:24] No machineconfiguration.openshift.io/currentConfig annotation on node ip-10-0-71-173.us-east-2.compute.internal: map[volumes.kubernetes.io/controller-managed-attach-detach:true], in cluster bootstrap, loading initial node annotation from /etc/machine-config-daemon/node-annotations.json I0214 02:38:09.447551 14698 node.go:45] Setting initial node config: rendered-master-e30d9150ae84489554e018ca318b7da3 I0214 02:38:09.497297 14698 daemon.go:696] In bootstrap mode I0214 02:38:09.497324 14698 daemon.go:724] Current+desired config: rendered-master-e30d9150ae84489554e018ca318b7da3 I0214 02:38:09.530252 14698 daemon.go:917] No bootstrap pivot required; unlinking bootstrap node annotations I0214 02:38:09.530330 14698 daemon.go:955] Validating against pending config rendered-master-e30d9150ae84489554e018ca318b7da3 I0214 02:38:09.547416 14698 daemon.go:971] Validated on-disk state I0214 02:38:09.570568 14698 daemon.go:1005] Completing pending config rendered-master-e30d9150ae84489554e018ca318b7da3 I0214 02:38:09.570591 14698 update.go:1240] completed update for config rendered-master-e30d9150ae84489554e018ca318b7da3 I0214 02:38:09.581595 14698 daemon.go:1021] In desired config rendered-master-e30d9150ae84489554e018ca318b7da3 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:0581 |