[Google Pixel 8 Pro] badabing2003:
I see that your device is currently on slot b and slot be verity/verification is disabled, whereas slot a is enabled.

If you ever boot to slot a, they would get enabled again, and to disable them you would need to wipe.

=======================================
Selected Device on 2024-06-27 23:06:04:
=======================================
Device ID: REDACTED
Device Model: husky
Device Active Slot: b
Device Mode: adb
Device Name: Pixel 8 Pro
Device First API Level: 34
Device Version End Date: October 2030
Device Security Update End Date: October 2030
Has init_boot partition: True
Device Bootloader Version: ripcurrent-14.4-11403750
Device is Rooted: True
Device Build: AP1A.240505.005
Device API Level: 34
Android Version: 14
Android Name: Android 14
Android Codename: Upside Down Cake
Android Release Date: Q3 2023
Android Latest Update: Present
Device Architecture: arm64-v8a
Device Kernel: Linux localhost 5.15.131-android14-11-gd99d9fe08e0c-ab11209359 #1 SMP PREEMPT Tue Dec 12 17:18:56 UTC 2023 aarch64 Toybox
Device Kernel Version: 5.15
Device KMI: 5.15.131-android14
sys_oem_unlock_allowed: 1
ro.boot.flash.locked: 1
ro.boot.vbmeta.device_state:
ro.product.first_api_level: 34
ro.boot.veritymode:
ro.boot.verifiedbootstate: green
ro.secure: 1
ro.zygote: zygote64
ro.vendor.product.cpu.abilist: arm64-v8a
ro.vendor.product.cpu.abilist32:
vbmeta type: ab
Slot A Verity: Enabled
Slot A Verification: Enabled
Slot B Verity: Disabled
Slot B Verification: Disabled
WARNING! WARNING! WARNING! Slot a verity / verification does not match slot b verity / verification WARNING! WARNING! WARNING! There is a mismatch of currently selected vbmeta verity state and device's verity state
WARNING! WARNING! WARNING! There is a mismatch of currently selected vbmeta verification state and device's verification state
This has a device wipe implications, please double check.
Magisk Manager Version: 1.0:1
Checked for Package: tpvlsflmn.g.hq.non
KernelSU App Version: :
APatch App Version: :
Magisk Version: 27.0:27000
Magisk Config SHA1: 3b14ba68ebacc15e86bea283d644c2739b5c8f9b
Magisk Modules:
Systemless Hosts enabled 1.0
Play Integrity Fork enabled v8 [Update Available]

So how do you fix this?

Download the latest OTA for your device

Load it in PF, process it, and create a Magisk Patch

Select the patched init_boot from the list

Then Flash Pixel Phone, making sure you select to disable verity / verification.

If everything goes fine, your system should reboot to slot A, rooted with verity / verification disabled.

Flash Pixel phone one more time, to make sure slot B is also the same.

You should be find.

By the way, this is ok

Cancelling ongoing OTA update (if one is in progress, ignore errors) ...
[ERROR:update_engine_client_android.cc(316)] Status(-8, EX_SERVICE_SPECIFIC): '1: No ongoing update to cancel.'
Resetting an already applied update (if one exists) ...

Notice how it says ignore errors.

Errors are expecting if the update is not currently applying.

The resetting part should have cleared it from your device.

If you encounter any issues, stop and don't continue, post another support file just so we make sure you don't accidentally end up needing a wipe.