DNS 400 bad request, cannot provision

Hi all,

I recently installed foreman to interface with oVirt and some physical
environment I have. Install went smoothly under CentOS 6.5, however it
seems I'm unable to create any VM's due to rDNS creation erroring out. I
have proxy log info in a paste bin here: http://pastebin.com/rVXbMvZ7

This is the error in the web UI that I get:
Unable to save
Create Reverse DNS record for morgansvm.sjc.datacentric.com task failed
with the following error: ERF12-2357 [ProxyAPI::ProxyException]: Unable to
set DNS entry ([RestClient::BadRequest]: 400 Bad Request) for proxy
https://foreman.sjc.datacentric.com:8443/dns

I found a bug referencing this error code ERF12-2357 that suggested setting :dns:
false in the settings.yaml file, which I've tried, no good. I tried
defining the the rndc key path, didn't help. I added the foreman-proxy user
to the named group, but no change. Nothing I do seems to get this working.
I had tried renaming the rndc key to foreman, but that didn't help.

Is there a major step that I've missed? This is a fresh install, I haven't
mucked with anything. Desperate for help, totally out of ideas.

Thanks,
Morgan

Also, looks like I forgot to omit my domain in the error message :slight_smile: oh well.

··· On Wednesday, July 2, 2014 10:58:57 AM UTC-7, Morgan McLean wrote: > > Hi all, > > I recently installed foreman to interface with oVirt and some physical > environment I have. Install went smoothly under CentOS 6.5, however it > seems I'm unable to create any VM's due to rDNS creation erroring out. I > have proxy log info in a paste bin here: http://pastebin.com/rVXbMvZ7 > > This is the error in the web UI that I get: > Unable to save > Create Reverse DNS record for morgansvm.sjc.datacentric.com task failed > with the following error: ERF12-2357 [ProxyAPI::ProxyException]: Unable to > set DNS entry ([RestClient::BadRequest]: 400 Bad Request) for proxy > https://foreman.sjc.datacentric.com:8443/dns > > I found a bug referencing this error code ERF12-2357 that suggested > setting :dns: false in the settings.yaml file, which I've tried, no good. > I tried defining the the rndc key path, didn't help. I added the > foreman-proxy user to the named group, but no change. Nothing I do seems to > get this working. I had tried renaming the rndc key to foreman, but that > didn't help. > > Is there a major step that I've missed? This is a fresh install, I haven't > mucked with anything. Desperate for help, totally out of ideas. > > Thanks, > Morgan > > >

> Hi all,
>
> I recently installed foreman to interface with oVirt and some physical
> environment I have. Install went smoothly under CentOS 6.5, however it
> seems I'm unable to create any VM's due to rDNS creation erroring out. I
> have proxy log info in a paste bin here: http://pastebin.com/rVXbMvZ7

The dns server is returning NOTAUTH, which indicates something wrong
with your rdnc key. Did you follow the instructions here?

Foreman :: Manual

Make sure the rndc key can be ready by the foreman-proxy user. Something
like:

su - foreman-proxy -s /bin/sh -c "cat /etc/foreman-proxy/rndc.key"

> This is the error in the web UI that I get:
> Unable to save
> Create Reverse DNS record for morgansvm.sjc.datacentric.com task failed
> with the following error: ERF12-2357 [ProxyAPI::ProxyException]: Unable to
> set DNS entry ([RestClient::BadRequest]: 400 Bad Request) for proxy
> https://foreman.sjc.datacentric.com:8443/dns
>
> I found a bug referencing this error code ERF12-2357 that suggested setting :dns:
> false in the settings.yaml file, which I've tried, no good.

If you want to disable DNS management entirely, you'll need to unset
'TFTP Proxy' from the Domain and Subnet first – then set it to false in
proxy settings.yml, and finally go to Smart Proxies and click Refresh to
update the features.

··· On Wed, Jul 02, 2014 at 10:58:57AM -0700, Morgan McLean wrote:

