Skip to content

[uss_qualifier/scenarios/dss] Check that OIR requests rejected for missing OVNs leave subscriptions unchanged - #1831

Open
MariemBaccari wants to merge 1 commit into
interuss:mainfrom
Orbitalize:add_implicit_sub_test
Open

MariemBaccari wants to merge 1 commit into
interuss:mainfrom
Orbitalize:add_implicit_sub_test

Conversation

@MariemBaccari

Copy link
Copy Markdown
Contributor

interuss/dss#1792 reported that, since interuss/dss#1690, a DSS rejecting an oir PUT with a 409 (missing OVNs) persists subscription changes. A conflicting creation with new_subscription leaves behind a new implicit subscription, and a conflicting mutation that specifies an existing implicit subscription changes it. This PR extends OIRKeyValidation to check that rejected requests have no side effect on subscriptions.

@MariemBaccari
MariemBaccari force-pushed the add_implicit_sub_test branch 2 times, most recently from c80c459 to ce7c563 Compare October 20, 2026 08:42

@BenjaminPelletier BenjaminPelletier left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me with one small change and one possible (but not required) change.


**[astm.f3548.v21.DSS0005,5](../../../../../../requirements/astm/f3548/v21.md)** requires the implementation of the DSS endpoint to allow callers to retrieve the subscriptions they created.

## 🛑 Rejected request did not create or modify subscriptions check

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this check fails, it seems like the test scenario can still continue since that's what it did before. And, continuing test execution after check failure is the preferred outcome unless it would be very difficult to do so because knowing all the problems in one run is far better than each run revealing only the first-encountered problem.

Suggested change
## 🛑 Rejected request did not create or modify subscriptions check
## ⚠️ Rejected request did not create or modify subscriptions check


The subscriptions owned by the client within the planning area are queried before and after the rejected request, and compared.

## 🛑 Successful subscription search query check

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this needs to change since this fragment is only being run at the end of a scenario and it's a little harder to skip the check below if this one fails, but it seems like failing this check could allow the test scenario to continue (and therefore be changed to ⚠️ severity) if there were logic to skip attempting the check below.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants