Please, make available a F32-PPC64le test machine as soon as possible, i need to debug a F32 package on that architecture.
Metadata Update from @smooge: - Issue assigned to kevin - Issue priority set to: Waiting on Assignee (was: Needs Review)
You can use a mock chroot to test other releases...
I can try and upgrade the existing machine.
ppc64le-test.fedorainfracloud.org with Fedora 31 prevents using F32 chroot for GPG keys issues.
ppc64le-test.fedorainfracloud.org
That just needs the updated mock. I have updated it, try again now?
Next weekend
ok. Please re-open if that doesn't work...
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @sagitter: - Issue status updated to: Open (was: Closed)
F32-buildroot still does not work on ppc64le-test.fedorainfracloud.org:
<img alt="F32-buildroot_on_ppc64le-test.zip" src="/fedora-infrastructure/issue/raw/files/c84d3fc64c87e95d484f8d0ac5dc747c9655dde851826247c21d7c20168e256f-F32-buildroot_on_ppc64le-test.zip" />
oops. I didn't also update mock-core-configs (I forgot they split those out). So it was trying to install rawhide packages (signed by the f33 key) in a fedora 32 chroot.
Ive updated those and confiirmed it works for me now.
Can you try and see if it works for you?
[sagitter@ppc64le-test ~][PROD]$ mock -r fedora-32-ppc64le --init INFO: mock.py version 2.0 starting (python version = 3.7.6)... Start(bootstrap): init plugins INFO: selinux enabled Finish(bootstrap): init plugins Start: init plugins INFO: selinux enabled Finish: init plugins INFO: Signal handler active Start: run Start: clean chroot Finish: clean chroot Start(bootstrap): chroot init INFO: calling preinit hooks INFO: enabled root cache INFO: enabled package manager cache Start(bootstrap): cleaning package manager metadata Finish(bootstrap): cleaning package manager metadata INFO: enabled HW Info plugin Mock Version: 2.0 INFO: Mock Version: 2.0 Finish(bootstrap): chroot init Start: chroot init INFO: calling preinit hooks INFO: enabled root cache Start: unpacking root cache Finish: unpacking root cache INFO: enabled package manager cache Start: cleaning package manager metadata Finish: cleaning package manager metadata INFO: enabled HW Info plugin Mock Version: 2.0 INFO: Mock Version: 2.0 ERROR: Command failed: # /usr/bin/systemd-nspawn -q -M 4f81519fca5c44129f5de561f69f8f04 -D /var/lib/mock/fedora-32-ppc64le/root -a --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin --setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007" --setenv=PS1=<mock-chroot> \s-\v\$ --setenv=LANG=en_US.UTF-8 /usr/sbin/usermod -u 151390 --non-unique mockbuild
ppc64le-test.fedorainfracloud.org is still active? i can't connect.
It is not. I meant to try and update this ticket before now.
The openstack cloud that had this instance in it has been decomissioned.
We plan to bring up new instances, but it might not be for a while as we need to ship servers to a new site, etc.
@sharkcz is there a ppc64le instance you could help @sagitter use in the mean time or help them track down the issue they are hitting?
We have a backup solution for such cases in form of a public VM. @sagitter, send me an email with your public ssh key.
@kevin, I'm thinking about spinning up a dedicated VM in the OpenPOWER hub Brno, that could replace ppc64le-test until there is the new Fedora cloud again. I suppose you manage everything via ansible, so a VM with public IP address and loaded public ssh should allow you to deploy all the required setup. Am I right or are there other conditions too?
Yes, thats it. If you can setup something we could set it's dns and just run the existing playbook against it if you like.
That does allow access by all fedora packagers.
Ack, I've asked @mruprich to prepare the VM.
@sagitter, send me an email with your public ssh key.
Sent.
Yes, thats it. If you can setup something we could set it's dns and just run the existing playbook against it if you like. That does allow access by all fedora packagers. Hi, do you have some specific requirements regarding VM? Some specific HW? Do you need a public IP? Also, I didn't find F32 on ppc64, the latest I can get my hands on is F31. I guess we an just use F31 and than change repos to f32?
@mruprich, you should have an email with the details :-) F-31 is the right version
@mruprich, you should have an email with the details :-) F-31 is the right version Got it, thanks :)
@kevin, what public ssh key do you need to be present for ansible?
https://infrastructure.fedoraproject.org/infra/ssh/admin.pub has the one
@kevin The machine is ready for you. You can access it like this: ssh kevin@rh-power-vm14.fit.vutbr.cz The specs are these: CPU(s): 4 Max memory: 8388608 KiB Used memory: 8388608 KiB virtual size: 40G (42949672960 bytes)
You have sudo access and you can do whatever you want with the VM. Let me know that it works. If anything goes wrong, just ping me or @sharkcz
ok, the machine is all setup as ppc64le-test.fedorainfracloud.org
I can confirm a f32 mock chroot works.
@sagitter please re-open this if you still see an issue we need to address here.
@sharkcz and @mruprich Thanks so much for the temp test machine. Will let you know when we have stuff moved and up in a new datacenter to take over.
Thank you all.
@sharkcz and @mruprich The machine seems to be down... can you check on it?
it's up again, I have to reboot it, I suspect it's some DHCP glitch, we have met already, the VM runs, but loses IP address
Login to comment on this ticket.