You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Evans Ye (JIRA)" <ji...@apache.org> on 2019/02/12 09:24:00 UTC
[jira] [Comment Edited] (BIGTOP-3161) Upgrade to Puppet 5.X
[ https://issues.apache.org/jira/browse/BIGTOP-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765827#comment-16765827 ]
Evans Ye edited comment on BIGTOP-3161 at 2/12/19 9:23 AM:
-----------------------------------------------------------
During development, I found that the newest version of puppetlabs-apt can lead to dependency cycle:
{code}
# Error: Found 1 dependency cycle:
# (Package[apt-transport-https] => Apt::Source[Bigtop_0] => Package[apt-transport-https])\nTry the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz
# Error: Failed to apply catalog: One or more resource dependency cycles detected in graph
{code}
The root cause is that the apt module did Package install of apt-transport-https behind the scene...
https://github.com/puppetlabs/puppetlabs-apt/commit/bbec706b5da9d9e2ea0bedbc73be8d38f31d4cd8#diff-a3efcdc2c485949d50da5816e90d89deR38
An workaround is to pin the version to 6.2.1
TL;DR:
Why 6.2.1 is working? Cause there's a bug for ensuring the installation of apt-transport-https, which has been fixed in 6.3.0:
https://github.com/puppetlabs/puppetlabs-apt/blob/6.3.0/manifests/source.pp#L91-L92
was (Author: evans_ye):
During development, I found that the newest version of puppetlabs-apt can lead to dependency cycle:
{code}
# Error: Found 1 dependency cycle:
# (Package[apt-transport-https] => Apt::Source[Bigtop_0] => Package[apt-transport-https])\nTry the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz
# Error: Failed to apply catalog: One or more resource dependency cycles detected in graph
{code}
The root cause is that the apt module did Package install of apt-transport-https behind the scene...
https://github.com/puppetlabs/puppetlabs-apt/commit/bbec706b5da9d9e2ea0bedbc73be8d38f31d4cd8#diff-a3efcdc2c485949d50da5816e90d89deR38
An workaround is to pin the version to 6.2.1
> Upgrade to Puppet 5.X
> ---------------------
>
> Key: BIGTOP-3161
> URL: https://issues.apache.org/jira/browse/BIGTOP-3161
> Project: Bigtop
> Issue Type: Sub-task
> Components: build, deployment
> Affects Versions: 1.3.0
> Reporter: Evans Ye
> Assignee: Evans Ye
> Priority: Major
>
> The puppet version for Bigtop Puppet is quite old and inconsistent across platforms. Fore example, we have 3.6 on centos 7 but 4.6 on fedora, which cause various of compatibility problems. One recent example is deploying Alluxio BIGTOP-3159. It's time to bump the version of puppet up to a recent one, and sync the puppet version across platforms supported by Bigtop.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)