I tried defining the the rndc key path, didn’t help. I added the
foreman-proxy user to the named group, but no change. Nothing I do
seems to get this working. I had tried renaming the rndc key to
foreman, but that didn’t help.

Is there a major step that I’ve missed? This is a fresh install, I haven’t
mucked with anything. Desperate for help, totally out of ideas.

Thanks,
Morgan


Stephen Benjamin


Red Hat GmbH | http://de.redhat.com/ | Sitz: Grasbrunn
Handelsregister: Amtsgericht München, HRB 153243
Geschäftsführer: Charles Cachera, Michael Cunningham,
Michael O’Neill, Charles Peters

I've done all of this already, like I mentioned; see my below
configuration. Is something here screwed up and I'm unaware?

DNS settings:

:dns: true
:dns_provider: nsupdate
:dns_key: /etc/foreman-proxy/rndc.key
:dns_server: 127.0.0.1
:dns_ttl: 86400

RNDC Key file:

[root@foreman foreman-proxy]# su - foreman-proxy -s /bin/sh -c "cat
/etc/foreman-proxy/rndc.key"

key "foreman" {
algorithm hmac-md5;
secret "vRsm8ncXT2lnGEhvnLN1iw==";
};

Named.conf

key "foreman" {
algorithm hmac-md5;
secret "GGd1oNCxaKsh8HA84sP1Ug==";
};

controls {
inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { "rndc-key"; };
inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { "foreman"; };
};
Zones.conf

zone "0.16.172.in-addr.arpa" {

type master;

file "/var/named/dynamic/db.0.16.172.in-addr.arpa";

update-policy {

        grant foreman zonesub ANY;

grant rndc zonesub ANY;

};

};

zone "sjc.datacentric.com" {

type master;

file "/var/named/dynamic/db.sjc.datacentric.com";

update-policy {

        grant foreman zonesub ANY;

grant rndc zonesub ANY;

};

};

Thanks,
Morgan

··· On Wed, Jul 2, 2014 at 11:34 PM, Stephen Benjamin wrote:

On Wed, Jul 02, 2014 at 10:58:57AM -0700, Morgan McLean wrote:

Hi all,

I recently installed foreman to interface with oVirt and some physical
environment I have. Install went smoothly under CentOS 6.5, however it
seems I’m unable to create any VM’s due to rDNS creation erroring out. I
have proxy log info in a paste bin here: http://pastebin.com/rVXbMvZ7

The dns server is returning NOTAUTH, which indicates something wrong
with your rdnc key. Did you follow the instructions here?

Foreman :: Manual

Make sure the rndc key can be ready by the foreman-proxy user. Something
like:

su - foreman-proxy -s /bin/sh -c “cat /etc/foreman-proxy/rndc.key”

This is the error in the web UI that I get:
Unable to save
Create Reverse DNS record for morgansvm.sjc.datacentric.com task failed
with the following error: ERF12-2357 [ProxyAPI::ProxyException]: Unable
to
set DNS entry ([RestClient::BadRequest]: 400 Bad Request) for proxy
https://foreman.sjc.datacentric.com:8443/dns

I found a bug referencing this error code ERF12-2357 that suggested
setting :dns:
false in the settings.yaml file, which I’ve tried, no good.

If you want to disable DNS management entirely, you’ll need to unset
’TFTP Proxy’ from the Domain and Subnet first – then set it to false in
proxy settings.yml, and finally go to Smart Proxies and click Refresh to
update the features.

I tried defining the the rndc key path, didn’t help. I added the
foreman-proxy user to the named group, but no change. Nothing I do
seems to get this working. I had tried renaming the rndc key to
foreman, but that didn’t help.

Is there a major step that I’ve missed? This is a fresh install, I
haven’t
mucked with anything. Desperate for help, totally out of ideas.

Thanks,
Morgan


