Issue 371 in roster-dns-management: dnslszone reverse --origin for a zone that does not exist raises KeyError

[roster-dns...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 371 by Cooke...@gmail.com: dnslszone reverse --origin for a zone
that does not exist raises KeyError
http://code.google.com/p/roster-dns-management/issues/detail?id=371

If you execute dnslszone reverse --origin=origin_value where the
origin_value does not belong to an existing view, the tool will raise a
KeyError. This has not been tested on dnslszone forward
--origin=origin_value yet.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[roster-dns...@googlecode.com]

Comment #1 on issue 371 by Cooke...@gmail.com: dnslszone reverse --origin

for a zone that does not exist raises KeyError
http://code.google.com/p/roster-dns-management/issues/detail?id=371

Correction: this occurs where the origin_value does not belong to an
existing reverse zone.

Also, I have discovered that this error will also be thrown if there are
more than 1 reverse zones with different zone origins.

[roster-dns...@googlecode.com]

Updates:
Owner: Cooke...@gmail.com

Comment #2 on issue 371 by Cooke...@gmail.com: dnslszone reverse --origin

for a zone that does not exist raises KeyError
http://code.google.com/p/roster-dns-management/issues/detail?id=371

(No comment was entered for this change.)

[roster-dns...@googlecode.com]

Updates:
Owner: ---

Comment #3 on issue 371 by Cooke...@gmail.com: dnslszone reverse --origin