Closed
Bug 965540
Opened 11 years ago
Closed 11 years ago
Unable to start nucleus on dev paas
Categories
(Infrastructure & Operations :: IT-Managed Tools, task)
Infrastructure & Operations
IT-Managed Tools
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jgmize, Assigned: cturra)
References
Details
When trying to push the latest nucleus code to the dev paas, I get the following error, repeated many times, in the shell and in the logs:
Waiting for filesystem service to appear at /app/fs/media
|
Assignee | |
Comment 1•11 years ago
|
||
as discussed on irc, it looks like the filesystem in question here might have been affected by the nfs volume move work we did last night. essentially these filesystem services are just directories on an volume - what i noticed is many of the old ones do not have a valid unix user assigned to them.
Josh and i deleted the application and did a new stackato push creating a new filesystem service. this came up as expected. we did see some filesystem gateway timeouts, which is something being tracked in bug 949425. to get around that issue, we just needed to push a second time.
marking this as r/fixed now that the application has deployed successfully to the dev cluster.
Assignee: server-ops-webops → cturra
Status: NEW → RESOLVED
Closed: 11 years ago
OS: Linux → All
Hardware: x86_64 → All
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•