Error user cannot be added, directories are read only

Question

Dear all,

We have deployed on azure an Atlassian docker image connected to an empty sql server database and process the whole setup and be able to setup the Atlassian admin account

Then we have an existing staging database with all our existing setting, projects, SSO configuration, licences,etc.

What we are trying to do is from that previous setup, then connect the deployed docker instance to our SQL db with all data.

For that we have :

* edit the dbconfig.xml file and simply change to the correct DB
* Restart the container

Then what happen after this is when we hit the ip of our docker instance, it start  a new process of setup from scratch even if we provide an already configured DB

It request also the creation of an admin account which cannot be created because it says "Directories are read only"

I am stuck for days in this situation now and I would like to know how can I point my instance to use the given database data which contains everything instead of redoing a full setup.

Any idea what is happening or how to do ?

regards

Calderara Serge · Answer

@Rilwan Ahmed thanks for your reply.

I have a doubt to about what you are saying which is probably true but We have a production instance where some time we copy the db and place it on our staging instance on difference server and switching Db like this works without trouble

The process I have done is the one describe by atlassian in their document for migrating application from one server to an other, so I I have no idea why it should not work ?

regards

Rilwan Ahmed · Answer

I am not sure. But I think, every new installation is taken as new SEN number. Jira considers it as new jira and asks for setup.

serge calderara · Answer

@Rilwan Ahmed thanks for your reply.

Yes in my old jira instance Directories a in following orders:

1 Active Directory (Enabled)

2- Internal directory (Enabled)

To explain clearly what I have done :

My old instance DC node 1 is configured as below :
- media/atl/jira/shared is maped to a Azure storage file share call home-dc-shared
- original db is called jiradb on Server1, then I create a copy named NewJiraDB on Server2

What I have done :

* Deployed an atlassian docker Image to Azure with an empty SQL db located on Server2
* Provide a dumy admin user as requested
* Stop my container instance
* Update the dbconfig.xml to point to the copy db NewJiraDB
* Restart the container
* Then I loged in with the admin login I have set in my old jira => FAILED
* Then I loged in with my previous dumy admin => OK
* Then I am prompt again to enter Licence and create user admin

Then I am stuck at this stage, I do not undertsand why Jira is procedeing to setup phase again after pointing it to my copy db which contains every thing

Any idea what I miss or what is wrong ?