snapd

Fetch-assertion requests lacking refresh reason header

Bug #1937309 reported by Maximiliano Bertacchini on 2021-07-22

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	snapd	Fix Released	High	Miguel Pires	snapd 2.53

Bug Description

We've noticed that a significant amount of all refresh requests handled by the Snap Store unexpectedly lack the "Snap-Refresh-Reason: scheduled" header. On closer inspection, we found that most of them are "fetch-assertion" actions, which are initiated automatically as part of automatic snap refreshes. Apparently, only "refresh" actions include this header.

Having these requests correctly marked with this header would help us collect more accurate metrics and better prioritize traffic.

See original description

Maximiliano Bertacchini (maxiberta) on 2021-07-22

description:

updated

Ian Johnson (anonymouse67) on 2021-07-22

no longer affects:

snappy

Samuele Pedroni (pedronis) on 2021-07-23

Changed in snapd:
assignee:	nobody → Samuele Pedroni (pedronis)

Paweł Stołowski (stolowski) on 2021-07-27

Changed in snapd:
status:	New → Triaged
importance:	Undecided → High

Revision history for this message

Miguel Pires (miguelpires1) wrote on 2021-08-18:

https://github.com/snapcore/snapd/pull/10584

Changed in snapd:
assignee:	Samuele Pedroni (pedronis) → Miguel Pires (miguelpires1)
status:	Triaged → In Progress

Miguel Pires (miguelpires1) on 2021-08-25

Changed in snapd:
status:	In Progress → Fix Committed

Ian Johnson (anonymouse67) on 2021-10-21

Changed in snapd:
milestone:	none → 2.53

Miguel Pires (miguelpires1) on 2022-11-11

Changed in snapd:
status:	Fix Committed → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.