I’m having a lot of trouble with an image that used to have the 4.x ONE context installed.
I have uninstalled it, using apt-get remove (no purge, sadly).
By now I’ve reinstalled and purged and reinstalled both versions, leaving only the 5.6.x ONE context.
I’ve also fully udpated the VM.
It seemed to work after that but on second glance, no. it doesn’t even update the NIC config.
I would like to reproduce whats happening but most of the context upstart scripts just tell me they’d need to run at boot time. That’s not helping
Is there a way I can re-run this manually and in the same exact manner as it should happen on boot?
to see what happens?
But, worse, I also still got some problems with onegate.
Doesn’t seem to matter if I source the context or not, it’ll always through some ruby error.
root@svc-ubuntu14:~# . /var/run/one-context/context.sh.network root@svc-ubuntu14:~# onegate /usr/lib/ruby/1.9.1/uri/common.rb:176:in `split': bad URI(is not URI?): (URI::InvalidURIError) from /usr/lib/ruby/1.9.1/uri/common.rb:211:in `parse' from /usr/lib/ruby/1.9.1/uri/common.rb:747:in `parse' from /usr/bin/onegate.rb:370:in `initialize' from /usr/bin/onegate.rb:541:in `new' from /usr/bin/onegate.rb:541:in `<main>'
The only other odd thing I notice is the path itself:
I get this /var/run/one-context/context.sh.network instead of /var/run/one-context/one_env like on the other OS. Is it normal?