Promote 15.3 profiles given 15.2 approaches EOL about rockstor-installer HOT 6 CLOSED

The main hold-up on releasing the final stable rpm is an as yet un-formalised (read as yet not understood) config import issue reported by @Hooverdan96 that is being explored in a private RC test of the installer builds.

Linking to the now active issue with a proof of concept fix:
rockstor/rockstor-core#2334

Another hold-up, of sorts, infrastructure wise, is our first issue in our open source website repo:

"Migrate to Hugo ..." rockstor/rockstor-website#1

Noting that we are now all Hugo on the main website. As of the merging of:

rockstor/rockstor-website#22

Plus ensuring we have an understood 'zypper dup' path for them to follow to 'jump' up to the Leap 15.3 profile. Or it's equivalent.

To be addressed against the following issue:
rockstor/rockstor-doc#352

The Leap 15.3 profiles do now look to be in good shape, hence this proposed update. But as with all non trivial modern software, we are on shifting sands so eyes-open.

There is also the now formalised email notification issue that has cropped up in our Leap 15.3 based offering:
rockstor/rockstor-core#2324

from rockstor-installer.

Hello @skewty and thanks for your interest in our re-release via the v4 "Built on openSUSE" endeavour.

Is this issue holding up the 4.0 ISO release?

Not majorly, but a little. We are as per:
https://forum.rockstor.com/t/beta-built-on-opensuse-testing-channel-changelog/7097/16
now at 4.0.9-0 Release Candidate 10 in our testing channel, from which this rockstor-installer repo gets it's rockstor package.

The main hold-up on releasing the final stable rpm is an as yet un-formalised (read as yet not understood) config import issue reported by @Hooverdan96 that is being explored in a private RC test of the installer builds. Unfortunately all our core developers/contributors are currently busy getting our ducks in a row in our infrastructure/backend systems ready for the re-release by way of the v4. But I myself hope to have my immediate backlog done soon so I can re-focus on that potential blocker so we can at least get it to the GitHub issue stage.

Perhaps a GitHub Milestone with the remaining issues before the 4.0 ISOs can be released would be a good idea?

Funny you should say that. @FroggyFlox prompted me similarly a while back to do this and as a result we created the following milestone in the main rockstor-core repo:

"First 4 Stable (ISO)"
https://github.com/rockstor/rockstor-core/milestones

The referenced config import to-be-issue, once we understand and can clearly define it, will be created in that repo and likely added to that otherwise completed to date "First 4 Stable (ISO)" milestone.

As for hold-ups in this repo (rockstor-installer). I don't thing there are any really; bar, as indicated, this issue in a small way. Given the nearness of Leap 15.2's EOL we will likely promote installer profiles based on Leap 15.3 (this issues focus for the readme updates) but given we have quite a few folks already running the v4 "Build on openSUSE" variant we want to see them through to the EOL and continue with the rpm and installer profile maintenance until then. Plus ensuring we have an understood 'zypper dup' path for them to follow to 'jump' up to the Leap 15.3 profile. Or it's equivalent.

Another hold-up, of sorts, infrastructure wise, is our first issue in our open source website repo:

"Migrate to Hugo ..."
rockstor/rockstor-website#1

Which will in turn ease our way to publishing/explaining the planned 8 pre-build installers derived from the 6 profiles within this (rockstor-installer) repo:
I.e.
Both 15.2 and 15.3 bases for machine targets of X86_64/RaspberryPi4/ARM64EFI
Which gives us 6 installers, but we have in the closed beta tests two sub target images for the ARM64EFI profiles (qcow2 and raw.zx).

Our ARM64EFI profile has an end target defined as qcow2 (intended for a hardware partner), but we copy out the raw file and 'xz --threads=4' it while we are there within our semi-automated builders we lined up read for the re-release. This is intended to provide maximum flexibility for those on that platform (generic ARM64 based servers likely).

Hope that helps, at least to put this issue into perspective. The Leap 15.3 profiles do now look to be in good shape, hence this proposed update. But as with all non trivial modern software, we are on shifting sands so eyes-open.

from rockstor-installer.

The main hold-up on releasing the final stable rpm is an as yet un-formalised (read as yet not understood) config import issue reported by @Hooverdan96 that is being explored in a private RC test of the installer builds.

Linking to the now active issue with a proof of concept fix:
rockstor/rockstor-core#2334

Another hold-up, of sorts, infrastructure wise, is our first issue in our open source website repo:

"Migrate to Hugo ..." rockstor/rockstor-website#1

Noting that we are now all Hugo on the main website. As of the merging of:

rockstor/rockstor-website#22

Plus ensuring we have an understood 'zypper dup' path for them to follow to 'jump' up to the Leap 15.3 profile. Or it's equivalent.

To be addressed against the following issue:
rockstor/rockstor-doc#352

The Leap 15.3 profiles do now look to be in good shape, hence this proposed update. But as with all non trivial modern software, we are on shifting sands so eyes-open.

There is also the now formalised email notification issue that has cropped up in our Leap 15.3 based offering:
rockstor/rockstor-core#2324

from rockstor-installer.

I am currently working on this issue.

from rockstor-installer.

Is this issue holding up the 4.0 ISO release?

Perhaps a GitHub Milestone with the remaining issues before the 4.0 ISOs can be released would be a good idea?

from rockstor-installer.

Linking to the now active issue with a proof of concept fix:
rockstor/rockstor-core#2334

To be addressed against the following issue:
rockstor/rockstor-doc#352

There is also the now formalised email notification issue that has cropped up in our Leap 15.3 based offering:
rockstor/rockstor-core#2324

All of the above are now resolved via the release of 4.1.0-0 and the consequent publishing of the 15.2 to 15.3 howto that also depended on a 4.1.0-0 fix.

from rockstor-installer.