openindiana/hipster box: broken rsync, wants a password

[ThomasWaldmann]

Maybe this is not the correct issue tracker, but I didn't find a better matching one.

The vagrant box is currently unusable for my borgbackup testing, because rsync wants a password (it should just work with the ssh key):

tw@server:~/w/borg$ vagrant box outdated
Checking if box 'openindiana/hipster' version '202409' is up to date...

tw@server:~/w/borg$ vagrant up openindiana
Bringing machine 'openindiana' up with 'virtualbox' provider...
==> openindiana: Importing base box 'openindiana/hipster'...
==> openindiana: Matching MAC address for NAT networking...
==> openindiana: Checking if box 'openindiana/hipster' version '202409' is up to date...
==> openindiana: Setting the name of the VM: borg_openindiana_1727730378317_44536
==> openindiana: Fixed port collision for 22 => 2222. Now on port 2202.
==> openindiana: Clearing any previously set network interfaces...
==> openindiana: Preparing network interfaces based on configuration...
    openindiana: Adapter 1: nat
==> openindiana: Forwarding ports...
    openindiana: 22 (guest) => 2202 (host) (adapter 1)
==> openindiana: Running 'pre-boot' VM customizations...
==> openindiana: Booting VM...
==> openindiana: Waiting for machine to boot. This may take a few minutes...
    openindiana: SSH address: 127.0.0.1:2202
    openindiana: SSH username: vagrant
    openindiana: SSH auth method: private key
    openindiana: 
    openindiana: Vagrant insecure key detected. Vagrant will automatically replace
    openindiana: this with a newly generated keypair for better security.
    openindiana: 

    openindiana: Inserting generated public key within guest...

    openindiana: Removing insecure key from the guest if it's present...
==> openindiana: Machine booted and ready!
==> openindiana: Checking for guest additions in VM...
==> openindiana: Rsyncing folder: /mnt/fastssd/tw/w/borg/ => /vagrant/borg/borg
(vagrant@127.0.0.1) Password: 
(vagrant@127.0.0.1) Password: 
There was an error when attempting to rsync a synced folder.
Please inspect the error message below for more info.

Host path: /mnt/fastssd/tw/w/borg/
Guest path: /vagrant/borg/borg
Command: "rsync" "--verbose" "--archive" "--delete" "--exclude" ".python-version" "--no-owner" "--no-group" "--rsync-path" "sudo rsync" "-e" "ssh -p 2202 -o LogLevel=FATAL   -o ControlMaster=auto -o ControlPath=/tmp/vagrant-rsync-20240930-3856413-ahggoe -o ControlPersist=10m  -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i '/mnt/fastssd/tw/w/borg/.vagrant/machines/openindiana/virtualbox/private_key'" "--exclude" ".vagrant/" "/mnt/fastssd/tw/w/borg/" "vagrant@127.0.0.1:/vagrant/borg/borg"
Error: rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(231) [sender=3.2.7]

[ThomasWaldmann]

BTW, you could fill out that (maybe point to the correct github repo or give some contact info):

https://app.vagrantup.com/openindiana

[Toasterson]

BTW, you could fill out that (maybe point to the correct github repo or give some contact info):

https://app.vagrantup.com/openindiana

Good point. Added links to the Issue tracker and Source repo to the box. Not much more I can add at the moment there but this should help guide people to the right place.

In general if you don't find the place to open a Bug the Bug tracker is maintained. We have legacy tasks we couldn't find an agreement what to do with but new ones are responded to quickly.

Looks like the rsync setup changed since the last time I tested. I'll have a look to update/fix it.

[Toasterson]

Looks like this one is a bit deeper than with rsync. The Key setup I am making on the box works, but then vagrant generates new keys that do not work with our OpenSSH. There is a longer running analysis at the moment due to a problem with Encrypted Keys somehow. Fun side bug I found. I can have a box version with v202409 but vagrants config.vm.box.version only accepts semantic versioning...

We have a version of OpenSSH in the works that fixes this, but it has other problems we need to hunt down.