Bugzilla problem

[Tony Molloy]

Hi,

I've installed the latest bugzilla from epel-5 on CentOS-5. It appears to be 
working OK from what testing I've done.

However I have 2 problems.

1.   When I run testserver.pl I get the following

[root@richmond bugzilla]# ./testserver.pl http://bugzilla.csis.ul.ie/bugzilla
TEST-OK Webserver is running under group id in $webservergroup.
TEST-OK Got front picture.
TEST-OK Webserver is executing CGIs via mod_cgi.
TEST-OK Webserver is preventing fetch of                              
<<<<< 
http://bugzilla.csis.ul.ie/bugzilla//etc/bugzilla/localconfig.
TEST-OK GD version 2.35, libgd version 2.0.33; Major versions match.
TEST-OK GD library generated a good PNG image.
TEST-OK Chart library generated a good PNG image.
TEST-OK Template::Plugin::GD is installed.

Why is the webserver preventing fetch of localconfig.

2.  On the top of the login page I see the following.

The local XML file '/var/lib/bugzilla/data/bugzilla-update.xml' cannot be 
created. Please make sure the web server can write in this directory and that 
you can access the web. If you are behind a proxy, set the proxy_url 
parameter correctly

The webserver runs as user apache and the protections on data are

drwxrwx---  root apache root:object_r:httpd_bugzilla_script_rw_t data

Is this just an apache mis-configuration

Regards,

Tony

[Thorsten Leemhuis]

Hi!

On 23.01.2008 15:38, Tony Molloy wrote:
>  I've installed the latest bugzilla from epel-5 on CentOS-5. It
> appears to be 
>  working OK from what testing I've done.
>  
>  However I have 2 problems.
>  
>  1.   When I run testserver.pl I get the following
>  [...]
>  2.  On the top of the login page I see the following.
>  [...]
>  Is this just an apache mis-configuration 
Seems nobody can't or doesn't want to (¹) reply. I'd suggest you ask on
bugzilla specific forums and mailing lists for help; I suppose chances
are bigger to find help there. In case there is a problem with the EPEL
packages please file them in bugzilla.redhat.com, then you'll reach the
maintainer of the bugzilla packages in EPEL.

CU
knurd (who never ever looked at the bugzilla package)

(¹) -- your post is not really on topic on this list; but also not
completely off topic and there is no epel-users-list, so it was IMHO
fine to post it here

[Tony Molloy]

On Friday 25 January 2008 15:58:31 Thorsten Leemhuis wrote:
>  Hi!
>
>  On 23.01.2008 15:38, Tony Molloy wrote:
>  > I've installed the latest bugzilla from epel-5 on CentOS-5. It appears to
>  > be working OK from what testing I've done.
>  >
>  > However I have 2 problems.
>  >
>  > 1.   When I run testserver.pl I get the following
>  > [...]
>  > 2.  On the top of the login page I see the following.
>  > [...]
>  > Is this just an apache mis-configuration
>
>  Seems nobody can't or doesn't want to (¹) reply. I'd suggest you ask on
>  bugzilla specific forums and mailing lists for help; I suppose chances
>  are bigger to find help there. In case there is a problem with the EPEL
>  packages please file them in bugzilla.redhat.com, then you'll reach the
>  maintainer of the bugzilla packages in EPEL.
>
>  CU
>  knurd (who never ever looked at the bugzilla package)
>  
I filed a bug on bugzilla.redhat.com and comtacted dwalsh(a)redhat.com about 
this. 

>  (¹) -- your post is not really on topic on this list; but also not
>  completely off topic and there is no epel-users-list, so it was IMHO
>  fine to post it here 
Thanks,