Stephen Benjamin


Red Hat GmbH | http://de.redhat.com/ | Sitz: Grasbrunn
Handelsregister: Amtsgericht München, HRB 153243
Geschäftsführer: Charles Cachera, Michael Cunningham,
Michael O’Neill, Charles Peters

Found my key mismatch in my last email, sorry all.

Thanks,
Morgan

··· On Thu, Jul 3, 2014 at 9:17 AM, Morgan McLean wrote:

I’ve done all of this already, like I mentioned; see my below
configuration. Is something here screwed up and I’m unaware?

DNS settings:

:dns: true
:dns_provider: nsupdate
:dns_key: /etc/foreman-proxy/rndc.key
:dns_server: 127.0.0.1
:dns_ttl: 86400

RNDC Key file:

[root@foreman foreman-proxy]# su - foreman-proxy -s /bin/sh -c “cat
/etc/foreman-proxy/rndc.key”

key “foreman” {
algorithm hmac-md5;
secret “vRsm8ncXT2lnGEhvnLN1iw==”;
};

Named.conf

key “foreman” {
algorithm hmac-md5;
secret “GGd1oNCxaKsh8HA84sP1Ug==”;
};

controls {
inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { “rndc-key”; };
inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { “foreman”; };
};
Zones.conf

zone “0.16.172.in-addr.arpa” {

type master;

file "/var/named/dynamic/db.0.16.172.in-addr.arpa";

update-policy {

        grant foreman zonesub ANY;

grant rndc zonesub ANY;

};

};

zone “sjc.datacentric.com” {

type master;

file "/var/named/dynamic/db.sjc.datacentric.com";

update-policy {

        grant foreman zonesub ANY;

grant rndc zonesub ANY;

};

};

Thanks,
Morgan

On Wed, Jul 2, 2014 at 11:34 PM, Stephen Benjamin stephen@redhat.com > wrote:

On Wed, Jul 02, 2014 at 10:58:57AM -0700, Morgan McLean wrote:

Hi all,

I recently installed foreman to interface with oVirt and some physical
environment I have. Install went smoothly under CentOS 6.5, however it
seems I’m unable to create any VM’s due to rDNS creation erroring out. I
have proxy log info in a paste bin here: http://pastebin.com/rVXbMvZ7

The dns server is returning NOTAUTH, which indicates something wrong
with your rdnc key. Did you follow the instructions here?

Foreman :: Manual

Make sure the rndc key can be ready by the foreman-proxy user. Something
like:

su - foreman-proxy -s /bin/sh -c “cat /etc/foreman-proxy/rndc.key”

This is the error in the web UI that I get:
Unable to save
Create Reverse DNS record for morgansvm.sjc.datacentric.com task failed
with the following error: ERF12-2357 [ProxyAPI::ProxyException]: Unable
to
set DNS entry ([RestClient::BadRequest]: 400 Bad Request) for proxy
https://foreman.sjc.datacentric.com:8443/dns

I found a bug referencing this error code ERF12-2357 that suggested
setting :dns:
false in the settings.yaml file, which I’ve tried, no good.

If you want to disable DNS management entirely, you’ll need to unset
’TFTP Proxy’ from the Domain and Subnet first – then set it to false in
proxy settings.yml, and finally go to Smart Proxies and click Refresh to
update the features.

I tried defining the the rndc key path, didn’t help. I added the
foreman-proxy user to the named group, but no change. Nothing I do
seems to get this working. I had tried renaming the rndc key to
foreman, but that didn’t help.

Is there a major step that I’ve missed? This is a fresh install, I
haven’t
mucked with anything. Desperate for help, totally out of ideas.

Thanks,
Morgan


Stephen Benjamin


Red Hat GmbH | http://de.redhat.com/ | Sitz: Grasbrunn
Handelsregister: Amtsgericht München, HRB 153243
Geschäftsführer: Charles Cachera, Michael Cunningham,
Michael O’Neill, Charles Peters

