View Issue Details

IDProjectCategoryView StatusLast Update
0005109Talerdeployment and operationspublic2017-10-18 13:42
ReporterMarcello Stanisci Assigned ToMarcello Stanisci Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PriorityhighSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Versiongit (master) 
Target Version0.4Fixed in Version0.4 
Summary0005109: Need same merchant key regardless of the color
DescriptionThe current deployment scheme gives each color (blue/green) a different merchant instance private key.

That makes the db look different when the color is switched, because a lot of db methods take the instance key among their parameters.

Take this problem example:

test-green blog sells article X, then article X shows up in backoffice sold items.
Let's then switch to test-blue; article X then does NOT show up in backoffice sold items, because the db method will try to find article X against test-blue's public key,
which fails.

So deployment scripts should make sure all colors have the same key.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Relationships

related to 0005054 closedMarcello Stanisci 'contract_terms not found' for transaction which correctly went through 

Activities

Marcello Stanisci

2017-07-18 08:40

reporter   ~0012342

taler-auditor-sign does not pick [auditordb-postgres]/db_conn_str from custom .config/taler.conf

Marcello Stanisci

2017-07-18 09:47

reporter   ~0012343

problem was that taler-auditor-sign doesn't check if -c option has been given or not, and calls GNUNET_CONFIGURATION_load with cfgfile == (null).

temporarily fixed by passing "-c .config/taler.conf" to deployment script.

Marcello Stanisci

2017-07-18 09:48

reporter   ~0012344

Last edited: 2017-07-18 10:01

shared-data directory needs (persistent) write permission for group 'test'

UPDATE: well, not a real issue, as it sufficies to manually set permission when shared-data directory is created.

Marcello Stanisci

2017-07-19 09:44

reporter   ~0012349

73f1be4 @ deployment closes this.

Issue History

Date ModifiedUsernameFieldChange
2017-07-16 11:08Marcello StanisciNew Issue
2017-07-16 11:09Marcello StanisciSummarySame merchant key regardless of the color => Need same merchant key regardless of the color
2017-07-16 11:10Marcello StanisciDescription Updated
2017-07-18 08:40Marcello StanisciNote Added: 0012342
2017-07-18 09:45Marcello StanisciAssigned To => Marcello Stanisci
2017-07-18 09:45Marcello StanisciStatusnew => assigned
2017-07-18 09:47Marcello StanisciNote Added: 0012343
2017-07-18 09:48Marcello StanisciNote Added: 0012344
2017-07-18 09:52Marcello StanisciNote Edited: 0012344
2017-07-18 10:01Marcello StanisciNote Edited: 0012344
2017-07-18 10:30Marcello StanisciPrioritynormal => high
2017-07-19 07:35Marcello StanisciRelationship addedrelated to 0005054
2017-07-19 09:44Marcello StanisciNote Added: 0012349
2017-07-19 19:46Marcello StanisciStatusassigned => informing
2017-07-19 19:46Marcello StanisciResolutionopen => fixed
2017-07-20 07:23Christian GrothoffProduct Version => git (master)
2017-07-20 07:23Christian GrothoffFixed in Version => 0.4
2017-07-20 07:23Christian GrothoffTarget Version => 0.4
2017-10-18 13:42Christian GrothoffStatusinforming => closed