Why does fastlane add_badge work for me locally but fail on App Center - fastlane

As per the title, if I execute the following (for example) from my local machine, the command succeeds and all my icons get updated correctly:
fastlane addBadge branch_name:staging build_number:1558591886 branch_color:green
However, when the build runs on Visual Studio App Center, it errors with the following output:
[32mDriving the lane 'addBadge' 🚀[0m
[06:46:53]: [32m-----------------------[0m
[06:46:53]: [32m--- Step: add_badge ---[0m
[06:46:53]: [32m-----------------------[0m
[06:46:53]: [32mStart adding badges...[0m
[06:46:54]: './iOS/Assets.xcassets/AppIcons.appiconset/icon120x120.png'
dyld: Symbol not found: _OBJC_CLASS_$_NSFont
Referenced from: /Library/Frameworks/Mono.framework/Versions/5.18.1/lib/libpangocairo-1.0.0.dylib
Expected in: flat namespace
in /Library/Frameworks/Mono.framework/Versions/5.18.1/lib/libpangocairo-1.0.0.dylib
+---------------+----------+
| [33mLane Context[0m |
+---------------+----------+
| PLATFORM_NAME | |
| LANE_NAME | addBadge |
+---------------+----------+
[06:46:54]: [31mNo such file or directory # rb_sysopen - 1558593854-staging-green.svg.png[0m
For App Center, I'm calling the fastlane addBadge command from appcenter-pre-build.sh.
Question: Why is this error happening, what do I do to fix it?
Update 1: After adding --verbose to the addBadge command:
Here's what I get locally:
Driving the lane 'addBadge' 🚀
INFO [2019-05-24 09:58:54.78]: -----------------------
INFO [2019-05-24 09:58:54.78]: --- Step: add_badge ---
INFO [2019-05-24 09:58:54.78]: -----------------------
INFO [2019-05-24 09:58:54.86]: gem 'badge' is already installed
WARN [2019-05-24 09:58:54.87]: Install RSVG to get better results for shields on top of your icon
WARN [2019-05-24 09:58:54.87]:
WARN [2019-05-24 09:58:54.87]: Install it using (RSVG):
INFO [2019-05-24 09:58:54.87]: $ brew install librsvg
WARN [2019-05-24 09:58:54.87]:
DEBUG [2019-05-24 09:58:54.88]: Verbose active... VERSION: 0.10.0
DEBUG [2019-05-24 09:58:54.88]: Parameters: {:shield=>"1558591886-staging-green", :no_badge=>true, :glob=>"{/iOS/Assets.xcassets/AppIcons.appiconset/*.{png,PNG},/Droid/Resources/**/{icon}.{png,PNG}}", :dark=>nil, :alpha=>nil, :alpha_channel=>nil, :custom=>nil, :badge_gravity=>nil, :shield_parameters=>nil, :shield_io_timeout=>nil, :shield_geometry=>nil, :shield_gravity=>nil, :shield_scale=>nil, :shield_no_resize=>nil, :grayscale=>false}
INFO [2019-05-24 09:58:54.88]: Start adding badges...
DEBUG [2019-05-24 09:58:54.88]: Trying to load image from shields.io. Timeout: 10s
DEBUG [2019-05-24 09:58:54.88]: URL: https://img.shields.io/badge/1558591886-staging-green.png
INFO [2019-05-24 09:58:56.36]: './iOS/Assets.xcassets/AppIcons.appiconset/icon120x120.png'
DEBUG [2019-05-24 09:58:56.36]: Adding shields.io image ontop of icon
INFO [2019-05-24 09:58:56.43]: './iOS/Assets.xcassets/AppIcons.appiconset/icon58x58.png'
And here's what's outputted on App Center:
INFO [2019-05-24 00:13:28.42]: [32mDriving the lane 'addBadge' 🚀[0m
INFO [2019-05-24 00:13:28.43]: [32m-----------------------[0m
INFO [2019-05-24 00:13:28.43]: [32m--- Step: add_badge ---[0m
INFO [2019-05-24 00:13:28.43]: [32m-----------------------[0m
INFO [2019-05-24 00:13:28.50]: [32mgem 'badge' is already installed[0m
DEBUG [2019-05-24 00:13:28.51]: [34mVerbose active... VERSION: 0.10.0[0m
DEBUG [2019-05-24 00:13:28.51]: [34mParameters: {:shield=>"1558656638-staging-green", :no_badge=>true, :glob=>"{/iOS/Assets.xcassets/AppIcons.appiconset/*.{png,PNG},/Droid/Resources/**/{icon}.{png,PNG}}", :dark=>nil, :alpha=>nil, :alpha_channel=>nil, :custom=>nil, :badge_gravity=>nil, :shield_parameters=>nil, :shield_io_timeout=>nil, :shield_geometry=>nil, :shield_gravity=>nil, :shield_scale=>nil, :shield_no_resize=>nil, :grayscale=>false}[0m
INFO [2019-05-24 00:13:28.51]: [32mStart adding badges...[0m
DEBUG [2019-05-24 00:13:28.51]: [34mTrying to load image from shields.io. Timeout: 10s[0m
DEBUG [2019-05-24 00:13:28.51]: [34mURL: https://img.shields.io/badge/1558656638-staging-green.svg[0m
INFO [2019-05-24 00:13:29.27]: './iOS/Assets.xcassets/AppIcons.appiconset/icon120x120.png'
DEBUG [2019-05-24 00:13:29.27]: [34mAdding shields.io image ontop of icon[0m
dyld: Symbol not found: _OBJC_CLASS_$_NSFont
Referenced from: /Library/Frameworks/Mono.framework/Versions/5.12.0/lib/libpangocairo-1.0.0.dylib
Expected in: flat namespace
in /Library/Frameworks/Mono.framework/Versions/5.12.0/lib/libpangocairo-1.0.0.dylib
WARN [2019-05-24 00:13:29.34]: [33m[33mLane Context:[0m
INFO [2019-05-24 00:13:29.34]: {:PLATFORM_NAME=>nil, :LANE_NAME=>"addBadge"}
ERROR [2019-05-24 00:13:29.34]: [31mNo such file or directory # rb_sysopen - 1558656638-staging-green.svg.png[0m
It seems like on the build agent, an svg is being requested instead of a png. Could that have something to do with it?

Related

Ubuntu based build agent in AKS cluster giving unexpected error

We were able to successfully add the deployment to Azuredevops Agent pool and could execute the pipeline on them by following the Microsoft docs. But Its throwing strange error related to dynatrace for all the tasks which is getting executed inside them..
/opt/dynatrace/oneagent/agent/bin/1.251.xxxxxxxxxx/any/nodejs/nodejsagent.js:2611
const e = Buffer.allocUnsafe(8), d = 2 ** 32;
^
SyntaxError: Unexpected token *
at createScript (vm.js:56:10)
at Object.runInThisContext (vm.js:97:10)
at Module._compile (module.js:549:28)
at Object.Module._extensions..js (module.js:586:10)
at Module.load (module.js:494:32)
at tryModuleLoad (module.js:453:12)
at Function.Module._load (module.js:445:3)
at Module.require (module.js:504:17)
at module.js:676:12
at Array.forEach (native)
##[error]Exit code 1 returned from process: file name '/azp/externals/node/bin/node', arguments '"/azp/_work/_tasks/PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe/1.158.3/publishbuildartifacts.js"'.
Note:- Same image is tried with the Docker standalone container and where the pipelines are getting executed successfully. Where as when we trigger the pipelines to the AKS based agents (using the same docker image), getting the above syntax error.
Adding the logs which we got from Build-Agent
/azp/_diag/Worker_20221108-092937-utc.log
[2022-11-08 09:29:40Z INFO AgentPluginManager] Loaded task plugin id 'ecxxxxxxx-xxxx-xxxx-xxx-x-xxxxxxe' (main).
[2022-11-08 09:29:40Z INFO WorkerCommandManager] Enable plugin internal command extension.
[2022-11-08 09:29:40Z INFO HostContext] Well known directory 'Bin': '/azp/bin'
[2022-11-08 09:29:40Z INFO HostContext] Well known directory 'Root': '/azp'
[2022-11-08 09:29:40Z INFO HostContext] Well known directory 'Work': '/azp/_work'
[2022-11-08 09:29:40Z INFO HostContext] Well known directory 'Bin': '/azp/bin'
[2022-11-08 09:29:40Z INFO ProcessInvokerWrapper] Starting process:
[2022-11-08 09:29:40Z INFO ProcessInvokerWrapper] File name: '/azp/bin/Agent.PluginHost'
[2022-11-08 09:29:40Z INFO ProcessInvokerWrapper] Arguments: 'task "Agent.Plugins.Repository.CheckoutTask, Agent.Plugins"'
[2022-11-08 09:29:40Z INFO ProcessInvokerWrapper] Working directory: '/azp/_work'
[2022-11-08 09:29:40Z INFO ProcessInvokerWrapper] Require exit code zero: 'True'
[2022-11-08 09:29:40Z INFO ProcessInvokerWrapper] Encoding web name: utf-8 ; code page: '65001'
[2022-11-08 09:29:40Z INFO ProcessInvokerWrapper] Force kill process on cancellation: 'False'
[2022-11-08 09:29:40Z INFO ProcessInvokerWrapper] Redirected STDIN: 'True'
[2022-11-08 09:29:40Z INFO ProcessInvokerWrapper] Persist current code page: 'False'
[2022-11-08 09:29:40Z INFO ProcessInvokerWrapper] Keep redirected STDIN open: 'False'
[2022-11-08 09:29:40Z INFO ProcessInvokerWrapper] High priority process: 'False'
[2022-11-08 09:29:40Z INFO ProcessInvokerWrapper] Failed to update oom_score_adj for PID: 2515.
[2022-11-08 09:29:40Z INFO ProcessInvokerWrapper] System.UnauthorizedAccessException: Access to the path '/proc/2515/oom_score_adj' is denied.
---> System.IO.IOException: Permission denied
--- End of inner exception stack trace ---
at System.IO.FileStream.WriteNative(ReadOnlySpan`1 source)
at System.IO.FileStream.FlushWriteBuffer()
at System.IO.FileStream.Dispose(Boolean disposing)
at System.IO.Stream.Close()
at System.IO.StreamWriter.CloseStreamFromDispose(Boolean disposing)
at System.IO.StreamWriter.Dispose(Boolean disposing)
at System.IO.TextWriter.Dispose()
at System.IO.File.WriteAllText(String path, String contents)
at Microsoft.VisualStudio.Services.Agent.Util.ProcessInvoker.WriteProcessOomScoreAdj(Int32 processId, Int32 oomScoreAdj)

Sonarqube lts-community with docker compose not work

I've been trying to run sonarqube with docker compose for a long time. The database is running but sonarqube is not running. I use portainer for the implementation.
I use the following docker-compose file to start-up sonarqube:
version: "3"
services:
sonarqube:
image: sonarqube:lts-community
container_name: sonarqube
restart: unless-stopped
environment:
- SONARQUBE_JDBC_USERNAME=admin
- SONARQUBE_JDBC_PASSWORD=admin
- SONARQUBE_JDBC_URL=jdbc:postgresql://sonar_db:5432/sonarqube
networks:
- sonarnet
ports:
- "9901:9000"
- "9092:9092"
volumes:
- sonarqube_conf:/opt/sonarqube/conf
- sonarqube_data:/opt/sonarqube/data
- sonarqube_extensions:/opt/sonarqube/extensions
- sonarqube_bundled-plugins:/opt/sonarqube/lib/bundled-plugins
sonar_db:
image: postgres:latest
container_name: sonar_db
restart: unless-stopped
environment:
- POSTGRES_USER=admin
- POSTGRES_PASSWORD=admin
- POSTGRES_DB=sonarqube
volumes:
- sonarqube_db:/var/lib/postgresql10
- postgresql_data:/var/lib/postgresql10/data
networks:
- sonarnet
volumes:
postgresql_data:
sonarqube_bundled-plugins:
sonarqube_conf:
sonarqube_data:
sonarqube_db:
sonarqube_extensions:
networks:
sonarnet:
I get the following error:
2022.07.03 12:32:22 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2022.07.03 12:32:22 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:46345]
2022.07.03 12:32:22 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonarqube/elasticsearch]: /opt/sonarqube/elasticsearch/bin/elasticsearch
2022.07.03 12:32:22 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
warning: no-jdk distributions that do not bundle a JDK are deprecated and will be removed in a future release
2022.07.03 12:32:25 INFO es[][o.e.n.Node] version[7.16.2], pid[37], build[default/tar/2b937c44140b6559905130a8650c64dbd0879cfb/2021-12-18T19:42:46.604893745Z], OS[Linux/5.15.0-40-generic/amd64], JVM[Eclipse Adoptium/OpenJDK 64-Bit Server VM/11.0.13/11.0.13+8]
2022.07.03 12:32:25 INFO es[][o.e.n.Node] JVM home [/opt/java/openjdk]
2022.07.03 12:32:25 INFO es[][o.e.n.Node] JVM arguments [-XX:+UseG1GC, -Djava.io.tmpdir=/opt/sonarqube/temp, -XX:ErrorFile=../logs/es_hs_err_pid%p.log, -Des.networkaddress.cache.ttl=60, -Des.networkaddress.cache.negative.ttl=10, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -Djna.tmpdir=/opt/sonarqube/temp, -XX:-OmitStackTraceInFastThrow, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dio.netty.allocator.numDirectArenas=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Dlog4j2.formatMsgNoLookups=true, -Djava.locale.providers=COMPAT, -Des.enforce.bootstrap.checks=true, -Xmx512m, -Xms512m, -XX:MaxDirectMemorySize=256m, -XX:+HeapDumpOnOutOfMemoryError, -Des.path.home=/opt/sonarqube/elasticsearch, -Des.path.conf=/opt/sonarqube/temp/conf/es, -Des.distribution.flavor=default, -Des.distribution.type=tar, -Des.bundled_jdk=false]
2022.07.03 12:32:25 INFO es[][o.e.p.PluginsService] loaded module [analysis-common]
2022.07.03 12:32:25 INFO es[][o.e.p.PluginsService] loaded module [lang-painless]
2022.07.03 12:32:25 INFO es[][o.e.p.PluginsService] loaded module [parent-join]
2022.07.03 12:32:25 INFO es[][o.e.p.PluginsService] loaded module [reindex]
2022.07.03 12:32:25 INFO es[][o.e.p.PluginsService] loaded module [transport-netty4]
2022.07.03 12:32:25 INFO es[][o.e.p.PluginsService] no plugins loaded
2022.07.03 12:32:25 INFO es[][o.e.e.NodeEnvironment] using [1] data paths, mounts [[/opt/sonarqube/data (/dev/mapper/vg00-lv01)]], net usable_space [205.6gb], net total_space [237.2gb], types [ext4]
2022.07.03 12:32:25 INFO es[][o.e.e.NodeEnvironment] heap size [512mb], compressed ordinary object pointers [true]
2022.07.03 12:32:25 INFO es[][o.e.n.Node] node name [sonarqube], node ID [WAGp0sgmR0GCiwR4b935Hw], cluster name [sonarqube], roles [data_frozen, master, remote_cluster_client, data, data_content, data_hot, data_warm, data_cold, ingest]
2022.07.03 12:32:30 INFO es[][o.e.t.NettyAllocator] creating NettyAllocator with the following configs: [name=unpooled, suggested_max_allocation_size=256kb, factors={es.unsafe.use_unpooled_allocator=null, g1gc_enabled=true, g1gc_region_size=1mb, heap_size=512mb}]
2022.07.03 12:32:30 INFO es[][o.e.d.DiscoveryModule] using discovery type [zen] and seed hosts providers [settings]
2022.07.03 12:32:31 INFO es[][o.e.g.DanglingIndicesState] gateway.auto_import_dangling_indices is disabled, dangling indices will not be automatically detected or imported and must be managed manually
2022.07.03 12:32:31 INFO es[][o.e.n.Node] initialized
2022.07.03 12:32:31 INFO es[][o.e.n.Node] starting ...
2022.07.03 12:32:31 INFO es[][o.e.t.TransportService] publish_address {127.0.0.1:46345}, bound_addresses {127.0.0.1:46345}
2022.07.03 12:32:32 INFO es[][o.e.b.BootstrapChecks] explicitly enforcing bootstrap checks
ERROR: [1] bootstrap checks failed. You must address the points described in the following [1] lines before starting Elasticsearch.
bootstrap check failure [1] of [1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
ERROR: Elasticsearch did not exit normally - check the logs at /opt/sonarqube/logs/sonarqube.log
2022.07.03 12:32:32 INFO es[][o.e.n.Node] stopping ...
2022.07.03 12:32:32 INFO es[][o.e.n.Node] stopped
2022.07.03 12:32:32 INFO es[][o.e.n.Node] closing ...
2022.07.03 12:32:32 INFO es[][o.e.n.Node] closed
2022.07.03 12:32:32 WARN app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [es]: 78
2022.07.03 12:32:32 INFO app[][o.s.a.SchedulerImpl] Process[es] is stopped
2022.07.03 12:32:32 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped
sonarqube image: sonarqube:lts-community (version 8.9.9.56886 )
docker-compose version: 1.27.4
postgres image: 14.4-1
Can anyone help me?

Error while initializing actor system wavesplatform com.protonail.leveldb.jna.LevelDBException

I want to fork the waves blockchain in which I wanted to change the coin. I first change the name of coin in waves node
link : https://github.com/wavesplatform/Waves/blob/version-1.2.x/node/src/main/scala/com/wavesplatform/transaction/assets/exchange/AssetPair.scala
according to the link I deployed on windows and I got this error.
ERROR: 18:28:45,568 ERROR [main] c.w.actor.RootActorSystem$ - Error while initializing actor system wavesplatform com.protonail.leveldb.jna.LevelDBException: IO error: /root/.local/share/waves-testnet/data: Invalid argument
(note : full error is given below)
software details:
openjdk11
ubuntu 18.04LTS
I am deploying in windows through ubuntu 18.04LTS by following steps for installing in windows and installing deb file.
link for installing: https://docs.waves.tech/en/waves-node/how-to-install-a-node/on-windows
command: java -jar node/target/waves-all-1.2.15-DIRTY.jar node/target/classes/application.conf
I got error while initializing it with wavesplatform.
root#WJLP-1220:/mnt/c/Users/swatim/Desktop/wavesProject/Waves/node/target# java -jar waves-all-1.2.15-DIRTY.jar classes/application.conf
2021-01-04 18:28:44,524 INFO [main] c.w.Application$ - Starting...
2021-01-04 18:28:45,082 INFO [ctor.default-dispatcher-4] a.event.slf4j.Slf4jLogger - Slf4jLogger started 2021-01-04 18:28:45,193 INFO [main] c.w.Application$ - Waves v1.2.15-DIRTY Blockchain Id: T
2021-01-04 18:28:45,271 INFO [main] c.w.d.LevelDBFactory$ - Loaded com.wavesplatform.database.jna.LevelDBJNADBFactory with com.wavesplatform.database.jna.LevelDBJNADBFactory#72ba28ee
2021-01-04 18:28:45,568 ERROR [main] c.w.actor.RootActorSystem$ - Error while initializing actor system wavesplatform com.protonail.leveldb.jna.LevelDBException: IO error: /root/.local/share/waves-testnet/data: Invalid argument
at com.protonail.leveldb.jna.LevelDBNative.checkError(LevelDBNative.java:295)
at com.protonail.leveldb.jna.LevelDB.(LevelDB.java:16) at com.wavesplatform.database.jna.LevelDBJNADBFactory.openJnaDatabase(LevelDBJNADBFactory.scala:11)
at com.wavesplatform.database.jna.LevelDBJNADBFactory.open(LevelDBJNADBFactory.scala:15)
at com.wavesplatform.database.package$.openDB(package.scala:51)
at com.wavesplatform.Application.(Application.scala:69)
at com.wavesplatform.Application$.$anonfun$startNode$4(Application.scala:558)
at com.wavesplatform.Application$.$anonfun$startNode$4$adapted(Application.scala:555)
at com.wavesplatform.actor.RootActorSystem$.start(RootActorSystem.scala:25)
at com.wavesplatform.Application$.startNode(Application.scala:555)
at com.wavesplatform.Application$.main(Application.scala:524)
at com.wavesplatform.Application.main(Application.scala)

pgjdbc-ng throws mysterious ServiceLoader error

I'm getting a very weird error in my logs. This just started happening randomly and was not triggered by a version upgrade of anything.
2019-08-23 14:49:41.150 ccleves-mac-mini.local com.zaxxer.hikari.HikariDataSource 7177 INFO HikariPool-2 - Starting...
2019-08-23 14:49:41.150 ccleves-mac-mini.local com.zaxxer.hikari.HikariDataSource 7177 INFO HikariPool-1 - Starting...
2019-08-23 14:49:41.150 ccleves-mac-mini.local com.zaxxer.hikari.HikariDataSource 7177 INFO HikariPool-3 - Starting...
2019-08-23 14:49:41.676 ccleves-mac-mini.local com.zaxxer.hikari.pool.HikariPool 7703 ERROR HikariPool-3 - Error thrown while acquiring connection from data source
java.util.NoSuchElementException: null
at sun.misc.CompoundEnumeration.nextElement(CompoundEnumeration.java:59)
at java.util.ServiceLoader$LazyIterator.hasNextService(ServiceLoader.java:357)
at java.util.ServiceLoader$LazyIterator.hasNext(ServiceLoader.java:393)
at java.util.ServiceLoader$1.hasNext(ServiceLoader.java:474)
at com.impossibl.postgres.system.procs.Procs.loadDecoderProc(Procs.java:107)
at com.impossibl.postgres.system.procs.Procs.loadNamedBinaryCodec(Procs.java:83)
at com.impossibl.postgres.types.BaseType.<init>(BaseType.java:46)
at com.impossibl.postgres.types.BaseType.<init>(BaseType.java:50)
at com.impossibl.postgres.types.SharedRegistry.<init>(SharedRegistry.java:123)
at com.impossibl.postgres.jdbc.PGDriver.lambda$connect$0(PGDriver.java:106)
at java.util.HashMap.computeIfAbsent(HashMap.java:1127)
at com.impossibl.postgres.jdbc.PGDriver.lambda$connect$1(PGDriver.java:106)
at com.impossibl.postgres.system.BasicContext.init(BasicContext.java:303)
at com.impossibl.postgres.jdbc.PGDirectConnection.init(PGDirectConnection.java:276)
at com.impossibl.postgres.jdbc.ConnectionUtil.createConnection(ConnectionUtil.java:205)
at com.impossibl.postgres.jdbc.ConnectionUtil.createConnection(ConnectionUtil.java:165)
at com.impossibl.postgres.jdbc.PGDriver.connect(PGDriver.java:113)
at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:121)
at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:353)
at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:201)
at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:473)
at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:562)
at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:115)
at com.zaxxer.hikari.HikariDataSource.<init>(HikariDataSource.java:81)
Even weirder: It happens when I am developing the app in Eclipse. If I stop the app and then restart in Eclipse, it happens. If I close out Eclipse entirely and reopen it, the problem goes away and all connections open fine.
If I look at the connections on the Postgres server I don't see anything out of place. When it works, 10 connections get opened. When it fails, then just one.

Packaged Vagrant plugin not installed

I have written a custom vagrant plugin (https://github.com/cthrax/guest-tinycore) that when packaged as a gem and installed with 'vagrant plugin install /path/to/gem', states that it is installed successfully. However, when attempting to run any other vagrant command against the box, the plugin functionality is not available and I get the message:
The plugin "guest-tinycore" could not be found. Please make sure that it is
properly installed via vagrant plugin. Note that plugins made for
Vagrant 1.0.x are not compatible with 1.1+ and this error will likely
continue to show when you use plugin install with a 1.0.x plugin.
However, if I take this plugin and move it into the Vagrant application itself, as a core plugin, Vagrant picks it up successfully and all functionality works.
I'm looking for some guidance as to why the packaged version is not picked up by Vagrant correctly. Below is the debug log from running 'vagrant up'. (I've removed the output from the "guest-capabilities" call, so that I can get under the character limit.
Thanks in advance for any help!
INFO global: Vagrant version: 1.3.5
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/box/plugin.rb
INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/destroy/plugin.rb
INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/halt/plugin.rb
INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/help/plugin.rb
INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/init/plugin.rb
INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/package/plugin.rb
INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/plugin/plugin.rb
INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/provision/plugin.rb
INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/omnios/plugin.rb
INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/openbsd/plugin.rb
INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/pld/plugin.rb
INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/redhat/plugin.rb
INFO manager: Registered plugin: RedHat guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/solaris/plugin.rb
INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/solaris11/plugin.rb
INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/opensuse/plugin.rb
INFO manager: Registered plugin: OpenSUSE host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/provisioners/file/plugin.rb
INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/provisioners/puppet/plugin.rb
INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/provisioners/salt/plugin.rb
INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
INFO vagrant: `vagrant` invoked: ["up"]
DEBUG vagrant: Creating Vagrant environment
INFO environment: Environment initialized (#<Vagrant::Environment:0x00000100a0f928>)
INFO environment: - cwd: /Users/mbostwick/workspace/poseidon/app/vm
INFO environment: Home path: /Users/mbostwick/.vagrant.d
INFO environment: Local data path: /Users/mbostwick/workspace/poseidon/app/vm/.vagrant
DEBUG environment: Creating: /Users/mbostwick/workspace/poseidon/app/vm/.vagrant
DEBUG environment: Loading plugins from: /Users/mbostwick/.vagrant.d/plugins.json
INFO environment: Loading plugin from JSON: guest-tinycore
ERROR root: Failed to load plugin: guest-tinycore
ERROR root: -- Error: #<LoadError: cannot load such file -- guest-tinycore>
ERROR root: -- Backtrace:
ERROR root: /Applications/Vagrant/embedded/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
/Applications/Vagrant/embedded/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant.rb:193:in `require_plugin'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/environment.rb:744:in `block in load_plugins'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/environment.rb:741:in `each'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/environment.rb:741:in `load_plugins'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/environment.rb:132:in `initialize'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/bin/vagrant:74:in `new'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/bin/vagrant:74:in `<top (required)>'
/Applications/Vagrant/bin/../embedded/gems/bin/vagrant:23:in `load'
/Applications/Vagrant/bin/../embedded/gems/bin/vagrant:23:in `<main>'
INFO interface: error: The plugin "guest-tinycore" could not be found. Please make sure that it is
properly installed via `vagrant plugin`. Note that plugins made for
Vagrant 1.0.x are not compatible with 1.1+ and this error will likely
continue to show when you use `plugin install` with a 1.0.x plugin.
[31mThe plugin "guest-tinycore" could not be found. Please make sure that it is
properly installed via `vagrant plugin`. Note that plugins made for
Vagrant 1.0.x are not compatible with 1.1+ and this error will likely
continue to show when you use `plugin install` with a 1.0.x plugin.
[0m
INFO environment: Running hook: environment_load
INFO environment: Initializing config...
INFO loader: Set :default = "/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/config/default.rb"
DEBUG loader: Populating proc cache for "/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/config/default.rb"
DEBUG loader: Load procs for pathname: /Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/config/default.rb
INFO loader: Set :root = #<Pathname:/Users/mbostwick/workspace/poseidon/app/vm/Vagrantfile>
DEBUG loader: Populating proc cache for #<Pathname:/Users/mbostwick/workspace/poseidon/app/vm/Vagrantfile>
DEBUG loader: Load procs for pathname: /Users/mbostwick/workspace/poseidon/app/vm/Vagrantfile
INFO loader: Loading configuration in order: [:default, :home, :root]
DEBUG loader: Loading from: default (evaluating)
DEBUG loader: Loading from: root (evaluating)
DEBUG provisioner: Provisioner defined: shell
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG hosts: Host path search classes: [VagrantPlugins::HostWindows::Host, VagrantPlugins::HostSlackware::Host, VagrantPlugins::HostRedHat::Host, VagrantPlugins::HostOpenSUSE::Host, VagrantPlugins::HostFreeBSD::Host, VagrantPlugins::HostGentoo::Host, VagrantPlugins::HostArch::Host, VagrantPlugins::HostBSD::Host, VagrantPlugins::HostLinux::Host]
INFO hosts: Host class: VagrantPlugins::HostBSD::Host
INFO runner: Running action: #<Vagrant::Action::Builder:0x00000100a69a68>
INFO cli: CLI: [] "up" []
DEBUG cli: Invoking command class: VagrantPlugins::CommandUp::Command []
DEBUG command: 'Up' each target VM...
DEBUG command: Getting target VMs for command. Arguments:
DEBUG command: -- names: []
DEBUG command: -- options: {:provider=>nil}
DEBUG command: Loading all machines...
INFO command: Active machine found with name default. Using provider: virtualbox
INFO environment: Getting machine: default (virtualbox)
INFO environment: Uncached load of machine.
INFO loader: Set :vm_default = []
INFO loader: Loading configuration in order: [:default, :home, :root, :vm_default]
DEBUG loader: Loading from: default (cache)
DEBUG loader: Loading from: root (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
INFO box_collection: Searching for box: poseidon (virtualbox) in /Users/mbostwick/.vagrant.d/boxes/poseidon/virtualbox/metadata.json
INFO box_collection: Box found: poseidon (virtualbox)
INFO environment: Box exists with Vagrantfile. Reloading machine config.
INFO loader: Set :box_poseidon_virtualbox = #<Pathname:/Users/mbostwick/.vagrant.d/boxes/poseidon/virtualbox/Vagrantfile>
DEBUG loader: Populating proc cache for #<Pathname:/Users/mbostwick/.vagrant.d/boxes/poseidon/virtualbox/Vagrantfile>
DEBUG loader: Load procs for pathname: /Users/mbostwick/.vagrant.d/boxes/poseidon/virtualbox/Vagrantfile
INFO loader: Loading configuration in order: [:default, :box_poseidon_virtualbox, :home, :root, :vm_default]
DEBUG loader: Loading from: default (cache)
DEBUG loader: Loading from: box_poseidon_virtualbox (evaluating)
DEBUG loader: Upgrading config from version 1 to 2
DEBUG loader: Upgrading config to version 2
DEBUG loader: Upgraded to version 2 with 0 warnings and 0 errors
DEBUG loader: Loading from: root (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
INFO machine: Initializing machine: default
INFO machine: - Provider: VagrantPlugins::ProviderVirtualBox::Provider
INFO machine: - Box: #<Vagrant::Box:0x00000100d4d7e8>
INFO machine: - Data dir: /Users/mbostwick/workspace/poseidon/app/vm/.vagrant/machines/default/virtualbox
DEBUG virtualbox: Instantiating the driver for machine ID: "0dd96364-f3ae-4bbd-a116-279894338e3f"
INFO base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "--version"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: 4.2.18r88780
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG meta: Finding driver for VirtualBox version: 4.2.18
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_4_2
INFO base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "showvminfo", "0dd96364-f3ae-4bbd-a116-279894338e3f"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: Name: vm_default_1382672231
Groups: /
Guest OS: Linux 2.6
UUID: 0dd96364-f3ae-4bbd-a116-279894338e3f
INFO command: With machine: default (VirtualBox (0dd96364-f3ae-4bbd-a116-279894338e3f))
INFO interface: info: Bringing machine 'default' up with 'virtualbox' provider...
INFO batch_action: Enabling parallelization by default.
INFO batch_action: Disabling parallelization because provider doesn't support it: virtualbox
INFO batch_action: Batch action will parallelize: false
INFO batch_action: Starting action: #<Vagrant::Machine:0x00000100a0b3c8> up {:destroy_on_error=>true, :parallel=>true, :provision_ignore_sentinel=>false, :provision_types=>nil}
INFO machine: Calling action: up on provider VirtualBox (0dd96364-f3ae-4bbd-a116-279894338e3f)
INFO runner: Running action: #<Vagrant::Action::Builder:0x000001009ed2d8>
INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::CheckVirtualbox:0x00000100ba4fe0>
INFO base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "--version"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: 4.2.18r88780
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 0
DEBUG meta: Finding driver for VirtualBox version: 4.2.18
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_4_2
INFO base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "list", "hostonlyifs"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x00000100ba4fb8>
INFO runner: Running action: #<Vagrant::Action::Builder:0x00000100e53a20>
INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::Created:0x00000100e50910>
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "showvminfo", "0dd96364-f3ae-4bbd-a116-279894338e3f", "--machinereadable"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: name="vm_default_1382672231"
INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::Created:0x000001018e6f78>
INFO runner: Running action: #<Vagrant::Action::Warden:0x000001009edeb8>
INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::CheckVirtualbox:0x00000100ba4ec8>
INFO base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "--version"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: 4.2.18r88780
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG meta: Finding driver for VirtualBox version: 4.2.18
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_4_2
INFO base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "list", "hostonlyifs"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000100ba4ea0>
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x00000100ba4e78>
INFO runner: Running action: #<Vagrant::Action::Builder:0x00000100cbe8b8>
INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::IsRunning:0x00000100cbd1c0>
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "showvminfo", "0dd96364-f3ae-4bbd-a116-279894338e3f", "--machinereadable"]
DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: name="vm_default_1382672231"
groups="/"
ostype="Linux 2.6"
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::IsRunning:0x00000100cbd1c0>
INFO runner: Running action: #<Vagrant::Action::Warden:0x00000100d5ea48>
INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::MessageAlreadyRunning:0x00000100d5e9a8>
INFO interface: info: VirtualBox VM is already running.
INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::MessageAlreadyRunning:0x00000100d5e9a8>
INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Call:0x00000100ba4e78>
INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000100ba4ea0>
INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::CheckVirtualbox:0x00000100ba4ec8>
INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Call:0x00000100ba4f18>
INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000100ba4f40>
INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Call:0x00000100ba4fb8>
INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::CheckVirtualbox:0x00000100ba4fe0>
INFO environment: Running hook: environment_unload
INFO runner: Running action: #<Vagrant::Action::Builder:0x00000100e170c0>
This appears to have fixed itself by magic. After blowing away and cloning fresh from github the install works exactly as expected and all functionality works.