Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
1.3.0, 1.4.0
-
None
-
None
-
Windows 10
Vagrant 2.2.7
Description
Steps to reproduce:
- Install Vagrant
- Download and untar 1.4.0 tarball from the site
- cd bigtop/provisioner/vargant
- Follow the steps in README up to and including first 'vagrant up' (no changes to config files)
Expected results:
At least four services (namenode, resourcemanager, proxyserver, historyserver) in running state (according to systemd).
Actual results:
The four above mentioned services in failed state (according to systemd), and installation script failed.
Yet OS processes up and running for all four services, according to ps.
Attachments
Attachments
Issue Links
- Blocked
-
BIGTOP-3302 init scripts using su do not work on recent systemd
- Resolved
- duplicates
-
BIGTOP-3302 init scripts using su do not work on recent systemd
- Resolved