Re: fedup: boot image not found
On Mon, 2014-12-15 at 15:21 -0800, Adam Williamson wrote: > (It occurs to me that I can probably do some wiki template magic in > the fedup test case instructions so they will provide the correct > instrepo parameter for the most recent nightly compose or TC/RC; > I'll have to look at that later.) So hey, I did this. If you look at any of the fedup test cases - e.g. https://fedoraproject.org/wiki/QA:Testcase_upgrade_fedup_cli_previous_desktop - you should now always see an accurate installation repository URL in the instructions (like, right now, it points into the 2014-12-08 Rawhide nightly tree, as that's what we have nominated for testing). It should handle things properly when 22 branches and we go to testing Branched nightlies instead of Rawhide ones, and then when we start testing TCs and RCs. This might be a good time to mention a magic wiki template I added as part of relval work: https://fedoraproject.org/wiki/Template:CurrentFedoraCompose up until today it simply contained the text of the current compose - so, '22 20141208', at present. To make the fedup instructions stuff possible, I made it a bit smarter, as explained in the template documentation, there. It may be useful for others doing stuff with validation testing. You can call the template with various parameters to get various info about the current compose. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: fedup: boot image not found
On 16.12.2014 00:21, Adam Williamson wrote: > On Mon, 2014-12-15 at 18:14 +, Brian McGrew wrote: >>> On Dec 15, 2014, at 9:12 AM, Adam Williamson < >>> adamw...@fedoraproject.org> wrote: >>> >>> On Mon, 2014-12-15 at 16:40 +, Brian McGrew wrote: Good morning all, Running fedup and getting the following on a stock install of F20: [admin@knotts ~]$ sudo fedup --network 21 --product=workstation [sudo] password for admin: setting up repos... getting boot images... Downloading failed: couldn't get boot images: No more mirrors to try. Last error was: [Errno 14] HTTP Error 404 - Not Found [admin@knotts ~]$ sudo fedup --network rawhide -- product=workstation setting up repos... getting boot images... Downloading failed: couldn't get boot images: No more mirrors to try. Last error was: [Errno 14] HTTP Error 404 - Not Found [admin@knotts ~]$ >>> >>> Can't immediately see a good reason it isn't working, does it work >>> with --instrepo= >>> https://dl.fedoraproject.org/pub/fedora/linux/releases/21/Server/x86_64/os/ >>> ? (assuming x86_64, >>> of >>> course) >> >> Of course x86_64! That appears to be working. Odd! Will let you >> know if it doesn’t finish. I’ll get to 21 and then to rawhide and >> see what happens. > > fedup is rarely tested prior to Alpha, FWIW. You will need to manually > provide a --instrepo parameter again. Here, I may as well explain > what's actually going on there. > > What fedup gets from the 'installation repository' is a kernel and a > special initramfs. The initramfs contains the bits that drive the > actual upgrade step of the fedup process - they're in the package > 'fedup-dracut', and part of the Fedora compose process involves > building the special initramfs with those bits in it. > > This special initramfs is called upgrade.img. When you pass fedup a -- > instrepo parameter, it looks for the file .treeinfo.signed in the > location you specify. So, for that one above, it found: > > https://dl.fedoraproject.org/pub/fedora/linux/releases/21/Server/x86_64/os/.treeinfo.signed > > you can go look at that for yourself, and you'll see what's in it - > the name is apt, it provides 'info'rmation on the 'tree'. The bit > fedup cares about is that it tells it where to find its special > upgrade initramfs: > > [images-x86_64] > kernel = images/pxeboot/vmlinuz > initrd = images/pxeboot/initrd.img > upgrade = images/pxeboot/upgrade.img > boot.iso = images/boot.iso > > fedup goes and grabs the 'kernel' and 'upgrade' files (the kernel is > just the kernel file that's in the kernel package in the same tree), > and that's what it adds to the bootloader config, the environment you > boot into after the first fedup phase has downloaded all the packages > and told you to reboot to continue. > > If you *don't* pass a --instrepo parameter, what fedup does is it asks > mirrormanager for the location: it asks mirrormanager for a mirror > list for the 'fedora-install' repository for the release you specified > you wanted to upgrade to, and the appropriate arch. You can do the > same thing through mirror manager's web interface: > > https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-install-21&arch=x86_64 > > So if you just say 'fedup --network 21' on an x86_64 system, fedup > goes and asks mirrormanager for that list of repos, then picks one and > uses it as the 'installation repository'. (When I read your mail the > first thing I did was check that URL and make sure the list it > produced was sane; it does seem to be, so I'm not quite sure why you > got a 404. It's possible you hit a bad mirror which didn't have the > files in place, I guess?) > > So now let's see what happens if you try and fedup to 22 without > giving it any help: > > https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-install-22&arch=x86_64 > > "# repo = fedora-install-22 arch = x86_64 error: invalid repo or arch" > > Ooops. Well, let's try Rawhide: > > https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-install-rawhide&arch=x86_64 > > OK, that's a proper list, so you could try 'fedup --network > rawhide'...but wait! What does fedup do with the instrepo? It looks > for .treeinfo.signed. Let's check that's available on a mirror from > the list: > > http://fedora.mirror.nexicom.net/linux/development/rawhide/x86_64/os/.treeinfo.signed > ... > 404. > > Oh dear. First problem here is, Rawhide trees generally aren't signed. > So, you'd also have to pass --nogpgcheck; this will make it look for > the un-signed version of the file instead, which is just .treeinfo : > > http://fedora.mirror.nexicom.net/linux/development/rawhide/x86_64/os/.treeinfo > ... > 404. > > Well pants! Why, you wonder? Because the nightly compose attempt > failed. There's an automated attempt to 'compose' the Rawhide (and > Branched, when it exists) tree nightly. That's the proces
Re: fedup: boot image not found
On Mon, 2014-12-15 at 18:14 +, Brian McGrew wrote: > > On Dec 15, 2014, at 9:12 AM, Adam Williamson < > > adamw...@fedoraproject.org> wrote: > > > > On Mon, 2014-12-15 at 16:40 +, Brian McGrew wrote: > > > Good morning all, > > > > > > Running fedup and getting the following on a stock install of > > > F20: > > > > > > [admin@knotts ~]$ sudo fedup --network 21 --product=workstation > > > [sudo] password for admin: > > > setting up repos... > > > getting boot images... > > > > > > Downloading failed: couldn't get boot images: No more mirrors to > > > try. Last error was: [Errno 14] HTTP Error 404 - Not Found > > > > > > > > > [admin@knotts ~]$ sudo fedup --network rawhide -- > > > product=workstation setting up repos... > > > getting boot images... > > > > > > Downloading failed: couldn't get boot images: No more mirrors to > > > try. Last error was: [Errno 14] HTTP Error 404 - Not Found > > > [admin@knotts ~]$ > > > > Can't immediately see a good reason it isn't working, does it work > > with --instrepo= > > https://dl.fedoraproject.org/pub/fedora/linux/releases/21/Server/x86_64/os/ > > ? (assuming x86_64, > > of > > course) > > Of course x86_64! That appears to be working. Odd! Will let you > know if it doesn’t finish. I’ll get to 21 and then to rawhide and > see what happens. fedup is rarely tested prior to Alpha, FWIW. You will need to manually provide a --instrepo parameter again. Here, I may as well explain what's actually going on there. What fedup gets from the 'installation repository' is a kernel and a special initramfs. The initramfs contains the bits that drive the actual upgrade step of the fedup process - they're in the package 'fedup-dracut', and part of the Fedora compose process involves building the special initramfs with those bits in it. This special initramfs is called upgrade.img. When you pass fedup a -- instrepo parameter, it looks for the file .treeinfo.signed in the location you specify. So, for that one above, it found: https://dl.fedoraproject.org/pub/fedora/linux/releases/21/Server/x86_64/os/.treeinfo.signed you can go look at that for yourself, and you'll see what's in it - the name is apt, it provides 'info'rmation on the 'tree'. The bit fedup cares about is that it tells it where to find its special upgrade initramfs: [images-x86_64] kernel = images/pxeboot/vmlinuz initrd = images/pxeboot/initrd.img upgrade = images/pxeboot/upgrade.img boot.iso = images/boot.iso fedup goes and grabs the 'kernel' and 'upgrade' files (the kernel is just the kernel file that's in the kernel package in the same tree), and that's what it adds to the bootloader config, the environment you boot into after the first fedup phase has downloaded all the packages and told you to reboot to continue. If you *don't* pass a --instrepo parameter, what fedup does is it asks mirrormanager for the location: it asks mirrormanager for a mirror list for the 'fedora-install' repository for the release you specified you wanted to upgrade to, and the appropriate arch. You can do the same thing through mirror manager's web interface: https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-install-21&arch=x86_64 So if you just say 'fedup --network 21' on an x86_64 system, fedup goes and asks mirrormanager for that list of repos, then picks one and uses it as the 'installation repository'. (When I read your mail the first thing I did was check that URL and make sure the list it produced was sane; it does seem to be, so I'm not quite sure why you got a 404. It's possible you hit a bad mirror which didn't have the files in place, I guess?) So now let's see what happens if you try and fedup to 22 without giving it any help: https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-install-22&arch=x86_64 "# repo = fedora-install-22 arch = x86_64 error: invalid repo or arch" Ooops. Well, let's try Rawhide: https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-install-rawhide&arch=x86_64 OK, that's a proper list, so you could try 'fedup --network rawhide'...but wait! What does fedup do with the instrepo? It looks for .treeinfo.signed. Let's check that's available on a mirror from the list: http://fedora.mirror.nexicom.net/linux/development/rawhide/x86_64/os/.treeinfo.signed ... 404. Oh dear. First problem here is, Rawhide trees generally aren't signed. So, you'd also have to pass --nogpgcheck; this will make it look for the un-signed version of the file instead, which is just .treeinfo : http://fedora.mirror.nexicom.net/linux/development/rawhide/x86_64/os/.treeinfo ... 404. Well pants! Why, you wonder? Because the nightly compose attempt failed. There's an automated attempt to 'compose' the Rawhide (and Branched, when it exists) tree nightly. That's the process that generates all the images you see mentioned in the .treeinfo file - the upgrade initramfs, but also boot.iso and various other bits and pieces. It doesn't always work. When
Re: fedup: boot image not found
> On Dec 15, 2014, at 9:12 AM, Adam Williamson > wrote: > > On Mon, 2014-12-15 at 16:40 +, Brian McGrew wrote: >> Good morning all, >> >> Running fedup and getting the following on a stock install of F20: >> >> [admin@knotts ~]$ sudo fedup --network 21 --product=workstation >> [sudo] password for admin: >> setting up repos... >> getting boot images... >> >> Downloading failed: couldn't get boot images: No more mirrors to >> try. Last error was: [Errno 14] HTTP Error 404 - Not Found >> >> >> [admin@knotts ~]$ sudo fedup --network rawhide --product=workstation >> setting up repos... >> getting boot images... >> >> Downloading failed: couldn't get boot images: No more mirrors to >> try. Last error was: [Errno 14] HTTP Error 404 - Not Found >> [admin@knotts ~]$ > > Can't immediately see a good reason it isn't working, does it work > with --instrepo= > https://dl.fedoraproject.org/pub/fedora/linux/releases/21/Server/x86_64/os/ ? > (assuming x86_64, of > course) Of course x86_64! That appears to be working. Odd! Will let you know if it doesn’t finish. I’ll get to 21 and then to rawhide and see what happens. Thanks, -b > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net > http://www.happyassassin.net > > -- > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: fedup: boot image not found
On Mon, 2014-12-15 at 16:40 +, Brian McGrew wrote: > Good morning all, > > Running fedup and getting the following on a stock install of F20: > > [admin@knotts ~]$ sudo fedup --network 21 --product=workstation > [sudo] password for admin: > setting up repos... > getting boot images... > > Downloading failed: couldn't get boot images: No more mirrors to > try. Last error was: [Errno 14] HTTP Error 404 - Not Found > > > [admin@knotts ~]$ sudo fedup --network rawhide --product=workstation > setting up repos... > getting boot images... > > Downloading failed: couldn't get boot images: No more mirrors to > try. Last error was: [Errno 14] HTTP Error 404 - Not Found > [admin@knotts ~]$ Can't immediately see a good reason it isn't working, does it work with --instrepo= https://dl.fedoraproject.org/pub/fedora/linux/releases/21/Server/x86_64/os/ ? (assuming x86_64, of course) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
