From ayoung at redhat.com Tue Jan 7 19:37:54 2014 From: ayoung at redhat.com (Adam Young) Date: Tue, 07 Jan 2014 14:37:54 -0500 Subject: [rhos-list] Congrats to Jamie Lennox on appointment to Keystone core Message-ID: <52CC5792.6060007@redhat.com> Jamie has well earned his core status on Keystone. Well done. From ADRIAANL at za.ibm.com Wed Jan 8 20:04:46 2014 From: ADRIAANL at za.ibm.com (Adriaan de Lange) Date: Wed, 8 Jan 2014 22:04:46 +0200 Subject: [rhos-list] AUTO: Adriaan de Lange is out of the office - LEAVE - (returning 01/23/2014) Message-ID: I am out of the office until 01/23/2014. Good day Please note that Im on leave and will not be availble. If you need any assistance please contact Shandani Madima ITS Service Delivery Manager Middleware & ICS Tel: +27 11 302 9246 Mobile: +27 82 347 7037 Adriaan De Lange Certified IT Specialist ITS Note: This is an automated response to your message "rhos-list Digest, Vol 18, Issue 1" sent on 08/01/2014 19:00:03. This is the only notification you will receive while this person is away. From xzhao at bnl.gov Tue Jan 14 15:01:41 2014 From: xzhao at bnl.gov (Xin Zhao) Date: Tue, 14 Jan 2014 10:01:41 -0500 Subject: [rhos-list] rhos kernel update ? Message-ID: <52D55155.1090006@bnl.gov> Hello, The new kernel version from SL6.4 security updates is kernel-2.6.32-431.1.2.el6.x86_64, higher than what is available by way of the openstack repo (kernel-2.6.32-358.123.2.openstack.el6). Is there a plan to upgrade the openstack specific kernel to 431 ? Thanks, Xin From pmyers at redhat.com Tue Jan 14 15:20:21 2014 From: pmyers at redhat.com (Perry Myers) Date: Tue, 14 Jan 2014 10:20:21 -0500 Subject: [rhos-list] rhos kernel update ? In-Reply-To: <52D55155.1090006@bnl.gov> References: <52D55155.1090006@bnl.gov> Message-ID: <52D555B5.90703@redhat.com> On 01/14/2014 10:01 AM, Xin Zhao wrote: > Hello, > > The new kernel version from SL6.4 security updates is > kernel-2.6.32-431.1.2.el6.x86_64, higher than what is available by way > of the openstack repo (kernel-2.6.32-358.123.2.openstack.el6). > Is there a plan to upgrade the openstack specific kernel to 431 ? New kernels for OpenStack are shipped in RHEL 6.5. In RHEL 6.5 you should have access to 2.6.32-431.1.2.el6 The .openstack kernels shipped in the RHOS channel directly were only supplied because we could not get certain patches into the RHEL 6.4 async stream (without creating risk for our non OpenStack customers) All of the core functionality we put into the .openstack kernels (GRE, openvswitch enhancements, network namespaces) were merged into the mainline RHEL 6.5 kernel. So the correct path is to update from the last .openstack kernel in RHOS 4.0 to the RHEL 6.5 kernel. Perry From mmosesohn at mirantis.com Tue Jan 14 15:25:43 2014 From: mmosesohn at mirantis.com (Matthew Mosesohn) Date: Tue, 14 Jan 2014 19:25:43 +0400 Subject: [rhos-list] rhos kernel update ? In-Reply-To: <52D555B5.90703@redhat.com> References: <52D55155.1090006@bnl.gov> <52D555B5.90703@redhat.com> Message-ID: Perry, thanks for the clarification. I wasn't sure if the patches were merged in 6.5 yet either. On Tue, Jan 14, 2014 at 7:20 PM, Perry Myers wrote: > On 01/14/2014 10:01 AM, Xin Zhao wrote: >> Hello, >> >> The new kernel version from SL6.4 security updates is >> kernel-2.6.32-431.1.2.el6.x86_64, higher than what is available by way >> of the openstack repo (kernel-2.6.32-358.123.2.openstack.el6). >> Is there a plan to upgrade the openstack specific kernel to 431 ? > > New kernels for OpenStack are shipped in RHEL 6.5. In RHEL 6.5 you > should have access to 2.6.32-431.1.2.el6 > > The .openstack kernels shipped in the RHOS channel directly were only > supplied because we could not get certain patches into the RHEL 6.4 > async stream (without creating risk for our non OpenStack customers) > > All of the core functionality we put into the .openstack kernels (GRE, > openvswitch enhancements, network namespaces) were merged into the > mainline RHEL 6.5 kernel. > > So the correct path is to update from the last .openstack kernel in RHOS > 4.0 to the RHEL 6.5 kernel. > > Perry > > _______________________________________________ > rhos-list mailing list > rhos-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhos-list From xzhao at bnl.gov Fri Jan 24 22:16:31 2014 From: xzhao at bnl.gov (Xin Zhao) Date: Fri, 24 Jan 2014 17:16:31 -0500 Subject: [rhos-list] instances with ephemeral disk can't start ? Message-ID: <52E2E63F.8040305@bnl.gov> Hello, In our grizzly openstack testbed, instances that use ephemeral disk fail to run, in the scheduler log there is the following errors: scheduler.log:2014-01-24 16:43:55.772 ERROR nova.scheduler.filter_scheduler [req-32173fb7-8d49-4d17-8490-4a6ddaf18a67 45a137d469c940cab24655ce65a8455e 614dfb1842824ded94893d0e4c2525dc] [instance: 799b985a-eba5-49ef-80b9-c515fa0523c2] Error from last host: cldh0195.cloud.local (node cldh0195.cloud.local): [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 864, in _run_instance\n set_access_ip=set_access_ip)\n', u' File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1123, in _spawn\n LOG.exception(_(\'Instance failed to spawn\'), instance=instance)\n', u' File "/usr/lib64/python2.6/contextlib.py", line 23, in __exit__\n self.gen.next()\n', u' File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1119, in _spawn\n block_device_info)\n', u' File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 1540, in spawn\n admin_pass=admin_password)\n', u' File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 1842, in _create_image\n ephemeral_size=ephemeral_gb)\n', u' File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/imagebackend.py", line 158, in cache\n *args, **kwargs)\n', u' File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/imagebackend.py", line 291, in create_image\n prepare_template(target=base, max_size=size, *args, **kwargs)\n', u' File "/usr/lib/python2.6/site-packages/nova/openstack/common/lockutils.py", line 228, in inner\n retval = f(*args, **kwargs)\n', u' File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/imagebackend.py", line 146, in call_if_not_exists\n fetch_func(target=target, *args, **kwargs)\n', u"/TypeError: _create_ephemeral() got an unexpected keyword argument 'max_size'/\n"] I see a bug report like this : https://bugzilla.redhat.com/show_bug.cgi?id=1044562, I wonder if this bug is fixed in grizzly or not? I am using grizzly rpms from the RDO repo: $> rpm -qf /usr/lib/python2.6/site-packages/nova/virt/libvirt/imagebackend.py python-nova-2013.1.4-1.el6.noarch Thanks, Xin -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfv at eurotux.com Mon Jan 27 19:07:53 2014 From: dfv at eurotux.com (Diogo Vieira) Date: Mon, 27 Jan 2014 19:07:53 +0000 Subject: [rhos-list] Swift: Getting errors like "Unable to create container" with successfully creating it Message-ID: <6AAF2BF8-8C74-4E7F-A06A-C23B5C8827D8@eurotux.com> Hi, I've been noticing a strange pattern on my swift cluster and I was hoping you could help me. I'm running 1 Proxy Node and 1 Storage Node on the same physical machine and 4 more Storage Nodes in virtual machines. Whenever I try to create a new container in the Horizon (dashboard) interface I get an "Unable to create container" error. What's strange is that if I refresh the list I can confirm it has been created. The same problem happens using the REST API which gives me an 503 "Service unavailable" error but successfully creates the container. Since I couldn't find any logs or any similar problem happening to other people, can you try to help me troubleshoot this problem? What should I do first? Thank you for your help, Diogo Vieira From johnvh24 at hotmail.com Tue Jan 28 22:00:04 2014 From: johnvh24 at hotmail.com (John Van Haastert) Date: Tue, 28 Jan 2014 14:00:04 -0800 Subject: [rhos-list] Redhat RHEL Openstack 4.0 - Patch updates Message-ID: Recommendation for the best way to get the RedHat updates for Openstack 4.0 channel subscription. Is it just a matter of changing the /etc/yum/pluginconf/rhnplugin.conf ?enabled = 1? to ?enabled = 0? and then run "sudo yum update? ? Currently ?yum update? is showing 942 packages excluded due to repository priority protections. Want to make sure that I get updates specific to the RedHat Openstack 4.0 channel subscription ( i.e. RHEL 6.5 - Havanan). The RedHat Classic Subscription Management has a several Openstack Updates is the above the correct way of getting these OpenStack 4.0 updates ? Thanks in advance. ?Johnvh From johnvh24 at hotmail.com Tue Jan 28 23:47:13 2014 From: johnvh24 at hotmail.com (John Van Haastert) Date: Tue, 28 Jan 2014 15:47:13 -0800 Subject: [rhos-list] Redhat RHEL Openstack 4.0 - Patch updates In-Reply-To: <3E9D7F60-F20D-49BA-BF8A-385B314F131B@hotmail.com> References: <3E9D7F60-F20D-49BA-BF8A-385B314F131B@hotmail.com> Message-ID: I believe that should be /etc/yum/pluginconf/priorities.conf instead of rhnplugin.cong. Just want to be sure if I change to ?enable=0? that I will not pick up other Openstack updates not intended for OpenStack 4.0 channel subscription. ?Johnvh On Jan 28, 2014, at 2:00 PM, John Van Haastert wrote: > Recommendation for the best way to get the RedHat updates for Openstack 4.0 channel subscription. Is it just a matter of changing the /etc/yum/pluginconf/rhnplugin.conf ?enabled = 1? to ?enabled = 0? and then run "sudo yum update? ? > > Currently ?yum update? is showing 942 packages excluded due to repository priority protections. Want to make sure that I get updates specific to the RedHat Openstack 4.0 channel subscription ( i.e. RHEL 6.5 - Havanan). The RedHat Classic Subscription Management has a several Openstack Updates is the above the correct way of getting these OpenStack 4.0 updates ? > > Thanks in advance. > > ?Johnvh From wook-k at hanmail.net Wed Jan 29 00:44:51 2014 From: wook-k at hanmail.net (=?utf-8?B?6rmA7Jqx?=) Date: Wed, 29 Jan 2014 09:44:51 +0900 (KST) Subject: [rhos-list] hi I have question(Loaded plugins: product-id.....) Message-ID: <20140129094451.HM.F000000000GQdUx@wook-k.wwl1552.hanmail.net> An HTML attachment was scrubbed... URL: From johnvh24 at hotmail.com Wed Jan 29 03:06:05 2014 From: johnvh24 at hotmail.com (John Van Haastert) Date: Tue, 28 Jan 2014 19:06:05 -0800 Subject: [rhos-list] Redhat RHEL Openstack 4.0 - Patch updates In-Reply-To: References: <3E9D7F60-F20D-49BA-BF8A-385B314F131B@hotmail.com> Message-ID: I believe this is an issue with running the RDO Packstack which in that case I do not want the RedHat OpenStack 4.0 updates. ?Johnvh On Jan 28, 2014, at 3:47 PM, John Van Haastert wrote: > I believe that should be /etc/yum/pluginconf/priorities.conf instead of rhnplugin.cong. Just want to be sure if I change to ?enable=0? that I will not pick up other Openstack updates not intended for OpenStack 4.0 channel subscription. > > ?Johnvh > > On Jan 28, 2014, at 2:00 PM, John Van Haastert wrote: > >> Recommendation for the best way to get the RedHat updates for Openstack 4.0 channel subscription. Is it just a matter of changing the /etc/yum/pluginconf/rhnplugin.conf ?enabled = 1? to ?enabled = 0? and then run "sudo yum update? ? >> >> Currently ?yum update? is showing 942 packages excluded due to repository priority protections. Want to make sure that I get updates specific to the RedHat Openstack 4.0 channel subscription ( i.e. RHEL 6.5 - Havanan). The RedHat Classic Subscription Management has a several Openstack Updates is the above the correct way of getting these OpenStack 4.0 updates ? >> >> Thanks in advance. >> >> ?Johnvh > > From pmyers at redhat.com Wed Jan 29 18:38:56 2014 From: pmyers at redhat.com (Perry Myers) Date: Wed, 29 Jan 2014 13:38:56 -0500 Subject: [rhos-list] Redhat RHEL Openstack 4.0 - Patch updates In-Reply-To: References: Message-ID: <52E94AC0.6070208@redhat.com> On 28/01/14 17:00, John Van Haastert wrote: > Recommendation for the best way to get the RedHat updates for > Openstack 4.0 channel subscription. Is it just a matter of changing > the /etc/yum/pluginconf/rhnplugin.conf ?enabled = 1? to ?enabled = 0? > and then run "sudo yum update? ? > > Currently ?yum update? is showing 942 packages excluded due to > repository priority protections. Want to make sure that I get > updates specific to the RedHat Openstack 4.0 channel subscription ( > i.e. RHEL 6.5 - Havanan). The RedHat Classic Subscription Management > has a several Openstack Updates is the above the correct way of > getting these OpenStack 4.0 updates ? > > Thanks in advance. Lon or Bryan, can you assist with this question? Perry From lhh at redhat.com Wed Jan 29 21:25:27 2014 From: lhh at redhat.com (Lon Hohberger) Date: Wed, 29 Jan 2014 16:25:27 -0500 Subject: [rhos-list] Redhat RHEL Openstack 4.0 - Patch updates In-Reply-To: <52E94AC0.6070208@redhat.com> References: <52E94AC0.6070208@redhat.com> Message-ID: <52E971C7.3020301@redhat.com> On 01/29/2014 01:38 PM, Perry Myers wrote: > On 28/01/14 17:00, John Van Haastert wrote: >> Recommendation for the best way to get the RedHat updates for >> Openstack 4.0 channel subscription. Is it just a matter of changing >> the /etc/yum/pluginconf/rhnplugin.conf ?enabled = 1? to ?enabled = 0? >> and then run "sudo yum update? ? >> >> Currently ?yum update? is showing 942 packages excluded due to >> repository priority protections. Want to make sure that I get >> updates specific to the RedHat Openstack 4.0 channel subscription ( >> i.e. RHEL 6.5 - Havanan). The RedHat Classic Subscription Management >> has a several Openstack Updates is the above the correct way of >> getting these OpenStack 4.0 updates ? >> >> Thanks in advance. > > Lon or Bryan, can you assist with this question? > Once subscribed to RHN, /etc/yum/pluginconf/rhnplugin.conf's "enabled" attribute will be 1 (as you guessed), but merely changing it is not likely to have the desired effect. It sounds as though the system isn't using RHN classic - is that right? If so, you'll need to register with RHN. Subscribing a system to RHN Classic can be accomplished using the rhn_register utility. The RHEL OpenStack Platform 4 release notes detail which channels to subscribe to (or disable) in section 2.3.2 for RHN classic and 2.3.1 for subscription-manager (CDN): https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/4/pdf/Release_Notes/Red_Hat_Enterprise_Linux_OpenStack_Platform-4-Release_Notes-en-US.pdf Also, when you run 'yum update', it will tell you which repository a given package is coming from. If you have additional repositories, such as EPEL, installed, certain packages from these repositories may try to replace the supported ones from Red Hat. A quick way to work around this is to uninstall the third party repositories, but if you don't want to do this... If you're using RHN Classic, I think you can give priorities to each channel over other repositories on the system. Edit /etc/yum/pluginconf/rhnplugin.conf and priorities for each of the channels you really don't want other repositories to override (channel names can be found in 2.3.2 of the OpenStack 4 release notes from Red Hat): [rhel-x86_64-server-6] priority=1 [rhel-x86_64-server-6-ost-4] priority=1 If you're using subscription manager, I'd have to do a bit more looking around (a quick check to see if editing /etc/yum/pluginconf.d/subscription-manager.conf in the same way as RHN Classic didn't appear to work for me). However, with both RHN Classic and CDN/subscription-manager, the following should work (with no configuration editing): yum update --disablerepo= E.g.: yum update --disablerepo=epel -- Lon From johnvh24 at hotmail.com Thu Jan 30 03:30:22 2014 From: johnvh24 at hotmail.com (John Van Haastert) Date: Wed, 29 Jan 2014 19:30:22 -0800 Subject: [rhos-list] Redhat RHEL Openstack 4.0 - Patch updates In-Reply-To: <52E971C7.3020301@redhat.com> References: <52E94AC0.6070208@redhat.com> <52E971C7.3020301@redhat.com> Message-ID: Thanks Lon, I have tried initially to use subscription manager but have since settle back on RHN Classic using rhn_register. I have install RDO packstack havana for now and RHN Classic Web is showing critical Openstack updates but I am now assuming those updates are specific to Red Hat Openstack 4 Channel deployment. Is this correct ? yum repolist Loaded plugins: priorities, product-id, rhnplugin, security, subscription-manager This system is receiving updates from Red Hat Subscription Management. This system is receiving updates from RHN Classic or RHN Satellite. epel/metalink | 8.7 kB 00:00 epel | 4.2 kB 00:00 epel/primary_db | 5.9 MB 00:02 foreman | 2.9 kB 00:00 foreman-plugins | 3.7 kB 00:00 openstack-havana | 2.9 kB 00:00 puppetlabs-deps | 1.9 kB 00:00 puppetlabs-products | 1.9 kB 00:00 puppetlabs-products/primary_db | 105 kB 00:00 rhel-6-server-cf-tools-1-rpms | 2.8 kB 00:00 rhel-6-server-rhev-agent-rpms | 3.1 kB 00:00 rhel-6-server-rpms | 3.7 kB 00:00 rhel-lb-for-rhel-6-server-rpms | 3.7 kB 00:00 rhel-x86_64-server-6-ost-4 | 1.6 kB 00:00 rhel-x86_64-server-optional-6 | 1.8 kB 00:00 1515 packages excluded due to repository priority protections repo id repo name status epel Extra Packages for Enterprise Linux 6 - x86_64 10,328+69 foreman Foreman stable 215 foreman-plugins Foreman stable - plugins 42 openstack-havana OpenStack Havana Repository 563+155 puppetlabs-deps Puppet Labs Dependencies El 6 - x86_64 54 puppetlabs-products Puppet Labs Products El 6 - x86_64 327 rhel-6-server-cf-tools-1-rpms Red Hat CloudForms Tools for RHEL 6 (RPMs) 30+1 rhel-6-server-rhev-agent-rpms Red Hat Enterprise Virtualization Agents for RHEL 6 Server (RPMs) 36 rhel-6-server-rpms Red Hat Enterprise Linux 6 Server (RPMs) 11,622+572 rhel-lb-for-rhel-6-server-rpms Red Hat Enterprise Linux Load Balancer (for RHEL 6 Server) (RPMs) 14 rhel-x86_64-server-6 Red Hat Enterprise Linux Server (v. 6 for 64-bit x86_64) 11,617+566 rhel-x86_64-server-6-ost-4 Red Hat OpenStack 4.0 323+192 rhel-x86_64-server-optional-6 RHEL Server Optional (v. 6 64-bit x86_64) 6,823+115 repolist: 41,994 cat /etc/yum/pluginconf.d/rhnplugin.conf [main] enabled = 1 gpgcheck = 1 timeout = 120 cat /etc/yum/pluginconf.d/priorities.conf [main] enabled = 1 cat /etc/yum/pluginconf.d/subscription-manager.conf [main] enabled=1 cat /etc/yum/pluginconf.d/product-id.conf [main] enabled=1 cat /etc/yum/pluginconf.d/security.conf [main] enabled=1 Type Advisory Synopsis Status Updated RHSA-2014:0089 Moderate: openstack-keystone security and bug fix update Failed 1/22/14 RHBA-2014:0046 Red Hat Enterprise Linux OpenStack Platform 4 Bug Fix and Enhancement Advisory None 1/22/14 RHSA-2014:0090 Moderate: openstack-heat security, bug fix, and enhancement update Failed 1/22/14 RHSA-2014:0091 Moderate: openstack-neutron security, bug fix, and enhancement update Failed 1/22/14 RHEA-2013:1859 Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory None 12/20/13 sunserver2.cyanoptics.com 1/29/14 2:22:31 AM EET Error while executing packages action: empty transaction [[6]] Assuming given the above /etc/yum/pluginconf.d/ files the enabled=1 is preventing these updates. Thanks again Lon just wanted a sanity check. ?Johnvh On Jan 29, 2014, at 1:25 PM, Lon Hohberger wrote: > On 01/29/2014 01:38 PM, Perry Myers wrote: >> On 28/01/14 17:00, John Van Haastert wrote: >>> Recommendation for the best way to get the RedHat updates for >>> Openstack 4.0 channel subscription. Is it just a matter of changing >>> the /etc/yum/pluginconf/rhnplugin.conf ?enabled = 1? to ?enabled = 0? >>> and then run "sudo yum update? ? >>> >>> Currently ?yum update? is showing 942 packages excluded due to >>> repository priority protections. Want to make sure that I get >>> updates specific to the RedHat Openstack 4.0 channel subscription ( >>> i.e. RHEL 6.5 - Havanan). The RedHat Classic Subscription Management >>> has a several Openstack Updates is the above the correct way of >>> getting these OpenStack 4.0 updates ? >>> >>> Thanks in advance. >> >> Lon or Bryan, can you assist with this question? >> > > Once subscribed to RHN, /etc/yum/pluginconf/rhnplugin.conf's "enabled" > attribute will be 1 (as you guessed), but merely changing it is not > likely to have the desired effect. > > It sounds as though the system isn't using RHN classic - is that right? > If so, you'll need to register with RHN. Subscribing a system to RHN > Classic can be accomplished using the rhn_register utility. > > The RHEL OpenStack Platform 4 release notes detail which channels to > subscribe to (or disable) in section 2.3.2 for RHN classic and 2.3.1 for > subscription-manager (CDN): > > > https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/4/pdf/Release_Notes/Red_Hat_Enterprise_Linux_OpenStack_Platform-4-Release_Notes-en-US.pdf > > Also, when you run 'yum update', it will tell you which repository a > given package is coming from. If you have additional repositories, such > as EPEL, installed, certain packages from these repositories may try to > replace the supported ones from Red Hat. > > A quick way to work around this is to uninstall the third party > repositories, but if you don't want to do this... > > If you're using RHN Classic, I think you can give priorities to each > channel over other repositories on the system. Edit > /etc/yum/pluginconf/rhnplugin.conf and priorities for each of the > channels you really don't want other repositories to override (channel > names can be found in 2.3.2 of the OpenStack 4 release notes from Red Hat): > > [rhel-x86_64-server-6] > priority=1 > [rhel-x86_64-server-6-ost-4] > priority=1 > > If you're using subscription manager, I'd have to do a bit more looking > around (a quick check to see if editing > /etc/yum/pluginconf.d/subscription-manager.conf in the same way as RHN > Classic didn't appear to work for me). However, with both RHN Classic > and CDN/subscription-manager, the following should work (with no > configuration editing): > > yum update --disablerepo= > > E.g.: > > yum update --disablerepo=epel > > -- Lon > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmyers at redhat.com Thu Jan 30 03:51:21 2014 From: pmyers at redhat.com (Perry Myers) Date: Wed, 29 Jan 2014 22:51:21 -0500 Subject: [rhos-list] Redhat RHEL Openstack 4.0 - Patch updates In-Reply-To: References: <52E94AC0.6070208@redhat.com> <52E971C7.3020301@redhat.com> Message-ID: <52E9CC39.2000407@redhat.com> On 01/29/2014 10:30 PM, John Van Haastert wrote: > Thanks Lon, > > I have tried initially to use subscription manager but have since settle > back on RHN Classic using *rhn_register.* > > I have install RDO packstack havana for now and RHN Classic Web is > showing critical Openstack updates but I am now assuming those updates > are specific to Red Hat Openstack 4 Channel deployment. Is this correct ? I'll let Lon answer the more detailed question, but just to take a step back... Why are you using RDO and RHEL OSP on the same machine? It's not supported/intended to mix the upstream community release packages with the supported packages. For example, you don't want to be using the upstream RDO, Foreman or Puppetlabs repositories on a machine that you're using for RHOS, since the RHOS 4 repository contains the specific Ruby, Puppet and Foreman RPMs that we ship and support. If you have a mixed environment containing dependencies from both the product and community repositories, that will present support issues. In fact, some of the issues you are seeing right now could be possibly due to mixing the product and community repositories. Can you replicate the issues you are seeing on a machine with ONLY the RHEL OSP official repositories present? > > *yum repolist* > * > *Loaded plugins: priorities, product-id, rhnplugin, security, > subscription-manager > This system is receiving updates from Red Hat Subscription Management. > This system is receiving updates from RHN Classic or RHN Satellite. > epel/metalink > > | 8.7 kB 00:00 > epel > > | 4.2 kB 00:00 > epel/primary_db > > | 5.9 MB 00:02 > foreman > > | 2.9 kB 00:00 > foreman-plugins > > | 3.7 kB 00:00 > *openstack-havana * > > | 2.9 kB 00:00 > puppetlabs-deps > > | 1.9 kB 00:00 > puppetlabs-products > > | 1.9 kB 00:00 > puppetlabs-products/primary_db > > | 105 kB 00:00 > rhel-6-server-cf-tools-1-rpms > > | 2.8 kB 00:00 > rhel-6-server-rhev-agent-rpms > > | 3.1 kB 00:00 > *rhel-6-server-rpms* > > | 3.7 kB 00:00 > rhel-lb-for-rhel-6-server-rpms > > | 3.7 kB 00:00 > *rhel-x86_64-server-6-ost-4 * > > | 1.6 kB 00:00 > *rhel-x86_64-server-optional-6 * > > | 1.8 kB 00:00 > *1515 packages excluded due to repository priority protections* > repo id repo > name > status > epel > Extra Packages for Enterprise Linux 6 - x86_64 > 10,328+69 > foreman > Foreman stable > 215 > foreman-plugins > Foreman stable - plugins > 42 > *openstack-havana > OpenStack Havana Repository * > 563+155 > puppetlabs-deps > Puppet Labs Dependencies El 6 - x86_64 > 54 > puppetlabs-products > Puppet Labs Products El 6 - x86_64 > 327 > rhel-6-server-cf-tools-1-rpms Red > Hat CloudForms Tools for RHEL 6 (RPMs) > 30+1 > rhel-6-server-rhev-agent-rpms Red > Hat Enterprise Virtualization Agents for RHEL 6 Server (RPMs) > 36 > rhel-6-server-rpms Red > Hat Enterprise Linux 6 Server (RPMs) > 11,622+572 > rhel-lb-for-rhel-6-server-rpms Red > Hat Enterprise Linux Load Balancer (for RHEL 6 Server) (RPMs) > 14 > *rhel-x86_64-server-6 * > * Red Hat Enterprise Linux Server (v. 6 for 64-bit x86_64) * > 11,617+566 > *rhel-x86_64-server-6-ost-4 Red > Hat OpenStack 4.0 * > 323+192 > *rhel-x86_64-server-optional-6* > *RHEL Server Optional (v. 6 64-bit x86_64) * > 6,823+115 > repolist: 41,994 > > > *cat /etc/yum/pluginconf.d/rhnplugin.conf * > [main] > enabled = 1 > gpgcheck = 1 > timeout = 120 > *cat **/etc/yum/pluginconf.d/**priorities.conf * > [main] > enabled = 1 > cat */etc/yum/pluginconf.d/subscription-manager.conf * > [main] > enabled=1 > cat */etc/yum/pluginconf.d/product-id.conf * > [main] > enabled=1 > cat */etc/yum/pluginconf.d/security.conf * > [main] > enabled=1 > > Type Advisory Synopsis Status Updated > [Security Advisory] RHSA-2014:0089 > > Moderate: openstack-keystone security and bug fix update Failed > 1/22/14 > [Bug Fix Advisory] RHBA-2014:0046 > Red Hat > Enterprise Linux OpenStack Platform 4 Bug Fix and Enhancement > Advisory None 1/22/14 > [Security Advisory] RHSA-2014:0090 > > Moderate: openstack-heat security, bug fix, and enhancement update > Failed > 1/22/14 > [Security Advisory] RHSA-2014:0091 > > Moderate: openstack-neutron security, bug fix, and enhancement update > Failed > 1/22/14 > [Product Enhancement Advisory] RHEA-2013:1859 > Red Hat > Enterprise Linux OpenStack Platform Enhancement Advisory None 12/20/13 > > > sunserver2.cyanoptics.com > > 1/29/14 2:22:31 AM EET *Error while executing packages action: empty > transaction [[6]]* > > > Assuming given the above /etc/yum/pluginconf.d/ files the enabled=1 is > preventing these updates. > > Thanks again Lon just wanted a sanity check. > > ?Johnvh > > On Jan 29, 2014, at 1:25 PM, Lon Hohberger > wrote: > >> On 01/29/2014 01:38 PM, Perry Myers wrote: >>> On 28/01/14 17:00, John Van Haastert wrote: >>>> Recommendation for the best way to get the RedHat updates for >>>> Openstack 4.0 channel subscription. Is it just a matter of changing >>>> the /etc/yum/pluginconf/rhnplugin.conf ?enabled = 1? to ?enabled = 0? >>>> and then run "sudo yum update? ? >>>> >>>> Currently ?yum update? is showing 942 packages excluded due to >>>> repository priority protections. Want to make sure that I get >>>> updates specific to the RedHat Openstack 4.0 channel subscription ( >>>> i.e. RHEL 6.5 - Havanan). The RedHat Classic Subscription Management >>>> has a several Openstack Updates is the above the correct way of >>>> getting these OpenStack 4.0 updates ? >>>> >>>> Thanks in advance. >>> >>> Lon or Bryan, can you assist with this question? >>> >> >> Once subscribed to RHN, /etc/yum/pluginconf/rhnplugin.conf's "enabled" >> attribute will be 1 (as you guessed), but merely changing it is not >> likely to have the desired effect. >> >> It sounds as though the system isn't using RHN classic - is that right? >> If so, you'll need to register with RHN. Subscribing a system to RHN >> Classic can be accomplished using the rhn_register utility. >> >> The RHEL OpenStack Platform 4 release notes detail which channels to >> subscribe to (or disable) in section 2.3.2 for RHN classic and 2.3.1 for >> subscription-manager (CDN): >> >> >> https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/4/pdf/Release_Notes/Red_Hat_Enterprise_Linux_OpenStack_Platform-4-Release_Notes-en-US.pdf >> >> Also, when you run 'yum update', it will tell you which repository a >> given package is coming from. If you have additional repositories, such >> as EPEL, installed, certain packages from these repositories may try to >> replace the supported ones from Red Hat. >> >> A quick way to work around this is to uninstall the third party >> repositories, but if you don't want to do this... >> >> If you're using RHN Classic, I think you can give priorities to each >> channel over other repositories on the system. Edit >> /etc/yum/pluginconf/rhnplugin.conf and priorities for each of the >> channels you really don't want other repositories to override (channel >> names can be found in 2.3.2 of the OpenStack 4 release notes from Red >> Hat): >> >> [rhel-x86_64-server-6] >> priority=1 >> [rhel-x86_64-server-6-ost-4] >> priority=1 >> >> If you're using subscription manager, I'd have to do a bit more looking >> around (a quick check to see if editing >> /etc/yum/pluginconf.d/subscription-manager.conf in the same way as RHN >> Classic didn't appear to work for me). However, with both RHN Classic >> and CDN/subscription-manager, the following should work (with no >> configuration editing): >> >> yum update --disablerepo= >> >> E.g.: >> >> yum update --disablerepo=epel >> >> -- Lon >> >> > > > > _______________________________________________ > rhos-list mailing list > rhos-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhos-list > From johnvh24 at hotmail.com Thu Jan 30 05:21:12 2014 From: johnvh24 at hotmail.com (John Van Haastert) Date: Wed, 29 Jan 2014 21:21:12 -0800 Subject: [rhos-list] Redhat RHEL Openstack 4.0 - Patch updates In-Reply-To: <52E9CC39.2000407@redhat.com> References: <52E94AC0.6070208@redhat.com> <52E971C7.3020301@redhat.com> <52E9CC39.2000407@redhat.com> Message-ID: I will start over. Was not sure if packstack was available via RHOS. Thanks, -Johnvh > On Jan 29, 2014, at 7:51 PM, Perry Myers wrote: > >> On 01/29/2014 10:30 PM, John Van Haastert wrote: >> Thanks Lon, >> >> I have tried initially to use subscription manager but have since settle >> back on RHN Classic using *rhn_register.* >> >> I have install RDO packstack havana for now and RHN Classic Web is >> showing critical Openstack updates but I am now assuming those updates >> are specific to Red Hat Openstack 4 Channel deployment. Is this correct ? > > I'll let Lon answer the more detailed question, but just to take a step > back... > > Why are you using RDO and RHEL OSP on the same machine? It's not > supported/intended to mix the upstream community release packages with > the supported packages. > > For example, you don't want to be using the upstream RDO, Foreman or > Puppetlabs repositories on a machine that you're using for RHOS, since > the RHOS 4 repository contains the specific Ruby, Puppet and Foreman > RPMs that we ship and support. > > If you have a mixed environment containing dependencies from both the > product and community repositories, that will present support issues. > > In fact, some of the issues you are seeing right now could be possibly > due to mixing the product and community repositories. > > Can you replicate the issues you are seeing on a machine with ONLY the > RHEL OSP official repositories present? > >> >> *yum repolist* >> * >> *Loaded plugins: priorities, product-id, rhnplugin, security, >> subscription-manager >> This system is receiving updates from Red Hat Subscription Management. >> This system is receiving updates from RHN Classic or RHN Satellite. >> epel/metalink > From sclewis at redhat.com Thu Jan 30 21:33:23 2014 From: sclewis at redhat.com (Scott Lewis) Date: Thu, 30 Jan 2014 16:33:23 -0500 (EST) Subject: [rhos-list] RHOS 3.0 Bugfix update 4 is Live! In-Reply-To: <280902900.11272870.1391117165106.JavaMail.root@redhat.com> Message-ID: <958149977.11274531.1391117603617.JavaMail.root@redhat.com> The Red Hat OpenStack team has successfully released a bugfix update to its OpenStack 3.0 "Grizzly" offering, available via the Red Hat Enterprise Linux OpenStack Platform (RHEL-OSP) [1] and Red Hat Cloud Infrastructure [2] products. This is the fourth update provided to the major release, since its general availability on 10 Jul 2013. Additional updates will continue to be provided via planned bugfix releases, and asynchronous updates for important bugs, issues, vulnerabilities, and customer cases until its planned End Of Life on 31 Jul 2014 [3]. Congratulations to all the teams and individuals, upstream and downstream, that made this release possible while continuing to provide updates for RHEL-OSP 4 "Havana", and creating the upcoming RHEL-OSP 5 "Icehouse" version. This release includes selected bugfixes, customer issues, features and security updates. This release also serves to provide hardening, stability and functionality by validating additional upstream bugs, and providing updates to RHEL OSP documentation. Errata: - Main bugfix advisory: http://rhn.redhat.com/errata/RHBA-2014-0110.html - Nova security advisory: http://rhn.redhat.com/errata/RHSA-2014-0112.html - Keystone security advisory: http://rhn.redhat.com/errata/RHSA-2014-0113.html - sos-plugin enhancement: http://rhn.redhat.com/errata/RHEA-2014-0111.html - augeas bugfix advisory: http://rhn.redhat.com/errata/RHBA-2014-0114.html Documentation is available at: https://access.redhat.com/site/documentation/Red_Hat_Enterprise_Linux_OpenStack_Platform/ - Technical notes: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/3/html/Technical_Notes/index.html RHOS 3.0 Async 4 will rely on RHEL 6.5. Optionally, MRG-M and RHEL LB can be enabled for use in certain configurations. Issues fixed for this release: openstack-nova 6 openstack-quantum 3 openstack-ceilometer 2 openstack-cinder 2 sos-plugins-openstack 2 openstack-glance 1 openstack-heat 1 openstack-keystone 1 python-django-horizon 1 ------------------------- Total Result 19 [1] https://www.redhat.com/products/enterprise-linux/openstack-platform/ [2] http://www.redhat.com/products/cloud-computing/cloud-infrastructure/ [3] https://access.redhat.com/site/support/policy/updates/openstack/platform/ Thanks, Scott Scott Lewis Engineering Program Manager Red Hat OpenStack Office: 919-754-4228 sclewis at redhat.com From pmyers at redhat.com Thu Jan 30 21:39:29 2014 From: pmyers at redhat.com (Perry Myers) Date: Thu, 30 Jan 2014 16:39:29 -0500 Subject: [rhos-list] Redhat RHEL Openstack 4.0 - Patch updates In-Reply-To: References: <52E94AC0.6070208@redhat.com> <52E971C7.3020301@redhat.com> <52E9CC39.2000407@redhat.com> Message-ID: <52EAC691.70505@redhat.com> On 01/30/2014 12:21 AM, John Van Haastert wrote: > I will start over. Was not sure if packstack was available via RHOS. Yep. packstack is definitely shipped with RHOS. Thanks :) Perry From lhh at redhat.com Fri Jan 31 14:01:55 2014 From: lhh at redhat.com (Lon Hohberger) Date: Fri, 31 Jan 2014 09:01:55 -0500 Subject: [rhos-list] Redhat RHEL Openstack 4.0 - Patch updates In-Reply-To: References: <52E94AC0.6070208@redhat.com> <52E971C7.3020301@redhat.com> Message-ID: <52EBACD3.7080701@redhat.com> On 01/29/2014 10:30 PM, John Van Haastert wrote: > Thanks Lon, > > I have tried initially to use subscription manager but have since settle > back on RHN Classic using *rhn_register.* Ok! > I have install RDO packstack havana for now and RHN Classic Web is > showing critical Openstack updates but I am now assuming those updates > are specific to Red Hat Openstack 4 Channel deployment. Is this correct ? The updates shown in RHN Classic's web UI will be specific to channels to which your machine is subscribed and will not report about additional software such as RDO. So, the updates would be from the ROSP 4 channel or RHEL 6 channel, etc. If you're using RDO, you could disable the OpenStack 4 channel to avoid conflicts. Or, you could disable RDO, reconfigure, and use the OpenStack 4 channel :] -- Lon From johnvh24 at hotmail.com Fri Jan 31 19:45:12 2014 From: johnvh24 at hotmail.com (John Van Haastert) Date: Fri, 31 Jan 2014 11:45:12 -0800 Subject: [rhos-list] Redhat RHEL Openstack 4.0 - Patch updates In-Reply-To: <52EAC691.70505@redhat.com> References: <52E94AC0.6070208@redhat.com> <52E971C7.3020301@redhat.com> <52E9CC39.2000407@redhat.com> <52EAC691.70505@redhat.com> Message-ID: Thanks Perry, Okay have removed the RDO repo and installed packstack from the RHOS 4.0 repo and updates are getting updated. Is there an equivalent RHOS script like the rod bighammer to uninstall packstack from RHOS deployment or is bighammer script fine to remove RHOS 4.0 packtstack as well ? ?Johnvh On Jan 30, 2014, at 1:39 PM, Perry Myers wrote: > On 01/30/2014 12:21 AM, John Van Haastert wrote: >> I will start over. Was not sure if packstack was available via RHOS. > > Yep. packstack is definitely shipped with RHOS. > > Thanks :) > > Perry > From pmyers at redhat.com Fri Jan 31 23:17:07 2014 From: pmyers at redhat.com (Perry Myers) Date: Fri, 31 Jan 2014 18:17:07 -0500 Subject: [rhos-list] Redhat RHEL Openstack 4.0 - Patch updates In-Reply-To: References: <52E94AC0.6070208@redhat.com> <52E971C7.3020301@redhat.com> <52E9CC39.2000407@redhat.com> <52EAC691.70505@redhat.com> Message-ID: <52EC2EF3.2000602@redhat.com> On 01/31/2014 02:45 PM, John Van Haastert wrote: > Thanks Perry, > > Okay have removed the RDO repo and installed packstack from the RHOS 4.0 repo and updates are getting updated. > > Is there an equivalent RHOS script like the rod bighammer to uninstall packstack from RHOS deployment or is bighammer script fine to remove RHOS 4.0 packtstack as well ? I'm not familiar with rod bighammer, so I may need to defer to someone else on the list who is. I think our formal docs cover uninstallation. /me checks... https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/4/html/Getting_Started_Guide/appe-Getting_Started_Guide-Removing_PackStack_Deployments.html Yep, for RHOS I think that is the script you should be running. Perry