Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
A
ansible
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 36
    • Issues 36
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • las-it-organisation
  • 32-0-IT instructions and rules
  • ansible
  • Issues
  • #67

Closed
Open
Opened May 03, 2019 by julian.gethmann@gethmannOwner

NFS might not be mounted on start

Calling host: asterix.las.kit.edu (Fedora 29)

Failing nodes: asterix.las.kit.edu

Summary

NFS is not mounted on boot.

Steps to reproduce

Boot the computer

What is the current bug behavior?

las-archiv1 is not mounted though it is in the fstab

What is the expected correct behaviour?

las-archiv1 is mounted after booting

Possible fixes

Probably the mounts are done before the network target is reached and therefore the NFS export is not viewable at that time, yet.

/cc @gethmann

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: las-it-organisation/32-0-IT-InstructionsAndRules/ansible#67