Bug 1498643
| Summary: | Master controller service failed to start during installation | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Vikas Laad <vlaad> |
| Component: | Installer | Assignee: | Scott Dodson <sdodson> |
| Status: | CLOSED DUPLICATE | QA Contact: | Johnny Liu <jialiu> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.7.0 | CC: | aos-bugs, jokerman, mifiedle, mmccomas, rrati |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-10-05 20:19:47 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
Vikas Laad
2017-10-04 20:23:28 UTC
We don't manage the instances and the instances need to be labeled prior to running the installer. Rob, Just to clarify, if the instance is not tagged with the appropriate label there's no configuration file for either master or node that would label the instance correctly? The stance we took is that we'd rely on the master looking up the correct metadata as that's the most important bit and adding this to a configuration file on the instance is just another config file value that needs to be kept in sync. -- Scott Correct. The master will not label nodes under any circumstances. It also doesn't store that label information anywhere. On startup the master looks on its instance for one of 2 specific labels, and if it finds one then it uses the value of that label. If it doesn't find the label (there's an old and new method) then the controllers process will exit or print a warning in its log file depending on command line options. Ok, I think ansible can gather the tags from the metadata API. I think what we'll do is query that API for all node and master hosts. If a node or master host has the AWS cloud provider configured and they don't have a tag named "kubernetes.io/cluster/xxxx" we'll block the upgrade and install on 3.7 with a message that links to documentation. We need to get that documentation ready that explains both how to properly label new installations and how to retroactively label existing installations. We'll do that in https://bugzilla.redhat.com/show_bug.cgi?id=1498643 *** This bug has been marked as a duplicate of bug 1491399 *** |