agreed_to_es_terms and agreed_to_ws_terms aren't in the satellite schema while they are in the hosted schema.
this is fixed and should be in the future satellite builds
is there anything to test here?
Mass move to ON_QA for the QA push two days ago.
Additional Comment #2 From Todd Warner (taw) on 2005-01-10 00:52 ------- Private Comment is there anything to test here?
Not relevant to 3.6.5 - moving to 3.7.0
nothing to test here. these fields are unused in sat.
Test plan: 1) create a satellite 2) using sqlplus, do a: desc rhnUserInfo and make certain the fields are in the table.
SQL> desc rhnUserInfo; Name Null? Type ----------------------------------------- -------- ---------------------------- USER_ID NOT NULL NUMBER NO_CLEAR_SETS NOT NULL NUMBER PAGE_SIZE NOT NULL NUMBER EMAIL_NOTIFY NOT NULL NUMBER BAD_EMAIL NOT NULL NUMBER TZ_OFFSET NOT NULL NUMBER TIMEZONE_ID NUMBER SHOW_APPLIED_ERRATA NOT NULL CHAR(1) SHOW_SYSTEM_GROUP_LIST NOT NULL CHAR(1) AGREED_TO_TERMS NOT NULL CHAR(1) USE_PAM_AUTHENTICATION NOT NULL CHAR(1) LAST_LOGGED_IN DATE AGREED_TO_WS_TERMS CHAR(1) AGREED_TO_ES_TERMS CHAR(1) CREATED NOT NULL DATE MODIFIED NOT NULL DATE
mass move: PROD_READY --> CLOSED:CURRENTRELEASE