IvanLabrovic
Flight Engineer
Flight Engineer
  • 392 Views

lab grade backup-review (DO380 course version 4.14)

Jump to solution

Hi,

I am running DO380 in version 4.14 and struggling with the results of the grade script on the lab "Lab: Backup, Restore, and Migration of Applications with OADP"
The gradescript is saying: "Mediawiki is not in read only."
All other checks have OK/Passed

I am confused, should wiki in the restored namespace be readonly? I explicitly added the removal of the lockfile in de restore spec, so i cant understand why the grade script wants to check if it is in readonly.
And that i also what the solution of createing the backup spec says.

Does anyone have some insight what i could be missing here?

1 Solution

Accepted Solutions
Chetan_Tiwary_
Moderator
Moderator
  • 269 Views

@IvanLabrovic I checked this in the lab 

Chetan_Tiwary__0-1715695897747.png

Also I see this info in the lab's problem statement :

Chetan_Tiwary__1-1715695994292.png

I checked this with our course  architect and I quote : "The reason for the wiki to be read-only is so that a safe backup that includes all data can be performed. Once restored, the wiki instance should still be read only, since the source of the backup included that lock file. The script checks for the presence of the lock to ensure this is in place.

Perhaps in a real world scenario, removing the lock file on the restored instance would make sense, but the exercise does not ask for that to occur, so checking for the lock file and read only status is still appropriate."

However, we have taken a note of this and will ensure to add an additional step to remove the lock on the restored instance, so that it is more realistic and the wiki is now functional as a production instance a user can add content to. But this will be there in an upcoming release / version update of the course. 

Thanks for your time and reporting this here!

View solution in original post

2 Replies
Chetan_Tiwary_
Moderator
Moderator
  • 311 Views

@IvanLabrovic I will check it and let you know once I have an update. 

Chetan_Tiwary_
Moderator
Moderator
  • 270 Views

@IvanLabrovic I checked this in the lab 

Chetan_Tiwary__0-1715695897747.png

Also I see this info in the lab's problem statement :

Chetan_Tiwary__1-1715695994292.png

I checked this with our course  architect and I quote : "The reason for the wiki to be read-only is so that a safe backup that includes all data can be performed. Once restored, the wiki instance should still be read only, since the source of the backup included that lock file. The script checks for the presence of the lock to ensure this is in place.

Perhaps in a real world scenario, removing the lock file on the restored instance would make sense, but the exercise does not ask for that to occur, so checking for the lock file and read only status is still appropriate."

However, we have taken a note of this and will ensure to add an additional step to remove the lock on the restored instance, so that it is more realistic and the wiki is now functional as a production instance a user can add content to. But this will be there in an upcoming release / version update of the course. 

Thanks for your time and reporting this here!

Join the discussion
You must log in to join this conversation.