On Mon, 2019-05-13 at 16:29 -0600, Lars Kurth wrote:
> Hi all,
> I am going to step in here with my hat as Xen Project community
> manager. We had a discussion about this issue as part of last week's
> community call. I CC'ed a number of stake-holders, which probably
> should have been on the thread such as ITL (which builds QubesOS
> on top of Fedora) and Michael A Young (the Xen package manager).
> First of all apologies that this issue has lingered so long. Key
> members of the community were not aware of the issues raised in
> this thread, otherwise we would have acted earlier. With this in
> mind, please in future raise issues with me, on xen-devel@,
> committers@ or the Xen-Fedora package manager. The Xen Community
> would like to see Fedora running as guest: in fact it would be
> somewhat odd if there was a Xen-Dom0 package and guest support
> didn't work. And there are some downstreams such as QubesOS,
> which depend on this support.
Thanks for stepping in. Of course we always want as much stuff as
possible to work, but that does not mean we block the release on it. We
certainly want Fedora to work as a guest on VMWare, VirtualBox and
Parallels too; we don't block the release on any of those either...
> > Well, I mean, every few *days* a compose gets nominated for validation
> > testing, and a mail is sent to test-announce. Just check your test-
> > announce archives for mails with "nominated for testing" in their
> > subject lines, and you'll see dozens. Is this not sufficient
> > notification?
> We discussed this at the community call and came to the conclusion that
> we can run regular tests of Fedora RC's as part of our OSSTEST
> infrastructure. Ian Jackson volunteered to implement this, but there
> are some questions on
> a) The installer (which we can handle ourselves)
> b) When we would trigger a test - aka is there some trigger other than the
> c) How would results best be reported back to Fedora
> Apologies, I am not very familiar with how the Fedora Test group works.
> Is there some documentation which would help integrate what you to with
> the test system of another open source project?
b) you can use fedmsg / fedora-messaging:
A message is emitted every time a compose attempt finishes (on the fedmsg
topic 'org.fedoraproject.prod.pungi.compose.status.change': see
for a log of past messages). What you will want to do is listen for
completed Branched and Rawhide composes and run tests whenever one
completes successfully. This is already exactly what we do to schedule
openQA tests; you can crib from the openQA test scheduler:
particularly the fedmsg consumer:
c) ideally it would be good to report to both resultsdb and to the
wiki. Again, we already do this for openQA, and you can crib from the
reporting to ResultsDB might be tricky due to authentication issues,
I'm not sure if we ever put the openID auth stuff into production. For
wiki reporting you will either have to auth manually every so often or
ask Fedora infra for a special token that doesn't expire (this is what
we do for the openQA results).
Reporting to ResultsDB you do through resultsdb_api -
https://pagure.io/taskotron/resultsdb_api - and optionally you can use
my resultsdb_conventions -
https://pagure.io/taskotron/resultsdb_conventions - which makes it
somewhat easier (IMO anyway) and will make your results consistent with
those from openQA and Autocloud. Reporting to the wiki you can do
through my crazy python-wikitcms library -
https://pagure.io/fedora-qa/python-wikitcms . Again, fedora_openqa does
all this for openQA results, so you can crib from that. Let me know if
you have trouble with this.
> > > > from Oracle. On that basis, I'm proposing we remove this Final
> > > > criterion:
> > >
> > > s/Oracle/Xen Project/ I believe?
> > Perhaps, it's just that it always seemed to be you doing the testing,
> > so they got a bit conflated :)
> Can we come to some arrangement, by which such issues get communicated
> to the Xen Project earlier? Aka me, xen-devel@ or committers@
It would be nice if you could ensure someone from Xen is actually
watching the Fedora lists, if working in Fedora is a target for Xen. We
*could* try and CC stuff all the time, but imagine if we tried to do
that for everybody. But yes, for future conversations of this nature
I'll try and remember to include those lists.
> > > > "The release must boot successfully as Xen DomU with releases providing
> > > > a functional, supported Xen Dom0 and widely used cloud providers
> > > > utilizing Xen."
> > > >
> > > > and change the 'milestone' for the test case -
> > > > https://fedoraproject.org/wiki/QA:Testcase_Boot_Methods_Xen_Para_Virt -
> > > > from Final to Optional.
> > > >
> > > > Thoughts? Comments? Thanks!
> > >
> > > I would prefer for it to remain as it is.
> > This is only practical if it's going to be tested, and tested regularly
> > - not *only* on the final release candidate, right before we sign off
> > on the release. It needs to be tested regularly throughout the release
> > cycle, on the composes that are "nominated for testing".
> Would the proposal above work for you? I think it satisfies what you are
> looking for. We would also have someone who monitors these test results
In theory, yeah, but given the history here I'm somewhat sceptical. I'd
also say we still haven't really got a convincing case for why we
should continue to block the release (at least in theory) on Fedora
working in Xen when we don't block on any other virt stack apart from
our 'official' one, and we don't block on all sorts of other stuff we'd
"like to have working" either. Regardless of the testing issues, I'd
like to see that too if we're going to keep blocking on Xen...
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
I pulled the server net install iso for rawhide, the future Fedora 31,
and tried to install it. I used custom install with existing partitions
on a bios partitioned disk. It refused to install because it wanted gpt
I swap back and forth between predefined partitions, so I always have a
working Fedora to fall back on. This has worked fine in the past.
Is gpt and uefi now required for install? I didn't see a way to toggle
Anybody else able to reproduce this?
Basically you just boot a Rawhide LiveOS image in a VM with
systemd.log_level=debug and then once booted see what you get for
# journalctl -b -o short-monotonic
It should start with 0 seconds, with the first line of what you see in
dmesg. For me it's missing everything before 20 seconds. If I don't
use the debug switch, it doesn't happen, so it's like the debug option
is flooding the journal and it just bails.
OOooh I have a possible suspect!
[liveuser@localhost ~]$ losetup
NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE
/dev/loop1 0 0 0 1 /LiveOS/rootfs.img
/dev/loop2 0 0 0 0 /overlay (deleted)
/dev/loop0 0 0 0 1
/run/initramfs/live/LiveOS/squashfs.img 0 512
What is this loop2 /overlay that's been deleted? I wonder if it's
possible the journal got flushed there at first, and then it was
I find it kinda hard to believe I've got more than 16MiB of journal
messages just by booting the system, and there are two system journals
in /var/log/journal/$MACHINEID/ but that's apparently not everything.
I am Afras Ashraf, I am a python programmer, a linux system administrator, and an Open Source enthusiast and Fedora is a distro which I have been in love with for 3 years now.
As part of my Open Source venture, I wanna help out with the Fedora Project. So as I went on through whatcanidoforfedora.org , I bookmarked links to all the places I could contribute to, and QA and Testing was one of those links.
I hope to be of use to the community, and help out with testing, instruction, writing, and coding.
I'm Melvin George, with an eye for details... and faults.
I'm from Bangalore, India. Presently pursuing opportunities in product
management with interest in defining Quality and UAT for products.
I started using OpenSuse about 8 years ago. But, about 5 years ago is when
I used the black and white screen of CentOS extensively, while I owned the
backend systems at a mobile app startup. It would give me the pleasure to
realise products that care for the user and adapt to user's needs as a
caring human would.
Thanks a lot for your time. Looking forward to knowing about each of you.
Until then, let's find some bugs, redefine quality standards and make the
coolest sidekick OS for users around the world!
I have added the requested information to the bugs as shown below:
Bug 1694782 - Authorization pop up can not be satified or dismissed
> So basically, the problem is that if you have an admin user with no
> password, when an action requiring admin privileges is attempted, you
> get this non-satisfiable auth popup?
Yes, that is correct. The action is completed okay, but later after a
screen timeout and reactivation the pop-up appears.
Bug 1715617 - DNF fails with what appears to be a fails download:
> That looks like a mirror issue; the mirror you're getting dealt by
> mirrormanager is sending you data very slowly. If you adjust the repo
> config to point to a different, specific mirror (via baseurl) rather
> than using the mirror list, can you still reproduce?
I should note that I haven't had any problems like this with running
updates and installs on other PCs here running F30 on the same network
with no adjustments to the repo parameters. Are you saying this might be
a problem with a local parameter in the Rawhide (F31) drop that has to
do with mirrors?
I would like to try this, but I need some help with how to make the
change. I've never done this before. I need to know how I can identify
the url for a repo and where to make the change.
Have a Great Day!