A few questions


#1

Folks in IRC seem to be a bit busy at the moment, so punting to the list.

Chef 10:

  • Quantal seems to be in a limbo state here. Using the apt repos runs
    into two different bugs for a clean install: CHEF-4077 (which is mislabled
    in Jira as a Chef 11 bug) and CHEF-3668 (which is more easily worked
    around). I did some research on this after I ran into chef-solr issues
    after upgrading from Precise -> Quantal.
  • Does bootstrapping chef-server via chef-solo install an embedded copy
    of couchdb, or will it use one that’s already there? The apt repos only
    seem to go up to 10.18.2, and I’m wondering if the chef-solr issue might be
    fixed in 10.24.0. Bootstrapping a new setup with 10.24.0 via chef-solo did
    result in a working chef-solr setup, so I’d like to get that working with
    my existing server.

Chef 11:

  • I’m still working on testing my Chef 11 server, which is why I want to
    fix the existing 10 server for the moment. However, I already use the
    standard ports 80/443 and would like to run Chef on alternate ports. I
    configured chef-server.rb like so:
    https://gist.github.com/stormerider/2d189b444b01af75f08b – however,
    while it runs on https://ops.xxx.co:8443, the login form does a POST to
    https://ops.xxx.co without the port in the URI, which then fails. I’m
    guessing I’ve missed a variable somewhere but it’s not obvious in the docs
    what I need to tweak to get this working.

Thanks for any help that can be provided.


~~ StormeRider ~~

“Every world needs its heroes […] They inspire us to be better than we
are. And they protect from the darkness that’s just around the corner.”

(from Smallville Season 6x1: “Zod”)

On why I hate the phrase “that’s so lame”… http://bit.ly/Ps3uSS


#2

On Tuesday, April 16, 2013 at 9:31 PM, Morgan Blackthorne wrote:

Chef 11:
I’m still working on testing my Chef 11 server, which is why I want to fix the existing 10 server for the moment. However, I already use the standard ports 80/443 and would like to run Chef on alternate ports. I configured chef-server.rb like so: https://gist.github.com/stormerider/2d189b444b01af75f08b – however, while it runs on https://ops.xxx.co:8443, the login form does a POST to https://ops.xxx.co without the port in the URI, which then fails. I’m guessing I’ve missed a variable somewhere but it’s not obvious in the docs what I need to tweak to get this working.

See Bryan’s earlier post about the beta release of a new chef server release. It’s supposed to fix this issue.


Daniel DeLeo


#3

Aha, thanks for the pointer! Upgrading now.


~~ StormeRider ~~

“Every world needs its heroes […] They inspire us to be better than we
are. And they protect from the darkness that’s just around the corner.”

(from Smallville Season 6x1: “Zod”)

On why I hate the phrase “that’s so lame”… http://bit.ly/Ps3uSS

On Tue, Apr 16, 2013 at 9:33 PM, Daniel DeLeo dan@kallistec.com wrote:

On Tuesday, April 16, 2013 at 9:31 PM, Morgan Blackthorne wrote:

Chef 11:

  • I’m still working on testing my Chef 11 server, which is why I want
    to fix the existing 10 server for the moment. However, I already use the
    standard ports 80/443 and would like to run Chef on alternate ports. I
    configured chef-server.rb like so:
    https://gist.github.com/stormerider/2d189b444b01af75f08b – however,
    while it runs on https://ops.xxx.co:8443, the login form does a POST to
    https://ops.xxx.co without the port in the URI, which then fails. I’m
    guessing I’ve missed a variable somewhere but it’s not obvious in the docs
    what I need to tweak to get this working.

See Bryan’s earlier post about the beta release of a new chef server
release. It’s supposed to fix this issue.


Daniel DeLeo