Wacky environment column in puppet.hosts

[Jason Koppe]

I installed puppet 2.6 on my master and increased dbconnections in hopes that it would get me past some 0.25.5 hurdles (one described in http://groups.google.com/group/puppet-users/browse_thread/thread/7ac829c7cb3b2d18/a58f9c8472f2dd8f) -- the upgrade definitely helped because puppetmasterd is updating more in the puppet database without a max connections limit, but I'm seeing some other fun stuff.

Below I null out the environment column, show that it's null for a particular host, then run puppetd a few times on the host.

mysql for root@localhost on indadm1> update hosts set environment = NULL;
Query OK, 1 row affected (0.01 sec)
Rows matched: 99  Changed: 1  Warnings: 0

mysql for root@localhost on indadm1> select * from hosts where name like 'iad-web2%';
+----+---------------------+---------------+-------------+---------------------+-----------------+-------------+---------------------+----------------+---------------------+
| id | name                | ip            | environment | last_compile        | last_freshcheck | last_report | updated_at          | source_file_id | created_at          |
+----+---------------------+---------------+-------------+---------------------+-----------------+-------------+---------------------+----------------+---------------------+
|  9 | iad-web2.indeed.net | 10.24.186.136 | NULL        | 2010-08-06 03:31:23 | NULL            | NULL        | 2010-08-06 03:31:23 |           NULL | 2010-06-08 19:47:22 |
+----+---------------------+---------------+-------------+---------------------+-----------------+-------------+---------------------+----------------+---------------------+
1 row in set (0.00 sec)

mysql for root@localhost on indadm1> select * from hosts where name like 'iad-web2%';
+----+---------------------+---------------+----------------+---------------------+-----------------+-------------+---------------------+----------------+---------------------+
| id | name                | ip            | environment    | last_compile        | last_freshcheck | last_report | updated_at          | source_file_id | created_at          |
+----+---------------------+---------------+----------------+---------------------+-----------------+-------------+---------------------+----------------+---------------------+
|  9 | iad-web2.indeed.net | 10.24.186.136 | --- production | 2010-08-06 03:31:23 | NULL            | NULL        | 2010-08-06 03:32:42 |           NULL | 2010-06-08 19:47:22 |
+----+---------------------+---------------+----------------+---------------------+-----------------+-------------+---------------------+----------------+---------------------+
1 row in set (0.00 sec)

mysql for root@localhost on indadm1> select * from hosts where name like 'iad-web2%';
+----+---------------------+---------------+----------------------+---------------------+-----------------+-------------+---------------------+----------------+---------------------+
| id | name                | ip            | environment          | last_compile        | last_freshcheck | last_report | updated_at          | source_file_id | created_at          |
+----+---------------------+---------------+----------------------+---------------------+-----------------+-------------+---------------------+----------------+---------------------+
|  9 | iad-web2.indeed.net | 10.24.186.136 | --- "--- production" | 2010-08-06 03:32:50 | NULL            | NULL        | 2010-08-06 03:32:50 |           NULL | 2010-06-08 19:47:22 |
+----+---------------------+---------------+----------------------+---------------------+-----------------+-------------+---------------------+----------------+---------------------+
1 row in set (0.00 sec)


--
Jason Koppe
Jason.Rob...@gmail.com
Cell (210) 445-8242

[James Turnbull]

Jason Koppe wrote:
> I installed puppet 2.6 on my master and increased dbconnections in hopes
> that it would get me past some 0.25.5 hurdles (one described in
> http://groups.google.com/group/puppet-users/browse_thread/thread/7ac829c7cb3b2d18/a58f9c8472f2dd8f)
> -- the upgrade definitely helped because puppetmasterd is updating more
> in the puppet database without a max connections limit, but I'm seeing
> some other fun stuff.
>
> Below I null out the environment column, show that it's null for a
> particular host, then run puppetd a few times on the host.
>
> mysql for root@localhost on indadm1> update hosts set environment = NULL;
> Query OK, 1 row affected (0.01 sec)
> Rows matched: 99 Changed: 1 Warnings: 0
>

Jason

That's a bug - can you please log a ticket.

Thanks

James Turnbull

--
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571

[Jason Koppe]

http://projects.puppetlabs.com/issues/4487

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.