View Issue Details

IDProjectCategoryView StatusLast Update
0011805Talerdeployment and operationspublic2026-09-18 12:52
Reportervecirex Assigned Tovecirex  
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status confirmedResolutionopen 
Summary0011805: test taler-merchant + taler-merchant-webui (1.6.24 / 1.6.46) on stage.my.taler-ops.ch
Description# Pre-deployment Sign-off

Scope:
- Full stage verification of combined stack already matching trixie-testing tip
- Backend: taler-merchant 1.6.24 (build_version 1.6.24, protocol 42:0:30)
- WebUI: taler-merchant-webui 1.6.46
- One merchant basis (backend); no separate merchants per subcomponent
- Payments for this ticket: CHF:0 only (talersticker / stickers template)
- Create dedicated instance named with backend version + smoke template

Relevant hosts:
- stage.my.taler-ops.ch (betel)

Relevant tags / packages:
- Live/stage: backend 1.6.24 / WebUI 1.6.46
- APT reference: trixie-testing taler-merchant=1.6.24-0+trixie , taler-merchant-webui=1.6.46-0+trixie
- Git: merchant v1.6.24 ; typescript-core v1.6.46
- Diff vs current prod for extra cases: backend v1.6.22->v1.6.24 ; WebUI v1.6.33-dev.7->v1.6.46

Known critical bugs:
- (none listed; add related Mantis IDs if any)

Setup (before tests):
- Create instance id: so-backend-1-6-24
  expect: instance exists; auth works
- Create public template: stickers (or reuse) with amount CHF:0 for talersticker path
  expect: template order create works
- Create additional smoke template: smoke-1-6-24 (minimal CHF:0)
  expect: template visible; order create HTTP 200

Tests (commands + expected):

Version / health:
curl -fsS https://stage.my.taler-ops.ch/config | jq -r '.name,.build_version,.version'
# expect: taler-merchant / 1.6.24 / 42:0:30

dpkg-query -W taler-merchant taler-merchant-webui
# expect: 1.6.24-0+trixie / 1.6.46-0+trixie

curl -fsS -o /dev/null -w '%{http_code}\n' https://stage.my.taler-ops.ch/webui/
# expect: 200

- live-harness tests (before suite): ok:___ / info:___ / fail:___

Payment / template (CHF:0 only):
- Create order from template stickers on instance so-backend-1-6-24 with amount CHF:0
  expect: order_id returned; pay URI/QR present
- Wallet/pay path for that order (stage exchange)
  expect: paid/settled success (or documented stage wallet result)
- Repeat via smoke-1-6-24 template
  expect: same success class
- COUNT=3 (or agreed N) CHF:0 sticker pays
  expect: N/N success; 0 unexpected fail

WebUI smoke on so-backend-1-6-24:
- Login; Orders; Templates; Products; Settings auth/token lifetime; template OTP device field; locked-product delete messaging; machine access token after MFA (if MFA test account exists)
  expect: pages load; actions match backend 1.6.24 capabilities

Diff-driven extras vs prod (22/33-dev.7 -> 24/46):
- Backend: operator-owned DB migrations posture; DD102 restart/exit; no order serial reuse after migration; pickup duration on template orders; KYC wake on status request; MFA/password/token behaviors from 1.6.23
- WebUI: login token lifetime config; template OTP device; locked-product deletion guidance; machine access tokens after MFA; plus 1.6.43 set (phone MFA, reauth, account deletion, live exchange status, i18n, product prices)
  expect: each checked item ok or explicitly N/A with reason

Closing:
- live-harness tests (after suite): ok:___ / info:___ / fail:___
  expect: fail=0 preferred; any fail triaged in ticket notes

Special considerations:
- Stage only; not a prod deploy
- Amount fixed CHF:0 for this ticket (no ECHT ladder)
- Instance naming keyed to backend version 1.6.24
- DB migrations: already applied on stage; do not re-run casually
- API protocol on stage is 42:0:30 (prod still 38:0:26 until backend prod ticket)

Other accepted risks:
- MFA phone / account deletion may use throwaway stage personas only
- Mixed payments covered only if enabled on stage instance

Sign-off:
- $NAME, $DATE

# Post-deployment report

Timeline:
- (suite start/end; instance/template creation times)

Post-deployment checks:
- (paste /config, dpkg-query, CHF:0 pay results, live-harness before/after lines)

Issues addressed:
- (if any)

Other issues:
- (if any)
Tagsmytops, quality, srv-betel

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2026-09-18 12:13 vecirex New Issue
2026-09-18 12:13 vecirex Status new => assigned
2026-09-18 12:13 vecirex Assigned To => vecirex
2026-09-18 12:13 vecirex Status assigned => confirmed
2026-09-18 12:35 vecirex Tag Attached: mytops
2026-09-18 12:35 vecirex Tag Attached: quality
2026-09-18 12:35 vecirex Tag Attached: srv-betel
2026-09-18 12:38 vecirex Category paivana => deployment and operations
2026-09-18 12:52 vecirex Severity minor => feature