Merge branch 'whyunorun' into 'master'

Add FAQ entry for pending jobs before a downtime.

See merge request !287

content/FAQ/_index.md

@@ -15,6 +15,7 @@ weight = "95"
 - [I want to talk to a human about my problem. Can I do that?](#i-want-to-talk-to-a-human-about-my-problem-can-i-do-that)
 - [My submitted job takes long time waiting in the queue or it is not running?](#my-submitted-job-takes-long-time-waiting-in-the-queue-or-it-is-not-running)
 - [What IP's do I use to allow connections to/from HCC resources?](#what-ip-s-do-i-use-to-allow-connections-to-from-hcc-resources)
+- [Why is my job is showing (ReqNodeNotAvail, Reserved for maintenance) before a downtime?](#why-is-my-job-is-showing-reqnodenotavail-reserved-for-maintenance-before-a-downtime)
 
 ---
 
@@ -191,3 +192,13 @@ if your local network blocks outgoing connections. To allow HCC IP's, add the fo
 
 If you are unsure on how to do this, contact your local IT support staff for assistance.
 For additional questions or issues with this, please [Contact Us](https://hcc.unl.edu/contact-us).
+
+#### Why is my job is showing (ReqNodeNotAvail, Reserved for maintenance) before a downtime?
+Jobs submitted before a downtime may pend and show _(ReqNodeNotAvail, Reserved for maintenance)_ for their status.
+(Information on upcoming downtimes can be found at [status.hcc.unl.edu](https://status.hcc.unl.edu/).)
+Any job which cannot finish before a downtime is scheduled to begin will pend and show this message.  For example,
+the downtime starts in 6 days but the script is requesting (via the `--time` option) 7 days of runtime.
+If you are sure your job can finish in time, you can lower the requested time to be less than the interval before
+the downtime begins (for example, 4 days if the downtime starts in 6 days). Use this with care however to ensure your
+job isn't prematurely terminated. Alternatively, you can simply wait until the downtime is completed. Jobs will
+automatically resume normally afterwards; no special action is required.