Backups not committed to git if one fails

[travisjohnsonga]

Hello -

When I run a config backup job, it one device has an error, none of the configs are committed to the git database.

Is there a setting or option to backup regardless?

[itdependsnetworks]

Can you confirm you are on 2.0? If so, it should not be this way and we need to fix it.

[travisjohnsonga]

I upgraded the plugin to 2.0 - now for some reason, the secrets aren't working.

I've got 2 secrets, which were previously used (username and token) but the group is gone, and when I try to create another secret group, the secrets aren't listed for use.

[itdependsnetworks]

it needs to be http(s) and token, but not sure what you are saying is happening. Can you re-produce on https://next.demo.nautobot.com/?

[travisjohnsonga]

The UI is 2.0 now,Does the plugin need upgrade to a 2.0 versionTravis Johnson404-234-2434On Oct 12, 2023, at 5:17 PM, Ken Celenza ***@***.***> wrote: Can you confirm you are on 2.0? If so, it should not be this way and we need to fix it. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[travisjohnsonga]

When I try to create the secret group, the box to select the secret, doesn’t list any of the secrets I’ve created.

…

On Fri, Oct 13, 2023 at 9:33 PM Ken Celenza ***@***.***> wrote: it needs to be http(s) and token, but not sure what you are saying is happening. Can you re-produce on https://next.demo.nautobot.com/? — Reply to this email directly, view it on GitHub <#657 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ4D7ZP4QCTW76BDP7TWVBDX7H2ZBAVCNFSM6AAAAAA56HFGYCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TENZYGQ2TI> . You are receiving this because you authored the thread.Message ID: <nautobot/nautobot-plugin-golden-config/repo-discussions/657/comments/7278454 @github.com>

[itdependsnetworks]

I am not able to re-produce that.

[travisjohnsonga]

Interesting, it happened after I upgraded the plugin for golden config. Any particular logs to check?

…

On Fri, Oct 13, 2023 at 9:40 PM Ken Celenza ***@***.***> wrote: I am not able to re-produce that. [image: image] <https://user-images.githubusercontent.com/9260483/275114522-bbd847e9-7e32-455d-8830-a918a8288704.png> — Reply to this email directly, view it on GitHub <#657 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ4D7ZIQ3T7IUIPXZPPQFBDX7H3TLAVCNFSM6AAAAAA56HFGYCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TENZYGQ3TO> . You are receiving this because you authored the thread.Message ID: <nautobot/nautobot-plugin-golden-config/repo-discussions/657/comments/7278477 @github.com>

[travisjohnsonga]

As a test - I created a dev database, ran migrations etc, logged into the UI and same issue.

There must have been something in the upgrade from 1.6.4 to 2.0.1 that didn't go right.

[itdependsnetworks]

I am not saying there isn’t an issue, I am saying I cannot reproduce it, as I shown with the screenshot.

I am asking what exact steps, since I followed your general steps and have a different end state. So there is a difference in the steps or setup now we are looking to find out what that is.

[itdependsnetworks]

Just to confirm, are you saying it never works in golden config (meaning you add the secrets and secrets groups) or just that it disappears when you migrate? If it just disappears, can you get it to work again?

• If you cannot, would need to know the steps since either of us can go right now and see it working on next.nautobot.com
• If you can get it working, the migration of secrets groups would go to core, and a bug opened there.

[travisjohnsonga]

I understand.

So, this is going to probably sound crazy; however, it's happening.

If I run the server with nautobot-server runserver 0.0.0.0:8000 --insecure I can edit secret groups fine.

Running it with uwsgi - it won't list the secrets in the drop down. Thoughts?

[travisjohnsonga]

I found that it only 'disappears' when running as a service. If I stop service and run again with nautobot-server runserver, functionality is normal again. Restart service, secrets are gone from the secrets group creation page.

I ran ps -aux | grep nautobot and it appears they are all running in the right user, which would expect to be the right venv. Ubuntu 22.04 nginx and postgres.

[travisjohnsonga]

Additionally, when I run in test mode, I can use the 'check secret' button and succeed. When run via uwsgi, the check secret fails.

My systemd files and uwsgi.ini are from the nautobot install guide.

https://blog.networktocode.com/post/installing-nautobot/

[travisjohnsonga]

Moved this to core - https://github.com/orgs/nautobot/discussions/4654

[itdependsnetworks]

Note for myself, we should move the git work to the after_return method.

[travisjohnsonga]

So a final update for this - thanks to help from the slack channel

I created the service override files and added envars to nautobot.service, and it still failed to get the secrets.
I had to additionally add them to the nautobot-worker.service daemon file, now all is good.

[itdependsnetworks]

good to hear! I still think that there is an issue with if it fails on one device it doesn't push to git, correct?

[travisjohnsonga]

I think something like that.....

When I run for all my devices now I get the following. Pretty sure it's because I'm missing a primary IP on them (environment cleanup needed - automating custom discovery thing to try and get the actual interfaces.....long story)

Perhaps if the job schedule/run included a filter for 'has_primary_ip'? Or if the default was to only run on devices with primary ip?

{'exc_type': 'NornirNautobotException', 'exc_module': 'nornir_nautobot.exceptions', 'exc_message': ['E3001: General Exception handler, original error message ```AggregatedResult (BACKUP CONFIG): a bunch of hostnames redacted