Bug 1375946
Summary: | [quick install]docker registry and router can not be deployed for failedScheduling | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | liujia <jiajliu> |
Component: | Installer | Assignee: | Samuel Munilla <smunilla> |
Status: | CLOSED ERRATA | QA Contact: | liujia <jiajliu> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.3.0 | CC: | anli, aos-bugs, bleanhar, jiajliu, jokerman, mmccomas |
Target Milestone: | --- | ||
Target Release: | 3.3.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, the quick installer could have labeled unschedulable nodes as infra nodes. This would prevent the registry and router from deploying as the nodes were unschedulable. The quick installer has been updated to only assign the infra label to schedulable nodes ensuring that the registry and router and deployed properly.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-10-27 16:13:29 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
liujia
2016-09-14 10:09:03 UTC
Hi Liu Jia, Would you mind attaching the quick install configuration that you used? Commit pushed to master at https://github.com/openshift/openshift-ansible https://github.com/openshift/openshift-ansible/commit/522a069d21b6557821bd85aa77ecfee43cf7c549 a-o-i: Don't set unschedulable nodes as infra Make sure we don't set an unschedulable node as infra as that can cause problems. Fixes: Bug 1375946 blocked verify by bug 1382885 and bug 1383004 worked around bug 1382885 and still blocked by bug 1383004 Version: atomic-openshift-utils-3.3.37-1.git.0.10ff25b.el7.noarch ansible-2.2.0.0-0.62.rc1.el7.noarch Steps: 1.Trigger a installation by quick-installer in HA env run "atomic-openshift-installer install" 2.It will generate inventory file with schedulable node labeled as follows: [nodes] openshift-x.x.x.x openshift_public_ip=x.x.x.x openshift_ip=192.168.2.164 openshift_public_hostname=x.x.x.x openshift_hostname=192.168.2.164 connect_to=openshift-x.x.x.x openshift_schedulable=False openshift-x.x.x.x openshift_public_ip=x.x.x.x openshift_ip=192.168.2.183 openshift_public_hostname=x.x.x.x openshift_hostname=192.168.2.183 connect_to=x.x.x.x openshift_schedulable=False openshift-x.x.x.x openshift_public_ip=x.x.x.x openshift_ip=192.168.2.184 openshift_public_hostname=x.x.x.x openshift_hostname=192.168.2.184 connect_to=x.x.x.x openshift_schedulable=False openshift-x.x.x.x openshift_public_ip=x.x.x.x openshift_ip=192.168.2.185 openshift_public_hostname=x.x.x.x openshift_hostname=192.168.2.185 connect_to=x.x.x.x openshift_node_labels="{'region': 'infra'}" openshift_schedulable=True Result: After installation complete, checked only node-192.168.2.185 is schedulable and it will be labeled with "{'region': 'infra'}". # oc get node NAME STATUS AGE 192.168.2.164 Ready,SchedulingDisabled 34m 192.168.2.183 Ready,SchedulingDisabled 34m 192.168.2.184 Ready,SchedulingDisabled 34m 192.168.2.185 Ready 34m And docker registry and router container will be scheduled to 192.168.2.185 which is labeled "{'region': 'infra'}". 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-2016:2122 |