Testing of qvm-tags-in-pillar under R4.2 is needed!

[gonzalo-bulnes]

Opening this issue as a placeholder for @ben-grande's sake. I'll add details (including the full error message) when I've time to investigate further, but help is welcome!

The default Salt configuration in R4.2 doesn't seem to allow qvm-tags-in-pillar and qvm-features-in-pillar to work.

I'm not sure what changed since R4.1, but the pillar extensions are consistently reported as "not found" in my early testing.

If anyone was able to confirm this, that would be a great first step towards documenting and troubleshooting the issue so that it can be fixed either upstream if the change of behaviour wasn't intentional, or here if adjustments to those two states are needed.

[gonzalo-bulnes]

@ben-grande Heads up, if this issue is confirmed, it affects the feature discussed in #14 and ben-grande/qusal#41 (under R4.2 that is the current Qubes OS version now).

[gonzalo-bulnes]

Also heads up @bcduggan in case you've noticed (or not!) this issue yourself. 🙂

[ben-grande]

Thanks for the ping. I can test but in some weeks from now only.

…

On Mon, Mar 25, 2024, 3:34 PM Gonzalo Bulnes Guilpain < ***@***.***> wrote: *Opening this issue as a placeholder fir @ben-grande <https://github.com/ben-grande>'s sake. I'll add details (including the full error message) when I've time to investigate further, but help is welcome!* The default Salt configuration in R4.2 diesn't seem to allow qvm-tags-in-pillar and qvm-features-in-pillar to work. I'm not sure what changed since R4.1, but the pillar extensions are consistently reported as "not found" in my early testing. If anyone was able to confirm this, that would be a great first step towards documenting and troubleshooting the issue so that it can be fixed either upstream if the change of behaviour wasn't intentional, or here if adjustments to those two states are needed. — Reply to this email directly, view it on GitHub <#27>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BCE2O4MAQPFPODSB7TZBLL3Y2AYWHAVCNFSM6AAAAABFHECLK6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGIYDKOJQG43TANA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[gonzalo-bulnes]

@ben-grande Let me know if you need a hand getting set up when the time comes (e.g. if you decide to go the RPM package way, though the two states are small enough that even a re-write in dom0 shouldn't take too long!)

[gonzalo-bulnes]

Might be relevant (or not!)—if I remember correctly the error message was similar but not the same:

I had the error [CRITICAL] Specified ext_pillar interface qvm_prefs is unavailable on a working 4.2 [...]

The recommend command qubesctl saltutil.sync_all solved it.

(source)

[ben-grande]

Tested on R4.2 and it works!

The recommend command qubesctl saltutil.sync_all solved it.

Yes, necessary.