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

port label not found on service check update #9808

Closed
shoenig opened this issue Jan 13, 2021 · 3 comments · Fixed by #9830
Closed

port label not found on service check update #9808

shoenig opened this issue Jan 13, 2021 · 3 comments · Fixed by #9830
Assignees
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/networking type/bug

Comments

@shoenig
Copy link
Member

shoenig commented Jan 13, 2021

#9707 (comment)

The original problem in this issue was resolved (service registration on job update), but the follow up with port label being lost during service check registration on job update remains. Thought it had been fixed in #9736 but it's still not working.

2021-01-13T13:08:18-06:00  Task hook failed  consul_services: error getting address for check "http port alive": invalid port "http": port label not found
2021-01-13T13:07:57-06:00  Started           Task started by client
2021-01-13T13:07:56-06:00  Driver            Downloading image
2021-01-13T13:07:56-06:00  Task Setup        Building Task Directory
2021-01-13T13:07:56-06:00  Received          Task received by client
@shoenig
Copy link
Member Author

shoenig commented Jan 13, 2021

Might be duplicate of #9364, though that one is using a numeric port and this one is using a port label.

@shoenig shoenig added the stage/accepted Confirmed, and intend to work on. No timeline committment though. label Jan 13, 2021
@drewbailey drewbailey self-assigned this Jan 15, 2021
@drewbailey
Copy link
Contributor

#9736 fixed the issue for system jobs, but the generic scheduler for service jobs uses a different method to compute in place updates.

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/networking type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants