Re: [atomic-devel] Note: Atomic Host integration for F22 at risk
by Colin Walters
(Forgot to CC cloud, if you reply please readd
atomic-devel(a)projectatomic.io )
On Thu, Mar 26, 2015, at 01:17 PM, Colin Walters wrote:
> On Thu, Mar 26, 2015, at 10:57 AM, Peter Robinson wrote:
>
> > Ultimately the request came in 3 weeks ago, that's post freeze.
> > Rel-eng has a lot to deliver in each release and limited resources,
> > Changes that need rel-eng engagement should have our buy in long
> > before they're sent to FESCo
>
> There's circular dependencies there...not sure how much attention
> a ticket would have for something not approved by FESCo, but on
> the other hand it's clearly true that the original https://fedoraproject.org/wiki/Changes/AtomicHost
> proposed in November could have made more clear that it needed
> a separate Anaconda build, and that would have helped make
> rel-eng aware.
>
> But debating history doesn't solve anything now.
> What you're saying sounds like a "No, we can't do this" - why not just say
> so in the ticket?
>
> What I was more hoping for was "We have limited resources, but
> here's how you can help/what you can change (and why)...". Like a
> patch review.
9 years, 1 month
Fedora 22 Beta blocker bug status #1
by Adam Williamson
Hi folks! It's everyone's favourite time of the year - time for QA to
make you feel bad about blocker bugs!
We're still six days out from Beta freeze, but I wanted to try and get
out ahead of the blocker list and try to keep up the 'shipping on
time' trend we started with Alpha...
If you're directly CCed on this email, it's for one of these reasons:
1) You maintain one of the packages that needs maintainer attention
2) You don't actually maintain one of the packages that needs
maintainer attention but I think you do because I can be an idiot
sometimes
3) You're a Great Leader of some sort (hi, Paul, Jaroslav) and thus
get to read lots of mail from idiot monkeys
If you're a case of 2), please feel free to yell at me at your leisure!
tl;dr
=====
Testers, please test and karma these updates:
https://admin.fedoraproject.org/updates/libedit-3.1-11.20141030cvs.fc22
https://admin.fedoraproject.org/updates/FEDORA-2015-4398 (you can up-
karma that one if networking works in the TC4 installer)
https://admin.fedoraproject.org/updates/fedora-release-22-0.14
Developers, the following bugs need fixes. If you believe any of them
should not be a blocker, please follow up here or in the bug report.
anaconda-n-friends
------------------
https://bugzilla.redhat.com/show_bug.cgi?id=1166598 "going back to
installation destination picker swaps partitions on disks"
https://bugzilla.redhat.com/show_bug.cgi?id=1185117 "Custom
partitioning does not allow convenient removal of volume including
snapshots (btrfs, LVM)"
others
------
https://bugzilla.redhat.com/show_bug.cgi?id=1197894 "growpart: sfdisk
dropped --show-pt-geometry option" (NEEDS ATTENTION)
https://bugzilla.redhat.com/show_bug.cgi?id=1204612 "eth0 is going
missing in the cloud images"
https://bugzilla.redhat.com/show_bug.cgi?id=1204739 "Installing Fedora
Server netinst ends up with blocked Cockpit port"
https://bugzilla.redhat.com/show_bug.cgi?id=1183807 "network spoke
listed as not connected despite having assigned IP and hostname"
https://bugzilla.redhat.com/show_bug.cgi?id=1185604 "fedup upgrade
fails within the initramfs-fedup env"
Detailed bug discussion
=======================
1. https://bugzilla.redhat.com/show_bug.cgi?id=1166598- anaconda -
"going back to installation destination picker swaps partitions on
disks"
AIUI, someone (vpodzime?) is tasked to work on this and there's a
plan, but it's moderately complex and there's some suggestion from
anaconda team that this is more appropriately a Final blocker than
Beta. The issue is fairly well understood and reproducible.
2. https://bugzilla.redhat.com/show_bug.cgi?id=1185117 - anaconda -
"Custom partitioning does not allow convenient removal of volume
including snapshots (btrfs, LVM)"
Again there's a question as to whether this is 'really' a blocker,
though personally I think cmurf made a strong argument; it's clearly
painful to remove a btrfs/LVM volume with more than a few snapshots in
custom partitioning, and we can't really pretend snapshotted volumes
aren't a thing. There might be an argument for pushing it to Final. I
do not know what the status of work on this bug is.
3. https://bugzilla.redhat.com/show_bug.cgi?id=1191842 - anaconda -
"unable to continue the installation after type into a weak password"
This is the good ol' password strength bikeshed. anaconda implemented a
system that allows the password strength checking to be customized,
but FESCo has some concerns about whether it's sufficient to their
requirements. I think I'm gonna leave this one to FESCo to herd, they
seem to be on top of what they want from it.
4. https://bugzilla.redhat.com/show_bug.cgi?id=1184173 - bind -
"dhclient fails to renew lease, results in dropped IPv4 network
connection"
This one is basically done, the update is being pushed stable. The fix
for this bug did cause the showstopper bug in TC3 whose fix caused the
showstopper bug in TC4, though. I hate software. Anyone want to bet
what the fix for the TC4 showstopper will break in TC5?!
5. https://bugzilla.redhat.com/show_bug.cgi?id=1197894 - cloud-utils -
"growpart: sfdisk dropped --show-pt-geometry option"
This one rather seems to have been sitting around since Alpha; we
could do with some urgency on it. Is anyone from Cloud WG able to step
up and ensure this gets resolved?
6. https://bugzilla.redhat.com/show_bug.cgi?id=1204612 - distribution -
"eth0 is going missing in the cloud images"
Kushal Das seems to have taken ownership of this one today, so it
looks like it's being taken care of.
7. https://bugzilla.redhat.com/show_bug.cgi?id=1204739 - fedora-
release - "Installing Fedora Server netinst ends up with blocked
Cockpit port"
I believe
https://admin.fedoraproject.org/updates/fedora-release-22-0.14 is
intended to fix this, though it's not marked as such. Probably needs
testing.
8. https://bugzilla.redhat.com/show_bug.cgi?id=1201120 - libblockdev -
"DeviceTreeError: could not find parent for subvol"
We have a potential fix for this as a scratch build awaiting testing
by the reporter who submitted the bug. I don't think anyone else has a
reproducer at present, though it should be fairly easy to work one up
if need be.
9. https://bugzilla.redhat.com/show_bug.cgi?id=1201897 - libedit -
"SIGSEGV in libedit call in installer"
This is the showstopper bug in TC4 (in non-live images, anaconda
crashes shortly after reaching the hub) that was triggered by the fix
for the showstopper bug in TC3 (see next bug!) We traced this one out
over the last couple of days and it looks like
https://admin.fedoraproject.org/updates/libedit-3.1-11.20141030cvs.fc22
addresses the problem; TC5 is currently underway.
10. https://bugzilla.redhat.com/show_bug.cgi?id=1204031 - lorax - "22
Beta TC3 install images do not bring up network (unless updates image
or kickstart used)"
So the bind update which we pulled into TC3 to fix bug #4 moved its
libraries around for $REASONS, and requires a file in
/etc/ld.so.conf.d to be respected when building the linker cache in
order for dhclient to work. Turned out /etc/ld.so.conf was left out of
the anaconda environment, so files in /etc/ld.so.conf.d weren't
respected when ldconfig.service rebuilt the linker cache on boot, and
dhclient stopped working. So we fixed lorax to include /etc/ld.so.conf
in the anaconda environment...which fixed this bug, but caused bug #9,
approximately because llvm. Oh software, how we hate you. Anyway, the
lorax change does seem to fix *this* bug (right before anaconda
crashes in TC4, you can see the network's working...), so unless
anyone sees any other problems with it, we should up-karma the update -
that's https://admin.fedoraproject.org/updates/FEDORA-2015-4398 - and
push it stable.
11. https://bugzilla.redhat.com/show_bug.cgi?id=1183807 -
NetworkManager - "network spoke listed as not connected despite having
assigned IP and hostname"
The status of this one is a bit mysterious. pwhalen stopped seeing it
in TC3 and TC4, but nothing went into those builds which would be
*expected* to fix it so far as anyone knows, and bcl mentioned seeing
something like it today in IRC. Probably needs testing with TC5 and
more investigation.
12. https://bugzilla.redhat.com/show_bug.cgi?id=1185604 - systemd -
"fedup upgrade fails within the initramfs-fedup env"
Both the cause and the fix for this seem to be known at this point,
and we're waiting on the systemd maintainers finding time to do an F21
build. We would really appreciate it if they'd do that soon, as we
want to be able to test upgrades properly. Thanks, systemd maintainers.
Extra credit: proposed blockers
===============================
We also have a couple of proposed blockers which look like fairly
strong candidates and should be treated with priority.
1. https://bugzilla.redhat.com/show_bug.cgi?id=1205534 - gnome-initial-
setup - "gnome-initial-setup crashes upon selecting language"
This one just came onto the radar today, but it looks fairly
significant, and is more or less described by the title.
2. https://bugzilla.redhat.com/show_bug.cgi?id=864198 - grubby -
"grubby fatal error updating grub.cfg when /boot is btrfs"
This is something of a greatest hit; grubby has had trouble handling
/boot on btrfs for a long time. For the last couple of releases
anaconda disallowed /boot-on-btrfs which meant it was effectively a
non-issue, but as of now, F22 anaconda allows it again; we either need
to ban it again, or fix grubby.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
9 years, 1 month
[FINAL CONFIRMATION] Deleting pre-F21 AMIs
by David Gay
Greetings.
As one of the things discussed in the "AMI lifetimes" thread this month, I would like to delete all Alpha, Beta, TC, RC, and other scratch AMIs pre-F21 from *both* our community cloud and official AWS accounts.
I've gotten a +1 via list, and two +1s in the meeting today. There have been no objections on the list or in the meeting. This will save us a notable amount in AWS storage charges.
Unless anyone has an objection, I'll start (carefully) deleting these AMIs in 24 hours.
-- David
9 years, 1 month
Password policy changes
by Adam Williamson
Hey, folks. I'm writing with my Server SIG member hat on, here. We've
been discussing password policy changes at our meeting today.
So the Great Password Policy Bunfight of 2015 was resolved by anaconda
creating a mechanism for products/spins to set their own password
policy:
https://github.com/rhinstaller/anaconda/commit/8f24eeaedd7691b6ebe119592e...
I'm slightly worried, however, about the possibility that everyone
goes out and picks a more lenient policy more or less at random and we
wind up with different policies on every Fedora medium. That seems
like it'd be needlessly confusing to users and difficult to document.
I'm wondering if those products/spins intending to set a policy weaker
than the default could all agree on the same one, so there'd only be
at most two policies to care about (and if all products/spins overrode
the upstream default, there'd only be one).
The obvious choice would be the pre-F22 policy, which I believe should
be:
--nostrict --minlen=6 --minquality=50 --nochanges --emptyok
(though it's not *entirely* clear from the code - I think it used
pwquality upstream defaults - so I may be a bit off).
What's the general feeling here? Have other SIGs discussed this yet?
Come to any decisions? Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
9 years, 1 month
Cloud image lifetimes
by David Gay
Greetings!
We sort of ran out of time in today's Cloud WG meeting, but I did want to ask:
What are your thoughts on AMI lifetimes? That is to say, how long should EC2 AMIs exist before they're deleted? A few points to consider:
- AMIs only cost us for storage, so it's not a *huge* cost to maintain a public AMI
- At the same time, there are a lot of AMIs, since we build 2-4 per AWS region per build, and that number is growing
- There are 9 regions now, and we have 2 virtualization types, and 2 volume types, as well (9 regions * 2 * 2 = 36 AMIs per Base image build, 18 for Atomic builds (since they are only available in HVM format))
- This total number will only grow larger as we add instance-store AMIs, and so on
- This isn't even taking into account any costs we'll have once we secure a deal with other providers like HP, Rackspace, and GCE, to maintain public images on their services
I propose we have some sort of discussion regarding how long cloud image builds should be available on services like AWS. I suspect this will resolve to having different lifetimes for scratch, test, RC, final, and maybe other build types.
Any input is appreciated. We can certainly talk about this at next week's meeting, as well.
-- David
9 years, 1 month
NetworkManager and network services both enabled in Fedora Atomic
by Dusty Mabe
Both NetworkManager and network systemd services are enabled in F21
and F22 Atomic and this could be causing some issues we are seeing.
We should probably open a BZ for this. If no one objects I will make
one.
I would suggest that we adopt the approach that Fedora Cloud Base
takes by just having the Network service enabled. This would also mean
we can pull the NetworkManager packages out of atomic and make the
image smaller.
Thoughts?
Dusty
9 years, 1 month
Cloud SIG meeting minutes (2015-03-18)
by Kushal Das
===================================
#fedora-meeting-1: Fedora Cloud SIG
===================================
Meeting started by kushal at 19:01:35 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2015-03-18/fedora-meeti...
.
Meeting summary
---------------
* rollcall (kushal, 19:01:45)
* Action items from previous meeting (kushal, 19:04:47)
* Maintaining Fedora docker images for f22 #97 (kushal, 19:06:22)
* Care and Feeding, Fedora Dockerfiles #84 (kushal, 19:14:53)
* LINK: https://fedorahosted.org/cloud/ticket/84 (jzb, 19:16:32)
* ACTION: jzb help find scollier additional maintainer for dockerfiles
(jzb, 19:25:14)
* ACTION: jzb (and others) update dockerfiles for dnf (jzb, 19:25:38)
* Getting sha256sum published for the cloud images
https://fedorahosted.org/cloud/ticket/93 (kushal, 19:30:56)
* LINK:
http://dl.fedoraproject.org/pub/alt/stage/22_Beta_TC2/Cloud-Images/x86_64...
(dgilmore, 19:33:48)
* LINK: http://paste.fedoraproject.org/199747/26707461/ (dgilmore,
19:37:51)
* LINK: https://fedorahosted.org/cloud/ticket/93 (dustymabe,
19:41:15)
* ACTION: kushal wil ask Lennart for more specific use case and
details for #93 (kushal, 19:52:34)
* LINK: http://cloud.fedoraproject.org/fedora-19.x86_64.qcow2
(dgilmore, 19:55:25)
* LINK: http://cloud.fedoraproject.org/fedora-21.x86_64.qcow2
(dgilmore, 19:55:34)
* LINK: http://cloud.fedoraproject.org/fedora/21/x86_64/SHA256SUM
(dgilmore, 19:56:48)
* Atomic as separate spin (or, going the other way, main cloud edition)?
https://fedorahosted.org/cloud/ticket/96 (kushal, 19:58:26)
* ACTION: create proposal page on wiki for Atomic spin for f23
forward, call for vote on mailing list. (jzb, 20:06:44)
* ACTION: jzb create proposal page on wiki for Atomic spin for f23
forward, call for vote on mailing list. (jzb, 20:07:04)
* Producing Updated Cloud/Atomic Images
https://fedorahosted.org/cloud/ticket/94 (kushal, 20:07:27)
* LINK: http://dl.fedoraproject.org/pub/alt/stage/21-20150309/ has the
last updates compose (dgilmore, 20:11:09)
Meeting ended at 20:15:13 UTC.
Action Items
------------
* jzb help find scollier additional maintainer for dockerfiles
* jzb (and others) update dockerfiles for dnf
* kushal wil ask Lennart for more specific use case and details for #93
* create proposal page on wiki for Atomic spin for f23 forward, call for
vote on mailing list.
* jzb create proposal page on wiki for Atomic spin for f23 forward, call
for vote on mailing list.
Action Items, by person
-----------------------
* jzb
* jzb help find scollier additional maintainer for dockerfiles
* jzb (and others) update dockerfiles for dnf
* jzb create proposal page on wiki for Atomic spin for f23 forward,
call for vote on mailing list.
* kushal
* kushal wil ask Lennart for more specific use case and details for
#93
* scollier
* jzb help find scollier additional maintainer for dockerfiles
* **UNASSIGNED**
* create proposal page on wiki for Atomic spin for f23 forward, call
for vote on mailing list.
People Present (lines said)
---------------------------
* jzb (79)
* kushal (73)
* dgilmore (70)
* dustymabe (19)
* oddshocks (19)
* scollier (13)
* mattdm (12)
* zodbot (7)
* jsmith (4)
* rtnpro (3)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Kushal
--
Fedora Cloud Engineer
CPython Core Developer
Director Python Software Foundation
http://kushaldas.in
9 years, 1 month
