Bug 1692707
Summary: | [machines]There is a Oops when use url to create the VMs with EDGE | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | YunmingYang <yunyang> |
Component: | cockpit-appstream | Assignee: | Katerina Koukiou <kkoukiou> |
Status: | CLOSED ERRATA | QA Contact: | YunmingYang <yunyang> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.0 | CC: | leiwang, mpitt, qiyuan, wshi, xchen |
Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
Target Release: | 8.1 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-11-05 20:41:55 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
YunmingYang
2019-03-26 09:37:41 UTC
I tried to reproduce this with trying to create a VM with this URL: https://dl.fedoraproject.org/pub/fedora/linux/development/30/Server/x86_64/os/ I also get an Oops, but it looks different first: "SCRIPT5: SCRIPT5: Access is denied". But a few seconds later I get the same oops as you. So this reproduces fine on our Windows 10 test image. Thanks! Fixed in https://github.com/cockpit-project/cockpit/pull/11639 Yunming, can you please QA ack? Test Versions: cockpit-machines-193-1.el8.noarch libvirt-dbus-1.2.0-2.module+el8.1.0+2983+b2ae9c0a.x86_64 Test Steps: 1.Use the browser which is 'EDGE' and login the cockpit 2.Create a machine with url on Virtual Machines page Test Results: The creation is successful and the installation is also successful. According to the results, The creation by using url on the EDGE is successful.So move the status to VERIFIED. 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 |