This MR updates the CI so that we can publish Alma9 rpms in the public stable/testing repositories described at https://gitlab.cern.ch/cta/operations/-/issues/1296#note_7754822 .
The testing
repository will allow the CTA community to test early versions of CTA at their own risk. The stable
repository will replace the old /cta-{4..5}
directory structures for Alma9 and later.
No
https://gitlab.cern.ch/cta/operations/-/issues/1296#note_7754822
You have updated documentation here: https://eoscta.docs.cern.ch/gitlab/alma9_runner/
This MR updates the CI so that we can publish Alma9 rpms in the public stable/testing repositories described at https://gitlab.cern.ch/cta/operations/-/issues/1296#note_7754822 .
The testing
repository will allow the CTA community to test early versions of CTA at their own risk. The stable
repository will replace the old /cta-{4..5}
directory structures for Alma9 and later.
No
https://gitlab.cern.ch/cta/operations/-/issues/1296#note_7754822
Maybe we should update this image to alma9
This MR updates the CI so that we can publish Alma9 rpms in the public stable/testing repositories described at https://gitlab.cern.ch/cta/operations/-/issues/1296#note_7754822 .
The testing
repository will allow the CTA community to test early versions of CTA at their own risk. The stable
repository will replace the old /cta-{4..5}
directory structures for Alma9 and later.
No
https://gitlab.cern.ch/cta/operations/-/issues/1296#note_7754822
Jorge Camarero Vera (551c5a1e) at 19 Mar 14:28
Jorge Camarero Vera (8a5aba08) at 19 Mar 14:28
Resolve "Check disk file metadata on delete requests"
In the case where a disk file has a wrong archive ID in its extended attributes, deletion of the disk file will delete the wrong archive file in CTA.
The deleted file could be the tape copy of a completely different file on a different VO.
The code below for deleting files should be amended to check that disk file metadata matches (instance name and disk file ID) and not rely on the archive file ID alone.
//------------------------------------------------------------------------------
// deleteArchive
//------------------------------------------------------------------------------
void Scheduler::deleteArchive(const std::string &instanceName, const common::dataStructures::DeleteArchiveRequest &request,
log::LogContext & lc) {
// We have different possible scenarios here. The file can be safe in the catalogue,
// fully queued, or partially queued.
// First, make sure the file is not queued anymore.
utils::Timer t;
log::TimingList tl;
if(request.address) {
//Check if address is provided, we can remove the request from the objectstore
m_db.cancelArchive(request,lc);
// no need to do anything else, if file was failed it will not be in the catalogue.
}
tl.insertAndReset("schedulerDbTime",t);
m_catalogue.ArchiveFile()->moveArchiveFileToRecycleLog(request,lc);
tl.insertAndReset("catalogueTime",t);
log::ScopedParamContainer spc(lc);
tl.addToLog(spc);
lc.log(log::INFO, "In Scheduler::deleteArchive(): success.");
}
Jorge Camarero Vera (551c5a1e) at 18 Mar 12:36
Provid ALERT logs for operators
Jorge Camarero Vera (a570c33a) at 18 Mar 09:45
Provid ALERT logs for operators
Jorge Camarero Vera (7c4b2343) at 15 Mar 09:29
Provid ALERT logs for operators
Jorge Camarero Vera (793796ef) at 15 Mar 09:06
Provid ALERT logs for operators
Jorge Camarero Vera (0f81b1e0) at 14 Mar 17:22
Reduct if complexity
Jorge Camarero Vera (0d97189c) at 14 Mar 16:33
Fix logs