Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1392519 - oc rsh and logs command failed when openstack cloudprovider is enabled but nodeName gotten from openstack metadata is not resolvable.
oc rsh and logs command failed when openstack cloudprovider is enabled but no...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
3.6.0
Unspecified Unspecified
urgent Severity high
: ---
: ---
Assigned To: Scott Dodson
Johnny Liu
: Regression, TestBlocker
Depends On: 1383015 1388253 1416703
Blocks:
  Show dependency treegraph
 
Reported: 2016-11-07 11:33 EST by Scott Dodson
Modified: 2017-08-10 01:15 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1388253
Environment:
Last Closed: 2017-08-10 01:15:47 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1716 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.6 RPM Release Advisory 2017-08-10 05:02:50 EDT

  None (edit)
Comment 3 Wenkai Shi 2017-04-21 04:50:48 EDT
Change Priority to urgent because it block testing for Integrate GlusterFS storage.
Comment 6 Johnny Liu 2017-06-09 05:31:25 EDT
Verified this bug with openshift-ansible-3.6.98-1.git.0.e651d65.el7.noarch, and PASS.

Change instance name, set openshift_hostname for each node, and make sure they have the same value, trigger installation, succeed.

#  grep nodeName /etc/origin/node/node-config.yaml 
nodeName: <hostname>
Comment 8 errata-xmlrpc 2017-08-10 01:15:47 EDT
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/RHEA-2017:1716

Note You need to log in before you can comment on or make changes to this bug.