Build fails searching for docs/requirements.txt

[rb2745]

Details

• Project URL: http://onap.readthedocs.io
• Build URL (if applicable): https://readthedocs.org/projects/onap/builds/6069511/
• Read the Docs username (if applicable):

Expected Result

Build succeeds using etc/requirements.txt (file in repo) and as specified in advanced settings

A description of what you wanted to happen Build to succeed using the requirements in etc/requirements.txt as it has until today. -or- A confirmation that there has been a change that requirements must always be in the docs folder.

Actual Result

Build fails with message - Could not open requirements file: [Errno 2] No such file or directory: 'docs/requirements.txt'

Wiping the build environment and resubmitting the advanced settings with etc/requirements specified does not fix the problem.

[safwanrahman]

I can successfully build your project locally with etc/requirements.txt in requirements. Maybe something is missing in production

[rb2745]

I duplicated the requirements.txt file in the docs folder to continue.

This worked until today 11/14/17 about 6am EST, now all builds are failing with an error message:

_Error Problem parsing YAML configuration. Invalid "requirementsfile": path docs/requirements.txt does not exist

[agjohnson]

Closing this as a duplicate. We put a hotfix out today and a proper fix coming shortly.

[Benjamin-Lee]

This is happening to me; I am having the same problem, especially since there is a docs/requirements.txt file in the repo.

[davtoh]

hi, same issue over here. I already tried relative paths of all sort and even the direct link to the requirements.txt file on the root of the project.

case: https://readthedocs.org/projects/intelligent-tracker/builds/7495674/ project: https://github.com/davtoh/intelligent-tracker

[stsewd]

@davtoh please see #4378 for more details

[rb2745]

The problem reported at the top of this thread was caused by an algorithm at read the docs that searched throughout a repository looking for a configuration yaml file, finding one or more files that were not related to a configuration and trying to use them as configuration. The problem was resolved by providing a configuration yaml file in the root of repository. For example: https://gerrit.onap.org/r/gitweb?p=doc.git;a=blob;f=readthedocs.yml;h=6e6b9af07e6d523a60342e76bf181288bf826c63;hb=HEAD

[davtoh]

ok, updating the repo with the yaml file prevents it from having this error. Maybe it could be useful to inform the user about the used yaml file and suggest to use readthedocs.yml in case of conflict?

[stsewd]

@davtoh the problem is a bug, users don't need to have a readthedocs.yml file, but I think is the recommended way of using rtd now.

[nomeata]

Had to do

$ cat readthedocs.yml 
requirements_file: null

to fix this problem.