Web UI: Bug in line order of service log
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Murano |
Fix Released
|
Medium
|
Unassigned |
Bug Description
If a service is present in more then one deployments, its logs have incorrect order of lines (according to timestamps).
*To reproduce:*
1. Create an environment with one service (service_1)
2. Deploy the environment
3. Add another service (service_2)
4. Deploy the environment again
5 Go to service 1 and check the Logs.
*Expected behavior:*
The log contains messages from both deployments in newer-to-older order, like this:
deployement2-
deployement2-
deployement2-
deployement1-
deployement1-
deployement1-
*Actual behavior:*
The log contains messages from both deployments, but the order is mixed: the deployments are correctly grouped in newer-to-older order, but the messages within a deployment are ordered in older-to-newer order, like this:
deployement2-
deployement2-
deployement2-
deployement1-
deployement1-
deployement1-
See attached screenshot
Changed in murano: | |
status: | New → Fix Committed |
Changed in murano: | |
importance: | Undecided → High |
Changed in murano: | |
milestone: | none → 0.2 |
Changed in murano: | |
status: | Fix Committed → Fix Released |
description: | updated |
Changed in murano: | |
importance: | High → Medium |
status: | Fix Released → Fix Committed |
summary: |
- Web UI: Bug in line order of service log + Launchpad Bug #1217369: Web UI: Bug in line order of service log |
summary: |
- Launchpad Bug #1217369: Web UI: Bug in line order of service log + Web UI: Bug in line order of service log |
Changed in murano: | |
status: | Fix Committed → Fix Released |