-
Bug
-
Resolution: Fixed
-
High
-
10.2.0, 10.3.2, 10.3.3
-
10.02
-
14
-
Severity 2 - Major
-
58
-
Issue Summary
NFS and SMB/CIFS shares are supported as the locations of the shared directory. Jira fails to start when CIFS shares are configured as the locations for the shared directory.
This is reproducible on Data Center: YES
Steps to Reproduce
- Install Jira version 9.16 and Start the Jira application.
- Configure a CIFS share and mount it within the Jira instance.
- Copy the contents from the local home directory to the CIFS share home directory.
- Create the cluster.properties file by configuring the shared home (i.e., the CIFS location).
- Restart Jira. The application start correctly with the shared home path configured in the previous steps.
- Proceed to install Jira version 10.3.3.
- Conduct an upgrade of Jira from version 9.16 to 10.3.3.
- Following the upgrade, the Jira application fail to start, displaying the errors outlined below.
2025-02-11 15:52:22,201+0000 main INFO [c.a.jira.startup.TemporaryDirectoryCleaner] Cleaning the temporary directory located at /install/atlassian-jira-software-10.3.3-standalone/temp
2025-02-11 15:52:22,202+0000 main INFO [c.a.jira.startup.TemporaryDirectoryCleaner] Finished cleaning the temporary directory.
2025-02-11 15:52:22,570+0000 main INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /jirasoftware-home/dbconfig.xml
2025-02-11 15:52:22,943+0000 main INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /jirasoftware-home/dbconfig.xml
2025-02-11 15:52:32,953+0000 main INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /jirasoftware-home/dbconfig.xml
2025-02-11 15:52:32,960+0000 main WARN [c.a.s.service.lock.ConfigFileLock] Lock file /mnt/shared/secrets-config.yaml.lock is stale, removing it.
2025-02-11 15:52:32,984+0000 main INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /jirasoftware-home/dbconfig.xml
2025-02-11 15:52:43,293+0000 main INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /jirasoftware-home/dbconfig.xml
2025-02-11 15:52:43,301+0000 main WARN [c.a.s.service.lock.ConfigFileLock] Lock file /mnt/shared/secrets-config.yaml.lock is stale, removing it.
2025-02-11 15:52:44,154+0000 main INFO [c.a.jira.startup.JiraStartupLogger]
___ Starting the JIRA Plugin System _________________
2025-02-11 15:52:51,663+0000 main INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /jirasoftware-home/dbconfig.xml
2025-02-11 15:53:01,716+0000 main INFO [c.a.jira.startup.JiraStartupLogger] Running Jira startup checks.
2025-02-11 15:53:01,717+0000 main INFO [c.a.jira.startup.JiraStartupLogger] Jira pre-database startup checks completed successfully.
2025-02-11 15:53:01,762+0000 main INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Database Checklist Launcher on post-database-configured-but-pre-database-activated queue
2025-02-11 15:53:01,763+0000 main INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Post database-configuration launchers on post-database-activated queue
2025-02-11 15:53:01,778+0000 main INFO [c.a.jira.startup.LauncherContextListener] Startup is complete. Jira is ready to serve.
Expected Results
Jira should start without any errors following the upgrade.
Actual Results
The Jira startup process is not completing successfully, resulting in messages such as "The database is not yet configured" and "Lock file /mnt/shared/secrets-config.yaml.lock is stale, removing it." Additionally, unable to access Jira after the startup attempt.
Workaround
Disable the secret storage using the property below :
-Datlassian.secret.service.state=disabled
