Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dataverse-1 container missing deployment on first launch. [WIN] #9949

Closed
jp-tosca opened this issue Sep 22, 2023 · 0 comments · Fixed by #10094
Closed

Dataverse-1 container missing deployment on first launch. [WIN] #9949

jp-tosca opened this issue Sep 22, 2023 · 0 comments · Fixed by #10094
Labels
Component: Containers Anything related to cloudy Dataverse, shipped in containers. Feature: None No user-facing feature in particular Type: Bug a defect User Role: Hackathon Participant Core developers, frequent contributors, drive-by contributors, etc.
Milestone

Comments

@jp-tosca
Copy link
Contributor

What steps does it take to reproduce the issue?
This was tested on windows, not sure this is the same on other platforms.

  1. git clone https://github.com/IQSS/dataverse.git
  2. mvn -Pct clean package
  3. mvn -Pct docker:run
  4. Visit localhost:4848 and login with admin
  5. Go to applications
  6. "No items found" will be displayed on the list of applications.
  7. docker container restart dataverse-1
  8. Visit localhost:4848 and login with admin
  9. Go to applications
  10. Dataverse should be listed
  • When does this issue occur?
    On a fresh clone of the repository after building the containers.

  • Which page(s) does it occurs on?
    n/a

  • What happens?

After cloning and building the repository and starting the containers configbaker-1 will never be able to connect to [http://dataverse:8080/api/info/version], the cause of this is that the application is not deployed the first time that the Dataverse-1 container launches.
 

  • To whom does it occur (all users, curators, superusers)?

So far windows, not sure if this affects other platforms.

  • What did you expect to happen?

the dataverse application should be able to be accessed and dependencies on configbaker-1 should be able to be resolved.

Which version of Dataverse are you using?
6.0

Any related open or closed issues to this bug report?

Screenshots:
image

image

image

@pdurbin pdurbin added the Component: Containers Anything related to cloudy Dataverse, shipped in containers. label Sep 22, 2023
@pdurbin pdurbin added Type: Bug a defect User Role: Hackathon Participant Core developers, frequent contributors, drive-by contributors, etc. Feature: None No user-facing feature in particular labels Oct 8, 2023
@pdurbin pdurbin moved this to Containerization (Oliver) in IQSS Dataverse Project Oct 8, 2023
jp-tosca added a commit that referenced this issue Nov 3, 2023
windows the first time the container started due
a race condition and the database not being available
pdurbin added a commit that referenced this issue Nov 4, 2023
@github-project-automation github-project-automation bot moved this from Containerization (Oliver) to Clear of the Backlog in IQSS Dataverse Project Nov 4, 2023
@pdurbin pdurbin added this to the 6.1 milestone Nov 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Containers Anything related to cloudy Dataverse, shipped in containers. Feature: None No user-facing feature in particular Type: Bug a defect User Role: Hackathon Participant Core developers, frequent contributors, drive-by contributors, etc.
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

2 participants