Description of problem: Channel Administrator gets error when trying to create a new config channel. Steps to Reproduce: 1. Create a new corporate account / grant entitlements 2. Create a new user and give new user Channel Admin role 3. Login as new user and try to create a config channel Actual results: Error page. Expected results: I'm assuming this should work or that the user shouldn't see the 'create new config channel' link in the first place. Also, even though the user gets an error page, the config channel is created. The new user can't see it though if they browse back to the page. Additional info: I have already created a few users to reproduce this one since we thought it may have been caused by the java code at first. Org Admin: ssprockets2/dog8code Channel Admin: gjetson002/dog8code
Whenever you generate an unexpected 500 page, be sure to include w/ the bug the traceback that was generated. In this case, I believe its: Form variables: ccid => 4468 User Information: User mbowman17 (id 3916069, org_id 4313995) Error notes: (none) Initial Request: Yes Error message: RHN::Exception: DBD::Oracle::st execute failed: ORA-01403: no data found ORA-06512: at "RHN.RHN_CONFIG_CHANNEL", line 69 ORA-06512: at line 2 (DBD NO_DATA: OCIStmtExecute) [for Statement "BEGIN :ret := rhn_config_channel.get_user_chan_access(:p1, :p2); END;" with ParamValues: :ret=undef, :p1='4468', :p2='3916069'] RHN::DB /var/cvs/rhn/web/modules/rhn/RHN/DB.pm 219 RHN::Exception::DB::throw RHN::DB::db /var/cvs/rhn/web/modules/rhn/RHN/DB.pm 475 RHN::DB::handle_error RHN::DB::User /var/cvs/rhn/web/modules/rhn/RHN/DB/User.pm 1338 RHN::DB::db::call_function RHN::DB::User /var/cvs/rhn/web/modules/rhn/RHN/DB/User.pm 1773 RHN::DB::User::verify_permission_function_helper RHN::Cleansers /var/www/lib/RHN/Cleansers.pm 171 RHN::DB::User::verify_config_channel_access RHN::Cleansers /var/www/lib/RHN/Cleansers.pm 140 RHN::Cleansers::check_param PXT::Request /var/cvs/rhn/web/modules/pxt/PXT/Request.pm 233 RHN::Cleansers::cleanse PXT::ApacheHandler /var/cvs/rhn/web/modules/pxt/PXT/ApacheHandler.pm 439 PXT::Request::cleanse_params PXT::ApacheHandler /var/cvs/rhn/web/modules/pxt/PXT/ApacheHandler.pm 439 (eval) PXT::ApacheAuth /var/cvs/rhn/web/modules/pxt/PXT/ApacheAuth.pm 23 PXT::ApacheHandler::initialize_pxt main /dev/null 0 PXT::ApacheAuth::handler main /dev/null 0 (eval)
You must have the config_admin acl to create config channels correctly, however links to create config channels show up to everybody. Also, anybody is allowed to delete config channels... this seems wrong to me, but it could be that I just don't know everything about how these work yet...
Added acl to toolbar to only show create/delete links if a config admin.
Please provide a test plan. Thanks!
This bug got rolled into the changes bretm and I made to the config channel ui (146886). Originally, this bug was filed because when a normal user tried to create a config channel, the ui allowed him to, but the db threw exceptions since the user didn't have the proper permissions. This is now not an issue since there is no way for a normal user to try and create a config channel. I suppose a test plan would be to log in as a normal user (not an org or config admin) and go to the channels tab. You should *not* see a "manage config channels" link in the left-hand navigation. You should not be able to get to a form that allows you to create a config channel.
PROD_READY 1. Logging in as a normal user with no admin rights, you see no links for manage config channels 2. Granting that user Config Admin rights and logging back in displays the config channel management links.
mass move: PROD_READY --> CLOSED:CURRENTRELEASE