We haven't seen it in a while, but reporting 'degraded' is a bug
either way, even if we're not seeing any failures. We have to be able
to rely on maas to tell us if it's healthy or not. If the flag doesn't
matter, then get rid of it.
On Thu, Aug 23, 2018 at 8:56 AM Andres Rodriguez
<email address hidden> wrote:
>
> ** Changed in: maas
> Milestone: 2.5.0alpha2 => 2.5.0beta1
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1781241
>
> Title:
> [2.4] rack controller remained in degraded state
>
> Status in MAAS:
> Incomplete
>
> Bug description:
> This is with 2.4.0-6981-g011e51b7a-0ubuntu1~18.04.1.
>
> After an HA deployment, one rack controller (qtmb3d) remained in a
> degraded state for over 20 minutes (the test timed out after that)
> (92% connected).
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1781241/+subscriptions
We haven't seen it in a while, but reporting 'degraded' is a bug /bugs.launchpad .net/bugs/ 1781241 g011e51b7a- 0ubuntu1~ 18.04.1. /bugs.launchpad .net/maas/ +bug/1781241/ +subscriptions
either way, even if we're not seeing any failures. We have to be able
to rely on maas to tell us if it's healthy or not. If the flag doesn't
matter, then get rid of it.
On Thu, Aug 23, 2018 at 8:56 AM Andres Rodriguez
<email address hidden> wrote:
>
> ** Changed in: maas
> Milestone: 2.5.0alpha2 => 2.5.0beta1
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> [2.4] rack controller remained in degraded state
>
> Status in MAAS:
> Incomplete
>
> Bug description:
> This is with 2.4.0-6981-
>
> After an HA deployment, one rack controller (qtmb3d) remained in a
> degraded state for over 20 minutes (the test timed out after that)
> (92% connected).
>
> To manage notifications about this bug go to:
> https:/