Bug 2011335
| Summary: | [Machines] Oops in VM's "Network Interface": TypeError: Cannot read properties of undefined (reading 'name') | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Ulhas Surse <usurse> |
| Component: | cockpit-appstream | Assignee: | Simon Kobyda <skobyda> |
| Status: | CLOSED MIGRATED | QA Contact: | Xianghua Chen <xchen> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.4 | CC: | kkoukiou, mmarusak, sbarcomb, yunyang |
| Target Milestone: | rc | Keywords: | MigratedToJIRA |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-15 12:56:14 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Ulhas Surse
2021-10-06 12:57:16 UTC
Hello Ulhas, I am afraid this is too vague for investigating. Can you please - describe exactly what you did - make a screenshot right before you press the action button that causes the crash, and attach the screenshot here, and open the developer console (Ctrl+Shift+J) - after the oops happens: please copy all output from the developer console here; if you still see anything more interesting than a blank page, please add another screenshot. Which browser are you using? Which RHEL version and architecture? Thanks! (In reply to Martin Pitt from comment #3) > Hello Ulhas, > > I am afraid this is too vague for investigating. Can you please > > - describe exactly what you did > - make a screenshot right before you press the action button that causes > the crash, and attach the screenshot here, and open the developer console > (Ctrl+Shift+J) > - after the oops happens: please copy all output from the developer console > here; if you still see anything more interesting than a blank page, please > add another screenshot. > > Which browser are you using? Which RHEL version and architecture? > > Thanks! Hi Martin, The server I was testing crashed after this and i had to rebuild that KVM guest (nested VM) to keep the environment running. This was my test lab env. So basically, from the cockpit of KVM host, try to edit any network configuration (try to add or modify the network of the VMs) the Oops page will be displayed. I will attach screenshots. Thanks! So this is really the "Virtual Machines" page, not the "Networking" one. Can you please still check `rpm -q cockpit-system cockpit-machines`? Katerina: The stack trace is hard to decipher (due to minimized code), but it seems to me that this crashes somewhere here: https://github.com/cockpit-project/cockpit/blob/211.3/pkg/machines/reducers.js#L112 That part of the code has not changed significantly, but of course the question is what actually called interfaces()/networks() with that invalid network interface. Any ideas for debugging/reproducing? In order to reproduce the crash it would be very useful to add here as attachment the XML files of the VMs on your system. (So for each VM virsh -c qemu:///$CONNECTION_NAME dumpxml $VM_NAME > $VM_NAME.xml, or copy them from /etc/libvirt/qemu/ directory if these are on system connection) One more observation is to set the locale from cockpit to "it_IT.UTF-8" and tried to configure the network. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |