Losing my faith and trust in Nethserver

[m.traeumner (Michael Träumner)]

@flatspin

Always applied the update and everything was fine AFAIR and we also hadn’t had this problem with V7.3 to V7.4. That’s the reason why I’m wondering.

@davidep

Are you kidding me? 7.3 to 7.4 was a mess too! Surely not for everyone…

Also we had a big problem with samba upstream update last year.

[SOLVED] CentOS 7.4 (1708) - Shared folder access

Before update please read carefully the full announcement. CentOS 7.4 is out with a major rebase of most of RPMs. See upstream release notes: https://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 The list of known issues is quite long this time. Upgrade and rescue This procedure applies to any NethServer 7.3 installation, even downgraded or broken ones. Just execute: yum --enablerepo=nethforge update Then, be sure to have installed patched sssd-libwclient: Execute: rpm -q sssd-libwclient…

But if we can find a solution, it is a very good thing.

[flatspin (Ralf Jeckel)]

@bobtskutter

that every operating system has problems with updates.

I’m completely with you and your comment is really welcome. You didn’t interrupt, you enriched this discussion.

What frustated me is, that it’s impossible to setup a stable machine. And that’s a difference to others.
You have the choice between an old maybe buggy and instable machine and a instable alpha-release machine. Nothing between. And that’s IMO the bad thing.

That updates can break something and that an admin has to decied what to install and that she/he is reposible for her/his work I’m absolutely aware.

[flatspin (Ralf Jeckel)]

@davidep sorry to bother you again, but I need your opinion.

I created a repo-file called “CentOS-temporary” with this content:

# CentOS temporary contains rpms from CentOS 7.4.1708

[C7.4.1708-extras]
name=CentOS-7.4.1708 - Extras
baseurl=http://mirror.centos.org/centos-7/7.4.1708/extras/x86_64
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=1

[C7.4.1708-base]
name=CentOS-7.4.1708 - CentOSPlus
baseurl=http://mirror.centos.org/centos-7/7.4.1708/os/x86_64/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=1

[C7.4.1708-updates]
name=CentOS-7.4.1708 - Base
baseurl=http://mirror.centos.org/centos-7/7.4.1708/updates/x86_64/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=1

[C7.4.1708-centosplus]
name=CentOS-7.4.1708 - Base
baseurl=http://mirror.centos.org/centos-7/7.4.1708/centosplus/x86_64/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=1

With the standard-centos repos disabled and this enabled, I can install the latest 7.4 stable version with kernel 3.10.0.693.21.
Is this compatibel with nethserver-repos-content?
Or in other words: Bad or good idea?

EDIT: This is no longer available. Repo moved to Centos-vault!

[filippo_carletti]

I don’t think that I’m qualified enough for a definitive answer, but it seems a good idea. (AFAIK, Davide is offline)

[bobtskutter (bob)]

If we assume that the install ISO for NethServer is stable. What if NethServer implemented the LVM snapshot method before installing updates. If the update process went wrong the user could roll back to previous good snaphot?
I don’t actually know how that would be implemented, but it sounds like a solution to recovering a Linux Server from a bad update.

Back Up (And Restore) LVM Partitions With LVM Snapshots

bob

[davidep (Davide Principi)]

Yes I’m on holiday now

If you can, wait the beta release next week. Your idea seems good but I cannot ensure it works. Read carefully the “release lock” thread for more info

[alefattorini (Alessio Fattorini)]

@davidep

Yes I’m on holiday now

And that says a lot how much devs care about the community