Due to the holidays and now the beginning of the semester I didn't get to do proper testing of 2.4.1 before it was pushed, and, well, oops: Amanda Backup Client Hosts Check -------------------------------- ERROR: host1: [unknown option "|auth=bsd"] [...] ERROR: host2: [unknown option "|auth=bsd"] Client check: 18 hosts checked in 2.209 seconds. 11 problems found. We don't pass --with-bsd-security to configure when building amanda, and that's now mandatory if you want "auth bsd" to work (which is needed for dealing with really old clients, like rhel5). If I can squeeze in some time today I'll just update the configure call and push an update, but I wanted to get a ticket filed now in any case.
OK, maybe that wasn't the problem. Turns out it's the clients (RHEL5, ugh) which are rejecting what the server sends them. Switching to other auth types doesn't appear to help. So I'm beginning to think that you simply can't back up an amanda 2.5 client with a 3.4 server, which is an unfortunate thing to push as an update. The problem is that the OPTIONS line sent by the server has changed from: DUMP /local/samba2 0 OPTIONS |;auth=bsd;compress-fast;index; to DUMP /local/samba 0 OPTIONS |auth=bsd;compress-fast;index; So I guess I'll get to digging into that. I've updated the ticket subject to reflect what's really happening.
I cooked up a very small patch to ensure that there's always a semicolon at the top of the OPTIONS list, which at least gets past amcheck. I went ahead and pushed to rawhide (so you could at least see it directly) but didn't build, just in case. I also switched to %autosetup because I find it easier to stack patches that way. (Just add -S git and fedpkg prep will give you a tree with commits for each patch.) I sent that patch off to amanda-users. I've never been sure if I should use the users or the hackers list for a patch to a released version. In any case, feel free to revert if that's problematic for you. I will make sure everything is OK for tonight's backup run and if it's OK and I get some feedback on the patch then I'll go ahead and build, merge back to F24 and issue updates.
Upstream was OK with the patch, but unfortunately there was an additional incompatibility. Upstream suggested an additional fix, which I applied to rawhide. Will see again with tonight's run.
Hi Jason, sorry for my late reaction, but I had to solve some other things. From comment #2: Thanks for that. I am ok with this changes. For next time is better to send the patch to amanda-hackers (its list for developers), but as you see, they will respond you as well on amanda-users. From comment #3: Ok, so please apply your patch with suggestion from upstream and build amanda for rawhide. When its done, please post there link to koji build. Thanks a lot for your help with this package.
So with the revised patch applied, I was able to get two successful backup runs for my very old Amanda clients. Unfortunately 3.4.1 is causing new selinux failures on my other hosts, even those that don't use xfsdump. So I can add some more AVCs to the pile but I have no reasonable belief that the selinux policy maintainers will ever actually fix any of them. And in any case, that's something for a separate ticket. The rawhide build is https://koji.fedoraproject.org/koji/taskinfo?taskID=17314022 I am happy to create updates for the release branches if you like.
Can somebody create updates for Fedora 25, I have this problem also.
Sure, give me a second.
amanda-3.4.1-3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-fc448307c1
amanda-3.4.1-3.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-49ee10ce2c
amanda-3.4.1-3.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-49ee10ce2c
amanda-3.4.1-3.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-fc448307c1
amanda-3.4.2-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-ec1e93b61f
amanda-3.4.2-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-5fcf946acc
amanda-3.4.2-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-5fcf946acc
amanda-3.4.2-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-ec1e93b61f
amanda-3.4.2-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
amanda-3.4.2-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.