Staypuft openstack deploy fails with yum @core group missing

Support
1

I get this error from anaconda on my controller host, during the package
install phase (I can't copy/paste from the console, but I can post a
screenshot if somebody needs the whole traceback):

in anaconda yumpayload.py in _selectYumGroup
…
NoSuchGroup: core

I'm pretty sure this is from the following snippet in the kickstart
provisioning template:

[snip]
%packages --ignoremissing
yum
dhclient
ntp
wget
@Core
epel-release
[snip]

Anybody run into this before, or have any ideas or hints for debugging?

Thanks in advance-

John

2

I thought I might be able to work around the lack of the core group by
replacing it manually with the list of packages that it contains. As a
first step, I removed the "@Core" package from the %packages directive in
the kickstart file, and I still get the same error. Now I'm really
stumped…

··· On Mon, Sep 8, 2014 at 12:40 PM, John Hazen wrote:

I get this error from anaconda on my controller host, during the package
install phase (I can’t copy/paste from the console, but I can post a
screenshot if somebody needs the whole traceback):

in anaconda yumpayload.py in _selectYumGroup
…
NoSuchGroup: core

I’m pretty sure this is from the following snippet in the kickstart
provisioning template:

[snip]
%packages --ignoremissing
yum
dhclient
ntp
wget
@Core
epel-release
[snip]

Anybody run into this before, or have any ideas or hints for debugging?

Thanks in advance-

John

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/o0Lwtam1CzI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

3

What media are you using? If it's local media make sure you have comps.xml
with the core group, e.g:

grep "<id>core"
/var/www/html/repos/released/RHEL-7/7.0/Server/x86_64/os/Packages/comps.xml
<id>core</id>

I had to use "createrepo -g" using the comps.xml and the directory where I
copied the contents of my RHEL 7 ISO otherwise I get the same error during
deployment.

Ramon

··· On Monday, 8 September 2014 20:40:30 UTC+1, John Hazen wrote: > > I get this error from anaconda on my controller host, during the package > install phase (I can't copy/paste from the console, but I can post a > screenshot if somebody needs the whole traceback): > > in anaconda yumpayload.py in _selectYumGroup > ... > NoSuchGroup: core > > I'm pretty sure this is from the following snippet in the kickstart > provisioning template: > > [snip] > %packages --ignoremissing > yum > dhclient > ntp > wget > @Core > epel-release > [snip] > > Anybody run into this before, or have any ideas or hints for debugging? > > Thanks in advance- > > John >
4

John,

Don't know about the @core, but I have seen that the puppet modules and
epel repo were not installed in my Centos 7 boxes using staypuft. The boxes
would reboot and puppet was nowhere to be found. I traced the error back to
the portion of the kickstart that you are making reference and I ended up I
circunventing this issue by adding the following code into the %POST
section of the kickstart default file:

Install puppet and epel

yum -y localinstall
http://mirror.centos.org/centos/7/extras/x86_64/Packages/epel-release-7-2.noarch.rpm
yum -y localinstall
http://yum.puppetlabs.com/puppetlabs-release-el-7.noarch.rpm
yum -y update
yum -y install puppet

You might want to try doing something similar with the @Core modules.

The other way to test this out is by removing the --ignoremissing from
%packages and see the console error when reaching the @Core portion

IB

··· On Monday, September 8, 2014 5:11:37 PM UTC-4, John Hazen wrote: > > I thought I might be able to work around the lack of the core group by > replacing it manually with the list of packages that it contains. As a > first step, I removed the "@Core" package from the %packages directive in > the kickstart file, and I still get the same error. Now I'm really > stumped... > > > On Mon, Sep 8, 2014 at 12:40 PM, John Hazen <jo...@hazen.net > > wrote: > >> I get this error from anaconda on my controller host, during the package >> install phase (I can't copy/paste from the console, but I can post a >> screenshot if somebody needs the whole traceback): >> >> in anaconda yumpayload.py in _selectYumGroup >> ... >> NoSuchGroup: core >> >> I'm pretty sure this is from the following snippet in the kickstart >> provisioning template: >> >> [snip] >> %packages --ignoremissing >> yum >> dhclient >> ntp >> wget >> @Core >> epel-release >> [snip] >> >> Anybody run into this before, or have any ideas or hints for debugging? >> >> Thanks in advance- >> >> John >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Foreman users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/foreman-users/o0Lwtam1CzI/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > >
5

Thanks, Ramon!

