OK, that’s consistent with a cut and paste of the now corrected example kiwi-ng installer build command:
kiwi-ng --profile=Leap15.1.x86_64 --type oem system build --description ./ --target-dir /home/kiwi-images/
which should have read 15.2 of course. As per the prior referenced pull request change:
(Click on “Files Changed” tab)
And from you picture of the ‘btrfs fi usage’ command you can see the multiple:
WARNING: RAID56 detected, not implemented
referenced earlier indicating the incomplete support for some usage functions. This is one of the indications of the parity raids being less well developed, they are basically just younger. But note that this short-coming has now been fixed in upstream btrfs. The same command on your “/” pool would not have those warnings.
You should be able to bring up the terminal program and do a:
and enter the root password you setup during the install. And “exit” once your are done with that terminal access.
1: Rockstor Config backup and download to a client machine, re-install (after building a 15.2 profile installer), import data pool, re-apply config backup: see: Configuration Backup and Restore
You will need to set each added users password after this as they will be random upon config restore. The Web-UI Admin user, setup on the first Web-UI screen, can do this within the Web-UI. Or use the root of course via the command line.
2: In place “Distribution Update” which should be pretty much along the normal lines of an in-place update for a regular Leap15.1 to Leap 15.2.
This latter method hasn’t yet been approached in our docs, given Leap 15.2 was our intended first ‘general consumption’ target, so I’ll make an first draft attempt below. You 15.1 was the result of us having used 15.0/15.1 and finnaly 15.2 during our 2 year transition phase from CentOS to finnaly Leap 15.2. My typo and your cut paste has landed you with a Leap15.1. Perfectly viable given it’s far more tested as a distro than 15.2 but we are aiming at Leap 15.2 for re-launch to get the newer kernel and btrfs stack. But given some folks will inevitably have difficulties via kernel regressions the Leap 15.1 option is a fall back position for us as it’s the same base kernel version as our CentOS ran (4.12) so very likely to work equally as well on their existing hardware. But the Leap 15.2 profile and it’s 5.3 kernel base is obviously preferred. We were just trying to cater for our existing clients on the kernel side while still offering newer btrfs backports.
Distribution update (draft)
There are numerous openSUSE docs on how this might be done. One example can be found here:
1: Make sure all updates are in place and you have rebooted there after. This ensures all updates are in-play.
2: Backup your existing repos just in case via:
cp -Rv /etc/zypp/repos.d /etc/zypp/repos.d.Old
and to restore these you would, if need be, execute:
cp -f /etc/zypp/repos.d.Old/* /etc/zypp/repos.d/
3: Check visually your existing repos via:
zypper lr -u
4: Change them from 15.1 to 15.2 if hardcoded (the default ones are) via:
sed -i 's/15\.1/15\.2/g;s/15_1/15_2/g' /etc/zypp/repos.d/*.repo
Which searches for “15.1/15_1” and replaces them with “15.2/15_2” respectively for all repos in all repo files.
5: Ensure visually all repos are changed over via:
zypper lr -u
6: Import all new keys and refresh the new repos themselves via:
zypper --gpg-auto-import-keys ref
7: Do a Distribution Update downloading all packages in advance via:
zypper dup --no-recommends --download-in-advance
Note: be sure to read and answer carefully all multi-choice questions on the way.
The likely safest answer in most cases will be to accept a vendor change i.e.:
Problem: problem with installed package dracut-kiwi-lib-9.21.3-lp151.1.1.x86_64
Solution 1: install dracut-kiwi-lib-9.20.5-lp126.96.36.199.x86_64 (with vendor change)
obs://build.opensuse.org/Virtualization:Appliances --> openSUSE
Solution 2: keep obsolete dracut-kiwi-lib-9.21.3-lp151.1.1.x86_64
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): 1
The above vendor change is simply moving from a prior OBS repo source (used in our installer build) to the ‘regular’ “openSUSE” variant/version native to the new ‘distro’ version.
Note also: if you see in the overview that “systemd-presets-branding-rockstor” package is going to be removed then cancel (c) and add our following OBS repository via:
zypper --non-interactive addrepo --refresh -p97 http://download.opensuse.org/repositories/home:/rockstor:/branches:/Base:/System/openSUSE_Leap_15.2/ home_rockstor_branches_Base_System
zypper --gpg-auto-import-keys ref
This relates to an in-progress fix regarding the current-as-of-writing omission of this repo in our installer. Post ‘fix’ installers should not be affected by this omission.
Once all multi choice options have been answered a large summary of changes with be shown along with indications of actions required once these changes have been enacted. Most likely:
Note: System reboot required.
Continue via “y” and you should be on your way.
Once all packages have been downloaded and installer/updated/etc your should see the following:
Core libraries or services have been updated.
Reboot is required to ensure that your system benefits from these updates.
where upon you can:
shutdown -r now
Please note that the first boot screen, the Grub options screen, will still show the original Rockstor installer version. This is expected and is purely cosmetic.
All the above steps will require the root user.
(Tested on a Rockstor 4 build on openSUSE Leap 15.1 variant installed from our installer recepie)
########## end of proposed Distro doc draft entry ###############
Yes, via the Distribution update (draft) method proposed above. But as Leap 15.2 is our intended first public release, and we are still in release candidate phase on our 15.2 variant, this method has had no real community testing. And given your testing activities/reports to date you may be just the candidate :).
If by this you mean your password no longer works (or has been misplaced), then try clicking on the “Forgot Password” link in the Sign In screen. That should send you instructions on how to proceed. I’ve checked your Appman account and you look to have registered and had your email verified successfully.
Hope that helps.