Opened 4 years ago

Closed 4 years ago

#2017 closed help (fixed)

housekeeping error

Reported by: amenon Owned by: annette
Component: Rose Keywords: Nesting suite, housekeeping, fetchone, ROSE_VERSION
Cc: Platform: ARCHER
UM Version: 10.4



In my nested suite, housekeeping is failing with the following message

[FAIL] 'list' object has no attribute 'fetchone'

The path to the error file is


Could you please help to sort this out?


Change History (6)

comment:1 Changed 4 years ago by grenville


We are working on this.


comment:2 Changed 4 years ago by annette

Hi Arathy,

I am wondering whether Rose has got confused under the hood.

Can you try submitting a clean run please? Run as:

rose suite-run --new

Let me know whether this works.


comment:3 Changed 4 years ago by annette

  • Owner changed from um_support to annette
  • Status changed from new to assigned

comment:4 Changed 4 years ago by annette


I think the issue may be that the version of Rose in your environment has changed, causing an incompatibility. Normally suites should keep the version of Rose fixed (regardless of your environment) by setting something like the following in the suite.rc:

       init-script = "export ROSE_VERSION={{ROSE_VERSION}}"

You have this in your suite, but the init-script setting is being overwritten in site/ncas-cray-xc30/suite-adds.rc in various places. Each of these should probably have the ROSE_VERSION line added.


comment:5 Changed 4 years ago by amenon

Thanks Annette. I couldn't submit a clean run yesterday as I had some problems in accessing Puma. I will add Rose_version to those lines in suite-adds.rc file. But do I need to start a clean run after that or can I re-load the suite?

comment:6 Changed 4 years ago by annette

  • Component changed from UM Model to Rose
  • Keywords fetchone, ROSE_VERSION added; fetchone removed
  • Resolution set to fixed
  • Status changed from assigned to closed


To resolve, ROSE_VERSION was correctly set in the suite. On the advice of Stuart Webster this was added to pre-script but did have to be set in various places. Stuart will address this in the next version of the nesting suite. A new run did have to be submitted. Also Arathy had different version of rose/cylc set in her .profile on PUMA and ARCHER which may have contributed to the problem.

Response from Arathy:

The house keeping succeeded now for the first cycle. It took a long time because of the Archer serial queue issue. Thanks a lot for helping to sort this out.

Note: See TracTickets for help on using tickets.