And it still errors. FML.

Thanks,
Morgan

··· On Thu, Jul 3, 2014 at 3:19 PM, Morgan McLean wrote:

Found my key mismatch in my last email, sorry all.

Thanks,
Morgan

On Thu, Jul 3, 2014 at 9:17 AM, Morgan McLean wrx230@gmail.com wrote:

I’ve done all of this already, like I mentioned; see my below
configuration. Is something here screwed up and I’m unaware?

DNS settings:

:dns: true
:dns_provider: nsupdate
:dns_key: /etc/foreman-proxy/rndc.key
:dns_server: 127.0.0.1
:dns_ttl: 86400

RNDC Key file:

[root@foreman foreman-proxy]# su - foreman-proxy -s /bin/sh -c “cat
/etc/foreman-proxy/rndc.key”

key “foreman” {
algorithm hmac-md5;
secret “vRsm8ncXT2lnGEhvnLN1iw==”;
};

Named.conf

key “foreman” {
algorithm hmac-md5;
secret “GGd1oNCxaKsh8HA84sP1Ug==”;
};

controls {
inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { “rndc-key”; };
inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { “foreman”; };
};
Zones.conf

zone “0.16.172.in-addr.arpa” {

type master;

file "/var/named/dynamic/db.0.16.172.in-addr.arpa";

update-policy {

        grant foreman zonesub ANY;

grant rndc zonesub ANY;

};

};

zone “sjc.datacentric.com” {

type master;

file "/var/named/dynamic/db.sjc.datacentric.com";

update-policy {

        grant foreman zonesub ANY;

grant rndc zonesub ANY;

};

};

Thanks,
Morgan

On Wed, Jul 2, 2014 at 11:34 PM, Stephen Benjamin stephen@redhat.com >> wrote:

On Wed, Jul 02, 2014 at 10:58:57AM -0700, Morgan McLean wrote:

Hi all,

I recently installed foreman to interface with oVirt and some physical
environment I have. Install went smoothly under CentOS 6.5, however it
seems I’m unable to create any VM’s due to rDNS creation erroring out.
I
have proxy log info in a paste bin here: http://pastebin.com/rVXbMvZ7

The dns server is returning NOTAUTH, which indicates something wrong
with your rdnc key. Did you follow the instructions here?

Foreman :: Manual

Make sure the rndc key can be ready by the foreman-proxy user. Something
like:

su - foreman-proxy -s /bin/sh -c “cat /etc/foreman-proxy/rndc.key”

This is the error in the web UI that I get:
Unable to save
Create Reverse DNS record for morgansvm.sjc.datacentric.com task
failed
with the following error: ERF12-2357 [ProxyAPI::ProxyException]:
Unable to
set DNS entry ([RestClient::BadRequest]: 400 Bad Request) for proxy
https://foreman.sjc.datacentric.com:8443/dns

I found a bug referencing this error code ERF12-2357 that suggested
setting :dns:
false in the settings.yaml file, which I’ve tried, no good.

If you want to disable DNS management entirely, you’ll need to unset
’TFTP Proxy’ from the Domain and Subnet first – then set it to false in
proxy settings.yml, and finally go to Smart Proxies and click Refresh to
update the features.

I tried defining the the rndc key path, didn’t help. I added the
foreman-proxy user to the named group, but no change. Nothing I do
seems to get this working. I had tried renaming the rndc key to
foreman, but that didn’t help.

Is there a major step that I’ve missed? This is a fresh install, I
haven’t
mucked with anything. Desperate for help, totally out of ideas.

Thanks,
Morgan


Stephen Benjamin


Red Hat GmbH | http://de.redhat.com/ | Sitz: Grasbrunn
Handelsregister: Amtsgericht München, HRB 153243
Geschäftsführer: Charles Cachera, Michael Cunningham,
Michael O’Neill, Charles Peters