Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1388253 - 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.4.0
Unspecified Unspecified
high Severity high
: ---
: ---
Assigned To: Scott Dodson
Johnny Liu
: Regression, TestBlocker
Depends On: 1383015 1416703
Blocks: 1392519
  Show dependency treegraph
 
Reported: 2016-10-24 17:14 EDT by Scott Dodson
Modified: 2017-03-08 13 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: 1383015
: 1392519 (view as bug list)
Environment:
Last Closed: 2017-01-18 07:44:12 EST
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 RHBA-2017:0066 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 12:23:26 EST

  None (edit)
Comment 1 Scott Dodson 2016-10-24 17:15:35 EDT
Cloned to 3.4 because the fix to 3.3.1 was to revert changes that we haven't reverted on master.
Comment 2 Scott Dodson 2016-11-07 16:51:44 EST
WIP - https://github.com/openshift/openshift-ansible/pull/2751
Comment 4 Gan Huang 2016-11-10 00:35:38 EST
Verified with openshift-ansible-3.4.18-1

nodeName is set the same with openshift_hostname which is defined in inventory hosts.
[root@openshift-103 ~]# cat /etc/origin/node/node-config.yaml |grep nodeName
nodeName: openshift-103.lab.sjc.redhat.com

Master and Node running well, and dynamic pvc is created successfully.
Comment 6 errata-xmlrpc 2017-01-18 07:44:12 EST
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-2017:0066

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