Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy sensu agent without validation (only the config file) #1322

Closed
davidphay opened this issue May 9, 2022 · 0 comments · Fixed by #1332
Closed

Deploy sensu agent without validation (only the config file) #1322

davidphay opened this issue May 9, 2022 · 0 comments · Fixed by #1332

Comments

@davidphay
Copy link

Description of problem

  • What did you do?
    I try to install sensu agent without the backend

  • What happened?
    I have an error because we expose only the socket (API is unavailable)

  • What did you expect to happen?
    I only want configure the sensu agent with the file(agent.yml) without any validation (sensu API or sensuctl)

  • How can someone reproduce the problem?
    use a fake URL and agent_managed_entity param to true.

Command used and debugging output

class {'sensu':
  use_ssl => true,
  api_host => 'my-fake-backend.lab',
  api_port => 443,
}

class { 'sensu::agent':
  backends      => ["my-fake-backend.lab:443"],
  subscriptions => ['linux'],
  labels      => { 'location' => 'uswest', 'contacts' => 'ops@example.com' },
  annotations => { 'cpu.warning' => '90', 'cpu.critical' => '100' },
  entity_name => "test2",
  namespace => "LAB",
  agent_managed_entity  => true,
}
  • What does your puppet config look like (including any hiera config)

  • Is this a masterless or master based puppet setup?
    master based setup

Platform and version information

  • Your OS: Linux CentOS 7
  • Your Ruby version: 2.4
  • Your version of Puppet: Puppet 7 CE
  • Your version of Sensu: 6.6
  • Your version of this module: 5.8

Anything else to add that you think will be helpful?

Notice: /Stage[main]/Sensu::Agent/Service[sensu-agent]: Triggered 'refresh' from 1 event
Error: Unable to connect to https://my-fake-backend.lab:443/api/core/v2/namespaces/LAB/entities/test2: Failed to open TCP connection to my-fake-backend.lab:443 (getaddrinfo: Name or service not known)
Notice: Failed to connect to validate entity test2; sleeping 2 seconds before retry
Error: Unable to connect to https://my-fake-backend.lab:443/api/core/v2/namespaces/LAB/entities/test2: Failed to open TCP connection to my-fake-backend.lab:443 (getaddrinfo: Name or service not known)
Notice: Failed to connect to validate entity test2; sleeping 2 seconds before retry
Error: Unable to connect to https://my-fake-backend.lab:443/api/core/v2/namespaces/LAB/entities/test2: Failed to open TCP connection to my-fake-backend.lab:443 (getaddrinfo: Name or service not known)
Notice: Failed to connect to validate entity test2; sleeping 2 seconds before retry
Error: Unable to connect to https://my-fake-backend.lab:443/api/core/v2/namespaces/LAB/entities/test2: Failed to open TCP connection to my-fake-backend.lab:443 (getaddrinfo: Name or service not known)
Notice: Failed to connect to validate entity test2; sleeping 2 seconds before retry
Error: Unable to connect to https://my-fake-backend.lab:443/api/core/v2/namespaces/LAB/entities/test2: Failed to open TCP connection to my-fake-backend.lab:443 (getaddrinfo: Name or service not known)
Notice: Failed to connect to validate entity test2; sleeping 2 seconds before retry
Error: Unable to connect to https://my-fake-backend.lab:443/api/core/v2/namespaces/LAB/entities/test2: Failed to open TCP connection to my-fake-backend.lab:443 (getaddrinfo: Name or service not known)
Notice: Failed to connect validate entity test2 within timeout window of 10 seconds; giving up.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant