DHCP activation behaves differently between browsers

[dann frazier]

MAAS 2.0b8.

We noticed that DHCP activation behaves differently between browsers:
  https://youtu.be/SZv7KWdka10

When the video starts, Michael is sharing his Firefox browser with me via hangouts. You can see that when he activates DHCP, he is asked to provide a range.

Next, I show my chrome window, connected to the same MAAS server as the same user. When I activate DHCP, I am only asked for confirmation.

Michael later tried chromium on his end, and he also did not see the range prompt. I tried Firefox on my end, and I did not see the range prompt either, so there's something more to it than just Firefox vs. Chrome.

[Andres Rodriguez (andreserl)]

Hi Dann,

First, and foremost, RC2 is out and available already that should fix any remaining UI issues.

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.

We know this is not ideal UX< but this is a problem that UX needs to fix so we can fix. This is being tracked separately.

Thanks

[dann frazier (dannf)]

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?

[dann frazier (dannf)]

Moving from Invalid->New since I'm not sure the problem I was reporting was clear - I've clarified that in Comment #2.

[Andres Rodriguez (andreserl)]

We believe that this issue is no longer present on the latest version of MAAS. Please update to the latest version and if you believe this issue still persists, please re-open this bug report or file a new bug report.