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

Fix: Delayed start services for support- services fail #4159

Merged
merged 1 commit into from
Sep 19, 2022
Merged

Fix: Delayed start services for support- services fail #4159

merged 1 commit into from
Sep 19, 2022

Conversation

bnevis-i
Copy link
Collaborator

Delayed start is not working for support services. Among other problems, for support services,
the service key is support-servicename,
but the service key in docker-compose is just servicename.

Update pre-seeding script to account for this.

Signed-off-by: Bryon Nevis bryon.nevis@intel.com

Closes #4152

PR Checklist

Please check if your PR fulfills the following requirements:

  • I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
  • I am not introducing a new dependency (add notes below if you are)
  • I have added unit tests for the new feature or bug fix (if not, why?) n/a
  • I have fully tested (add details below) this the new feature or bug fix (if not, why?)
  • I have opened a PR for the related docs change (if not, why?) n/a

Testing Instructions

(Update later with related edgex-compose change.)

New Dependency Instructions (If applicable)

Delayed start is not working for support services.
Among other problems, for support services,
the service key is support-servicename,
but the service key in docker-compose is just servicename.

Update pre-seeding script to account for this.

Signed-off-by: Bryon Nevis <bryon.nevis@intel.com>
@sonarcloud
Copy link

sonarcloud bot commented Sep 19, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
4.7% 4.7% Duplication

device-bacnet device-camera device-grove device-modbus device-mqtt device-rest device-snmp \
device-virtual device-rfid-llrp device-coap device-gpio \
app-service-http-export app-service-mqtt-export app-service-sample app-rfid-llrp-inventory \
app-service-external-mqtt-trigger; do
# Temporary workaround because service name in dockerfile is not consistent with service key.
# TAF scripts depend on legacy docker-compose service name. Fix in EdgeX 3.0.
service=`echo -n ${dockerservice} | sed -e 's/app-service-/app-/'`
service=`echo -n ${dockerservice} | sed -e 's/app-service-/app-/'`
# support- services have the opposite problem. service key is right, service name in docker isn't
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same issue with the core services. Service name is data while the service key is `core-data'. Something we need to clean-up in EdgeX 3.0. I have update this issue to cover App, Core and Support service names.
edgexfoundry/edgex-compose#231

Copy link
Member

@lenny-goodell lenny-goodell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bnevis-i bnevis-i merged commit 726ff50 into edgexfoundry:main Sep 19, 2022
@bnevis-i bnevis-i deleted the issue-4152 branch September 19, 2022 22:29
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 this pull request may close these issues.

Delayed start support services failed
2 participants