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 1720267 - cockpit-machines: When navigating to the network tab of a shut off VM an error notification appears saying that the IP addresses could not be fetched
Summary: cockpit-machines: When navigating to the network tab of a shut off VM an erro...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cockpit-appstream
Version: 8.1
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: 8.1
Assignee: Martin Pitt
QA Contact: YunmingYang
URL:
Whiteboard:
Depends On: 1724672
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-13 14:24 UTC by Katerina Koukiou
Modified: 2020-11-14 12:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 20:41:55 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot-notification (26.90 KB, image/png)
2019-06-13 14:24 UTC, Katerina Koukiou 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3325 0 None None None 2019-11-05 20:42:06 UTC

Description Katerina Koukiou 2019-06-13 14:24:54 UTC 
Created attachment 1580327 [details]
screenshot-notification

Description of problem:
virDomainInterfaceAddresses API fails for shut off VMs, which results in an error notification to appear on screen when a user navigates to the Network tab of a shut off VMs.


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

How reproducible:
Always

Fixed upstream by https://github.com/cockpit-project/cockpit/pull/12064
Comment 1 Martin Pitt 2019-06-13 14:26:51 UTC 
Yunming, can you please QE-ack this? Thanks!
Comment 2 Martin Pitt 2019-06-24 12:33:10 UTC 
Yunyang, can you please re-qa-approve? I had to fix the component, this is in cockpit-appstream. Thanks!
Comment 3 Martin Pitt 2019-06-27 14:01:02 UTC 
New libssh has a regression, cockpit's tests find that and thus the package currently fails to build. I'll leave some days to the libssh devs to fix this, otherwise we'll have to skip the tests on a RHEL 8.1 build.
Comment 5 YunmingYang 2019-08-07 07:30:42 UTC 
Test Versions:
cockpit-machines-197.1-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+3531+2918145b.x86_64


Test Steps:
1. Create a off VM
2. Switch to the Network tab of the VM row, check the information
3. Run the VM, switch to the Network tab of the VM row, check the information
4. Wait for VM booting completely, re-switch to the Network tab of the VM row

Test Results:
1. After step2, there is no error raised, the 'IP Address' is unknown
2. After step3, there is no error raised, the 'IP Address' is unknown
3. After step2, there is no error raised, the 'IP Address' is correct, the same with results of 'ip a'


According to the results, move the status to VERIFIED.
Comment 7 errata-xmlrpc 2019-11-05 20:41:55 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, 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-2019:3325
Note You need to log in before you can comment on or make changes to this bug.