Bug in create Repo wizard on v7 ?

[kristofpoppe]

Hi all, just upgraded to v7 build 2911 and tried to create a new repo. This repo should keep the meta data local and the effective data in a S3 compatible bucket.

For v6 we first created an object storage and then created the repo where we could select in the wizard the local metadata path and the option to 'extend' this with object storage.

We I try the same in v7, I select in the Create Repo wizard: Step 1: Repo Name & description > Step 2: Target location: Backup to Object storage >Step 3: Backup Proxy and cache location >Step 4: Retention Policy and then the wizard stops and gives me the option to 'Finish'

When I use the back button, and go back to Step 2: Target Location, the radio button is now on Backup to local disk.
So it seems there is no option to select an existing bucket in the wizard. The swapping of the radio button when going back in the wizard can be reproduced.

Any other users already tested this with the same behaviour ?

[Mike Resseler]

Does the repository have versioning enabled? If it does, you cannot select it in that wizard, only for a secondary copy. We added this additional check to avoid mistakes, and therefore we won't show incompatible repositories in the job wizard. Can you verfiy?

[kristofpoppe]

Hi Mike, thanks for the quick response !

The repo is a Wasabi repo, but created as S3-compatible. (not the new direct Wasabi selection on the wizard)
It's actually a new folder in an existing bucket which is already used by other jobs created on v6.
I can confirm that versioning is not enabled and the immutable flag is also down.

[Mildur]

I just tried the same steps in my lab. Also added a Wasabi bucket (not immutable) as S3 compatible.
I didn't had any issues with going back in the wizard. Backup to Object storage was still selected and I could finish the wizard and had my repository.

Best,
Fabian

[kristofpoppe]

Thank you Fabian,

I'll delete the object storage and try all over again an keep you posted.

[Polina]

Hi Kristof,

Our QA experts told me that this could happen if a folder selected for a cache has already been used as a local repository and contains some backup data.

[kristofpoppe]

Hi Polina, thanks for your response.

I came across the same remark.
The folder contained some .xml and .sqlite files. After I deleted these files, I was able to select them in the wizard.