You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Naresh Bhat (JIRA)" <ji...@apache.org> on 2017/07/03 07:20:00 UTC
[jira] [Updated] (BIGTOP-2794) [bigtop-puppet] Support CentOS 7
AArch64 bigtop puppet
[ https://issues.apache.org/jira/browse/BIGTOP-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Naresh Bhat updated BIGTOP-2794:
--------------------------------
Attachment: BIGTOP-2794_v1.patch
The image has been tagged as "7" - https://hub.docker.com/r/centos/aarch64/tags/
I have used the same in attached v1 patch. The puppetize.sh script installs the http://yum.puppetlabs.com/puppetlabs-release-el-7.noarch.rpm and after that it is unable to issue any "yum install <package>" command because which throws out the below error message
...
..........
Step 4 : RUN bash /tmp/puppetize.sh
---> Running in 42d468887cf8
warning: /var/tmp/rpm-tmp.myjx4s: Header V4 RSA/SHA1 Signature, key ID ef8d349f: NOKEY
Retrieving http://yum.puppetlabs.com/puppetlabs-release-el-7.noarch.rpm
Preparing... ########################################
Updating / installing...
puppetlabs-release-22.0-2 ########################################
Loaded plugins: fastestmirror, ovl
http://yum.puppetlabs.com/el/7/dependencies/aarch64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below knowledge base article
https://access.redhat.com/articles/1320623
If above article doesn't help to resolve this issue please create a bug on https://bugs.centos.org/
One of the configured repositories failed (Puppet Labs Dependencies El 7 - aarch64),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=puppetlabs-deps ...
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable puppetlabs-deps
or
subscription-manager repos --disable=puppetlabs-deps
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=puppetlabs-deps.skip_if_unavailable=true
failure: repodata/repomd.xml from puppetlabs-deps: [Errno 256] No more mirrors to try.
http://yum.puppetlabs.com/el/7/dependencies/aarch64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
/tmp/puppetize.sh: line 83: puppet: command not found
---> 774ffc05bfb6
Removing intermediate container 42d468887cf8
Successfully built 774ffc05bfb6
[centos@localhost centos-7-aarch64]$
Hence I am just thinking is it required to install the RPM ?
Can I skip it by modifying the puppetize.sh script ?
> [bigtop-puppet] Support CentOS 7 AArch64 bigtop puppet
> ------------------------------------------------------
>
> Key: BIGTOP-2794
> URL: https://issues.apache.org/jira/browse/BIGTOP-2794
> Project: Bigtop
> Issue Type: Improvement
> Components: docker
> Affects Versions: 1.2.0
> Environment: Cavium ThunderX2 server hardware (AArch64)
> Reporter: Naresh Bhat
> Fix For: 1.3.0
>
> Attachments: BIGTOP-2794.patch, BIGTOP-2794_v1.patch
>
>
> This jira issue is used to create and support docker/bigtop-puppet/centos-7-aarch64
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)