Problem with nfs deploy on job job-st2-register-content #238
Labels
Milestone
Comments
|
|
|
I'm happy to look into this, but I have some work projects I need to deal with right now. I'll check this issue out this weekend. |
|
Ir only happens when i use shared Volumes, pv or nfs. |
|
Would you post your values for st2.packs.images and st2.packs.volumes?
…On Sat, Sep 4, 2021, 06:34 elsopapa ***@***.***> wrote:
Ir only happens when i use shared Volumes, pv or nfs.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#238 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAL4QPRC3X7Y42K4QHF5ZITUAH74TANCNFSM5DLVHRKQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Default image from the repo (now im triyng |
|
I just edited your comments to make them easier to review. Now to see if I can tease something out of these logs... |
|
Are all the other pods running? Eg Please try this:
Are the volumes mounted correctly so that they have read/write access for many pods? |
|
The Volumes aré mounted (pv or nfs), i can write AnD read from the pods (ive uploaded the logs ) . All pods aré running ok, (it only fáils when it run the registry job ). |
|
Can you find the logs for the first instance of the failed register job? It tries 6 times. Maybe the first instance will have a more helpful error message |
|
the error is cannot initializating |
|
the helm only write the packs on the nfs server , the config and the virtualenv keeps empty |
|
the syslog filter by register job |
|
job |
|
Does this return anything? |
|
No resources found in st2 namespace. |
|
What about? |
|
same |
|
it only fails when i use a shared volumes, the register job works fine on a default install. |
|
Oh. I didn't specify the namespace. If adding To do that, run I think the |
|
the log , |
|
Was that with NFS or the PVC? What is the definition for your |
|
The definition |
|
Name: nfs-client |
|
Since NFS is changing the ownership on the fly (the That suggests that we need something a little more robust for copying pack contents. Do you have any recommendations for how to modify these lines so that they preserve ownership and permissions when possible without failing when the underlying filesystem doesn't support them? https://github.com/StackStorm/stackstorm-ha/blob/21108182a1475f8ef8c87e3a3e2cbe1fb79ce579/templates/_helpers.tpl#L204-L205 |
|
Looking at your logs, we only have two errors we need to work around: preserving ownership and timestamps. Other filesystems might have additional restrictions (such as changing permissions). |
|
For now, maybe you could try changing your NFS export options. There have been several attempts to add persistent volumes to the chart. In one of those tries, based on NFS, the README suggested exports like: @elsopapa Can you change your NFS export options? Or do you have to use |
cognifloyd
added
bug
|
I Will change the options of nfs export and give a try.
El mar., 7 de septiembre de 2021 19:39, Jacob Floyd <
***@***.***> escribió:
… For now, maybe you could try changing your NFS export options. There have
been several attempts to add persistent volumes to the chart. In one of
those tries, based on NFS, the README suggested exports like:
https://github.com/StackStorm/stackstorm-ha/blob/ef206060fe045ce5f8e5910e39a9287fcaa4a7b4/README.md#L218-L220
@elsopapa <https://github.com/elsopapa> Can you change your NFS export
options? Or do you have to use root_squash?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#238 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACK7TXKKJU7MCH5QW4EKWNDUA2IDXANCNFSM5DLVHRKQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
@cognifloyd we can definitely include |
|
If we add |
|
The problem was the options in the export file . Ive changed to no_root_squash and everything is working now. Thank you for your patience and support!!!! |
|
This is not an issue. thanks again |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a problem deploying with helm when using nfs , the job fail with "Job has reached the specified backoff limit"
File in nfs
The text was updated successfully, but these errors were encountered: