Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad Request

[Robin Beardsley]

This is what I ended up doing and it seems to have worked

mv /etc/sysconfig/rhn/systemid /etc/sysconfig/rhn/systemid.broken
yum clean all
moved the public.repo into /etc/yum.repos.d
yum downgrade httpd httpd-tools mod_ssl
/usr/sbin/spacewalk-service restart

mv /etc/sysconfig/rhn/systemid.broken /etc/sysconfig/rhn/systemid
yum clean all
removed public.repo from /etc/yum.repos.d
yum clean all

I can update clients again

Thanks all

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Radovan Drazny
Sent: Friday, April 21, 2017 9:53 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad Request

Robin,

this behavior is most likely caused by strict whitespace checking in httpd.
Try adding "HttpProtocolOptions Unsafe" directive to httpd config on your SW
server, and restart the httpd daemon. For more info see https://
httpd.apache.org/docs/2.4/mod/core.html#httpprotocoloptions

When an updated version of yum-rhn-plugin from Oracle will be available and
installed on your clients, you can remove the directive from you httpd config.

Problem is, I'm not sure this config option is available in the httpd version
shipped with Oracle linux. If httpd fails during the restart, remove the
"HttpProtocolOption".

In such case, the easiest workaround is what Avi recommended - you just have
to obtain previous versions of httpd, httpd-tools and mod_ssl rpms, and do a
manual downgrade.

Best regards

--
Radovan

On Friday, April 21, 2017 2:49:16 PM CEST Robin Beardsley wrote:
> Avi
>
> Thanks for the info. When I try and downgrade, I still get the same 404
> error.

> [root@oelsandbox ~]# yum downgrade httpd httpd-tools mod_ssl
> Loaded plugins: langpacks, rhnplugin, versionlock
> This system is receiving updates from Spacewalk server.
>
>
> One of the configured repositories failed (Unknown),
> and yum doesn't have enough cached data to continue. At this point the only
> safe thing yum can do is fail. There are a few ways to work "fix" this:
> 1. Contact the upstream for the repository and get them to fix the
> problem.

> 2. Reconfigure the baseurl/etc. for the repository, to point to a
> working
upstream. This is most often useful if you are using a newer
> distribution release than is supported by the repository (and the packages
> for the previous distribution release still work).
> 3. Run the command with the repository temporarily disabled
> yum --disablerepo= ...
>
> 4. Disable the repository permanently, so yum won't use it by default.
> Yum
will then just ignore the repository until you permanently enable it
> again or use --enablerepo for temporary usage:
>
> yum-config-manager --disable 
> or
> subscription-manager repos --disable=
>
> 5. Configure the failing repository to be skipped, if it is
> unavailable.
Note that yum will try to contact the repo. when it runs most
> commands, so will have to try and fail each time (and thus. yum will be be
> much slower). If it is a very temporary problem though, this is often a
> nice compromise:
>
> yum-config-manager --save
> --setopt=.skip_if_unavailable=true

> failed to retrieve repodata/repomd.xml from oraclelinux7-x86_64
> error was [Errno 14] HTTPS Error 400 - Bad Request
>
> My repolist:
> [root@oelsandbox ~]# yum repolist
> Loaded plugins: langpacks, rhnplugin, versionlock
> This system is receiving updates from Spacewalk server.
> repo id repo name
> status
oraclelinux7-x86_64 Oracle
> Linux 7 (x86_64) 0
> oraclelinux7-x86_64-addons Addons for Oracle Linux 7 (x86_64)
> 0 oraclelinux7-x86_64-optional Optional
> Packages for Oracle Linux 7 (x86_64) 0
> oraclelinux7-x86_64-scl12 Software Collection Library release
> 1.2 packages for Oracl 0 oraclelinux7-x86_64-spacewalk24-client Spacewalk
> 2.4 Client for Oracle Linux 7 (x86_64) 0
> oraclelinux7-x86_64-spacewalk24-server Spacewalk 2.4 Server for Oracle
> Linux 7 (x86_64) 0 oraclelinux7-x86_64-uek-r3 Latest
> Unbreakable Enterprise Kernel Release 3 for Oracle 0 repolist: 0
> [root@oelsandbox ~]#
>
> From: 
> spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>
> [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Avi Miller
Sent:
> Thursday, April 20, 2017 4:09 PM
> To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
> Subject: Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad
> Request

> Hi,
>
>
> > On 21 Apr 2017, at 1:23 am, Robin Beardsley
> > mailto:rbeards...@nedelta.com<mailto:rbeards...@nedelta.com%3cmailto:rbeards...@nedelta.com>>>
> >  wrote:
>
> >
> >
> > I’m hoping someone can help me. Today I tried to update my one of my
> > clients from my Spacew

Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad Request

[Rick van der Linde]

You may also want to try to set SELinux to "Permissive"to check whether it is 
an SELinux issue or else.



Rick



-Oorspronkelijk bericht-
Afzender: Robin Beardsley 
Verstuurd: Vrijdag 21 April 2017 16:21
Aan: spacewalk-list@redhat.com
Onderwerp: Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad Request

Thanks for the suggestions Radovan.  I’ll give it a shot.

 
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Radovan Drazny
Sent: Friday, April 21, 2017 9:53 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad Request

 
Robin,

this behavior is most likely caused by strict whitespace checking in httpd. 
Try adding "HttpProtocolOptions Unsafe" directive to httpd config on your SW 
server, and restart the httpd daemon. For more info see https://
httpd.apache.org/docs/2.4/mod/core.html#httpprotocoloptions

When an updated version of yum-rhn-plugin from Oracle will be available and 
installed on your clients, you can remove the directive from you httpd config.

Problem is, I'm not sure this config option is available in the httpd version 
shipped with Oracle linux. If httpd fails during the restart, remove the 
"HttpProtocolOption". 

In such case, the easiest workaround is what Avi recommended - you just have 
to obtain previous versions of httpd, httpd-tools and mod_ssl rpms, and do a 
manual downgrade.

Best regards

--
Radovan

On Friday, April 21, 2017 2:49:16 PM CEST Robin Beardsley wrote:
> Avi
> 
> Thanks for the info. When I try and downgrade, I still get the same 404
> error.

> [root@oelsandbox ~]# yum downgrade httpd httpd-tools mod_ssl
> Loaded plugins: langpacks, rhnplugin, versionlock
> This system is receiving updates from Spacewalk server.
> 
> 
> One of the configured repositories failed (Unknown),
> and yum doesn't have enough cached data to continue. At this point the only
> safe thing yum can do is fail. There are a few ways to work "fix" this: 
> 1. Contact the upstream for the repository and get them to fix the
> problem.

> 2. Reconfigure the baseurl/etc. for the repository, to point to a
> working
upstream. This is most often useful if you are using a newer
> distribution release than is supported by the repository (and the packages
> for the previous distribution release still work). 
> 3. Run the command with the repository temporarily disabled
> yum --disablerepo= ...
> 
> 4. Disable the repository permanently, so yum won't use it by default.
> Yum
will then just ignore the repository until you permanently enable it
> again or use --enablerepo for temporary usage:
> 
> yum-config-manager --disable 
> or
> subscription-manager repos --disable=
> 
> 5. Configure the failing repository to be skipped, if it is
> unavailable.
Note that yum will try to contact the repo. when it runs most
> commands, so will have to try and fail each time (and thus. yum will be be
> much slower). If it is a very temporary problem though, this is often a
> nice compromise:
> 
> yum-config-manager --save
> --setopt=.skip_if_unavailable=true

> failed to retrieve repodata/repomd.xml from oraclelinux7-x86_64
> error was [Errno 14] HTTPS Error 400 - Bad Request
> 
> My repolist:
> [root@oelsandbox ~]# yum repolist
> Loaded plugins: langpacks, rhnplugin, versionlock
> This system is receiving updates from Spacewalk server.
> repo id repo name 
> status
oraclelinux7-x86_64 Oracle
> Linux 7 (x86_64) 0
> oraclelinux7-x86_64-addons Addons for Oracle Linux 7 (x86_64) 
> 0 oraclelinux7-x86_64-optional Optional
> Packages for Oracle Linux 7 (x86_64) 0
> oraclelinux7-x86_64-scl12 Software Collection Library release
> 1.2 packages for Oracl 0 oraclelinux7-x86_64-spacewalk24-client Spacewalk
> 2.4 Client for Oracle Linux 7 (x86_64) 0
> oraclelinux7-x86_64-spacewalk24-server Spacewalk 2.4 Server for Oracle
> Linux 7 (x86_64) 0 oraclelinux7-x86_64-uek-r3 Latest
> Unbreakable Enterprise Kernel Release 3 for Oracle 0 repolist: 0
> [root@oelsandbox ~]#
> 
> From: spacewalk-list-boun...@redhat.com
> [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Avi Miller
Sent:
> Thursday, April 20, 2017 4:09 PM
> To: spacewalk-list@redhat.com
> Subject: Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad
> Request

> Hi,
> 
> 
> > On 21 Apr 2017, at 1:23 am, Robin Beardsley
> > mailto:rbeards...@nedelta.com>> wrote:
>
> >
> >
> > I’m hoping someone can help me. Today I tried to update my one of my
> > clients from my Spacewalker server and got this error.
> 
> You need to downgrade httpd on your Spacewalk server and wait for updated
> yum-rhn-plugin packages from Oracle. We’re pushing them out ASAP. 

Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad Request

[Uğur Engin]

Thanks @radovan. It saved my night.



On Fri, Apr 21, 2017 at 5:20 PM, Robin Beardsley 
wrote:

> Thanks for the suggestions Radovan.  I’ll give it a shot.
>
>
>
> *From:* spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-
> boun...@redhat.com] *On Behalf Of *Radovan Drazny
> *Sent:* Friday, April 21, 2017 9:53 AM
>
> *To:* spacewalk-list@redhat.com
> *Subject:* Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad
> Request
>
>
>
> Robin,
>
> this behavior is most likely caused by strict whitespace checking in
> httpd.
> Try adding "HttpProtocolOptions Unsafe" directive to httpd config on your
> SW
> server, and restart the httpd daemon. For more info see https://
> httpd.apache.org/docs/2.4/mod/core.html#httpprotocoloptions
>
> When an updated version of yum-rhn-plugin from Oracle will be available
> and
> installed on your clients, you can remove the directive from you httpd
> config.
>
> Problem is, I'm not sure this config option is available in the httpd
> version
> shipped with Oracle linux. If httpd fails during the restart, remove the
> "HttpProtocolOption".
>
> In such case, the easiest workaround is what Avi recommended - you just
> have
> to obtain previous versions of httpd, httpd-tools and mod_ssl rpms, and do
> a
> manual downgrade.
>
> Best regards
>
> --
> Radovan
>
> On Friday, April 21, 2017 2:49:16 PM CEST Robin Beardsley wrote:
> > Avi
> >
> > Thanks for the info. When I try and downgrade, I still get the same 404
> > error.
>
> > [root@oelsandbox ~]# yum downgrade httpd httpd-tools mod_ssl
> > Loaded plugins: langpacks, rhnplugin, versionlock
> > This system is receiving updates from Spacewalk server.
> >
> >
> > One of the configured repositories failed (Unknown),
> > and yum doesn't have enough cached data to continue. At this point the
> only
> > safe thing yum can do is fail. There are a few ways to work "fix" this:
> > 1. Contact the upstream for the repository and get them to fix the
> > problem.
>
> > 2. Reconfigure the baseurl/etc. for the repository, to point to a
> > working
> upstream. This is most often useful if you are using a newer
> > distribution release than is supported by the repository (and the
> packages
> > for the previous distribution release still work).
> > 3. Run the command with the repository temporarily disabled
> > yum --disablerepo= ...
> >
> > 4. Disable the repository permanently, so yum won't use it by default.
> > Yum
> will then just ignore the repository until you permanently enable it
> > again or use --enablerepo for temporary usage:
> >
> > yum-config-manager --disable 
> > or
> > subscription-manager repos --disable=
> >
> > 5. Configure the failing repository to be skipped, if it is
> > unavailable.
> Note that yum will try to contact the repo. when it runs most
> > commands, so will have to try and fail each time (and thus. yum will be
> be
> > much slower). If it is a very temporary problem though, this is often a
> > nice compromise:
> >
> > yum-config-manager --save
> > --setopt=.skip_if_unavailable=true
>
> > failed to retrieve repodata/repomd.xml from oraclelinux7-x86_64
> > error was [Errno 14] HTTPS Error 400 - Bad Request
> >
> > My repolist:
> > [root@oelsandbox ~]# yum repolist
> > Loaded plugins: langpacks, rhnplugin, versionlock
> > This system is receiving updates from Spacewalk server.
> > repo id repo name
> > status
> oraclelinux7-x86_64 Oracle
> > Linux 7 (x86_64) 0
> > oraclelinux7-x86_64-addons Addons for Oracle Linux 7 (x86_64)
> > 0 oraclelinux7-x86_64-optional Optional
> > Packages for Oracle Linux 7 (x86_64) 0
> > oraclelinux7-x86_64-scl12 Software Collection Library release
> > 1.2 packages for Oracl 0 oraclelinux7-x86_64-spacewalk24-client
> Spacewalk
> > 2.4 Client for Oracle Linux 7 (x86_64) 0
> > oraclelinux7-x86_64-spacewalk24-server Spacewalk 2.4 Server for Oracle
> > Linux 7 (x86_64) 0 oraclelinux7-x86_64-uek-r3 Latest
> > Unbreakable Enterprise Kernel Release 3 for Oracle 0 repolist: 0
> > [root@oelsandbox ~]#
> >
> > From: spacewalk-list-boun...@redhat.com
> > [mailto:spacewalk-list-boun...@redhat.com
> ] On Behalf Of Avi Miller
> Sent:
> > Thursday, April 20, 2017 4:09 PM
> > To: spacewalk-list@redhat.com
> > Subject: Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad
> > Request
>
> > Hi,
> >
> >
> > > On 21 Apr 2017, at 1:23 am, Robin Beardsley
> > &g

Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad Request

[Avi Miller]

Hi,

> On 21 Apr 2017, at 10:49 pm, Robin Beardsley  wrote:
> 
> Thanks for the info.  When I try and downgrade, I still get the same 404 
> error. 

Yes, it’s a catch-22. You need to disable the plugin and disable Spacewalk and 
downgrade using the upstream ULN/yum.oracle.com  repos.

To do this, download the public-yum-ol7.repo from 
http://yum.oracle.com/public-yum-ol7.repo 
 and put it in /etc/yum.repos.d/

Then, run yum to downgrade:

# yum —noplugins downgrade httpd httpd-tools mod_ssl

That will disable the Spacewalk client and downgrade http using the 
yum.oracle.com  repos. Once this is completed, move 
public-yum-ol7.repo out of /etc/yum.repos.d/

Cheers,
Avi

--
Oracle 
Avi Miller | Product Management Director | +61 (3) 8616 3496
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad Request

[Robin Beardsley]

Thanks for the suggestions Radovan.  I’ll give it a shot.

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Radovan Drazny
Sent: Friday, April 21, 2017 9:53 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad Request

Robin,

this behavior is most likely caused by strict whitespace checking in httpd.
Try adding "HttpProtocolOptions Unsafe" directive to httpd config on your SW
server, and restart the httpd daemon. For more info see https://
httpd.apache.org/docs/2.4/mod/core.html#httpprotocoloptions

When an updated version of yum-rhn-plugin from Oracle will be available and
installed on your clients, you can remove the directive from you httpd config.

Problem is, I'm not sure this config option is available in the httpd version
shipped with Oracle linux. If httpd fails during the restart, remove the
"HttpProtocolOption".

In such case, the easiest workaround is what Avi recommended - you just have
to obtain previous versions of httpd, httpd-tools and mod_ssl rpms, and do a
manual downgrade.

Best regards

--
Radovan

On Friday, April 21, 2017 2:49:16 PM CEST Robin Beardsley wrote:
> Avi
>
> Thanks for the info. When I try and downgrade, I still get the same 404
> error.

> [root@oelsandbox ~]# yum downgrade httpd httpd-tools mod_ssl
> Loaded plugins: langpacks, rhnplugin, versionlock
> This system is receiving updates from Spacewalk server.
>
>
> One of the configured repositories failed (Unknown),
> and yum doesn't have enough cached data to continue. At this point the only
> safe thing yum can do is fail. There are a few ways to work "fix" this:
> 1. Contact the upstream for the repository and get them to fix the
> problem.

> 2. Reconfigure the baseurl/etc. for the repository, to point to a
> working
upstream. This is most often useful if you are using a newer
> distribution release than is supported by the repository (and the packages
> for the previous distribution release still work).
> 3. Run the command with the repository temporarily disabled
> yum --disablerepo= ...
>
> 4. Disable the repository permanently, so yum won't use it by default.
> Yum
will then just ignore the repository until you permanently enable it
> again or use --enablerepo for temporary usage:
>
> yum-config-manager --disable 
> or
> subscription-manager repos --disable=
>
> 5. Configure the failing repository to be skipped, if it is
> unavailable.
Note that yum will try to contact the repo. when it runs most
> commands, so will have to try and fail each time (and thus. yum will be be
> much slower). If it is a very temporary problem though, this is often a
> nice compromise:
>
> yum-config-manager --save
> --setopt=.skip_if_unavailable=true

> failed to retrieve repodata/repomd.xml from oraclelinux7-x86_64
> error was [Errno 14] HTTPS Error 400 - Bad Request
>
> My repolist:
> [root@oelsandbox ~]# yum repolist
> Loaded plugins: langpacks, rhnplugin, versionlock
> This system is receiving updates from Spacewalk server.
> repo id repo name
> status
oraclelinux7-x86_64 Oracle
> Linux 7 (x86_64) 0
> oraclelinux7-x86_64-addons Addons for Oracle Linux 7 (x86_64)
> 0 oraclelinux7-x86_64-optional Optional
> Packages for Oracle Linux 7 (x86_64) 0
> oraclelinux7-x86_64-scl12 Software Collection Library release
> 1.2 packages for Oracl 0 oraclelinux7-x86_64-spacewalk24-client Spacewalk
> 2.4 Client for Oracle Linux 7 (x86_64) 0
> oraclelinux7-x86_64-spacewalk24-server Spacewalk 2.4 Server for Oracle
> Linux 7 (x86_64) 0 oraclelinux7-x86_64-uek-r3 Latest
> Unbreakable Enterprise Kernel Release 3 for Oracle 0 repolist: 0
> [root@oelsandbox ~]#
>
> From: 
> spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>
> [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Avi Miller
Sent:
> Thursday, April 20, 2017 4:09 PM
> To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
> Subject: Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad
> Request

> Hi,
>
>
> > On 21 Apr 2017, at 1:23 am, Robin Beardsley
> > mailto:rbeards...@nedelta.com<mailto:rbeards...@nedelta.com%3cmailto:rbeards...@nedelta.com>>>
> >  wrote:
>
> >
> >
> > I’m hoping someone can help me. Today I tried to update my one of my
> > clients from my Spacewalker server and got this error.
>
> You need to downgrade httpd on your Spacewalk server and wait for updated
> yum-rhn-plugin packages from Oracle. We’re pushing them out ASAP. Once
> we’ve released the new yum-rhn-plugin RPMs and you’ve upgraded all your
> clients, you can upgrade httpd on your server again.

> To downgrade, run:
>
> # yum downg

Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad Request

[Radovan Drazny]

Robin,

this behavior is most likely caused by strict whitespace checking in httpd. 
Try adding "HttpProtocolOptions Unsafe" directive to httpd config on your SW 
server, and restart the httpd daemon. For more info see https://
httpd.apache.org/docs/2.4/mod/core.html#httpprotocoloptions

When an updated version of yum-rhn-plugin from Oracle will be available and 
installed on your clients, you can remove the directive from you httpd config.

Problem is, I'm not sure this config option is available in the httpd version 
shipped with Oracle linux. If httpd fails during the restart, remove the 
"HttpProtocolOption". 

In such case, the easiest workaround is what Avi recommended - you just have 
to obtain previous versions of httpd, httpd-tools and mod_ssl rpms, and do a 
manual downgrade.

Best regards

--
Radovan

On Friday, April 21, 2017 2:49:16 PM CEST Robin Beardsley wrote:
> Avi
> 
> Thanks for the info.  When I try and downgrade, I still get the same 404
> error.
 
> [root@oelsandbox ~]# yum downgrade httpd httpd-tools mod_ssl
> Loaded plugins: langpacks, rhnplugin, versionlock
> This system is receiving updates from Spacewalk server.
> 
> 
> One of the configured repositories failed (Unknown),
> and yum doesn't have enough cached data to continue. At this point the only
> safe thing yum can do is fail. There are a few ways to work "fix" this: 
>  1. Contact the upstream for the repository and get them to fix the
> problem.
 
>  2. Reconfigure the baseurl/etc. for the repository, to point to a
> working
 upstream. This is most often useful if you are using a newer
> distribution release than is supported by the repository (and the packages
> for the previous distribution release still work). 
>  3. Run the command with the repository temporarily disabled
> yum --disablerepo= ...
> 
>  4. Disable the repository permanently, so yum won't use it by default.
> Yum
 will then just ignore the repository until you permanently enable it
> again or use --enablerepo for temporary usage:
> 
> yum-config-manager --disable 
> or
> subscription-manager repos --disable=
> 
>  5. Configure the failing repository to be skipped, if it is
> unavailable.
 Note that yum will try to contact the repo. when it runs most
> commands, so will have to try and fail each time (and thus. yum will be be
> much slower). If it is a very temporary problem though, this is often a
> nice compromise:
> 
> yum-config-manager --save
> --setopt=.skip_if_unavailable=true
 
> failed to retrieve repodata/repomd.xml from oraclelinux7-x86_64
> error was [Errno 14] HTTPS Error 400 - Bad Request
> 
> My repolist:
> [root@oelsandbox ~]# yum repolist
> Loaded plugins: langpacks, rhnplugin, versionlock
> This system is receiving updates from Spacewalk server.
> repo idrepo name
>  status
 oraclelinux7-x86_64Oracle
> Linux 7 (x86_64)0
> oraclelinux7-x86_64-addons Addons for Oracle Linux 7 (x86_64)  
>   0 oraclelinux7-x86_64-optional   Optional
> Packages for Oracle Linux 7 (x86_64)  0
> oraclelinux7-x86_64-scl12  Software Collection Library release
> 1.2 packages for Oracl 0 oraclelinux7-x86_64-spacewalk24-client Spacewalk
> 2.4 Client for Oracle Linux 7 (x86_64)   0
> oraclelinux7-x86_64-spacewalk24-server Spacewalk 2.4 Server for Oracle
> Linux 7 (x86_64)   0 oraclelinux7-x86_64-uek-r3 Latest
> Unbreakable Enterprise Kernel Release 3 for Oracle  0 repolist: 0
> [root@oelsandbox ~]#
> 
> From: spacewalk-list-boun...@redhat.com
> [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Avi Miller
 Sent:
> Thursday, April 20, 2017 4:09 PM
> To: spacewalk-list@redhat.com
> Subject: Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad
> Request
 
> Hi,
> 
> 
> > On 21 Apr 2017, at 1:23 am, Robin Beardsley
> > mailto:rbeards...@nedelta.com>> wrote:
>
> >
> >
> > I’m hoping someone can help me. Today I tried to update my one of my
> > clients from my Spacewalker server and got this error.
> 
> You need to downgrade httpd on your Spacewalk server and wait for updated
> yum-rhn-plugin packages from Oracle. We’re pushing them out ASAP. Once
> we’ve released the new yum-rhn-plugin RPMs and you’ve upgraded all your
> clients, you can upgrade httpd on your server again.
 
> To downgrade, run:
> 
> # yum downgrade httpd httpd-tools mod_ssl
> 
> On your Spacewalk server. That should restore functionality.
> 
> Cheers,
> Avi

Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad Request

[Robin Beardsley]

Avi

Thanks for the info.  When I try and downgrade, I still get the same 404 error.

[root@oelsandbox ~]# yum downgrade httpd httpd-tools mod_ssl
Loaded plugins: langpacks, rhnplugin, versionlock
This system is receiving updates from Spacewalk server.


One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
yum --disablerepo= ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable 
or
subscription-manager repos --disable=

 5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=.skip_if_unavailable=true

failed to retrieve repodata/repomd.xml from oraclelinux7-x86_64
error was [Errno 14] HTTPS Error 400 - Bad Request

My repolist:
[root@oelsandbox ~]# yum repolist
Loaded plugins: langpacks, rhnplugin, versionlock
This system is receiving updates from Spacewalk server.
repo idrepo name
  status
oraclelinux7-x86_64Oracle Linux 7 (x86_64)  
  0
oraclelinux7-x86_64-addons Addons for Oracle Linux 7 (x86_64)   
  0
oraclelinux7-x86_64-optional   Optional Packages for Oracle Linux 7 
(x86_64)  0
oraclelinux7-x86_64-scl12  Software Collection Library release 1.2 
packages for Oracl 0
oraclelinux7-x86_64-spacewalk24-client Spacewalk 2.4 Client for Oracle Linux 7 
(x86_64)   0
oraclelinux7-x86_64-spacewalk24-server Spacewalk 2.4 Server for Oracle Linux 7 
(x86_64)   0
oraclelinux7-x86_64-uek-r3 Latest Unbreakable Enterprise Kernel 
Release 3 for Oracle  0
repolist: 0
[root@oelsandbox ~]#

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Avi Miller
Sent: Thursday, April 20, 2017 4:09 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad Request

Hi,

> On 21 Apr 2017, at 1:23 am, Robin Beardsley 
> mailto:rbeards...@nedelta.com>> wrote:
>
> I’m hoping someone can help me. Today I tried to update my one of my clients 
> from my Spacewalker server and got this error.

You need to downgrade httpd on your Spacewalk server and wait for updated 
yum-rhn-plugin packages from Oracle. We’re pushing them out ASAP. Once we’ve 
released the new yum-rhn-plugin RPMs and you’ve upgraded all your clients, you 
can upgrade httpd on your server again.

To downgrade, run:

# yum downgrade httpd httpd-tools mod_ssl

On your Spacewalk server. That should restore functionality.

Cheers,
Avi

--
Oracle <http://www.oracle.com<http://www.oracle.com>>
Avi Miller | Product Management Director | +61 (3) 8616 3496
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia


___
Spacewalk-list mailing list
Spacewalk-list@redhat.com<mailto:Spacewalk-list@redhat.com>
https://www.redhat.com/mailman/listinfo/spacewalk-list<https://www.redhat.com/mailman/listinfo/spacewalk-list>
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk server HTTPS Error 400 - Bad Request

[Avi Miller]

Hi,

> On 21 Apr 2017, at 1:23 am, Robin Beardsley  wrote:
> 
> I’m hoping someone can help me.  Today I tried to update my one of my clients 
> from my Spacewalker server and got this error.

You need to downgrade httpd on your Spacewalk server and wait for updated 
yum-rhn-plugin packages from Oracle. We’re pushing them out ASAP. Once we’ve 
released the new yum-rhn-plugin RPMs and you’ve upgraded all your clients, you 
can upgrade httpd on your server again.

To downgrade, run:

# yum downgrade httpd httpd-tools mod_ssl

On your Spacewalk server. That should restore functionality.

Cheers,
Avi

--
Oracle 
Avi Miller | Product Management Director | +61 (3) 8616 3496
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia


___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list