Comment 2 for bug 1603509
Revision history for this message
| dann frazier (dannf) wrote Re: [Bug 1603509] Re: DHCP activation behaves differently between browsers | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
On Fri, Jul 15, 2016 at 11:26 AM, Andres Rodriguez
<email address hidden> wrote:
> Hi Dann,
>
> First, and foremost, RC2 is out and available already that should fix
> any remaining UI issues.
Right, I'm aware RC2 is out now, but it wasn't when we froze this
recipe that is now in QA. We can retest w/ RC2 (or whatever is the
latest then) once this QA is complete.
> Second, the action behaves differently because:
> 1. If you are not shown the ability to define a range is because you already have a Dynamic range created.
> 2. If it is asking you to create a range, it means you dont previously have a dynamic range created.
That makes sense - but I think it is orthogonal to the issue here.
Both of these browsers are pointed at the same MAAS instance (which
does happen to have a dynamic range defined). Nothing is happening
behind the scenes. Why does one prompt for the range and the other
not? Is Michael's firefox instance possibly caching something that
leads the UI to think there is no dynamic range defined?