Yes, it is due to the vagrant update - but that is not my question. kl. 23:45:19 UTC+2 tirsdag 20. mai 2014 skrev Alvaro Miranda Aguilera følgende: > > i think that happen only once when you upgrade vagrant binaries. > > install a new version of vagrant is done by jenkins also or manually? > > Alvaro > > > On Wed, May 21, 2014 at 6:58 AM, David Karlsen > <[email protected]<javascript:> > > wrote: > >> Hi. >> >> I have a jenkins template to start/stop machines, and hence it is not >> interactive and run with a tty, so I get this message: >> >> *20:55:45* Vagrant failed to initialize at a very early stage:*20:55:45* >> *20:55:45* Vagrant is attempting to interface with the UI in a way that >> requires*20:55:45* a TTY. Most actions in Vagrant that require a TTY have >> configuration*20:55:45* switches to disable this requirement. Please do that >> or run Vagrant*20:55:45* with TTY.*20:55:46* Vagrant failed to initialize at >> a very early stage:*20:55:46* *20:55:46* Vagrant is attempting to interface >> with the UI in a way that requires*20:55:46* a TTY. Most actions in Vagrant >> that require a TTY have configuration*20:55:46* switches to disable this >> requirement. Please do that or run Vagrant*20:55:46* with TTY.*20:55:46* >> Build step 'Jenkins » startVagrant' marked build as failure*20:55:47* >> [tac-jfr-srv] $ /bin/sh -e /tmp/hudson7881331129468902864.sh*20:55:47* >> VAGRANT_HOME is: >> /data/jenkins/workspace/tac/jfr/tac-jfr-srv/.vagrant.d*20:55:47* >> VBOX_USER_HOME is: >> /data/jenkins/workspace/tac/jfr/tac-jfr-srv/.vbox*20:55:47* >> VBOX_IPC_SOCKETID is: tac.jfr.tac-jfr-srv*20:55:48* Vagrant failed to >> initialize at a very early stage:*20:55:48* *20:55:48* Vagrant is attempting >> to interface with the UI in a way that requires*20:55:48* a TTY. Most >> actions in Vagrant that require a TTY have configuration*20:55:48* switches >> to disable this requirement. Please do that or run Vagrant*20:55:48* with >> TTY. >> >> >> >> >> >> >> If I log in as a real user I can see what is going on: >> >> -bash-4.1$ vagrant up >> Vagrant is upgrading some internal state for the latest version. >> Please do not quit Vagrant at this time. While upgrading, Vagrant >> will need to copy all your boxes, so it will use a considerable >> amount of disk space. After it is done upgrading, the temporary disk >> space will be freed. >> >> Press ctrl-c now to exit if you want to remove some boxes or free >> up some disk space. >> >> Press any other key to continue. >> >> >> >> I don't see any parameters such as --force-yes to allow automatic upgrade >> w/o user interaction - is there a way to circument it? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > >
-- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
