View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0010770Talerdeployment and operationspublic2025-12-12 17:482025-12-13 15:05
Reportervecirex Assigned Tovecirex  
PrioritynormalSeveritytrivialReproducibilityhave not tried
Status closedResolutionfixed 
Summary0010770: Upgrade existing TOPS/CHF test infra from v1.2.3 to v1.2.4 and do production-relevant tests [payment issue with iOS emerged]
DescriptionWe will test tonight if an upgrade from v1.2.3 to the next release v1.2.4 works, that on my non-crtiical taler.hacktivism.ch installation; for sure, a further version v1.2.5 fixing a few i18n/l10n strings is needed, cf. also https://bugs.gnunet.org/view.php?id=10702#c26937.

After the upgrade, as the very basis the following needs to be tested and done:

1.
Login to one of the self-provisioning instances with a verified IBAN acc. (KYC done, payments can be accepted).

2.
Pay to an already defined article, using in both cases the *currently* released Android and iPhone wallets.

3.
Use the template system in POS/inventory (non-expert, non.dev) mode to create a further article with all fields editable (text of the item as well as price).

4.
Repeat 2 on the new QR code from 3.

5.
See if the payments are shown properly in the backend and things are understandable: by this, also ticket 0010685 can most probably be closed. If overview is better, but there are still clearly visible issues, but just minor, we can also decide to remove ticket 0010685 as an actual blocker to 0010630. It would just be bad to do so if someone of us cannot easily grasp what's being shown there, as this happens to be the case until the current version v1.2.3.

6.
Despite the specific ticket mentioned in 5, go through all other tickets blocking 0010630 which are marked as open or solved and see if they're actually solved and not open anymore a/o if they're really resolved and marked as such, respectively: if so, close them. Tickets (assigned to me) which are related to the test or production infrastructure are not in scope here, it's just about tickets which directly relate to the taler-merchant software per se. The infra-related tickets are to be solved by me step by step, finally having 0010630 itself done by Tue, 16.12.
TagsNo tags attached.

Relationships

related to 0010702 assignedvecirex Test fresh install of taler-merchant v1.3.0 or higher in TOPS/CHF test env: version with which my.taler-ops.ch is live [2h] 
related to 0010771 feedbackvecirex taler-merchant v1.2.4 comes up with new warnings: check which of them are good predictors for more config needed 
child of 0010630 closedvecirex Set my.taler-ops.ch live [done in principle by this morning: still solving deps; work parallelized] 

Activities

vecirex

2025-12-12 18:04

manager   ~0026938

Add steps to do after the upgrade per se is done.

vecirex

2025-12-12 18:08

manager   ~0026939

Make point 5. clearer: -v

vecirex

2025-12-12 18:16

manager   ~0026940

Make point 6. clearer, too: -v

vecirex

2025-12-13 06:15

manager   ~0026948

Last edited: 2025-12-13 06:45

 Upgrade went through successfully, prior DB backup done with
pg_dump taler-merchant > $file
# with user
taler-merchant-httpd@bcead3ae4f5e:/$ echo $USER
taler-merchant-httpd

