Hi Praveen,
thanks for your feedback.
I was not using the libvirt provider - rather it is/was virtualbox:
"Bringing machine 'default' up with 'virtualbox' provider..."
Also I already used the newest CDK version (beta5).
Nevertheless, I cleaned up my whole environment, and installed the
newest box version: rhel-cdk-kubernetes-7.2-21.x86_64.vagrant-virtualbox.box
instead of rhel-cdk-kubernetes-7.2-19.x86_64.vagrant-virtualbox.box.
With the newest version, the success summary is missing when
running "vagrant up". It stops with a red coloured message
("Created symlink from..."). But the box is running, and also
Openshift.
Also the login error seems to be fixed (the public IP address is
configured correctly).
Here is the output:
[zisis@rhenium rhel-ose]$ ls -ld ~/.vagrant.d/ .vagra*/
/var/lib/libvirt/images/*
ls: cannot access /home/zisis/.vagrant.d/: No such file or directory
ls: cannot access .vagra*/: No such file or directory
ls: cannot access /var/lib/libvirt/images/*: No such file or directory
[zisis@rhenium rhel-ose]$ vagrant plugin install vagrant-registration
vagrant-service-manager
Installing the 'vagrant-registration' plugin. This can take a few minutes...
Installed the plugin 'vagrant-registration (1.2.1)'!
Installing the 'vagrant-service-manager' plugin. This can take a few minutes...
Installed the plugin 'vagrant-service-manager (1.0.0)'!
[zisis@rhenium rhel-ose]$ vagrant box add --name cdkv2
~/rhel-cdk-kubernetes-7.2-21.x86_64.vagrant-virtualbox.box
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'cdkv2' (v0) for provider:
box: Unpacking necessary files from:
file:///home/zisis/rhel-cdk-kubernetes-7.2-21.x86_64.vagrant-virtualbox.box
==> box: Successfully added box 'cdkv2' (v0) for 'virtualbox'!
[zisis@rhenium rhel-ose]$ vagrant box add --name cdkv2
~/rhel-cdk-kubernetes-7.2-21.x86_64.vagrant-virtualbox.box
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'cdkv2' (v0) for provider:
box: Unpacking necessary files from:
file:///home/zisis/rhel-cdk-kubernetes-7.2-21.x86_64.vagrant-virtualbox.box
==> box: Successfully added box 'cdkv2' (v0) for 'virtualbox'!
[zisis@rhenium rhel-ose]$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'cdkv2'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: rhel-ose_default_1460376944126_45361
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
default: No guest additions were detected on the base box for this VM! Guest
default: additions are required for forwarded ports, shared folders, host
only
default: networking, and more. If SSH fails on this machine, please install
default: the guest additions and repackage the box to continue.
default:
default: This is not an error message; everything may continue to work
properly,
default: in which case you may ignore this message.
==> default: Configuring and enabling network interfaces...
==> default: Registering box with vagrant-registration...
default: Would you like to register the system now (default: yes)? [y|n]n
==> default: Copying TLS certificates to
/home/zisis/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
==> default: Created symlink from
/etc/systemd/system/multi-user.target.wants/openshift.service to
/usr/lib/systemd/system/openshift.service.
[zisis@rhenium rhel-ose]$
[zisis@rhenium rhel-ose]$ curl -k -I https://192.168.100.10:8443/console/
HTTP/1.1 200 OK
Cache-Control: public, max-age=0, must-revalidate
Etag: W/"112fcc4_"
Vary: Accept-Encoding
Date: Mon, 11 Apr 2016 12:18:32 GMT
Content-Type: text/html; charset=utf-8
Regards,
Zisis
----- Ursprüngliche Mail -----
> Von: "Praveen Kumar" <[email protected]>
> An: "Zisis Lianas" <[email protected]>
> CC: "container-tools" <[email protected]>
> Gesendet: Montag, 11. April 2016 07:25:34
> Betreff: Re: [Container-tools] CDK Bug with public IP
> On Fri, Apr 8, 2016 at 5:59 PM, Zisis Lianas <[email protected]> wrote:
>> Hi container guys,
>
> Hi Zisis,
>
>>
>> I found a bug in the container development kit (cdk-2.0.0-beta5).
>>
>> When I change the PUBLIC_ADDRESS in the Vagrantfile
>> (cdk/components/rhel/rhel-ose/Vagrantfile),
>> it is not considered in the master-config.yaml in OpenShift. I had to fix
>> the IP address manually to
>> get the Box to work.
>>
>>
>> Reproducer:
>>
>> 1) Customize cdk/components/rhel/rhel-ose/Vagrantfile
>> #PUBLIC_ADDRESS="10.1.2.2"
>> PUBLIC_ADDRESS="192.168.100.10"
>>
>
> Thank you for trying out Container Development Kit and finding a
> issue. We tried to reproduce same issue[0] as you described but looks
> like you are missing something or trying a older version of CDK (This
> issue was part of beta4). As per your given details and logs, looks
> like you used 'libvirt' as provider for vagrant box, I would suggest
> you to give it another try after following below steps because libvirt
> keeps VM snapshot which gets load (In your case a older one).
>
> # vagrant destroy (If box is running)
> # rm -fr .vagrant (Same location where your custom vagrant file is)
> # rm -fr /var/lib/libvirt/images/*_0.img && systemctl restart libvirtd
> (This will remove any snapshot which libvirt created, please do a
> double check by inspecting '/var/lib/libvirt/images' dir)
> # vagrant up (Using your custom vagrant file)
>
> [0] http://fpaste.org/353710/35217614/
>
> Let us know if you still faced same issue.
>
> --
> Praveen Kumar
> http://fedoraproject.org/wiki/User:Kumarpraveen
> http://fedoraproject.org/
> http://kumar-pravin.blogspot.com
_______________________________________________
Container-tools mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/container-tools
