journalctl missing early boot entries
by Chris Murphy
All F21 installations I've done since beta lack early boot entries
when I use journalctl. Specifically when I use 'journalctl -o
short-monotonic' the earliest timestamp is 4+ seconds into boot. With
F21 beta this was working where I'd have dozens, maybe over 100
entries with 0.000 monotonic time, all kernel entries, all before
systemd is even launched.
Thing is, 216-5 works on beta, but doesn't work when I downgrade from
216-11 on RC4 to 216-5. So it makes me wonder if this isn't even
systemd's fault but that'd maybe implicate the kernel which seems
unlikely. Anyone else seeing this?
https://bugzilla.redhat.com/show_bug.cgi?id=1169269
--
Chris Murphy
9 years, 6 months
- 1
- 0
[Test-Announce] 2014-12-01 @ 1600 UTC - Blocker Review Meeting
by Adam Williamson
# F21 Blocker Review meeting
# Date: 2014-12-01
# Time: 16:00 UTC (run "date -d '2014-11-19 16:00 UTC'" to see local time)
# Location: #fedora-blocker-review on irc.freenode.net
Instead of the QA meeting this week, let's run a blocker review meeting.
Currently we have 5 proposed blockers and 6 proposed FEs.
If you want to take a look at the accepted blockers, the full list can be found
here: https://qa.fedoraproject.org/blockerbugs/milestone/21/final/buglist
We'll be evaluating these bugs to see if they violate the Final
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F21 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out the SOP
on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
See you there!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
test-announce mailing list
test-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
9 years, 6 months
- 1
- 0
[Test-Announce] Proposal to CANCEL: 2014-12-01 Fedora QA Meeting
by Adam Williamson
I don't think there's much to discuss at present besides Fedora 21
testing, so I think we may as well just go right ahead and run a blocker
review meeting instead of the QA meeting. I'll send out an announce for
that right after this mail - usual time, but in #fedora-blocker-review,
and we'll review blockers. =)
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
test-announce mailing list
test-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
9 years, 6 months
- 1
- 0
pungi
by Gene Czarcinski
I know we are into this product-zed stuff with lots of emphasis on Live
installs including Live Workstation but when was the last time pungi has
been successfully run? Yes, I know that TC3 was built by something but
was pungi involved? I have been assuming it was but I am unable to run
it myself.
To keep things simple, I am using
/usr/share/spin-kickstarts/fedora-install-server.ks and am only doing
"-G -C -B" since I really only want the netinstall. Also, this was done
on a fresh install for Workstation TC3 plus mock installed. I run pungi
under mock just like it says here:
http://fedoraproject.org/wiki/How_to_create_a_Fedora_install_ISO_for_testing
The first problem is that the mirrorlist stuff simply does not work and
pungi cannot file a good url for fedora. OK, replace the mirrorlist
with baseurl pointing at one of the mirrors (I chose
http://mirrors.kernel.org and
http://dl.fedoraproject.org/pub/linux/fedora/).
That gets me further but but it still crashes with:
> doing post-install configuration
> running runtime-postinstall.tmpl
> warning: Schema 'org.gnome.crypto.cache' has path
> '/desktop/gnome/crypto/cache/'. Paths starting with '/apps/',
> '/desktop/' or '/system/' are deprecated.
> warning: Schema 'org.gnome.crypto.pgp' has path
> '/desktop/gnome/crypto/pgp/'. Paths starting with '/apps/',
> '/desktop/' or '/system/' are deprecated.
> warning: Schema 'org.gnome.system.locale' has path '/system/locale/'.
> Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
> warning: Schema 'org.gnome.system.proxy' has path '/system/proxy/'.
> Paths starting with '/apps/', '/desktop/' or '/system/' are deprecated.
> warning: Schema 'org.gnome.system.proxy.http' has path
> '/system/proxy/http/'. Paths starting with '/apps/', '/desktop/' or
> '/system/' are deprecated.
> warning: Schema 'org.gnome.system.proxy.https' has path
> '/system/proxy/https/'. Paths starting with '/apps/', '/desktop/' or
> '/system/' are deprecated.
> warning: Schema 'org.gnome.system.proxy.ftp' has path
> '/system/proxy/ftp/'. Paths starting with '/apps/', '/desktop/' or
> '/system/' are deprecated.
> warning: Schema 'org.gnome.system.proxy.socks' has path
> '/system/proxy/socks/'. Paths starting with '/apps/', '/desktop/' or
> '/system/' are deprecated.
> No such key 'button-laytout' in schema
> 'org.gnome.desktop.wm.preferences' as specified in override file
> '/usr/share/glib-2.0/schemas/org.gnome.desktop.wm.preferences.gschema.override';
> ignoring override for this key.
> writing .discinfo file
> backing up installroot
> generating kernel module metadata
> doing depmod and module-info for 3.17.3-300.fc21.x86_64
> cleaning unneeded files
> running runtime-cleanup.tmpl
> creating the runtime image
> losetup: cannot find an unused loop device
> Traceback (most recent call last):
> File "/usr/bin/pungi", line 300, in <module>
> main()
> File "/usr/bin/pungi", line 171, in main
> mypungi.doBuildinstall()
> File "/usr/lib/python2.7/site-packages/pypungi/__init__.py", line
> 1414, in doBuildinstall
> workdir=workdir, outputdir=outputdir, volid=volid)
> File "/usr/lib/python2.7/site-packages/pylorax/__init__.py", line
> 304, in run
> size=size)
> File "/usr/lib/python2.7/site-packages/pylorax/treebuilder.py", line
> 165, in create_runtime
> label="Anaconda", size=fssize)
> File "/usr/lib/python2.7/site-packages/pylorax/imgutils.py", line
> 383, in mkext4img
> mkfsargs=["-L", label, "-b", "1024", "-m", "0"], graft=graft)
> File "/usr/lib/python2.7/site-packages/pylorax/imgutils.py", line
> 358, in mkfsimage
> with LoopDev(outfile, size) as loopdev:
> File "/usr/lib/python2.7/site-packages/pylorax/imgutils.py", line
> 258, in __enter__
> self.loopdev = loop_attach(self.filename)
> File "/usr/lib/python2.7/site-packages/pylorax/imgutils.py", line
> 116, in loop_attach
> dev = runcmd_output(["losetup", "--find", "--show", outfile])
> File "/usr/lib/python2.7/site-packages/pylorax/executils.py", line
> 417, in runcmd_output
> return execWithCapture(cmd[0], cmd[1:], **kwargs)
> File "/usr/lib/python2.7/site-packages/pylorax/executils.py", line
> 263, in execWithCapture
> raise subprocess.CalledProcessError(proc.returncode, [command]+argv)
> subprocess.CalledProcessError: Command '['losetup', '--find',
> '--show',
> '//work/Fedora/x86_64/installroot/images/runtime-workdir/LiveOS/rootfs.img']'
> returned non-zero exit status 1
> <mock-chroot>[root@vulture /]# ls -l
> /work/Fedora/x86_64/installroot/images/runtime-workdir/LiveOS/rootfs.img
> -h
> -rw-r--r--. 1 root root 2.0G Nov 24 15:36
> /work/Fedora/x86_64/installroot/images/runtime-workdir/LiveOS/rootfs.img
> <mock-chroot>[root@vulture /]#
I have not bz'ed this yet because it looks like there are similar
reports but I will just in case this provides some different info.
Is there some documentation which describes how the builds are done.
There is lots of documentation on building RPMs and creating livecds but
I have not found anything which describes how
Fedora-Server-netinst-x86_64-21_TC3.iso was created.
Fortunately, livecd-creator must use very different software because I
have not seen it have any problems.
Gene
9 years, 6 months
- 4
- 10