Bug 1202511
| Summary: | oo-admin-repair does not fix stale env vars in domains with no apps | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Brenton Leanhardt <bleanhar> |
| Component: | Node | Assignee: | Brenton Leanhardt <bleanhar> |
| Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.2.0 | CC: | abhgupta, adellape, agrimm, jhou, jokerman, libra-bugs, libra-onpremise-devel, mmccomas, pruan, qizhao, xiama |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rubygem-openshift-origin-controller-1.35.1.1-1.el6op | Doc Type: | Bug Fix |
| Doc Text: |
When checking for stale SSH keys and environment variables to repair, previously the oo-admin-repair tool on brokers did not check in user domains where there were no existing applications. This bug fix updates this logic so that domains without existing applications are now also checked, and as a result all stale SSH keys and environment variables are repaired as expected.
|
Story Points: | --- |
| Clone Of: | 1183048 | Environment: | |
| Last Closed: | 2015-04-06 17:06:46 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: | |||
| Bug Depends On: | 1183048 | ||
| Bug Blocks: | |||
|
Description
Brenton Leanhardt
2015-03-16 18:58:15 UTC
Check on puddle[2.2.z/2015-03-16.2] 1. Create a jenkins app #rhc app create jenkins jenkins 2. Delete the jenkins app from mongo >db.applications.remove({"canonical_name":"jenkins"}) > db.domains.findOne({"namespace":"123"}) { "_allowed_domains" : null, "_id" : ObjectId("5507cc46e5fed5adf90000b0"), "_type" : "Domain", "allowed_gear_sizes" : [ "small", "medium" ], "canonical_namespace" : "123", "created_at" : ISODate("2015-03-17T06:40:06.836Z"), "env_vars" : [ { "key" : "JENKINS_URL", "value" : "https://jenkins-123.ose22-manual.com.cn/", "component_id" : ObjectId("5507f437e5fed55c720001d8"), "unique" : false }, { "key" : "JENKINS_USERNAME", "value" : "system_builder", "component_id" : ObjectId("5507f437e5fed55c720001d8"), "unique" : false }, { "key" : "JENKINS_PASSWORD", "value" : "C_YErE1f2nAm", "component_id" : ObjectId("5507f437e5fed55c720001d8"), "unique" : false } Some stale env exists in domain 3.fix the issue # oo-admin-repair --ssh-keys Started at: 2015-03-17 09:34:32 UTC Total gears found in mongo: 6 Gear '123-php3-1' has a stale key 'domain-jenkins' in mongo with missing component/gear '5507f437e5fed55c720001d8'. Gear '123-php3-1' has a stale environment variable 'JENKINS_URL' in mongo with missing component/gear '5507f437e5fed55c720001d8'. Gear '123-php3-1' has a stale environment variable 'JENKINS_USERNAME' in mongo with missing component/gear '5507f437e5fed55c720001d8'. Gear '123-php3-1' has a stale environment variable 'JENKINS_PASSWORD' in mongo with missing component/gear '5507f437e5fed55c720001d8'. Finished at: 2015-03-17 09:34:53 UTC Total time: 21.336s SUCCESS 4.Check the env in the domain > db.domains.findOne({"namespace":"123"}) { "_allowed_domains" : null, "_id" : ObjectId("5507cc46e5fed5adf90000b0"), "_type" : "Domain", "allowed_gear_sizes" : [ "small", "medium" ], "canonical_namespace" : "123", "created_at" : ISODate("2015-03-17T06:40:06.836Z"), "env_vars" : [ ], "members" : [ { "_type" : "Member", "_id" : ObjectId("55078fa3e5fed55c7200002b"), "t" : null, "n" : "gpei", "r" : "admin", "f" : [ [ "owner", "admin" ] ], "e" : null } ], "namespace" : "123", "owner_id" : ObjectId("55078fa3e5fed55c7200002b"), "pending_ops" : [ ], "system_ssh_keys" : [ ], "updated_at" : ISODate("2015-03-17T06:40:06.836Z") } the env and sshkey in the domain are deleted. 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://rhn.redhat.com/errata/RHBA-2015-0779.html |