sekikn commented on PR #908:
URL: https://github.com/apache/bigtop/pull/908#issuecomment-1152458830

   @vivostar @iwasakims
   
   > I don't know the context of the thread. If you know the specific failure 
scenario (distro/arch), let me know.
   
   I was not involved in the discussion in question directly, but as far as I 
investigated and tried, puppetlabs doesn't seem to support ppc64le.
   
   Steps to reproduce are as follows. I ran them on Ubuntu 22.04.
   
   1. Download CentOS 7 image for ppc64le from any mirror site listed in 
http://isoredirect.centos.org/altarch/7/isos/ppc64le/.
   2. Create VM using the downloaded image (configure parameters in accordance 
with your environment):
   
   ```
   $ sudo apt-get install -y libvirt-clients virtinst libvirt-daemon-system 
qemu-utils qemu-system-ppc
   $ sudo virt-install --name=c7ppc --ram=8192 --vcpus=4 
--network=bridge=virbr0,model=virtio --os-variant=rhel7.9 --arch=ppc64le 
--machine=pseries-2.12 
--disk=/var/lib/libvirt/images/c7ppc.img,format=qcow2,size=20 
--cdrom=CentOS-7-ppc64le-Minimal-2009.iso --serial=pty --console=pty --boot=hd 
--graphics=none
   ```
   
   3. Test this PR in the created VM:
   
   ```
   $ sudo yum update -y
   $ sudo yum install -y curl git unzip wget
   $ git clone https://github.com/apache/bigtop.git
   $ cd bigtop
   $ curl -sL https://github.com/apache/bigtop/pull/908.patch | git apply
   $ sudo bigtop_toolchain/bin/puppetize.sh
   
   ...
   
   failure: repodata/repomd.xml from puppet7: [Errno 256] No more mirrors to 
try.
   http://yum.puppetlabs.com/puppet7/el/7/ppc64le/repodata/repomd.xml: [Errno 
14] HTTP Error 404 - Not Found
   bigtop_toolchain/bin/puppetize.sh: line 60: /opt/puppetlabs/bin/puppet: No 
such file or directory
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to