[
https://issues.apache.org/jira/browse/RYA-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David W. Lotts resolved RYA-54.
-------------------------------
Resolution: Fixed
> Rya vagrant script difficult to see failures
> --------------------------------------------
>
> Key: RYA-54
> URL: https://issues.apache.org/jira/browse/RYA-54
> Project: Rya
> Issue Type: Bug
> Components: examples
> Environment: Rya in a VM
> Reporter: David W. Lotts
> Assignee: David W. Lotts
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Rya example virtual machine is a wonderful way for new users to get up and
> running fast and have a positive first experience with Rya.
> Several folks have attempted to create the Rya example virtual machine and
> produce an unusable Rya instance on the first try. They have no clue what
> went wrong since they saw no errors and it appeared to complete successfully.
> Only when they attempt to use the web interface do they see errors.
> The relevent files are here:
> https://github.com/apache/incubator-rya/tree/develop/extras/vagrantExample/src/main/vagrant
> There are several reasons for this having to do with the {{Vagrant up}}
> command that runs the Vagrantfile, a combination of vagrant specific syntax,
> and Bash shell script:
> - The curl download utility produces a nice progress output meant for a
> terminal, but Vagrant adds newlines so that it scrolls and fills up the
> terminal buffer obscuring any errors messages that occur.
> - Most failures are tolerated and allow the process to continue even when the
> failure creates an unusable VM.
> - Running the command {{vagrant provision}} is not idempotent. When run more
> than once, it should reset the configuration as it was installed, making it a
> handy repair tool, however it generates false errors and fails. Also, it
> re-downloads very large files that are already present, making it no better
> than starting over.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
