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.

Sign up for GitHub

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

Jump to bottom

ServiceEnableTagOverride temporarily false after updating tags via catalog #2413

Open
nickwales opened this issue Oct 14, 2016 · 0 comments
Open

ServiceEnableTagOverride temporarily false after updating tags via catalog #2413

nickwales opened this issue Oct 14, 2016 · 0 comments
Labels
theme/service-metadata Anything related to management/tracking of service metadata type/bug Feature does not function as expected

Comments

@nickwales
Copy link
Contributor

Client: 0.7.0
Server: 0.7.0

consul info for both Client and Server

Client:

agent:
    check_monitors = 0
    check_ttls = 0
    checks = 40
    services = 40
build:
    prerelease =
    revision = 'a189091
    version = 0.7.0
consul:
    known_servers = 3
    server = false
runtime:
    arch = amd64
    cpu_count = 24
    goroutines = 75
    max_procs = 24
    os = linux
    version = go1.6.3
serf_lan:
    encrypted = false
    event_queue = 0
    event_time = 1322
    failed = 0
    health_score = 0
    intent_queue = 0
    left = 0
    member_time = 203710
    members = 16
    query_queue = 0
    query_time = 1848

Server:

agent:
    check_monitors = 0
    check_ttls = 0
    checks = 1
    services = 2
build:
    prerelease =
    revision = 'a189091
    version = 0.7.0
consul:
    bootstrap = false
    known_datacenters = 23
    leader = false
    leader_addr = 10.28.188.52:8300
    server = true
raft:
    applied_index = 25315303
    commit_index = 25315303
    fsm_pending = 0
    last_contact = 67.123638ms
    last_log_index = 25315303
    last_log_term = 1511
    last_snapshot_index = 25309666
    last_snapshot_term = 1511
    latest_configuration = [{Suffrage:Voter ID:10.28.188.52:8300 Address:10.28.188.52:8300} {Suffrage:Voter ID:10.28.188.51:8300 Address:10.28.188.51:8300} {Suffrage:Voter ID:10.28.188.57:8300 Address:10.28.188.57:8300}]
    latest_configuration_index = 24077016
    num_peers = 2
    protocol_version = 1
    protocol_version_max = 3
    protocol_version_min = 0
    snapshot_version_max = 1
    snapshot_version_min = 0
    state = Follower
    term = 1511
runtime:
    arch = amd64
    cpu_count = 2
    goroutines = 1413
    max_procs = 2
    os = linux
    version = go1.6.3
serf_lan:
    encrypted = false
    event_queue = 0
    event_time = 1322
    failed = 0
    health_score = 0
    intent_queue = 0
    left = 0
    member_time = 203687
    members = 16
    query_queue = 0
    query_time = 1848
serf_wan:
    encrypted = false
    event_queue = 0
    event_time = 1
    failed = 0
    health_score = 0
    intent_queue = 0
    left = 0
    member_time = 1270
    members = 103
    query_queue = 0
    query_time = 1

Operating system and Environment details

CentOS Linux release 7.1.1503 (Core)

Description of the Issue (and unexpected/desired result)

  • ServiceEnableTagOverride is set true
  • When updating tags via the catalog ServiceEnableTagOverride becomes false, until presumably the agent syncs, even when EnableTagOverride: true is set in the payload to the catalog.
  • Can't update again until ServiceEnableTagOverride becomes true

Reproduction steps

  • Create service
  • Update tags
  • Try to update tags immediately after, get rejected.
@slackpad slackpad added type/bug Feature does not function as expected theme/service-metadata Anything related to management/tracking of service metadata labels May 18, 2017
@slackpad slackpad mentioned this issue May 18, 2017
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
theme/service-metadata Anything related to management/tracking of service metadata type/bug Feature does not function as expected
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nickwales @slackpad