Issue with New Stamp Deployments on Azure

[amoswachanga]

Stamp deployment for production starts okay but then generates the following email notification issue.

Email notification header : Cron root@ServerNamevmss000000 [ ( ! -f /etc/opt/omi/creds/omi.keytab ) -o ( /etc/krb5.keytab -nt /etc/opt/omi/creds/omi.keytab ) ] && /opt/omi/bin/support/ktstrip /etc/krb5.keytab /etc/opt/omi/creds/omi.keytab

Email notification content:
src kt = /etc/krb5.keytab
File /etc/krb5.keytab does not exist
/opt/omi/bin/support/ktstrip: 38: exit: Illegal number: -1

It also starts provisioning all the servers but it seems the deployment never completes successfully

Some of the related issues I've found include: #335 and #362 and #333

[amoswachanga]

@eltoncarr Just to confirm, is this repo going to be maintained anymore now that @microsoft will be retiring the LaaS?

[RepoCloudSwyft]

Hi @amoswachanga

We have same error issue, regarding on the Stamp deployment for production starts okay but then generates the following email notification issue.

Same email notif: Cron root@csgclientvmss000000 [ ( ! -f /etc/opt/omi/creds/omi.keytab ) -o ( /etc/krb5.keytab -nt /etc/opt/omi/creds/omi.keytab ) ] && /opt/omi/bin/support/ktstrip /etc/krb5.keytab /etc/opt/omi/creds/omi.keytab

Did you get to fix this? Can we ask for help. Thanks

[amoswachanga]

Hi @RepoCloudSwyft ,

Unfortunately we haven't resolved this yet.

We consulted with the Azure Support team and they advised we check if this omi package is being installed correctly. Since the same scripts had worked previous, we suspect it has to do with the Ubuntu image or deprecated packages that don't get installed.

Because of the urgency we had, we are going for alternative setup ways but we are still interested in getting a grip of the underlying issue for the long term.

[RepoCloudSwyft]

Hi @amoswachanga,

Thank you for you response.

As of now we still working on this, as we also need this item to get deployed immediately.
We also thinking maybe that's why we have this issue is because of the msft security default implemented by msft last Feb 29. We are not getting email from smtp.office365.com we are using gmail server.

What alternative set up are you using? The manual set up of Native Ficus?

Hope we can get this resolve. Thanks

[amoswachanga]

Hi @RepoCloudSwyft,

Sorry I didn't get back to you sooner. We are using gmail as our smtp server but our emails are on Microsoft Exchange and those seem to work fine, since we are getting the notifications.

There are new issues with setting up Ficus in general based on this repo and even with the Edx's main repos because of deprecated packages like Python 2.7, MongoDB installation servers and the like. If we resolve the deployment issues we will do a pull request with the updates.

We've noted there are some updates on other branches on this repo which didn't seem to be concluded such as this one https://github.com/microsoft/oxa-tools/tree/oxa/dev.haw. You might get some insights into potential issues from there.

Let us know if you got any headway.

Thanks