Bug 1362289
| Summary: | [DOCS] Ansible Upgrade Scripts don't account for DNS changes. | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Eric Rich <erich> | |
| Component: | Documentation | Assignee: | Alex Dellapenta <adellape> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Eric Rich <erich> | |
| Severity: | high | Docs Contact: | Vikram Goyal <vigoyal> | |
| Priority: | high | |||
| Version: | 3.2.1 | CC: | adellape, anli, aos-bugs, jokerman, mmccomas, rhowe, sdodson, xtian | |
| 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: | ||||
| : | 1362290 1372452 (view as bug list) | Environment: | ||
| Last Closed: | 2016-09-01 18:39:00 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: | ||||
| Bug Blocks: | 1362290, 1372452 | |||
|
Description
Eric Rich
2016-08-01 20:13:40 UTC
https://github.com/openshift/openshift-ansible/blob/enterprise-3.2/playbooks/byo/openshift-cluster/enable_dnsmasq.yml Is likely one option to solve this. (In reply to Eric Rich from comment #0) > Description of problem: > Version-Release number of selected component (if applicable): 3.2 -> 3.2 ^ Think this is a typo of "3.1 -> 3.2". Scott, do you know whether this playbook is appropriate (and has been QE'd) for running on 3.1 -> 3.2 upgraded hosts? Or would it need a separate upgrade playbook? That playbook should work, we'd need QE to validate it as that wasn't part of the original work. What's the best way to ask them to test something that's already done? A new card for that specific functionality? (In reply to Scott Dodson from comment #3) > That playbook should work, we'd need QE to validate it as that wasn't part > of the original work. What's the best way to ask them to test something > that's already done? A new card for that specific functionality? Usually it's a new card, you can describe the detail in the card and move it complete if it's just waiting for QE to test. Or bug is also fine for QE. PR for explaining that the DNS changes for 3.2 only happen for new installs (and not upgrades): https://github.com/openshift/openshift-docs/pull/2693 Commit pushed to master at https://github.com/openshift/openshift-docs https://github.com/openshift/openshift-docs/commit/9629b304305a439f3f1dbb42eb120bdf702e4988 Merge pull request #2693 from adellape/dnsmasq_edit Bug 1362289: Note re DNS changes for 3.2 upgrades Changes from https://github.com/openshift/openshift-docs/pull/2693 are RELEASE_PENDING, but I'm leaving this BZ open until we can document the manual and/or automated steps for applying the 3.2 DNS changes to a cluster that was upgraded from 3.1. Cloned this BZ to https://bugzilla.redhat.com/show_bug.cgi?id=1372452 to complete the remaining steps. Closing this BZ. See revhistory here for the changes that were published from this BZ: https://docs.openshift.com/enterprise/latest/welcome/revhistory_full.html#tue-aug-23-2016 |