Mine doesn't work still. Probably the env issue since I'm away from the
field...
Anyhow. Updating the default value sounds good to me. We can address it in
later developments.
ERROR LOG:
---
$ vagrant destroy -f; vagrant up
/Users/eyeh/.vagrant.d/gems/2.4.4/gems/rubyhacks-0.1.5/lib/rubyhacks.rb:536:
warning: constant ::Fixnum is deprecated
vagrant conf local repo enabled: false
Adding output/ repo ? false
==> bigtop1: Forcing shutdown of VM...
==> bigtop1: Destroying VM and associated drives...
==> bigtop1: [vagrant-hostmanager:guests] Updating hosts file on active
guest virtual machines...
/Users/eyeh/.vagrant.d/gems/2.4.4/gems/rubyhacks-0.1.5/lib/rubyhacks.rb:536:
warning: constant ::Fixnum is deprecated
vagrant conf local repo enabled: false
Adding output/ repo ? false
Bringing machine 'bigtop1' up with 'virtualbox' provider...
==> bigtop1: Importing base box 'centos/7'...
==> bigtop1: Matching MAC address for NAT networking...
==> bigtop1: Checking if box 'centos/7' version '2004.01' is up to date...
==> bigtop1: Setting the name of the VM: vagrant_bigtop1_1607841501336_78663
==> bigtop1: Clearing any previously set network interfaces...
==> bigtop1: Preparing network interfaces based on configuration...
bigtop1: Adapter 1: nat
bigtop1: Adapter 2: hostonly
==> bigtop1: Forwarding ports...
bigtop1: 22 (guest) => 2222 (host) (adapter 1)
==> bigtop1: Running 'pre-boot' VM customizations...
==> bigtop1: Booting VM...
==> bigtop1: Waiting for machine to boot. This may take a few minutes...
bigtop1: SSH address: 127.0.0.1:2222
bigtop1: SSH username: vagrant
bigtop1: SSH auth method: private key
bigtop1:
bigtop1: Vagrant insecure key detected. Vagrant will automatically
replace
bigtop1: this with a newly generated keypair for better security.
bigtop1:
bigtop1: Inserting generated public key within guest...
bigtop1: Removing insecure key from the guest if it's present...
bigtop1: Key inserted! Disconnecting and reconnecting using new SSH
key...
==> bigtop1: Machine booted and ready!
[bigtop1] No Virtualbox Guest Additions installation found.
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: ftp.tc.edu.tw
* extras: ftp.tc.edu.tw
* updates: ftp.tc.edu.tw
Resolving Dependencies
--> Running transaction check
---> Package centos-release.x86_64 0:7-8.2003.0.el7.centos will be updated
---> Package centos-release.x86_64 0:7-9.2009.1.el7.centos will be an update
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository
Size
================================================================================
Updating:
centos-release x86_64 7-9.2009.1.el7.centos updates
27 k
Transaction Summary
================================================================================
Upgrade 1 Package
Total download size: 27 k
Downloading packages:
No Presto metadata available for updates
Public key for centos-release-7-9.2009.1.el7.centos.x86_64.rpm is not
installed
warning:
/var/cache/yum/x86_64/7/updates/packages/centos-release-7-9.2009.1.el7.centos.x86_64.rpm:
Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
Importing GPG key 0xF4A80EB5:
Userid : "CentOS-7 Key (CentOS 7 Official Signing Key) <
[email protected]>"
Fingerprint: 6341 ab27 53d7 8a78 a7c2 7bb1 24c6 a8a7 f4a8 0eb5
Package : centos-release-7-8.2003.0.el7.centos.x86_64 (@anaconda)
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Updating : centos-release-7-9.2009.1.el7.centos.x86_64
1/2
Cleanup : centos-release-7-8.2003.0.el7.centos.x86_64
2/2
Verifying : centos-release-7-9.2009.1.el7.centos.x86_64
1/2
Verifying : centos-release-7-8.2003.0.el7.centos.x86_64
2/2
Updated:
centos-release.x86_64 0:7-9.2009.1.el7.centos
Complete!
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: ftp.tc.edu.tw
* extras: ftp.tc.edu.tw
* updates: ftp.tc.edu.tw
No package kernel-devel-3.10.0-1127.el7.x86_64 available.
Error: Nothing to do
Unmounting Virtualbox Guest Additions ISO from: /mnt
umount: /mnt: not mounted
==> bigtop1: Checking for guest additions in VM...
bigtop1: No guest additions were detected on the base box for this VM!
Guest
bigtop1: additions are required for forwarded ports, shared folders,
host only
bigtop1: networking, and more. If SSH fails on this machine, please
install
bigtop1: the guest additions and repackage the box to continue.
bigtop1:
bigtop1: This is not an error message; everything may continue to work
properly,
bigtop1: in which case you may ignore this message.
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
umount /mnt
Stdout from the command:
Stderr from the command:
umount: /mnt: not mounted
---
Kengo Seki <[email protected]> 於 2020年12月13日 週日 上午8:37寫道：
> Hi Evans,
>
> In my environment, using the latest official CentOS image instead of
> puppetlabs' one seems to work, as follows.
> So I don't think we have to drop the Vagrant provisioner in this
> release and would like to propose to simply update default values in
> vagrantconfig.yaml,
> but I'm not also strongly against dropping it if you think we should
> reduce maintenance cost on it in this opportunity. :)
>
> ```
> ~/repos/bigtop/provisioner/vagrant$ git diff
> diff --git a/provisioner/vagrant/vagrantconfig.yaml
> b/provisioner/vagrant/vagrantconfig.yaml
> index a25690d2..bee87293 100644
> --- a/provisioner/vagrant/vagrantconfig.yaml
> +++ b/provisioner/vagrant/vagrantconfig.yaml
> @@ -15,8 +15,8 @@
>
> memory_size: 4096
> number_cpus: 1
> -box: "puppetlabs/centos-7.2-64-nocm"
> -repo: "http://repos.bigtop.apache.org/releases/1.3.0/centos/7/x86_64";
> +box: "centos/7"
> +repo: "http://repos.bigtop.apache.org/releases/1.5.0/centos/7/x86_64";
> num_instances: 1
> distro: centos
> components: [hdfs, yarn, mapreduce]
> ~/repos/bigtop/provisioner/vagrant$ vagrant up
>
> (snip)
>
> ==> bigtop1: Notice: Roles to deploy: [resourcemanager, nodemanager,
> mapred-app, hadoop-client, mapred-app, namenode, datanode]
>
> (snip)
>
> ==> bigtop1: Notice: Finished catalog run in 364.53 seconds
> ==> bigtop1: Configuring cache buckets...
> ~/repos/bigtop/provisioner/vagrant$ vagrant ssh
>
> (snip)
>
> [vagrant@bigtop1 ~]$ sudo jps
> 3812 JobHistoryServer
> 4212 NameNode
> 5993 Jps
> 3978 NodeManager
> 3531 ResourceManager
> 3438 WebAppProxyServer
> 4447 DataNode
> [vagrant@bigtop1 ~]$ hadoop version
> Hadoop 2.10.1
> Subversion https://gitbox.apache.org/repos/asf/bigtop.git -r
> 81ad7b000cec0503b9a1d5521fdaf0129443b536
> Compiled by jenkins on 2020-11-28T10:07Z
> Compiled with protoc 2.5.0
> From source with checksum 12fc83747448c6d239c8a4e93b4fa294
> This command was run using /usr/lib/hadoop/hadoop-common-2.10.1.jar
> [vagrant@bigtop1 ~]$ sudo -u yarn yarn jar
> /usr/lib/hadoop-mapreduce/hadoop-mapreduce-examples.jar pi 1 1
>
> (snip)
>
> Job Finished in 29.655 seconds
> Estimated value of Pi is 4.00000000000000000000
> ```
>
> Kengo Seki <[email protected]>
>
> On Sun, Dec 13, 2020 at 12:40 AM Evans Ye <[email protected]> wrote:
> >
> > I think having that malfunction feature removed is better to make 1.5
> > release quality stay untainted. If go for RC1 the effort is small since
> > all the build/repo/artifacts can stay AS-IS. Just the code need to be
> > modified.
> > However, you're right that it's for testing purpose so either way is ok.
> >
> > I don't think this worth to block the release though. I can still fire
> up a
> > JIRA for tracking.
> >
> > Luca Toscano <[email protected]> 於 2020年12月12日 週六 下午7:53寫道：
> >
> > > Hi Evans,
> > >
> > > I don't know exactly what it is the typical use case for the Vagrant
> > > provisioner, but I guess it should be mostly testing, so I think it
> > > should be fine for the purposes of the 1.5 release to leave it aside
> > > (and fix it later on).
> > > Do you have more details about the systemd failure? Maybe we could
> > > open a quick jira with details so people can chime in and check, to
> > > speed up the release :)
> > >
> > > Luca
> > >
> > > On Sat, Dec 12, 2020 at 10:55 AM Evans Ye <[email protected]> wrote:
> > > >
> > > > I'm still running tests but one thing need to discuss with folks
> first.
> > > >
> > > > The provisioner/vagrant component is failing in my test.
> > > >
> > > > ==> bigtop1: Error: Could not start Service[hadoop-yarn-proxyserver]:
> > > > Execution of '/bin/systemctl start hadoop-yarn-proxyserver' returned
> 1:
> > > Job
> > > > for hadoop-yarn-proxyserver.service failed. See "systemctl status
> > > > hadoop-yarn-proxyserver.service" and "journalctl -xe" for details.
> > > >
> > > > Seems it's due to the systemd changing. I searched on vagrant box
> but I
> > > see
> > > > NO NEW box for centos/ubuntu from puppetlabs. Also, our CI test does
> not
> > > > cover this component so it's likely to have bug down the road.
> Therefore,
> > > > I'm proposing to remove the component in 1.5 release. How do the
> folks
> > > > think?
> > > >
> > > > Evans
> > > >
> > > >
> > > > Kengo Seki <[email protected]> 於 2020年12月8日 週二 下午9:55寫道：
> > > >
> > > > > Luca and Evans,
> > > > >
> > > > > Thank you for testing the RC! Sure, I think we can wait for that
> until
> > > > > this weekend :)
> > > > >
> > > > > Kengo Seki <[email protected]>
> > > > >
> > > > > On Tue, Dec 8, 2020 at 6:24 PM Evans Ye <[email protected]>
> wrote:
> > > > > >
> > > > > > I'm really happy to see the release candidate is finally out.
> > > > > > With this timing the community will close this year with a strong
> > > result.
> > > > > > Thank you all for the efforts!
> > > > > > Let me find time this week to evaluate and vote.
> > > > > >
> > > > > > - Evans
> > > > > >
> > > > > > Luca Toscano <[email protected]> 於 2020年12月8日 週二 下午4:47寫道：
> > > > > >
> > > > > > > Hi!
> > > > > > >
> > > > > > > On Mon, Dec 7, 2020 at 12:47 AM Kengo Seki <[email protected]>
> > > wrote:
> > > > > > > >
> > > > > > > > This is the vote for release 1.5.0 of Apache Bigtop.
> > > > > > > >
> > > > > > > > It fixes the following issues:
> > > > > > > >
> > > > > > >
> > > > >
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311420&version=12345178
> > > > > > > >
> > > > > > > > The vote will be going for at least 72 hours and will be
> closed
> > > on
> > > > > > > Wednesday,
> > > > > > > > December 9th, 2020 at 5pm PST. Please download, test and vote
> > > with
> > > > > > >
> > > > > > > This is a great news, really glad to see 1.5.0 finally coming
> out!
> > > I
> > > > > > > might be able to try the debian-9 packages on a testing cluster
> > > with
> > > > > > > Bigtop 1.4 + Kerberos by the end of this week, but it would
> delay a
> > > > > > > bit the 72h. If this is ok, I'll keep this list posted with
> result
> > > (or
> > > > > > > if I don't manage to test properly).
> > > > > > >
> > > > > > > Luca
> > > > > > >
> > > > >
> > >
>
