Errors updating from 6.0.10-1 to 6.0.11-1

1. offizieller Beitrag

    Are these salt errors ok? The files in /tmp it mentions are not there.


    steve


    Reading package lists...
    Building dependency tree...
    Reading state information...
    Calculating upgrade...
    The following packages will be upgraded: openmediavault openmediavault-omvextrasorg
    apt-listchanges: Reading changelogs...
    Preconfiguring packages ...
    2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    Need to get 0 B/2442 kB of archives.
    After this operation, 241 kB of additional disk space will be used.
    (Reading database ... (Reading database ... 5%
    (Reading database ... 10%
    (Reading database ... 15%
    (Reading database ... 20%
    (Reading database ... 25%
    (Reading database ... 30%
    (Reading database ... 35%
    (Reading database ... 40%
    (Reading database ... 45%
    (Reading database ... 50%
    (Reading database ... 55%
    (Reading database ... 60%
    (Reading database ... 65%
    (Reading database ... 70%
    (Reading database ... 75%
    (Reading database ... 80%
    (Reading database ... 85%
    (Reading database ... 90%
    (Reading database ... 95%
    (Reading database ... 100%
    (Reading database ... 65490 files and directories currently installed.)
    Preparing to unpack .../openmediavault-omvextrasorg_6.0.7_all.deb ...
    Unpacking openmediavault-omvextrasorg (6.0.7) over (6.0.6) ...
    Preparing to unpack .../openmediavault_6.0.11-1_all.deb ...
    Unpacking openmediavault (6.0.11-1) over (6.0.10-1) ...
    Setting up openmediavault (6.0.11-1) ...
    Installing new version of config file /etc/cron.weekly/openmediavault-update-smart-drivedb ...
    Creating configuration database ...
    Migrating configuration database ...
    Setting up Salt environment ...
    [ERROR ] Command '/usr/bin/patch' failed with return code: 1
    [ERROR ] stdout: patching file /tmp/__salt.tmp.1cv64iu_ (read from /lib/python3/dist-packages/salt/modules/network.py)
    Reversed (or previously applied) patch detected! Skipping patch.
    1 out of 1 hunk ignored -- saving rejects to file /tmp/__salt.tmp.53hoit3g
    [ERROR ] retcode: 1
    [ERROR ] Command '/usr/bin/patch' failed with return code: 1
    [ERROR ] stdout: patching file /tmp/__salt.tmp.cviam1jn (read from /lib/python3/dist-packages/salt/fileserver/roots.py)
    Reversed (or previously applied) patch detected! Skipping patch.
    1 out of 1 hunk ignored -- saving rejects to file /tmp/__salt.tmp._8nyqlqv
    [ERROR ] retcode: 1
    Processing system modifications ...
    Processing triggers for rsyslog (8.2102.0-2) ...
    Processing triggers for openmediavault (6.0.11-1) ...
    Restarting engine daemon ...
    Updating workbench configuration files ...
    Setting up openmediavault-omvextrasorg (6.0.7) ...
    Updating configuration database ...
    warehouse21:
    ---------- ID: remove_apt_list_omvextras Function: file.absent Name: /etc/apt/sources.list.d/omvextras.list Result: True Comment: Removed file /etc/apt/sources.list.d/omvextras.list Started: 20:48:17.828712 Duration: 3.682 ms Changes: ---------- removed: /etc/apt/sources.list.d/omvextras.list
    ---------- ID: omvextrasbaserepo Function: pkgrepo.managed Name: deb https://openmediavault-plugin-…github.io/packages/debian shaitan main Result: True Comment: Configured package repo 'deb https://openmediavault-plugin-…github.io/packages/debian shaitan main' Started: 20:48:17.850210 Duration: 7550.989 ms Changes: ---------- repo: deb https://openmediavault-plugin-…github.io/packages/debian shaitan main
    ---------- ID: deb https://openmediavault-plugin-…github.io/packages/debian shaitan-testing main Function: pkgrepo.absent Result: True Comment: Package repo deb https://openmediavault-plugin-…github.io/packages/debian shaitan-testing main is absent Started: 20:48:25.401521 Duration: 95.547 ms Changes: ---------- ID: deb [arch=amd64] https://download.docker.com/linux/debian bullseye stable Function: pkgrepo.managed Result: True Comment: Configured package repo 'deb [arch=amd64] https://download.docker.com/linux/debian bullseye stable' Started: 20:48:25.497215 Duration: 5524.13 ms Changes: ---------- repo: deb [arch=amd64] https://download.docker.com/linux/debian bullseye stable
    ---------- ID: configure_apt_pref_omvextras Function: file.managed Name: /etc/apt/preferences.d/omvextras.pref Result: True Comment: File /etc/apt/preferences.d/omvextras.pref is in the correct state Started: 20:48:31.021608 Duration: 79.951 ms Changes: ---------- ID: refresh_database_apt Function: module.run Result: True Comment: pkg.refresh_db: Success Started: 20:48:31.102348 Duration: 3331.451 ms Changes: ---------- pkg.refresh_db: ---------- file:/var/cache/openmediavault/archives InRelease: False file:/var/cache/openmediavault/archives Packages: True file:/var/cache/openmediavault/archives Release: False file:/var/cache/openmediavault/archives Translation-en: False http://deb.debian.org/debian bullseye InRelease: None http://deb.debian.org/debian bullseye-updates InRelease: None http://httpredir.debian.org/debian bullseye-backports InRelease: None http://packages.openmediavault.org/public shaitan InRelease: None http://security.debian.org/debian-security bullseye-security InRelease: None https://download.docker.com/linux/debian bullseye InRelease: None https://openmediavault-plugin-…github.io/packages/debian shaitan InRelease: None https://openmediavault.github.io/packages shaitan InRelease: None

    Summary for warehouse21
    ------------
    Succeeded: 6 (changed=4)
    Failed: 0
    ------------
    Total states run: 6
    Total run time: 16.586 s
    Processing triggers for openmediavault (6.0.11-1) ...
    Updating workbench configuration files ...
    Restarting engine daemon ...

    votdev, i am getting tiered of this. Can you give me

    • a pointer, where the patch command is called (no idea of salt until now) and
    • an idication if you would consider accepting a patch for that. I would then try to wrap the cal lto patch into a script which will call patch, filter this error message (only for "Reversed (or previously applied) patch detected") and convert the return code to 0.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    • Offizieller Beitrag
    Zitat von Zoki

    votdev, i am getting tiered of this. Can you give me

    • a pointer, where the patch command is called (no idea of salt until now) and
    • an idication if you would consider accepting a patch for that. I would then try to wrap the cal lto patch into a script which will call patch, filter this error message (only for "Reversed (or previously applied) patch detected") and convert the return code to 0.

    It's not possible to do anything here because the Salt file.patch state does not support a verbose or quiet option. I hope that SaltStack will release a new version in near future that includes the patches AND that will include a bugfix that prevents the use of Salt 3004 in OMV6. Hopefully Salt 3005 will be released soon.

    Understand.

    The note: "A suitable patch executable must be available on the minion." implies one coud fake the path settings of salt and put a "improved" patch before the os one. May be doable, but it is better to wait for an official version.


    Drop a note, if time comes you need someone to try that.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    • Offizieller Beitrag
    Zitat von dsm1212

    Failed: 0

    This is all you need to look at.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Just FYI: For the update from 6.0.11-1 to 6.0.12-1 I got the errors again. This time I didn't get a success/failed summary. Actually I think the old interface printed Done when the update finished didn't it? The new one I just watch for the close to be enabled and then I assume it is finished...



    Preparing to unpack .../openmediavault_6.0.12-1_all.deb ...
    Unpacking openmediavault (6.0.12-1) over (6.0.11-1) ...
    Setting up openmediavault (6.0.12-1) ...
    Creating configuration database ...
    Migrating configuration database ...
    Setting up Salt environment ...
    [ERROR ] Command '/usr/bin/patch' failed with return code: 1
    [ERROR ] stdout: patching file /tmp/__salt.tmp.0iya_o2q (read from /lib/python3/dist-packages/salt/modules/network.py)
    Reversed (or previously applied) patch detected! Skipping patch.
    1 out of 1 hunk ignored -- saving rejects to file /tmp/__salt.tmp._inju0rb
    [ERROR ] retcode: 1
    [ERROR ] Command '/usr/bin/patch' failed with return code: 1
    [ERROR ] stdout: patching file /tmp/__salt.tmp.p4vr7t9k (read from /lib/python3/dist-packages/salt/fileserver/roots.py)
    Reversed (or previously applied) patch detected! Skipping patch.
    1 out of 1 hunk ignored -- saving rejects to file /tmp/__salt.tmp.tda4ft8c
    [ERROR ] retcode: 1
    Processing system modifications ...
    Processing triggers for rsyslog (8.2102.0-2) ...
    Processing triggers for openmediavault (6.0.12-1) ...
    Restarting engine daemon ...
    Updating workbench configuration files ...

    • Offizieller Beitrag
    Zitat von dsm1212

    I got the errors again

    Still just warnings and nothing to worry about.


    Zitat von dsm1212

    This time I didn't get a success/failed summary.

    Salt didn't change any config for any module. No problems there.

    Zitat von dsm1212

    Actually I think the old interface printed Done when the update finished didn't it? The new one I just watch for the close to be enabled and then I assume it is finished...

    OMV 5.x did. OMV 6.x has a progress bar at the top of dialog that stops and the close button becomes enabled.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • votdev

    Hat das Label gelöst hinzugefügt.

  • votdev

    Hat das Label Update hinzugefügt.

  • votdev

    Hat das Label OMV 6.x (RC1) hinzugefügt.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden