I'm unclear on what anaconda version we should include in this test compose. There is a build that is newer than what was in Alpha, and I created test images for it for QA testing, however it has yet to be marked stable. Should I include this testing build, a newer build, revert to the alpha build...?

I wasn't aware there were test images that needed testing :/ Obviously we should have done something to communicate this. Since 627401 will clearly be a Beta blocker, I'd say we should go with 14.17 for the TC, and then we can probably get the update approved based on TC testing.

Replying to [comment:4 adamwill]:

I wasn't aware there were test images that needed testing :/ Obviously we should have done something to communicate this. Since 627401 will clearly be a Beta blocker, I'd say we should go with 14.17 for the TC, and then we can probably get the update approved based on TC testing.

I've supplied the karma needed based on newgle's testing of the pre-beta anaconda-14.17-1 (see https://admin.fedoraproject.org/updates/anaconda-14.17-1.fc14). Well done newgle! :)

However, I am still concerned that we won't get very far beyond the installer without the fix for bug#627401. I'd prefer having as few roadblocks in the way of validating systemd operates correctly.

clarification to my comment: I forgot that 14.17 has an incorrect fix for 627401. So 14.17 is no good for the TC either. We'll need a 14.18 build with the correct 627401 fix.

http://alt.fedoraproject.org/pub/alt/stage/14-Beta.TC1/ has been posted. It'll be mirrored http://serverbeach1.fedoraproject.org/pub/alt/stage/14-Beta.TC1/ shortly.

it includes anaconda-14.17.1

er, see my last comment - I'm afraid a build with 14.17 will be a non-starter as it does not have a correct fix for the default.target problem and consequently will fail to boot correctly on install.

According to

http://koji.fedoraproject.org/koji/buildinfo?buildID=194573

14.17.1 (as opposed to 14.17) has another fix for 627401, dated today.

ah, cool, I missed the .1.