Inconsistent dnspython imports break zone import/export in production
Bug #1248247 reported by
Artom Lifshitz
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Designate |
Fix Released
|
Medium
|
Artom Lifshitz | ||
| Icehouse |
Fix Released
|
Medium
|
Artom Lifshitz | ||
Bug Description
The zones.py controller imports dnspython with 'import dns', then uses it as 'dns.zone.blah'. This works in unit tests, but does not work in production deployments.
The cause looks to be as follows.
It seems that because the test_zones.py unit tests import dnspython with 'from dns import zone as dnszone', dns.zone becomes usable, whereas it shouldn't be if simply 'import dns' was used.
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to designate (master) | #1 |
| Changed in designate: | |
| assignee: | nobody → Artom Lifshitz (artom-lifshitz) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to designate (master) | #2 |
| Changed in designate: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/