search

redhat-developer-tooling / openshift-vagrant

All-in-One OpenShift Enterprise Vagrant setup
37 stars 32 forks source link

cdk-v2-ose-3-2 won't start for me #71

Closed rhopp closed 8 years ago

rhopp commented 8 years ago

output of vagrant up --provider virtualbox

Bringing machine 'cdk' up with 'virtualbox' provider...
==> cdk: Importing base box 'cdk_v2'...

Progress: 10%
Progress: 20%
Progress: 30%
Progress: 40%
Progress: 50%
Progress: 90%
==> cdk: Matching MAC address for NAT networking...
==> cdk: Setting the name of the VM: openshift.cdk-2-ose-3-2
==> cdk: Clearing any previously set network interfaces...
==> cdk: Preparing network interfaces based on configuration...
    cdk: Adapter 1: nat
    cdk: Adapter 2: hostonly
==> cdk: Forwarding ports...
    cdk: 22 (guest) => 2222 (host) (adapter 1)
==> cdk: Running 'pre-boot' VM customizations...
==> cdk: Booting VM...
==> cdk: Waiting for machine to boot. This may take a few minutes...
    cdk: SSH address: 127.0.0.1:2222
    cdk: SSH username: vagrant
    cdk: SSH auth method: private key
    cdk: Warning: Remote connection disconnect. Retrying...
    cdk: 
    cdk: Vagrant insecure key detected. Vagrant will automatically replace
    cdk: this with a newly generated keypair for better security.
    cdk: 
    cdk: Inserting generated public key within guest...
    cdk: Removing insecure key from the guest if it's present...
    cdk: Key inserted! Disconnecting and reconnecting using new SSH key...
==> cdk: Machine booted and ready!
==> cdk: Checking for guest additions in VM...
    cdk: No guest additions were detected on the base box for this VM! Guest
    cdk: additions are required for forwarded ports, shared folders, host only
    cdk: networking, and more. If SSH fails on this machine, please install
    cdk: the guest additions and repackage the box to continue.
    cdk: 
    cdk: This is not an error message; everything may continue to work properly,
    cdk: in which case you may ignore this message.
==> cdk: Configuring and enabling network interfaces...
==> cdk: Rsyncing folder: /home/rhopp/git/openshift-vagrant/cdk-v2-ose-3-2/ => /vagrant
==> cdk: Running provisioner: shell...
    cdk: Running: inline script
==> cdk: /tmp/vagrant-shell: line 1: /opt/adb/openshift/add_insecure_registry: No such file or directory
==> cdk: sed: can't read /etc/sysconfig/openshift_option: No such file or directory
==> cdk: Trying to pull repository brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/ose ... 
==> cdk: failed
==> cdk: unable to ping registry endpoint https://brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/v0/
==> cdk: v2 ping attempt failed with error: Get https://brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/v2/: tls: oversized record received with length 20527
==> cdk:  v1 ping attempt failed with error: Get https://brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/v1/_ping: tls: oversized record received with length 20527
==> cdk: Failed to execute operation: Access denied
==> cdk: Failed to start openshift.service: Unit openshift.service failed to load: No such file or directory.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

I have most recent version from this repo - commit ee2c857ad17ac2087edd172189e1abb35b0a4b1c My system is Fedora 23, Virtualbox 5.0.10, Vagrant 1.8.1, 

$ vagrant plugin list
landrush (0.19.0)
vagrant-adbinfo (0.1.0)
vagrant-registration (1.2.1)
vagrant-service-manager (0.0.4)
rhopp commented 8 years ago

Turned out I had old vagrant box. Deleting ~/.vagrant.d/ solved the issue. Sorry for bothering.