vagrant-projects

vagrant-projects copied to clipboard

Describe the issue An older version of this project is being used 18.4.0-XE in this case. User currently has no issue to bring the Oracle DB up by running vagrant up. We can verify that Oracle DB is up and running by "sqlplus / as sysdba" etc. After an upgrade of vagrant to 2.4.3 recently, can't connect to the DB with a sql client software AquaData studio. We are trying to get into the vm by vagrant ssh but can't. Since we know the DB is running, our main focus/question is how to get into the vm. (1)How to make vagrant ssh work and (2) Is there any alternative to vagrant ssh to achieve the same goal.

Environment (please complete the following information):

• Host OS: macOS Ventura 13.4.1
• Vagrant version: 2.4.3
• Vagrant provider: VirtualBox:
  • VirtualBox version: 7.1
• Vagrant project: https://github.com/oracle/vagrant-projects/tree/main/OracleDatabase/18.4.0-XE
• Oracle Linux version: vagrant box list oraclelinux/7 (virtualbox, 7.9.194) oraclelinux/7 (virtualbox, 7.9.335)

Additional information We've tried this command that works in terms of getting us to run sqlplus / as sysdba ssh -i /<path_to>/vagrant-projects/OracleDatabase/18.4.0-XE/.vagrant/machines/oracle18c-xe-vagrant/virtualbox/private_key [email protected] -p 2222

The Vagrantfile is default as in the OracleDatabase/18.4.0-XE project and not modified, so the name of the vm is the defult oracle18c-xe-vagrant

Expected Behavior After running vagrant up, we run vagrant ssh, what we expect to see is prompt [vagrant@oracle18c-xe-vagrant ~] and then if we would do sudo su - oracle we'd expect to see prompt [oracle@oracle18c-xe-vagrant ~].

Actual Behavior After running vagrant up, we run vagrant ssh, what we actually see is prompt [vagrant@vbox ~] and then if we did sudo su - oracle anyway and we saw prompt [oracle@vbox ~].