Bug 1679782
Summary: | Inaccurate message when ssh into rhcos host | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Derek Carr <decarr> |
Component: | RHCOS | Assignee: | Steve Milner <smilner> |
Status: | CLOSED ERRATA | QA Contact: | Micah Abbott <miabbott> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.0 | CC: | bbreard, dustymabe, imcleod, jerzhang, jligon, nstielau |
Target Milestone: | --- | ||
Target Release: | 4.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-04 10:44:19 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
Derek Carr
2019-02-21 20:42:26 UTC
Tested with 47.327 ``` [bound] -bash-4.2$ ssh localhost <snip /> WARNING: Direct SSH access to machines is not recommended. This node has been annotated with machineconfiguration.openshift.io/ssh=accessed ``` I think the version you may have is pre the bugfix which fixed the message. Jerry can you confirm? Yes, the version with the fix is 47.323 The message was regressed briefly due to us switching around branches in our pipeline. This is fixed for versions 47.323 and later. Verified using 47.324 $ rpm-ostree status State: idle AutomaticUpdates: disabled Deployments: ● pivot://registry.svc.ci.openshift.org/rhcos/maipo@sha256:26dc9b8c8f65b1a76abe1614688f8dfa0eb42e861df019aa9825f8f12d62c43e CustomOrigin: Provisioned from oscontainer Version: 47.324 (2019-02-20T17:18:30Z) $ cat /etc/motd Red Hat CoreOS 4.0 Beta WARNING: Direct SSH access to machines is not recommended. This node has been annotated with machineconfiguration.openshift.io/ssh=accessed --- 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-2019:0758 |