RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1666829 - [machines] yellow popup error box shows old messages
Summary: [machines] yellow popup error box shows old messages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cockpit-appstream
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: 8.4
Assignee: Katerina Koukiou
QA Contact: Xianghua Chen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-16 16:57 UTC by Bimal Chollera
Modified: 2021-05-18 15:53 UTC (History)
6 users (show)

Fixed In Version: 233.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 15:53:08 UTC
Type: Bug
Target Upstream Version:
Embargoed:
kkoukiou: needinfo+
kkoukiou: needinfo+

Attachments (Terms of Use)

Description Bimal Chollera 2019-01-16 16:57:16 UTC 
Description of problem:

Add timestamp on the 'yellow' popup error box.
This way you can know if it new or old message.

Version-Release number of selected component (if applicable):

cockpit-system-184-1.el8.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Martin Pitt 2019-02-05 07:48:30 UTC 
Can you please be more specific which error box you mean? Maybe do a screenshot?
Comment 2 Martin Pitt 2019-03-11 10:56:32 UTC 
Bimal, ping?
Comment 4 Martin Pitt 2019-03-13 10:22:15 UTC 
Thanks Roman, that helps. Indeed this error message is confusing in this case. But instead of showing a timestamp, I propose to just remove it after re-clicking the action (such as "Start" or "Install").
Comment 6 Martin Pitt 2020-03-10 07:44:20 UTC 
I believe this behaviour didn't change, but I'll let Katerina give the definitive answer.
Comment 7 Xianghua Chen 2020-04-15 07:20:34 UTC 
Any update on it, katerina?
Comment 9 Katerina Koukiou 2020-11-19 11:31:02 UTC 
This behavior changed in release 232. Since this release, notifications will appear inline with vms rows, next to the state string, wrapped inside a popover. When a VM will get two errors caused by lifecycle operations, the second will overwrite the first one, so there is not confusion any more about which came first.
Comment 10 Xianghua Chen 2020-12-03 03:17:14 UTC 
Pre verified with:
cockpit-machines-233.1-1.el8.noarch

Steps:
1. Prepare a VM, keep it shut down
2. Deactivate the network, click Run 
There will be an icon and error occur at the State part with "Failed view more", then click "view more" you can see an error box pop up with details:
VM cirros failed to start
Requested operation is not valid: network 'default' is not active
3. Active the network, and rename the source image like:
# mv cirros1.qcow2 cirros.qcow2
4. Click Run again ,same icon and error as in step 2, but click "view more", you can see the new error message is showing failure caused by "No such file or directory"
5. Fresh the page, the error message is gone.
6. Enter the vm sub-page, and repeat step 2-5, the error message shows correctly.

So set as verify:tested.
Comment 13 Xianghua Chen 2020-12-14 06:28:04 UTC 
Verified with:
cockpit-224.2-1.el8.x86_64
cockpit-machines-233.1-1.el8.noarch
libvirt-dbus-1.3.0-2.module+el8.3.0+6423+e4cb6418.x86_64

Steps:
1. Prepare a VM, keep it shut down
2. Deactivate the network, click Run 
There will be an icon and error occur at the State part with "Failed view more", then click "view more" you can see an error box pop up with details:
VM cirros failed to start
Requested operation is not valid: network 'default' is not active
3. Active the network, and rename the source image like:
# mv cirros1.qcow2 cirros.qcow2
4. Click Run again ,same icon and error as in step 2, but click "view more", you can see the new error message is showing failure caused by "No such file or directory"
5. Fresh the page, the error message is gone.
6. Enter the vm sub-page, and repeat step 2-5, the error message shows correctly.

So verified.
Comment 15 errata-xmlrpc 2021-05-18 15:53:08 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (cockpit-appstream bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1875
Note You need to log in before you can comment on or make changes to this bug.