Tony
>  _______________________________________________
>  epel-devel-list mailing list
>  epel-devel-list(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/epel-devel-list

[R P Herrold]

On Fri, 25 Jan 2008, Tony Molloy wrote:

> > Seems nobody can't or doesn't want to (¹) reply. I'd
> suggest you ask on 
>  I filed a bug on bugzilla.redhat.com and comtacted dwalsh(a)redhat.com
> about
>  this. 
bug number, and which bugzilla Version, please; I am pretty 
familiar with the code and packaging it, as I have done so 
seperately from the EPEL effort for some time.  Last time I 
looked there was some strange handling (non-general or 
something -- I fergit) of the database keying in the 2. series 
bugzilla's packaging at EPEL.

-- Russ herrold

[Tony Molloy]

On Monday 28 January 2008 04:50:17 R P Herrold wrote:
>  On Fri, 25 Jan 2008, Tony Molloy wrote:
>  >> Seems nobody can't or doesn't want to (¹) reply. I'd suggest you ask
> on
>  >
>  > I filed a bug on bugzilla.redhat.com and comtacted dwalsh(a)redhat.com
>  > about this.
>
>  bug number, and which bugzilla Version, please; I am pretty
>  familiar with the code and packaging it, as I have done so
>  seperately from the EPEL effort for some time.  Last time I
>  looked there was some strange handling (non-general or
>  something -- I fergit) of the database keying in the 2. series
>  bugzilla's packaging at EPEL.
>
>  -- Russ herrold
>
>  _______________________________________________
>  epel-devel-list mailing list
>  epel-devel-list(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/epel-devel-list 
Sorry about that.

https://bugzilla.redhat.com/show_bug.cgi?id=429879

Tony

Bugzilla [EPEL package] problem

[R P Herrold]

On Mon, 28 Jan 2008, Tony Molloy wrote:

> > bug number, and which bugzilla Version, please; I am pretty
> > familiar with the code and packaging it, as I have done so
> > seperately from the EPEL effort for some time. 
>  https://bugzilla.redhat.com/show_bug.cgi?id=429879 
looks like some of the perl CGI scripts are not yet labelled 
properly to co-exist with enforcing in this packaging -- at 
least index.cgi and userprefs.cgi

The candidates to label are found with:
 	rpm -ql bugzilla | grep cgi
and we can see they are in:
 	/usr/share/bugzilla/

The sourced config file in that directory:
 	/usr/share/bugzilla/localconfig
was the one that I as thinking of that needed better handling 
in the packaging that I had seen (from my notes) 7 months ago.

The obvious short term workaround pending the update is to 
drop to permissive, which may or may not work in your 
environment.

-- Russ herrold

Bugzilla [EPEL package] problem

[Paul Howarth]

R P Herrold wrote:
>  On Mon, 28 Jan 2008, Tony Molloy wrote:
>  
> >> bug number, and which bugzilla Version, please; I am pretty
> >> familiar with the code and packaging it, as I have done so
> >> seperately from the EPEL effort for some time.
>  
> > https://bugzilla.redhat.com/show_bug.cgi?id=429879
>  
>  looks like some of the perl CGI scripts are not yet labelled properly to 
>  co-exist with enforcing in this packaging -- at least index.cgi and 
>  userprefs.cgi
>  
>  The candidates to label are found with:
>      rpm -ql bugzilla | grep cgi
>  and we can see they are in:
>      /usr/share/bugzilla/ 
All should be labelled correctly:

# semanage fcontext -l | grep bugzilla
/var/lib/bugzilla(/.*)?                            all files 
system_u:object_r:httpd_bugzilla_script_rw_t:s0
/usr/share/bugzilla(/.*)?                          directory 
system_u:object_r:httpd_bugzilla_content_t:s0
/usr/share/bugzilla(/.*)?                          regular file 
system_u:object_r:httpd_bugzilla_script_exec_t:s0

>  The obvious short term workaround pending the update is to drop to 
>  permissive, which may or may not work in your environment. 
Or add local policy to allow httpd_bugzilla_script_t to handle POSTed 
data (which ends up as being httpd_tmp_t) properly, as mentioned on 
fedora-selinux-list.

http://www.redhat.com/archives/fedora-selinux-list/2008-January/msg00146....

Paul.

Bugzilla [EPEL package] problem

[Tony Molloy]

On Monday 28 January 2008 15:48:18 Paul Howarth wrote:
>  R P Herrold wrote:
>  > On Mon, 28 Jan 2008, Tony Molloy wrote:
>  >>> bug number, and which bugzilla Version, please; I am pretty
>  >>> familiar with the code and packaging it, as I have done so
>  >>> seperately from the EPEL effort for some time.
>  >>
>  >> https://bugzilla.redhat.com/show_bug.cgi?id=429879
>  >
>  > looks like some of the perl CGI scripts are not yet labelled properly to
>  > co-exist with enforcing in this packaging -- at least index.cgi and
>  > userprefs.cgi
>  >
>  > The candidates to label are found with:
>  >     rpm -ql bugzilla | grep cgi
>  > and we can see they are in:
>  >     /usr/share/bugzilla/
>
>  All should be labelled correctly:
>
>  # semanage fcontext -l | grep bugzilla
>  /var/lib/bugzilla(/.*)?                            all files
>  system_u:object_r:httpd_bugzilla_script_rw_t:s0
>  /usr/share/bugzilla(/.*)?                          directory
>  system_u:object_r:httpd_bugzilla_content_t:s0
>  /usr/share/bugzilla(/.*)?                          regular file
>  system_u:object_r:httpd_bugzilla_script_exec_t:s0
>
>  > The obvious short term workaround pending the update is to drop to
>  > permissive, which may or may not work in your environment. 
I could do that but I don't want to. I'm working on a test server and I want 
it to run all services with selinux set to enforcing. Then I can configure 
all our production servers corectly.


What I did was generate a local policy and install it.


Tony

>  Or add local policy to allow httpd_bugzilla_script_t to handle POSTed
>  data (which ends up as being httpd_tmp_t) properly, as mentioned on
>  fedora-selinux-list.
>
>  http://www.redhat.com/archives/fedora-selinux-list/2008-January/msg00146.ht
> ml
>
>  Paul.
>
>  _______________________________________________
>  epel-devel-list mailing list
>  epel-devel-list(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/epel-devel-list