You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Kengo Seki (Jira)" <ji...@apache.org> on 2020/07/03 07:14:00 UTC
[jira] [Comment Edited] (BIGTOP-3277) Update deploy manifests to
support newly added distros in v1.5.0
[ https://issues.apache.org/jira/browse/BIGTOP-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150781#comment-17150781 ]
Kengo Seki edited comment on BIGTOP-3277 at 7/3/20, 7:13 AM:
-------------------------------------------------------------
Regarding the second problem, I still have not figured out why the conflict happens.
Puppet seems to give higher priority to the Bigtop repo correctly:
{code:java}
vagrant@debian10:~/bigtop$ cat /etc/apt/sources.list.d/Bigtop_0.list
# This file is managed by Puppet. DO NOT EDIT.
# Bigtop_0
deb file:///home/vagrant/bigtop/output/apt bigtop contrib
vagrant@debian10:~/bigtop$ cat /etc/apt/preferences.d/Bigtop_0.pref
# This file is managed by Puppet. DO NOT EDIT.
Explanation: apt: Bigtop_0
Package: *
Pin: origin home
Pin-Priority: 900
{code}
But the repository is regarded as priority 500 for some reason.
{code:java}
vagrant@debian10:~/bigtop$ sudo apt-cache policy
Package files:
(snip)
500 file:/home/vagrant/bigtop/output/apt bigtop/contrib amd64 Packages
release v=1.5.0-SNAPSHOT,o=Bigtop,a=stable,n=bigtop,l=Bigtop,c=contrib,b=amd64
500 http://deb.debian.org/debian buster-updates/main amd64 Packages
release o=Debian,a=stable-updates,n=buster-updates,l=Debian,c=main,b=amd64
origin deb.debian.org
500 http://security.debian.org/debian-security buster/updates/main amd64 Packages
release v=10,o=Debian,a=stable,n=buster,l=Debian-Security,c=main,b=amd64
origin security.debian.org
500 http://deb.debian.org/debian buster/main amd64 Packages
release v=10.4,o=Debian,a=stable,n=buster,l=Debian,c=main,b=amd64
origin deb.debian.org
Pinned packages:
vagrant@debian10:~/bigtop$ sudo apt-cache policy zookeeper
zookeeper:
Installed: (none)
Candidate: 3.4.13-2
Version table:
3.4.13-2 500
500 http://deb.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status
3.4.13-1 500
500 file:/home/vagrant/bigtop/output/apt bigtop/contrib amd64 Packages
{code}
Maybe I'm missing something.
was (Author: sekikn):
Regarding the second problem, I still have not figured out why the conflict happens.
Puppet seems to give higher priority to the Bigtop repo correctly:
{code}
vagrant@debian10:~/bigtop$ cat /etc/apt/sources.list.d/Bigtop_0.list
# This file is managed by Puppet. DO NOT EDIT.
# Bigtop_0
deb file:///home/vagrant/bigtop/output/apt bigtop contrib
vagrant@debian10:~/bigtop$ cat /etc/apt/preferences.d/Bigtop_0.pref
# This file is managed by Puppet. DO NOT EDIT.
Explanation: apt: Bigtop_0
Package: *
Pin: origin home
Pin-Priority: 900
{code}
But the repository is regarded as priority 500 for some reason.
{code}
vagrant@debian10:~/bigtop$ sudo apt-cache policy
Package files:
(snip)
500 file:/home/vagrant/bigtop/output/apt bigtop/contrib amd64 Packages
release v=1.5.0-SNAPSHOT,o=Bigtop,a=stable,n=bigtop,l=Bigtop,c=contrib,b=amd64
500 http://deb.debian.org/debian buster-updates/main amd64 Packages
release o=Debian,a=stable-updates,n=buster-updates,l=Debian,c=main,b=amd64
origin deb.debian.org
500 http://security.debian.org/debian-security buster/updates/main amd64 Packages
release v=10,o=Debian,a=stable,n=buster,l=Debian-Security,c=main,b=amd64
origin security.debian.org
500 http://deb.debian.org/debian buster/main amd64 Packages
release v=10.4,o=Debian,a=stable,n=buster,l=Debian,c=main,b=amd64
origin deb.debian.org
Pinned packages:
vagrant@debian10:~/bigtop$
{code}
Maybe I'm missing something.
> Update deploy manifests to support newly added distros in v1.5.0
> ----------------------------------------------------------------
>
> Key: BIGTOP-3277
> URL: https://issues.apache.org/jira/browse/BIGTOP-3277
> Project: Bigtop
> Issue Type: Sub-task
> Components: deployment
> Affects Versions: 1.4.0
> Reporter: Kengo Seki
> Assignee: Kengo Seki
> Priority: Major
>
> The current deploy manifests seem to work with most of distros we support in v1.5.0 as they are, but we have to address at least the following issues on Debian 10:
> 1. In case that JDK is not pre-installed, the current bigtop-deploy/puppet/manifests/jdk.pp doesn't work. It should be fixed as BIGTOP-3343.
> {code:java}
> Error: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install openjdk-8-jdk' returned 100: Reading package lists...
> Building dependency tree...
> Reading state information...
> E: Unable to locate package openjdk-8-jdk
> Error: /Stage[main]/Jdk/Package[jdk]/ensure: change from 'purged' to 'present' failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install openjdk-8-jdk' returned 100: Reading package lists...
> Building dependency tree...
> Reading state information...
> E: Unable to locate package openjdk-8-jdk
> {code}
> 2. Debian 10 has a "zookeeper" package by default, so we have to give ours higher priority somehow.
> {code:java}
> Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install zookeeper-server' returned 100: Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> The following packages have unmet dependencies:
> zookeeper-server : Depends: zookeeper (= 3.4.13-1) but 3.4.13-2 is to be installed
> E: Unable to correct problems, you have held broken packages.
> Error: /Stage[main]/Hadoop_zookeeper::Server/Package[zookeeper-server]/ensure: change from 'purged' to 'latest' failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install zookeeper-server' returned 100: Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> The following packages have unmet dependencies:
> zookeeper-server : Depends: zookeeper (= 3.4.13-1) but 3.4.13-2 is to be installed
> E: Unable to correct problems, you have held broken packages.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)