VPC subnets not correct in Foreman

Hello all,

I have a VPC built with Cloud Formation with a 10.x/16 network cut up into
/26 networks for spreading out across the AZs. So x.0/26 is for 1a, x.64/26
is 1b and x.128/26 for 1c. We also have a number of /26 subnets for ELBs.
Foreman only shows 1number /26 network and that isn't even in my Cloud
Formation template, the rest of them it is showing are showing are /24 and
/27 networks and many of those start with 15.x. The correct Subnets are
showing in the AWS console.

The Foreman instance (1.3-rc3 is inside the VPC with SG rules to allow it
to pull packages and talk to the AWS api. It is new installer based and
other than templates and setting based Ohad's post is unmodified.

Has anyone seen this behaviour and help shed a light on what is happening?

Jim

Should I be raising this as a bug, because if this is reproducible it means
VPC support in Foreman-1.3 is broken?

Jim

··· On 8 October 2013 09:30, James Bailey wrote:

Hello all,

I have a VPC built with Cloud Formation with a 10.x/16 network cut up into
/26 networks for spreading out across the AZs. So x.0/26 is for 1a, x.64/26
is 1b and x.128/26 for 1c. We also have a number of /26 subnets for ELBs.
Foreman only shows 1number /26 network and that isn’t even in my Cloud
Formation template, the rest of them it is showing are showing are /24 and
/27 networks and many of those start with 15.x. The correct Subnets are
showing in the AWS console.

The Foreman instance (1.3-rc3 is inside the VPC with SG rules to allow it
to pull packages and talk to the AWS api. It is new installer based and
other than templates and setting based Ohad’s post is unmodified.

Has anyone seen this behaviour and help shed a light on what is happening?

Jim

Yes please. I only tested it with a very simple VPC setup, so hard for
me to shed any light on it.

You could try getting information out of Fog using the Rails console
about which subnets it's aware of. Which OS are you on?

··· -- Dominic Cleal Red Hat Engineering

On 08/10/13 12:11, James Bailey wrote:

Should I be raising this as a bug, because if this is reproducible it
means VPC support in Foreman-1.3 is broken?

Jim

On 8 October 2013 09:30, James Bailey <paradoxbound@gmail.com > mailto:paradoxbound@gmail.com> wrote:

Hello all,

I have a VPC built with Cloud Formation with a 10.x/16 network cut
up into /26 networks for spreading out across the AZs. So x.0/26 is
for 1a, x.64/26 is 1b and x.128/26 for 1c. We also have a number of
/26 subnets for ELBs. Foreman only shows 1number /26 network and
that isn't even in my Cloud Formation template, the rest of them it
is showing are showing are /24 and /27 networks and many of those
start with 15.x. The correct Subnets are showing in the AWS console.

The Foreman instance (1.3-rc3 is inside the VPC with SG rules to
allow it to pull packages and talk to the AWS api. It is new
installer based and other than templates and setting based Ohad's
post is unmodified.

Has anyone seen this behaviour and help shed a light on what is
happening?

Jim


You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, 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/groups/opt_out.

Running CentOS-6.4 and Foreman-1.3-rc3.

I am happy to try and get a rails console up and running and share the
output but I have never used one before, sorry more admin than dev.
However if someone can spare a few minutes to help me get going I will do
what I can.

Jim

··· On 8 October 2013 13:10, Dominic Cleal wrote:

Yes please. I only tested it with a very simple VPC setup, so hard for
me to shed any light on it.

You could try getting information out of Fog using the Rails console
about which subnets it’s aware of. Which OS are you on?


Dominic Cleal
Red Hat Engineering

On 08/10/13 12:11, James Bailey wrote:

Should I be raising this as a bug, because if this is reproducible it
means VPC support in Foreman-1.3 is broken?

Jim

On 8 October 2013 09:30, James Bailey <paradoxbound@gmail.com > > mailto:paradoxbound@gmail.com> wrote:

Hello all,

I have a VPC built with Cloud Formation with a 10.x/16 network cut
up into /26 networks for spreading out across the AZs. So x.0/26 is
for 1a, x.64/26 is 1b and x.128/26 for 1c. We also have a number of
/26 subnets for ELBs. Foreman only shows 1number /26 network and
that isn't even in my Cloud Formation template, the rest of them it
is showing are showing are /24 and /27 networks and many of those
start with 15.x. The correct Subnets are showing in the AWS console.

The Foreman instance (1.3-rc3 is inside the VPC with SG rules to
allow it to pull packages and talk to the AWS api. It is new
installer based and other than templates and setting based Ohad's
post is unmodified.

Has anyone seen this behaviour and help shed a light on what is
happening?

Jim


You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, 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/groups/opt_out.


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, 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/groups/opt_out.

Sorry should have added that I am about on irc @paradoxbound

Jim

··· On 8 October 2013 13:24, James Bailey wrote:

Running CentOS-6.4 and Foreman-1.3-rc3.

I am happy to try and get a rails console up and running and share the
output but I have never used one before, sorry more admin than dev.
However if someone can spare a few minutes to help me get going I will do
what I can.

Jim

On 8 October 2013 13:10, Dominic Cleal dcleal@redhat.com wrote:

Yes please. I only tested it with a very simple VPC setup, so hard for
me to shed any light on it.

You could try getting information out of Fog using the Rails console
about which subnets it’s aware of. Which OS are you on?


Dominic Cleal
Red Hat Engineering

On 08/10/13 12:11, James Bailey wrote:

Should I be raising this as a bug, because if this is reproducible it
means VPC support in Foreman-1.3 is broken?

Jim

On 8 October 2013 09:30, James Bailey <paradoxbound@gmail.com >> > mailto:paradoxbound@gmail.com> wrote:

Hello all,

I have a VPC built with Cloud Formation with a 10.x/16 network cut
up into /26 networks for spreading out across the AZs. So x.0/26 is
for 1a, x.64/26 is 1b and x.128/26 for 1c. We also have a number of
/26 subnets for ELBs. Foreman only shows 1number /26 network and
that isn't even in my Cloud Formation template, the rest of them it
is showing are showing are /24 and /27 networks and many of those
start with 15.x. The correct Subnets are showing in the AWS console.

The Foreman instance (1.3-rc3 is inside the VPC with SG rules to
allow it to pull packages and talk to the AWS api. It is new
installer based and other than templates and setting based Ohad's
post is unmodified.

Has anyone seen this behaviour and help shed a light on what is
happening?

Jim


You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, 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/groups/opt_out.


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, 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/groups/opt_out.

In that case, first install "foreman-console", then run:

cd ~foreman && sudo -u foreman scl enable ruby193 'RAILS_ENV=production
rails c'

then at the console, replacing with your compute resource name, try:

2.0.0p247 :030 > ComputeResource.find_by_name("your CR name").subnets
=> <Fog::Compute::AWS::Subnets
filters={}
[]
>

It should list all of the subnet info from AWS, it'll be interesting to
compare it to what you expect to list.

··· -- Dominic Cleal Red Hat Engineering

On 08/10/13 13:24, James Bailey wrote:

Running CentOS-6.4 and Foreman-1.3-rc3.

I am happy to try and get a rails console up and running and share the
output but I have never used one before, sorry more admin than dev.
However if someone can spare a few minutes to help me get going I will
do what I can.

Jim

On 8 October 2013 13:10, Dominic Cleal <dcleal@redhat.com > mailto:dcleal@redhat.com> wrote:

Yes please.  I only tested it with a very simple VPC setup, so hard for
me to shed any light on it.

You could try getting information out of Fog using the Rails console
about which subnets it's aware of.  Which OS are you on?

--
Dominic Cleal
Red Hat Engineering

On 08/10/13 12:11, James Bailey wrote:
> Should I be raising this as a bug, because if this is reproducible it
> means VPC support in Foreman-1.3 is broken?
>
> Jim
>
>
> On 8 October 2013 09:30, James Bailey <paradoxbound@gmail.com >     <mailto:paradoxbound@gmail.com> >     > <mailto:paradoxbound@gmail.com <mailto:paradoxbound@gmail.com>>> >     wrote:
>
>     Hello all,
>
>     I have a VPC built with Cloud Formation with a 10.x/16 network cut
>     up into /26 networks for spreading out across the AZs. So
x.0/26 is
>     for 1a, x.64/26 is 1b and x.128/26 for 1c. We also have a
number of
>     /26 subnets for ELBs. Foreman only shows 1number /26 network and
>     that isn't even in my Cloud Formation template, the rest of
them it
>     is showing are showing are /24 and /27 networks and many of those
>     start with 15.x. The correct Subnets are showing in the AWS
console.
>
>     The Foreman instance (1.3-rc3 is inside the VPC with SG rules to
>     allow it to pull packages and talk to the AWS api. It is new
>     installer based and other than templates and setting based Ohad's
>     post is unmodified.
>
>     Has anyone seen this behaviour and help shed a light on what is
>     happening?
>
>     Jim
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to foreman-users+unsubscribe@googlegroups.com
<mailto:foreman-users%2Bunsubscribe@googlegroups.com>.
> To post to this group, send email to foreman-users@googlegroups.com <mailto:foreman-users@googlegroups.com>.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google
Groups "Foreman users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-users+unsubscribe@googlegroups.com
<mailto:foreman-users%2Bunsubscribe@googlegroups.com>.
To post to this group, send email to foreman-users@googlegroups.com
<mailto:foreman-users@googlegroups.com>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.


You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, 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/groups/opt_out.

Tracked down the issue my muppetry, I was using the wrong set of AWS creds.

··· On 8 October 2013 13:50, Dominic Cleal wrote:

In that case, first install “foreman-console”, then run:

cd ~foreman && sudo -u foreman scl enable ruby193 ‘RAILS_ENV=production
rails c’

then at the console, replacing with your compute resource name, try:

2.0.0p247 :030 > ComputeResource.find_by_name(“your CR name”).subnets
=> <Fog::Compute::AWS::Subnets
filters={}
[]

It should list all of the subnet info from AWS, it’ll be interesting to
compare it to what you expect to list.


Dominic Cleal
Red Hat Engineering

On 08/10/13 13:24, James Bailey wrote:

Running CentOS-6.4 and Foreman-1.3-rc3.

I am happy to try and get a rails console up and running and share the
output but I have never used one before, sorry more admin than dev.
However if someone can spare a few minutes to help me get going I will
do what I can.

Jim

On 8 October 2013 13:10, Dominic Cleal <dcleal@redhat.com > > mailto:dcleal@redhat.com> wrote:

Yes please.  I only tested it with a very simple VPC setup, so hard

for

me to shed any light on it.

You could try getting information out of Fog using the Rails console
about which subnets it's aware of.  Which OS are you on?

--
Dominic Cleal
Red Hat Engineering

On 08/10/13 12:11, James Bailey wrote:
> Should I be raising this as a bug, because if this is reproducible

it

> means VPC support in Foreman-1.3 is broken?
>
> Jim
>
>
> On 8 October 2013 09:30, James Bailey <paradoxbound@gmail.com > >     <mailto:paradoxbound@gmail.com> > >     > <mailto:paradoxbound@gmail.com <mailto:paradoxbound@gmail.com>>> > >     wrote:
>
>     Hello all,
>
>     I have a VPC built with Cloud Formation with a 10.x/16 network

cut

>     up into /26 networks for spreading out across the AZs. So
x.0/26 is
>     for 1a, x.64/26 is 1b and x.128/26 for 1c. We also have a
number of
>     /26 subnets for ELBs. Foreman only shows 1number /26 network

and

>     that isn't even in my Cloud Formation template, the rest of
them it
>     is showing are showing are /24 and /27 networks and many of

those

>     start with 15.x. The correct Subnets are showing in the AWS
console.
>
>     The Foreman instance (1.3-rc3 is inside the VPC with SG rules

to

>     allow it to pull packages and talk to the AWS api. It is new
>     installer based and other than templates and setting based

Ohad’s

>     post is unmodified.
>
>     Has anyone seen this behaviour and help shed a light on what is
>     happening?
>
>     Jim
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it,

send

> an email to foreman-users+unsubscribe@googlegroups.com
<mailto:foreman-users%2Bunsubscribe@googlegroups.com>.
> To post to this group, send email to

foreman-users@googlegroups.com mailto:foreman-users@googlegroups.com.

> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google
Groups "Foreman users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-users+unsubscribe@googlegroups.com
<mailto:foreman-users%2Bunsubscribe@googlegroups.com>.
To post to this group, send email to foreman-users@googlegroups.com
<mailto:foreman-users@googlegroups.com>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.


You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, 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/groups/opt_out.


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, 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/groups/opt_out.