No DB scheme update was necessary this time (cf. last time, going from v1.2.1 to v1.2.3: https://bugs.gnunet.org/view.php?id=10701#c26703); using the command line option --log=info for taler-merchant-httpd now shows some additional warnings, given additional options available, but not yet set (if all of them relevant for production: separate ticket to address this in production is 0010771); errors, however, so far not visible (tests mentioned in descr to be carried out next).

Immediate output from taler-merchant-httpd is this:

root@bcead3ae4f5e:/# su -s /bin/bash taler-merchant-httpd
taler-merchant-httpd@bcead3ae4f5e:/$ taler-merchant-httpd --log=info &
[1] 179148
taler-merchant-httpd@bcead3ae4f5e:/$
taler-merchant-httpd@bcead3ae4f5e:/$ taler-merchant-webhook &
[2] 179149
taler-merchant-httpd@bcead3ae4f5e:/$
taler-merchant-httpd@bcead3ae4f5e:/$ taler-merchant-kyccheck &
[3] 179150
taler-merchant-httpd@bcead3ae4f5e:/$
taler-merchant-httpd@bcead3ae4f5e:/$ taler-merchant-wirewatch &
[4] 179151
taler-merchant-httpd@bcead3ae4f5e:/$
taler-merchant-httpd@bcead3ae4f5e:/$ taler-merchant-depositcheck &
[5] 179152
taler-merchant-httpd@bcead3ae4f5e:/$
taler-merchant-httpd@bcead3ae4f5e:/$ taler-merchant-exchangekeyupdate &
[6] 179153
taler-merchant-httpd@bcead3ae4f5e:/$
taler-merchant-httpd@bcead3ae4f5e:/$ taler-merchant-reconciliation &2025-12-13T05:02:17.667487+0000 taler-merchant-httpd-179148 INFO Starting taler-merchant-httpd
2025-12-13T05:02:17.667662+0000 taler-merchant-httpd-179148 INFO Configuration fails to specify option `DEFAULT_PAY_DELAY' in section `merchant'!
2025-12-13T05:02:17.667676+0000 taler-merchant-httpd-179148 INFO Configuration fails to specify option `DEFAULT_REFUND_DELAY' in section `merchant'!
2025-12-13T05:02:17.667681+0000 taler-merchant-httpd-179148 INFO Configuration fails to specify option `DEFAULT_WIRE_TRANSFER_DELAY' in section `merchant'!
2025-12-13T05:02:17.667687+0000 taler-merchant-httpd-179148 INFO Configuration fails to specify option `DEFAULT_WIRE_TRANSFER_ROUNDING_INTERVAL' in section `merchant'!
2025-12-13T05:02:17.667699+0000 taler-merchant-httpd-179148 WARNING Configuration fails to specify option `TERMS_ETAG' in section `merchant'!
2025-12-13T05:02:17.667705+0000 taler-merchant-httpd-179148 WARNING Terms of service not configured
2025-12-13T05:02:17.667860+0000 taler-merchant-httpd-179148 WARNING Configuration fails to specify option `PRIVACY_ETAG' in section `merchant'!
2025-12-13T05:02:17.667872+0000 taler-merchant-httpd-179148 WARNING Privacy policy not configured
2025-12-13T05:02:17.667881+0000 taler-merchant-httpd-179148 INFO Loading merchant SPA from default location
2025-12-13T05:02:17.669998+0000 taler-merchant-httpd-179148 INFO Loading templates from `/usr/share/taler-merchant//templates/'
2025-12-13T05:02:17.670345+0000 taler-merchant-depositcheck-179156 INFO Running with configuration /etc/taler-merchant/taler-mer2025-12-13T05:02:17.671003+0000 taler-merchant-httpd-179148 INFO Loading template `/usr/share/taler-merchant//templates/offer_refund.en.must' (offer_refund)
2025-12-13T05:02:17.671359+0000 taler-merchant-httpd-179148 INFO Loading template `/usr/share/taler-merchant//templates/request_payment.en.must' (request_payment)
2025-12-13T05:02:17.671521+0000 taler-merchant-httpd-179148 INFO Loading template `/usr/share/taler-merchant//templates/show_order_details.en.must' (show_order_details)
chant.conf
2025-12-13T05:02:17.691163+0000 taler-merchant-httpd-179148 INFO Loading SQL resources from `merchant-'
2025-12-13T05:02:17.691715+0000 taler-merchant-depositcheck-179156 INFO Loading SQL resources from `merchant-'
2025-12-13T05:02:17.692290+0000 taler-merchant-httpd-179148 INFO SQL resource `/usr/share/taler-merchant/sql/merchant-0028.sql' does not exist
2025-12-13T05:02:17.692419+0000 taler-merchant-depositcheck-179156 INFO SQL resource `/usr/share/taler-merchant/sql/merchant-0028.sql' does not exist
2025-12-13T05:02:17.692486+0000 taler-merchant-httpd-179148 INFO Setup exchange https://exchange.taler-ops.ch/ as trusted
2025-12-13T05:02:17.751307+0000 taler-merchant-httpd-179148 INFO Parsed 1 wire accounts from JSON
2025-12-13T05:02:17.762936+0000 taler-merchant-depositcheck-179156 INFO Parsed 1 wire accounts from JSON
2025-12-13T05:02:17.942498+0000 taler-merchant-depositcheck-179156 INFO Looking up pending deposits query status was 0
2025-12-13T05:02:17.944444+0000 taler-merchant-depositcheck-179156 INFO Looking up pending deposits query status was 0
2025-12-13T05:02:17.950013+0000 taler-merchant-httpd-179148 INFO Loading latest keys of `https://exchange.taler-ops.ch/' from database
2025-12-13T05:02:17.950371+0000 taler-merchant-httpd-179148 INFO Loaded /keys from database with 1 accounts, 1 fees
2025-12-13T05:02:17.950477+0000 taler-merchant-httpd-179148 INFO Reloaded /keys of https://exchange.taler-ops.ch/ from database
2025-12-13T05:02:17.950578+0000 taler-merchant-httpd-179148 INFO Processing find operations for `https://exchange.taler-ops.ch/'
2025-12-13T05:02:17.950822+0000 taler-merchant-httpd-179148 INFO Received instance settings notification: reload `(null)'
2025-12-13T05:02:17.958123+0000 taler-merchant-httpd-179148 INFO Removing left-over `/run/taler-merchant//httpd/merchant-http.sock' from previous execution
2025-12-13T05:02:17.958715+0000 taler-merchant-httpd-179148 INFO set socket '/run/taler-merchant//httpd/merchant-http.sock' to mode 660
2025-12-13T05:02:18.824388+0000 taler-merchant-httpd-179148 INFO Received notification xw9k15vbekgdmcmn31skh75kvxnd1gtw5mw7wme4c2025-12-13T05:02:18.824381+0000 taler-merchant-depositcheck-179156 INFO Received notification xw9k15vbekgdmcmn31skh75kvxnd1gtw5mmpq0x9ecwtr0 with extra data `https://exchange.taler-ops.ch/'
2025-12-13T05:02:18.827061+0000 taler-merchant-httpd-179148 INFO Received keys change notification: reload `https://exchange.taler-ops.ch/'
w7wme4cmpq0x9ecwtr0 with extra data `https://exchange.taler-ops.ch/'
2025-12-13T05:02:18.880512+0000 taler-merchant-httpd-179148 INFO Parsed 1 wire accounts from JSON
2025-12-13T05:02:18.880765+0000 taler-merchant-depositcheck-179156 INFO Parsed 1 wire accounts from JSON
2025-12-13T05:02:19.058770+0000 taler-merchant-depositcheck-179156 INFO Looking up pending deposits query status was 0
2025-12-13T05:02:19.060590+0000 taler-merchant-depositcheck-179156 INFO Looking up pending deposits query status was 0
2025-12-13T05:02:19.080896+0000 taler-merchant-httpd-179148 INFO Loading latest keys of `https://exchange.taler-ops.ch/' from database
2025-12-13T05:02:19.081334+0000 taler-merchant-httpd-179148 INFO Loaded /keys from database with 1 accounts, 1 fees
2025-12-13T05:02:19.081450+0000 taler-merchant-httpd-179148 INFO Reloaded /keys of https://exchange.taler-ops.ch/ from database
2025-12-13T05:02:19.085606+0000 taler-merchant-httpd-179148 INFO Processing find operations for `https://exchange.taler-ops.ch/'

taler-merchant-httpd@bcead3ae4f5e:/$ taler-merchant-httpd --version
taler-merchant-httpd v1.2.4-git-8ad

vecirex

2025-12-13 06:22

manager   ~0026949

As for the new warnings: 0010771

vecirex

2025-12-13 06:42

manager   ~0026951

Last edited: 2025-12-13 06:44

 @sebasjm: NOT critical, but in the frontend it's written, when logged in

"Taler Backoffice
1.2.4-dev.1 (24:0:12"

Acc. to the merchant git, there are pre-release v1.2.4 marked with dev1, dev2 and dev3, but this version now installed from trixie-testing is the effective v1.2.4 patch release in the v1.2 line, so should not have any dev markers.

I assume, the string was touched last time when creating v1.2.4-dev1 and then forgotten to update.

Perhaps a more dynamic approach, using env / tag info could help here for the future? Thanks!

vecirex

2025-12-13 13:00

manager   ~0026953

Point 1 above fine, points 3 to 4 only fine for Android; real CHF payments with newest released

- Android Taler Wallet v1.1.0 (google 68) work, but for
- iOS Taler Wallet v1.2.0 do NOT work

in both cases with an already existing templated order where text and amount can be freely edited ("protein"), and then also with two newly created templated orders ("protein2" and "protein3") in POS/inventory mode created by the new Taler Merchant v1.2.4.

Unfortunately, the error message shown on iOS is not very helpful, it being (with i18n mix, too):

"Interner Systemfehler

unexpected exception (message:)"

We had this in the past already, was fixed via new wallet version: to be done again for some specific reason?

Screenshots attached contain the QR code which works for Android, but not for iOS.
taler-merchant-payment-template-existing--does-not-work-for-ios.png (33,311 bytes)   
taler-merchant-payment-template-existing--does-not-work-for-ios.png (33,311 bytes)   
taler-merchant-payment-template-new-1--does-not-work-for-ios.png (31,784 bytes)   
taler-merchant-payment-template-new-1--does-not-work-for-ios.png (31,784 bytes)   
taler-merchant-payment-template-new-2--does-not-work-for-ios.png (30,513 bytes)   
taler-merchant-payment-template-new-2--does-not-work-for-ios.png (30,513 bytes)   

vecirex

2025-12-13 13:03

manager   ~0026954

Because of iOS:

Prio++, severity blocker per se

vecirex

2025-12-13 14:00

manager   ~0026955

Last edited: 2025-12-13 14:20

 Update:

All things fine also with the iOS app in above-mentioned v1.2.0: I had a local issue with my LAN doing domain resolution, which the iPhone was using, while Inet connectivity was given at any time also with DNS for other sites, so this was not directly obvious given the very unspecific error msg; only with diagnostic and debugging modes on, it became clearer by error code 7001 that a network-related issue is given. -> 0010772
taler-ios-wallet-1-2-0-failing-paying-in-taler-merchant-1-2-4-using-templated-order_diagnostic-mode+debugging-on.png (147,497 bytes)   
taler-ios-wallet-1-2-0-failing-paying-in-taler-merchant-1-2-4-using-templated-order_diagnostic-mode+debugging-on.png (147,497 bytes)   

vecirex

2025-12-13 14:36

manager   ~0026956

As what concerns point 5 in the descr text, yes, orders paid are shown and it can be grasped what's happening, but there's room for improvement how the amounts are displayed -- separate ticket & suggestion, non-blocking in principle, but nicer is better for demos, of course: 0010773

vecirex

2025-12-13 15:04

manager   ~0026957

Test scope defined here done, thus closing.

Work on other tickets blocking 0010630 ongoing, one of which was closed already before (0010704).

Issue History

Date Modified Username Field Change
2025-12-12 17:48 vecirex New Issue
2025-12-12 17:48 vecirex Status new => assigned
2025-12-12 17:48 vecirex Assigned To => vecirex
2025-12-12 17:48 vecirex Relationship added child of 0010630
2025-12-12 17:49 vecirex Relationship added child of 0010702
2025-12-12 17:49 vecirex Relationship replaced related to 0010702
2025-12-12 18:04 vecirex Description Updated
2025-12-12 18:04 vecirex Note Added: 0026938
2025-12-12 18:08 vecirex Description Updated
2025-12-12 18:08 vecirex Note Added: 0026939
2025-12-12 18:09 vecirex Description Updated
2025-12-12 18:09 vecirex Description Updated
2025-12-12 18:10 vecirex Description Updated
2025-12-12 18:16 vecirex Description Updated
2025-12-12 18:16 vecirex Note Added: 0026940
2025-12-13 06:15 vecirex Summary Upgrade existing TOPS/CHF test infra from v1.2.3 to v1.2.4 (and perhaps to v1.2.5) and do tests => Upgrade existing TOPS/CHF test infra from v1.2.3 to v1.2.4 and do production-relevant tests
2025-12-13 06:15 vecirex Description Updated
2025-12-13 06:15 vecirex Note Added: 0026948
2025-12-13 06:22 vecirex Relationship added related to 0010771
2025-12-13 06:22 vecirex Note Added: 0026949
2025-12-13 06:42 vecirex Note Added: 0026951
2025-12-13 06:44 vecirex Note Edited: 0026951
2025-12-13 06:44 vecirex Note Edited: 0026951
2025-12-13 06:45 vecirex Note Edited: 0026948
2025-12-13 13:00 vecirex Note Added: 0026953
2025-12-13 13:00 vecirex File Added: taler-merchant-payment-template-existing--does-not-work-for-ios.png
2025-12-13 13:00 vecirex File Added: taler-merchant-payment-template-new-1--does-not-work-for-ios.png
2025-12-13 13:00 vecirex File Added: taler-merchant-payment-template-new-2--does-not-work-for-ios.png
2025-12-13 13:03 vecirex Priority high => urgent
2025-12-13 13:03 vecirex Severity trivial => block
2025-12-13 13:03 vecirex Summary Upgrade existing TOPS/CHF test infra from v1.2.3 to v1.2.4 and do production-relevant tests => Upgrade existing TOPS/CHF test infra from v1.2.3 to v1.2.4 and do production-relevant tests [payment issue with iOS emerged]
2025-12-13 13:03 vecirex Note Added: 0026954
2025-12-13 13:59 vecirex Priority urgent => normal
2025-12-13 13:59 vecirex Severity block => trivial
2025-12-13 14:00 vecirex Note Added: 0026955
2025-12-13 14:00 vecirex File Added: taler-ios-wallet-1-2-0-failing-paying-in-taler-merchant-1-2-4-using-templated-order_diagnostic-mode+debugging-on.png
2025-12-13 14:20 vecirex Note Edited: 0026955
2025-12-13 14:36 vecirex Note Added: 0026956
2025-12-13 15:04 vecirex Note Added: 0026957
2025-12-13 15:05 vecirex Status assigned => closed
2025-12-13 15:05 vecirex Resolution open => fixed