On Tue, Feb 28, 2017 at 4:51 PM, Julián Tete <danteconrad14@gmail.com> wrote:
I think this: Helping to fix Upstream, is Helping to fix Downstream. If you wish teach me to open a bug case for oVirt.
Please see http://www.ovirt.org/community/get-involved/report-a-bug/ . Thanks and best regards,
This is a serious bug, you can´t debuggging with vdsm.log, is a invisible bug (a invisible log bug it's a nasty bug)
2017-02-28 2:54 GMT-05:00 Yedidyah Bar David <didi@redhat.com>:
On Mon, Feb 27, 2017 at 11:46 PM, Colin Coe <colin.coe@gmail.com> wrote:
I didn't create a bugzilla, I logged a ticket with Red Hat Support. We're a RHEL and RHEV shop.
May I note that nothing prevents you from doing both, as a customer. If you find a bug, and want engineering to know about it, by all means open one. If you also want support people help you, open a support case, and mention that you also opened a bug (and its number). If you don't, and support decides it's indeed a bug, they will likely open one for you eventually.
Best,
On Tue, Feb 28, 2017 at 5:44 AM, Julián Tete <danteconrad14@gmail.com> wrote:
:P Please don't forget about the URL of the Ticket to check in.
2017-02-27 16:22 GMT-05:00 Colin Coe <colin.coe@gmail.com>:
I'm just happy to hear it's not just me seeing this.
CC
On 27 Feb. 2017 21:54, "Julián Tete" <danteconrad14@gmail.com> wrote:
Hello Colin
Yeah with VNC the problem goes away, by the way. A nasty bug :( Where is the URL in the Bugzilla ?. I want to track this because SPICE recognize my latinoamerican keyboard, VNC doesn't
2017-02-25 1:48 GMT-05:00 Colin Coe <colin.coe@gmail.com>: > > Hi > > I see this also and I've logged a bug with Red Hat support on it. I > have found though that sometimes, if you wait long enough (i.e. > approx 22 > minutes) it will eventually boot. > > The other thing I've found is that if you change from SPICE to VNC, > the > problem goes away completely. > > Thanks > > On Sat, Feb 25, 2017 at 3:55 AM, Julián Tete > <danteconrad14@gmail.com> > wrote: >> >> Hello Friends of oVirt >> >> Suddenly I have a super creepy bug: >> >> I can't boot a CentOS-7-x86_64-Minimal-1611.iso >> >> I check the sha256sum and everything is OK >> >> The Virtual Machine Stuck in: >> >> "EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: >> (null)" >> >> or >> >> "systemd-journal[88]: Received SIGTERM from PID 1 (systemd). >> type=1403 audit(1487936348.599:2): policy loaded auid=4294967295 >> ses=4294967295 >> systemd[1]: Successfully loaded SELinux policy in 239.970ms. >> systemd[1]: Relabelled /dev and /run in 17.007ms." >> >> But Fedora 25, Debian 8, openSUSE Leap 12.2, Windows Server 2012 >> R2, >> Ubuntu 16.04.1 works like a charm >> >> oVirt Data: >> >> Software: >> >> oVirt Engine Version: 3.6.7.5-1.el7.centos >> >> backend version: 3.6.7 >> sdk version : 3.6.9.1 >> cli version : 3.6.9.2 >> python version : 2.7.5.final.0 >> >> OS Version: RHEL - 7 - 2.1511.el7.centos.2.10 >> Kernel Version: 4.6.0 - 1.el7.elrepo.x86_64 >> KVM Version: 2.3.0 - 31.el7_2.10.1 >> LIBVIRT Version: libvirt-1.2.17-13.el7_2.5 >> VDSM Version: vdsm-4.17.32-1.el7 >> SPICE Version: 0.12.4 - 15.el7_2.2 >> GlusterFS Version: [N/A] >> CEPH Version: librbd1-0.80.7-3.el7 >> Emulated Machine: pc-i440fx-rhel7.2.0 >> >> Hardware: >> >> Manufacturer: HP >> Family: ProLiant >> Product Name: ProLiant BL460c Gen8 >> CPU Model: Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz >> CPU Type: Intel SandyBridge Family >> CPU Sockets: 2 >> CPU Cores per Socket: 8 >> CPU Threads per Core: 2 (SMT Enabled) >> >> _______________________________________________ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Didi
-- Didi