That is exactly the root of the error. I found it yesterday, (would have
found it sooner, but I didn't notice that google was rewriting my search)
but didn't update because I was still stuck on a different part of the
provision.

··· On Wed, Sep 10, 2014 at 1:47 AM, Ramon Acedo wrote:

What media are you using? If it’s local media make sure you have comps.xml
with the core group, e.g:

grep “core”
/var/www/html/repos/released/RHEL-7/7.0/Server/x86_64/os/Packages/comps.xml
core

I had to use “createrepo -g” using the comps.xml and the directory where I
copied the contents of my RHEL 7 ISO otherwise I get the same error during
deployment.

Ramon

On Monday, 8 September 2014 20:40:30 UTC+1, John Hazen wrote:

I get this error from anaconda on my controller host, during the package
install phase (I can’t copy/paste from the console, but I can post a
screenshot if somebody needs the whole traceback):

in anaconda yumpayload.py in _selectYumGroup
…
NoSuchGroup: core

I’m pretty sure this is from the following snippet in the kickstart
provisioning template:

[snip]
%packages --ignoremissing
yum
dhclient
ntp
wget
@Core
epel-release
[snip]

Anybody run into this before, or have any ideas or hints for debugging?

Thanks in advance-

John

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/o0Lwtam1CzI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

6

Unfortunately, the install fails before it gets to the %POST section, so I
don't think I can fix it with commands in POST.

I'm about to give up on staypuft. Very frustrating.

I think the one option I have now is to try to get it working with an ISO
install over PXE, because it's clear that the initrd doesn't have enough
stuff on it to be useful.

Or, if that doesn't work, maybe I'll just try to re-install everything from
scratch.

argh…

··· On Monday, September 8, 2014 3:17:53 PM UTC-7, Ignacio Bravo wrote: > > John, > > Don't know about the @core, but I have seen that the puppet modules and > epel repo were not installed in my Centos 7 boxes using staypuft. The boxes > would reboot and puppet was nowhere to be found. I traced the error back to > the portion of the kickstart that you are making reference and I ended up I > circunventing this issue by adding the following code into the %POST > section of the kickstart default file: > > # Install puppet and epel > yum -y localinstall > http://mirror.centos.org/centos/7/extras/x86_64/Packages/epel-release-7-2.noarch.rpm > yum -y localinstall > http://yum.puppetlabs.com/puppetlabs-release-el-7.noarch.rpm > yum -y update > yum -y install puppet > > You might want to try doing something similar with the @Core modules. > > The other way to test this out is by removing the --ignoremissing from > %packages and see the console error when reaching the @Core portion > > IB > > > > On Monday, September 8, 2014 5:11:37 PM UTC-4, John Hazen wrote: >> >> I thought I might be able to work around the lack of the core group by >> replacing it manually with the list of packages that it contains. As a >> first step, I removed the "@Core" package from the %packages directive in >> the kickstart file, and I still get the same error. Now I'm really >> stumped... >> >> >> On Mon, Sep 8, 2014 at 12:40 PM, John Hazen wrote: >> >>> I get this error from anaconda on my controller host, during the package >>> install phase (I can't copy/paste from the console, but I can post a >>> screenshot if somebody needs the whole traceback): >>> >>> in anaconda yumpayload.py in _selectYumGroup >>> ... >>> NoSuchGroup: core >>> >>> I'm pretty sure this is from the following snippet in the kickstart >>> provisioning template: >>> >>> [snip] >>> %packages --ignoremissing >>> yum >>> dhclient >>> ntp >>> wget >>> @Core >>> epel-release >>> [snip] >>> >>> Anybody run into this before, or have any ideas or hints for debugging? >>> >>> Thanks in advance- >>> >>> John >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Foreman users" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/foreman-users/o0Lwtam1CzI/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> foreman-user...@googlegroups.com. >>> To post to this group, send email to forema...@googlegroups.com. >>> Visit this group at http://groups.google.com/group/foreman-users. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >>
7

I'm sorry for your frustration. Frankly, we don't support CentOS and people
run it on this platform mostly for development. We do not test deployment on
CentOS thoroughly atm. Could you please share more information about your
setup? Is that CentOS 6 that you use for staypuft? Staypuft and staypuft-
installer versions? What workarounds did you apply (e.g. installation media)?
What's your networking layout and configuration?

Quick search for no @core issue brought some BZs with livecd install so it
does not help much. I haven't seen this error so I wonder what's different in
you case.

··· -- Marek

On Tuesday 09 of September 2014 11:44:40 John Hazen wrote:

Unfortunately, the install fails before it gets to the %POST section, so I
don’t think I can fix it with commands in POST.

I’m about to give up on staypuft. Very frustrating.

I think the one option I have now is to try to get it working with an ISO
install over PXE, because it’s clear that the initrd doesn’t have enough
stuff on it to be useful.

Or, if that doesn’t work, maybe I’ll just try to re-install everything from
scratch.

argh…

On Monday, September 8, 2014 3:17:53 PM UTC-7, Ignacio Bravo wrote:

John,

Don’t know about the @core, but I have seen that the puppet modules and
epel repo were not installed in my Centos 7 boxes using staypuft. The
boxes
would reboot and puppet was nowhere to be found. I traced the error back
to
the portion of the kickstart that you are making reference and I ended up
I
circunventing this issue by adding the following code into the %POST
section of the kickstart default file:

Install puppet and epel

yum -y localinstall
http://mirror.centos.org/centos/7/extras/x86_64/Packages/epel-release-7-2.
noarch.rpm yum -y localinstall
http://yum.puppetlabs.com/puppetlabs-release-el-7.noarch.rpm
yum -y update
yum -y install puppet

You might want to try doing something similar with the @Core modules.

The other way to test this out is by removing the --ignoremissing from
%packages and see the console error when reaching the @Core portion

IB

On Monday, September 8, 2014 5:11:37 PM UTC-4, John Hazen wrote:

I thought I might be able to work around the lack of the core group by
replacing it manually with the list of packages that it contains. As a
first step, I removed the “@Core” package from the %packages directive in
the kickstart file, and I still get the same error. Now I’m really
stumped…

On Mon, Sep 8, 2014 at 12:40 PM, John Hazen jo...@hazen.net wrote:

I get this error from anaconda on my controller host, during the package
install phase (I can’t copy/paste from the console, but I can post a
screenshot if somebody needs the whole traceback):

in anaconda yumpayload.py in _selectYumGroup
…
NoSuchGroup: core

I’m pretty sure this is from the following snippet in the kickstart
provisioning template:

[snip]
%packages --ignoremissing
yum
dhclient
ntp
wget
@Core
epel-release
[snip]

Anybody run into this before, or have any ideas or hints for debugging?

Thanks in advance-

John

–
Marek

8

Hi Marek-

Good (I guess) to know that CentOS isn't supported, or even tested. That
would explain the level of work I am having to do to make it work.

I have gotten past the @core problem, and now am stuck getting boot up to
work after the reboot. I'll post more about that if I can't figure it out
in a few hours.

··· On Wed, Sep 10, 2014 at 12:49 AM, Marek Hulan wrote:

I’m sorry for your frustration. Frankly, we don’t support CentOS and people
run it on this platform mostly for development. We do not test deployment
on
CentOS thoroughly atm. Could you please share more information about your
setup? Is that CentOS 6 that you use for staypuft? Staypuft and staypuft-
installer versions? What workarounds did you apply (e.g. installation
media)?
What’s your networking layout and configuration?

Quick search for no @core issue brought some BZs with livecd install so it
does not help much. I haven’t seen this error so I wonder what’s different
in
you case.

–
Marek

On Tuesday 09 of September 2014 11:44:40 John Hazen wrote:

Unfortunately, the install fails before it gets to the %POST section, so
I
don’t think I can fix it with commands in POST.

I’m about to give up on staypuft. Very frustrating.

I think the one option I have now is to try to get it working with an ISO
install over PXE, because it’s clear that the initrd doesn’t have enough
stuff on it to be useful.

Or, if that doesn’t work, maybe I’ll just try to re-install everything
from
scratch.

argh…

On Monday, September 8, 2014 3:17:53 PM UTC-7, Ignacio Bravo wrote:

John,

Don’t know about the @core, but I have seen that the puppet modules and
epel repo were not installed in my Centos 7 boxes using staypuft. The
boxes
would reboot and puppet was nowhere to be found. I traced the error
back

to
the portion of the kickstart that you are making reference and I ended
up

I
circunventing this issue by adding the following code into the %POST
section of the kickstart default file:

Install puppet and epel

yum -y localinstall

http://mirror.centos.org/centos/7/extras/x86_64/Packages/epel-release-7-2.

noarch.rpm yum -y localinstall
http://yum.puppetlabs.com/puppetlabs-release-el-7.noarch.rpm
yum -y update
yum -y install puppet

You might want to try doing something similar with the @Core modules.

The other way to test this out is by removing the --ignoremissing from
%packages and see the console error when reaching the @Core portion

IB

On Monday, September 8, 2014 5:11:37 PM UTC-4, John Hazen wrote:

I thought I might be able to work around the lack of the core group by
replacing it manually with the list of packages that it contains. As
a

first step, I removed the “@Core” package from the %packages
directive in

the kickstart file, and I still get the same error. Now I’m really
stumped…

On Mon, Sep 8, 2014 at 12:40 PM, John Hazen jo...@hazen.net wrote:

I get this error from anaconda on my controller host, during the
package

install phase (I can’t copy/paste from the console, but I can post a
screenshot if somebody needs the whole traceback):

in anaconda yumpayload.py in _selectYumGroup
…
NoSuchGroup: core

I’m pretty sure this is from the following snippet in the kickstart
provisioning template:

[snip]
%packages --ignoremissing
yum
dhclient
ntp
wget
@Core
epel-release
[snip]

Anybody run into this before, or have any ideas or hints for
debugging?

Thanks in advance-

John

–
Marek

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/o0Lwtam1CzI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.