Comments (14)
@wzymaster, did you may any customizations? Also, I noticed that you are referencing the comprehensive/lms/template. Is this a custom theme you created? It may not be applicable to your scenario.
from oxa-tools.
from oxa-tools.
To help narrow down the possible causes:
- Are you using onebox.sh ?
- If so, what parameters did you invoke onebox.sh with?
- Which branch of oxa-tools did you use,
from oxa-tools.
- Yes, I am using onebox.sh to deploy this stack
- command is
./onebox.sh -d hokiePokiePass11
to deploy - I always use master branch
from oxa-tools.
actually, I identified that this issue is caused by % if course.display_org_with_default in my_course_org_filter:
in edx/app/edxapp/themes/comprehensive/lms/templates/courseware/course_about.html
file.
After I commented out this line, I get error like :
Unauthorized access. Error Code: 1001
from oxa-tools.
@sdolenc can you provide me instructions on how to deploy STAMP stack on ubuntu 16 ? The attached doc. is only related to deployment on windows using Power Shell.
I deployed my stack using ./onebox.sh -d hokiePokiePass11
on a clean ubuntu 16 box on Azure.
Please advise and your help is highly appreciated !
from oxa-tools.
to clarify:
- STAMP deployment is a high availability "production-like" environment. Both Mongo and MySql databases are replicated across multiple VMs. The "frontend" machines running the web application are part of a Virtual Machine Scale Set (VMSS) which is designed to scale to multiple machines based on system load. The instructions for deploying a STAMP currently assume you are using a Windows machine.
- The onebox deployments are for experimentation and is more brittle. It deploys an edx instance that is similar to STAMP functionally, but everything is running on "one box." The databases, django web services, etc are all running on the same machine and sharing the same system resources.
I believe I identified the root cause of the bug you're encountering. There are two longterm solutions we're considering (we could even take both or go an entirely different route):
- A solution is to make our onebox deployment resemble the functionality of our STAMP deployment even closer. The STAMP deployment includes combined login/registration without custom theming automatically (edx-theme is where this bug is happening). I submitted PR #277 to make the onebox deployment follow that pattern
- It looks there are fixes that were made in stabilization branch (oxa/release.fic) that haven't yet been merged to our development branch (oxa/dev.fic). I submitted a pull requests microsoft/edx-theme#155 which should hopefully solve this.
In the meantime: you can try either (or both) proposed solutions on a new/clean machine by
- using "noTheming" branch in oxa-tools before deploying onebox.sh . This will include the fix proposed in #277
- add -b release to your onebox.sh parameter list. This will ensure you're using oxa/release.fic branches. This means you'll have all the fixes contained in microsoft/edx-theme#155
I hope this helps!
from oxa-tools.
we've merged microsoft/edx-theme#155 . I believe the issue should be resolved, but feel free to reopen if you're still encountering it
from oxa-tools.
@sdolenc thanks very much and I will give it a try. Before I proceed with new release, I encountered a new issue while doing certificate verification(callback from Microsoft), after disable microsoft theme :
Is it related to the bug that you just merged ?
from oxa-tools.
(reopening issue so we can get to the bottom of this)
Strange. I have two theories for what might be going on. Can you send me information about the edx-platform version you're using?
- navigate to the following directory
/edx/app/edxapp/edx-platform
sudo -H -u edxapp bash
git fetch
- can you send the results of the following commands?
git status
(branch, number of commits behind, edited files, etc)- if the status doesn't return branch then try
git branch
if that doesn't work then get the full list of branches that contain the current commit withgit branch --remote --contains
git log -2
(hashes of current and previous commit)
from oxa-tools.
@sdolenc here is output from commands :
edxapp@edx:~/edx-platform$ git status
On branch oxa/dev.fic
Your branch is behind 'origin/oxa/dev.fic' by 6 commits, and can be fast-forwarded.
(use "git pull" to update your local branch)
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)
modified: lms/djangoapps/student_account/views.py
modified: lms/envs/common.py
no changes added to commit (use "git add" and/or "git commit -a")
edxapp@edx:~/edx-platform$ git branch
* oxa/dev.fic
edxapp@edx:~/edx-platform$ git branch --remote --contains
origin/HEAD -> origin/oxa/dev.fic
origin/ananth/bugfix-90913
origin/ananthu/bug-404-fix
origin/ananthu/bugfix-103970
origin/ananthu/bugfix-404-issue
origin/ananthu/bugfix404-final
origin/d2r
origin/disableCMSPII
origin/oxa/bug-httponly
origin/oxa/dev.fic
origin/oxa/master.fic
origin/oxa/release.fic
origin/removePII2rel
origin/removePIIstudent
origin/restreicted_perm
edxapp@edx:~/edx-platform$ git log -2
commit 1b7b5caf4a6712fe5397868e21ed5a22dd73408a
Author: Kabir Khan <[email protected]>
Date: Fri Dec 22 15:48:13 2017 -0800
Fixing build timeouts with travis_wait (#182)
* Fixing build timeouts with travis_wait
* Build on travis
* Fixing newly failing localization test
commit b65bdea6bef8fbec875eb31434d2052e794128b0
Author: Kabir Khan <[email protected]>
Date: Fri Dec 15 14:00:29 2017 -0800
OAuth Restricted Application APIs (#174)
* Restricted application statistics3 (#173)
* update code coverage settings
* fixing code cov target
* initial grades api implementation
* adding v1 urls to lms
* Added CourseAccess exception
* adding self
* Added initial pagination functionality
* Initial functionality for pagination of bulk grades
* Initial functionality for pagination of bulk grades
* Fixing formatting
* Fixing formatting
* deleted to get old formatting back hopefully
* adding back views
* Fixing pagination
* Improvements to bulk grades api
* Refactored and added organization filtering
* Adding tests
* Adding more tests
* removing extra indent
* Patching view read/create function
* Restricted oauth changes
* Test fixes
* Build on travis
* Patch tests with setting to auto expire access tokens
* fixing tests and quality errors
* Fixed grades test
* Fixes quality error
* Adding grades api improvements
* Improvements to restricted oauth setup of grades api v1
* Fixing tests, bulk grades admin needs staff access not superuser
* Removing BULK_GRADES_ADMIN setting
* Fixing enrollment org_filter tests
* 1. Added allowedusers filter to the restricted application model.
2. Get course grades if all user who are enrolled in a course.
3. New scope "statistics" to pull grades informationof all users enrolled in a course with elevated permission.
4. Added permission check to valdiate allowed users, ONLY if applicable.
* adding the missing files
* Fixing security issues and cleaning up unreached code paths
* Fixing user function
* Fixing testing strategy
* Fixing grades test setup
* Fixing test error
(cherry picked from commit e6005553ea27e24be6d64c0f88af4294909c8e93)
* Updating to trigger build
* Updating to trigger build
* Remove unused travis matrix, fix coverage running on test files, fix unit tests.
* Actually removing unused test matrix
* Test fixes, removing unused code. ++codecov
* Fixing quality error
from oxa-tools.
A couple things
- Your deployment is pretty old (from December). That wouldn't normally be a problem, but I believe you're encountering this bug because there was some experimental code in
oxa/dev.fic
back then. We've since moved that work intooxa/dev.fic_msa
of theedx-platform
repo as we stabilize those changes. - I'm going to try to get the the onebox defaults to align with the code/settings that are deployed as part of STAMP for external partners. This would be a more stable and supported set of configurations. This work would need to be scheduled against our other priorities so I'm not sure when it'll land. In the meantime, I recommend
- deploying STAMP instead. There are instructions on the readme
- deploying with onebox on a "fresh" machine (one where you haven't deployed edx yet) with the following settings: a) checkout
noTheming
branch of theoxa-tools
repo and b) using--branches master
I'm closing this one since I believe those workaround will unblock you. Please open new issue(s) for any future problems.
In any event, I apologize for all the difficulty you've encountered. Thank you for identifying these issues. It helps us build a more stable workflow.
from oxa-tools.
@sdolenc I just wants to set up a Microsoft Edx so that I am able to acquire certificate from the authorized courses. Can I bypass STAMP configuration ?
I am a bit confused with "a) checkout noTheming branch and b) using --branches master". If I understand it correctly, you mean to use noTheming
branch in Git and run onebox.sh
with --branches master
parameters ?
Are you able to provide me with the full commands to deploy this onto a fresh
machine ?
from oxa-tools.
We recommend you deploy a STAMP, but if you need to deploy a single-machine instance for some reason then the onebox script will probably work. The additional instructions I provided will allow onebox to align closer with the settings in STAMP. Here are the specific instructions
- new machine (no attempted edx installation yet)
git clone -b noTheming https://github.com/Microsoft/oxa-tools
pushd oxa-tools
- (you could do a
git checkout noTheming
if you didn't do the -b param in step 2) script log.txt
(to record the output of the installation)sudo bash onebox.sh --branches master
(and other params depending on what you're trying to do)
I hope that clears things up
from oxa-tools.
Related Issues (20)
- Unable to access Frontend VM from jump box HOT 3
- Search results empty even though courses are present HOT 3
- General concerns regarding mooncake version HOT 1
- Issue with Installing ecommerce after oxa-tools HOT 3
- VMSS scaleset HOT 2
- Attach another vmss to a live cluster (Green/Blue deployment) HOT 1
- EdX Database (Mysql) Setup Failed HOT 8
- SMTP settings just does not work Office 365 HOT 11
- how to setup backup or disaster recover plan HOT 1
- VM has reported a failure when processing extension 'installoxa' HOT 4
- Question about ClusterAdministratorEmailAddress HOT 1
- On 23-05-2019, Deployment was failed with "Execution of edX MySQL migrations failed" message HOT 20
- bvt.sh not available HOT 1
- Unable to integrate Azure AD SSO HOT 22
- edx sandbox playbook failed HOT 15
- SSH public key can't be used at jumpbox and failed during installation HOT 3
- Install new module and new migration HOT 1
- OXA Bootstrap email notification missing HOT 15
- Issue with New Stamp Deployments on Azure HOT 5
- This repo is missing important files HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from oxa-tools.