| 2023-09-07 18:30:51 |
Peter Mattingly |
description |
> Prepare a concise summary
When attempting to commission an instance multiple times, only the logs of the first commissioning appear normally in the "Logs" screen. A browser refresh is required for the logs to appear.
> Identify your version and build first
The customer is experiencing the issue on MAAS 3.2.8. During testing MAAS 3.2.9 also appeared to be affected.
> Explain whether you’re using the UI, CLI, or API
The UI.
> Explain what happens
The issue was noted when the customer had migrated from MAAS 2.X to MAAS 3.X. In MAAS 2.X logging information would update in nearly real-time. This was useful for monitoring multiple actions applied to an instance (e.g., commissioning, testing, etc.,). However, when updating to MAAS 3.X it was noted that while the logging information for a first commissioning action did show normally in the "Logs" screen, other subsequent information appeared to be missing. After some experimentation it was found that a refresh of the browser was required, thus interrupting the expected updates to logging information and disrupting their workflow.
> Explain how to reproduce your issue
1) Install MAAS 3.2.X (where `X` is 8 or 9)
2) Begin a commissioning action on an instance.
3) Observe the "Logs" screen associated with the instance, and observe the commissioning information.
4) Begin a second commissioning action on the instance, and again observe the "Logs" screen and note that new logging information does not automatically populate.
5) Manually refresh the page, and note that new logging information has appeared related to the second commissioning action.
> Take screenshots, if relevant
See attached.
> Locate and capture logfiles, if at all possible
NA
----
Also note that this issue may be related to this bug found during a review of open bugs: https://bugs.launchpad.net/maas/+bug/1840058. There may be some sort of invisible timeout associated with populating new information? But this is unclear, as during testing waiting times for new information to appear exceeded 60 seconds.
Then also, this bug is associated with case 00364439. |
> Prepare a concise summary
When attempting to commission an instance multiple times, only the logs of the first commissioning appear normally in the "Logs" screen. A browser refresh is required for the logs to appear.
> Identify your version and build first
The customer is experiencing the issue on MAAS 3.2.8. During testing MAAS 3.2.9 also appeared to be affected.
> Explain whether you’re using the UI, CLI, or API
The UI.
> Explain what happens
The issue was noted when the customer had migrated from MAAS 2.X to MAAS 3.X. In MAAS 2.X logging information would update in nearly real-time. This was useful for monitoring multiple actions applied to an instance (e.g., commissioning, testing, etc.,). However, when updating to MAAS 3.X it was noted that while the logging information for a first commissioning action did show normally in the "Logs" screen, other subsequent information appeared to be missing. After some experimentation it was found that a refresh of the browser was required, thus interrupting the expected updates to logging information and disrupting their workflow.
> Explain how to reproduce your issue
1) Install MAAS 3.2.X (where `X` is 8 or 9)
2) Begin a commissioning action on an instance.
3) Observe the "Logs" screen associated with the instance, and observe the commissioning information.
4) Begin a second commissioning action on the instance, and again observe the "Logs" screen and note that new logging information does not automatically populate.
5) Manually refresh the page, and note that new logging information has appeared related to the second commissioning action.
> Take screenshots, if relevant
See attached.
> Locate and capture logfiles, if at all possible
NA
----
Also note that this issue may be related to this bug found during a review of open bugs: https://bugs.launchpad.net/maas/+bug/1840058. There may be some sort of invisible timeout associated with populating new information? But this is unclear, as during testing waiting times for new information to appear exceeded 60 seconds. |
|
