Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1519129 - Node shows notready state after reboot
Summary: Node shows notready state after reboot
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Dan Williams
QA Contact: Meng Bo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-30 08:26 UTC by Jaspreet Kaur
Modified: 2018-01-19 14:34 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-19 14:33:45 UTC


Attachments (Terms of Use)

Description Jaspreet Kaur 2017-11-30 08:26:07 UTC
Description of problem: when a node or master is rebooted, it should ideally comeup without any issues however it shows NotReady status everytime after reboot.

Below errors are seen :



Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
ansible --version

How reproducible:

Steps to Reproduce:
1.
2.Please attach logs from ansible-playbook with the -vvv flag
3.

Actual results: Node is shown as NotReady

Expected results: Should come up without issues.

Additional info:
Restarting the node manually helps.

Comment 2 Scott Dodson 2017-11-30 14:54:12 UTC
In order to debug this please provide `journalctl -b 0 --no-pager` from a node that failed to become ready after a reboot.

Comment 18 Ben Bennett 2018-01-19 14:33:45 UTC
Seems the needed information was:
  It seems currently, the nodeName must match the instance name in AWS in order for the cloud provider integration to work properly. The name must also be RFC1123 compliant.

The attached cases were closed.


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